OK, I'm out of ideas on this one, hoping someone here has seen this before: I can connect to the .mdb file but when I run the task it crashes with an error saying it can't get a connection.
Platform is Windows Server 2008 R2 running VS 2005 (yeah, I know but it's a contract job so there's nothing I can do about this). On this platform when I test my connection (OLEDB Jet 4.0 or Office 12) via the connection manager, it is successful. When I configure my OLE DB Source I can see the tables & columns from the MS Access DB. When I run the task or package it immediately crashes with:
[OLE DB Source ] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Office12" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
On my development machine (Windows XP, oh-yeah, workin' for the gov'mt here, and VS 2005) I can run this package successfully either as a task or as execute package. I can execute it using a connection via the Jet 4.0 provider.
I've verified that I can open the .mdb and make changes directly.
I've downloaded the Office 12 drivers. Same error whether I configure my connection via Office 12 or OLEDB Jet 4.0
I've verified that the .ldb file can be created by the account executing the SSIS package
How is it possible that SSIS can connect and show me the tables & columns in the .mdb but then crashes and can't acquire a connection when I execute the task?
Thanks for any help with this!