October 4, 2010 at 9:58 am
We've a SSIS sql agent job running on a server but the actual SSIS package is deployed to the msdb database of another server. When i tried to run the job, i'm getting the below error. Everything seems to be right but I'm not sure why am i getting this error. The account has sql admin rights.
Executed as user: SQLIS. ...cute Package Utility Version 9.00.4035.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:37:20 PM Error: 2010-09-30 14:37:21.65 Code: 0xC0202009 Source: NLS_Files Connection manager "Excel Err Report" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2010-09-30 14:37:21.65 Code: 0xC00291EC Source: New Excel Err Report File Execute SQL Task Description: Failed to acquire connection "Excel Err Report". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:37:20 PM Finished: 2:37:21 PM Elapsed: 0.875 seconds. The package execution failed. The step failed.
October 4, 2010 at 11:34 am
Any thoughts?
October 4, 2010 at 11:53 am
Are you running on a 64-bit server? If so, have you tried running the package in 32-bit mode to see whether that fixes your problem?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 4, 2010 at 12:13 pm
The server on which the SSIS job runs as well as the server on which the SSIS package was deployed, both are 64-bit servers.
If I find a 32 bit server, should i deploy the package on this server and let the job remain on the server it is existing now?
Thanks.
October 4, 2010 at 12:15 pm
Phil Parkin (10/4/2010)
Are you running on a 64-bit server? If so, have you tried running the package in 32-bit mode to see whether that fixes your problem?
Sorry, I'm not sure how to run the package in 32-bit mode...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply