Event 623 RRS feed

  • Question

  • We're running Exchange 2003 and had this event occur this afternoon (along with 9791 and 1022). I've seen several KBs that each provide a hotfix, but I'm not sure which of the potential causes was our problem. How do I figure that out? There were no backups running. Here is event 623:

    Event Type: Error
    Event Source: ESE
    Event Category: Transaction Manager
    Event ID: 623
    Date: 9/22/2011
    Time: 2:33:37 PM
    User: N/A
    Computer: serverName
    Information Store (3008) storeName: The version store for this instance (1) has reached its maximum size of 249Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Possible long-running transaction:
    SessionId: 0xBD331240
    Session-context: 0x00000000
    Session-context ThreadId: 0x00003560
    Cleanup: 1


    Thursday, September 22, 2011 9:27 PM


All replies

  • Hi mhashemi,

    Yes, there are a lot of resources about the Event 623:

    Do end users meet some symptoms?

    "Users unable to access their inbox", "Email backing up in the local delivery queue" and "Email awaiting directory lookup". See:


    "immediately at the start of the Information Store service". See:


    Anyhow, please download the Exbpa and run a Health Check. If warning/error exists, please try to resolve it.


    After that, please check Event 1221, if there are a lot of white space, please run the Eseutil /D. Then run isinteg until you see 0 errors, 0 fixes & 0 warning.

    Eseutil /D Defragmentation Mode
    Exchange Command-Line Parameters for the Isinteg.exe Tool


    Frank Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Marked as answer by emma.yoyo Thursday, September 29, 2011 4:42 AM
    Friday, September 23, 2011 6:49 AM
  • We saw that users were unable to access their mailbox for about 15 minutes. This is the first time this has happened. :)

    How would you define "a lot of white space?" I've got a DB that's about 100GB and the white space is 911MB which doesn't seem like much.

    I'll run the BPA too.

    Friday, September 23, 2011 2:04 PM
  • This can actually be due to a long running transaction, for example I had this happen years ago when running a rule on a service account mailbox that was 10GB. Systems low on resources typicall disk latency which you can take a look at (log buffer stalls) which will consume your version memory. Monitor your log buffer stalls in perfmon


    ESE log buffers that are set too low can cause the Microsoft Exchange Information Store service to stop responding


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    • Marked as answer by emma.yoyo Thursday, September 29, 2011 4:42 AM
    Friday, September 23, 2011 3:09 PM
  • Some more information I have is that event 1022 showed two specific users. I talked to them and they couldn't think of anything they were doing in Outlook that'd cause a long transaction and I didn't see any large messages from that day.

    The troubleshooting blog from the Exchange team suggests running isinteg -S Servername -FIX -TEST ALLTESTS and eseutil /g. Can these be run will Exchange is running, or do I need to dismount all the stores first?

    Friday, September 23, 2011 5:57 PM
  • When you run it it will prompt you telling you that it will dismount.

    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    Friday, September 23, 2011 6:24 PM
  • Hi mhashemi,

    Any updates?

    Frank Wang

    Monday, September 26, 2011 1:58 AM
  • Hi mhashemi,

    Any updates?

    Frank Wang

    Wednesday, September 28, 2011 1:40 AM