SSMS Import of MS Access accdb external component has thrown an exception (System.Data)

Question

SSMS Import of MS Access accdb external component has thrown an exception (System.Data)

Richard Williams 15

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)

Richard Williams 15 Reputation points

2024-12-14T09:40:25.9933333+00:00

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?
Richard Williams 15 Reputation points

2024-12-17T13:05:46.2666667+00:00

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?
Richard Williams 15 Reputation points

2025-01-10T12:20:15.0066667+00:00

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?
Awais_Saad 0 Reputation points

2025-02-18T19:22:56.72+00:00

we have the same problem after upgrading to latest SSMS 20.2

1 answer

Your answer

Richard Williams 15 Reputation points

2024-12-14T09:40:25.9933333+00:00

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?
Richard Williams 15 Reputation points

2024-12-17T13:05:46.2666667+00:00

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?
Richard Williams 15 Reputation points

2025-01-10T12:20:15.0066667+00:00

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?
Awais_Saad 0 Reputation points

2025-02-18T19:22:56.72+00:00

we have the same problem after upgrading to latest SSMS 20.2

Answer 1

ZoeHui-MSFT 41,491

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.

Richard Williams 15 Reputation points

2024-12-14T09:45:16.1666667+00:00

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!
ZoeHui-MSFT 41,491 Reputation points

2024-12-16T01:33:20.83+00:00

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. :)
Richard Williams 15 Reputation points

2024-12-17T12:58:57.15+00:00

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?
Williams, Alan 0 Reputation points

2025-04-23T13:58:54.19+00:00

As with all of the "solutions" I am finding to this constantly recurring issue, the link to a microsoft site points to a dead-end as of April 2025, so no help is provided whatsoever. There is no redirection to a valid link that contains the proper files. The dead end link provides the links to buy other MS products in no way related to the issue. That is a JOKE!

Microsoft simply does not support their product properly. People are constantly given the runaround to this issue and they do not take ownership of their product. This has been going on for years. They publish office security patches that break the AccessDatabaseEngine and then leave the customer hanging.

Share via

SSMS Import of MS Access accdb external component has thrown an exception (System.Data)

1 answer

Your answer