A warning message that resembles the following is logged in the Application log on a server that is running Microsoft Exchange Server 2010:
ID: 122 Level: Warning Source: MSExchange Search Indexer Machine: server_name.company_name.com Message: MS Search (Exchange) reached the memory cap, and now the memory is 7193395200 Bytes. The cap is 4294967296 Bytes
Note The memory usage in the warning message is between four gigabytes (GB) and seven GB.
This issue can occur because this event is logged based on the Process\Working Set Peak counter for the Microsoft Exchange Search Indexer service (Msftesql.exe) instead of the Process\Working Set counter. Therefore, this warning message is logged repeatedly when the following conditions are true:
The Msftesql.exe process is started.
The memory usage for the Msftesql.exe process is greater than four GB at any time.
Note Because event ID 122 is based on the Process\Working Set Peak counter, the event is logged repeatedly, even if the memory usage for the Msftesql.exe process decreases to less than 4 GB.
To work around this issue, restart the Msftesql.exe process.
Note If the issue that is described in the "Symptoms" section reoccurs, restart the Msftesql.exe process again.
Event ID 122 is an informational warning message that the memory usage for Msftesql.exe process has increased to over four GB. However, the memory usage for the Msfteaql.exe process may only be two GB in some instances.
The issue that is described in the "Symptoms" section is more common on Exchange Server 2010 servers that have a large amount of physical RAM. For example, this issue is more likely to occur if the server that is running Exchange Server 2010 has over 96 GB of physical RAM.
For more information about performance monitoring, visit the following TechNet website: