Export (0) Print
Expand All
Expand Minimize

MaxOpenMessagesPerLogon has been set

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-05-14

The Microsoft Exchange Analyzer Tool reads the following registry entry to determine whether the MaxOpenMessagesPerLogon registry value is present and configured:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

If the Exchange Analyzer finds the MaxOpenMessagesPerLogon registry value present and configured to have a value more than 0, a nondefault configuration message is displayed.

Every time that a MAPI client or application opens a message on an Exchange Server computer, it causes the Microsoft Exchange Information Store service (store.exe) to consume a small amount of physical memory. When the message is closed by the Microsoft Office Outlook 2003 or Outlook 2007 clients, the memory is released. To prevent one or more MAPI clients from causing the Exchange store service to continuously allocate memory, a new configuration feature was introduced in Exchange 2000 Server Service Pack 1 (SP1) that lets an administrator limit the number of messages each MAPI client logon session can open simultaneously. Setting such a limit may be useful in your environment if certain client applications unintentionally open many messages, thereby affecting overall server performance.

This feature is implemented by using the MaxOpenMessagesPerLogon registry value on the Exchange Server computer. We recommend that a limit no more than 1000 be set. A value of 1,000 allows each client to use approximately 4 to 6 megabytes (MBs) of memory. For some environments, a smaller value of 500 may be more appropriate.

importantImportant:
This article contains information about how to edit the registry. Before you edit the registry, make sure that you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.

  1. Open a registry editor, such a Regedit.exe or Regedt32.exe.

  2. Open:

    HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

  3. Right-click ParametersSystem, select New | DWORD Value, and give the new value a name of MaxOpenMessagesPerLogon.

  4. In the right pane, double-click the MaxOpenMessagesPerLogon value, and then enter the maximum number of simultaneously open messages, in decimal.

  5. Close the registry editor and restart the Microsoft Exchange Information Store service for the change to take effect.

Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

For more information about the MaxOpenMessagesPerLogon registry value, see Microsoft Knowledge Base article 289109, "XADM: How to Limit the Number of Messages Opened for Each MAPI Logon" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=289109).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft