Data Source Credentials Issue with Snowflake DirectQuery in Power BI Service

[Analyst04]

Issue Summary:

We are experiencing a data source credentials issue after publishing a Power BI report to the Power BI Service. The report uses DirectQuery to connect to Snowflake.

---

Behavior Observed:

• In Power BI Desktop, all visuals load correctly.
• After publishing to the Power BI Service, some visuals populate as expected, while others fail with the following error:

“An exception occurred due to an on-premise service issue. See details.”
“Error fetching data for this visual. Please try again later or contact support.”

---

Additional Details:

• Connection Type: DirectQuery
• Data Source: Snowflake
• Gateway Configuration: using an On-premises Data Gateway 

---

Troubleshooting Steps Taken:

• Re-entered credentials in dataset settings
• Refreshed the dataset manually
• Verified gateway connectivity 

---

Attachments:

• Screenshot of the error message (attached)
  

---

Request:

Any guidance is appreciated:

• Whether this is a known issue with Snowflake DirectQuery in Power BI Service
• Any recommended steps to resolve the credentials issue
• Whether gateway configuration or authentication method could be contributing to the problem

[v-ssriganesh]

Hi @Analyst04,
We regret the inconvenience caused. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

[v-ssriganesh]

Hello @Analyst04,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. 

Thank you.

[Analyst04]

Hi @v-ssriganesh ,
I connected with Microsoft they suggested it might be the gateway update issue. Currently we are looking into it.

[GilbertQ]

Hi @Analyst04 

Another tip would be is to open up the PBIX file on your gateway and see if you can refresh it from your gateway. The reason for this is to determine if your gateway can access snowflakes successfully.

[Analyst04]

Hi @GilbertQ ,

The refresh works fine both on Power BI Desktop and in the Power BI Service. However, a few visuals are not rendering correctly in the service.

Could this be related to model size, visual-level filters, or service limitations? Appreciate any pointers to help troubleshoot this further.
Regards
Analyst04

[v-ssriganesh]

Hello @Analyst04,
Thank you for reaching out to the Microsoft Fabric Community Forum.

This isn’t a widely documented issue specific to Snowflake DirectQuery, but gateway-related errors are common with on-premises setups. Please consider below points:

• Ensure the gateway is updated and restarted.
• Verify credentials in Power BI Service dataset settings match Power BI Desktop, including Snowflake role permissions.
• Confirm authentication (e.g: OAuth2 or basic) and network connectivity from the gateway to Snowflake.
• Check gateway logs for detailed errors and test connectivity via diagnostic tools.

If Snowflake is publicly accessible, confirm if the gateway is required. Misconfiguration here might cause the issue. Refer to the official documentation for gateway setup and troubleshooting:

• Configure an on-premises data gateway

• https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot

If you have any further questions, please don't hesitate to contact us through the community. We are happy to assist you.

Best Regards,
Ganesh singamshetty.

[Analyst04]

Hi @GaneshSingamshetty,

Thanks for the suggestions. I have checked all the points you mentioned gateway updates, credentials, authentication, and connectivity. Everything seems to be in place, but the issue still persists.

Is there anything else I could try or look into?

Best,
@Analyst04