Azure Blob Storage Cloud Drive Client Agent Features. Once the Mac client agent software is deployed on users' Mac, the cloud drive will show up in the Mac finder as if it were a pluggable external drive with the following features. Azure Storage Explorer troubleshooting guide.; 17 minutes to read +16; In this article. Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux. The app can connect to storage accounts hosted on Azure, national clouds, and Azure Stack.
If your download is not starting, click here.
Thank you for downloading Azure Storage Explorer for Mac from our software library
The download version of Azure Storage Explorer for Mac is 0.8.0. The package you are about to download is authentic and was not repacked or modified in any way by us. The software is periodically scanned by our antivirus system. We also encourage you to check the files with your own antivirus before launching the installation.
Azure Storage Explorer antivirus report
This download is virus-free.This file was last analysed by Free Download Manager Lib 6 days ago.
Often downloaded with
Backup & Restore
MoneyWiz - Personal Finance
Bookkeeping & Cataloging
-->
Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux. 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 permissions issues
Role-based access control RBAC enables highly granular access management of Azure resources by combining sets of permissions into roles. Here are some strategies to get RBAC working optimally in Storage Explorer.
How do I access my resources in Storage Explorer?
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. 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.
Note
Access keys grant unrestricted permissions to anyone who holds them. Therefore, we don't recommend that you hand out these keys to account users. 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. 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 Storage has two layers of access: management and data. Subscriptions and storage accounts are accessed through the management layer. Containers, blobs, and other data resources are accessed through the data layer. For example, if you want to get a list of your storage accounts from Azure, you send a request to the management endpoint. If you want a list of blob containers in an account, you send a request to the appropriate service endpoint.
Azure roles can grant you 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.
Storage Explorer makes it easy to access your resources by gathering the necessary information to connect to your Azure resources. 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?
If you want to access blob containers or queues, you can attach to those resources using your Azure credentials.
For other resource types, we don't currently have an RBAC-related solution. As a workaround, you can request a SAS URI to attach to your resource.
Recommended Azure built-in roles
There are several Azure built-in roles that 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:
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:
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:
It works quickly and easily. And it also can help people get songs even the songs can't be downloaded - record songs with ID3 tags. For download music, users just need to copy and paste the URL(web address) of a song to the download box. Open song download for mac.
If you can't find any self-signed certificates by following these steps, contact us through the feedback tool. 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 issuesBlank sign-in dialog box
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:
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:
Reauthentication loop or UPN change
If you're in a reauthentication loop or have changed the UPN of one of your accounts, follow these steps:
Conditional Access
Because of a limitation in the Azure AD Library used by Storage Explorer, Conditional Access isn't supported when Storage Explorer is being used on Windows 10, Linux, or macOS.
Mac Keychain errors
The macOS Keychain can sometimes enter a state that causes issues for the Storage Explorer authentication library. To get the Keychain out of this state, follow these steps:
General sign-in troubleshooting steps
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:
Microsoft Azure Storage Explorer Mac
Can't remove an attached account or storage resource
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:
Note
Close Storage Explorer before you delete these folders.
Note
If you have ever imported any SSL certificates, back up the contents of the
certs directory. Later, you can use the backup to reimport your SSL certificates.
Proxy issues
First, make sure that the following information you entered is correct:
Note
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:
Tools for diagnosing issues
If you have networking tools, such as Fiddler for Windows, you can diagnose the problems as follows:
Contact proxy server admin
If your proxy settings are correct, you may have to contact your proxy server admin to:
'Unable to Retrieve Children' error message
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. 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.
If you do see the account keys, file an issue in GitHub so that we can help you resolve the issue.
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:
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.
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:
Local credential management varies depending on the Linux distribution. If your Linux distribution doesn't provide a built-in GUI tool for local credential management, you can install a third-party tool to manage your local credentials. For example, you can use Seahorse, an open-source GUI tool for managing Linux local credentials.
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.
Issues with SAS URL
If you're connecting to a service through a SAS URL and experiencing an error:
If you accidentally attached by using an invalid SAS URL and now cannot detach, follow these steps:
Linux dependenciesSnap
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:
Download Azure Storage Explorer Tool.tar.gz File
You can also download the application as a .tar.gz file, but you'll have to install dependencies manually.
Storage Explorer as provided in the .tar.gz download is supported for the following versions of Ubuntu only. Storage Explorer might work on other Linux distributions, but they are not officially supported.
Storage Explorer requires .NET Core to be installed on your system. We recommend .NET Core 2.1, but Storage Explorer will work with 2.2 as well.
Note
Storage Explorer version 1.7.0 and earlier require .NET Core 2.0. If you have a newer version of .NET Core installed, you'll have to patch Storage Explorer. If you're running Storage Explorer 1.8.0 or later, you need at least .NET Core 2.1.
Many libraries needed by Storage Explorer come preinstalled with Canonical's standard installations of Ubuntu. Custom environments may be missing some of these libraries. If you have issues launching Storage Explorer, we recommend making sure the following packages are installed on your system:
Patching Storage Explorer for newer versions of .NET Core
For Storage Explorer 1.7.0 or earlier, you might have to patch the version of .NET Core used by Storage Explorer:
'Open In Explorer' from the Azure portal doesn't work
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:
Next steps
If none of these solutions work for you, open an issue in GitHub. You can also do this by selecting the Report issue to GitHub button in the lower-left corner.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |