Fix Microsoft.ACE.OLEDB.12.0 Provider Not Registered Error in SSMS
Question details
The user needs to resolve an OLEDB provider error that prevents importing Excel data into a SQL Server database.
- Product
- SQL Server Management Studio 2019
- Device & OS
- not provided
- Scenario
- Importing an Excel spreadsheet into a database using the SQL Server Import and Export Wizard in SSMS.
- Observed behavior
- An error message appears stating that the 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
Verify whether your SSMS installation and your installed Microsoft Office applications are 32-bit or 64-bit, as an architecture mismatch is the primary cause of this error.
Install the Microsoft Access Database Engine Redistributable
Installing the appropriate version of the Access Database Engine provides the missing OLEDB drivers required for SSMS to read Excel files.
SSMS requires the Microsoft.ACE.OLEDB.12.0 or 16.0 provider to communicate with Excel files. If Microsoft Office is not installed on the server, or if there is a bitness mismatch (e.g., 32-bit SSMS with 64-bit Office), the provider will fail to load.
Navigate to the official Microsoft Download Center and search for 'Microsoft Access Database Engine 2010 Redistributable' or the 2016 version. Click 'Download'.
Choose the 32-bit (AccessDatabaseEngine.exe) or 64-bit (AccessDatabaseEngine_X64.exe) version. Since SSMS is generally a 32-bit application, the 32-bit driver is often required when using the SSMS Import/Export Wizard directly.
Run the downloaded executable file and follow the installation wizard. Once the installation is complete, close and restart SQL Server Management Studio.
Save the Excel File as a CSV (Workaround)
Bypass the OLEDB provider requirement entirely by converting your Excel data into a flat CSV file before importing it into SQL Server.
Consult the Microsoft Learn SQL Server Community
If installing the redistributable does not resolve the issue, seek specific database troubleshooting assistance from the official Microsoft community.
Bypass Complex Office Driver Issues with WPS Office
The Microsoft.ACE.OLEDB.12.0 error is a common headache caused by Microsoft Office and SQL Server architecture clashes. Switch to WPS Office, a highly compatible, lightweight, and free alternative. You can easily manage your spreadsheet data and save files as flat CSVs to seamlessly import into SQL Server Management Studio without relying on problematic OLEDB drivers.
Frequently Asked Questions
Why does SSMS say the Microsoft.ACE.OLEDB.12.0 provider is not registered?
This error occurs when SQL Server Management Studio cannot locate the Access Database Engine OLEDB provider. This usually happens because the engine is not installed on the machine, or there is an architecture mismatch (such as trying to use a 64-bit driver with a 32-bit SSMS application).
Can I install both 32-bit and 64-bit versions of the ACE OLEDB provider?
By default, Microsoft prevents installing both 32-bit and 64-bit versions side-by-side. However, you can bypass this limitation by downloading the required installer, opening the Command Prompt, and running the installer file path with the '/quiet' switch.
Is there a way to import Excel to SSMS without installing OLEDB drivers?
Yes. The most reliable workaround is to open your Excel file in a spreadsheet program, save the file as a CSV (Comma Separated Values), and then use the 'Flat File Source' option in the SQL Server Import and Export Wizard.
Does SSMS 2019 run in 32-bit or 64-bit?
SQL Server Management Studio (SSMS) 2019 is a 32-bit application. Therefore, when you launch the Import/Export Wizard directly from within SSMS, it runs as a 32-bit process and requires the 32-bit Microsoft.ACE.OLEDB.12.0 provider to read Excel files.
