Hi! Techies, I've a7 two node Exchange2003cluster and Microsoft Search service terminated unexpectedly on all the cluster node at the same timeand prety much restartedshortly. below is the event generated Event Type:ErrorEvent Source:Microsoft SearchEvent Category:Gatherer Event ID:10009Date:9/15/2009Time:6:03:51 PMUser:N/AComputer:SYEXCHS02CDescription:An error occurred in the resource status monitor for instance <Exchange MS Search Instance (SYEXCHS02)>: 800706be - The remote procedure call failed. OS: Windows 2003 ENT Server Exchange:Enterprise Server 2003 is there a reason forthe remote procedure call failure on all the 7 clusters and what is a fix for the issue.I'm able to find a Hotfix for Exchange 2000 Servers, but it does not suite for Exch 2003. Can anyone help me to troubleshoot this problem!!! Thank you all.

What does the ExBPA report say? Did it log any errors in application logs? Are you able to failover the group to another node and then the keep the resource online?Milind Naphade | MCTS:M | http://www.msexchangegeek.com

Is MS search resource restarted successfully? Does the issue cause any impact on the exchange server, like failover or offline resource? Please check the resources on the cluster admin console It looks as though cluster is attempting to bring MS search back online, but it fails to initialize MS search and generates the 800706be error. Something is preventing us from bringing the resource back online after it fails. The similar symptom has been fixed by running the Microsoft Search resource in a separate Resource monitor. The recommendation is to change the current option in the Exchange Resource for MSSearch on the clusters to run this resource in a separate Resource Monitor: 1. Open Cluster Manager 2. Go to the resource group for Exchange Notes: Which node is the active node this is needed for the confirmation the change took effect 3. Open the task manager on the active node and locate resrcmon.exe. Note the number of instances running. 4. Right-click the passive node and choose PAUSE NODE 5. Right-click the resource instance, choose Take Offline 6. Open the Properties of Exchange MS Search Instance 7. Select the Checkbox for Run this resource in a separate Resource Monitor 8. A Pop-up window will appear The properties were stored but not all changes will take effect until the next time the resource is brought online Error ID: 5024(000013a0). Click OK on the Pop-up 9. Bring the MSSearch resource online 10. Confirm MSSearch is running under its own monitor: Open the task manager on the active node and locate the resrcmon.exe, there should now be 1 additional instance running beyond the number noted in step #3 Resources: Exchange Server 2003 computer cannot bring the Microsoft Search resource online

Any update?