SSIS Package Execution Error - The requested OLE DB provider Microsoft.ACE.OLEDB.16.0 is not registered

Question

SSIS Package Execution Error - The requested OLE DB provider Microsoft.ACE.OLEDB.16.0 is not registered

Ryan 16

Hello Community,

I have been getting this error message every time I run my saved SSIS package. And even though I have looked up this error message across the web, the solutions have not seemed to work.

To provide the background information with the drivers and software installed:

Microsoft® Excel® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20538) 32-bit
Microsoft SQL Server 2022 (RTM-CU15-GDR) (KB5046862) - 16.0.4155.4 (X64) Oct 18 2024 16:16:11 Copyright (C) 2022 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor)
Microsoft AccessDatabaseEngineX64 16.0.4519.1000 Gen P0
Other ODBC Drivers:

The SSIS Package is saved in SSISDB;

The connection manager string: Provider=Microsoft.ACE.OLEDB.12.0;Data Source=[UNC Path of the file address];Extended Properties="EXCEL 8.0;HDR=YES";

When I use the Import and Export wizard, and select the Data Source as Excel, there is no issue detecting the Excel document and the sheets/tables; And there is no issue loading the data to the database table with the wizard (the 'run immediately' option);

The error appears when I try to rerun the saved SSIS package at any location. I have tried Visual Studio, SSISDB, SQL Server Agent, all show the error message. Both 32-bit and 64-bit Microsoft AccessDatabaseEngine had been installed and tried, same outcome;

Full validation error messages:

User's image

Would this still be a driver issue, or SSIS package setup issue?

Many thanks!

Yitzhak Khabinsky 27,091 Reputation points

2025-06-30T11:44:10.78+00:00

@Ryan,

What's the latest?
Did you have a chance to try the proposed solution(s)?
Ryan 16 Reputation points

2025-06-30T16:20:51.29+00:00

Hi Yitzhak,

Yes, I have made a request to the IT service department to have the ACE driver installed on the SQL Server rather than on my local laptop machine. And I believe that is the source of the issue, as I double checked the driver list with another DBA colleague, his powershell line shows like this:

I do not have the SSISOLEDB - I believe this is the missing driver that is responsible for all these error messages that I have been getting right

5 answers

Your answer

Yitzhak Khabinsky 27,091 Reputation points

2025-06-30T11:44:10.78+00:00

@Ryan,

What's the latest?
Did you have a chance to try the proposed solution(s)?
Ryan 16 Reputation points

2025-06-30T16:20:51.29+00:00

Hi Yitzhak,

Yes, I have made a request to the IT service department to have the ACE driver installed on the SQL Server rather than on my local laptop machine. And I believe that is the source of the issue, as I double checked the driver list with another DBA colleague, his powershell line shows like this:

I do not have the SSISOLEDB - I believe this is the missing driver that is responsible for all these error messages that I have been getting right

Answer 1

Michael Taylor 61,111

SSIS packages can run in either x86 or x64 mode. It is a property of the package. It depends on how you are actually running the package as to where it is set.

When developing the package you would set it in the properties for the project. It is Run64BitRuntime.
If you are using SQL Agent then it is a property of the job when you set it up. Edit the job to specify which bitness you want.
If you're using a batch file and running dtexec directly then you need to pass a flag to have it run in x86 mode since SQL is x64 by default.
If you want to view the existing package details then use the SSIS node in SSMS. Alternatively you can use the catalog views to look using T-SQL.

My gut instinct is that you want your package to be x64 and therefore should ensure your Access runtime is x64. Then make sure your SSIS package is configured to run as x64 and not x86.

Ryan 16 Reputation points

2025-06-24T20:57:46.8733333+00:00

Hi Michael,

I suppose this is referring to the 32 vs 64-bit runtime;

In the SQL Server Agent (and also in the SSISDB) configuration, I do not have the 32-bit runtime checked. I did play with this checkbox before and the error message just get reverted: "If the 32-bit driver is not installed, run the package in 64-bit mode." OR "If the 64-bit driver is not installed, run the package in 32-bit mode."

