I'm having trouble solving a problem with event id 9646 on an Exchange 2003 server. I've used exmon to see the sessions, but the user that is having the problem doesn't even show up with any connections. The user can login at a Windows 7 PC using Outlook 2007 without any problem. When that user tries to login on an XP pc with either Outlook 2007 or Outlook 2003, it can't connect. If I'm seeing event 9464 shouldn't I see a lot of sessions in exmon?

Always post the full event log detail entry since few of us memorize every event id number. The handy-dandy copy-to-clipboard icon can help you with that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Sorry. 9646 is very common. I figured anyone who would be able to answer a question about it would already be very familiar with it. Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9646 Date: 1/7/2011 Time: 2:10:45 PM User: N/A Computer: Elroy Description: Mapi session "/O=Tralfaz/OU=Astro/cn=Recipients/cn=testuser exceeded the maximum of 32 objects of type "session". For more information, click http://www.microsoft.com/contentredirect.asp.

ok.. here is a good KB article http://support.microsoft.com/kb/842022 this explains cause and solution you might want to consider doing what is mentioned in "more information" section in above articleDhruv

Thanks. I had seen that article and tried the solution. Keep in mind that I'm seeing the same thing on 2003 and 2007 clients. I don't want to perform the suggestion in the more information section because it is only happening to one user. That doesn't warrant making global changes.

this article talks about per user sessions and not total sessions globally on the information store.Dhruv

I understand that. But since no one else is having the problem, there must be a fix that doesn't involve allowing more than a standard amount of connections. I need to determine why this user is taking so many connections.

I'm finding that no matter what I try, the user cannot login using any Outlook flavor on any other PC. It only works on one PC. What could cause that?

On Mon, 10 Jan 2011 19:18:48 +0000, MikeM-2468 wrote: >I'm finding that no matter what I try, the user cannot login using any Outlook flavor on any other PC. It only works on one PC. What could cause that? Wireless devices (especially iPhones running version 4.0). WiFi connections through multiple access points. Being logged on to other machines. Desktop mailbox indexing programs. POP3/IMAP4 clients. Other users using his account to connect to his mailbox. If you look at the "Logons" view of the database do you see many connections for that account? Assuming you have the default timeout on TCP connections (two hours) you should be able to shut down his machine be able to use another machine a few hours later (or shut down his machine and start to move the mailbox to another database and then cancel the move to disconnect the sessions immediately). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I now find that the one pc would get kicked periodically too. Then I'd have to wait 2 hours to try to connect again. It seems to me that I should be able to logon to the same mailbox from at least a couple of PCs at once - in fact, I have. Even with this account. Is there anything group policy related that could cause this problem? There were some test changes made to Junk Mail policies, but those polices have been deleted. When I look at the Logons view, am I counting the items under the Username column or the Windows 2000 Account column?

On Tue, 11 Jan 2011 13:32:04 +0000, MikeM-2468 wrote: >I now find that the one pc would get kicked periodically too. That's pretty much expected. >Then I'd have to wait 2 hours to try to connect again. If you shorten the KeepAlive time to 5 minutes you won't have to wait so long -- and it'll probably make the symptom disappear -- but it won't fix the underlying problem of why there are so many connections to the mailbox. See this KB: http://support.microsoft.com/kb/324270 >It seems to me that I should be able to logon to the same mailbox from at least a couple of PCs at once - in fact, I have. Even with this account. You can -- until the number of sessions reaches 32. >Is there anything group policy related that could cause this problem? There were some test changes made to Junk Mail policies, but those polices have been deleted. No. But connectivity problems can cause it. If the client loses the connection and reconnects repeatedly within that 2 hour window you can eat up the 32 sessions. >When I look at the Logons view, am I counting the items under the Username column or the Windows 2000 Account column? The "User Name" is the name of the mailbox. The "Account" column is the NT account(s) with connections to the mailbox. So, for the maulbox (i.e. User), get the number of connections for each account. You'll probably find one account with lots of connections. You can add additional columns that should report the information about (and in some cases, from) the client used by the account. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I never see more than 15 connections to the mailbox. I've used tcpview and exmon also and see nothing that I don't see on a hundred other mailboxes.

From your description, I understand that the issue only occurs on certain user on Windows XP system. If I misunderstood, please let me know. First, I would like to confirm the following question: 1. Does other user use the problematic Windows XP machine to connect Outlook have the same problem? 2. Is there any difference between the problematic user and other normal user, such as OU? Since the issue only occurs on certain user, we can eliminate the Exchange server cause. I suspect the issue is caused by corrupted user mailbox or the causes in KB842022. To troubleshoot the issue, please refer to the article to modify the registry. Before modifying the registry, you can back up the registry key first to avoid unexpected problem or you want to revert it back. If the issue persists, I suggest you move the user mailbox to another Storage Group or Database to check the result. Regards, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

