January 11, 2011 at 12:55 pm
Hi everyone - Does anyone have experience with this issue. Trying to pump data into 32 bit Excel 2007 in a 64 bit environment via command line using dtexec.
The environment:
Windows Server 2003 R2
Enterprise x64 Edition
Service Pack 2
Error Message:
Error: 2011-01-11 13:45:27.92
Code: 0xC0202009
Source: AGI_RECON_Report_Mailing_Extract Connection manager "Excel_2007"
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" H
result: 0x80040154 Description: "Class not registered".
End Error
Error: 2011-01-11 13:45:27.92
Code: 0xC020801C
Source: Current Program year 2009 2010 OLE DB Destination [1191]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAG
ER. The AcquireConnection method call to the connection manager "Excel_2007" fa
iled 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: 2011-01-11 13:45:27.92
Code: 0xC0047017
Source: Current Program year 2009 2010 DTS.Pipeline
Description: component "OLE DB Destination" (1191) failed validation and retu
rned error code 0xC020801C.
End Error
January 11, 2011 at 1:02 pm
How are you running the package? If it is through Agent then you need to execute the package with the 32-bit DTExec command. Unfortunately I don't have my link list right now.. But you chose operating system command instead of Integration services and fill out the command line to execute the package, in SQL 2008 they now have a checkbox that basically says, run 32-bit version..
CEWII
January 11, 2011 at 1:17 pm
I'm manually executing the SSIS via a .cmd file using dtexec.
January 12, 2011 at 7:53 am
tan110 (1/11/2011)
I'm manually executing the SSIS via a .cmd file using dtexec.
Make sure you use the dtexec from the 32-bit program folder.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 12, 2011 at 9:31 am
tan110 (1/11/2011)
I'm manually executing the SSIS via a .cmd file using dtexec.
I agree with da-zero, use the explicit path to the DTExec in C:\Program Files (x86), don't rely on the path. you have it easier than most in this case. Most have to switch TO using the operating system command.
CEWII
January 12, 2011 at 11:42 am
Yes, that worked, thank you so much!
January 12, 2011 at 11:50 am
tan110 (1/12/2011)
Yes, that worked, thank you so much!
No problem. Glad it all worked out.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 12, 2011 at 12:27 pm
Excellent..
CEWII
January 13, 2011 at 8:48 am
For SSIS jobs there's an 'Execution Options' tab iwhere you can specify 'Use 32 bit runtime' , no need to write batch files.
Regards
January 13, 2011 at 8:59 am
Paul Brewer (1/13/2011)
For SSIS jobs there's an 'Execution Options' tab iwhere you can specify 'Use 32 bit runtime' , no need to write batch files.Regards
That is unfortunately only possible from SQL Server 2008 or higher.
See the following url:
http://msdn.microsoft.com/en-us/library/ms141701(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 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply