Azure 存储资源管理器故障排除指南Azure Storage Explorer troubleshooting guide

Azure 存储资源管理器是一个独立的应用,使用它可在 Windows、macOS 和 Linux 上轻松处理 Azure 存储数据。Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux. 应用可连接到托管在 Azure、National Clouds 和 Azure Stack 上的存储帐户。The app can connect to storage accounts hosted on Azure, national clouds, and Azure Stack.

本指南汇总了存储资源管理器中常见问题的解决方法。This guide summarizes solutions for issues that are commonly seen in Storage Explorer.

RBAC 权限问题RBAC permissions issues

使用基于角色的访问控制 (RBAC) 可以通过将权限集组合成角色,来对 Azure 资源进行精细的访问管理。 Role-based access control RBAC enables highly granular access management of Azure resources by combining sets of permissions into roles. 下面是在存储资源管理器中以最佳方式使用 RBAC 的一些策略。Here are some strategies to get RBAC working optimally in Storage Explorer.

如何在存储资源管理器中访问我的资源?How do I access my resources in Storage Explorer?

如果你在通过 RBAC 访问存储资源时遇到问题,原因可能是你尚未获得相应的角色。If you're having problems accessing storage resources through RBAC, you might not have been assigned the appropriate roles. 以下部分介绍了存储资源管理器目前要求提供哪些权限来访问存储资源。The following sections describe the permissions Storage Explorer currently requires for access to your storage resources. 如果你不确定自己是否拥有相应的角色或权限,请联系 Azure 帐户管理员。Contact your Azure account administrator if you're not sure you have the appropriate roles or permissions.

“读取:列出/获取存储帐户”权限问题"Read: List/Get Storage Account(s)" permissions issue

必须有权列出存储帐户。You must have permission to list storage accounts. 若要获取此权限,必须具有“读取者”角色。 To get this permission, you must be assigned the Reader role.

列出存储帐户密钥List storage account keys

存储资源管理器还可以使用帐户密钥对请求进行身份验证。Storage Explorer can also use account keys to authenticate requests. 可以通过权限更高的角色(例如“参与者”角色)来获取帐户密钥的访问权限。 You can get access to account keys through more powerful roles, such as the Contributor role.


访问密钥向其任何持有者授予不受限制的权限。Access keys grant unrestricted permissions to anyone who holds them. 因此,我们不建议将这些密钥分发给帐户用户。Therefore, we don't recommend that you hand out these keys to account users. 如果需要撤销访问密钥,可以通过 Azure 门户重新生成访问密钥。If you need to revoke access keys, you can regenerate them from the Azure portal.

数据角色Data roles

必须至少拥有一个可以授予对资源中数据的读取访问权限的角色。You must be assigned at least one role that grants access to read data from resources. 例如,如果需要列出或下载 Blob,则至少需要拥有“存储 Blob 数据读取者”角色。 For example, if you want to list or download blobs, you'll need at least the Storage Blob Data Reader role.

为何需要管理层角色才能在存储资源管理器中查看我的资源?Why do I need a management layer role to see my resources in Storage Explorer?

Azure 存储提供两个访问层:“管理”和“数据”。 Azure Storage has two layers of access: management and data. 订阅和存储帐户是通过管理层访问的。Subscriptions and storage accounts are accessed through the management layer. 容器、Blob 和其他数据资源是通过数据层访问的。Containers, blobs, and other data resources are accessed through the data layer. 例如,若要从 Azure 获取存储帐户的列表,应向管理终结点发送请求。For example, if you want to get a list of your storage accounts from Azure, you send a request to the management endpoint. 若要列出帐户中的 Blob 容器,应向相应的服务终结点发送请求。If you want a list of blob containers in an account, you send a request to the appropriate service endpoint.

RBAC 角色可以包含对管理或数据访问层的权限。RBAC roles can contain permissions for management or data layer access. 例如,“读取者”角色授予对管理层资源的只读访问权限。The Reader role, for example, grants read-only access to management layer resources.

严格地讲,“读取者”角色不提供数据层的权限,并非一定要有该角色才能访问数据层。Strictly speaking, the Reader role provides no data layer permissions and isn't necessary for accessing the data layer.

在存储资源管理器中,可以通过收集连接到 Azure 资源所需的信息,来轻松访问资源。Storage Explorer makes it easy to access your resources by gathering the necessary information to connect to your Azure resources. 例如,若要显示 Blob 容器,存储资源管理器会向 Blob 服务终结点发送“列出容器”请求。For example, to display your blob containers, Storage Explorer sends a "list containers" request to the blob service endpoint. 若要获取该终结点,存储资源管理器会搜索你有权访问的订阅和存储帐户列表。To get that endpoint, Storage Explorer searches the list of subscriptions and storage accounts you have access to. 若要查找订阅和存储帐户,存储资源管理器还需要有权访问管理层。To find your subscriptions and storage accounts, Storage Explorer also needs access to the management layer.

如果你没有一个可以授予任何管理层权限的角色,则存储资源管理器无法获取连接到数据层所需的信息。If you don't have a role that grants any management layer permissions, Storage Explorer can't get the information it needs to connect to the data layer.

如果我无法从管理员获取管理层权限,该怎么办?What if I can't get the management layer permissions I need from my administrator?

目前,对于此问题,我们尚未制定 RBAC 相关的解决方法。We don't currently have an RBAC-related solution for this issue. 一种解决方法是请求一个 SAS URI 并将其附加到资源As a workaround, you can request a SAS URI to attach to your resource.

有几个内置 RBAC 角色可以提供使用存储资源管理器所需的权限。There are several built-in RBAC roles which can provide the permissions needed to use Storage Explorer. 其中一些角色是:Some of those roles are:

错误:证书链中的自签名证书(和类似错误)Error: Self-signed certificate in certificate chain (and similar errors)

如果存在以下情况之一,则往往会发生证书错误:Certificate errors typically occur in one of the following situations:

  • 应用通过透明代理进行连接,这意味着一台服务器(例如公司的服务器)正在截取 HTTPS 流量,对其进行解密,然后使用自签名证书对其进行加密 。The app is connected through a transparent proxy, which means a server (such as your company server) is intercepting HTTPS traffic, decrypting it, and then encrypting it by using a self-signed certificate.
  • 正在运行的应用程序正在向收到的 HTTPS 消息注入自签名 SSL 证书。You're running an application that's injecting a self-signed SSL certificate into the HTTPS messages that you receive. 注入证书的应用程序示例包括防病毒软件和网络流量检查软件。Examples of applications that inject certificates include antivirus and network traffic inspection software.

当存储资源管理器看到自签名或不受信任的证书时,无法再判断收到的 HTTPS 消息是否被更改。When Storage Explorer sees a self-signed or untrusted certificate, it no longer knows whether the received HTTPS message has been altered. 如果拥有自签名证书的副本,可通过执行以下步骤,让存储资源管理器信任它:If you have a copy of the self-signed certificate, you can instruct Storage Explorer to trust it by following these steps:

  1. 获取证书的 Base-64 编码 X.509 (.cer) 副本。Obtain a Base-64 encoded X.509 (.cer) copy of the certificate.
  2. 转到“编辑” > “SSL 证书” > “导入证书”,然后使用文件选取器查找、选择和打开 .cer 文件 Go to Edit > SSL Certificates > Import Certificates, and then use the file picker to find, select, and open the .cer file.

此问题还有可能是由于存在多个证书(根证书和中间证书)造成的。This issue may also occur if there are multiple certificates (root and intermediate). 若要修复此错误,必须同时添加这两个证书。To fix this error, both certificates must be added.

如果你不确定该证书来源于何处,可以执行以下步骤来找到它:If you're unsure of where the certificate is coming from, follow these steps to find it:

  1. 安装 OpenSSL。Install OpenSSL.
    • Windows:任何精简版本均可。Windows: Any of the light versions should be sufficient.
    • Mac 和 Linux:应包含在操作系统中。Mac and Linux: Should be included with your operating system.
  2. 运行 OpenSSL。Run OpenSSL.
    • Windows:打开安装目录,选择“/bin/”,然后双击“openssl.exe” 。Windows: Open the installation directory, select /bin/, and then double-click openssl.exe.
    • Mac 和 Linux:从终端运行 opensslMac and Linux: Run openssl from a terminal.
  3. 运行 s_client -showcerts -connect s_client -showcerts -connect
  4. 查找自签名证书。Look for self-signed certificates. 如果不确定哪些证书是自签名证书,请记下使用者 ("s:") 和证书颁发者 ("i:") 相同的任意位置。If you're unsure of which certificates are self-signed, make note of anywhere the subject ("s:") and issuer ("i:") are the same.
  5. 找到自签名证书后,将每个证书中从 -----BEGIN CERTIFICATE-----(含)到 -----END CERTIFICATE-----(含)的所有内容复制并粘贴到新的 .cer 文件中。When you find self-signed certificates, for each one, copy and paste everything from (and including) -----BEGIN CERTIFICATE----- through -----END CERTIFICATE----- into a new .cer file.
  6. 打开存储资源管理器,然后转到“编辑” > “SSL 证书” > “导入证书”。Open Storage Explorer and go to Edit > SSL Certificates > Import Certificates. 然后使用文件选取器查找、选择并打开创建的 .cer 文件。Then use the file picker to find, select, and open the .cer files that you created.

如果通过上述步骤无法找到任何自签名证书,请通过反馈工具联系我们以获取更多帮助。If you can't find any self-signed certificates by following these steps, contact us through the feedback tool. 也可选择通过命令行使用 --ignore-certificate-errors 标志打开存储资源管理器。You can also open Storage Explorer from the command line by using the --ignore-certificate-errors flag. 使用此标志打开后,存储资源管理器将忽略证书错误。When opened with this flag, Storage Explorer ignores certificate errors.

登录问题Sign-in issues

空白登录对话框Blank sign-in dialog box

出现空白登录对话框的原因往往是 Active Directory 联合身份验证服务 (AD FS) 提示存储资源管理器执行 Electron 不支持的重定向。Blank sign-in dialog boxes most often occur when Active Directory Federation Services (AD FS) prompts Storage Explorer to perform a redirect, which is unsupported by Electron. 若要解决此问题,可以尝试使用设备代码流进行登录。To work around this issue, you can try to use Device Code Flow for sign-in. 为此,请执行以下步骤:To do so, follow these steps:

  1. 在左侧垂直工具栏上,打开“设置” 。On the left vertical tool bar, open Settings. 在“设置”面板中,转到“应用程序” > “登录” 。In the Settings Panel, go to Application > Sign in. 启用“使用设备代码流登录” 。Enable Use device code flow sign-in.
  2. 打开“连接”对话框(选择左侧纵栏上的插头图标,或选择帐户面板上的“添加帐户”) 。Open the Connect dialog box (either through the plug icon on the left-side vertical bar or by selecting Add Account on the account panel).
  3. 选择要登录到的环境。Choose the environment you want to sign in to.
  4. 选择“登录” 。Select Sign In.
  5. 按照下一个面板上的说明进行操作。Follow the instructions on the next panel.

如果由于默认浏览器已登录到其他帐户而导致你无法登录到要使用的帐户,请执行以下操作之一:If you can't sign in to the account you want to use because your default browser is already signed in to a different account, do one of the following:

  • 手动将链接和代码复制到浏览器的私有会话中。Manually copy the link and code into a private session of your browser.
  • 手动将链接和代码复制到其他浏览器中。Manually copy the link and code into a different browser.

重新验证循环或 UPN 更改Reauthentication loop or UPN change

如果你处于重新验证循环中,或者已更改其中一个帐户的 UPN,请执行以下步骤:If you're in a reauthentication loop or have changed the UPN of one of your accounts, follow these steps:

  1. 删除所有帐户,然后关闭存储资源管理器。Remove all accounts and then close Storage Explorer.
  2. 从计算机中删除 .IdentityService 文件夹。Delete the .IdentityService folder from your machine. 在 Windows 中,该文件夹位于 C:\users\<username>\AppData\LocalOn Windows, the folder is located at C:\users\<username>\AppData\Local. 对于 Mac 和 Linux,可以在用户目录的根目录中找到该文件夹。For Mac and Linux, you can find the folder at the root of your user directory.
  3. 如果运行 Mac 或 Linux,则还需要从操作系统的密钥存储中删除 Microsoft.Developer.IdentityService 条目。If you're running Mac or Linux, you'll also need to delete the Microsoft.Developer.IdentityService entry from your operating system's keystore. 在 Mac 上,密钥存储是 Gnome Keychain 应用程序。On the Mac, the keystore is the Gnome Keychain application. 对于 Linux,该应用程序通常称为 Keyring,但名称可能会有所不同,具体取决于分发版。In Linux, the application is typically called Keyring, but the name might differ depending on your distribution.

Mac 密钥链错误Mac Keychain errors

有时,macOS 密钥链可能会进入导致存储资源管理器的身份验证库出现问题的状态。The macOS Keychain can sometimes enter a state that causes issues for the Storage Explorer authentication library. 若要使 Keychain 进入此状态,请执行以下步骤:To get the Keychain out of this state, follow these steps:

  1. 关闭存储资源管理器。Close Storage Explorer.

  2. 打开 Keychain(按命令键+空格键,键入 keychain,然后按 Enter)。Open Keychain (press Command+Spacebar, type keychain, and press Enter).

  3. 选择“登录”Keychain。Select the "login" Keychain.

  4. 选择挂锁图标以锁定 Keychain。Select the padlock icon to lock the Keychain. (该过程完成后,挂锁将以锁定状态显示。(The padlock will appear locked when the process is complete. 这可能需要几秒钟的时间,具体要取决于打开的应用)。It might take a few seconds, depending on what apps you have open).


  5. 打开存储资源管理器。Open Storage Explorer.

  6. 此时会出现一条类似于“服务中心想要访问 Keychain”的消息。You're prompted with a message like "Service hub wants to access the Keychain." 输入 Mac 管理员帐户密码,然后选择“始终允许” (如果未显示“始终允许” ,则选择“允许” )。Enter your Mac admin account password and select Always Allow (or Allow if Always Allow isn't available).

  7. 请尝试登录。Try to sign in.

常规登录故障排除步骤General sign-in troubleshooting steps

  • 在 macOS 上操作时,如果登录窗口永远不会出现,而是一直显示“正在等待身份验证” 对话框,请尝试这些步骤If you're on macOS, and the sign-in window never appears over the Waiting for authentication dialog box, try these steps.
  • 重启存储资源管理器。Restart Storage Explorer.
  • 如果身份验证窗口为空,请等待至少一分钟,然后关闭身份验证对话框。If the authentication window is blank, wait at least one minute before closing the authentication dialog box.
  • 确保为计算机和存储资源管理器正确配置了代理和证书设置。Make sure that your proxy and certificate settings are properly configured for both your machine and Storage Explorer.
  • 如果运行 Windows,并且你有权访问同一台计算机上的 Visual Studio 2019 和登录凭据,请尝试登录到 Visual Studio 2019。If you're running Windows and have access to Visual Studio 2019 on the same machine and to the sign-in credentials, try signing in to Visual Studio 2019. 成功登录 Visual Studio 2019 后,则可打开存储资源管理器并在帐户面板中查看帐户。After a successful sign-in to Visual Studio 2019, you can open Storage Explorer and see your account in the account panel.

如果这些方法均不起作用,请在 GitHub 上提出问题If none of these methods work, open an issue in GitHub.

缺少订阅和中断的租户Missing subscriptions and broken tenants

如果成功登录后无法检索订阅,请尝试以下故障排除方法:If you can't retrieve your subscriptions after you successfully sign in, try the following troubleshooting methods:

  • 验证你的帐户是否有权访问所需的订阅。Verify that your account has access to the subscriptions you expect. 可以通过登录到尝试使用的 Azure 环境的门户,来验证是否能够访问这些订阅。You can verify your access by signing in to the portal for the Azure environment you're trying to use.
  • 确保已通过正确的 Azure 环境(Azure 中国世纪互联)登录。Make sure you've signed in through the correct Azure environment (Azure China 21Vianet).
  • 如果使用代理服务器,请确保已正确配置存储资源管理器代理。If you're behind a proxy server, make sure you've configured the Storage Explorer proxy correctly.
  • 尝试删除并重新添加帐户。Try removing and re-adding the account.
  • 如果有“更多信息”链接,请检查针对失败的租户报告的错误消息。If there's a "More information" link, check which error messages are being reported for the tenants that are failing. 如果你不确定如何处理错误消息,请随意在 GitHub 上提出问题If you aren't sure how to respond to the error messages, feel free to open an issue in GitHub.

