I've seen a ton of posts related to the search service and it would be great if someone could shed some light on my problem. Last night I upgraded my Exchange 2007 organization from SP1 Rollup 7 to SP3 Rollup 2. I have a two node SCC using SCR to a target mailbox server (single node SCC). I upgraded my target SCR node to SP3 rollup2 - right after doing so I noticed a very high cpu usage (90-100%) in process microsoft.exchange.search.exsearch.exe. I also updated my passive node in the SCC and noticed high cpu usage but not as high as the SCR node 20-50% only in that one process. I have left my active node on SP3 (non rollup 2) as it is not exhibiting the high cpu behavior. Here's my question....I've seen several posts related to the search service but all are indicative of a corrupted search catalogue and why would my "passive" nodes be displaying this behavior for the search service if the databases aren't even mounted on them? I was wondering if the issue could be related to the fact that I haven't put SP3 rollup 2 on my active node yet - but I couldn't understand why that would make a difference. Has anyone seen this before and would rebuilding the index help?

Hi KESM0724, Suggest you install the Rollup 2 on the active node as well. How to Install Update Rollups in a Single Copy Cluster http://technet.microsoft.com/en-us/library/bb885045(EXCHG.80).aspx After that, please see this blog: Exchange Search Fails After Installing Exchange 2007 SP3 http://blogs.technet.com/b/exchangesearch/archive/2011/01/18/exchange-search-fails-after-installing-exchange-2007-sp3.aspx Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.