Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
CAUSE
This problem may occur if a MAPI client opens more than the default value of the following server objects:
Note Microsoft Exchange Server 2003 Service Pack 1 (SP1) increased the default value of several server objects. The increased values are shown in the "SP1 and later service packs" column in the following table.
Entry | Default Value | SP1 and later service packs |
objtMessage | 250 | 250 |
objtFolder | 500 | 500 |
objtAttachment | 100 | 500 |
objtFolderView | 500 | 500 |
objtMessageView | 500 | 500 |
objtAttachView | 250 | 500 |
objtStream | 50 | 250 |
objtACLView | 50 | 50 |
objtRulesView | 50 | 50 |
objtFXSrcStrm | 50 | 50 |
objtFXDstStrm | 50 | 50 |
objtCStream | 50 | 50 |
objtNotify | 500,000 | 500,000 |
RESOLUTION
In Exchange Server 2003, the number of server-side objects that are allowed by clients is limited to prevent a single client from the exhausting resources on the Exchange server. When the event log error that is mentioned in the "Symptoms" section occurs, it indicates possible poor behavior on behalf of a client opening too many objects or leaving too many objects open on the server. If the event log error occurs, investigate any third-party applications or add-ins that are running on the client.
Additionally, investigate the user behavior that is associated with the indicated logon. This will help you better understand why the default number of objects is insufficient. In rare circumstances, the number of resources is insufficient and may be adjusted. However, use caution before you adjust the maximum number of objects that are allowed. When you increase the maximum number of objects of a particular type, you also increase the amount of memory that may be consumed by client requests. Incorrectly configuring this value could lead to out-of-memory warnings or virtual memory fragmentation warnings.
You can add a registry key that adjusts the maximum number of resources that a MAPI client can use at the same time. This adjustment overrides the default limit of each server object that is mentioned in the "Cause" section.
Note You should only adjust the value for the object type that is referred to in the event log error that is mentioned in the "Symptoms" section. You should adjust these values with caution, and only increase the value in small increments. For example, only adjust the value by 100.
For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To add a registry key that limits the maximum number of resources that a MAPI client can use at the same time, follow these steps:
- Click Start, click run, type regedit, and then click OK.
- Expand the following registry subkey:
\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
- Right-click ParametersSystem, point to New, and then click Key.
- Type MaxObjsPerMapiSession, and then press ENTER to name the new subkey.
- Right-click MaxObjsPerMapiSession, click New, and then click DWORD Value.
- Type Object_type, and then press ENTER to name the object.
Note Object_type is the name of the object type in the error message that is mentioned in the "Symptoms" section. For example, type objtMessage, and then press ENTER. - Right-click Object_type, and then click Modify.
- In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the objtMessage object. The default value is 250.