Home Sectie blog System Center Operations Manager 2007 R2 SCOM - All default Event/Alerts numbers
SCOM - All default Event/Alerts numbers PDF Print E-mail



System Center Operations Manager Logo from Oostdam.InfoSystem Center Operations Manager 2007 R2 is a great product! You can find a lot of information about this product and the way it works on the internet. Sometimes however, problem and solutions are not so well documented. I managed to list all the default event alerts you can normally run into. Use the search function with Ctrl+F and find the number your looking for.f Enjoy!! and welcome to the world of System Center, which makes the working as an Enterprise System Administrator a lot more easy! This artice is written in the English language, as statistics showed that most visitors of this page are from English speaking countries.


Overview of all default System Center Operations Managers 2007 R2 Events:

1HealthServiceOperations Manager1Health Service
1OpsMgr ConnectorOperations Manager1Health Service
1Health Service ModulesOperations Manager1Health Service Module
1Health Service ESE StoreOperations Manager1General
2HealthServiceOperations Manager2Health Service Executive
2OpsMgr ConnectorOperations Manager2Health Service Executive
2Health Service ModulesOperations Manager2Notification
2Health Service ESE StoreOperations Manager2Database Page Cache
3HealthServiceOperations Manager3Configuration Manager
3OpsMgr ConnectorOperations Manager3Configuration Manager
3Health Service ModulesOperations Manager3Data Warehouse
3Health Service ESE StoreOperations Manager3Logging/Recovery
4HealthServiceOperations Manager4Connector Manager
4OpsMgr ConnectorOperations Manager4Connector Manager
4Health Service ModulesOperations Manager4AD Agent Assignment
4Health Service ESE StoreOperations Manager4Space Management
5HealthServiceOperations Manager5Persistence Manager
5OpsMgr ConnectorOperations Manager5Persistence Manager
5Health Service ESE StoreOperations Manager5Table/Column/Index Definition
6HealthServiceOperations Manager6Execution Manager
6OpsMgr ConnectorOperations Manager6Execution Manager
6Health Service ESE StoreOperations Manager6Record Manipulation
7HealthServiceOperations Manager7Health Manager
7OpsMgr ConnectorOperations Manager7Health Manager
7Health Service ESE StoreOperations Manager7Performance
8HealthServiceOperations Manager8Performance Manager
8OpsMgr ConnectorOperations Manager8Performance Manager
8Health Service ESE StoreOperations Manager8Database Repair
9HealthServiceOperations Manager9Secure Storage Manager
9OpsMgr ConnectorOperations Manager9Secure Storage Manager
9Health Service ESE StoreOperations Manager9Database Conversion
10HealthServiceOperations Manager10Data Publisher Manager
10OpsMgr ConnectorOperations Manager10Data Publisher Manager
10Health Service ESE StoreOperations Manager10Online Defragmentation
11Health Service ESE StoreOperations Manager11System Parameter Settings
12Health Service ESE StoreOperations Manager12Database Corruption
13Health Service ESE StoreOperations Manager13Database Zeroing
14Health Service ESE StoreOperations Manager14Transaction Manager
15Health Service ESE StoreOperations Manager15Resource Failure Simulation
16Health Service ESE StoreOperations Manager16ShadowCopy
17Health Service ESE StoreOperations Manager17<EOL>
100HealthServiceOperations Manager100Crashing Events  
100Health Service ESE StoreOperations Manager100%1 (%2) %3The database engine %4.%5.%6.%7 started.
101HealthServiceOperations Manager3221225573The Health Service encountered a fatal error from ESE indicating that the database was corrupt.The error code was %1.The database will be deleted and re-created.
101HealthServiceOperations Manager101Hanging Events
101OpsMgr ConnectorOperations Manager3221225573The Health Service encountered a fatal error from ESE indicating that the database was corrupt.The error code was %1.The database will be deleted and re-created.
101Health Service ESE StoreOperations Manager101%1 (%2) %3The database engine stopped.
102HealthServiceOperations Manager3221225574Removing corrupt state directory "%1" failed with error code %2.The service will try to continue to run.
102OpsMgr ConnectorOperations Manager3221225574Removing corrupt state directory "%1" failed with error code %2.The service will try to continue to run.
102Health Service ESE StoreOperations Manager102%1 (%2) %3The database engine (%5.%6.%7.%8) started a new instance (%4).
103HealthServiceOperations Manager2147483751A task to reset the health service store has been submitted.The service store will be deleted and re-created.
103OpsMgr ConnectorOperations Manager2147483751A task to reset the health service store has been submitted.The service store will be deleted and re-created.
103Health Service ESE StoreOperations Manager103%1 (%2) %3The database engine stopped the instance (%4).
104HealthServiceOperations Manager3221225576The Health Service can only supports running as the local system user account.The service was configured to run under a different user account so it can not start.Please reset the service configuration back to the default setting.
104OpsMgr ConnectorOperations Manager3221225576The Health Service can only supports running as the local system user account.The service was configured to run under a different user account so it can not start.Please reset the service configuration back to the default setting.
104Health Service ESE StoreOperations Manager104%1 (%2) %3The database engine stopped the instance (%4) with error (%5).
200Health Service ESE StoreOperations Manager200%1 (%2) %3The database engine is starting a full backup.
201Health Service ESE StoreOperations Manager201%1 (%2) %3The database engine is starting an incremental backup.
202Health Service ESE StoreOperations Manager202%1 (%2) %3The database engine has completed the backup procedure successfully.
203Health Service ESE StoreOperations Manager203%1 (%2) %3The database engine has stopped the backup with error %4.
204Health Service ESE StoreOperations Manager204%1 (%2) %3The database engine is restoring from backup. Restore will begin replaying logfiles in folder %4 and continue rolling forward logfiles in folder %5.
205Health Service ESE StoreOperations Manager205%1 (%2) %3The database engine has stopped restoring.
206Health Service ESE StoreOperations Manager206%1 (%2) %3Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup.
207Health Service ESE StoreOperations Manager207%1 (%2) %3The database engine has stopped backup because it was halted by the client or the connection with the client failed.
210Health Service ESE StoreOperations Manager210%1 (%2) %3A full backup is starting.
211Health Service ESE StoreOperations Manager211%1 (%2) %3An incremental backup is starting.
212Health Service ESE StoreOperations Manager212%1 (%2) %3A shadow copy backup is starting.
213Health Service ESE StoreOperations Manager213%1 (%2) %3The backup procedure has been successfully completed.
214Health Service ESE StoreOperations Manager214%1 (%2) %3The backup has stopped with error %4.
215Health Service ESE StoreOperations Manager215%1 (%2) %3The backup has been stopped because it was halted by the client or the connection with the client failed.
216Health Service ESE StoreOperations Manager216%1 (%2) %3A database location change was detected from '%4' to '%5'.
217Health Service ESE StoreOperations Manager217%1 (%2) %3Error (%4) during backup of a database (file %5). The database will be unable to restore.
218Health Service ESE StoreOperations Manager218%1 (%2) %3Error (%4) during backup of file %5.
219Health Service ESE StoreOperations Manager219%1 (%2) %3Error (%4) occured during database headers update with the backup information.
220Health Service ESE StoreOperations Manager220%1 (%2) %3Beginning the backup of the file %4 (size %5).
221Health Service ESE StoreOperations Manager221%1 (%2) %3Ending the backup of the file %4.
222Health Service ESE StoreOperations Manager222%1 (%2) %3Ending the backup of the file %4. Not all data in the file has been read (read %5 bytes out of %6 bytes).
223Health Service ESE StoreOperations Manager223%1 (%2) %3Starting the backup of log files (range %4 - %5). 
224Health Service ESE StoreOperations Manager224%1 (%2) %3Deleting log files %4 to %5.
225Health Service ESE StoreOperations Manager225%1 (%2) %3No log files can be truncated.
226Health Service ESE StoreOperations Manager226%1 (%2) %3The backup has been stopped prematurely (possibly because the instance is terminating).
227Health Service ESE StoreOperations Manager227%1 (%2) %3There were %4 log file(s) not found in the log range we attempted to truncate.
300Health Service ESE StoreOperations Manager300%1 (%2) %3The database engine is initiating recovery steps.
301Health Service ESE StoreOperations Manager301%1 (%2) %3The database engine has begun replaying logfile %4.
302Health Service ESE StoreOperations Manager302%1 (%2) %3The database engine has successfully completed recovery steps.
303Health Service ESE StoreOperations Manager303%1 (%2) %3Database engine error %4 occurred.
304Health Service ESE StoreOperations Manager304%1 (%2) %3The database engine has successfully completed replay steps.
398Health Service ESE StoreOperations Manager398%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted and was corrected but page verification failed with error %7.This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file.Please contact your hardware vendor for further assistance diagnosing the problem.
399Health Service ESE StoreOperations Manager399%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted and has been corrected.This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file.Please contact your hardware vendor for further assistance diagnosing the problem.
400Health Service ESE StoreOperations Manager400%1 (%2) %3Synchronous overlapped read page time error %4 occurred. If this error persists, please restore the database from a previous backup.
401Health Service ESE StoreOperations Manager401%1 (%2) %3Synchronous overlapped write page issue error %4 occurred.
402Health Service ESE StoreOperations Manager402%1 (%2) %3Synchronous overlapped write page error %4 occurred.
403Health Service ESE StoreOperations Manager403%1 (%2) %3Synchronous overlapped patch file write page error %4 occurred.
404Health Service ESE StoreOperations Manager404%1 (%2) %3Synchronous read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.
405Health Service ESE StoreOperations Manager405%1 (%2) %3Pre-read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.
406Health Service ESE StoreOperations Manager406%1 (%2) %3Direct read found corrupted page %4 with error %5. If this error persists, please restore the database from a previous backup.
407Health Service ESE StoreOperations Manager407%1 (%2) %3Buffer I/O thread termination error %4 occurred.
408Health Service ESE StoreOperations Manager408%1 (%2) %3Unable to write to logfile %4. Error %5.
409Health Service ESE StoreOperations Manager409%1 (%2) %3Unable to write to the header of logfile %4. Error %5.
410Health Service ESE StoreOperations Manager410%1 (%2) %3Unable to read logfile %4. Error %5.
411Health Service ESE StoreOperations Manager411%1 (%2) %3The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version for the database.
412Health Service ESE StoreOperations Manager412%1 (%2) %3Unable to read the header of logfile %4. Error %5.
413Health Service ESE StoreOperations Manager413%1 (%2) %3Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error %4.
414Health Service ESE StoreOperations Manager414%1 (%2) %3Unable to write to section 0 while flushing logfile %4. Error %5.
415Health Service ESE StoreOperations Manager415%1 (%2) %3Unable to write to section 1 while flushing logfile %4. Error %5.
416Health Service ESE StoreOperations Manager416%1 (%2) %3Unable to write to section 2 while flushing logfile %4. Error %5.
417Health Service ESE StoreOperations Manager417%1 (%2) %3Unable to write to section 3 while flushing logfile %4. Error %5.
418Health Service ESE StoreOperations Manager418%1 (%2) %3Error %5 occurred while opening a newly-created logfile %4.
419Health Service ESE StoreOperations Manager419%1 (%2) %3Unable to read page %5 of database %4. Error %6.
420Health Service ESE StoreOperations Manager420%1 (%2) %3Unable to read the header of database %4. Error %5. The database may have been moved and therefore may no longer be located where the logs expect it to be.
421Health Service ESE StoreOperations Manager421%1 (%2) %3The database %4 created at %5 was not recovered. The recovered database was created at %5.
422Health Service ESE StoreOperations Manager422%1 (%2) %3The database %4 created at %5 was not recovered.
423Health Service ESE StoreOperations Manager423%1 (%2) %3The database engine found a bad page.
424Health Service ESE StoreOperations Manager424%1 (%2) %3The database disk is full. Deleting logfiles to recover disk space may make the database unstartable if the database file(s) are not in a Clean Shutdown state. Numbered logfiles may be moved, but not deleted, if and only if the database file(s) are in a Clean Shutdown state. Do not move %4.
425Health Service ESE StoreOperations Manager425%1 (%2) %3The database signature does not match the log signature for database %4.
426Health Service ESE StoreOperations Manager426%1 (%2) %3The database engine could not find the file or folder called %4.
427Health Service ESE StoreOperations Manager427%1 (%2) %3The database engine could not access the file called %4.
428Health Service ESE StoreOperations Manager428%1 (%2) %3The database engine is rejecting update operations due to low free disk space on the log disk.
429Health Service ESE StoreOperations Manager429%1 (%2) %3The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database file(s) are not in a Clean Shutdown state. Numbered logfiles may be moved, but not deleted, if and only if the database file(s) are in a Clean Shutdown state. Do not move %4.
430Health Service ESE StoreOperations Manager430%1 (%2) %3Database %4 and its patch file do not match.
431Health Service ESE StoreOperations Manager431%1 (%2) %3The starting restored logfile %4 is too high. It should start from logfile %5.
432Health Service ESE StoreOperations Manager432%1 (%2) %3The ending restored logfile %4 is too low. It should end at logfile %5.
433Health Service ESE StoreOperations Manager433%1 (%2) %3The restored logfile %4 does not have the correct log signature.
434Health Service ESE StoreOperations Manager434%1 (%2) %3The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it.
435Health Service ESE StoreOperations Manager435%1 (%2) %3The restored logfile %4 is missing.
436Health Service ESE StoreOperations Manager436%1 (%2) %3The signature of logfile %4 does not match other logfiles. Recovery cannot succeed unless all signatures match. Logfiles %5 to %6 have been deleted.
437Health Service ESE StoreOperations Manager437%1 (%2) %3There is a gap in sequence number between logfile %4 and the logfiles previous to it. Logfiles %5 to 0x%6 have been deleted so that recovery can complete.
438Health Service ESE StoreOperations Manager438%1 (%2) %3The backup database %4 must be a multiple of 4 KB.
439Health Service ESE StoreOperations Manager439%1 (%2) %3Unable to write a shadowed header for file %4. Error %5.
440Health Service ESE StoreOperations Manager440%1 (%2) %3The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.
441Health Service ESE StoreOperations Manager441%1 (%2) %3File system error %5 during IO on database %4. If this error persists, the database file may be damaged and may need to be restored from a previous backup.
442Health Service ESE StoreOperations Manager442%1 (%2) %3IO size mismatch on database %4, IO size %5 expected while returned size is %6.
443Health Service ESE StoreOperations Manager443%1 (%2) %3File system error %5 during IO on logfile %4.
444Health Service ESE StoreOperations Manager444%1 (%2) %3IO size mismatch on logfile %4, IO size %5 expected while returned size is %6.
445Health Service ESE StoreOperations Manager445%1 (%2) %3The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
446Health Service ESE StoreOperations Manager446%1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed.
447Health Service ESE StoreOperations Manager447%1 (%2) %3A bad page link (error %4) has been detected in a B-Tree (ObjectId: %5, PgnoRoot: %6) of database %7 (%8 => %9, %10).
448Health Service ESE StoreOperations Manager448%1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).
449Health Service ESE StoreOperations Manager449%1 (%2) %3Streaming data allocation inconsistency detected (%4,%5).
450Health Service ESE StoreOperations Manager450%1 (%2) %3A gap in the logfile sequence was detected. Logfile %4 is missing.Other logfiles past this one may also be required. This message may appear again if the missing logfiles are not restored.
451Health Service ESE StoreOperations Manager451%1 (%2) %3Unable to write to section 4 while flushing logfile %4. Error %5.
452Health Service ESE StoreOperations Manager452%1 (%2) %3Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7.
453Health Service ESE StoreOperations Manager453%1 (%2) %3Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to %7 (%10).
454Health Service ESE StoreOperations Manager454%1 (%2) %3Database recovery/restore failed with unexpected error %4.
455Health Service ESE StoreOperations Manager455%1 (%2) %3Error %5 occurred while opening logfile %4.
456Health Service ESE StoreOperations Manager456%1 (%2) %3The primary header page of file %4 was damaged. The shadow header page was used instead.
457Health Service ESE StoreOperations Manager457%1 (%2) %3The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed unless all signatures match.
458Health Service ESE StoreOperations Manager458%1 (%2) %3The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available logfiles.
459Health Service ESE StoreOperations Manager459%1 (%2) %3The file %4 is missing and could not be backed-up.
460Health Service ESE StoreOperations Manager460%1 (%2) %3A torn-write was detected while restoring from backup in logfile %4 of the backup set. The failing checksum record is located at position %5. This logfile has been damaged and is unusable.
461Health Service ESE StoreOperations Manager461%1 (%2) %3A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This logfile has been damaged and is unusable.
462Health Service ESE StoreOperations Manager462%1 (%2) %3A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The logfile damage will be repaired and recovery will continue to proceed.
463Health Service ESE StoreOperations Manager463%1 (%2) %3Corruption was detected while restoring from backup logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.
464Health Service ESE StoreOperations Manager464%1 (%2) %3Corruption was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.
465Health Service ESE StoreOperations Manager465%1 (%2) %3Corruption was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.
466Health Service ESE StoreOperations Manager466%1 (%2) %3An invalid checksum record in logfile %4 was patched using its shadow sector copy.
467Health Service ESE StoreOperations Manager467%1 (%2) %3Database %6: Index %4 of table %5 is corrupted (%7).
468Health Service ESE StoreOperations Manager468%1 (%2) %3Unable to write to section 5 while flushing logfile %4. Error %5.
470Health Service ESE StoreOperations Manager470%1 (%2) %3Database %4 is partially attached. Attachment stage: %5. Error: %6.
471Health Service ESE StoreOperations Manager471%1 (%2) %3Unable to rollback operation #%4 on database %5. Error: %6. All future database updates will be rejected.
472Health Service ESE StoreOperations Manager472%1 (%2) %3The shadow header page of file %4 was damaged. The primary header page was used instead.
473Health Service ESE StoreOperations Manager473%1 (%2) %3Database %4 was partially detached.Error %5 encountered updating database headers.
474Health Service ESE StoreOperations Manager474%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page checksum mismatch.The expected checksum was %8 and the actual checksum was %9.The read operation will fail with error %7.If this condition persists then please restore the database from a previous backup.This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
475Health Service ESE StoreOperations Manager475%1 (%2) %3The database page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch.The expected page number was %8 and the actual page number was %9.The read operation will fail with error %7.If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
476Health Service ESE StoreOperations Manager476%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains no page data.The read operation will fail with error %7.If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
477Health Service ESE StoreOperations Manager477%1 (%2) %3The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch.The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7.If this condition persists then please restore the logfile from a previous backup.
478Health Service ESE StoreOperations Manager478%1 (%2) %3The streaming page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch.The expected checksum was %8 and the actual checksum was %9.The read operation will fail with error %7.If this condition persists then please restore the database from a previous backup.
479Health Service ESE StoreOperations Manager479%1 (%2) %3The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch.The expected checksum was %8 and the actual checksum was %9.The read operation will fail with error %7.If this condition persists then please restore using an earlier backup set.
480Health Service ESE StoreOperations Manager480%1 (%2) %3The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch.The expected page number was %8 and the actual page number was %9.The read operation will fail with error %7.If this condition persists then please restore using an earlier backup set.
481Health Service ESE StoreOperations Manager481%1 (%2) %3An attempt to read from the file "%4" at offset %5 for %6 bytes failed after %10 seconds with system error %8: "%9".The read operation will fail with error %7.If this error persists then the file may be damaged and may need to be restored from a previous backup.
482Health Service ESE StoreOperations Manager482%1 (%2) %3An attempt to write to the file "%4" at offset %5 for %6 bytes failed after %10 seconds with system error %8: "%9".The write operation will fail with error %7.If this error persists then the file may be damaged and may need to be restored from a previous backup.
483Health Service ESE StoreOperations Manager483%1 (%2) %3An attempt to create the folder "%4" failed with system error %6: "%7".The create folder operation will fail with error %5.
484Health Service ESE StoreOperations Manager484%1 (%2) %3An attempt to remove the folder "%4" failed with system error %6: "%7".The remove folder operation will fail with error %5.
485Health Service ESE StoreOperations Manager485%1 (%2) %3An attempt to delete the file "%4" failed with system error %6: "%7".The delete file operation will fail with error %5.
486Health Service ESE StoreOperations Manager486%1 (%2) %3An attempt to move the file "%4" to "%5" failed with system error %7: "%8".The move file operation will fail with error %6.
487Health Service ESE StoreOperations Manager487%1 (%2) %3An attempt to copy the file "%4" to "%5" failed with system error %7: "%8".The copy file operation will fail with error %6.
488Health Service ESE StoreOperations Manager488%1 (%2) %3An attempt to create the file "%4" failed with system error %6: "%7".The create file operation will fail with error %5.
489Health Service ESE StoreOperations Manager489%1 (%2) %3An attempt to open the file "%4" for read only access failed with system error %6: "%7".The open file operation will fail with error %5.
490Health Service ESE StoreOperations Manager490%1 (%2) %3An attempt to open the file "%4" for read / write access failed with system error %6: "%7".The open file operation will fail with error %5.
491Health Service ESE StoreOperations Manager491%1 (%2) %3An attempt to determine the minimum I/O block size for the volume "%4" containing "%5" failed with system error %7: "%8".The operation will fail with error %6.
492Health Service ESE StoreOperations Manager492%1 (%2) %3The logfile sequence in "%4" 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.
493Health Service ESE StoreOperations Manager493%1 (%2) %3A read operation on the file "%4" at offset %5 for %6 bytes failed %7 times over an interval of %8 seconds before finally succeeding.More specific information on these failures was reported previously.Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file.
494Health Service ESE StoreOperations Manager494%1 (%2) %3Database recovery failed with error %4 because it encountered references to a database, '%5', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.
495Health Service ESE StoreOperations Manager495%1 (%2) %3Database recovery on '%5' failed with error %4. The database is not in the state expected at the first reference of this database in the log files. It is likely that a file copy of this database was restored, but not all log files since the file copy was made are currently available. Procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.
496Health Service ESE StoreOperations Manager496%1 (%2) %3Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7.
497Health Service ESE StoreOperations Manager497%1 (%2) %3From information provided by the headers of %4, the file is not a database file. The headers of the file may be corrupted.
498Health Service ESE StoreOperations Manager498%1 (%2) %3There is a gap in log sequence numbers, last used log file has generation %4. Logfiles %5 to %6 have been deleted so that recovery can complete.
499Health Service ESE StoreOperations Manager499%1 (%2) %3There is a gap in log sequence numbers, last used log file has generation %4. Logfile %5 (generation %6) have been deleted so that recovery can complete.
500Health Service ESE StoreOperations Manager500%1 (%2) %3The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
501Health Service ESE StoreOperations Manager501%1 (%2) %3The database engine repaired one page link.
502Health Service ESE StoreOperations Manager502%1 (%2) %3The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
503Health Service ESE StoreOperations Manager503%1 (%2) %3The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
504Health Service ESE StoreOperations Manager504%1 (%2) %3The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
505Health Service ESE StoreOperations Manager505%1 (%2) %3An attempt to open the compressed file "%4" for read / write access failed because it could not be converted to a normal file.The open file operation will fail with error %5.To prevent this error in the future you can manually decompress the file and change the compression state of the containing folder to uncompressed.Writing to this file when it is compressed is not supported.
506Health Service ESE StoreOperations Manager506%1 (%2) %3An attempt to determine the amount of free/total space for the volume "%4" containing "%5" failed with system error %7: "%8".The operation will fail with error %6.
507Health Service ESE StoreOperations Manager507%1 (%2) %3A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
508Health Service ESE StoreOperations Manager508%1 (%2) %3A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
509Health Service ESE StoreOperations Manager509%1 (%2) %3A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to be serviced by the OS. In addition, %8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted %9 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
510Health Service ESE StoreOperations Manager510%1 (%2) %3A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to be serviced by the OS. In addition, %8 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted %9 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
512Health Service ESE StoreOperations Manager512%1 (%2) %3The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). 
513Health Service ESE StoreOperations Manager513%1 (%2) %3The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). In addition, %7 other %4 tasks have also taken an abnormally long time to be serviced since the last message regarding this problem was posted %8 seconds ago.
514Health Service ESE StoreOperations Manager514%1 (%2) %3Log sequence numbers for this instance have almost been completely consumed. The current log generation is %4 which is approaching the maximum log generation of %5, there are %6 log generations left to be used. To begin renumbering from generation 1, the instance must be shutdown cleanly and all log files must be deleted. Backups will be invalidated.
515Health Service ESE StoreOperations Manager515%1 (%2) %3Database %4: Page %5 failed verification due to a flush-order dependency mismatch.This page should have flushed before page %6, but the latter page has instead flushed first. Recovery/restore will fail with error %7. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on one or both of these pages sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.
516Health Service ESE StoreOperations Manager516%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch.The expected timestamp was %6 but the actual timestamp on the page was %7.Recovery/restore will fail with error %8.If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.
517Health Service ESE StoreOperations Manager517%1 (%2) %3Database recovery failed with error %4 because it encountered references to a database, '%5', which does not match the current set of logs. The database engine will not permit recovery to complete for this instance until the mismatching database is re-instated. If the database is truly no longer available or no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.
518Health Service ESE StoreOperations Manager518%1 (%2) %3The log file %4 is missing (error %5) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.
519Health Service ESE StoreOperations Manager519%1 (%2) %3The range of log files %4 to %5 is missing (error %6) and cannot be used. If these log files are required for recovery, a good copy of these log files will be needed for recovery to complete successfully.
520Health Service ESE StoreOperations Manager520%1 (%2) %3Log truncation failed because not all log files required for recovery were successfully copied.
521Health Service ESE StoreOperations Manager521%1 (%2) %3Unable to schedule a log write on log file %4. Error %5.
522Health Service ESE StoreOperations Manager522%1 (%2) %3An attempt to open the device name "%4" containing "%5" failed with system error %7: "%8".The operation will fail with error %6.
523Health Service ESE StoreOperations Manager523%1 (%2) %3Database %4 requires log files %5-%6 in order to recover all committed data.Recovery could only locate up to log file: %7, and could not locate log generation %8.If the log file cannot be found, the database(s) can be recovered manually, but will result in losing committed data.%nDetails:%n%tLog directory: %9
524Health Service ESE StoreOperations Manager524%1 (%2) %3Database %4 has lost %5 committed log files (%6-%7), however lost log resilience has allowed ESE to recover this database to a consistent state, but with data loss.Recovery could only locate log files up to %8.%nDetails:%n%tLog directory: %9
525Health Service ESE StoreOperations Manager525%1 (%2) %3The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If the log file cannot be found, the database(s) can still be recovered manually, but will result in losing committed data.%nDetails:%n%tLog directory: %6
526Health Service ESE StoreOperations Manager526%1 (%2) %3The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since this committed logs are specified as unneeded, so that ESE can recover (through generation %4) any attached databases to a consistent state, but with data loss.%nDetails:%n%tLog directory: %8
527Health Service ESE StoreOperations Manager527%1 (%2) %3ESE has removed %4 committed log files (%5-%6) to maintain an in order log stream.However lost log resilience has allowed ESE to recover to a consistent state, but with data loss.Recovery could only recover through log files up to %7.%nDetails:%n%tLog directory: %8
528Health Service ESE StoreOperations Manager528%1 (%2) %3Recovery could only locate up to log file: %4 (generation %5) before detecting an out of sequence logs, and could not locate log generation %6.If the log file cannot be found, the database(s) can be recovered manually, but will result in losing committed data.%nDetails:%n%tLog directory: %7
529Health Service ESE StoreOperations Manager529%1 (%2) %3The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. The read operation will fail with error %7.If this condition persists then please restore the logfile from a previous backup.
600Health Service ESE StoreOperations Manager600%1 (%2) %3The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped.
601Health Service ESE StoreOperations Manager601%1 (%2) %3The database engine could not find the entrypoint %4 in the file %5.
602Health Service ESE StoreOperations Manager602%1 (%2) %3Database '%4': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during off-peak hours. If this message persists, offline defragmentation may be run to remove all skipped pages from the database.
603Health Service ESE StoreOperations Manager603%1 (%2) %3Database '%4': The database engine lost unused pages %5-%6 while attempting space reclamation on a B-Tree (ObjectId %7). The space may not be reclaimed again until offline defragmentation is performed.
604Health Service ESE StoreOperations Manager604%1 (%2) %3Locale ID %4 (%5 %6) is either invalid or not installed on this machine.
605Health Service ESE StoreOperations Manager605%1 (%2) %3Column '%4' of Table '%5' was converted to a Tagged column.
606Health Service ESE StoreOperations Manager606%1 (%2) %3Column '%4' of Table '%5' was converted to a non-Tagged column.
607Health Service ESE StoreOperations Manager607%1 (%2) %3Column '%4' of Table '%5' was converted from Binary to LongBinary.
608Health Service ESE StoreOperations Manager608%1 (%2) %3Column '%4' of Table '%5' was converted from Text to LongText.
609Health Service ESE StoreOperations Manager609%1 (%2) %3The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade from %5.%6.%7 SP%8 to %9.%10.%11 SP%12. This message is informational and does not indicate a problem in the database.
610Health Service ESE StoreOperations Manager610%1 (%2) %3The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade to %5.%6.%7 SP%8. This message is informational and does not indicate a problem in the database.
611Health Service ESE StoreOperations Manager611%1 (%2) %3Database '%4': The secondary index '%5' of table '%6' will be rebuilt as a precautionary measure after the Windows version upgrade of this system. This message is informational and does not indicate a problem in the database.
612Health Service ESE StoreOperations Manager612%1 (%2) %3The database engine has successfully completed index cleanup on database '%4'.
613Health Service ESE StoreOperations Manager613%1 (%2) %3Database '%4': The primary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.
614Health Service ESE StoreOperations Manager614%1 (%2) %3Database '%4': The secondary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.
615Health Service ESE StoreOperations Manager615%1 (%2) %3The database engine is converting the database '%4' from format %5 to format %6.
616Health Service ESE StoreOperations Manager616%1 (%2) %3The database engine has successfully converted the database '%4' from format %5 to format %6.
617Health Service ESE StoreOperations Manager617%1 (%2) %3Attempted to use database '%4', but conversion did not complete successfully on this database. Please restore from backup and re-run database conversion.
618Health Service ESE StoreOperations Manager618%1 (%2) %3Database '%4': The database engine has built an in-memory cache of %5 space tree nodes on a B-Tree (ObjectId: %6, PgnoRoot: %7) to optimize space requests for that B-Tree. The space cache was built in %8 milliseconds. This message is informational and does not indicate a problem in the database.
619Health Service ESE StoreOperations Manager619%1 (%2) %3Attempted to attach database '%4' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.
620Health Service ESE StoreOperations Manager620%1 (%2) %3Unable to convert record format for record %4:%5:%6.
621Health Service ESE StoreOperations Manager621%1 (%2) %3Database '%4': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation of the database.
622Health Service ESE StoreOperations Manager622%1 (%2) %3Database '%4': Available B-Tree IDs (ObjectIDs) have almost been completely consumed. Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation of the database.
623Health Service ESE StoreOperations Manager623%1 (%2) %3The version store for this instance (%4) has reached its maximum size of %5Mb. 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.%nPossible long-running transaction:%n%tSessionId: %6%n%tSession-context: %7%n%tSession-context ThreadId: %8%n%tCleanup: %9
624Health Service ESE StoreOperations Manager624%1 (%2) %3The version store for this instance (%4) 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.%nCurrent version store size for this instance: %5Mb%nMaximum version store size for this instance: %6Mb%nGlobal memory pre-reserved for all version stores: %7Mb%nPossible long-running transaction:%n%tSessionId: %8%n%tSession-context: %9%n%tSession-context ThreadId: %10%n%tCleanup: %11
625Health Service ESE StoreOperations Manager625%1 (%2) %3The database engine does not support the LCMapString() flags %4.
626Health Service ESE StoreOperations Manager626%1 (%2) %3The database engine updated %4 index entries in database %5 because of a change in the NLS version. This message is informational and does not indicate a problem in the database.
627Health Service ESE StoreOperations Manager627%1 (%2) %3The database engine was unable to updated index entries in database %5 because the database is read-only.
628Health Service ESE StoreOperations Manager628%1 (%2) %3Database '%4': While attempting to move to the next orprevious node in a B-Tree, the database engine skipped over %7non-visible nodes in %8 pages. It is likely that these non-visiblenodes are nodes which have been marked for deletion but which areyet to be purged. The database may benefit from widening the onlinemaintenance window during off-peak hours in order to purge such nodesand reclaim their space. If this message persists, offlinedefragmentation may be run to remove all nodes which have been markedfor deletion but are yet to be purged from the database.%n%tName: %5%n%tOwning Table: %6%n%tObjectId: %9%n%tPgnoRoot: %10%n%tType: %11%n%tUnversioned Deletes: %12%n%tUncommitted Deletes: %13%n%tCommitted Deletes: %14%n%tNon-Visible Inserts: %15
629Health Service ESE StoreOperations Manager629%1 (%2) %3Database '%4': While attempting to move to the next orprevious node in a B-Tree, the database engine skipped over %7non-visible nodes in %8 pages. In addition, since this message waslast reported %16 hours ago, %17 other incidents of excessivenon-visible nodes were encountered (a total of %18 nodes in %19 pageswere skipped) during navigation in this B-Tree. It is likely thatthese non-visible nodes are nodes which have been marked for deletionbut which are yet to be purged. The database may benefit fromwidening the online maintenance window during off-peak hours in orderto purge such nodes and reclaim their space. If this messagepersists, offline defragmentation may be run to remove all nodeswhich have been marked for deletion but have yet to be purged fromthe database.%n%tName: %5%n%tOwning Table: %6%n%tObjectId: %9%n%tPgnoRoot: %10%n%tType: %11%n%tUnversioned Deletes: %12%n%tUncommitted Deletes: %13%n%tCommitted Deletes: %14%n%tNon-Visible Inserts: %15
700Health Service ESE StoreOperations Manager700%1 (%2) %3Online defragmentation is beginning a full pass on database '%4'.
701Health Service ESE StoreOperations Manager701%1 (%2) %3Online defragmentation has completed a full pass on database '%4', freeing %5 pages. This pass started on %6 and ran for a total of %7 seconds, requiring %8 invocations over %9 days. Since the database was created it has been fully defragmented %10 times over %11 days.
702Health Service ESE StoreOperations Manager702%1 (%2) %3Online defragmentation is resuming its pass on database '%4'. This pass started on %5 and has been running for %6 days.
703Health Service ESE StoreOperations Manager703%1 (%2) %3Online defragmentation has completed the resumed pass on database '%4', freeing %5 pages. This pass started on %6 and ran for a total of %7 seconds, requiring %8 invocations over %9 days. Since the database was created it has been fully defragmented %10 times over %11 days.
704Health Service ESE StoreOperations Manager704%1 (%2) %3Online defragmentation of database '%4' was interrupted and terminated. The next time online defragmentation is started on this database, it will resume from the point of interruption.
705Health Service ESE StoreOperations Manager705%1 (%2) %3Online defragmentation of database '%4' terminated prematurely after encountering unexpected error %5. The next time online defragmentation is started on this database, it will resume from the point of interruption.
706Health Service ESE StoreOperations Manager706%1 (%2) %3Online zeroing of database %4 started
707Health Service ESE StoreOperations Manager707%1 (%2) %3Online zeroing of database %4 finished after %5 seconds with err %6%n%7 pages%n%8 blank pages%n%9 pages unchanged since last zero%n%10 unused pages zeroed%n%11 used pages seen%n%12 deleted records zeroed%n%13 unreferenced data chunks zeroed
708Health Service ESE StoreOperations Manager708%1 (%2) %3Online defragmentation is beginning a full pass on streaming file '%4'.
709Health Service ESE StoreOperations Manager709%1 (%2) %3Online defragmentation has completed a full pass on streaming file '%4'.
710Health Service ESE StoreOperations Manager710%1 (%2) %3Online defragmentation of streaming file '%4' has shrunk the file by %5 bytes.
711Health Service ESE StoreOperations Manager711%1 (%2) %3Online defragmentation of streaming file '%4' terminated prematurely after encountering unexpected error %5.
712Health Service ESE StoreOperations Manager712%1 (%2) %3Online zeroing of streaming file '%4' started.
713