Windows Integration Errors

How to Fix Microsoft.ACE.OLEDB Error -2147217865 with SharePoint Lists

Khadija KhanKhadija Khan Oct 21, 2026 868 views

Question details

Users need to resolve the Microsoft.ACE.OLEDB error -2147217865 encountered while attempting to read or query a SharePoint list from an external application.

How to Fix Microsoft.ACE.OLEDB Error -2147217865 with SharePoint Lists
Product
Microsoft Access Database Engine
Device & OS
Windows
Scenario
Connecting an application to a SharePoint list using the Microsoft.ACE.OLEDB data provider.
Observed behavior
The application intermittently or constantly returns error -2147217865, preventing data retrieval from the SharePoint list.
Before you start

Ensure you have administrator privileges on your local Windows machine to install or modify database engine components, and verify you have read permissions for the target SharePoint list.

Solution 1Recommended

Match Architecture and Reinstall Microsoft Access Database Engine

The most common cause of OLEDB provider errors is a mismatch between the bitness (32-bit vs 64-bit) of your calling application and the installed ACE.OLEDB engine.

If your application is compiled as a 32-bit process, it cannot utilize a 64-bit OLEDB provider, and vice versa. Installing the correct Access Database Engine Redistributable aligns the architectures and resolves registration errors.

1
Check application bitness

Determine whether the application or script you are using to query SharePoint is running as a 32-bit or 64-bit process.

2
Download the Access Database Engine

Navigate to the official Microsoft download page for the Microsoft Access Database Engine 2010 or 2016 Redistributable.

3
Install the matching version

Run the downloaded installer that strictly matches your application's architecture. Choose the x64 installer for 64-bit apps, or the x86 installer for 32-bit apps.

4
Restart the application

Fully close and restart your development environment, application, or service to ensure the newly registered OLEDB provider is loaded correctly.

Installation Success: Once the architectures match, the 'provider is not registered' or generic OLEDB initialization errors should immediately cease.
Free Microsoft Office alternative

Try WPS Office for a Seamless and Free Productivity Experience

If you are dealing with complex Microsoft database integrations and errors, you might be looking for a lighter, more reliable daily office suite. WPS Office provides a complete, free alternative to Microsoft Office with high compatibility and zero complex database engine dependencies for your standard document tasks.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the software: Run the lightweight installer and follow the on-screen prompts to complete the setup.
  3. 3. Open your files: Launch WPS Office and instantly open your existing Excel spreadsheets or CSV data exports.
Highly compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Lightweight installation with no complex OLEDB provider configurations required.Free to use with a familiar, user-friendly tabbed interface.Seamlessly open and manage data exports without relying on heavy database engines.
QA img-9

Frequently Asked Questions

Why does the ACE.OLEDB provider intermittently fail on SharePoint lists?

Intermittent failures often occur due to temporary network latency, SharePoint server throttling, or token expiration. Adding retry logic to your application's connection string usually resolves these sporadic drops.

Can I install both 32-bit and 64-bit Access Database Engines on the same machine?

By default, Microsoft does not support installing both architectures side-by-side. You must align your application's architecture with the single installed version of the ACE.OLEDB provider, though some advanced workarounds exist using silent installation flags.

Is the Access Database Engine 2010 Redistributable still supported?

Access Database Engine 2010 is older and may lack support for newer security protocols. Whenever possible, it is recommended to upgrade to the Access Database Engine 2016 Redistributable for better compatibility and security updates.

How can I check if the ACE.OLEDB provider is properly registered on my PC?

You can check your Windows Registry under 'HKEY_LOCAL_MACHINE\SOFTWARE\Classes' to see if 'Microsoft.ACE.OLEDB.12.0' (or 16.0) exists, or use a simple PowerShell script to attempt to instantiate the COM object.