Would it be a 64 bit by default? Also I would like to make sure, would I be needing a Microsoft AccessDatabaseEngine 64 bit version or a 32 bit version, I am seeing mixed results from the web.

Thanks
Michael Taylor 61,111 Reputation points

2025-06-24T21:09:25.0166667+00:00

Yes, SQL is x64 by default so SSIS package run as x64 as well. You only want to use x86 if you have legacy dependencies. You need to also install the Access Database Engine OLEDB provider for x64.

To ensure everything is installed correctly you can then search for Data Sources in Windows search. You'll see an option for ODBC Data Sources (64-bit). You can confirm the driver is installed there.

Note a catch-22 with Office. You cannot install x86 versions of Office with x64 versions of the ACE driver. They are not compatible. So if you installed Office x86 already then you won't be able to install the x64 ACE driver. Installing Office on a SQL Server probably doesn't make sense but I don't know about your environment. I believe MS365 subscriptions now install Office x64 by default so if you installed it that way you should be good. If you're not sure then open Office and go to Accounts and then About .... In the version string it'll say what bitness it is.

I've not tried it myself but supposedly you can get x64 ACE working even with x86 Office installed by running the ACE installer with the passive option.
Ryan 16 Reputation points

2025-06-25T00:05:52.8466667+00:00

Firstly, I do have Microsoft AccessDatabaseEngineX64 16.0 installed, but it does not show in the ODBC Data Sources - Drivers section (in the initial post screenshot), does it indicate that it is not installed correctly? Unfortunately, I am working with a managed device here so I cannot control the installation and download for these drivers. I can only check with what I can see.

Second of all, my Excel reads: Microsoft® Excel® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20538) 32-bit. Does it mean that I need a Access Database Engine OLEDB provider for x86 (the 32 bit version)? If so, I tried with that option in the previous screenshot, "32-bit runtime", did not perform as intended;

In the last point, are you referring to running the .exe /quiet in Command Prompt? Unfortunately with managed devices I cannot achieve that.

Thanks!
Michael Taylor 61,111 Reputation points

2025-06-25T01:53:13.99+00:00

Change your package to run with the 32-bit runtime. If it works then you have the 32-bit version of the driver installed.

Another thing to verify is running the following T-SQL command EXEC master.sys.sp_MSset_oledb_prop. It will show you what 64-bit drivers SQL has access to. If Access isn't listed then SQL doesn't have access to it.

To clarify, SSMS is a 32-bit program. So it works with 32-bit drivers for things like Import/Export. SQL is a 64-bit program so it works with 64-bit drivers. It can be confusing when things "work" in SSMS but not SQL. SSIS packages run in the context of the DTS host and therefore can run either way. If it works in SSMS then you most likely have the 32-bit drivers installed.
Ryan 16 Reputation points

2025-06-25T05:03:19.7266667+00:00

If I check the "32-bit runtime" box, I get this error message:

The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode.

With this query: EXEC master.sys.sp_MSset_oledb_prop I get the result below:

The only time it works, is by directly using the Import/Export Wizard. If I rerun the saved DTSX package in anyway, this error message kicks in. It is as if the ACE has not taken effect.
Michael Taylor 61,111 Reputation points

2025-06-25T13:46:06.7+00:00

ACE isn't installed on the SQL Server. To clarify here, you need to install the x64 Access driver on the SQL Server machine, not your local client machine. Please install the driver on the SQL Server machine and then rerun the script to confirm SQL sees it.

Once it is installed ensure your SSIS package is not using 32-bit runtime and run it again.
Ryan 16 Reputation points

2025-07-09T22:19:24.6066667+00:00

Hi Michael,

Microsoft.ACE.OLEDB.16.0 has been installed onto the server. However new error message appearing as: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "(null)" Hresult: 0x80004005 Description: "(null)".

Official documentation suggests: Change the value of the RetainSameConnection property from False to True. However, failed to solve the issue.

Full message:

Answer 2

Yitzhak Khabinsky 27,091

Hi @Ryan,

