locked
Azure Storage Explorer: server encountered an internal error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am getting the 'server encountered an internal error" error when I click to expand the Emulator-default port=> tables node in Azure Storage Explorer(version 1.6.2). However the azure table storage emulator has been initialized and is running. What am I missing? 

    Update: wrt to the GitHub post=>"Self-Signed Certificate in Certificate Chain", I have already configured the same and I still get the 'server encountered an internal error" error. I am also using the default ports used by the Storage Emulator. 


    Thanks, Ajit Goel


    • Edited by ajitgoel Wednesday, January 16, 2019 7:14 PM
    Wednesday, January 16, 2019 4:32 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    I see that you have also posted the query on GitHub, Copied the information here for benefitting the community.

    a. removing LocalDB database,
    b. deleting the localdb created mdf, ldf files,
    c. installing "SQL server Express" and manually creating the database that the Azure Storage explorer needed, and then configuring Azure Storage explorer to work with "SQL server Express"
    Wednesday, January 23, 2019 8:07 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Please  delete data from "%appData/StorageExplorer" folder or entire folder from your machine. After deleting, when you launch storage explorer you will be ask to reenter your credentials. That should fix this issue.

    Hope this helps!

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

    Please don't forget to “mark the replies as answers” if they helped, also set "like" it’s a boost for us to keep blogging J

    Click here to learn more. Visit the dedicated Community forum to share, explore and talk to experts about Microsoft Kaizala.

    Wednesday, January 16, 2019 4:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can try the suggestions mentioned above@Thuyavan ganesan.

    Adding additional information:
    If you are connected to Azure through a proxy, verify that your proxy settings are correct. If you were granted access to a resource from the owner of the subscription or account, verify that you have read or list permissions for that resource.

    While connecting to Azure Storage just check the box as "http" to connect the Azure Storage. This will also help in connecting azure storage explorer.

    Wednesday, January 16, 2019 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    None of the solutions mentioned above work. BTW, I am trying to connect to the local Azure storage account on my desktop. 

    Thanks, Ajit Goel

    Wednesday, January 16, 2019 1:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am connecting to my local azure account on my PC. Would I be asked to reenter my credentials in this case also?

    Thanks, Ajit Goel

    Wednesday, January 16, 2019 1:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes if you have cleared StorageExplorer folder , you would required to re enter your credentials 
    Wednesday, January 16, 2019 3:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    How are you trying to connect (a connection string?)  Is the storage explorer able to communicate with the emulator at all?  and can you confirm that the emulator is running correctly (for example, by using something else to try and connect?)

    Could you try to implement the steps described in this GitHub post. Although those steps are for a “self-signed certificate in certificate chain” error, the underlying causes of the errors are usually the same. Let us know how it goes.

    Try changing the ports used by the Storage Emulator to the default 10000-10003. This would prevent from using other programs that utilize this port range at the same time check and let me know the status.

    Wednesday, January 16, 2019 5:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I dont understand. I have never been asked to reenter my credentials.I am connecting to my localdb database through the azure storage emulator and azure storage explorer. 

    Thanks, Ajit Goel

    Wednesday, January 16, 2019 7:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Sumanth Marigowda.

    I am trying to connect to the local localdb database through the azure storage explorer. I am assuming that the azure storage emulator is able to communicate to the localdb correctly but it throws an error when it tries to get the details of each individual component(blob containers, queues, tables). The azure storage explorer is running successfully(I have a screenshot in my question above). 

    wrt to the GitHub post=>"Self-Signed Certificate in Certificate Chain", I have already configured the same and I have the same issue. 

    I am using the default ports used by the Storage Emulator. 

    Thanks, Ajit Goel

    Wednesday, January 16, 2019 7:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am investigating on this issue.  In mean while can you try the  suggestions/workaround mentioned in GitHub thread.

    Thursday, January 17, 2019 10:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks @SumathMarigowda. i have deleted the %AppData%\StorageExplorer and I have the same issue. I had done the same before also. 

    I will later today walk through trying to debug the issue and see if i can find something else. 

    Thanks, Ajit Goel

    Thursday, January 17, 2019 2:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is there a error log location for the azure storage explorer? perhaps that will help me identify what the issue could be?

    Thanks, Ajit Goel

    Thursday, January 17, 2019 4:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hope you have enabled the log already.  if have it you can run the below cmd and get the logs 


    Get-AzureStorageBlob -Container '$logs' | where { $_.Name -match 'table/2014/05/21/05' -and $_.ICloudBlob.Metadata.LogType -match 'write' } | foreach { "{0} {1} {2} {3}" –f $_.Name, $_.ICloudBlob.Metadata.StartTime, $_.ICloudBlob.Metadata.EndTime, $_.ICloudBlob.Metadata.LogType }

    How to enable:

    https://docs.microsoft.com/en-us/rest/api/storageservices/enabling-storage-logging-and-accessing-log-data

    Hope this helps!

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

    Please don't forget to “mark the replies as answers” if they helped, also set "like" it’s a boost for us to keep blogging J

    Click here to learn more. Visit the dedicated Community forum to share, explore and talk to experts about Microsoft Kaizala.

     
    Thursday, January 17, 2019 7:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Thuyavan Ganesan,

    where do I need to run this command? I am having issues connecting to the localdb database from the azure storage explorer, on my local pc. 

    Thanks, Ajit Goel

    Thursday, January 17, 2019 7:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    https://docs.microsoft.com/en-us/rest/api/storageservices/enabling-storage-logging-and-accessing-log-data#HowtoenableStorageLoggingusingPowerShell<o:p></o:p>

    How to enable Storage Logging using the Azure portal

    In the Azure portal, use the Diagnostics blade to control Storage Logging, accessible from the MONITORING section of a storage account's Menu blade.

    You can specify the storage services that you want to log, and the retention period (in days) for the logged data.

    How to enable Storage Logging using PowerShell

    You can use PowerShell on your local machine to configure Storage Logging in your storage account by using the Azure PowerShell cmdlet Get-AzureStorageServiceLoggingProperty to retrieve the current settings, and the cmdlet Set-AzureStorageServiceLoggingProperty to change the current settings.

    The cmdlets that control Storage Logging use a LoggingOperations parameter that is a string containing a comma-separated list of request types to log. The three possible request types are read, write, and delete. To switch off logging, use the value none for the LoggingOperations parameter.

    The following command switches on logging for read, write, and delete requests in the Queue service in your default storage account with retention set to five days:

    <button class="action" data-bi-name="copy" style="font-style:inherit;font-variant:inherit;font-weight:inherit;font-size:inherit;font-family:inherit;margin:0px;box-sizing:inherit;cursor:pointer;padding:2px 10px;border-width:0px 0px 0px 1px;display:flex;-webkit-box-align:center;align-items:center;">Copy</button>
    Set-AzureStorageServiceLoggingProperty -ServiceType Queue   
-LoggingOperations read,write,delete -RetentionDays 5
    Thursday, January 17, 2019 9:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    And how will this help me? I am using localdb as the local azure storage instead of actual azure storage. I am getting an error connecting from localdb (as the local azure storage) to the azure storage explorer, on my local pc. 

    Thanks, Ajit Goel

    Thursday, January 17, 2019 9:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i have created a github ticket

    https://github.com/Microsoft/AzureStorageExplorer/issues/1078

    Thanks, Ajit Goel

    Friday, January 18, 2019 3:57 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I see that you have also posted the query on GitHub, Copied the information here for benefitting the community.

    a. removing LocalDB database,
    b. deleting the localdb created mdf, ldf files,
    c. installing "SQL server Express" and manually creating the database that the Azure Storage explorer needed, and then configuring Azure Storage explorer to work with "SQL server Express"
    Wednesday, January 23, 2019 8:07 AM