Forum Discussion
Error 3892
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.
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
- BirenMar 26, 2025Copper Contributor
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