-
Exchange 2007: Mapi session exceeded the maximum of 32 objects of type “session”
Posted on February 13th, 2008 9 commentsError Message: “Mapi session “/o=Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=JohnSmith” exceeded the maximum of 32 objects of type “session”".
Source: MSExchangeIS
Event ID: 9646On the client side, the user is unable to connect to Microsoft Exchange or getting this error:
Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server is down for maintenance.
This usually happens when the user loses network connectivity while Outlook is still open. The Exchange server wasn’t able to close the sessions properly so they just stayed there even when they are not in use.
By default, Exchange only allows up to 32 MAPI (Outlook) sessions per user. To fix this problem, you must close some of the sessions.
What to do:
- Download and extract Sysinternals’ TCPView (free) on the Exchange server
- Open the Exchange Management Shell and type in the following command to get a list of all the opened sessions. Make a note of the IP Addresses:
Get-LogonStatistics jsmith | Sort-Object clientipaddress | Format-Table username,clientipaddress,logontime - Open Tcpview.exe on the server. Sort it by Remote Address, then sort it by Process.
- Look for the IP Addresses from Step 2 in the Remote Address column (if you only see hostnames, go to Options -> uncheck Resolve Addresses) and close their connections for the store.exe process (right-click and choose Close Connection, you can select multiple connections by holding the Shift or Ctrl key)
- Run the command from Step 2 again and you will see that the sessions disappeared. The user should now be able to connect to the Exchange server again.
9 responses to “Exchange 2007: Mapi session exceeded the maximum of 32 objects of type “session””
-
Thanks a lot !
We’ve got this problem with a client and it’s fix the problem !
-
I can confirm that this works. This is a workaround, of course, and does not solve the problem of loosing connectivity.
-
Sole IT Man October 17th, 2008 at 11:07
This saved my a$$ I don’t know who you are but thank you thank you thank you for sharing this information. I don’t know what I would have done except reboot my exchange server in the middle of the day (not a very good choice) and kick of everyone just because one user could not conenct.
Awesome post!!!!
-
webmaster October 18th, 2008 at 16:15
You’re welcome, glad I was able to help
. Btw, we haven’t had this issue ever since we installed Exchange Server 2007 SP1 and Update Rollup 1 back in March. We used to get about 1-3 cases of this every week. -
Great! Thank you very much!
I always wanted to write in my site something like that. Can I take part of your post to my blog?
Of course, I will add backlink?Sincerely, Timur Alhimenkov
-
Thanks, this was very helpful. In my case, the user went over their allotment of connections because he was on a laptop which was periodically connecting to a wireless access point not on our network, which would disconnect him from the Exchange server.
I had trouble closing the connections with TCPView until I realized I had to right-click the .exe and Run as Administrator.
-
Thanks for this post. I had this problem for this first time today because of a flakey WIFI connection and am back up and running within mintues.
-
Charles R April 7th, 2010 at 15:04
Your resolution saved the day for me! Thanks for posting such useful info!
Leave a reply
Le Ber February 29th, 2008 at 04:12