How to fix Error 7369 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: Error 7369 – Invalid Collation from OLE DB Provider

Why This Error Happens

This error occurs when the OLE DB provider for a linked server returns a Locale Identifier (LCID) that SQL Server 2025 does not recognize or cannot map to a valid collation. This typically happens due to a mismatch between the collation settings of the remote data source and the local SQL Server instance, outdated or corrupted OLE DB provider drivers, or misconfigured provider options that fail to pass proper locale information. It can also surface after an OS or SQL Server upgrade where legacy provider versions are incompatible with newer collation handling in Windows Server 2025.

Step-by-Step Resolution Guide

Step 1: Verify and Update the OLE DB Provider

  • Confirm which provider is being used (e.g., MSOLEDBSQL, MSDASQL, or a third-party provider) by checking the linked server properties in SQL Server Management Studio (SSMS).
  • Download and install the latest version of the Microsoft OLE DB Driver for SQL Server from the official Microsoft site.
  • Restart the SQL Server service after installation to ensure the updated driver is loaded.

Step 2: Check and Align Collation Settings

  • Run SELECT SERVERPROPERTY('Collation'); on both the local and remote servers to compare collation settings.
  • If mismatched, reconfigure the linked server to explicitly map collations using sp_addlinkedserver with the @collation parameter set correctly.
  • Ensure both servers use compatible regional/locale settings in Windows Server 2025 under Control Panel > Region > Administrative > Language for non-Unicode programs.

Step 3: Adjust Linked Server Provider Options

  • Open SSMS, navigate to Server Objects > Linked Servers > [Your Linked Server] > Properties.
  • Under “Provider Options,” enable “Use Remote Collation” and manually specify the correct collation name if auto-detection is failing.
  • Disable “Nested Queries” temporarily if the provider has known compatibility issues with complex query structures.

Step 4: Rebuild the Linked Server Configuration

  • Drop the existing linked server using EXEC sp_dropserver 'LinkedServerName', 'droplogins';.
  • Recreate it using sp_addlinkedserver, explicitly defining the @provider, @datasrc, and @provstr parameters with correct values.
  • Test connectivity immediately using EXEC sp_testlinkedserver 'LinkedServerName';.

Alternative or Verification Steps

  • Run a simple test query like SELECT * FROM OPENQUERY(LinkedServerName, 'SELECT 1'); to confirm the connection no longer throws Error 7369.
  • If the issue persists, switch to a different OLE DB provider (e.g., moving from MSDASQL to MSOLEDBSQL) or use a LINKED SERVER via ODBC instead, as some legacy providers are deprecated and unsupported on Windows Server 2025.