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

by

Troubleshooting Guide: Error 7692 – Full-Text Catalog Path Exceeds Character Limit

Why This Error Happens

This error occurs when the full path of a full-text catalog—including the drive letter, directory structure, and catalog name—exceeds the maximum character limit enforced by SQL Server 2025 (typically 260 characters, tied to legacy Windows MAX_PATH constraints unless long path support is explicitly configured). This commonly happens when databases are nested deeply within folder hierarchies, when instance names or database names are unusually long, or when default data directories were changed to a deeply nested path during installation. SQL Server validates this path length internally and rejects the CREATE FULLTEXT CATALOG or CREATE FULLTEXT INDEX statement before any file system operation occurs.

Step-by-Step Resolution Guide

Step 1: Identify the Full Resolved Path

  • Run the following to check the current default full-text catalog directory:
  EXEC xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer', N'DefaultFullTextDirectory';
  • Combine this with your intended catalog name and database path to calculate total character length.
  • Confirm the exact failing path reported in the error message (SQL Server logs the offending string via %.*ls).

Step 2: Shorten the Catalog or Directory Path

  • Move the data/catalog storage location to a shorter root path, such as D:\FTCat\ instead of D:\SQLData\Instances\MSSQL2025\MSSQL\FTData\LongProjectName\.
  • Rename the full-text catalog to a shorter, non-descriptive identifier (e.g., FTC1 instead of FullTextCatalog_ProductionOrders_2025).
  • Use ALTER DATABASE [YourDB] MODIFY FILE or relocate via sp_fulltext_catalog only after shortening the target directory structure.

Step 3: Enable Windows Long Path Support (If Applicable)

  • On Windows Server 2025 / Windows 11, open Local Group Policy Editor (gpedit.msc).
  • Navigate to Computer Configuration > Administrative Templates > System > Filesystem.
  • Enable “Enable Win32 long paths”.
  • Restart the SQL Server service for the policy to take effect:
  Restart-Service -Name 'MSSQLSERVER'
  • Note: This only extends OS-level path handling; SQL Server’s internal 260-character validation for full-text catalogs may still apply depending on build/version, so Step 2 remains the primary fix.

Step 4: Recreate the Full-Text Catalog

  • Drop the failed catalog object if it was partially created:
  DROP FULLTEXT CATALOG [FTC1];
  • Recreate it using the shortened path:
  CREATE FULLTEXT CATALOG [FTC1] IN PATH 'D:\FTCat';
  • Rebuild any dependent full-text indexes afterward.

Alternative or Verification Steps

  • Verify the fix by querying sys.fulltext_catalogs to confirm the catalog was created successfully and check its path column for the shortened value.
  • If renaming/shortening isn’t feasible due to naming conventions, mount a shorter-named volume or use a symbolic link (mklink /D) pointing to the deep directory structure to reduce the effective path length SQL Server sees.