This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 51%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
I have created a Linked Service using the SnowflakeV2 connector. The connector is configured to use Key Pair authentication and using the AutoResolveIntegrationRuntime works perfectly.
When switching to a self-hosted integration runtime, I receive the error:
Can anyone offer any suggestions as to how I can get the connector working with a self-hosted IR?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 36%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBM%3C/text%3E%3C/svg%3E)
Hello Andy Reed,
Welcome to the Microsoft Q&A forum.
Can you please use the latest SHIR and try again. With the latest SHIR, it should resolve the issue.
Hi Bhargava-MSFT,
Data Factory is reporting that the integration runtime is already on the latest runtime.
Hello Andy Reed,
I'm sorry to hear that the issue persists with the latest SHIR version. PG confirmed that the issue was fixed in the July build. I recommend submitting a support case since you are still encountering the error. The support team can assist you further. If you don't have a support plan, please let me know, and I can enable a one-time free support request to address this case
Hi Bhargava-MSFT,
I have managed to work around this issue now. Many thanks for your help.
Hello Andy Reed
I am glad to hear you managed to resolve the issue! Could you share a bit more about the workaround you implemented? I would love to understand what worked for you.
Your solution will also help the community look for answers to similar questions.
Thank you.