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

by

Troubleshooting Guide: Error 7664 – Full-Text Change Tracking Not Started

Why This Error Happens

This error occurs when SQL Server attempts to flush full-text change tracking data for a table or indexed view that does not have change tracking enabled or active. It typically happens when change tracking was manually disabled, paused, or never initialized before an automatic or manual flush operation was triggered. This can also occur after a database restore or attach operation where full-text catalog metadata becomes out of sync with the actual table configuration.

Step-by-Step Resolution Guide

Step 1: Verify Current Change Tracking Status

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Run the following query to check the change tracking state:
SELECT OBJECT_NAME(object_id) AS TableName, change_tracking_state_desc
FROM sys.fulltext_index_catalog_usages fc
JOIN sys.fulltext_indexes fi ON fc.object_id = fi.object_id;
  • Confirm whether the change_tracking_state_desc returns OFF or NULL for the affected table.

Step 2: Enable Change Tracking on the Table

  • Run the following T-SQL command to enable change tracking explicitly:
ALTER FULLTEXT INDEX ON [SchemaName].[TableName]
SET CHANGE_TRACKING AUTO;
  • Replace [SchemaName].[TableName] with the actual schema and table name referenced in the error message.
  • If the full-text index does not exist at all, recreate it using CREATE FULLTEXT INDEX ON before setting change tracking.

Step 3: Force a Full Population and Flush

  • Manually trigger a full population to rebuild the tracking metadata:
ALTER FULLTEXT INDEX ON [SchemaName].[TableName]
START FULL POPULATION;
  • After population completes, manually flush the tracked changes:
ALTER FULLTEXT INDEX ON [SchemaName].[TableName]
START CHANGE_TRACKING UPDATE INDEX;

Step 4: Restart the Full-Text Filter Daemon Launcher Service

  • Open Services.msc on Windows Server 2025 / Windows 11.
  • Locate SQL Full-text Filter Daemon Launcher (MSSQLSERVER) (or the named instance equivalent).
  • Right-click and select Restart to clear any stuck background processes tied to full-text indexing.

Step 5: Rebuild the Full-Text Catalog (If Error Persists)

  • If the table still throws Error 7664, drop and recreate the full-text catalog:
DROP FULLTEXT INDEX ON [SchemaName].[TableName];
DROP FULLTEXT CATALOG [CatalogName];

CREATE FULLTEXT CATALOG [CatalogName] AS DEFAULT;
CREATE FULLTEXT INDEX ON [SchemaName].[TableName] (ColumnName)
KEY INDEX [PK_IndexName]
WITH CHANGE_TRACKING AUTO;
  • This resets all metadata associations and forces SQL Server to reinitialize tracking from scratch.

Alternative or Verification Steps

  • Verify the fix by querying sys.fulltext_indexes and confirming change_tracking_state_desc returns AUTO instead of OFF or NULL.
  • If the error persists after rebuilding the catalog, check the SQL Server error log for correlating full-text crawl failures and ensure the service account running SQL Server has read/write permissions on the full-text catalog file directory.