cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Error message while running queries

CJOkpala
New Contributor II

While running queries, both in SQL or notebooks, we get this error message below:
INTERNAL_ERROR: Unexpected error when trying to access the statement result. Missing credentials to access the DBFS root storage container in Azure.

The access connector is set correctly, has proper permissions to the Storage account. Not sure where the issue comes from.

2 REPLIES 2

lingareddy_Alva
Honored Contributor II

Hi @CJOkpala 

This error suggests an issue with the credentials needed to access your Azure storage container from Databricks. Let's troubleshoot this methodically since there seems to be a disconnect between your configured access connector and the actual authentication happening during query execution.

The error "Missing credentials to access the DBFS root storage container in Azure" typically occurs when Databricks cannot properly authenticate with the Azure Storage account that hosts your DBFS root or external tables.

Here are several potential causes and solutions:
1. Azure Storage Account Access Configuration
The problem might be related to how your Databricks workspace is configured to access the storage account:

Check if Unity Catalog is in use: If you're using Unity Catalog, the authentication method differs from traditional external locations
Verify Service Principal permissions: The service principal used by the access connector needs specific permissions

2. Access Connector Configuration Issues
Even though you mentioned the access connector is set correctly, double-check these common issues:

3. Credential Scoping Problems

4. Multi-level Authentication Issues

5. Immediate Workarounds
While troubleshooting the root cause, you could try:
1. Temporarily mount the storage explicitly
dbutils.fs.mount(
source = "abfss://<container-name>@<storage-account-name>.dfs.core.windows.net/",
mount_point = "/mnt/my-mount-point",
extra_configs = {...} # Your auth configs
)

2. Check if the issue happens in a different cluster with identical configurations.

 

LR

Hi LRALVA,

Thanks for reaching out but in my case we don't mount the storage since using Unity Catalog we use storage credentials/external locations.

 

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local communityโ€”sign up today to get started!

Sign Up Now