Microsoft has documented a SQL Server issue where linked server queries that use the MSDASQL provider and include a provider string (@provstr) can fail with:
Msg 7416, Level 16 Access to the remote server is denied because no login-mapping exists.
According to the documentation, a stricter connection validation check in the Database Engine can reject certain linked server configurations that use MSDASQL, even if earlier builds allowed those connections.
Affected releases
The issue is listed for these SQL Server releases and updates:
- SQL Server 2025 CU6 + GDR (build 17.0.4060.2)
- SQL Server 2025 CU5 (build 17.0.4045.5)
- SQL Server 2025 CU4 + GDR (build 17.0.4040.1)
- SQL Server 2025 CU4 (build 17.0.4035.5)
- SQL Server 2025 CU3 + GDR (build 17.0.4030.1)
- SQL Server 2022 CU26 (build 16.0.4265.3)
- SQL Server 2022 CU25 + GDR (build 16.0.4262.2)
- SQL Server 2022 CU25 (build 16.0.4255.1)
- SQL Server 2022 CU24 + GDR (build 16.0.4252.3)
- SQL Server 2022 CU24 (build 16.0.4245.2)
- SQL Server 2019 CU32 + GDR (build 15.0.4480.2)
- SQL Server 2019 CU32 + GDR (build 15.0.4470.1)
- SQL Server 2022 CU24 + GDR (build 16.0.4250.1)
- SQL Server 2025 CU4 + GDR (build 17.0.4040.1)
- SQL Server 2025 CU5 (build 17.0.4045.5)
Example scenario
This documented pattern can occur when a linked server is configured to use MSDASQL and the connection includes a provider string via @provstr. In that case, SQL Server may return Msg 7416 instead of completing the linked server query.
The packet does not include a supported workaround or fix details, so this note is limited to the documented failure condition and affected builds.