Failed to scan Snowflake source

Pehrsson, Andreas 65 Reputation points
2023-10-20T06:06:06.67+00:00

Hi,

We are trying to run a scan on a registered Snowflake source but get the error:

Error: (3805) Connector Exception: Connection to the database (with URL jdbc:snowflake://xxxxxx.snowflakecomputing.com?db=%22xxxx%22&warehouse=purview_wh&application=Microsoft_Purview) failed: JDBC driver encountered communication error. Message: HTTP status=403

Added x to snowflake url and database name.

The key vault has been added as credential following these instructions https://learn.microsoft.com/en-us/purview/manage-credentials#grant-the-purview-managed-identity-access-to-your-azure-key-vault

What could be the reason for the error?

Thank you

Microsoft Purview
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.
1,518 questions
{count} votes

Accepted answer
  1. KranthiPakala-MSFT 46,627 Reputation points Microsoft Employee
    2023-10-20T18:23:32.02+00:00

    Update: 10/24/2023:
    @Pehrsson, Andreas I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

    Error Message:

    • Error: (3805) Connector Exception: Connection to the database (with URL jdbc:snowflake://xxxxxx.snowflakecomputing.com?db=%22xxxx%22&warehouse=purview_wh&application=Microsoft_Purview) failed: JDBC driver encountered communication error. Message: HTTP status=403

    Solution:

    • The issue was due to improper Key vault configuration. Reconfiguring key vault correctly resolved the connection issue.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    I hope this helps!

    Update 10/20/2023:
    @Pehrsson, Andreas Welcome to Microsoft Q&A forum and thanks for reaching out here.

    As per your latest error message I suspect something wrong with your Scan credential's configuration or the keyValut configuration.

    Kindly revalidate below troubleshooting steps and if the issue persists, I recommend filing a support ticket for deeper investigation as we need to go through step by step to identify the exact root cause of the issue.

    User's image

    Hope this helps.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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