November 1, 2017 at 7:11 am
Hello,
I have SSIS package which worked fine for last 2 years and was successfully run in last month but suddenly started failing with error below. Nothing as far as I know changed on server or execution parameters. Package is being run as x32 bit mode and was never changed. I'm completely stumped. Searched online to no avail.
EventActvity:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNE CTIONMANAGER. 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.
November 1, 2017 at 7:33 am
artisticcheese - Wednesday, November 1, 2017 7:11 AMHello,I have SSIS package which worked fine for last 2 years and was successfully run in last month but suddenly started failing with error below. Nothing as far as I know changed on server or execution parameters. Package is being run as x32 bit mode and was never changed. I'm completely stumped. Searched online to no avail.
Package:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (1).". EventActvity:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNE CTIONMANAGER. 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.
There was a security update for Windows that may have affected this. Try downloading and using the ACE drivers instead of the Jet Drivers.
Refer to this article for more information:
October 10, 2017—KB4041679
Sue
November 1, 2017 at 9:04 am
Sue_H - Wednesday, November 1, 2017 7:33 AMartisticcheese - Wednesday, November 1, 2017 7:11 AMHello,I have SSIS package which worked fine for last 2 years and was successfully run in last month but suddenly started failing with error below. Nothing as far as I know changed on server or execution parameters. Package is being run as x32 bit mode and was never changed. I'm completely stumped. Searched online to no avail.
Package:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (1).". EventActvity:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNE CTIONMANAGER. 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.
There was a security update for Windows that may have affected this. Try downloading and using the ACE drivers instead of the Jet Drivers.
Refer to this article for more information:
October 10, 2017—KB4041679Sue
Thanks, this worked. Replaced JET with ACE. As an additional bonus since ACE comes in x64 package no more x32 code execution path.
November 1, 2017 at 9:25 am
Sue_H - Wednesday, November 1, 2017 7:33 AMThere was a security update for Windows that may have affected this. Try downloading and using the ACE drivers instead of the Jet Drivers.
Refer to this article for more information:
October 10, 2017—KB4041679Sue
Thanks for this link Sue. We still use some JET packages and we haven't installed that KB yet. Will ask network team to delay, as not sure we'll have a chance to work through the entire package catalog before patch day.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 1, 2017 at 10:10 am
It's kind of sad how MS did this as so many people have worked around the issues with Jet/ACE drivers, 32/64 bit. With the widespread use of Excel, I would have thought they would provide a bit more notice for everyone rather than just breaking things.
Sue
November 1, 2017 at 10:23 am
I all honesty, I hate the JET/ACE drivers. I'd take a CSV, tab-delimited, etc, or even a fixed width file over a .xls(x) any day. I least then I can control the data; and not getting a ****ing Truncation error on line 127 because the text is longer in column J in that row that it is in rows 2-50... ARGH. :hehe:
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 1, 2017 at 11:12 am
Thom A - Wednesday, November 1, 2017 10:23 AMI all honesty, I hate the JET/ACE drivers. I'd take a CSV, tab-delimited, etc, or even a fixed width file over a .xls(x) any day. I least then I can control the data; and not getting a ****ing Truncation error on line 127 because the text is longer in column J in that row that it is in rows 2-50... ARGH. :hehe:
I'd rather have any kind of text file as well.
Unfortunately, Excel seems to be the most popular "database" used these days. Wait until they have spreadsheet isolation levels.
Sue
November 1, 2017 at 11:18 am
Sue_H - Wednesday, November 1, 2017 11:12 AMWait until they have spreadsheet isolation levels.
Oh... are those apart of the rumoured TraSH (Transfer from SpreadsHeet) Drivers? :laugh:
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply