Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi all,
recently we started getting this error on all of .mdb files located on out on-premise server, to with we setup connection through gateway.
This happens when trying to refresh semantic model on app.powerbi web. We are reallyl out of ideas - no thing really changed and this started only after around 20 december.
Any ideas? Surely its not an network error as files readily avaible and can be opened in access or powerbi desktop. Also credentials are correct (i tried creating new connnection with new credential but error is the same)
{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} Table: FACT_1200_linereport.
You didn't change the data format of a column in that table?
Nothing was changes as far as i know - similar errors happen on at least 3 access files. I even tried to convert from .mdb to newer format but that did not change anything. Tried also putting this files on different server - also no change.
In general you should try to avoid using Access (and especially .mdb format) for your data storage. Do you have an option to migrate your data to SQL Server?
Hi @Anonymous ,
Please make sure your gateway version is up to date that the gateway can reach the data source server. If the server is unreachable, consider restarting it.
You may also verify the report has a gateway selected. If there is no gateway selected, the data source might have changed or might be missing.
If none of this works. you may consider the issue is not caused by firewall restrictions,try launching the on-premises data gateway application and ensure the HTTPS mode is off.
Some users have reported that rebooting the server where the gateway is installed resolved the issue.
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Best regards.
Community Support Team_Caitlyn
Disabling https is an option we are taking in consideration - but it will need to be done through change request so its not quick in our case.
I tried to use ODBC connector, and while it works if i only import few tables from database; when i import all ~50 i get this error when trying to refresh on app.powerbi:
Too slow connection in this case? Especially this part is new error:
Too many client tasks.\r\nERROR
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.