Forum Discussion
PowerBI no longer able to reference Access database
Hi all, since the 14th of this month our PowerPI report has been unable to connect to our Access database ( this sits on a local server) , the error states: The database you are trying to open requires a newer version of Microsoft Access - I have seen lots of info regarding Large Number format, but this is not in use and the version outweighs 16.7 ( we are on 16.19XXX ). I hope someone can point us in the right direction, the full error PoweBI is producing below:
Kind regards
Last refresh failed: 19/05/2026, 07:05:01
An error occurred while processing the semantic model.Hide details
| Data source error: | {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The database you are trying to open requires a newer version of Microsoft Access."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"Power Bi DataHD.accdb"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} |
| Cluster URI: | WABI-US-NORTH-CENTRAL-C-PRIMARY-redirect.analysis.windows.net |
| Activity ID: | a9d33a72-209b-4cd1-9fe7-04150865074b |
| Request ID: | 184629fd-eb3d-4533-bf10-6abef5c26b7e |
| Time: | 2026-05-19 06:05:01Z |
So you should try this now :
Step 1: Find the actual gateway machine
Go to Power BI Service:
Settings → Manage connections and gateways
Find the gateway associated with this dataset
Note the machine name listed under that gateway
That is the machine where you need to install the 64-bit Access Database Engine.
Step 2: Check which gateway the dataset is using
Go to your Workspace → Datasets → (the failing dataset) → Settings
Expand Gateway and cloud connections
It will show you exactly which gateway cluster is mapped
Step 3: Go to THAT machine and:
Install the 64-bit Access Database Engine 2016 (/quiet if Office C2R blocks it)
Confirm the "On-premises data gateway service" IS present and running
Restart that service
If no gateway shows as mapped, it's possible the gateway was uninstalled or the service crashed around May 14th, which would perfectly explain why refreshes suddenly stopped on that date. In that case the gateway would need to be reinstalled on the correct server from: https://aka.ms/opdg
5 Replies
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to oussamahaimoud sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Hi Baseley09,
Hope you are doing well!
Try this solution step by step :
Step 1: Verify the ACE OLEDB provider on the Gateway Server
On the server running the On-Premises Data Gateway, check what Access Database Engine is installed:
Open Control Panel → Programs and Features
Look for "Microsoft Access Database Engine 2010" or "Microsoft Access Database Engine 2016 Redistributable"
It must be the 64-bit version, the gateway is 64-bit only
Step 2: Install/Reinstall the correct 64-bit ACE provider
Even if Office 16.19 is installed on that server, a Click-to-Run (C2R) Office installation virtualizes its ACE driver and does NOT expose it to the gateway. This is the most common hidden cause.
Download and install the standalone 64-bit redistributable:
Access Database Engine 2016 (64-bit): https://www.microsoft.com/en-us/download/details.aspx?id=54920
Run the installer. If it blocks due to a C2R Office conflict, run it with the /quiet switch from the command line:
accessdatabaseengine_X64.exe /quiet
Step 3: Restart the Gateway Service
After installation, on the gateway server:
Open Services (services.msc)
Restart "On-premises data gateway service"
Step 4: Test the refresh
Go to the Power BI Service and trigger a manual refresh on the semantic model.
Hope this fixs your issue. Don't forget to accept as solution and thumbs up in order to help others
Thank you very much for the information oussamahaimoud , we have followed the steps, installed the Acces database engine but we notice the "On-premises data gateway service" service is not present on this server.
So you should try this now :
Step 1: Find the actual gateway machine
Go to Power BI Service:
Settings → Manage connections and gateways
Find the gateway associated with this dataset
Note the machine name listed under that gateway
That is the machine where you need to install the 64-bit Access Database Engine.
Step 2: Check which gateway the dataset is using
Go to your Workspace → Datasets → (the failing dataset) → Settings
Expand Gateway and cloud connections
It will show you exactly which gateway cluster is mapped
Step 3: Go to THAT machine and:
Install the 64-bit Access Database Engine 2016 (/quiet if Office C2R blocks it)
Confirm the "On-premises data gateway service" IS present and running
Restart that service
If no gateway shows as mapped, it's possible the gateway was uninstalled or the service crashed around May 14th, which would perfectly explain why refreshes suddenly stopped on that date. In that case the gateway would need to be reinstalled on the correct server from: https://aka.ms/opdg
Hi Baseley09,
Just checking, the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.
Thank you.
