Office Installation Errors

Fix the 64-Bit ACE OLE DB Installation Error in Office 365

Khadija KhanKhadija Khan Nov 22, 2026 868 views

Question details

Install the appropriate ACE OLE DB provider to import Excel data into a Visual Studio 2015 tabular project.

Product
Microsoft Access Database Engine, Office 365 ProPlus, and Visual Studio 2015
Device & OS
not provided
Scenario
The user is importing an Excel file into a Visual Studio tabular project and needs the ACE OLE DB provider.
Observed behavior
The 64-bit provider installer detects 32-bit Office components and blocks installation, although Office 365 ProPlus appears to be 64-bit.
Before you start

Identify the Excel import tool and its process architecture, then check the installed Office and Access Database Engine versions. The provider architecture must be compatible with the process loading it as well as the installed Office components.

Solution 1Recommended

Check Office architecture and remove conflicting components

Use this approach when the 64-bit ACE installer reports that 32-bit Office is installed.

1
Check Office bitness

Open Word and select File > Account > About Word. Check whether the installed Office version is labeled 32-bit or 64-bit.

2
Inspect installed components

Open Control Panel > Programs > Programs and Features. Look for other Office products and Microsoft Access Database Engine entries that may have a conflicting architecture.

3
Remove confirmed conflicts

In Programs and Features, select any confirmed conflicting Office or Access Database Engine installation and choose Uninstall. If needed, reinstall the Office products in the architecture you intend to use.

4
Install the matching provider

Download the appropriate Access Database Engine installer from Microsoft and run it. Choose a provider architecture compatible with both the Office installation and the process performing the import.

5
Retry the Excel import

Return to the Visual Studio 2015 tabular project and run the Excel import again. If the installer still reports a conflict, note the exact error and installed component versions before asking for help in Microsoft developer forums.

Check Office architecture and remove conflicting components
Check the importing process: A 64-bit Office installation alone does not guarantee that the import tool uses a 64-bit process. A 32-bit process needs a 32-bit provider, so verify the import tool's architecture before changing Office components.
Free Microsoft Office alternative

Work with Excel files in WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move existing documents and spreadsheets. WPS does not install or repair the Microsoft ACE OLE DB provider required by the Visual Studio import.

Open and edit Excel spreadsheets in WPS SpreadsheetCompatible with Microsoft Excel XLS and XLSX formatsFamiliar interface for a straightforward transition from OfficeFree, lightweight tools for everyday document work
microsoft office alternative - wps office

Frequently Asked Questions

How can I tell whether Office is 32-bit or 64-bit?

In Word, select File > Account > About Word and look for the architecture in the version information.

Why does the installer detect 32-bit Office when Word is 64-bit?

Another Office product or Access Database Engine component may be installed with a conflicting architecture. Check Control Panel > Programs > Programs and Features for additional entries.

Should I install the 32-bit or 64-bit ACE provider for Visual Studio?

Check the architecture of the process performing the Excel import. It must be able to load the provider, and the provider installation must also be compatible with the Office components on the machine.

What should I do if the conflict remains after checking installed programs?

Record the exact installer error, Office bitness, provider version, and Visual Studio import details, then seek help in Microsoft developer forums.