Error message when you use the Cluster Administrator to bring the SQL Server full-text search resource online: "SQL Cluster Resource 'Full Text' failed"

View products that this article applies to.

This article was previously published under Q304282

Expand all | Collapse all

SYMPTOMS

The SQL Full Text Search Resource may fail to come online through the Cluster Administrator and the following error message may be reported in the Microsoft Windows NT system event logs:

Event ID:1069
Source:Clussvc
Description: SQL Cluster Resource "Full Text" failed.

In the Windows NT application log, the following error messages may appear:

Warning: 6/18/2001 10:14:25 PM 2 3 3055 Microsoft Search N/A VIRTUALSQL1 The Gatherer property mapping file cannot be opened.
Error: 80070002. The default values are being used. You may have to copy the property mapping file from the setup CD, or reinstall the application.

Error: 6/18/2001 10:14:25 PM 1 3 3058 Microsoft Search N/A VIRTUALSQL1 The application [SQLServer] cannot be initialized.
Error: 80070002 - The system cannot find the file specified.

Back to the top

CAUSE

When the SQL Full Text resource is brought online through Cluster Administrator, it looks for configuration files present in the MSSQL\FTData (or MSSQL$INSTANCENAME\FTDATA) folder (named clus0.0, clus1.1 and so on). The configuration files contain crucial information about the Full Text application path, catalog paths, index paths and so forth. If the configuration files are corrupt or the account that is performing the failover does not have Full control over the FTData folder, the errors listed in the "Symptoms" section may display. The following actions may cause the error message to occur:

Removing or renaming the contents of the FTDATA folder.
Copying the FTData folder from a different server onto the clustered server.
Insufficient permissions for the Cluster Service startup account to the FTData folder and all it's subfolders.
Insufficient permissions for the Cluster Service and SQL Service startup accounts to the HKLM\Software\Microsoft\Search\1.0 registry key and all the subkeys present under the HKLM\Software\Microsoft\Search\1.0 registry key.
The Cluster service and SQL Service accounts do not have full control over the previously-mentioned registry keys and FTDATA folder.

The Cluster Service and SQL Service accounts need full control over the previously mentioned registry keys and FTData folder.

Back to the top

WORKAROUND

To work around this behavior either:

Make sure that the Cluster Service, the SQL Service and the SYSTEM account have full control over the MSSQL\FTdata folder and all its subfolders.
Make sure that the accounts mentioned in step 5 of the "Cause" section have Full Control over the HKLM\Software\Microsoft\Search\1.0 registry key and all it's child keys.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Back to the top

MORE INFORMATION

If the files in the FTDATA folder are replaced, corrupted, or deleted, or if the FTDATA folder itself is deleted, the SQL Server Fulltext cluster resource may have to be rebuilt to be restored to a stable state. The only supported method to rebuild the SQL Server Fulltext cluster resource is to completely remove and reinstall the SQL Server failover cluster instance.

For more information about how to remove a failover cluster instance, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/aa216166(sql.80).aspx (http://msdn2.microsoft.com/en-us/library/aa216166(sql.80).aspx)

For more information about how to create a new failover cluster instance, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa216056(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa216056(SQL.80).aspx)

Back to the top