Thursday, October 05, 2006

Event ID 9694

WARNING: The following post contains information only an Exchange Administrator will ever care about. Apologies to all non-technical readers but this has consumed so much of my life this week that I must write about it.

Here is the scenario: User has Outlook 2003 SP2 running on XP SP2 machine talking to Exchange 2003 SP1. Outlook is running in cached mode. Client has numerous crack add-ins such as Plaxo, Linked-in, and Google desktop search engine. And they also run AIM. Client loses connectivity to Exchange and is getting kicked out of AIM at the same time. Event ID 9646 appears on Exchange server:

Mapi session "/O={Exchange org name}/OU=R_VA/cn=Recipients/cn={username}" exceeded the maximum of 32 objects of type "session".

And guess what? User is locked out for 30 minutes unless you reboot the IS!

Really, at the end of the research, I became convinced that both Outlook and Exchange were behaving properly. Something else was generating massive amounts of MAPI sessions. The only answer is AIM and the incredible number of open chat windows this particular user had active during any given hour. I found this article that discusses how to increase the allowed number sessions from the default of 32 to something more. I have made the registry fixes, now I sit back and wait for the howls or blissful silence.

***Update on how this turned out here***

Technorati tags: , ,

0 comments: