Forum Discussion
Power BI Snowflake Error
Hi all, When I'm trying to refresh power BI dashboards from both desktop and service, I'm receiving this error:
I haven't got any error till afternoon, but suddenly getting these errors.
Can someone please help me with this?
Thanks,
Sainath
Hi SainathKrothap,
I would look a little deeper than the underlying Snowflake table here.
The important part of the error is:
Get https://...blob.core.windows.net/results/...followed by:
dial tcp: lookup ...blob.core.windows.net: no such hostThat points to the Snowflake client failing to resolve/reach the Azure Blob endpoint being used to retrieve the query results, rather than a normal table/query error.
Snowflake's client connectivity troubleshooting guidance specifically notes that larger query result sets are retrieved through STAGE endpoints and can fail if the client doesn't have full network access to those endpoints. The same guidance also calls out DNS configuration problems for hostname-resolution failures.
One quick isolation test would be to run a very small Snowflake query from Power BI, for example a limited number of rows. If small queries work but the normal refresh fails when larger results are returned, that would strengthen the case that the failure is happening during result retrieval rather than during SQL execution itself.
Since you are also seeing it suddenly in both Desktop and Service, I would ask your Snowflake/network team to check DNS/proxy/firewall resolution for the Snowflake-generated *.blob.core.windows.net result endpoint and review the Snowflake allowlist/network diagnostics.
Microsoft's Snowflake connector documentation also points to Snowflake's connectivity troubleshooting guidance for integration issues.
I wouldn't start by changing the Power BI model or Snowflake table yet. The no such host message is the part I would investigate first.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
4 Replies
- GilbertQSuper User
I would highly recommend that you chat to your Snowflake DBA or Snowflake Administrator as it looks to be an issue with the underlying Snowflake table. Once that is fixed you could then try and refresh to see if it is working.
- ShivekMaharajPower Participant
Hi SainathKrothap,
I would look a little deeper than the underlying Snowflake table here.
The important part of the error is:
Get https://...blob.core.windows.net/results/...followed by:
dial tcp: lookup ...blob.core.windows.net: no such hostThat points to the Snowflake client failing to resolve/reach the Azure Blob endpoint being used to retrieve the query results, rather than a normal table/query error.
Snowflake's client connectivity troubleshooting guidance specifically notes that larger query result sets are retrieved through STAGE endpoints and can fail if the client doesn't have full network access to those endpoints. The same guidance also calls out DNS configuration problems for hostname-resolution failures.
One quick isolation test would be to run a very small Snowflake query from Power BI, for example a limited number of rows. If small queries work but the normal refresh fails when larger results are returned, that would strengthen the case that the failure is happening during result retrieval rather than during SQL execution itself.
Since you are also seeing it suddenly in both Desktop and Service, I would ask your Snowflake/network team to check DNS/proxy/firewall resolution for the Snowflake-generated *.blob.core.windows.net result endpoint and review the Snowflake allowlist/network diagnostics.
Microsoft's Snowflake connector documentation also points to Snowflake's connectivity troubleshooting guidance for integration issues.
I wouldn't start by changing the Power BI model or Snowflake table yet. The no such host message is the part I would investigate first.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
- SainathKrothapFrequent Visitor
Hi ShivekMaharaj , thank you for your response.
My IT team resolved this error, they told me it was a internal server DNS problem.
Thank you,
Sainath
- v-kathullacCommunity Support
Hi SainathKrothap ,
Thanks For the update that your issue got resolved by your IT team Let us know if you need any further assistance?
Thanks,
Chaithanya.