How to get rid of 9646 events

Applies to Exchange 2003 Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9646 Description: Mapi session “/o=<org>/ou=First Administrative Group/cn=Recipients/cn=<userName>” exceeded the maximum of 32 objects of type “session”. Seen these in your environment?  Sometimes they are caused by desktop search engines opening too many MAPI sessions, other times they are because your…


Database Status Unknown in 2k7 EMC? This might be why….

Applies to Exchange 2007  So I ran into a case today that was pretty interesting.  The symptoms were a fairly generic error in the app log: Event ID: 4001Task Category: GeneralLevel: ErrorKeywords: ClassicUser: N/AComputer: server nameDescription:A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds. Diagnostic…


Repeating 623 version store error.

Applies to Exchange 2003 I had a case a couple weeks ago I thought I’d write about.  What was happening is the Version Store would run out of memory and a 623 error would throw.  Version Store buckets allocated would climb from 4 to over 2000 in less than 5 minutes.  The store would then…


How to fix smashed schema in Exchange 2003

Dan and I and some other engineers wrote up a blog post you can find here on how to recover from a smashes schema scenario on your Exchange Servers.   It’s pretty succinct so I don’t have anything to add to it, it’s an interesting read though.


How to determine who is connecting to your server in cached mode.

Applies to:  Exchange 2000/2003   This may seem like a basic thing to some people, but for those who don’t know, here goes.  This can be easily done by running Exmon, available here. So download Exmon and fire it up on your Exchange Server. Go to the By Clientmon tab, and in there you’ll see…


Spoof your old dead Exchange Server

Ok, so if you have say, Citrix, or a standard image with Office pre-installed, then someone had to pick an Exchange server to point to for the Outlook profile creation wizard.So sometimes, in large organizations, teams don’t necessarily speak to one another before they make small decisions like which server to point to.  The person…


Version Store 624 events

Applies to Exchange 2000, Exchange 2003, Exchange 2007. So in Version Store 623 errors, Version Store gets ‘clogged’, if you will, and will fail to process transactions. 624 errors on the other hand, are caused by a lack of available virtual memory on the server.  Sometimes this has no impact and the server corrects itself,…


Avoiding Version Store problems in the enterprise environment

Applies to Exchange 2003    So one of the things that can go wrong with Exchange is that it can run out of something called Version Store.  Version store is an in-memory list of changes made to the database.  Nagesh Mahadev has an awesome post about Version Store on our blog, posted here.  To…


PTE depletion, handle leaks and You

Applies to:  Windows 2000 Server/Advanced Server, Windows 2003 32bit Server, Exchange 2000/2003 PTEs  Ok, so one of the most overlooked resources we run into with performance and availability problems is the availability (or lack thereof) of Free Page Table Entries.  What is a PTE?  It’s basically an I/O partition table, if you will.  Wikipedia has an…