Troubleshooting Guide: SQL Server Error 4126 – “No full-text indexed columns were found”

Why This Error Happens

This error occurs when you attempt to create or alter a full-text index on a table where no columns have been designated as eligible for full-text indexing, typically due to unsupported data types (such as image, rowversion, or incompatible computed columns) or because all previously indexed columns were removed. It can also happen if the column list passed to CREATE FULLTEXT INDEX is empty or references columns that no longer exist in the schema. In some cases, corrupted metadata in the full-text catalog from an improper upgrade to SQL Server 2025 can cause the engine to lose track of valid column mappings.

Step-by-Step Resolution Guide

Step 1: Verify Column Data Types and Table Schema

• Run sp_help 'YourTableName' to inspect the data types of all columns.
• Confirm that at least one column uses a full-text-compatible type: char, varchar, nvarchar, text, ntext, xml, varbinary, or image (with a associated type column).
• Remove any references to deprecated or dropped columns from your index creation script.

Step 2: Rebuild the Full-Text Index Definition

• Drop the existing broken full-text index using:

  DROP FULLTEXT INDEX ON YourTableName;

• Recreate it explicitly, specifying valid columns and a unique key index:

  CREATE FULLTEXT INDEX ON YourTableName(ColumnName LANGUAGE 1033)
  KEY INDEX PK_YourTableName
  ON YourFullTextCatalog;

• Ensure PK_YourTableName references an existing unique, single-column, non-nullable index.

Step 3: Validate Full-Text Catalog Integrity

• Open SQL Server Management Studio (SSMS) and navigate to Database > Storage > Full Text Catalogs.
• Right-click the catalog and select Rebuild if metadata corruption is suspected.
• On Windows Server 2025, confirm the SQL Full-text Filter Daemon Launcher service is running via services.msc.

Step 4: Check for Column-Level Permissions and Filegroup Issues

• Verify the SQL Server service account has CONTROL permission on the target table.
• Confirm the filegroup hosting the full-text catalog is online and not set to read-only:

  SELECT name, is_read_only FROM sys.filegroups;

Alternative or Verification Steps

• After recreating the index, run SELECT * FROM sys.fulltext_index_columns WHERE object_id = OBJECT_ID('YourTableName'); to confirm columns are now registered.
• If the error persists, drop and recreate the entire full-text catalog, then reapply indexes one table at a time to isolate the problematic column or schema element.