Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello All,
I have a Power BI Report that conneccts to Snowflake through KeyPair.
It refreshes in my desktop without any errors. However on the server it runs through gateway, and failes to refresh with the error below.
One think I can confirm is, Desktop and Server runs on the same credentials and this Snowflake role has access to all the tables/views.
I have already looked into the Implementation2.0 and it did not resolve the issue.
Any help is appreciated.
Thanks!
Solved! Go to Solution.
Hello,
Sorry for the delayed response. I have tried these but nothing worked.
But while digging through, I understand the issue is with the Keypair Update on snowflake account.
For Power BI (Desktop, cloud, gateway) Snowflake Account has to be TYPE= PERSONAL.
Snowflake account TYPE = LEGACY_SERVICE /SERVICE is not supported for KeyPair Authentication.
My snowflake was set to LEGACY_SERVICE, whick is a potential reason for the failures.
Additional documentation: Partner support for Snowflake authentication methods | Snowflake Documentation
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.
Thank You.
Hello,
Sorry for the delayed response. I have tried these but nothing worked.
But while digging through, I understand the issue is with the Keypair Update on snowflake account.
For Power BI (Desktop, cloud, gateway) Snowflake Account has to be TYPE= PERSONAL.
Snowflake account TYPE = LEGACY_SERVICE /SERVICE is not supported for KeyPair Authentication.
My snowflake was set to LEGACY_SERVICE, whick is a potential reason for the failures.
Additional documentation: Partner support for Snowflake authentication methods | Snowflake Documentation
Thank you for sharing the details. If you have any more questions, please let us know and we’ll be happy to help.
Regards,
Microsoft Fabric Community Support Team.
Thank you for contacting the Microsoft Fabric community forum.
The issue is linked to the gateway execution environment, not Snowflake permissions.When a dataset refresh occurs in Power BI Service, the gateway’s mashup engine executes queries, which is different from the local Desktop engine. Due to differences in runtime, drivers, and execution context, refresh results can vary between Desktop and Service. More details are available here:https://learn.microsoft.com/power-bi/connect-data/refresh-troubleshooting-refresh-scenarios
While removing Implementation="2.0" may help in some Snowflake scenarios, it doesn't always impact how the gateway processes connections, so it did not resolve this issue. Please check the gateway setup to ensure it is correct. The on-premises data gateway should be up to date, and the Snowflake data source must be fully configured with all required settings like server, warehouse, and role. Mismatched or incomplete configurations can still cause refresh failures, even if Desktop works as expected:https://learn.microsoft.com/power-bi/connect-data/service-gateway-onprem
It’s also important to consider how the private key is accessed. The gateway operates under a Windows service account, so if the key is stored locally or in a restricted folder, it might not be accessible during refresh, even if it works in Power BI Desktop. Ensure the key is in PKCS#8 format, set up correctly in Power BI Service, and available to the gateway service account.
Finally, confirm that the Snowflake driver on the gateway machine is current and supported, as driver differences can affect refreshes.Power Query Snowflake connector - Power Query | Microsoft Learn
If you have any further questions, feel free to reach out and we'll be glad to assist.
Regards,
Microsoft Fabric Community Support Team.
Temporarily install Power BI Desktop on one of your gateway VMs (don't forget to remove it afterwards) . Then try to connect to your data source from that Power BI Desktop. See if you get an error message.
Thanks for the response. MY gateway is set up by the Admin team. However, most cases you can change the ADBC to ODBC by removing Implemantation 2.0 from you MQuery!
However that did not work for me. Trying the other ways
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |