"Error 400: Unable to load" when creating shortcut to ADLS2

[Krumelur]

I saw the following error a couple of weeks back, then it disappeared, now it's back.

In a Lakehouse I'm creating a shortcut to ADLS2. The storage account has 33 containers. In the wizard only 2 are displayed, then a "Show more" link is added. Clicking this link produces the error "Error 400 - The specifed resource name contains invalid characters.".

There are no invalid characters in any of the container names, they are all just lowercase characters and hypens.

Also, as I wrote, the error was there, gone, and now is back.

If I click on one of the two containers being displayed, I can see their content, so it is not a permission issue.

I tried changing the connection from SPN to OAuth, no success.

Known issue?

[Anonymous]

HI @Krumelur,

>>If I click on one of the two containers being displayed, I can see their content, so it is not a permission issue.

Have you tried to use Azure Storage Explorer or view these containers contents at azure portal side with the account that you used to test? 

Use Azure Storage Explorer with Azure Data Lake Storage Gen2 - Azure Storage | Microsoft Learn

I'd like to confirm if you have enough permission to view all these contents(include content that named with lowercase characters and hyphens) normally based on native connectors.

Please share some more detail information include snapshot about test result to help us clarify and troubleshoot on your scenario.
Regards,

Xiaoxin Sheng

[Krumelur · Accepted solution]

Yes, access permissions are not the problem. I did some debugging in Edge and found the following. The "Show more" link is supposed to trigger a continuation on the container list. However, the XHR fails because of an invalid parameter value "directory=model_root". See screenshots below.

If I replay the request, I see exactly the error I get in Fabric.

If I remove the parameter (second screenshot), the request will return the remaining container names.

It's working as long there is no continutation used. I can observer similar behavior in Azure Portal's storage explorer. There, the list of containers also ends after two items and clicking "More" reveals the others. For other storage accounts, the initial count of containers is higher. I don't know what the logic is when a continuation token is issued and when not, but I'm certain the scripting issue is the root problem here. 

 

[Anonymous]

HI @Krumelur,

I'm glad to hear you find the causing of this issue.

According to your description and snapshots, it seems like the 'directory=model_root' parameter only work for azure portal and storage explorer. They do not work when these requests are sent from fabric - create 'ADLS Gen2 shortcut' navigation panel.

I suppose they may cause by Azure data lake storage team apply changes on the Gen 2 interface or assign new parameter strings for fabric usage.

For this scenario, I'd like to suggest you try to contact to ADLS or fabric support team to report this scenario to confirm if any backend changes on it and get further support.

Regards,

Xiaoxin Sheng