Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to:
- SQL Server 2025 CU and GDR updates since April 2026
- SQL Server 2022 CU and GDR updates since March 2026
- SQL Server 2019 CU and GDR updates since April 2026
- SQL Server 2017 CU and GDR updates since April 2026
- SQL Server 2016 SP3 and Azure Connect Pack GDR updates since April 2026
- Azure SQL Managed Instance
Summary
This article describes a known issue in which linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string fail and generate error 7416. The article also provides workarounds that restore linked server connectivity without rolling back the update.
Symptoms
Linked server queries that use the MSDASQL provider and specify a provider string (@provstr) fail and return the following error message when a user that isn't a member of the sysadmin fixed server role runs the query:
Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.
The failure can occur even if the linked server and login mappings are configured correctly.
Cause
A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.
Workaround
To work around this issue without rolling back the update, use one of the following methods:
- If your configuration doesn't require the provider string (
@provstr), remove it from the linked server definition. - Add a
User IDentry to the provider string (@provstr). For example, setUser ID=<value>. The provider string must still includeUIDas well.
You can also prevent the failure by granting sysadmin permissions to the affected user. However, we don't recommend that you use this method.