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

by

Troubleshooting Guide: SQL Server Error 9942 – Full-Text Population Informational Message

Why This Error Happens

Error 9942 is actually an informational message, not a critical failure—it is logged by SQL Server whenever a full-text population (crawl) starts or completes for a given table or indexed view. This message typically appears in the SQL Server Error Log because the Full-Text Engine (FTE) is reporting status on a scheduled, incremental, or manual population request. In most cases, it signals normal operation, but if it appears excessively or is paired with population failures, it usually points to underlying issues such as a corrupted full-text catalog, insufficient permissions on the full-text index filegroup, or resource contention during large-scale crawls.

Step-by-Step Resolution Guide

Step 1: Confirm the Message is Informational, Not an Error

  • Open SQL Server Management Studio (SSMS) and navigate to Management > SQL Server Logs.
  • Filter the log for Event ID 9942 and review the accompanying text (e.g., “population for table or indexed view… has completed/started”).
  • Confirm there are no accompanying error-level messages (Severity 16+) immediately before or after it.

Step 2: Verify Full-Text Catalog and Index Health

  • Run the following query to check catalog status:
  SELECT * FROM sys.fulltext_catalogs;
  SELECT * FROM sys.dm_fts_index_population;
  • If a catalog shows a status other than “Idle” or “Online” for an extended period, rebuild it:
  ALTER FULLTEXT CATALOG [YourCatalogName] REBUILD;
  • Check the physical catalog files under C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\FTData\ for corruption or unexpected size discrepancies.

Step 3: Validate Service Account Permissions

  • Open Services.msc on Windows Server 2025 / Windows 11 and locate the SQL Server (MSSQLSERVER) and SQL Full-text Filter Daemon Launcher services.
  • Ensure the service account has Read/Write access to the FTData directory and the database files directory.
  • Restart both services after any permission changes:
  Restart-Service -Name 'MSSQLSERVER'
  Restart-Service -Name 'MSSQLFDLauncher'

Step 4: Manually Repopulate the Full-Text Index

  • If the informational messages indicate a stalled or repeating crawl, force a full repopulation:
  ALTER FULLTEXT INDEX ON [YourSchema].[YourTable] START FULL POPULATION;
  • Monitor progress via sys.dm_fts_index_population until the status_description returns to Idle.

Step 5: Review Resource Allocation for Large Crawls

  • Check Task Manager > Performance tab on Windows Server 2025 for CPU/Memory pressure during the crawl window.
  • If the server is resource-constrained, adjust the maxfulltextcrawl_range configuration value or schedule population during off-peak hours using SQL Server Agent.

Alternative or Verification Steps

  • Re-run SELECT * FROM sys.dm_fts_index_population; and confirm the row for the affected table disappears (indicating population completed) or shows status = 0 (idle).
  • If messages persist excessively, drop and recreate the full-text index as a last resort: DROP FULLTEXT INDEX ON [YourTable]; followed by CREATE FULLTEXT INDEX ON [YourTable](...) KEY INDEX [YourPK] ON [YourCatalog];