- High CPU usage in the noderunner.exe process
- High memory usage in noderunner.exe
- High handle count in noderunner.exe
- Failed content indexes
- Database failovers
Additionally, the following event may be logged in the Application log:
If you review the Search Service logs, you may see several events that contain the following text:
Also, the following event is logged in the System log:
Finally, the Unified Logging Service (ULS) logs may contain several events with the following text:
Note By default, the Search Service logs are located at %ProgramDir%\Microsoft\Exchange Server\V15\Logging\Search, and the ULS logs are located at %ProgramData%\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\Logs.
Database failovers occur when content indexes are marked "Failed" or "Failed and Suspended." These failovers are typically indicated in the Application log through event ID 122.
Article ID: 3121815 - Last Review: 11 May 2016 - Revision: 1