This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 11%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERW%3C/text%3E%3C/svg%3E)
I've been using SQL Server Management Studio for some time to import tables from MS Access into SQL Server.
Now I get an error
External component has thrown an exception. (System.Data)
when I choose an Access database to import from. This worked only a couple of weeks ago, any ideas what might have changed?
I only have Office 2016 installed. The full error is:
External component has thrown an exception. (System.Data)
Program Location:
at System.Data.OleDb.DataSourceWrapper.InitializeAndCreateSession(OleDbConnectionString constr, SessionWrapper& sessionWrapper) at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection) at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionInternal.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.OleDb.OleDbConnection.Open() at Microsoft.SqlServer.Dts.DtsWizard.DTSWizard.GetOpenedConnection(WizardInputs wizardInputs, String connEntryName) at Microsoft.SqlServer.Dts.DtsWizard.Step1.OnLeavePage(LeavePageEventArgs e)
As I said in my previous answer, this did seem to work and I was able to import Access tables into MSSQL using SSMS. Then, a couple of days later the same error was occurring in SSMS. I tried both version 19 and version 20, same issue. So I uninstalled and reinstalled accessdatabaseengine_X64.exe and accessdatabaseengine.exe again. The problem has gone away, again! Can anyone explain this instability?
This solution worked but now, each time I try to use import I have to uninstall and then re-install accessdatabaseengine_X64.exe and accessdatabaseengine.exe again before the import works. Is there some way of stopping this from happening?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 81%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
we have the same problem after upgrading to latest SSMS 20.2
Hi @Richard Williams,
Please try to install both 32bit and 64bit version for access.
You may download 32-bit and 64-bit access drivers from this source https://www.microsoft.com/en-us/download/details.aspx?id=54920 first, and then go to terminal -> go to downloads (or where you downloaded the access drivers to) -> run "accessdatabaseengine_X64.exe /quiet" -> then run "Accessdatabaseengine.exe /quiet"
Or refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
This worked although I had to uninstall the existing versions of these two files. The sizes of the two new files that I downloaded and installed were different from the original ones which always worked fine until a couple of weeks ago. So Microsoft seems to have changed something in the SSMS import which then required a reinstall of accessdatabaseengine_X64.exe and accessdatabaseengine.exe, nice that they didn't warn users!
Hi @Richard Williams,
If this helps on your issue, you could mark it as answer so other user with similar problem could see this easier. :)
This worked fine, I was able to import the tables that I needed from Access to MSSQL, however, a few days later the same error message appeared. I tried both version 19 of SSMS and 20, same issue. I then went back uninstalled and re-installed accessdatabaseengine_X64.exe and accessdatabaseengine.exe and the import worked again. Cab anyone suggest why this is going on?
This did solve the problem but I had to uninstall the existing accessdatabaseengine_X64.exe and accessdatabaseengine.exe installations before reinstalling them. Then, a couple of days later the same error was occurring in SSMS. I tried both version 19 and version 20, same issue. So I uninstalled and reinstalled accessdatabaseengine_X64.exe and accessdatabaseengine.exe again. The problem has gone away, again! Can anyone explain this instability?