Issue on configurating Hot folders in Microsoft Azure Explorer

Hi Team,

We are trying to configure Hotfolders in SAP hybris. We have installed Microsoft Azure Storage Explorer as one of the prerequisites. We are facing an issue as shown in attached screenshot saying Invalid storage account. Can you please have a look at the logs (log-hybris.txt) and helps us on this.

30062-log-hybris.txt

Sumarigo-MSFT 43,801 Reputation points Microsoft Employee

2020-11-03T09:53:38.273+00:00

<< Private message note - This is a private message which only you as Original Poster and Microsoft Moderators can view. Please respond directly to this comment to privately share the requested information. For your privacy, please do not share any Personal Identifiable Information (PII) as a public comment. All private messages will be periodically deleted from the site >>

@Enugula, Srikanth (Cognizant) Just checking in to see if the above answer helped. If this answers your query, please don’t forget to "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

1 answer

Sumarigo-MSFT 43,801 Reputation points Microsoft Employee

2020-10-05T08:00:39.54+00:00

@Enugula, Srikanth (Cognizant) Based on the error message, Delete data from "%appData/StorageExplorer" folder or entire folder from your machine. After deleting when you launch storage explorer you will be prompted to re-enter your credentials.

This guide summarizes solutions for this issue seen in Storage Explorer. "Unable to Retrieve Children"

This article provides complete resolution for Azure Storage Explorer Troubleshooting: "unable to retrieve child resources” error message

If the issue still persists, Un-install and re-install the latest Storage Explorer

You can also refer How to connect to Hot Folders to Azure Storage Explorer

Hope this helps! Kindly let us know if the above helps or you need further assistance on this issue.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Please don’t forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Enugula, Srikanth (Cognizant) 1 Reputation point

2020-10-05T10:29:17.187+00:00

Hi @Sumarigo-MSFT

Thanks for the your valuable response.

We have tried the suggestion option (Removing Storage Explorer folder). Issue is still persisted even after doing this, even it`s not prompted us to re enter any credentials again on re launching Azure Storage Explorer.

We can see another error in Hybris console as shown below. Attached complete error log with name log-hybris.txt below
30192-log-hybris.txt

Can you please provide your thoughts/inputs on this.

Caused by: com.microsoft.azure.storage.StorageException: Invalid storage account.
at com.microsoft.azure.storage.StorageException.translateException(StorageException.java:87) ~[azure-storage-8.1.0.jar:?]
at com.microsoft.azure.storage.core.StorageRequest.materializeException(StorageRequest.java:313) ~[azure-storage-8.1.0.jar:?]
at com.microsoft.azure.storage.core.ExecutionEngine.executeWithRetry(ExecutionEngine.java:185) ~[azure-storage-8.1.0.jar:?]

Sumarigo-MSFT 43,801 Reputation points Microsoft Employee

2020-10-22T09:45:25.177+00:00

@Enugula, Srikanth (Cognizant) Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
Not really sure what SAP hybris is. Could you give us some more context on what it is? Is this storage account in public azure, azure china, etc? Why are you attaching with key instead of signing in?

Ultimately, it looks like the error is coming from the server. So from the Storage Explorer side, all I can say is to make sure the account name, account key, and endpoint domains are all correct. If you are continues to receive this error, then you’ll need to talk to the server team. I don’t think we’ve ever seen this error message before
Sign in to comment