Your connection string shows that SSIS package is using Microsoft.ACE.OLEDB.12.0 provider.

All you need to do is to install and start using Microsoft ACE OLEDB Provider 16.0. The connection string in SSIS should be using it as follows:

Provider=Microsoft.ACE.OLEDB.16.0;...

After that issue the following statement is SSMS to verify what 64-bit OLEDB Providers are installed:

EXEC master.sys.sp_enum_oledb_providers;

Or in PowerShell:

 (New-Object system.data.oledb.oledbenumerator).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTION

P.S. Microsoft ACE OLEDB Provider has nothing to do with ODBC drivers.

Ryan 16 Reputation points

2025-06-25T15:55:08.08+00:00

Hello Yitzhak,

EXEC master.sys.sp_MSset_oledb_prop I get the result below:

If I change the connection string to start using Microsoft ACE OLEDB Provider 16.0, the error message shows as below, which also is not registered
Yitzhak Khabinsky 27,091 Reputation points

2025-06-25T17:00:56.4933333+00:00

The query in SSMS shows you that the 64-bit ACE provider is not installed. You need to do that.
Here is the link: https://www.microsoft.com/en-us/download/details.aspx?id=54920&msockid=1d54ab6b747067823c53bd7d75486660

You should see it when it is installed. Here is how it looks like on my machine.
Ryan 16 Reputation points

2025-06-25T17:11:53.75+00:00

Thank you, that's great guidance there; Because I am on a centralized managed device, just to give clear instructions to the IT Service department, is it installation to a specific SQL server, and not on the local laptop? Because I can see on the Control Panel --> Programs, I do see the name of this ACE installed; Where should the installation be so that it properly appears on this PowerShell screen?
Yitzhak Khabinsky 27,091 Reputation points

2025-06-25T18:36:29.4133333+00:00
Microsoft ACE OLEDB Provider 16.0 should be installed in two places:

Developer workstation where SSIS projects are developed in Visual Studio.

SSIS run-time server where MS SQL Server is installed with SSIS as its component.
Ryan 16 Reputation points

2025-06-25T21:22:01.53+00:00

Sounds good, and just to confirm, it is the X64 version of the ACE driver that I need right, not the 32-bit one
Yitzhak Khabinsky 27,091 Reputation points

2025-06-26T11:47:33.24+00:00
On the developer workstation it depends on what Visual Studio is used. For VS2022, it is a 64-bit application, it should be 64-bit ACE Provider. For any other VS version like VS 2019 and earlier it should be 32-bit ACE Provider.

On the SSIS run-time server it always should be 64-bit ACE Provider.

Answer 3

RUDRAKSHA SHARMA 0

Hi Ryan,

This error typically points to an architecture mismatch between your SSIS runtime and the installed OLE DB provider.

Here’s the breakdown and fix:

Why This Happens:

Your system is running 64-bit SQL Server, but Office is 32-bit.

The ACE.OLEDB.12.0 or 16.0 provider (used to connect to Excel) is not registered for 64-bit or is conflicting with the 32-bit Office version.

The Import/Export wizard works because it runs in 32-bit mode, but SSIS in SSISDB and SQL Server Agent run by default in 64-bit mode.

Fix 1 (Recommended): Run the package in 32-bit mode

If you're executing the package via SQL Server Agent:

Edit the Job Step.

Go to the Execution Options tab.

Enable Use 32-bit runtime.

If you're running via Visual Studio:

Right-click the project > Properties.

Go to Debugging.

Set Run64BitRuntime = False.

This forces the package to run using the 32-bit ACE driver, which is compatible with your Office setup.

Fix 2 (If you prefer 64-bit execution)

Uninstall 32-bit Office (including all 32-bit Access Database Engine components).

Install the 64-bit version of Microsoft Access Database Engine 2016 Redistributable: Download link

Update your connection string to:

   
   Provider=Microsoft.ACE.OLEDB.16.0;Data Source=...;Extended Properties="Excel 12.0;HDR=YES";

