Symptom 1The Content Index State on all mailbox databases is FailedAndSuspended.
Symptom 2The following message is logged in the Unified Logging System (ULS) logs:
Note By default, Exchange ULS log files are saved in the following location:
Symptom 3The NodeRunner.exe process throws an exception when it tries to allocate more memory than the available memory. In this situation, the following errors are logged:
- Locate the Noderunner.exe.config file. By default, this file is located along the following path:C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config
- Edit the file, and then locate the following key:
<nodeRunnerSettings memoryLimitMegabytes="<value>" />
- If the value of the key is set to any value other than 0, change it to 0, as follows:
<nodeRunnerSettings memoryLimitMegabytes="0" />
- Restart the Microsoft Exchange Host Controller Service.
The following screen shot shows the four nodes of the NodeRunner.exe process: Admin, Content, Query, and Index.
If you're familiar with SharePoint Server, you probably know how to limit the memory that's allocated to the NodeRunner.exe process by using the application configuration file. However, it's unsupported in Exchange Server 2013 to limit memory allocation for NodeRunner.exe by this method.
The default setting for the minimum memory requirement for NodeRunner.exe is 0. The NodeRunner.exe process can consume and change its memory requirements dynamically, based on current requirements and available memory. However, you can set the upper limit and restrict the volume of memory that Node Runner can access by using the memoryLimitMegabytes parameter in the NodeRunner.exe.config file. If you limit memory usage by NodeRunner.exe, and if the Exchange server can't allocate memory for the NodeRunner.exe operation, the operation may fail with an OutOfMemoryException exception.
Article ID: 3094698 - Last Review: Oct 16, 2015 - Revision: 1