Forum Discussion

Srisakthi's avatar
Srisakthi
Super User
1 year ago
Solved

Mirrored Azure Databricks Catalog

Hi Everyone,

 

I had created my Mirrored Azure Databricks Catalog some 20 days ago. it was working fine til yesterday and suddenly it stopped working today. When i clicked on Manage Catalog i see the below error

{"error":{"code":"ArtifactConnection_InaccessibleDatasource","pbi.error":{"code":"ArtifactConnection_InaccessibleDatasource","details":[{"code":"ArtifactConnection_InaccessibleDatasource","detail":{"type":1,"value":"A datasource bound to connection is inaccessible to the binding user. DatasourceId: 2154ee5f-5d6a-4d47-b164-f1ae23538e5e. ConnectionId: 2154ee5f-5d6a-4d47-b164-f1ae23538e5e. UserObjectId: 38077e87-6e1c-4249-a693-740f470d264c. DMTSErrorCode: DMTS_OAuthTokenRefreshFailedError."}}],"exceptionCulprit":1}}}

 

Error message is not clear whether error is at Azure databricks permission or connectivity to azure databricks from fabric. It would be great if the error message is clear. 

Fix for issue : Re-authenticated the connection in "Manage Connections and gateway" and it started working.

 

Regards,

Srisakthi

Mirroring
Tips and Tricks
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi, Srisakthi 

     

    Thanks for sharing your question. From the information provided, it appears that re-authenticating the connection in "Manage Connections and gateway" resolved the issue. This suggests that the problem was likely related to the authentication or permissions for accessing the Azure Databricks datasource.

     

    Best Regards,

    Community Support Team _Charlotte

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi, Srisakthi 

     

    Thanks for sharing your question. From the information provided, it appears that re-authenticating the connection in "Manage Connections and gateway" resolved the issue. This suggests that the problem was likely related to the authentication or permissions for accessing the Azure Databricks datasource.

     

    Best Regards,

    Community Support Team _Charlotte

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.