The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
EDIT: This appears to only be for a few Workspaces/Apps. Publishing the same report elsewhere works fine. Still unable to resolve it for the few workspaces that are affected.
We noticed yesterday that any of our reports that had direct queries are erroring out in the service. They have always worked in the past. They work fine in Desktop but once published we get the following error when trying to view the report:
Cannot load model
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
We are also seeing this error when we go into the settings for the data model: This feature is not supported. Please make sure you have installed the latest version of the gateway.
We are running version 3000,202.16 from December 2023.
Any ideas what could be going on?
Solved! Go to Solution.
Hi @TCavins
Reports using DirectQuery run fine in Power BI desktop, but errors appear after publishing. Here are some possible causes and troubleshooting steps:
The error message mentioning the need for the latest version of the gateway suggests there might be an issue with the gateway configuration. Ensure that your gateway is up-to-date and correctly configured. Power BI requires a properly configured gateway for DirectQuery connections, especially when dealing with on-premises data sources.
DirectQuery has certain limitations and may behave differently in the service compared to Power BI Desktop. Verify that the usage of DirectQuery in your reports aligns with these limitations. Additionally, there could be capacity throttling or query limits that affect the performance of DirectQuery in the Power BI service.
Check the data source settings in Power BI Service. Ensure that the credentials are correctly set and that the data source is accessible from the service. Sometimes, changing the privacy level settings for the data sources or adjusting the current file to ignore privacy levels can resolve issues.
Verify if the user experiencing the issue has the necessary permissions. In some cases, users might require build permissions on the underlying DirectQuery dataset, not just viewer access.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @TCavins
Reports using DirectQuery run fine in Power BI desktop, but errors appear after publishing. Here are some possible causes and troubleshooting steps:
The error message mentioning the need for the latest version of the gateway suggests there might be an issue with the gateway configuration. Ensure that your gateway is up-to-date and correctly configured. Power BI requires a properly configured gateway for DirectQuery connections, especially when dealing with on-premises data sources.
DirectQuery has certain limitations and may behave differently in the service compared to Power BI Desktop. Verify that the usage of DirectQuery in your reports aligns with these limitations. Additionally, there could be capacity throttling or query limits that affect the performance of DirectQuery in the Power BI service.
Check the data source settings in Power BI Service. Ensure that the credentials are correctly set and that the data source is accessible from the service. Sometimes, changing the privacy level settings for the data sources or adjusting the current file to ignore privacy levels can resolve issues.
Verify if the user experiencing the issue has the necessary permissions. In some cases, users might require build permissions on the underlying DirectQuery dataset, not just viewer access.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.