"Unable to Retrieve Child Resources"

[kinneymic]

Preflight Checklist

• [X] I have installed the latest version of Storage Explorer.
• [X] I have checked existing resources, including the troubleshooting guide and the release notes.
• [X] I have searched for similar issues.

Storage Explorer Version

1.33.1

Regression From

no

Architecture

x64

Storage Explorer Build Number

20240410.2

Platform

Windows

OS Version

No response

Bug Description

Our IT recently gave me permissions to an Azure subscription, and further read access to a certain storage account. When I click on the "File Shares" drop down an error appears.

Steps to Reproduce

1. Launch Storage Explorer
2. Under desired subscription click on Storage accounts
3. Under desired storage account click on the File Shares drop down *Error shows up immediately

Unable to retrieve child resources

ProducerError:{ "name": "Error", "message": "Unable to perform operation 'FileServiceClient.listSharesSegment'. No suitable credentials provided.", "stack": "Error: Unable to perform operation 'FileServiceClient.listSharesSegment'. No suitable credentials provided.\n at sl.runOperation (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\file-extension\dist\src\index.js:38:5637)\n at sl.listSharesSegment (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\file-extension\dist\src\index.js:56:6448)\n at FileShareNodeProducer.produceFileShareNodes (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\file-extension\dist\src\index.js:56:53842)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Azure.Storage.FileShareProducer.produceFileShareNodes (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\@storage-explorer\file-extension\dist\src\index.js:59:13147)\n at async Ze.executeOperation (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\out\app\node\NodeProcessHostProxy.js:3:2742)\n at async Bt._handleExecuteRequest (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\out\app\node\NodeProcessHostProxy.js:7:915)\n at async Bt._handleMessage (C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\out\app\node\NodeProcessHostProxy.js:6:30146)\n at async C:\Users\z003du2z\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\out\app\node\NodeProcessHostProxy.js:6:27657" }

Actual Experience

Expected Experience

I expected to see and navigate through the File Share named "airflow-dags" (as illustrated through my SAS connection):

Additional Context

No response

[kinneymic]

I can successfully see the file share when I go to the online portal (portal.azure.com):

[kinneymic]

Looks like this was solved internally. IT figured out the right role for me.

[dinhe878]

I encountered the same error while executing different steps:

1. Launch Storage Explorer.
2. Under desired subscription click on a Storage account.
3. Navigate to a blob container.
4. Navigate to a folder in that blob container.
5. Right click while selecting the folder, select "Copy Direct Link".
6. Open a browser and paste the link and enter.
7. Select "Open Microsoft Azure Storage Explorer".
8. Now redirect to the Microsoft Azure Storage Explorer, with "Open Direct Link" dialog select "Navigate to Container".
9. Quit the Microsoft Azure Storage Explorer app.
10. Re-execute the link in step 6.
11. The identical same error message appears.

[dinhe878]

Looks like this was solved internally. IT figured out the right role for me.

Hi @kinneymic, can you tell me more how did IT fixed your issue?

[kinneymic]

Looks like this was solved internally. IT figured out the right role for me.

Hi @kinneymic, can you tell me more how did IT fixed your issue?

They used the "Contributor" role. But since I am not the owner, they are now creating a custom role for me. (which is more complicated than I understand)

[dinhe878]

Thanks @kinneymic. If possible, could you ask more details about this custom role that your IT created for you? We have encountered this same error with somewhat different scenario, but it might be just the same role-issue that triggers that.