MAPI session /O=QCA/OU=London/cn=Recipients/cn=KhanS exceeded the maximum of 32 objects of type "session"
We had the same issue last year and a LAN accelerator was the problem. However, I don't think that this is still the case. How can I solve this problem?
I imagine this behavior started when you installed Exchange Server 2003 SP1, which throttles MAPI connections to 32 connections per user. If the user is accessing a large mailbox, disable cached mode to see if this behavior ceases.
If neither of these suggestions point to obvious issues, check to see which MAPI clients are running on KhanS's computer. If you're certain that KhanS requires more than 32 MAPI connections, then you can increase the Maximum Allowed Sessions Per User registry key on your Exchange server. The key is located in the following path:
If the Maximum Allowed Sessions Per User key doesn't appear, create it as a new DWORD value.
Next, set Maximum Allowed Sessions Per User to a decimal value greater than 32.
I'd suggest trying this in a lab first, backing up your registry and taking other precautions as you normally would when changing your production Exchange server. Once the change is made, recycle the MSExchange Information Store Service and monitor regularly to ensure that the issues have gone away.
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on Legacy Exchange Server versions
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.