Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 623 Source: ESE
<process name> (<PID>) The version store for instance <instance> ("<name>") has reached its maximum size of <value>Mb. 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: <value> Session-context: <value> Session-context ThreadId: <value>.
|English: Request a translation of the event description in plain English.|
We are doing an Outlook 2010 migration in a Exchange 2003 environment and this error has appeared to us. Apparently this issue occurs because of changes to the nickname cache in Outlook 2010. See ME2721098 for details.
You may experience slow client performance on server that is running Microsoft Exchange 2000 Server. This problem occurs if the version store runs out of memory. See ME891639 for a hotfix applicable to Microsoft Exchange 2000.
See ME893599, ME911836 and ME953952 for hotfixes applicable to Microsoft Exchange Server 2003.
If this problem occurs when you run long running transactions like migrations, etc., you might have to disable the caching of your Hard-disk controller. See ME288700 for additional information on this problem. This workaround worked fine for me.
When you are running Microsoft Exchange 2000 Server on a Microsoft Windows 2000 Server-based computer, the computer may stop responding and this event is logged. See ME329422 for a hotfix applicable to Microsoft Windows 2000.
If some of the e-mail users on your Exchange 2000 server cannot access their inboxes, see ME821547 for a hotfix applicable to Microsoft Exchange 2000 Server.
As per Microsoft: "On a computer that is running Microsoft Exchange 2000 Server, the Microsoft Exchange Information Store service may intermittently stop responding (hang) when it tries to update the mailbox table during a database transaction". See ME892396 for a hotfix applicable to Microsoft Exchange 2000 Server.
See ME815417 and the link to "EventID 623 from source ESE98" for more information on this event.
For some instances of this error, Microsoft has confirmed that this was a bug fixed in Microsoft Exchange 2000 Server Service Pack 3. See ME318162.
As per ME317722, this may also occur when Exchange 2000 converts mail from MAPI to MIME format and there is a large number of clients using the POP3/IMAP services.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 623 from source ESE98|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated