Snowflake Keypair Refresh

[LSWilliams94]

Hi all,

I'm currently facing an issue where I've published a report that connects to our Snowflake database using keypair authentication, when I try to refresh it fails immediately saying keypair is not supported. I've checked the data source and it passes successfully. I can also run a refresh in desktop successfully.

It's also weird as we have another model that's pulling in data from snowflake using keypair authentication and that refreshes absolutely fine.

[v-veshwara-msft]

Hi @LSWilliams94 ,

Just wanted to check if the responses provided were helpful. If further assistance is needed, please reach out.
Thank you.

[v-veshwara-msft]

Hi @LSWilliams94 ,

Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.

Thank you.

[v-veshwara-msft · Accepted solution]

Hi @LSWilliams94 ,

Thanks for reaching out to Microsoft Fabric Community.

Thank you for the inputs @GilbertQ 

As suggested, comparing the configuration between the working and failing models is a good starting point, especially since another dataset in your environment refreshes successfully using keypair authentication.

In addition to reviewing how the connection is defined in Desktop, could you please confirm:

->Whether both datasets are mapped to the same gateway cluster
 ->Whether the gateway is running on the latest version
->The exact refresh error message shown in the Service refresh history

If both models appear identically configured, you may also consider clearing and re entering the Snowflake credentials in the Service and verifying the dataset to gateway mapping, as credential metadata can sometimes cause immediate refresh failures even when the test connection succeeds.

Hope this helps. Please reach out for further assistance.
Thank you.

[GilbertQ]

Hi @LSWilliams94 

What I would recommend doing is if you have another model that is working successfully I would compare the way you are bringing the data in and using the QP authentication as potentially there is some difference which is causing the other model to fail for some reason. Typically I don't use the keypair, I use the basic authentication for Snowflake.

[LSWilliams94]

It was quite interesting actually, I did look at the other model and what the difference was. I had an excel file as a data source and for some reason, that was causing the issue, I just had to import it to sharepoint and it fixed itself. Was weird that it was trying to say it was a snowflake issue though when really it was a local file/gateway issue