Forum Discussion
Biren
Jan 06, 2025Copper Contributor
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 givi...
Nazeer
Jan 16, 2025Copper Contributor
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!