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

by

Troubleshooting Guide: Error 7603 – Inconsistent Accent Sensitivity in Full-Text Catalog

Why This Error Happens

This error occurs when the accent sensitivity setting (accent-sensitive vs. accent-insensitive) configured for a full-text catalog does not match the accent sensitivity of the underlying language collation used during indexing. This mismatch typically arises after a database restore from a server with different collation settings, an in-place upgrade to SQL Server 2025, or manual edits to catalog properties that were not propagated to all associated indexes. The result is a corrupted or inconsistent catalog state that SQL Server flags to prevent unreliable search results.

Step-by-Step Resolution Guide

Step 1: Identify the Affected Catalog and Collation Settings

  • Run the following query to identify the catalog ID referenced in the error:
SELECT fic.fulltext_catalog_id, fic.name, fic.is_accent_sensitivity_on
FROM sys.fulltext_catalogs fic;
  • Cross-reference the fulltext_catalog_id from the error message (Error 7603) with the output.
  • Check the collation of the associated table/column using SELECT DATABASEPROPERTYEX('YourDB', 'Collation');.

Step 2: Drop and Rebuild the Inconsistent Full-Text Catalog

  • Open SQL Server Management Studio (SSMS) 2025 or a new query window connected to the affected instance.
  • Drop the corrupted catalog using:
DROP FULLTEXT CATALOG YourCatalogName;
  • Recreate the catalog with explicit accent sensitivity matching your collation requirements:
CREATE FULLTEXT CATALOG YourCatalogName WITH ACCENT_SENSITIVITY = ON;
  • Re-associate the catalog with the relevant full-text indexes using CREATE FULLTEXT INDEX.

Step 3: Rebuild and Repopulate the Full-Text Index

  • Force a full repopulation to ensure all data is reindexed cleanly:
ALTER FULLTEXT INDEX ON YourSchema.YourTable START FULL POPULATION;
  • Monitor progress via sys.dm_fts_index_population to confirm the population status changes to “Idle” without errors.
  • Restart the SQL Server Full-Text Filter Daemon Launcher service via services.msc or PowerShell:
Restart-Service -Name "MSSQLFDLauncher"

Alternative or Verification Steps

  • Verify the fix by querying sys.fulltext_catalogs again to confirm is_accent_sensitivity_on matches your intended setting (0 or 1) for the specific catalog ID.
  • If the error persists after rebuilding, run DBCC CHECKDB on the database to rule out underlying corruption, then consider migrating the catalog to a new filegroup with matching collation settings from the start.