On Wed, 12 Jan 2011 12:32:24 +0000, MikeM-2468 wrote: >I never see more than 15 connections to the mailbox. I've used tcpview and exmon also and see nothing that I don't see on a hundred other mailboxes. Are the connections all from the same IP address? If you terminate a few of the connections can the mailbox be used (at least for a little while)? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Wed, 12 Jan 2011 12:32:24 +0000, MikeM-2468 wrote: >I never see more than 15 connections to the mailbox. I've used tcpview and exmon also and see nothing that I don't see on a hundred other mailboxes. Are you using Windows Server 2003 SP2 (or installed the SNP in SP1)? Have you disabled the stuff that the Scalable Network Pack enables? http://support.microsoft.com/kb/950224 http://support.microsoft.com/?kbid=948496 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I'll reply to the three recent posts in order. In response to Novak Wu: The problem occurs on Windows 7 and XP. Other users can logon to the pc with no problem. No difference in OU. See Dhruvaraj's post on Friday, January 07, 2011 7:52 PM along with my reply RE KB842022. In response to Rich Matheisen: "Are the connections all from the same IP address?" No. I see connections from the primary PC (W7 which works 99% of the time) and connections from the other pc (or PCs if I try more than one). One peculiar thing I've seen is that if I try to close the connections in tcpview they don't go away even several minutes after the pc is powered off. "Are you using Windows Server 2003 SP2 (or installed the SNP in SP1)?" 2003 EE SP1. SNP is not installed.

More testing has shown the following: If I have the mailbox open on Windows 7 running Outlook 2007, I can't (usually) open the mailbox on another PC (XP running Outlook 2007 or 2003). If I close the mailbox on Windows 7, I can immediately open it on multiple XP pcs. While it's open on the XP boxes, I can successfully open it on Windows 7 but if I close it on XP, sometimes I can and sometimes I can't reopen it.

On Thu, 13 Jan 2011 13:24:59 +0000, MikeM-2468 wrote: >I'll reply to the three recent posts in order. In response to Novak Wu: The problem occurs on Windows 7 and XP. Other users can logon to the pc with no problem. No difference in OU. See Dhruvaraj's post on Friday, January 07, 2011 7:52 PM along with my reply RE KB842022. In response to Rich Matheisen: "Are the connections all from the same IP address?" No. I see connections from the primary PC (W7 which works 99% of the time) and connections from the other pc (or PCs if I try more than one). One peculiar thing I've seen is that if I try to close the connections in tcpview they don't go away even several minutes after the pc is powered off. "Are you using Windows Server 2003 SP2 (or installed the SNP in SP1)?" 2003 EE SP1. SNP is not installed. How large (in terms of folders and the number of items in the folders) is the mailbox? And is this problem associated only with one mailbox? I'll bet you already said something about that, but I can't find a clear statement about it in this thread. If it's just this one mailbox, how about moving it to another database? If there's a problem in the mailbox that usually (but not always) fixes it. As to running SP1, why not SP2 and updating the tcpip.sys driver? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The mailbox is about 250MB with less than 20 folders. The problem is only with one mailbox, but most users don't try to open their mailbox twice (with the exception of some utility mailboxes which are open by 6 or more users at a time.) I think I have an acceptable workaround for my purposes - closing the mailbox on the W7 box before opening it on XP. If that doesn't work consistently, I'll move the mailbox to another store. We won't go to SP2 since we're moving to 2010 soon (unless it's a requirement of the migration).

On Fri, 14 Jan 2011 12:43:49 +0000, MikeM-2468 wrote: >The mailbox is about 250MB with less than 20 folders. That's not big enough to be a problem. >The problem is only with one mailbox, Hav you tried moving the mailbox to another database? >but most users don't try to open their mailbox twice (with the exception of some utility mailboxes which are open by 6 or more users at a time.) I do that pretty often. I don't have that problem, though. >I think I have an acceptable workaround for my purposes - closing the mailbox on the W7 box before opening it on XP. If that doesn't work consistently, I'll move the mailbox to another store. I'd do that now. >We won't go to SP2 since we're moving to 2010 soon (unless it's a requirement of the migration). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hello MikeM-2468, => To fix Event id 9646 Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9646 Date: 1/7/2011 Time: 2:10:45 PM User: N/A Computer: Elroy Description: Mapi session "/O=Tralfaz/OU=Astro/cn=Recipients/cn=testuser exceeded the maximum of 32 objects of type "session". For more information, click http://www.microsoft.com/contentredirect.asp. => Disabled the TCP\IP chimney from command prompt Netsh int ip set chimney DISABLED It will fix the issue. EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

Thanks for the info. I found that as a potential solution but making any server level changes is not an option as this only impacts a single mailbox.

We have been running into this issue quite a bit as well. It started with CRM rollup 12 (not sure if you are running that as well) through some calls with the microsoft exchange and crm team we have gone from having about 12 users run into this issue every 30 minutes, down to 2 users running into it once a day after installing CRM rollup 15. It is still annoying and very odd that these "fixes" they have suggested work for some users but not all. We also tried moving to a different datastore with no luck. Could this have anything to do with a replication job that we have running twice a day to our offsite server?