Forum Discussion
Power BI Service - Failure to Refresh
Hi G_Terry ,
Thank you for the update. Since the gateway has been patched and your admin is reviewing the Access driver registration, you are proceeding correctly. At this stage, it is advisable for your admin to examine the gateway logs on the server, as these logs can help determine whether the issue is related to the Access driver, file path permissions, or the gateway service itself.
If the driver is functioning properly and the logs do not clarify the cause, submitting a support ticket to Microsoft would be the most effective next step, as their team can perform a detailed log analysis and provide further guidance.
Thank you,Tejaswi.
Hi G_Terry
DataFormat.error usually indicates the data couldn't be interpreted correctly due to corrupted data, unexpected nulls, or incompatible types.
I think the error is a red herring though.
It's not the query, as it's refreshing successfully in Power BI desktop.
I doubt it's the data in the Access DB for the same reason.
I'd suggest you make sure the on-premises data gateway is up to date.
Ensure the machine running the gateway has the latest Microsoft Access Database Engine installed.
After that, I agree with FBergamaschi, might be one for Microsoft.
I hope this helps, please mark as solved if it does!
kudos always welcome .
Connect with me on LinkedIn
Subscribe to my YouTube channel for Fabric/Power Platform related content!
Thanks for the response. Our company has a gateway server, on which the gateway is created for the Access database in question. The gateway connection was created relatively recently, and I had requested of the enterprise configuration team that the 64 bit Access driver be installed on the gateway server, which was done. The connection is created via a UNC path to the share where the Access table file is located. Once the correct connection was made, the refresh worked initially, as I recall both instant refresh, and also scheduled. Then it just quit working. The old "unspecified error," which is usually useless in my experience, comes up as you can see. At this point, guess I will put in a ticket.
Hi G_Terry ,
Thanks for sharing the additional details. Since the refresh was working earlier with the gateway and the 64-bit Access driver, but later stopped with the “unspecified error,” it means the original setup was fine and something in the environment has changed. In such cases, the most common causes are either the Access driver getting unregistered after a Windows update, or the gateway service account losing permissions to the shared folder where the Access file sits.
I would suggest confirming that the driver is still properly installed on the gateway server, checking if the service account has uninterrupted access to the UNC path, and verifying that the file itself has not been moved, renamed or locked. The gateway logs (found under C:\Program Files\On-premises data gateway\GatewayLogs) will normally point to the exact issue. If none of these checks resolve it, raising a support ticket would be the right step as the logs will help the support team narrow down whether it is a driver, permissions, or gateway service problem.
Thank you,Tejaswi.
