asked on NOPROVIDER_ 64BIT_ERROR attempting to import Access table to SQL Server
I had this question after viewing SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64B
I have a similar issue. I am trying to import a table from an Access 2016 to SQl Server 2008 R2. This is successful if done through Management Studio -- Tasks -- Import Data. However I would like to automate through a Job in SQL Server Agent. Created a package to do this during the manual import by checking "Save SSIS Package". When I try to run this package through a job I encounter the exact same error above. Tried to run this package with dtexec as well but get the same error. Is there a way to do this ? Thanks.
I have a similar issue. I am trying to import a table from an Access 2016 to SQl Server 2008 R2. This is successful if done through Management Studio -- Tasks -- Import Data. However I would like to automate through a Job in SQL Server Agent. Created a package to do this during the manual import by checking "Save SSIS Package". When I try to run this package through a job I encounter the exact same error above. Tried to run this package with dtexec as well but get the same error. Is there a way to do this ? Thanks.
Microsoft AccessMicrosoft SQL Server
Last Comment
Deepak Chauhan
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Above error is showing ""Could not use '\\Kermit\WCHub\WCHubTCM_b
Please check if that file already opened somewhere else.
Please check if that file already opened somewhere else.
ASKER
Yes it is opened by another user. It is a back end Access file that multiple users may have open. I can successfully execute the import from Management Studio when other users are using the file. I thought there would be a way to do this through a Job as well. A matter of permissions ?
From permissions standpoint you can check the SQL Agent service account ( by which you are running SQL Agent service ) should have permissions on Assess file and database also because using SSMS you are connecting with your ID ( having all administrative permissions everywhere) but whenever we schedule a job , all operation will be done by SQL Agent service account.
Message
Executed as user: STAMP\TCM_Services. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 9:18:28 AM Error: 2017-11-03 09:18:30.37 Code: 0xC0202009 Source: Import_tblWCHub Connection manager "SourceConnectionOLEDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Could not use '\\Kermit\WCHub\WCHubTCM_b