无法删除附加的帐户或存储资源Can't remove an attached account or storage resource

如果无法通过 UI 删除附加的帐户或存储资源,可以通过删除以下文件夹来手动删除所有附加的资源:If you can't remove an attached account or storage resource through the UI, you can manually delete all attached resources by deleting the following folders:

  • Windows: %AppData%/StorageExplorerWindows: %AppData%/StorageExplorer
  • macOS:/Users/<your_name>/Library/Application Support/StorageExplorermacOS: /Users/<your_name>/Library/Application Support/StorageExplorer
  • Linux:~/.config/StorageExplorerLinux: ~/.config/StorageExplorer


先关闭存储资源管理器,然后删除这些文件夹。Close Storage Explorer before you delete these folders.


如果曾经导入了任何 SSL 证书,请备份 certs 目录的内容。If you have ever imported any SSL certificates, back up the contents of the certs directory. 以后,可以使用备份来重新导入 SSL 证书。Later, you can use the backup to reimport your SSL certificates.

代理问题Proxy issues

首先,请确保输入的以下信息正确:First, make sure that the following information you entered is correct:

  • 代理 URL 和端口号The proxy URL and port number
  • 用户名和密码(若代理需要)Username and password if the proxy requires them


存储资源管理器不支持使用代理 auto-config 文件来配置代理设置。Storage Explorer doesn't support proxy auto-config files for configuring proxy settings.

常见解决方法Common solutions

如果仍遇到问题,请尝试以下故障排除方法:If you're still experiencing issues, try the following troubleshooting methods:

  • 如果在不使用代理时可以连接到 Internet,请确认未启用代理设置时存储资源管理器可以正常工作。If you can connect to the internet without using your proxy, verify that Storage Explorer works without proxy settings enabled. 如果出现这种情况,可能是代理设置有问题。If this is the case, there may be an issue with your proxy settings. 与管理员配合找到问题所在。Work with your administrator to identify the problems.
  • 确认使用代理服务器的其他应用程序按预期运行。Verify that other applications that use the proxy server work as expected.
  • 验证是否能够连接到尝试使用的 Azure 环境的门户。Verify that you can connect to the portal for the Azure environment you're trying to use.
  • 确认可以收到来自服务终结点的响应。Verify that you can receive responses from your service endpoints. 在浏览器中输入其中一个终结点 URL。Enter one of your endpoint URLs into your browser. 如果可以连接,应收到 InvalidQueryParameterValue 或类似的 XML 响应。If you can connect, you should receive InvalidQueryParameterValue or a similar XML response.
  • 如果其他人也在通过该代理服务器使用存储资源管理器,请确认他们可以连接。If someone else is also using Storage Explorer with your proxy server, verify that they can connect. 如果他们可以连接,请与代理服务器管理员联系。If they can, you may have to contact your proxy server admin.

诊断问题的工具Tools for diagnosing issues

如果有 Fiddler for Windows 等网络服务工具,则能够按以下方式诊断问题:If you have networking tools, such as Fiddler for Windows, you can diagnose the problems as follows:

  • 如果必须通过代理工作,则必须将网络服务工具配置为通过代理进行连接。If you have to work through your proxy, you may have to configure your networking tool to connect through the proxy.

  • 检查网络服务工具使用的端口号。Check the port number used by your networking tool.

  • 输入存储资源管理器中代理设置的本地主机 URL 和网络服务工具的端口号。Enter the local host URL and the networking tool's port number as proxy settings in Storage Explorer. 如果正确完成此操作,网络服务工具将开始记录存储资源管理区向管理和服务终结点发出的网络请求。When you do this correctly, your networking tool starts logging network requests made by Storage Explorer to management and service endpoints. 例如,在浏览器中输入 作为 Blob 终结点时,收到如下所示的响应:For example, enter for your blob endpoint in a browser, and you'll receive a response that resembles the following:


    此响应表示资源存在,不过无法访问它。This response suggests the resource exists, even though you can't access it.

与代理服务器管理员联系Contact proxy server admin

如果代理设置正确,则必须与代理服务器管理员联系,以便:If your proxy settings are correct, you may have to contact your proxy server admin to:

  • 确保代理不会阻止到 Azure 管理或资源终结点的流量。Make sure your proxy doesn't block traffic to Azure management or resource endpoints.
  • 验证代理服务器使用的身份验证协议。Verify the authentication protocol used by your proxy server. 存储资源管理器当前不支持 NTLM 代理。Storage Explorer doesn't currently support NTLM proxies.

“无法检索子级”错误消息"Unable to Retrieve Children" error message

如果通过代理连接到 Azure,请确认代理设置正确无误。If you're connected to Azure through a proxy, verify that your proxy settings are correct. 如果已获取以订阅或帐户所有者身份访问资源的权限,请验证是否对该资源拥有读取或列出权限。If you're granted access to a resource from the owner of the subscription or account, verify that you have read or list permissions for that resource.

连接字符串没有完整的配置设置Connection string doesn't have complete configuration settings

如果收到此错误消息,则表示你可能没有所需的权限来获取你的存储帐户的密钥。If you receive this error message, it's possible that you don't have the necessary permissions to obtain the keys for your storage account. 若要确认是否如此,请转到门户并找到你的存储帐户。To confirm that this is the case, go to the portal and locate your storage account. 可以通过右键单击存储帐户的节点并选择“在门户中打开”来执行此操作 。You can do this by right-clicking the node for your storage account and selecting Open in Portal. 然后转到“访问密钥”边栏选项卡 。Then, go to the Access Keys blade. 如果你无权查看密钥,则会看到“你没有访问权限”消息。If you don't have permissions to view keys, you'll see a "You don't have access" message. 若要解决此问题,可以从其他某人获取帐户密钥并结合名称和密钥附加存储帐户,或者,向某人索要存储帐户的 SAS 并使用它来附加存储帐户。To work around this issue, you can either obtain the account key from someone else and attach through the name and key, or you can ask someone for a SAS to the storage account and use it to attach the storage account.

如果看到了帐户密钥,请在 GitHub 上提出问题,使我们能够帮助你解决问题。If you do see the account keys, file an issue in GitHub so that we can help you resolve the issue.

添加新连接时出错:TypeError:无法读取未定义的属性 'version'Error occurred while adding new connection: TypeError: Cannot read property 'version' of undefined

如果你在尝试添加自定义连接时收到此错误消息,则可能是本地凭据管理器中存储的连接数据已损坏。If you receive this error message when you try to add a custom connection, the connection data that's stored in the local credential manager might be corrupted. 若要解决此问题,请尝试删除已损坏的本地连接,然后重新添加它们:To work around this issue, try deleting your corrupted local connections, and then re-add them:

  1. 启动存储资源管理器。Start Storage Explorer. 在顶部菜单中,转到“帮助” > “切换开发人员工具” 。From the menu, go to Help > Toggle Developer Tools.
  2. 在打开的窗口中的“应用程序”选项卡上,转到“本地存储”(左侧)>“file://”。 In the opened window, on the Application tab, go to Local Storage (left side) > file://.
  3. 根据遇到问题的连接类型,查找其密钥并将其值复制到文本编辑器。Depending on the type of connection you're having an issue with, look for its key and then copy its value into a text editor. 该值是自定义连接名称的数组,如下所示:The value is an array of your custom connection names, like the following:
    • 存储帐户Storage accounts
      • StorageExplorer_CustomConnections_Accounts_v1
    • Blob 容器Blob containers
      • StorageExplorer_CustomConnections_Blobs_v1
      • StorageExplorer_CustomConnections_Blobs_v2
    • 文件共享File shares
      • StorageExplorer_CustomConnections_Files_v1
    • 队列Queues
      • StorageExplorer_CustomConnections_Queues_v1
    • Tables
      • StorageExplorer_CustomConnections_Tables_v1
  4. 保存当前连接名称后,将开发人员工具中的值设置为 []After you save your current connection names, set the value in Developer Tools to [].

若要保留未损坏的连接,可以使用以下步骤来查找损坏的连接。If you want to preserve the connections that aren't corrupted, you can use the following steps to locate the corrupted connections. 如果你不介意丢失所有现有连接,则可以跳过以下步骤,并按照平台特定说明清除连接数据。If you don't mind losing all existing connections, you can skip these steps and follow the platform-specific instructions to clear your connection data.

  1. 在文本编辑器中,将每个连接名称重新添加到开发人员工具,并检查连接是否仍在运行。From a text editor, re-add each connection name to Developer Tools, and then check whether the connection is still working.
  2. 如果连接正常工作,则表示它未损坏,你可以安全地将其保留。If a connection is working correctly, it's not corrupted and you can safely leave it there. 如果连接不起作用,请从开发人员工具中删除其值并将其记录,以便以后可以重新添加它。If a connection isn't working, remove its value from Developer Tools, and record it so that you can add it back later.
  3. 重复此步骤,直到检查完所有连接。Repeat until you have examined all your connections.

完成所有连接后,针对所有未添加回的连接名称,必须清除其损坏的数据(如果有),并使用存储资源管理器中的标准步骤将其重新添加。After going through all your connections, for all connections names that aren't added back, you must clear their corrupted data (if there is any) and add them back by using the standard steps in Storage Explorer:

  1. 在“开始”菜单中,搜索“凭据管理器”并将其打开。 On the Start menu, search for Credential Manager and open it.
  2. 转到“Windows 凭据”。 Go to Windows Credentials.
  3. 在“一般凭据”下,找到具有 <connection_type_key>/<corrupted_connection_name> 键的条目(例如 StorageExplorer_CustomConnections_Accounts_v1/account1)。 Under Generic Credentials, look for entries that have the <connection_type_key>/<corrupted_connection_name> key (for example, StorageExplorer_CustomConnections_Accounts_v1/account1).
  4. 删除这些条目并重新添加连接。Delete these entries and re-add the connections.

如果运行这些步骤后仍遇到此错误,或者你想要分享连接损坏原因的看法,请在 GitHub 页上提出问题If you still encounter this error after running these steps, or if you want to share what you suspect has corrupted the connections, open an issue on our GitHub page.

SAS URL 的问题Issues with SAS URL

如果通过 SAS URL 连接到服务时遇到错误:If you're connecting to a service through a SAS URL and experiencing an error:

  • 请确认 URL 提供了读取或列出资源所需的权限。Verify that the URL provides the necessary permissions to read or list resources.
  • 请确认 URL 未过期。Verify that the URL has not expired.
  • 如果 SAS URL 基于访问策略,请确认访问策略尚未吊销。If the SAS URL is based on an access policy, verify that the access policy has not been revoked.

如果意外附加了无效的 SAS URL,并且现在无法分离,请执行以下步骤:If you accidentally attached by using an invalid SAS URL and now cannot detach, follow these steps:

  1. 运行存储资源管理器时,按 F12 打开“开发人员工具”窗口。When you're running Storage Explorer, press F12 to open the Developer Tools window.
  2. 在“应用程序”选项卡上,选择左侧树中的“本地存储” > “file://”。 On the Application tab, select Local Storage > file:// in the tree on the left.
  3. 查找与有问题的 SAS URI 服务类型关联的键。Find the key associated with the service type of the problematic SAS URI. 例如,如果用于 blob 容器的 SAS URI 错误,请查找名为 StorageExplorer_AddStorageServiceSAS_v1_blob 的键。For example, if the bad SAS URI is for a blob container, look for the key named StorageExplorer_AddStorageServiceSAS_v1_blob.
  4. 键的值应为 JSON 数组。The value of the key should be a JSON array. 找到与错误 URI 关联的对象,并将其删除。Find the object associated with the bad URI, and then delete it.
  5. 按 Ctrl+R 重新加载存储资源管理器。Press Ctrl+R to reload Storage Explorer.

Linux 依赖项Linux dependencies

Snap Store 中以内嵌项的形式提供了存储资源管理器 1.10.0 和更高版本。Storage Explorer 1.10.0 and later is available as a snap from the Snap Store. 存储资源管理器内嵌项会自动安装其所有依赖项,并在新版内嵌项推出时更新。The Storage Explorer snap installs all its dependencies automatically, and it's updated when a new version of the snap is available. 安装存储资源管理器内嵌项是建议的安装方法。Installing the Storage Explorer snap is the recommended method of installation.

存储资源管理器要求使用密码管理器,你可能需要手动连接密码管理器才能正常运行存储资源管理器。Storage Explorer requires the use of a password manager, which you might need to connect manually before Storage Explorer will work correctly. 可以运行以下命令,将存储资源管理器连接到系统的密码管理器:You can connect Storage Explorer to your system's password manager by running the following command:

snap connect storage-explorer:password-manager-service :password-manager-service

还可以下载 .tar.gz 文件格式的应用程序,但必须手动安装依赖项。You can also download the application as a .tar.gz file, but you'll have to install dependencies manually.


仅 Ubuntu 分发版支持 .tar.gz 下载内容中提供的存储资源管理器。Storage Explorer as provided in the .tar.gz download is supported only for Ubuntu distributions. 其他分发版尚未经过验证,可能需要替代包或附加包。Other distributions haven't been verified and may require alternative or additional packages.

这些包是 Linux 上存储资源管理器的最常见要求:These packages are the most common requirements for Storage Explorer on Linux:


存储资源管理器 1.7.0 及更低版本需要 .NET Core 2.0。Storage Explorer version 1.7.0 and earlier require .NET Core 2.0. 如果安装了更高版本的 .NET Core,则必须修补存储资源管理器If you have a newer version of .NET Core installed, you'll have to patch Storage Explorer. 如果运行存储资源管理器 1.8.0 或更高版本,则可以使用的最高版本为 .NET Core 2.2。If you're running Storage Explorer 1.8.0 or later, you should be able to use up to .NET Core 2.2. 高于 2.2 的版本目前尚未验证其使用情况。Versions beyond 2.2 have not been verified to work at this time.

  1. 下载存储资源管理器。Download Storage Explorer.
  2. 安装 .NET Core 运行时Install the .NET Core Runtime.
  3. 运行以下命令:Run the following command:
    sudo apt-get install libgconf-2-4 libgnome-keyring0

修补适用于 .NET Core 更高版本的存储资源管理器Patching Storage Explorer for newer versions of .NET Core

对于存储资源管理器 1.7.0 或更低版本,可能需要修补存储资源管理器使用的 .NET Core 版本:For Storage Explorer 1.7.0 or earlier, you might have to patch the version of .NET Core used by Storage Explorer:

  1. 从 NuGet 下载 StreamJsonRpc 版本 1.5.43。Download version 1.5.43 of StreamJsonRpc from NuGet. 在页面的右侧找到“下载包”链接。Look for the "Download package" link on the right side of the page.
  2. 下载该包后,将其文件扩展名从 .nupkg 更改为 .zipAfter you download the package, change its file extension from .nupkg to .zip.
  3. 将包解压缩。Unzip the package.
  4. 打开 streamjsonrpc.1.5.43/lib/netstandard1.1/ 文件夹。Open the streamjsonrpc.1.5.43/lib/netstandard1.1/ folder.
  5. StreamJsonRpc.dll 复制到存储资源管理器文件夹中的以下位置:Copy StreamJsonRpc.dll to the following locations in the Storage Explorer folder:
    • StorageExplorer/resources/app/ServiceHub/Services/Microsoft.Developer.IdentityService/
    • StorageExplorer/resources/app/ServiceHub/Hosts/ServiceHub.Host.Core.CLR.x64/

Azure 门户中的“在资源管理器中打开”不起作用"Open In Explorer" from the Azure portal doesn't work

如果在 Azure 门户上单击“在资源管理器中打开”按钮不起作用,请确保使用兼容的浏览器 。If the Open In Explorer button on the Azure portal doesn't work, make sure you're using a compatible browser. 以下浏览器已通过兼容性测试:The following browsers have been tested for compatibility:

  • Microsoft EdgeMicrosoft Edge
  • Mozilla FirefoxMozilla Firefox
  • Google ChromeGoogle Chrome
  • Microsoft Internet ExplorerMicrosoft Internet Explorer

后续步骤Next steps

如果上述解决方法均不起作用,请在 GitHub 上提出问题If none of these solutions work for you, open an issue in GitHub. 也可以选择左下角的“向 GitHub 报告问题”按钮。 You can also do this by selecting the Report issue to GitHub button in the lower-left corner.