Microsoft KB Archive/304282

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

Article ID: 304282

Article Last Modified on 10/11/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Developer Edition

-



This article was previously published under Q304282



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 &quot;Full Text&quot; 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.



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 &quot;Symptoms&quot; 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.



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 &quot;Cause&quot; section have Full Control over the HKLM\Software\Microsoft\Search\1.0 registry key and all it's child keys.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.



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.

Additional query words: full text search cluster gatherprm.txt 80070002

Keywords: kbprb KB304282

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.