Hello all,Hopefully a fairly basic question. We have a fairly small Exchange server 2k3 (sp2) serving about 100 mailboxes.We've slowly had a buildup of event id 9646's (exceeded 32 object access). To begin with this hasn't concerned me too much as I've just put it down to outlook crashes/client AV software however i'm starting to see some fairly old logons. For example we have one logon from the 24/01/2007 with a last access time of the same date/time still listed in Systems Managers logon section. Is this normal?I'm starting to wonder if these connections are not getting closed up by exchange correctly.Any ideas? Or an I just being an idiot and misinterpreting the dialog?

I'm in the same boat. It is my VPN and OWA users who accumulate old connections over the course of days orweeksand eventually experience the problem (and log event id 9646 on the server). I can use the sysinternals tcpview utilityto forceconnections closed, or reboot the server. Increasing connection limits or giving users 'view information store status' permission(as mentioned in kb842022)seems like a bad idea and just delays the problem from showingthe symptom,but doesn't solve it. Is there some way to automaticallytime out old connections on Exchange 2003 sp2?

I am too facing the same strange problem after migrating exchange 2003 server to a new hardware , I agree wht RonAbt says about giving the users "view information store status " is not a proper solution , there should be some fix for this .I know exchange service pack 1 puts a limit on no. of sessions to 32 for security reasons, but why exchange does not closeold logon sessions for users who exceeded the limit , unless you mount and dismount the mailbox store sessions do not reset. Don't know why microsoft din't document the solution about this issue in 842022 kb.I think its a bug in exchange with no proper solution , just with workarounds which we have to accept finally. If someone could provide a real good solution , Thanks in advance Regards, X!A