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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
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
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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.
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
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.