Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 492 Source: ESE
<process name> (<process id>) The logfile sequence in "<directory name>" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Why are some errors fatal?
Error: -510. As per ME970671, you may get this on a clustered Exchange 2007 under heavy load. See the article on how you may eliminate these events by increasing the timeout on the database resources.
This event indicates that the database engine is unable to replay the log file sequence. See MSEX2K3DB for additional information about this event.
See the link to "EventID 492 from source ESE98" for information on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 492 from source ESE98, MSEX2K3DB, ME970671|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated