Forum Discussion

Biren's avatar
Biren
Copper Contributor
Jan 06, 2025

Error 3892

Had anyone encountered Error 3892. The test connection to SQL server is successful via integration runtime and I can see tables and views to scan. However, when trying to scan, it is failing and giving me following error.

Error: (3892) Failed to connect to Microsoft Purview managed resources. Please check your network settings and make sure the integration runtime you use for scan can access it.

Please can someone have idea about what to do or how to check scan access to IR?

Thanks

4 Replies

  • Biren's avatar
    Biren
    Copper Contributor
    Jan 17, 2025

    Hi Nazeer, 

    Thanks for your insights! IR was set up with both keys and connection to SQL server was also established.  We found that there was some dns resolution issue while we kick off scans. After solving this issue we can scan tables now. 

     

    • ArnoudW's avatar
      ArnoudW
      Copper Contributor
      Mar 25, 2025

      Hi Biren,

       

      I'm currently working on trying to set up a scan to a SQL Server via an SH Integration Runtime, and during this process we seem to be running into a similar issue as you were. Could you please elaborate on the 'DNS Resolution' and how you managed to resolve it?

      Within Purview we are able to connect to the SQL server when testing the connection in the set-up scan menu, and when selecting a specific database, we are able to see all assets on that database.

       

      Kind regards,

       

      Arnoud

      • Biren's avatar
        Biren
        Copper Contributor
        Mar 26, 2025

        Hi Arnoud

        First check if private endpoint is enabled to SQL server or not? also if SH runtime (is it on VM ?) is able success the DNS CNAME looks (FQDNs)? It requires to succeed the DNS CNAME lookup of both storage FQDN and storage private link FQDN.

        Best luck

        Biren

  • Nazeer's avatar
    Nazeer
    Copper Contributor
    Jan 16, 2025

    Hi Biren 

    We've encountered the same issue. This must be an on-premise SQL Server that you are trying to scan natively, which is supported. The error you are getting is because the data source that your IR is set to is not authorized with one of the two keys generated when you set up a scan to that data source.

    Observe that there must have been two hidden keys generated when you click on scan. So copy any one of the two keys and setup your Integration Runtime with that copied key on the SQL Server VM.

    If your IR was already set with some different key, and one which is not in use, you can uninstall it and install it again to set it up with a different key. As far as I know there is no other way to get your IR authorized.

    Hope this helps!