Note: Only proceed with this if you're switching your entire Office suite to 64-bit, as mixing 32-bit Office with a 64-bit driver can lead to additional issues.

Alternative Option

If Excel isn't a strict requirement, consider converting the Excel file to CSV and using the Flat File Source in SSIS. It simplifies the connection and avoids OLE DB dependency issues altogether.

Let me know if you need help with the conversion or adjusting your SSIS package accordingly.

Ryan 16 Reputation points

2025-06-30T22:42:24.5733333+00:00

Hello,

Regarding the fix1.

I did play with that checkbox before, and the error message just gets reverted: "If the 32-bit driver is not installed, run the package in 64-bit mode." OR "If the 64-bit driver is not installed, run the package in 32-bit mode."

I do believe it is the location of where the driver is installed might be the issue;

Thanks
Yitzhak Khabinsky 27,091 Reputation points

2025-07-01T12:39:12.62+00:00

@Ryan,

You can safely ignore this AI generated answer.

The solution for the issue you are experiencing is outlined in my answer. The 64-bit Microsoft ACE OLEDB Provider 16.0 needs to be installed on the SSIS run-time server.
Ryan 16 Reputation points

2025-07-09T19:34:32.2133333+00:00

Hello Yitzhak,

I believe the Provider has been installed onto the Server, by running the following command:

However, I am still getting error messages after running the package in both local and remote desktop SSMS. The package ran from Integration Services Catalogs:

Is this an access related issue to the file path? If so I tried running with proxy and still the same error messages;

Thanks
Yitzhak Khabinsky 27,091 Reputation points

2025-07-10T12:54:16.31+00:00
@Ryan,

The screen shot confirms that the correct 64-bit Microsoft ACE Provider is installed.

The latest error message tells us that it is impossible to reach Excel file. Two possible reasons for that:

A fully qualified path that is used by the SSIS package is incorrect.

It is permissions related issue.
A decision to execute SSIS package with the Proxy account is correct. Just make sure that the Proxy account has access to the file system.
Ryan 16 Reputation points

2025-07-10T21:09:02.09+00:00

This would be interesting. Official documentation suggests: Change the value of the RetainSameConnection property from False to True. However, failed to solve the issue.

For a change, I moved the Excel file to my local desktop and have added proxy as my own user account, yet still fails;

Just to make sure, when I am selecting the destination from the wizard, when building the dtsx file, I should use 'Microsoft OLE DB Provider for SQL Server' as the right one to connect?
Yitzhak Khabinsky 27,091 Reputation points

2025-07-11T12:04:51.7433333+00:00

The 'Microsoft OLE DB Provider for SQL Server' is deprecated. It is better to start using 'Microsoft OLE DB Driver for SQL Server' while reading/writing data in MS SQL Server database. It is available since 2018.
Ryan 16 Reputation points

2025-07-11T20:21:19.5533333+00:00

Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted. End Error Error: 2025-07-11 13:16:19.58 Code: 0xC0011002

Description: Failed to open package file "....\Profile\Desktop\LTC July.dtsx" due to error 0x80070035 "The network path was not found.". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage or the specified XML file has an incorrect format. End Error

This is the error message that appears if I ran it in SQL Server Agent. It says failed to open the package that is stored on the desktop. What would be potential wrong with the path, it is the UNC path of the desktop;
Yitzhak Khabinsky 27,091 Reputation points

2025-07-11T21:33:25.09+00:00

SSIS package on the file system? 😢
What about SSIS Catalog?
Ryan 16 Reputation points

2025-07-11T22:32:29.45+00:00

Do you mean the SQL Server instead of the File System option?
Ryan 16 Reputation points

2025-07-16T20:08:00.7966667+00:00

Hi @Yitzhak Khabinsky ,When I am tried to save the SSIS package created from the I/E wizard, the completion page shows the source provider as ACE.OLEDB.12.0; To confirm, would I need ACE.OLEDB.16.0 or 12.0, or ideally both?

Thanks!
Yitzhak Khabinsky 27,091 Reputation points

2025-07-17T19:16:44.4433333+00:00

It is better to use ACE.OLEDB.16.0

