SQL Server: linked server MSDASQL queries with provider string fail with error 7416
Summary
Linked server queries that use the MSDASQL provider (OLE DB Provider for ODBC Drivers) and specify a provider string ([user]) fail with error 7416 for users who are not sysadmin. A stricter connection validation check in the Database Engine causes this. Microsoft confirms the issue and states it is addressed starting with the October 2026 GDR update.
Symptoms
Queries over such linked servers fail for users who are not members of the sysadmin fixed server role: 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.
Affected
- SQL Server 2025 CU and GDR updates since April 2026 (e.g. KB5128492, KB5126967)
- SQL Server 2022 CU and GDR updates since March 2026 (e.g. KB5128493, KB5104824, KB5126934)
- SQL Server 2019 CU and GDR updates since April 2026 (e.g. KB5128495, KB5128494)
- 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
Workaround
- If the configuration does not require the provider string ([user]), remove it from the linked server definition.
- Alternatively, add a User ID entry to the provider string ([user]), for example User ID=<value>. The provider string must still include UID.
- Granting sysadmin permissions to the affected user also avoids the failure, but Microsoft does not recommend it.
Fix
Addressed starting with the October 2026 GDR update. Workarounds already applied continue to be respected by the update.
Recommendation
Check whether linked servers use MSDASQL with a provider string. Apply the workaround where affected, or install the October 2026 GDR update after testing. Do not grant sysadmin rights as a workaround, and review access to MSDASQL linked servers using least privilege.
Sources
- SQL Server: Linked server queries that use MSDASQL fail with error 7416 (KB5128492, October 2026) Vendor · support.microsoft.com
- Troubleshoot MSDASQL linked server fails with error 7416 Vendor · learn.microsoft.com
Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 22:05.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.