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

by

Troubleshooting Guide: Error 9914 – Failed to Resume Full-Text Population in SQL Server 2025

Why This Error Happens

Error 9914 typically occurs when SQL Server attempts to resume a paused or interrupted full-text index population but cannot access the underlying full-text catalog files or metadata. This is often caused by corrupted full-text catalog files, insufficient permissions for the SQL Server service account on the catalog directory, or an inconsistent internal state left behind after an unexpected server shutdown or failed crawl. In some cases, this error also surfaces when the associated table or indexed view schema has changed while a population was still marked as active in the system metadata.

Step-by-Step Resolution Guide

Step 1: Verify Full-Text Catalog and Service Account Permissions

  • Open SQL Server Configuration Manager and confirm the SQL Server service account has Full Control on the full-text catalog folder (typically under C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\FTData).
  • Right-click the folder, go to Properties > Security, and add the service account if missing.
  • Restart the SQL Server service after applying permission changes.

Step 2: Check the Status of the Full-Text Index

  • Run the following query to inspect the current population status:
SELECT * FROM sys.dm_fts_index_population WHERE database_id = DB_ID('YourDatabaseName');
  • If the status shows as “paused” or “throttled” unexpectedly, this confirms a stuck population state.
  • Cross-reference the table/indexed view ID from the error message using:
SELECT OBJECT_NAME(object_id) FROM sys.tables WHERE object_id = <table_or_indexed_view_ID>;

Step 3: Rebuild the Full-Text Catalog

  • Disable and re-enable full-text indexing on the affected table to clear any corrupted internal state:
ALTER FULLTEXT INDEX ON YourTableName DISABLE;
ALTER FULLTEXT INDEX ON YourTableName ENABLE;
  • If the issue persists, drop and recreate the full-text catalog entirely:
DROP FULLTEXT INDEX ON YourTableName;
DROP FULLTEXT CATALOG YourCatalogName;
CREATE FULLTEXT CATALOG YourCatalogName;
CREATE FULLTEXT INDEX ON YourTableName(...) KEY INDEX YourPrimaryKeyIndex;

Step 4: Restart the Full-Text Population Manually

  • Force a full population restart using:
ALTER FULLTEXT INDEX ON YourTableName START FULL POPULATION;
  • Monitor progress via SQL Server Management Studio under Database > Storage > Full Text Catalogs.

Step 5: Check Windows Event Viewer and SQL Server Error Logs

  • Open Event Viewer on Windows Server 2025 / Windows 11 and navigate to Applications and Services Logs > MSSQLSERVER.
  • Look for related I/O errors, disk corruption warnings, or access denial events around the same timestamp as Error 9914.

Alternative or Verification Steps

  • After applying fixes, re-run the sys.dm_fts_index_population query to confirm the status changes to “idle” or “completed” rather than “error” or “paused.”
  • If the error persists after rebuilding the catalog, consider restoring the database from a known good backup, as this may indicate deeper corruption in the database’s full-text metadata structures.