Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to Blob storage container #28525

Closed
rossdo88 opened this issue Apr 2, 2019 — with docs.microsoft.com · 15 comments
Closed

Unable to connect to Blob storage container #28525

rossdo88 opened this issue Apr 2, 2019 — with docs.microsoft.com · 15 comments

Comments

Copy link

rossdo88 commented Apr 2, 2019

When i tried to connect Azure blob via Azure storage explore, error:
Error - Unable to retrieve child resources in Azure Storage Explorer

when open by browser:

InvalidUri The requested URI does not represent any resource on the server. RequestId:88282800-14f3-4963-a5da-07a260a6f58b Time:2019-04-01T14:13:09.8399259Z http://rachel:11002/ URL path http://rachel:11002/ doesn't represent any valid resource on the server Microsoft.Cis.Services.Nephos.Common.Protocols.Rest.InvalidUrlProtocolException: URL path http://rachel:11002/ doesn't represent any valid resource on the server at Microsoft.Cis.Services.Nephos.Storage.Service.Protocols.Rest.HttpRestProcessor.ExtractOperationContext(NephosUriComponents uriComponents) in D:_work\1\s\xfe\storage\service\Protocols\REST\src\HttpRestProcessor.cs:line 334 at Microsoft.Cis.Services.Nephos.Common.Protocols.Rest.BasicHttpProcessorWithAuthAndAccountContainer1.ProcessImpl(AsyncIteratorContext1 async)+MoveNext() in D:_work\1\s\xfe\common\Protocols\REST\src\BasicHttpProcessorWithAuthAndAccountContainerBase.cs:line 2374


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@AshokPeddakotla-MSFT
Copy link
Contributor

@rossdo88 Thanks for the feedback! We are currently investigating and will update you shortly.

@AshokPeddakotla-MSFT
Copy link
Contributor

@rossdo88 Please follow this article to resolve the issue. Let me know if you need further help.

Copy link
Author

rossdo88 commented Apr 2, 2019

it does not help, delete data in folder means delete storage you just added

@AshokPeddakotla-MSFT
Copy link
Contributor

@rossdo88 I am assigning this issue to the @SumanthMarigowda-MSFT to provide further insights on this issue.

@qibozhu
Copy link

qibozhu commented Apr 3, 2019

@rossdo88 Hi, which platform did you deploy blob storage container? Windows or Linux? Which Azure Storage Explorer version did you use?

For Linux, you need to use specific Azure Storage Explorer version 1.5.0. For Windows, the latest version should work.

Please look at this document for more information.
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-store-data-blob#azure-storage-explorer

Copy link
Author

rossdo88 commented Apr 4, 2019

It was installed in Windows edge. The Explorer is lastest version. This issue still keeps going. I have test in few VM, local PC. happend the same.

@SumanthMarigowda-MSFT-zz
Copy link
Contributor

@rossdo88
Issue may occur due to: Network issue/ Proxy/subscription/updates
There a few reasons you may be seeing this error,
Firstly I would suggest to try the troubleshooting steps mentioned in this article
2. Roll back to the older version 1.4.2(Try testing in older version) Mainly check the network connectivity
Refer to the suggestion mentioned in this GitHub link

For Mac / Linux, you need to also remove Microsoft.Developer.IdentityService entry from your OS' keystore. Restart App and r-authenticate. Solves issues.

For Windows: delete the %appdata%\StorageExplorer folder, then restart the app. It will prompt you to enter the credentials

You may also refer to the suggestion mentioned in this link :
Kindly let us know if the above helps or you need further assistance on this issue.

@Alberto-Vega
Copy link
Contributor

@rossdo88 Were you able to resolve this issue?

@rossdo88
Copy link
Author

rossdo88 commented Apr 8, 2019

no i cannot be able to resolve this issue. i have gone through above suggest but not work.

@SumanthMarigowda-MSFT-zz
Copy link
Contributor

SumanthMarigowda-MSFT-zz commented Apr 9, 2019

@rossdo88 For further troubleshooting on this query I would request you to create a MSDN forum thread, Please mentions this GitHub link in the community thread

We will now proceed to close this thread. If there are further questions regarding this matter we will continue in the MSDN community

Copy link

Hi
I'm getting the same issue
What we have to put in device hostname in the following conection string

DefaultEndpointsProtocol=http;BlobEndpoint=http://:11002/;AccountName=;AccountKey=

@rossdo88
Copy link
Author

rossdo88 commented Apr 9, 2019

Hi
I'm getting the same issue
What we have to put in device hostname in the following conection string

DefaultEndpointsProtocol=http;BlobEndpoint=http://:11002/;AccountName=;AccountKey=

@PranjaliSoni Have you been able to resolve this issue?

Copy link

No, I'm confused that what to be put as "host device name" in this connection string to be used in Azure Storage Explorer.

DefaultEndpointsProtocol=http;BlobEndpoint=http://:11002/;AccountName=;AccountKey=

@SumanthMarigowda-MSFT-zz
Copy link
Contributor

@rossdo88 we noticed that you didn't open a new issue on MSDN yet and in order to resolve your issue faster our suggestion is that you please file a support request @ https://aka.ms/azsupt and reference this issue in the description. If you do not have access to a support plan, please reach out @ AZCommunity@microsoft.com with a link to this Doc/Issue as well as your subscription ID and we can help get the support ticket opened for this issue.Please mention "ATTN subm" in the subject field. Thank you for your cooperation on this matter and look forward to your reply.

@PranjaliSoni  please use as "host device name" the hostname of the IoTEdge device. If you are having the exact same issue please follow the same steps as suggested above. 

Copy link

@PranjaliSoni the device host name is the ip address of the VM assuming you have a VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants