AzureStorageExplorer icon indicating copy to clipboard operation
AzureStorageExplorer copied to clipboard

Unable to retrieve child resources

Open jrolain opened this issue 2 months ago • 8 comments

Storage Explorer Version

1.40.0

Regression From

1.39.1

Architecture

x64

Storage Explorer Build Number

20250925.27

Platform

Windows

OS Version

Windows 11

Bug Description

Attempting to browse storage with Azure Storage Explorer using SAS token to connect and receiving the following error:

Unable to retrieve child resources

ProducerError:{ "name": "Node Fetch Error", "message": "{"name":"Node Fetch Error","cause":{},"code":"ENOTFOUND","errno":-3008}" }

Resource Types

Blobs

Authentication Method

Shared access signature (SAS)

Connection Type

None

Steps to Reproduce

  1. Launch Storage Explorer
  2. Select Attach to a resource
  3. Select Storage Account or Service
  4. Select Shared access signature URL (SAS)
  5. Type (or paste) in Service URL
  6. Once storage is connected attempt to view Blob containers

Actual Experience

Error received:

Unable to retrieve child resources

ProducerError:{ "name": "Node Fetch Error", "message": "{"\name":"Node Fetch Error","cause":{},"code":"ENOTFOUND","errno":-3008}" }

Expected Experience

Able to browse/view Blob containers and contents.

Additional Context

No response

jrolain avatar Oct 24 '25 14:10 jrolain

I have a similar issue with many ressources that worked previously.

dradjou avatar Oct 24 '25 17:10 dradjou

I’m also experiencing this issue. My setup involves a Virtual Machine hosted in one Azure tenant and a Storage Account in a different tenant. I’m trying to access the file shares from the Storage Account using Microsoft Azure Storage Explorer from my VM.

However, I’m encountering the following error:

Unable to retrieve child resources

ProducerError: { "name": "Node Fetch Error", "message": "read ECONNRESET", "stack": "Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20)", "cause": {}, "code": "ECONNRESET", "errno": -4077 }

Could you please advise if there are any network, firewall, or tenant configuration requirements that need to be in place for cross-tenant access to Azure File Shares via Storage Explorer?

SumukhaHatwar avatar Oct 24 '25 17:10 SumukhaHatwar

@jrolain @dradjou Could you self-diagnose by following these suggested steps in the troubleshooting guide and let us know your findings? Thanks.

jinglouMSFT avatar Oct 24 '25 17:10 jinglouMSFT

@SumukhaHatwar Yours is a different cause. It's probably better to open a new issue so it's not getting buried in this issue. From the error message it seemed you had some issues with SSL/TLS. Take a look at this section in the troubleshooting guide and let us know your findings. Thanks.

jinglouMSFT avatar Oct 24 '25 18:10 jinglouMSFT

@jinglouMSFT - self-diagnosed and all settings are correct. This worked before I updated Storage Explorer ~2 days ago

jrolain avatar Oct 24 '25 18:10 jrolain

Selecting File Shares under a Storage Account generates the following error:

Build 1.40.2 (110) AzCopy Version: 10.30.1

Unable to retrieve child resources

ProducerError:{
  "name": "Electron Net Error",
  "message": "net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH",
  "stack": "Error: net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH\n    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:124413)\n    at SimpleURLLoaderWrapper.emit (node:events:519:28)",
  "cause": {}
}

jamesfdavis avatar Nov 17 '25 21:11 jamesfdavis

Any updates on this issue? I installed version 1.40.2 and had the same issue. Then I uninstalled and went back to 1.39.1...still have the same issue and error. Nothing changed with any of the other variables (SAS, Storage, etc.).

jrolain avatar Dec 05 '25 18:12 jrolain

Any updates on this issue? I installed version 1.40.2 and had the same issue. Then I uninstalled and went back to 1.39.1...still have the same issue and error. Nothing changed with any of the other variables (SAS, Storage, etc.).

We determined this was related to a security block in place on the MSFT ENDPOINTS.

I'd check your underlying connectivity.

jamesfdavis avatar Dec 05 '25 19:12 jamesfdavis