responseContent={\"error\":{\"code\":\"BadGatewayConnection\",\"message\":\"The network connectivity issue encountered for 'Microsoft.Storage'; cannot fulfill the request.\"}})

Question

We have connectivity to snowflake and we are using azure storage queue to send notification to snowflake once blob is created or uploaded in storage container. Snowflake then loads the blob file to snowflake database.

But we are facing intermittent issue often where we get network error and some does not load to snowflake.

This happened on 17th, 18th & 19th of May 2024. Please let us know do we need to raise a support ticket?

errorCode=BadGateway, QueueErrorCode=, , httpStatusCode=InternalServerError, errorType=UnexpectedError, errorMessage=An unexpected error has occurred. Please report the x-ms-request-id header value to our forums for assistance or raise a support ticket., errorMessage=One or more errors occurred. (Failed to retrieve credentials for armId=/subscriptions/, responseContent={"error":{"code":"BadGatewayConnection","message":"The network connectivity issue encountered for 'Microsoft.Storage'; cannot fulfill the request."}}), innerErrorMessage=Failed to retrieve credentials for armId=/subscriptions/, responseContent={"error":{"code":"BadGatewayConnection","message":"The network connectivity issue encountered for 'Microsoft.Storage'; cannot fulfill the request."}}"}

Answer 1

Hi Anbhule,Rupesh (HHSC Contractor)- Thanks for reaching out.

Based on the high-level error details, you can do some of the few checks as below:

Check for how were the latency values looking at the time when these errors occurred. If you observe a high E2E latency spike compared to Server latency, it points to some congestion from the client or something happening on the networking side. You can check for enabling the logging and check for the response for the particular calls and their latency values.

Check for server timeout errors around that time. You can check for Monitoring -> Metrics -> Select Transactions as metric type -> Apply splitting based on Response Type. There might be some transient issue on the server side as well.

Below are the reference links for the same:

https://learn.microsoft.com/en-us/azure/storage/blobs/monitor-blob-storage?tabs=azure-portal

https://techcommunity.microsoft.com/t5/azure-paas-blog/how-to-isolate-latency-issue-for-azure-storage-account/ba-p/1430656

Based on the above it might give you some hints whether this is more on the client/network side or on the storage side. For further review/analysis, you can reach out to the support team with the instance details further.

Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.

---

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

Hello Anbhule,Rupesh (HHSC Contractor),

Greetings! Welcome to Microsoft Q&A Platform.

I understand that you’re encountering some connectivity issues between Snowflake and Azure Storage. Based on the error message, it appears that there’s a network connectivity problem related to ‘Microsoft. Storage’.

Adding to above information. Please consider the following to troubleshoot the issue further,Check the Storage account configuration and confirm that the storage account name and connection string used in your Snowflake configuration are accurate also validate the container and path settings in your stage definition.

Use network diagnostic tools to check connectivity between your Snowflake instance and Azure Storage and Ping the Azure Storage endpoints from your Snowflake environment to verify if there are any latency or packet loss issues.

Check if there are any firewall rules or network security groups blocking traffic between the two services.

Implement a retry mechanism in your application or Snowflake task. If a load fails due to a network error, retry the operation after a short delay. Snowflake provides built-in retry options for loading data from external stages.

If the issue persists, consider reaching out to Azure support and provide them with the error details and any relevant logs for further investigation.

Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.

---

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.