The ACE.OLEDB.12.0 was recently removed by Microsoft from being available on their Web sites.
Ryan 16 Reputation points

2025-07-18T17:01:43.1166667+00:00

Then it seems that creating the package initially from the I/E wizard may not be very ideal. Is it the preferred way to build packages using the wizard, or is it better to use Visual Studio to begin with?

Answer 4

john willaim 0

To fix the "OLE DB provider not registered" error in SSIS:

Install the Microsoft Access Database Engine (both 32-bit and 64-bit versions) from Microsoft Download Center.
Configure SSIS to match the bitness of your provider (32-bit or 64-bit).

Check provider registration using this SQL command:

   sql
   CopyEdit
   EXEC master.sys.sp_MSset_oledb_prop;

Ensure the correct connection string in your SSIS package for the provider.
Rebuild and redeploy your SSIS package.

Answer 5

Dinesh Yadlapalli 0 Microsoft External Staff Moderator

Hi @Ryan,

Thank you for reaching out to the Microsoft Q & A Forum.

This behavior aligns with the ACE provider not being available in the bitness that the package is executing under on the server, even though it’s available in the environment where the wizard ran. SSIS can execute in 32‑bit or 64‑bit mode depending on how and where you run it. When the mode doesn’t match the installed ACE provider or the provider isn’t installed for that mode, you get the error.

Please try below steps.

Install Access Database Engine 2016 x64 on the SQL Server where SSIS is executed.
In SSIS connection manager, use:

Provider=Microsoft.ACE.OLEDB.16.0;

Extended Properties="Excel 12.0 Xml;HDR=YES;IMEX=1";

or keep 12.0 moniker if you have that installed x64.

Ensure packages run 64‑bit in SSISDB/SQL Agent.

It is primarily a driver/bitness deployment issue on the server (ACE provider installed for the wrong architecture or not installed at all for the architecture you are using), combined with how SSIS is being invoked (32‑ vs 64‑bit). Align the provider installation with the runtime mode and update the connection’s extended properties to match .xlsx. Once those are consistent, the package should validate and execute.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

Ryan 16 Reputation points

2025-11-28T19:32:18.88+00:00

Hi Dinesh,

Is there a query or anything that I can use to check which Access Database Engine I currently have on the SQL Server?

This is all under a managed environment, so would be easier for me to communicate with the IT team if I can show them what is installed on the server currently.

I ran this query:

EXEC master.sys.sp_MSset_oledb_prop

The result shows as below:

Thanks
Dinesh Yadlapalli 0 Reputation points Microsoft External Staff Moderator

2025-12-12T08:16:07.9+00:00
Hi @Ryan,

Sorry for the inconvenience caused. Please refer below things.

"sp_MSset_oledb_prop" listing registered OLE DB providers on the SQL Server instance. The key detail is "Microsoft.ACE.OLEDB.16.0". This means the Access Database Engine (ACE) provider version 16.0 is installed and registered for the SQL Server process bitness. Since SQL Server 2022 runs as 64-bit, this indicates that the 64-bit ACE provider is present on the server.

Please try below steps.

Run below query.

EXEC sp_enum_oledb_providers;

Note: This is procedure to list all OLE DB providers registered with SQL Server. It will show the same list you have, including "Microsoft.ACE.OLEDB.16.0".

If Microsoft.ACE.OLEDB.16.0 appears, ACE 2016 or later is installed.

Because SQL Server is 64-bit, this registration means the 64-bit ACE provider is available for SSIS packages running in 64-bit mode.

Communicate to IT:

"The SQL Server instance has Microsoft.ACE.OLEDB.16.0 registered, which corresponds to the Access Database Engine 2016 or later. This is the 64-bit provider since SQL Server itself is 64-bit.”

If you need 32-bit execution , confirm whether the x86 ACE provider is installed by checking the Windows registry or running dtexec /32 from the command line.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

Share via

SSIS Package Execution Error - The requested OLE DB provider Microsoft.ACE.OLEDB.16.0 is not registered

5 answers

Your answer