search

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
377 stars 87 forks source link

Login with setting "Language" "Use system language" and a system with a German local not possible #7318

Closed Gineus closed 1 year ago

Gineus commented 1 year ago

Preflight Checklist

Storage Explorer Version

1.13.1 (93)

Regression From

No response

Architecture

i86

Storage Explorer Build Number

20230822.1

Platform

Windows

OS Version

Windows 10

Bug Description

If I use the System Setting and do the steps described under "Steps to reproduce" the following message appears in the Activities Tab:

{ "message": "\"Could not load file or assembly 'System.IO.FileSystem, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Das System kann die angegebene Datei nicht finden.\"" }

My current locale is de_DE.

If I switch the language in Storage Explorer to "English" the login works.

Steps to Reproduce

  1. Launch Storage Explorer
  2. Press on the Account Management tab on the left side
  3. Click on "Sign in with Azure"
  4. In the Wizard select "Azure" and press the "Next" button

Actual Experience

After pressing the "Next" button an error message appears in the "Activities" tab.

Expected Experience

Same behavior (successful login) independent of the selected language.

Additional Context

No response

MRayermannMSFT commented 1 year ago

@Gineus can you please gather authentication logs: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/storage-explorer-troubleshooting?tabs=Windows#authentication-logs

And then share them on this issue via drag-and-drop into the comment response text box? Thanks.

MRayermannMSFT commented 1 year ago

Closing due to lack of response.

If you're still encountering this issue, we recommend opening an Azure support ticket via the Azure portal. Alternatively you can open a new issue here. This issue will no longer be monitored.