Event ID: 624 Source: ESE98

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

EvLog 3.0 – Monitor an unlimited number of servers with $49/year

With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Event ID: 624 Source: ESE98

Source: ESE98

Type: Error

Description:
<process name> (<process id>) The version store for instance <ID> ("<name>") cannot grow because it is receiving Out-Of-Memory errors from the OS. 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. Current version store size for this instance: <value>Mb Maximum version store size for this instance: <value>Mb Global memory pre-reserved for all version stores: {number}Mb Possible long-running transaction: SessionId: <ID> Session-context: <value> Session-context ThreadId: <thread ID>.

English: Request a translation of the event description in plain English.

Comments:
EventID.Net
See MSEX2K3DB and the link to "EventID 624 from source ESE" for information on this event.
Click if the comment is good!

Private comment: Subscribers only. See example of private comment

Links: EventID 624 from source ESE, MSEX2K3DB

Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...

Feedback: Send comments or solutions - Notify me when updated

Printer friendly