netman70
asked on
Outlook 2003 disconnects from Exchange
I have Exchange 2003, SP1. The Event Log starts showing recurring messages of:
Mapi session "852c273a-01a9-4907-bab8-3 f2a2efe00c 8" exceeded the maximum of 32 objects of type "Session"
And at some point, users are no longer able to connect to Exchange via Outlook (version 2003, running in cached mode). Restarting the ExchangeIS service or rebooting the server seems to fix this problem for a while but problem reappears after a few days. I have looked at Microsoft KB830829 and KB830836. I created a "Maximum Allowed Sessions Per User" entry under "HKEY_LOCAL_MACHINE\SYSTEM \CurrentCo ntrolSet\S ervices\MS ExchangeIS \Parameter sSystem" and increased the value from 32 (default) to 64 and then 128 but the problem will not go away.
Any advise would be greatly appreciated.
Thanks
Mapi session "852c273a-01a9-4907-bab8-3
And at some point, users are no longer able to connect to Exchange via Outlook (version 2003, running in cached mode). Restarting the ExchangeIS service or rebooting the server seems to fix this problem for a while but problem reappears after a few days. I have looked at Microsoft KB830829 and KB830836. I created a "Maximum Allowed Sessions Per User" entry under "HKEY_LOCAL_MACHINE\SYSTEM
Any advise would be greatly appreciated.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Simply put, an application keeps spawning MAPI sessions. Bare bones Outlook 2003 as a general rule will not cause this. Its usually related to 3rd party MAPI enabled apps such as Outlook or server side Anti-Virus, other Outlook add-ins, Blackberry, Pagemaster, etc...
Start by turning up diagnostics logging for MSExchangeIS Mailbox\Logons and try to use the resulting events to find out which users specifically are causing this issue. Once you have the user pinned down it is a lot easier to figure out the cause.
Start by turning up diagnostics logging for MSExchangeIS Mailbox\Logons and try to use the resulting events to find out which users specifically are causing this issue. Once you have the user pinned down it is a lot easier to figure out the cause.
ASKER
Setting the ""Maximum Allowed Sessions Per User" to 128 seems to have worked. Thanks
ASKER