error creating catalog in Unity Catalog – EXTERNAL_LOCATION_DOES_NOT_EXIST and admin console storage
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2025 03:50 AM
Hi all, I’m trying to create a new catalog in Azure Databricks Unity Catalog but I’m running into issues. When I tried to add a default path in the Admin Console → Metastore settings, I got this error: “Metastore storage root URL does not exist. Please provide a storage location for the catalog (for example 'CREATE CATALOG myCatalog MANAGED LOCATION <location-path>'). Alternatively set up a metastore root storage location.” I’m on Azure Databricks Premium (free trial) with Unity Catalog enabled. My storage account is STORAGE123 and the container is warehousetest, and I already set up a Data Connector for this storage. Do I need to explicitly create a Storage Credential and External Location in Unity Catalog even though the container is already connected with a Data Connector? Is the metastore-level storage path mandatory, or can catalogs be created only with external locations? What’s the correct setup order (Admin console path → external location → catalog)? Any guidance or step-by-step instructions would be really appreciated.
Thanks!