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

Error when adding connection and when trying to access connection #1421

Closed
debchat opened this issue May 29, 2019 · 3 comments
Closed

Error when adding connection and when trying to access connection #1421

debchat opened this issue May 29, 2019 · 3 comments
Assignees
Milestone

Comments

@debchat
Copy link

debchat commented May 29, 2019

Storage Explorer Version: 1.8.1
Platform/OS: Windows 10
Architecture: x64
Regression From:

Bug description
Trying to use Storage Explorer to connect to Azure storage.

Steps to Reproduce

  1. Add account
  2. Use SAS URI
  3. Next page - fill URI
  4. Fills other fields as expected.
  5. Tweak - change name slightly. Then I can click "connect"
  6. "Adding new connection"
  7. Stays in that phase for very long time

Azure1

Even if I press "Refresh all", then open "Storage accounts"
Azure2

Expected Experience
I expect a new storage account will be visible and I can see content of that storage account.

Actual Experience
Cannot go past "Adding new connection" stage

@MRayermannMSFT MRayermannMSFT changed the title Storage Explorer 1.8.1 Error when adding connection and when trying to access connection Jun 19, 2019
@MRayermannMSFT MRayermannMSFT added this to the 1.10.0 milestone Jun 19, 2019
@MRayermannMSFT
Copy link
Member

Related to #985

@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Aug 19, 2019
@MRayermannMSFT MRayermannMSFT modified the milestones: 1.10.0, 1.11.0 Sep 3, 2019
@debchat
Copy link
Author

debchat commented Sep 3, 2019

Please see new ticket #1771. I encountered the same problem today. Wish we find out the root cause.
Searching in the web, I find the users are calling it the "infamous" issue. See here.

https://www.urtech.ca/2019/02/solved-azure-storage-explorer-cannot-read-property-connectionstring-of-undefined-other-troubleshooting/

@MRayermannMSFT
Copy link
Member

Closing. In 1.10, if something gets corrupted we show a broken node now. Please open a new issue if you continue to encounter problems.

Storage Explorer automation moved this from Committed to Done Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants