Article ID: 830836 - View products that this article applies to.
When you try to send more than 250 messages or 100 attachments by using a batch or script, the messages or attachments may not be sent, and events that are similar to the following may be logged in the application event log:
Event Type: Error
Event Type: Error
This issue occurs because of a limit on the number of items that clients can open. By default, this limit is set to 100 for attachments and 250 for messages.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Important If you increase the MaxObjsPerMapiSession value, it can have a significant performance affect on the Microsoft Exchange server. Specifically, if the batch file or the script that you used to send the messages or the attachments does not correctly close out MAPI sessions, no clients can log on to the Exchange server if you have increased the MaxObjsPerMapiSession value. We recommend that you correct the batch file or the script instead of changing the MaxObjsPerMapiSession value.
Note Microsoft Exchange Server 2003 Service Pack 1 (SP1) increases the default values of the object types that are listed in the "More Information" section. This behavior is referenced in the following Microsoft Knowledge Base article:
830829To resolve this issue, follow these steps:
(https://support.microsoft.com/kb/830829/ )Your Exchange Server 2003 computer may stop responding after a MAPI client opens more than the default value of certain server objects
If the problem persists after you have applied Exchange Server 2003 SP1 to the computer that is running Exchange, determine which item from the following list is causing these items to remain open in the client:
After the data is collected, follow these steps:
As mentioned previously, this problem may be caused by a program that integrates with Outlook, with an Outlook add-in, or with a batch file or script that is running against the mailbox.
As a further troubleshooting step, remove or disable any third-party Outlook add-in and antivirus software on the client computer. Then, verify the results of the server again to ensure that these objects are no longer open.
The following objects are typical objects that you may see in event ID 9646 messages:
Article ID: 830836 - Last Review: October 25, 2007 - Revision: 1.7