ERROR: The requested OLE DB Provider Microsoft.ACE.OLEDB.16.0 is not registered

Question

Post reply

ERROR: The requested OLE DB Provider Microsoft.ACE.OLEDB.16.0 is not registered

Express12

SSCoach

Points: 18526
More actions
May 2, 2025 at 10:59 am

#4586985

Using VS2019 editor -- developing SSIS Pkg to ingest an Excel XLSX v16.03 file and LOAD into a SQL 2019 Std table -- receiving ERROR in VS2019 editor for Data Flow SOURCE Excel:
The requested OLE DB Provider Microsoft.ACE.OLEDB.16.0 is not registered AND/OR --- Microsoft.ACE.OLEDB.12.0 not found
BT

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Express12 SSCoach Points: 18526 More actions · Answer 1

Thought I'd post the resolution I applied for this issue:

Issue: Error using an SSIS Pkg to ingest an Excel XLSX v16.x file into a SQL 2019 table

If you are receiving this error:

-- ERROR: The requested OLE DB Provider Microsoft.ACE.OLEDB.16.0 is not registered

or

-- ERROR: Provider=Microsoft.ACE.OLEDB.12.0 not found

Try installing the 32-bit "Microsoft Access Database Engine 2016\accessdatabaseengine.exe" in QUIET mode...

NOTE: if you already have the 64-bit "Microsoft Access Database Engine 2016" installed and you try to install the 32-bit version w/out specifying /QUIET, you will receive a PopUp stating U must "UNINSTALL your OFFICE Products".. U probably DON'T want to do that! Just install the 32-bit version in /QUIET mode, side-by side the 64-bit version!

To install the 32-bit "Microsoft Access Database Engine 2016" --- side-by-side an existing 64-bit "Microsoft Access Database Engine 2016" installation --- use QUIET mode:

1. From CMD prompt, change into the DIR housing the 32-bit version of "Microsoft Access Database Engine 2016" driver & run with /QUIET:

2. CD\your_dir\your Microsoft Access Database Engine 2016 install sw\

3. then run: accessdatabaseengine.exe /quiet (NOTE: though the CMD prompt window flashes and returns quickly, this QUIET install may take a few min's; allow the install to run in the background for a min or 2.. then retry your process)

4. Run your SSIS Pkg (SQL Job) in 32-bit mode

Doing this resolved issues using SSIS to ingest an Excel XLSX v16.x file into a SQL table; in the SSIS Pkg I was able to specify Source: EXCEL 16.0 (In my SSIS Pkg Connection to the XLSX file, I specified "EXCEL 2016" instead of 2007-2010, etc)

This reply was modified 4 months, 1 week ago by Express12.
This reply was modified 4 months, 1 week ago by Express12.
This reply was modified 4 months, 1 week ago by Express12.

BT

Phil Parkin SSC Guru Points: 247180 More actions · Answer 2

Not directly related, but if you migrate to VS2022, everything is 64-bit, putting an end to this kind of faffing about!

pietlinden SSC Guru Points: 63595 More actions · Answer 3

Phil,

does that fix the problem if you're using the import wizard from within SQL Server?

Thanks!

Pieter

frederico_fonseca SSCoach Points: 16251 More actions · Answer 4

import wizard is 32 bit if you execute immediately - if you schedule to run on server it will execute the package on the server in 64bit mode by default.

VS has NOTHING to do with the import wizard.

Jeff Moden SSC Guru Points: 1004641 More actions · Answer 5

I just use the 64 bit version and install it in the QUIET mode.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)