DM_GWPipeline_Gateway_MashupDataAccessError

[data_wizard_NOT]

Hello

I'm getting the following error with scheduled or on-command refreshes:

• 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 Adbc.DataSource function is not available in this environment"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: Query2.
• Cluster URIWABI-WEST-US-redirect.analysis.windows.net
• Activity ID10bf57e4-b183-41c1-a224-d5ae0a07b9c4
• Request IDb19da75a-bc75-fdf5-beda-0b41343c8cf1
• Time2025-04-03 21:39:35Z

The weird thing is, I have at least 5 other dashboards that consume the same data sources (via Snowflake) but none of them are failing. I did recently update this dashboard in Power BI Desktop but I didn't touch anything regarding the data source or permissions. Refreshing in Power BI Desktop works perfectly fine.

I searched across the forum for similar issues but unfortunately I didn't find any solution.

Appreciate any help I can get!

[v-dineshya · Accepted solution]

Hi @data_wizard_NOT ,

Thanks for reaching out to the Microsoft fabric community forum. 

Here are some steps to troubleshoot:

Check the Data Gateway: Ensure the data gateway is online and properly configured.
Go to Power BI Service > Settings > Gateways and verify the status of the gateway. Check if the gateway is shared correctly if it's a cluster.

Gateway Connection Configuration: Even though you didn’t change the data source, sometimes updates can alter connection settings. Re-check the Data Source Settings in the Power BI Service. Verify that the Snowflake connection in the Power BI service matches the credentials and connection settings from Desktop.

Snowflake Connection Issue:

The error mentions "Adbc.DataSource" not being available. This could be due to:

Driver Issues: Ensure the correct Snowflake ODBC driver is installed and updated on the gateway machine.

Version Mismatch: Compare the Snowflake driver versions between the desktop and the gateway.

Query-Specific Issue: Since only Query2 is failing, inspect this query in Power BI Desktop:

Look for any custom functions, complex joins, or transformations that might behave differently in the service. Try simplifying the query temporarily to see if the error persists.

Refresh Settings in Power BI Service:

Sometimes, scheduled refresh settings can behave differently from manual refreshes. Check the refresh schedule and error settings. Try triggering an on-demand refresh from the service and monitor if the error reappears.

Permissions:

Even if permissions haven't changed, double-check that the service principal or user credentials used by the gateway have the correct access to Snowflake.

Error Logging:

In the Power BI Service, go to Dataset Settings > Refresh History for detailed logs. You can also check the gateway logs on the server where the gateway is installed for more insights.

Please refer the below article.

Troubleshoot gateways - Power BI | Microsoft Learn

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards

[SaiTejaTalasila]

Hi @data_wizard_NOT ,

Their might be some issue in the data gateway. You can create connections under any other gateway and refresh your report.

Thanks,

Sai Teja 

[Anonymous]

Save the pbix file as a different name.

Deploy to workspace.

Connect to Data Source and verify authentication

Try a refresh on new deployment.

If you get the same error, you can delete this deployment.

Then, you need to look at the Data Source created for authentication and dig more into the Adbc.DataSource function that is returning this error.