Mapi session excedded

HI all
I am a network administrator and i came across this wiered error 9646 which is for excedded mapi connection.
I checked on various solution and nothing points to Exchange 2007 though my users are using outlook 2003 on the end.
The user having this problem cannot connect to her outlook via desktop or laptop using xp(desktop) & laptop(vista)
LVL 7
vishal_impactAsked:
Who is Participating?
 
vishal_impactAuthor Commented:
HI
for all this as i sais i managed to resolve it all by myself from this link
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_field_notice09186a0080851821.shtml
The issue was with tcp ip chimney please have a look in the link for detailed info and commands i used
Thanx
Vish
0
 
adolphus850Commented:
Look at Exchange System Manager/Servers/<server>/<storage group>/<mailbox store>/logons. Visually find the user name (if this name is not known from log, as it was in my case) which exceeded 32 sessions.

Find the user's IP address, open tcpview.exe (from Sysinternals) and close all connections to store.exe generated by that IP.

It is also possible to amend a regkey that allows more sessions.  The above is for 2003.  it could be different for 2007.

Adol
0
 
sekhar_kiitCommented:
Hi,

If the error logs on Exchange 2003, please follow the following article to change the maximum allowed mapi sessions to more than 32:
http://support.microsoft.com/kb/842022

If this is Exchange Server2007, follow the below link:
http://support.microsoft.com/?kbid=925815

But this will load memory on the server. Restarting the IS will disconnect all the simultaneous connections. If you want permanent and proper resolution at a broader aspect check for the NIC which may causing the network connection failures and opening new connections. Please refer the below article which can help you:

http://msexchangeteam.com/archive/2007/07/18/446400.aspx

Regards,
Sekhar
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
vishal_impactAuthor Commented:
HI
I think i have managed to crack down it by
NTSH from exchange pwershell
Thnx anywayz nice to see quick response
0
 
sekhar_kiitCommented:
Can you please give a brief description of the solution or the powershell script? So that it will be helpful for others also in future.
0
 
vishal_impactAuthor Commented:
ok
it was just ntsh
then ummm was all just about diabling the chimney tcp ip
i could do these from gui as well but then need to restart server which is not good at all and all will avoid that
0
 
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.