Microsoft KB Archive/282122

= XADM: Server Cannot Bring the Microsoft Search Resource Online =

Article ID: 282122

Article Last Modified on 11/23/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q282122



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



For a Microsoft Exchange Server 2003 version of this article, see 830189.



SYMPTOMS
On an Exchange 2000 Server computer in a clustered environment, you may experience the following symptoms:  You receive an error message that indicates that the server cannot bring the Microsoft Search (MSSearch) resource online. The MSSearch resource instance appears as Failed in the Cluster Administrator utility.  An event with a description similar to the following is logged in the System log of Event Viewer: The server threw an exception. 



RESOLUTION
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. To resolve this issue, follow these steps:  If the server cluster is an Active/Active cluster configuration, move the affected Exchange virtual server to a cluster node that is not running any other Exchange Server resources. All the following steps must be performed on this node. If the server cluster is an Active/Passive cluster configuration, all remaining steps must be performed on the Active cluster node. Delete the failed MSSearch resource in the affected virtual server, if the MSSearch resource exists.</li> Delete the MSSearch application. To do so: <ol style="list-style-type: lower-alpha;">  Copy the following code to a new text file, and then save the file as Deleteapp.vbs.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, see the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For additional information about the support options available from Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Sub Usage WScript.Echo &quot;Microsoft Search Version 2.0&quot; WScript.Echo &quot;Deletes an Application&quot; WScript.Echo WScript.Echo &quot;Usage: Deleteapp.vbs Application&quot; WScript.Echo end Sub

Sub Main

if WScript.Arguments.Count = 1 then if WScript.Arguments(0) = &quot;/?&quot; or WScript.Arguments(0) = &quot;-?&quot; then Usage WScript.Quit(1) end if   end if

if WScript.Arguments.Count < 1 then Usage WScript.Quit(1) end if

dim applicationName applicationName = WScript.arguments(0)

WScript.echo &quot;Deleting Search Application &quot; & applicationName Set objHost = WScript.CreateObject(&quot;MSSearch.Admin&quot;)

'Delete the application objHost.Applications.Remove(applicationName)

End Sub

call Main </li> Start the Cluster Administrator utility, right-click the Network Name resource that is associated with the affected Exchange virtual server, and then click Properties.</li> Click the Parameters tab, and then confirm that the name of the Exchange virtual server that has the failed MSSearch resource appears in the Name box. For example,  .</li> Click Cancel.</li> Start a command prompt, change to the folder that contains the Deleteapp.vbs file that you created, and then enter the following command, where  is the name of the Exchange virtual server that you confirmed in step c:

cscript deleteapp.vbs ExchangeServer_

For example,  .

If you receive the following message when you press ENTER, the MSSearch application may not exist:

The specified object cannot be found. Specify the name of an existing object.

Typically, this behavior occurs if the application has been removed, or if it has not been created. If you receive this message, ignore it, and continue to step 4.</li></ol> </li> Click Start, click Run, type regedit in the Open box, and then click OK.</li> Locate the following registry subkey:

</li> Under the Databases registry subkey, export and then delete all ExchangeServer_  registry keys (where   is the name of the Exchange virtual server that you noted in step c earlier in this article). For example, export, and then delete ExchangeServer_ .</li> Stop and then restart the Microsoft Search (MSSEARCH) service. To do this, type the following commands at a command prompt, and press ENTER after each command:

net stop mssearch

net start mssearch

</li> Click Start, click Run, type %windir%\cluster, and then click OK.</li> Right-click Exres.dll, click Properties, and then click the Version tab. Note the version number listed next to File version.</li> Click Cancel, and then start Registry Editor if it is not already running.</li> Locate the following registry subkey:

In this subkey,  is one of the following GUIDs:  <li>If the Exres.dll version that you noted in step 9 is 6.0.4592.0 or earlier, use the GUID associated with the Microsoft Exchange Information Store instance. Microsoft Exchange Information Store appears in the Data column in the right pane when you click this GUID.</li> <li>If the Exres.dll version that you noted in step 9 is later than 6.0.4592.0, use the GUID associated with the Microsoft Exchange System Attendant instance. Microsoft Exchange System Attendant appears in the Data column in the right pane when you click this GUID.</li></ul> </li> <li>Under the GUID, click Parameters, right-click ResourceVersion in the right pane, and then click Modify.</li> <li>In the Value data box, type 1 (one), and then click OK.</li> <li>Quit Registry Editor.</li> <li>Stop and then restart either the Microsoft Exchange System Attendant resource instance or the Microsoft Exchange Information Store resource instance, as determined by the version of the Exres.dll file from step 9. When you restart the appropriate resource instance, the MSSearch application is automatically re-created.</li> <li>In the Cluster Administrator utility, create a new Microsoft Search Server Instance resource and make it dependant on the Exchange Information Store resource. Name the resource MSSearch-, where  is the name of the affected Exchange virtual server. For example, name the resource MSSearch- .</li> <li>Start a command prompt, type the following commands, and then press ENTER after each command. In the following commands,  is the name of the affected Exchange virtual server and   is the network drive where the Exchange Server Information Store database is located.

cluster res MSSearch- /priv ApplicationName=&quot;ExchangeServer_ &quot;

cluster res MSSearch- /priv ApplicationPath=&quot; \Exchsrvr\ExchangeServer_ &quot;

cluster res MSSearch- /priv

Note You can determine the path of the default database from the LogPath registry value in the following registry subkey:

</li> <li>Start the Cluster Administrator utility (if it is not already started), and then bring the MSSearch resource online.</li></ol>

Additional query words: content indexing ci

Keywords: kbpending kbprb KB282122

-

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

© Microsoft Corporation. All rights reserved.