1 outlook 2007 client cannot connect to exchange. THe send/recieve error says network problems, but no issue with rpings etc. The exchange app log reports this Event ID 9646 Source: MSExchange IS Mapi session "/o=Org/ou=First Administrative Group/cn=Recipients/cn=GBecker" exceeded the maximum of 32 objects of type "session". Does anyone know what to look for on the client? I'll post this in an outlook group too, but figured this might be over the heads of outlook folk :-) THanks~!

Any add-ins on the Outlook client? Have you tried blowing away the profile and creating a new one? Does the user have the same problem if running Outlook from a different machine? Some workaround suggestions here: http://support.microsoft.com/kb/830836 Tony www.activedir.org

I had the same issue. A poor internet connection causing our vpn to drop constantly. We fixed the inetrnet connection and haven't had a problme since. Restarting the info store was the only way to clear the hung sessions. I belive they will eventually drop off but it takes a very long time. Here's info on increasing the number of allowed sessions. http://support.microsoft.com/kb/842022

I still never found the root cause of the issue, but i gave the user 'view info store status' rights on her mailbox store and it solved the issue. I was nervous about raising the max mapi sessions...i'm sure its there for a reason. I theorize that the root cause of all the MAPI calls could be that she has 15 shared calendars open at a time.

Hi,There is a limitation for simultaneous connection for Exchange Server 2003 Sp1,the limit is 32 sessions simultaneous for 1 client. here you can found more information and how to solved the problem. http://support.microsoft.com/kb/842022 Regards Jose

The problem with the microsoft error description is that it assumes you are using an unusual client software to connect with Exchange. There is no explanation of what could be the cause when the client is Outlook.We had this problem some time ago and it turned out to be a failing ethernet cable out of the client PC. On replacing the cable, the connection became stable and the client stopped requesting new sessions of the server.

I was having this same issue, I called microsoft and they told me this was a know issue and to run this command on your exchange server netsh int ipset chimney disabled