Shceduled/ On Demand Refresh Failures with Snowflake data sources.

[amol_mahajan]

Hi All,

I've been facing intermittent refresh failures when using snowflake cloud data source. It gives error as below:
The credentials provided for the Snowflake source are invalid. (Source at sophos.XX-west-X.snowflakecomputing.com;XXXXXXXX_WAREHOUSE.). The exception was raised by the IDbCommand interface. Table: VW_VALUE_DATE.

here the table names will be different for different reports but all using same login and same warehouse.

Sometimes it gives this error and sometimes it automatically runs fine without any changes. I'm not sure what's casuign this.

We're using Global Username passwords for snowflake access which can be used by multiple reports/users at once.

if anyone faced similar issue please let me know how to address this error & random failures.

[v-pgoloju]

Hi @amol_mahajan,

Just following up to see if the response provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.

Best regards,

Prasanna Kumar

[amol_mahajan · Accepted solution]

Hi All,

I got my resolution from this post and it is working.
https://community.fabric.microsoft.com/t5/Service/Snowflake-data-source-refresh-errors-following-Jul...

It was new snowflake connector implementation issue on PBI service side.

[v-pgoloju]

Hi @amol_mahajan,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @rohit1991 and @BhavinVyas3003  for prompt and helpful responses.

Just following up to see if the roubleshoot points provided by community members were helpful in addressing the issue.

If one of the responses helped resolve your query, please consider marking it as the Accepted Solution. Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[rohit1991]

Hi @amol_mahajan ,

Random Snowflake refresh errors in Power BI are almost always caused by using shared or global credentials. Here’s what works in real life:

• Set up a dedicated Snowflake user for each Power BI dataset instead of sharing one login. Session conflicts are super common if you share.
  
  

• If you can, switch from username/password to OAuth or key pair authentication it’s much more reliable, especially with multiple refreshes running.
  
  

• Double-check and re-enter your credentials in Power BI Service settings, just to be sure nothing is cached or expired.
  
  

• If you’re using an on-prem gateway, network hiccups or VPN drops can cause these errors worth checking your gateway logs.
  
  

• As a last resort, try staggering refresh schedules if you’re stuck sharing an account, but honestly, dedicated users and stable auth methods are the real fix.
  
  

[BhavinVyas3003]

This issue is likely due to using shared/global credentials with Snowflake, which can cause session conflicts or token expiry during concurrent refreshes.

• Use dedicated service accounts instead of shared ones.
• Prefer OAuth or Key Pair Authentication over username/password.
• Check for gateway or network issues if on-prem is involved.
• Revalidate credentials in Power BI Service settings.

It’s an intermittent auth/session issue, switching to stable auth methods usually resolves it.