Question 185099 in Azure Question posted in
The official documentation to get you started can be found here.

Azure – Purview – error (3805) connector exception connection to the database

Question: When doing a Purview scan on Azure Databricks, I get the following error. What could be the cause of the error and how we can fix it?

Remarks: For safety, I have replaced the 16 digits in the error with xxxxxxxxxxxxxxxx. Also we have Java JDK 11 installed on the server hosting the Integration Runtime

Error: (3805) Connector Exception: Connection to the database (with URL jdbc:databricks://adb-xxxxxxxxxxxxxxxx.11.azuredatabricks.net:443/default;transportMode=http;ssl=1;httpPath=sql/protocolv1/o/xxxxxxxxxxxxxxxx/0455-165046-lamas36;AuthMech=3) failed: [Databricks]DatabricksJDBCDriver Communication link failure. Failed to connect to server. Reason: HTTP Response code: 403, Error message: Unknown. More info.

Tags:

2

Answers


  1. 0

    403 error means that your identity for which you generated the personal access token (PAT) doesn’t have sufficient permissions to access the given SQL Warehouse. Adjust permissions to it.

    Login or Signup to reply.
  2. 0

    I tried the similar thong from my environment, and it got scanned successfully.

    enter image description here

    While researching about the error I found out that the cause of error is Wrong Personal Access token (PAT) is using in the credential I was able to repro the error.

    The cause of error can be:

    • Wrong Personal Access token (PAT) using in credential.
    • Expired Personal Access token (PAT).

    The resolution is to use valid Personal Access token (PAT) in credentials:

    • Create appropriate Personal Access token (PAT) to access azure databricks and copy it as shown below.
      enter image description here

    • Add that token in keyvault and use it in credential as below.
      enter image description here

    • Create a new credential with above secret.
      enter image description here

    • Use it in credential.
      enter image description here

    Successfully scanned:
    enter image description here

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search