October 16, 2009 at 7:49 am
I have an SSIS package that runs fine on several servers. The app it runs for just moved to a 64bit sql server so I put the package there and it fails every time. It runs successfully from the BIDS Designer on the server, but won't run from a SQL Server Agent job. Error message:
Executed as user: MyDomain\SQLAdmin. ...cute Package Utility Version 9.00.4035.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:08:08 AM Error: 2009-10-16 09:08:09.20 Code: 0xC0202009 Source: FTE_Change_Report Connection manager "Excel Connection Manager" 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: 2009-10-16 09:08:09.20 Code: 0xC020801C Source: Data Flow Task Excel Destination [68] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" 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 . The step failed.
The package exports a result set to Excel. This is crazy. It runs on any server but the one it's supposed to. It runs in the Designer on the server. I can't figure it out. Need some help.
October 16, 2009 at 8:03 am
Sounds like a permissions issue, is it exporting to a local directory and what access does it need to write to that excel destination, and what account are you running it under.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
October 16, 2009 at 8:07 am
As soon as I saw Excel and "Class not registered" I knew your problem..
There are no 64-bit excel drivers.
But don't worry, there IS a workaround..
You have to call the 32-bit version of DTEXEC..
You can use the command line (mostly) that you can get from the existing SQL Agent job step. BUT you specify OS Command as the type and provide that command line with the full path to the 32-bit DTExec command which will probably be located under C:\Program Files(X86).
As it sits now you are calling the package with a 64-bit executable, and it wants 64-bit drivers, but there aren't any 64-bit jet drivers available to you so it fails. We are forcing it to use the 32-bit version which will work just fine.
Clear?
CEWII
October 16, 2009 at 8:53 am
That was it! Run the package with the 32 bit dtexec.exe. Thank you very very much.
October 16, 2009 at 9:01 am
You are welcome, had the very same problem last year..
CEWII
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply