Share via

An error occurred while calling o361.sql. : com.databricks.backend.daemon.data.client.adl.AzureCredentialNotFoundException: Could not find ADLS Gen2 Token

PRAKASAM, SIVA 0 Reputation points
2024-02-23T03:19:34.6433333+00:00

An error occurred while calling o361.sql. : com.databricks.backend.daemon.data.client.adl.AzureCredentialNotFoundException: Could not find ADLS Gen2 Token

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.


1 answer

Sort by: Most helpful
  1. PRADEEPCHEEKATLA 91,866 Reputation points
    2024-02-23T04:46:03.9466667+00:00

    @PRAKASAM, SIVA - Thanks for the question and using MS Q&A platform.

    It looks like you are encountering an error related to Azure Databricks and ADLS Gen2 token. This error message indicates that the Azure Databricks backend daemon is unable to find the ADLS Gen2 token.

    To resolve this issue, you can try the following steps:

    • Check if the ADLS Gen2 token is still valid. If it has expired, you will need to generate a new token.
    • Ensure that the ADLS Gen2 token is correctly configured in Azure Databricks. You can check the configuration "Secrets" and verifying that the correct ADLS Gen2 token.

    For more details, refer to Connect to Azure Data Lake Storage Gen2 and Blob Storage.

    If the issue persists, please share more details like (configuration script used, error message with complete stacktrace) for further assistance.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.