Microsoft KB Archive/812666

= How to recover a failed full-text search resource on a clustered instance of SQL Server 2000 =

PSS ID Number: 812666

Article Last Modified on 4/13/2005

-

The information in this article applies to:


 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Enterprise Evaluation Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

IN THIS TASK

 * SUMMARY
 * Remove the failed full-text search resource
 * Identify the required resources
 * Reinstall the full-text search service
 * Re-create the full-text search resource
 * REFERENCES



SUMMARY
This article describes how to recover a full-text search resource that has failed on a clustered instance of Microsoft SQL Server 2000. To recover the full-text search resource, you must remove it and then re-create it. You must also reinstall the full-text search service on the clustered instance of SQL Server without affecting the instance of SQL Server.

back to the top

Remove the failed full-text search resource
To remove the failed full-text search resource from your clustered instance of SQL Server, follow these steps:  Start Cluster Administrator on the node that has the failed full-text search resource. Use Cluster Administrator to locate and delete the failed full-text search resource. Delete the registry keys that are related to the instance of SQL Server where the full-text search will be reinstalled. To do so, follow these steps.

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.  Click Start, and then click Run. In the Run dialog box, type regedit in the Open box, and then click OK. In Registry Editor, locate and then click the following registry key:

 In the right pane, delete the registry values that have the same name as your instance of SQL Server. For a default instance of SQL Server, the registry value is named SQLServer. For a named instance of SQL Server, the registry value is named SQLServer$ .</li></ol> </li></ol>

back to the top

Identify the required resources
To recover the full-text search service on the clustered instance of SQL Server, you must identify the following resources:
 * Identify the method that you used to install SQL Server. You must have access to the SQL Server setup files to install the full-text search service. Therefore, if you installed SQL Server on your computer by using the CD-ROM, make sure that the CD-ROM is available.

back to the top

Reinstall the full-text search service
To reinstall the full-text search service, follow these steps:
 * 1) Use the Searchstp.exe program to install the full-text search service. If the full-text search service is not installed on the computer, the Searchstp.exe program will create it.
 * 2) Use the Ftsetup.exe program to configure the full-text search service and to configure the instance of SQL Server as an application that uses the full-text search service. On SQL Server clusters, the Ftsetup.exe program also creates the required configuration files to maintain the failover properties for the full-text search resource. The Ftsetup.exe program uses the following parameter options:
 * 3) * ApplicationName: For a default instance of SQL Server, the parameter value must be SQLServer. For a named instance of SQL Server, the parameter value must be SQLServer\.
 * 4) * User: For a local system account, the parameter value must be 0. For a domain user account, the value of the parameter must be \.
 * 5) * IsMasterNode: This parameter indicates whether the Ftsetup.exe program runs on the node that owns the disk where the FTDATA folder will be created. The parameter value must be 0 or 1.
 * 6) * IsUpgrade: This parameter indicates whether the FtSetup.exe program is upgrading the full-text search service to a later version. This parameter value must be 0 or 1.
 * 7) * IsCluster: This parameter indicates whether the Ftsetup.exe program runs on a clustered instance of SQL Server. For a stand-alone instance of SQL Server, the parameter value must be 0. For a clustered instance of SQL Server, the parameter value must be 1.
 * 8) * IsUninstall: This parameter indicates whether the Ftsetup.exe program removes the full-text search service. If the Ftsetup.exe program installs the full-text search service, the parameter value must be 0. If the Ftsetup.exe program removes the full-text search service, the parameter value must be 1. However, if the parameter value is 1, the values for the IsMasterNode parameter, the IsUpgrade parameter, and the IsCluster parameter must all be set to 0.

back to the topback to the top

Re-create the full-text search resource
To re-create the full-text search resource on your clustered instance of SQL Server, follow these steps.

On the node of the SQL Server cluster that owns the disks and the resource groups
<ol> In Cluster Administrator, bring the SQL Server resource online.</li> Create a command file named Installsearch.cmd to run on the node of the SQL Server cluster that owns the disks and the resource groups. To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, and then click Run.</li> In the Run dialog box, type notepad.exe in the Open box, and then click OK.</li>  Add the following commands to the text file (where  is the path of the setup files that were used to install the instance of SQL Server): &quot;Full path of SQL Server Setup files\x86\FullText\MSSearch\Search\SearchStp.exe&quot; /s /a:SQLServer[$Instance name]

&quot;Full path of SQL Server Setup\x86\FullText\ftsetup.exe&quot; SQLServer[$Instance name] Domain name\User account 1 0 1 0 Note For a default instance of SQL Server, remove [$ ]. For a named instance of SQL Server, replace [$ ] with the name of the instance of SQL Server. </li> Save the file as installsearch.cmd .</li></ol> </li>  At a command prompt, run the following command: Full path of the Installsearch.cmd file > installsearch.out Note After you run the command, you must wait for the disk activities and the network activities to stop. If the command runs successfully, a subfolder named SQLServer$ is created in the FTDATA folder on the shared drive. </li> Use Cluster Administrator to create the full-text search resource. To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> Start Cluster Administrator on the node where the virtual server group is located.</li> On the File menu, point to New, and then click Resource.</li> In the New Resource dialog box, add a new resource with the following properties: <ul> Set the value of the Name property to Full-text search.</li> Leave the value of the Description property blank.</li> Set the value of the Resource Type property to Microsoft Search Service Instance.</li> Set the value of the Group property to .</li></ul> </li> Click Next.</li> <li>On the Possible Owners page, click the appropriate nodes, and then click Next.</li> <li>On the Dependencies page, move the SQL Server resource from the Available Resources list to the Resource Dependencies list.</li> <li>Click Finish.</li> <li>Right-click the full-text search resource, and then click Properties.</li> <li>In the Full-Text Search Properties dialog box, click the Advanced tab.</li> <li>Under Restart, click to clear the Affect the group check box.</li> <li>Click Apply, and then click OK.</li></ol> </li> <li>Create registry values named ApplicationName and ApplicationPath for the full-text search resource that you created in step 4. To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type regedit, and then click OK.</li> <li>In Registry Editor, locate the registry key for the full-text search resource. To do so, view the Name value for each resource under the following registry key:

Note Registry keys that correspond to all cluster resources are identified by their GUIDs.</li> <li>Expand the registry key for the full-text search resource, and then click the Parameters registry key.</li> <li>Use the following information to add a registry value to the  registry key for the full-text search resource: <ul> <li>Name: ApplicationName</li> <li>Type: REG_SZ</li> <li>Value: For a named instance of SQL Server, the value is SQLServer$ (where   is the name of the instance of SQL Server that is being used.) For a default instance of SQL Server, the value is SQLServer.</li></ul> </li> <li>Use the following information to add a registry value to the  registry key for the full-text search resource: <ul> <li>Name: ApplicationPath</li> <li>Type: REG_SZ</li> <li>Value: The full path of the folder that contains the full-text data files. For a named instance of SQL Server, the value ends in MSSQL$ \FTDATA. For a default instance of SQL Server, the value ends in MSSQL\FTDATA.</li></ul> </li></ol> </li> <li>Use Cluster Administrator to bring the full-text search resource online.

Note If the cluster resource successfully comes online, a file that is named Clust*.* is created in the FTDATA folder.</li></ol>

On the node of the SQL Server cluster that does not own the disks and the resource groups
<ol> <li>Use Cluster Administrator to take the full-text search resource offline. Do not move the group to the other node, because that would change the parameters that have to be passed in the following steps.</li> <li>Create a file named Installsearch.cmd for the node of the SQL Server cluster that does not own the resource groups. To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type notepad.exe in the Open box, and then click OK.</li> <li> Add the following commands to the text file (where  is the path of the setup files that were used to install the instance of SQL Server): &quot;Full path of SQL Server Setup files\x86\FullText\MSSearch\Search\SearchStp.exe&quot; /s /a:SQLServer[$Instance name]

&quot;Full path of SQL Server Setup files\x86\FullText\ftsetup.exe&quot; SQLServer[$Instance name] Domain name\User account 0 0 1 0 Note For a default instance of SQL Server, remove [$ ]. For a named instance of SQL Server, replace [$ ] with the name of the instance of SQL Server. </li> <li>Save the file as installsearch.cmd .</li></ol> </li> <li> At a command prompt, run the following command: Full path of the Installsearch.cmd file > installsearch.out Note After you run the command, you have to wait for the disk activities and the network activities to stop. </li> <li>Create registry values named ApplicationName and ApplicationPath for the full-text search resource. To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type regedit, and then click OK.</li> <li>In Registry Editor, locate the registry key for the full-text search resource. To do so, view the Name value for each resource under the following registry key:

Note Registry keys that correspond to all cluster resources are identified by their GUIDs.</li> <li>Expand the registry key for the full-text search resource, and then click the Parameters registry key.</li> <li>Use the following information to add a registry value to the  registry key for the full-text search resource: <ul> <li>Name: ApplicationName</li> <li>Type: REG_SZ</li> <li>Value: For a named instance of SQL Server, the value is SQLServer$ (where   is the name of the instance of SQL Server that is being used.) For a default instance of SQL Server, the value is SQLServer.</li></ul> </li> <li>Use the following information to add a registry value to the  registry key for the full-text search resource: <ul> <li>Name: ApplicationPath</li> <li>Type: REG_SZ</li> <li>Value: The full path of the folder that contains the full-text data files. For a named instance of SQL Server, the value ends in MSSQL$ \FTDATA. For a default instance of SQL Server, the value ends in \MSSQL\FTDATA.</li></ul> </li></ol> </li> <li>Use Cluster Administrator to bring the full-text search resource online.</li></ol>

Other considerations
If the latest SQL Server service pack is installed on the clustered instances of SQL Server, follow these steps to upgrade the full-text search service to the latest service pack level on the nodes in the SQL Server cluster: <ol> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type notepad.exe, and then click OK.</li> <li> Add the following command to the text file: Full path of SQL Server service pack Setup files\x86\FullText\MSSearch\Search\SearchStp.exe /s /a:SQLServer$Instance name </li> <li>Save the file as installsearch_SP.cmd .</li> <li>Use Cluster Administrator to take the full-text search resource offline.</li> <li> At a command prompt on the node that owns the SQL Server resources, run the following command: Full path of the Installsearch_SP.cmd file > installsearch_SP.out Note When the installsearch_SP.cmd command is complete, open the Installsearch_SP.out file and make sure that there are no errors in the file. </li> <li>Use Cluster Administrator to take the full-text search resource offline, move the virtual server group to the each node that is participating in the cluster, and then repeat steps 1 through 7 on the computer that owns the clustered resources.</li> <li>Use Cluster Administrator to bring the full-text search resource online.</li></ol>

back to the top

<div class="references_section">