Share via

Error: (3805)

SM 5 Reputation points
2024-01-17T00:03:15.5433333+00:00

Hi,

We are trying to run a snowflake scan in Purview and getting the below error: "Error: (3805) Connector Exception: Metadata Table 'INFORMATION_SCHEMA.DATABASES' is not accessible. Please verify 'SELECT' permissions." Its a scheduled scan and was working fine every week until Jan 5th 2024. As per snowflake admin, all the required permissions are in place and nothing changed since Jan 5th.

Any help is appreciated.

Regards, Sorabh

Microsoft Security | Microsoft Purview

3 answers

Sort by: Most helpful
  1. SM 5 Reputation points
    2024-01-30T18:36:14.9366667+00:00

    @PRADEEPCHEEKATLA @VISHAL SHARMA - yes, the issue got sorted on its own. Wierd!

    Was this answer helpful?


  2. Debarchan Sarkar - MSFT 1,131 Reputation points Microsoft Employee
    2024-01-26T05:18:59.5833333+00:00

    That's great to hear! Sometimes transient issues can occur with cloud services, which might resolve on their own after a short period. It's possible that was the case here. However, it's still important to monitor the situation moving forward. If the issue recurs, it could indicate a more persistent problem that needs in-depth investigation. Don't hesitate to reach out if you have any further questions or concerns about Microsoft Purview or any other topic. Here are some potential next steps you might consider: Review the results of the successful scan in Purview Studio. Consider setting up alerts or notifications for scan failures to stay informed about similar issues in the future. Explore advanced features of Purview such as data classification, labeling, and cataloging. Look into best practices for configuring and managing your Purview account.

    Remember, continuous monitoring and proactive management can help ensure the smooth operation of your data governance efforts with Microsoft Purview.

    Was this answer helpful?


  3. Ortiz Ocio Leire TEF-D 20 Reputation points
    2024-01-18T11:50:42.4466667+00:00

    We have the same problem, and honestly I discard any issue with the configuration on our side as we are Re-running scans that previously (on 02 January 2024) were working properly.

    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.