March 28, 2011 at 4:21 am
Created my first SSIS package through the wizard. It runs fine when I execute by clicking on it, but when I put it into the SSIS repository it fails everytime and I get the following message:
Source: SDimport Connection manager "SourceConnectionExcel" 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: 2011-03-25 17:15:15.07 Code: 0xC020801C Source: Data Flow Task Source - Sheet1$ [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: ... The package execution fa... The step failed.
Can anyone help ?
March 28, 2011 at 4:34 am
Are you running the package on a 64-bit machine? If yes, the JET OLE DB provider, used to connect to Excel files, can only run in 32-bit.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 28, 2011 at 4:38 am
It runs on 64-bit. So how do I import from excel then ?
March 28, 2011 at 4:50 am
MarvinTheAndriod (3/28/2011)
It runs on 64-bit. So how do I import from excel then ?
By executing the package in 32-bit mode. If SQLServer 2005, run the package with the dtexec utility located in the x86 program files folder.
Otherwise you can select a checkbox in the execution options in the SQL Server Agent Integration Services jobstep.
More information: http://msdn.microsoft.com/en-us/library/ms162810.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 28, 2011 at 5:01 am
Thanks. Ticked the option for 32bit execution. I now get this error:
Option "/X86" is not valid. The command line parameters are invalid. The step failed.
March 28, 2011 at 5:15 am
MarvinTheAndriod (3/28/2011)
Thanks. Ticked the option for 32bit execution. I now get this error:Option "/X86" is not valid. The command line parameters are invalid. The step failed.
You are running this from a SQL Server 2008 Agent? Can you post the entire command line? (the last tab in the jobstep editor)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 28, 2011 at 6:09 am
Its being run on 2005 SSIS, the command line is as follows:
/SQL "\STImport" /SERVER "DA-ACC-1" /X86 /CHECKPOINTING OFF /REPORTING E
March 29, 2011 at 12:51 am
MarvinTheAndriod (3/28/2011)
Its being run on 2005 SSIS, the command line is as follows:/SQL "\STImport" /SERVER "DA-ACC-1" /X86 /CHECKPOINTING OFF /REPORTING E
That's odd, SQL Server 2005 shouldn't have the checkbox for 32-bit execution.
The following MSDN pages explain how a package should be run in 32-bit mode:
http://msdn.microsoft.com/en-us/library/ms141701(v=SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms139805(v=SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms141766(v=SQL.90).aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply