OS: Microsoft Server 2008 x64 (with SP2) Exchange: 2007 SP3 Standard (with no update rollups) Databases: 4, totalling 100Gb altogether (all with IndexEnabled set to True) It seems that the 'Microsoft Exchange Search Indexer' constantly hammers my CPU, maxxing it out. There are no events of interest in the System or Application Log. By looking through all the Search-related performance counters, I see an ever-increasing rate of 'FB, ST terminated time out' and 'FB, ST unresponsive to shutdown'. From my Googling, here are the descriptions for those counters: FB, ST terminated time out: Number of terminated single-threaded filter daemons to date due to a time-out. A time out occurs when the FD takes too long to process a document. These timeouts are controlled by the FTE_FilterDaemonBatchAgingInterval and FTE_ChunkBufferTimeOutSeconds admin parameters. FB, ST unresponsive to shutdown: Number of times to date that the single-threaded filter daemons were given a directive to shutdown but didn't respond in time. Has anyone seen similar CPU activity for this search indexing service? What further steps can I do to troubleshoot the issue?

Hi, Please refer to the following article to rebuild Search Indexer to troubleshoot the issue. How to Rebuild the Full-Text Index Catalog http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx After that, please monitor the process again to check the result. Thanks. Novak 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.