How to fix "the specify container does not exist"

Kiba, Wilfried 0 Reputation points
2024-05-28T22:09:51.04+00:00

Hi,

When running the upgrade for my storage account to enable hierarchical namespace, I face an issue saying that “the specify container does not exist”. Can you help me to resolve this issue?

Please find attached a screeshot of the issueerreur

I am following this tutorial page.

https://microsoftlearning.github.io/DP-900T00A-Azure-Data-Fundamentals/Instructions/Labs/dp900-02-storage-lab.html#explore-azure-data-lake-storage-gen2

Thanks

Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
1,409 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amrinder Singh 4,110 Reputation points Microsoft Employee
    2024-06-01T04:31:31.48+00:00

    Hello Kiba, Wilfried - Based on the snippet you have shared,

    In the Step 2, it states validation is completed.

    In the Step 3, it fails, and the error message states some validation has failed. When you click on the View Errors link, you are getting container does not exist. Is that understanding, correct?

    Now, if there are validation error it creates a container named hnserror with an error file pointing to the potential reason of the blocker. But in case the validation succeeded this container might not have got created in the first place itself and hence the exception is then correct because container doesn't exist.

    I would recommend the below:

    Retry the complete Upgrade Process to see if that helps.

    Review for any blocking/im-compatible/feature enabled on the account. Below is the link to refer:

    https://video2.skills-academy.com/en-us/azure/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to?tabs=azure-portal#review-feature-support

    If the above doesn't help, you might need to reach out to Support Team to review the backend logs and help with further troubleshooting ahead.

    0 comments