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

by

Troubleshooting Guide: SQL Server Error 5841 – Unsupported Default Full-Text Language

Why This Error Happens

Error 5841 occurs when the Language ID (LCID) configured as the default full-text language — either at the server (sp_configure 'default full-text language') or instance level — does not correspond to a language actually registered with the Full-Text Search (FTS) component. This typically happens after a SQL Server upgrade/migration where a legacy LCID is no longer mapped, or when the Full-Text Search feature was installed without its complete set of wordbreaker/language resource files. It can also occur if the sys.fulltext_languages catalog is out of sync with the installed FTS binaries due to a corrupted or incomplete installation.

Step-by-Step Resolution Guide

Step 1: Identify the Currently Configured Language ID

  • Open SQL Server Management Studio (SSMS) and connect to the instance.
  • Run the following to check the current server-level default:
  EXEC sp_configure 'default full-text language';
  • Cross-reference the returned LCID against supported values:
  SELECT * FROM sys.fulltext_languages;
  • If the configured LCID does not appear in this list, that confirms the mismatch causing Error 5841.

Step 2: Reset the Default Full-Text Language to a Supported Value

  • Set the default full-text language to a known-good, universally supported LCID (e.g., 1033 for English – US):
  EXEC sp_configure 'show advanced options', 1;
  RECONFIGURE;
  EXEC sp_configure 'default full-text language', 1033;
  RECONFIGURE;
  • If the issue is scoped to a specific database or column, check and reset at that level too:
  EXEC sp_fulltext_database 'enable';
  • Validate any CREATE FULLTEXT INDEX or CREATE TABLE scripts referencing LANGUAGE arguments and update hardcoded LCIDs to supported ones.

Step 3: Repair or Reinstall the Full-Text Search Component

  • Open Control Panel > Programs > SQL Server 2025 Installation Center (or use Setup.exe from installation media).
  • Select Maintenance > Repair and choose the affected instance.
  • Ensure the Full-Text and Semantic Extractions for Search feature checkbox is selected during repair.
  • On Windows Server 2025 / Windows 11, confirm the following paths contain the expected language resource files post-repair:
  C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn\FTData\
  • Restart the SQL Server (MSSQLSERVER) and SQL Full-text Filter Daemon Launcher services via services.msc.

Step 4: Restart Services and Clear Cached Configuration

  • Restart the SQL Server instance to apply the RECONFIGURE changes:
  Restart-Service -Name 'MSSQLSERVER' -Force
  • Restart the SQL Server Full-text Filter Daemon Launcher service as well, since it caches language resource mappings:
  Restart-Service -Name 'MSSQLFDLauncher' -Force
  • Clear any stale Full-Text Catalog if corruption is suspected:
  ALTER FULLTEXT CATALOG ft_catalog REBUILD;

Alternative or Verification Steps

  • Confirm the fix by re-running EXEC sp_configure 'default full-text language'; and verifying the returned LCID matches an entry in sys.fulltext_languages, then attempt to create a test full-text index without errors.
  • If the error persists after repair, consider a clean uninstall/reinstall of the Full-Text and Semantic Extractions for Search feature via the SQL Server Installation Center, ensuring the installation media matches the exact build/version of SQL Server 2025 currently installed.