Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
753 questions
Google Big Query scan failing in Purview
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 97%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKR%3C/text%3E%3C/svg%3E)
KumKum Rekhari
0
Reputation points
I am scanning a google big query project from Purview and getting this error - Error 3805 : Connector Exception - Connection to the database with the URL ( jdbc:bigquery://https://www.googleapis.com/bigquery (followed by project and service accout details) failed :Simba:bigqueryjdbcdriver(100004) Httptransport IO Error:EXEC_JOB_TIMEOUT_ERROR)
The jdbc driver is installed in Self hosted integration runtime and service account is set up in google big query . Can you help please?
{count} votes
-
PRADEEPCHEEKATLA-MSFT 69,771 Reputation points Microsoft Employee2023-11-20T06:04:14.2566667+00:00 @KumKum Rekhari - Thanks for the question and using MS Q&A platform.
It seems like there is an issue with the connection to the Google BigQuery project. The error message indicates that there is a timeout error while executing the job. This could be due to a number of reasons such as network connectivity issues, incorrect credentials, or an issue with the configuration of the scan.
To troubleshoot this issue, I would suggest the following steps:
Check the network connectivity between the self-hosted integration runtime and the Google BigQuery project. Ensure that there are no firewall rules blocking the connection.
Verify that the credentials used to connect to the Google BigQuery project are correct. Ensure that the service account has the necessary permissions to access the project.
Check the configuration of the scan. Ensure that the correct integration runtime is selected and that the credentials are configured correctly.
Check the logs for any additional error messages that may provide more information about the issue.
If you have already checked these steps and are still experiencing issues, please provide me with more information about your setup and the steps you have taken so far.
-
PRADEEPCHEEKATLA-MSFT 69,771 Reputation points Microsoft Employee
2023-11-27T09:05:46.0933333+00:00 @KumKum Rekhari - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sign in to comment