Refresh Error - Direct Query to Lakehouse

[fabulous5]

I am trying to refresh a Production Dashboard copy from PBI desktop and it fails with following error. Nothing has changed much and I am an admin on the workspace, I was doing some migration from Dev to Prod recently and things works fine in Dev even when I download the Dev file to my local Desktop. This is a dashboard which connect directly to the Gold LH in direct query mode

Error
DirectQuery to AS - lh_gl_bcs An error occurred while loading the model. Verify that the connection information is correct and that you have permissions to access the data source.

[v-sdhruv]

Hi @fabulous5 ,

I just wanted to check in and ask if the issue you were facing has been resolved. If not, we’d be happy to assist further—please let us know how we can help.Also, if any of the responses has addressed your query, please accept it as a solution  so that other members can easily find it. 

Thank You

[v-sdhruv]

Hi @fabulous5 ,

I just wanted to check in and ask if the issue you were facing has been resolved. If not, we’d be happy to assist further—please let us know how we can help.

Looking forward to your update!

Thank You

[v-sdhruv]

Hi @fabulous5 ,

Just wanted to check if you had the opportunity to review the suggestions provided?
If any of the response/s has addressed your query, please accept it as a solution  so that other members can easily find it. 
Thank you @Akash_Varuna , @pankajnamekar25  and @Sandip_Palit for your prompt and detailed response to the query.

Regards,
Shruti

[Akash_Varuna]

Hi @fabulous5 Possibly because of misconfigured permissions or changes during the migration from Dev to Prod, this error occurs. Ensure that the Gold LH dataset is accessible and that all workspace roles are correctly assigned in Production. Double-check connection settings for accuracy, especially for DirectQuery mode. If the issue persists, republish the report after revalidating the data source.

[pankajnamekar25]

Hello @fabulous5 

Possible Causes

Connection string or Lakehouse name may differ between Dev and Prod.

Permissions for the Lakehouse or tables in the Prod workspace may not match Dev.

The migrated dashboard may still be referencing Dev Lakehouse metadata.

Schema or table structure may have changed during Dev→Prod promotion.

Workspace connection to Fabric Lakehouse may not be correctly mapped in the Prod environment.

 Solutions

Reconnect the dataset in Power BI Desktop to the Prod Lakehouse explicitly via Get Data > Lakehouse.

Check table-level permissions in the Fabric workspace — you may be admin but missing data access rights.

Go to Model > Manage Parameters and confirm the Lakehouse name/path matches Prod setup.

Refresh schema (right-click the table > Refresh Preview) to detect any metadata mismatch.

Open Transform Data > Advanced Editor and verify the workspace ID and Lakehouse path are correct.

Rebuild the connection in Desktop by removing and re-adding the Lakehouse if metadata is corrupted.

Thanks

 Pankaj Namekar | LinkedIn

If this solution helps, please accept it and give a kudos (Like), it would be greatly appreciated.

[Sandip_Palit · Accepted solution]

An error occurred while loading the model. Verify that the connection information is correct and that you have permissions to access the data source. Please follow these solution steps:

1. Validate Data Source Credentials
- Open the Power BI Desktop file (PBIX) causing the error.
- Go to File > Options and settings > Data source settings.
- Check the data source settings for lh_gl_bcs and ensure they match what is used in the Dev environment.
- Click "Edit Permissions" and confirm that your credentials are correct. If needed, clear the permissions and re-enter them.

2. Confirm Connection Information
- In Power BI Desktop, go to "Transform Data" > "Data Source Settings".
- Make sure the server name and database name are accurate and accessible from your current network.
- If the connection uses a gateway in production, ensure the gateway is correctly mapped and active.

3. Test Access to the Gold LH AS Model
- Open SQL Server Management Studio (SSMS) or another compatible tool.
- Try connecting to the Analysis Services database using the same credentials and server info as Power BI.
- Ensure that you can query the model and that no permission issues are preventing access.

4. Verify Workspace and Permissions
- Even if you are an admin on the workspace, ensure that you also have necessary permissions on the dataset and data source.
- Go to the Power BI Service, check the dataset settings under the production workspace, and confirm if your account has access.

5. Compare Dev vs Prod Settings
- Open the Dev version of the PBIX that works fine.
- Compare the following with the Prod version:
- Data source settings
- Connection strings
- Any parameters used in the data source definition

6. Clear Cache and Rebuild Connection
- In Power BI Desktop, go to File > Options and settings > Options > Global > Data Load.
- Clear the cache to remove any corrupted temporary files.
- Rebuild the connection to the data source by removing it and adding it again.

7. Re-check Gateway Mapping 
- If your dashboard uses a gateway in the production workspace, ensure that the gateway is online and the data source is correctly mapped.
- Go to Power BI Service > Manage Gateways and verify the production data source settings.

8. Update and Re-Publish
- After verifying and fixing all of the above, save the PBIX file.
- Re-publish it to the Production workspace and refresh the dataset.

If this solution resolves your issue, please like and accept the solution.