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

by

Troubleshooting Guide: SQL Server Error 450 — Code Page Translation Not Supported for Text Data Type

Why This Error Happens

This error occurs when SQL Server 2025 attempts to convert text data between two incompatible code pages, but the required code page translation table is missing, corrupted, or unsupported by the underlying collation. It commonly surfaces during cross-database queries, linked server operations, or BCP/BULK INSERT jobs where source and destination columns use mismatched collations tied to different code pages. Since the text data type is deprecated in favor of varchar(max), legacy code page mapping files bundled with older client drivers may no longer align with SQL Server 2025’s updated locale and collation engine.

Step-by-Step Resolution Guide

Step 1: Identify the Conflicting Code Pages

  • Note the exact %d to %d values reported in the error message — these correspond to Windows code page identifiers (e.g., 1252, 932, 65001).
  • Run the following query to check the collation of the affected column(s):
SELECT name, collation_name FROM sys.columns WHERE object_id = OBJECT_ID('YourTableName');
  • Cross-reference the collation with sys.fn_helpcollations() to confirm the associated code page.

Step 2: Migrate the Column Away from the Deprecated Text Type

  • Since text is deprecated, convert the column to varchar(max) or nvarchar(max), which handle Unicode natively and avoid code page translation entirely.
  • Run:
ALTER TABLE YourTableName ALTER COLUMN YourColumn VARCHAR(MAX);
  • If Unicode characters are involved, use NVARCHAR(MAX) instead to bypass code page dependency completely.

Step 3: Align Collations Across Source and Destination

  • If migration isn’t immediately possible, force matching collations on both sides of the operation (e.g., linked server, BCP file, or cross-database join):
ALTER TABLE YourTableName ALTER COLUMN YourColumn TEXT COLLATE Latin1_General_CI_AS;
  • For BCP/BULK INSERT operations, explicitly specify the code page in the command:
bcp YourTable in datafile.txt -c -C 1252 -S ServerName -T

Step 4: Update Client Drivers and Locale Files

  • On Windows Server 2025 / Windows 11, ensure the latest Microsoft OLE DB Driver for SQL Server and ODBC Driver 18+ are installed, as older drivers may reference outdated code page tables.
  • Check %SystemRoot%\System32\drivers\etc\ and regional settings under Control Panel > Region > Administrative > Language for non-Unicode programs to confirm the OS locale matches your SQL Server instance’s default code page.
  • Restart the SQL Server service after updating drivers or locale settings:
net stop MSSQLSERVER && net start MSSQLSERVER

Alternative or Verification Steps

  • Re-run the original query, import job, or linked server call that triggered Error 450 and confirm no code page warnings appear in the SQL Server error log (ERRORLOG in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\).
  • As a fallback, export the data using sqlcmd -f 65001 to force UTF-8 encoding, sidestepping legacy code page conversion issues entirely.