Hacked By AnonymousFox

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/ESENT.dll.mui

MZ@	!L!This program cannot be run in DOS mode.

$<ߵRRRЫRЫPRRichRPEL!


@h@ 8.rdata@@.rsrc  @@n~]
T88n~]$8.rdata8x.rdata$zzzdbg .rsrc$01 .rsrc$02 0ln㭁	n~](@Xp			 !X4MUI.$Y1}˅ˬI7[,SMUIen-USdlx4P ",0H#EO&3z*X0&v (x		@8$%1 (%2) %3%4

General

0Database Page Cache

,Logging/Recovery

,Space Management

DTable/Column/Index Definition

0Record Manipulation

 Performance

(Database Repair

0Database Conversion

8Online Defragmentation

<System Parameter Settings

0Database Corruption

,Database Zeroing

0Transaction Manager

@Resource Failure Simulation

 ShadowCopy

$Failure Items

$System Device

<EOL>

p%1 (%2) %3The database engine %4.%5.%6.%7 started.

X%1 (%2) %3The database engine stopped.

%1 (%2) %3The database engine (%5.%6.%7.%8) is starting a new instance (%4).

%1 (%2) %3The database engine stopped the instance (%4).

%n

%nDirty Shutdown: %6

%n

%nInternal Timing Sequence: %5

%1 (%2) %3The database engine stopped the instance (%4) with error (%5).

%n

%nInternal Timing Sequence: %6

(%1 (%2) %3The database engine started a new instance (%4). (Time=%5 seconds)

%n

%nAdditional Data:%n

%7

%n

%nInternal Timing Sequence: %6

%1 (%2) %3The parameter %4 was attempted to be set to %5, but was overridden to %6 by the registry settings (at %7).

%1 (%2) %3The parameter %4 was read from the registry settings (at %7), but the ESE engine rejected the value %5 with err %6.

T%1 (%2) %3The specific ESE configuration store is locked in a read inhibit state, clear the %1 registry value to enable ESE to continue and utilize the config store.

|%1 (%2) %3The database engine is starting a full backup.

%1 (%2) %3The database engine is starting an incremental backup.

%1 (%2) %3The database engine has completed the backup procedure successfully.

%1 (%2) %3The database engine has stopped the backup with error %4.

H%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.

t%1 (%2) %3The database engine has stopped restoring.

%1 (%2) %3Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup.

%1 (%2) %3The database engine has stopped backup because it was halted by the client or the connection with the client failed.

T%1 (%2) %3A full backup is starting.

d%1 (%2) %3An incremental backup is starting.

`%1 (%2) %3A shadow copy backup is starting.

%1 (%2) %3The backup procedure has been successfully completed.

h%1 (%2) %3The backup has stopped with error %4.

%1 (%2) %3The backup has been stopped because it was halted by the client or the connection with the client failed.

%1 (%2) %3A database location change was detected from '%4' to '%5'.

%1 (%2) %3Error (%4) during backup of a database (file %5). The database will be unable to restore.

x%1 (%2) %3Error (%4) during copy or backup of file %5.

%1 (%2) %3Error (%4) occured during database headers update with the backup information.

%1 (%2) %3Starting the copy or backup of the file %4 (size %5).

p%1 (%2) %3Ending the copy or backup of the file %4.

%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).

%1 (%2) %3Starting the backup of log files (range %4 - %5). 

X%1 (%2) %3Deleting log files %4 to %5. 

\%1 (%2) %3No log files can be truncated. 

%1 (%2) %3The backup has been stopped prematurely (possibly because the instance is terminating).

%1 (%2) %3There were %4 log file(s) not found in the log range we attempted to truncate. 

,%1 (%2) %3An internal copy (for seeding or analysis purposes) is starting. The streaming ESE backup APIs are being used for the transfer method.

%1 (%2) %3The internal database copy (for seeding or analysis purposes) procedure has been successfully completed.

%1 (%2) %3The internal database copy (for seeding or analysis purposes) has stopped. Error: %4.

h%1 (%2) %3The internal database copy (for seeding or analysis purposes) has been stopped because it was halted by the client or because the connection with the client failed.

D%1 (%2) %3Ending the internal copy (for seeding or analysis purposes) of the file %4. Not all data in the file has been read (read %5 bytes out of %6 bytes).

0%1 (%2) %3The internal database copy (for seeding or analysis purposes) has been stopped prematurely, possibly because the instance is terminating.

%1 (%2) %3The database engine is initiating recovery steps.

@%1 (%2) %3The database engine has finished replaying logfile %4.

%n

%nProcessing Stats: %5

%nLog record of type '%6' was seen most frequently (%7 times)

%1 (%2) %3The database engine has successfully completed recovery steps.

d%1 (%2) %3Database engine error %4 occurred.

%1 (%2) %3The database engine has successfully completed replay steps.

(%1 (%2) %3The database engine created a new database (%4, %5). (Time=%6 seconds)

%n

%nAdditional Data: %9

%n

%nInternal Timing Sequence: %7

H%1 (%2) %3The database engine attached a database (%4, %5). (Time=%6 seconds)

%n

%nSaved Cache: %8

%nAdditional Data: %9

%n

%nInternal Timing Sequence: %7

L%1 (%2) %3The database engine detached a database (%4, %5). (Time=%6 seconds)

%n

%nRevived Cache: %8

%nAdditional Data: %9

%n

%nInternal Timing Sequence: %7

%1 (%2) %3The database engine has fired callback for attach of database %4 during recovery at log position %5. The callback returned %6.

%1 (%2) %3The database engine has fired callback for detach of database %4 during recovery at log position %5. The callback returned %6.

0%1 (%2) %3The database [%4] format version is being held back to %6 due to application parameter setting of %5. Current default engine version: %7.

%1 (%2) %3The database [%4] version was upgraded from %5 to %6. Current engine format version parameter setting: %7

%1 (%2) %3The database [%4] version %5 is higher than the maximum version understood by the engine %6.

H%1 (%2) %3The database [%4] version %5 is higher than the maximum version configured by the application %6. Current engine format version parameter setting: %7

@%1 (%2) %3The database [%4] has completed incremental reseed page patching operations for %5 pages.

%n

%nDetails:

%nRange of Patching: %6

%nTiming: %7

%1 (%2) %3Replay of a %4 for database "%5" at log position %6 was deferred due to %7.  Additional information:  %8

%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.

t%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.

(%1 (%2) %3Synchronous overlapped read page time error %4 occurred. If this error persists, please restore the database from a previous backup.

%1 (%2) %3Synchronous overlapped write page issue error %4 occurred.

%1 (%2) %3Synchronous overlapped write page error %4 occurred.

%1 (%2) %3Synchronous overlapped patch file write page error %4 occurred.

%1 (%2) %3Synchronous read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.

%1 (%2) %3Pre-read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.

%1 (%2) %3Direct read found corrupted page %4 with error %5. If this error persists, please restore the database from a previous backup.

%1 (%2) %3Buffer I/O thread termination error %4 occurred.

p%1 (%2) %3Unable to write to logfile %4. Error %5.

%1 (%2) %3Unable to write to the header of logfile %4. Error %5.

h%1 (%2) %3Unable to read logfile %4. Error %5.

8%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.

%1 (%2) %3Unable to read the header of logfile %4. Error %5.

p%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.

%1 (%2) %3Unable to write to section 0 while flushing logfile %4. Error %5.

%1 (%2) %3Unable to write to section 1 while flushing logfile %4. Error %5.

%1 (%2) %3Unable to write to section 2 while flushing logfile %4. Error %5.

%1 (%2) %3Unable to write to section 3 while flushing logfile %4. Error %5.

%1 (%2) %3Error %5 occurred while opening a newly-created logfile %4.

%1 (%2) %3Unable to read page %5 of database %4. Error %6.

T%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.

%1 (%2) %3The database %4 created at %5 was not recovered. The recovered database was created at %5.

%1 (%2) %3The database %4 created at %5 was not recovered.

h%1 (%2) %3The database engine found a bad page.

d%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.

%1 (%2) %3The database signature does not match the log signature for database %4.

%1 (%2) %3The database engine could not find the file or folder called %4.

%1 (%2) %3The database engine could not access the file called %4.

%1 (%2) %3The database engine is rejecting update operations due to low free disk space on the log disk.

|%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.

x%1 (%2) %3Database %4 and its patch file do not match.

%1 (%2) %3The starting restored logfile %4 is too high. It should start from logfile %5.

%1 (%2) %3The ending restored logfile %4 is too low. It should end at logfile %5.

%1 (%2) %3The restored logfile %4 does not have the correct log signature.

%1 (%2) %3The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it.

d%1 (%2) %3The restored logfile %4 is missing.

H%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.

T%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.

%1 (%2) %3The backup database %4 must be a multiple of 4 KB.

%1 (%2) %3Unable to write a shadowed header for file %4. Error %5.

%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.

T%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.

%1 (%2) %3IO size mismatch on database %4, IO size %5 expected while returned size is %6.

%1 (%2) %3File system error %5 during IO or flush on logfile %4.

%1 (%2) %3IO size mismatch on logfile %4, IO size %5 expected while returned size is %6.

T%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.

@%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.

%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).

%1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).

%1 (%2) %3Streaming data allocation inconsistency detected (%4,%5).

%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.

%1 (%2) %3Unable to write to section 4 while flushing logfile %4. Error %5.

%1 (%2) %3Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7.

$%1 (%2) %3Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to %7 (%10).

%1 (%2) %3Database recovery/restore failed with unexpected error %4.

t%1 (%2) %3Error %5 occurred while opening logfile %4.

%1 (%2) %3The primary header page of file %4 was damaged. The shadow header page (%5 bytes) was used instead.

L%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.

4%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.

%1 (%2) %3The file %4 is missing and could not be backed-up.

%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.

d%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.

%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.

%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.

%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.

%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.

%1 (%2) %3An invalid checksum record in logfile %4 was patched using its shadow sector copy.

%1 (%2) %3Database %6: Index %4 of table %5 is corrupted (%7).

%1 (%2) %3Unable to write to section 5 while flushing logfile %4. Error %5.

%1 (%2) %3Database %4 is partially attached. Attachment stage: %5. Error: %6.

%1 (%2) %3Unable to rollback operation #%4 on database %5. Error: %6. All future database updates will be rejected.

%1 (%2) %3The shadow header page of file %4 was damaged. The primary header page (%5 bytes) was used instead.

%1 (%2) %3Database %4 was partially detached.  Error %5 encountered updating database headers.

%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 stored checksum was %8 and the computed 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.

%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 stored 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.

@%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.

%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.

%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.

x%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.

%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.

4%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.

4%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.

%1 (%2) %3An attempt to create the folder "%4" failed with system error %6: "%7".  The create folder operation will fail with error %5.

%1 (%2) %3An attempt to remove the folder "%4" failed with system error %6: "%7".  The remove folder operation will fail with error %5.

%1 (%2) %3An attempt to delete the file "%4" failed with system error %6: "%7".  The delete file operation will fail with error %5.

%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.

%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.

%1 (%2) %3An attempt to create the file "%4" failed with system error %6: "%7".  The create file operation will fail with error %5.

4%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.

8%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.

`%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.

%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.

%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.

%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.

%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.

%1 (%2) %3Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7.

%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.

@%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.

P%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.

%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.

t%1 (%2) %3The database engine repaired one page link.

%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.

%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.

%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.

$%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.

h%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.

D%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.

D%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.

%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.

%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.

 %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).



`%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. 



%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.

 %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.

L%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10.  The 'before' timestamp persisted to the log record was %6 but the actual timestamp on the page was %7.  The 'after' update timestamp %9 that would have updated the on page timestamp.  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 some time in the past. Please contact your hardware vendor for further assistance diagnosing the problem.

%nAdditional information:

%n%tWithin initial required range: %11

%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.

%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.

%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.

%1 (%2) %3Log truncation failed because not all log files required for recovery were successfully copied.

%1 (%2) %3Unable to schedule a log write on log file %4. Error %5.

,%1 (%2) %3An attempt to open the device with name "%4" containing "%5" failed with system error %7: "%8". The operation will fail with error %6.

%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

%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

%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

H%1 (%2) %3The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these 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.

@%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

%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 file %6 (generation %7).  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: %8

%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, restore the logfile from a previous backup.

%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost flush detection timestamp mismatch. The read operation will fail with error %7.

%nThe flush state on database page %8 was %9 while the flush state on flush map page %10 was %11.

%nIf this condition persists, 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.

x%1 (%2) %3The database engine attempted a clean write operation on page %4 of database %5. This action was performed in an attempt to correct a previous problem reading from the page.

%1 (%2) %3A request to read from the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3A request to write to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

h%1 (%2) %3A patch request for file "%4" at page number "%5" has failed to be issued with error %6. If this condition persists then please restore using an earlier backup set.

8%1 (%2) %3An attempt to determine the minimum I/O block size for the volume containing "%4" failed.  The default sector-size of 512 bytes will be used.

%1 (%2) %3An attempt to create temporary database %4 failed with error %5.

X%1 (%2) %3A request for a node on an empty page (Pgno: %7) has been made (error %4) for a B-Tree (ObjectId: %5, PgnoRoot: %6) of database %8. This is typically due to a lost I/O from 

storage hardware. Please check with your hardware vendor for latest firmware revisions, make changes to your controller's caching parameters, use crash consistent hardware with Forced

Unit Access support, and/or replace faulty hardware.

%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10.  The remote ("before") timestamp persisted to the log record was %6 but the actual timestamp on the page was %7 (note: DbtimeCurrent = %9). This indicates the active node lost a flush (error %8). This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past on the active node. Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10.  The remote ("before") timestamp persisted to the log record was %6 but the actual timestamp on the page was %7 (note: DbtimeCurrent = %9). This indicates the passive node lost a flush (error %8). This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past on the passive node. Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3Database %4: Page %5 logical data checksum %6 failed to match logged scan check %7 checksum (seed %8) at log position %9.

t%1 (%2) %3Database %4: Page %5 was shown to be uninitialized at log position %8, while the remote ("before") timestamp persisted to the log record was %6 (note: DbtimeCurrent = %7).

%1 (%2) %3Database %4: Page %5 (objid %6) has a logical corruption of type '%7'.

%nDetails: %8

%1 (%2) %3Previous log's accumulated segment checksum mismatch in logfile %4, Expected: %5, Actual: %6.

$%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error %7.

%nThe flush state on database page %8 was %9 while the flush state on flush map page %10 was %11.

%nIf this condition persists, 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.

%1 (%2) %3Database %4: Page %5 appears to be uninitialized at log position %10 on the remote node.  The remote ("before") timestamp persisted to the log record was %6 but the actual timestamp on the page was %7 (note: DbtimeCurrent = %9). This indicates the active node lost a flush (error %8). This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past on the active node. Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3The log generation (%4) is too low (%5) to be supported or replayed by this database engine (min supported %6).

%1 (%2) %3The log generation (%4) is too high (%5) to be supported or replayed by this database engine (max supported %6).

X%1 (%2) %3The log generation's [%4] version %5 is higher than the maximum version configured by the application %6. Current engine format version parameter setting: %7

%1 (%2) %3A Database %4 has a page (pgno %5) with too few lines, operation attempted on line %6, actual number of lines on page %7.

%1 (%2) %3Database %4: A compressed LV chunk failed verification during decompression due to a checksum mismatch. This indicates a logical corruption in the compress/decompress pipeline.

pgnoFDP = %5. Key = %6.

,%1 (%2) %3An attempt to flush to the file/disk buffers of "%4" failed after %5 seconds with system error %6: "%7".  The flush operation will fail with error %8.  If this error persists then the file system may be damaged and may need to be restored from a previous backup.

X%1 (%2) %3The log file at "%4" is corrupt with reason '%5'. Last valid segment was %6, current segment is %7. The expected checksum was %8 and the actual checksum was %9. The read completed with error-code %10.  If this condition persists then please restore the logfile from a previous backup.

%1 (%2) %3Failed looking up restore-map entry for database %4 with unexpected error %5.

X%1 (%2) %3The log segment read from the file "%4" at offset %6 (segment number %5) 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.

%1 (%2) %3The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped.

%1 (%2) %3The database engine could not find the entrypoint %4 in the file %5.

%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.

%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.

d%1 (%2) %3Locale ID %4 (%5 %6) is either invalid, not installed on this machine or could not be validated with system error %7: "%8". The operation will fail with error %9.

%1 (%2) %3Column '%4' of Table '%5' was converted to a Tagged column.

%1 (%2) %3Column '%4' of Table '%5' was converted to a non-Tagged column.

%1 (%2) %3Column '%4' of Table '%5' was converted from Binary to LongBinary.

%1 (%2) %3Column '%4' of Table '%5' was converted from Text to LongText.

%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.

%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.

%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.

%1 (%2) %3The database engine has successfully completed index cleanup on database '%4'.

t%1 (%2) %3Database '%4': The primary index '%5' of table '%6' is out of date with sorting libraries. If used in this state (i.e. not rebuilt), it may appear corrupt or get further corrupted. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.

x%1 (%2) %3Database '%4': The secondary index '%5' of table '%6' is out of date with sorting libraries. If used in this state (i.e. not rebuilt), it may appear corrupt or get further corrupted. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.

%1 (%2) %3The database engine is converting the database '%4' from format %5 to format %6.

%1 (%2) %3The database engine has successfully converted the database '%4' from format %5 to format %6.

P%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.

p%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.

T%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.

%1 (%2) %3Unable to convert record format for record %4:%5:%6.

@%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.

%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.

%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

%n%tSession-trace:

%n%10

X%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

%n%tSession-trace:

%n%12

%1 (%2) %3The database engine does not support the LCMapString() flags %4.

%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.

%1 (%2) %3The database engine was unable to updated index entries in database %5 because the database is read-only.

D%1 (%2) %3Database '%4': While attempting to move to the next or

previous node in a B-Tree, the database engine took %17 milliseconds (waiting %18 milliseconds on faults) to skip over %7

non-visible nodes in %8 pages (faulting in %19 pages). It is likely that these non-visible

nodes are nodes which have been marked for deletion but which are

yet to be purged. The database may benefit from widening the online

maintenance window during off-peak hours in order to purge such nodes

and reclaim their space. If this message persists, offline

defragmentation may be run to remove all nodes which have been marked

for 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

%n%tFiltered: %16

%n%tDbtime Distrib: %20

	%1 (%2) %3Database '%4': While attempting to move to the next or

previous node in a B-Tree, the database engine took %21 milliseconds (waiting %22 milliseconds on faults) to skip over %7

non-visible nodes in %8 pages (faulting in %23 pages). In addition, since this message was

last reported %16 hours ago, %17 other incidents of excessive

non-visible nodes were encountered (a total of %18 nodes in %19 pages

were skipped) during navigation in this B-Tree. It is likely that

these non-visible nodes are nodes which have been marked for deletion

but which are yet to be purged. The database may benefit from

widening the online maintenance window during off-peak hours in order

to purge such nodes and reclaim their space. If this message

persists, offline defragmentation may be run to remove all nodes

which have been marked for deletion but have 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

%n%tFiltered: %20

%n%tDbtime Distrib: %24

t%1 (%2) %3The version store for this instance (%4) has a long-running transaction that exceeds the maximum transaction size.

%nCurrent version store size for this instance: %5Mb

%nMaximum transaction size for this instance: %6Mb

%nMaximum version store size for this instance: %7Mb

%nLong-running transaction:

%n%tSessionId: %8

%n%tSession-context: %9

%n%tSession-context ThreadId: %10

%n%tCleanup: %11

%n%tSession-trace:

%n%12

%1 (%2) %3The file system reports that the database file at %4 has a sector size of %5 which is greater than the page size of %6.  This may result in higher torn write corruption incidence and/or in database corruption via lost flushes.

%1 (%2) %3The file system reports that the log file at %4 has a sector size of %5 which is unsupported, using a sector size of 4096 instead.  This may result in transaction durability being lost.

8%1 (%2) %3Recovery had to pause (%4 ms) to allow an older read-only transaction to complete. If this condition persists, it can result in stale copies.

X%1 (%2) %3Recovery had to pause for a long time (%4 ms) to allow an older read-only transaction to complete. If this condition persists, it can result in stale copies.

%1 (%2) %3Failed to attach flush map file "%4" with error %5.

%1 (%2) %3Flush map file "%4" will be deleted. Reason: %5.

%1 (%2) %3New flush map file "%4" will be created to enable persisted lost flush detection.

%1 (%2) %3Error %4 validating page %5 on flush map file "%6". The flush type of the database pages will be set to 'unknown' state.

%1 (%2) %3Inconsistent timestamp detected on page %4 of flush map file "%5" (empty if flush map persistence in disabled). The maximum timestamp on the flush map is %6, but database page %7 has a timestamp of %8. If flush map persistence is enabled, this problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3Error %4 validating header page on flush map file "%5". The flush map file will be invalidated.

%nAdditional information: %6

%1 (%2) %3The log format feature version %5 could not be used due to the current log format %6, controlled by the parameter %4.

%1 (%2) %3The database format feature version %5 could not be used due to the current database format %6, controlled by the parameter %4.

p%1 (%2) %3 Out of date NLS sort version detected on the database '%4' for Locale '%5', index sort version: (SortId=%6, Version=%7), current sort version: (SortId=%8, Version=%9).

%1 (%2) %3A session has an outstanding transaction causing the checkpoint depth (of %4 logs) to exceed a quarter of the JET_paramCheckpointTooDeep setting.%n

%n

Details:%n

Transaction Context Info: %5%n

Transaction Start Times: %6%n

%1 (%2) %3Online defragmentation is beginning a full pass on database '%4'.

%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.

%1 (%2) %3Online defragmentation is resuming its pass on database '%4'. This pass started on %5 and has been running for %6 days.

(%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.

%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.

%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.

h%1 (%2) %3Online zeroing of database %4 started

%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

%1 (%2) %3Online defragmentation is beginning a full pass on streaming file '%4'.

%1 (%2) %3Online defragmentation has completed a full pass on streaming file '%4'.

%1 (%2) %3Online defragmentation of streaming file '%4' has shrunk the file by %5 bytes.

%1 (%2) %3Online defragmentation of streaming file '%4' terminated prematurely after encountering unexpected error %5.

|%1 (%2) %3Online zeroing of streaming file '%4' started.

%1 (%2) %3Online zeroing of streaming file '%4' finished after %5 seconds with err %6%n

%7 pages%n

%8 unused pages zeroed%n

%1 (%2) %3Online defragmentation has successfully been stopped on streaming file '%4'.

%1 (%2) %3Online defragmentation has been paused one or more times in the last 60 minutes for the following databases: '%4'.  The ESE Database Cache is not large enough to simultaneously run online defragmentation against the listed databases.  Action: Stagger the online maintenance time windows for the listed databases or increase the amount of physical RAM in the server.

%1 (%2) %3Online defragmentation has resumed one or more times in the last 60 minutes for the following databases: "%4'.

%1 (%2) %3Online Maintenance is starting Database Checksumming background task for database '%4'.

%1 (%2) %3Online Maintenance is starting Database Page Zeroing background task for database '%4'.

@%1 (%2) %3Online Maintenance is resuming Database Checksumming background task for database '%4'. This pass started on %5 and has been running for %6 days.

8%1 (%2) %3Online Maintenance is resuming Database Zeroing background task for database '%4'. This pass started on %5 and has been running for %6 days.

@%1 (%2) %3Online Maintenance Database Checksumming background task has completed for database '%4'. This pass started on %5 and ran for a total of %6 seconds, requiring %7 invocations over %8 days. Operation summary:

%n

%9 pages seen%n

%10 bad checksums%n

%11 uninitialized pages

t%1 (%2) %3Online Maintenance Database Zeroing background task has completed for database '%4'. This pass started on %5 and ran for a total of %6 seconds, requiring %7 invocations over %8 days. Operation summary:

%n

%9 pages seen%n

%10 bad checksums%n

%11 uninitialized pages%n

%12 pages unchanged since last zero%n

%13 unused pages zeroed%n

%14 used pages seen%n

%15 deleted records zeroed%n

%16 unreferenced data chunks zeroed

%1 (%2) %3Online Maintenance Database Checksumming background task for database '%4' encountered error %5 after %6 seconds.

%1 (%2) %3Online Maintenance Database Zeroing background task for database '%4' encountered error %5 after %6 seconds.

%1 (%2) %3Online Maintenance Database Checksumming background task for database '%4' was interrupted and terminated. The next time Online Maintenance Database Checksumming is started on this database, it will resume from the point of interruption.

%1 (%2) %3Online Maintenance Database Zeroing background task for database '%4' was interrupted and terminated. The next time Online Maintenance Database Checksumming is started on this database, it will resume from the point of interruption.

%1 (%2) %3The database page read from the file '%4' at offset %5 (database page %6) failed verification due to a page checksum mismatch. 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.

%1 (%2) %3

Online defragmentation has defragmented index '%6' of table '%5' in database '%4'. This pass started on %7.%n

%8 pages visited%n

%9 pages freed%n

%10 partial merges%n

%11 pages moved

%1 (%2) %3Online maintenance database zeroing has been paused one or more times in the last 60 minutes for the following databases: '%4'. The ESE database cache is not large enough to simultaneously run online page zeroing against the listed databases. Action: Stagger the online maintenance time windows for the listed databases or increase the amount of physical RAM in the server.

%1 (%2) %3Online maintenance database zeroing has resumed one or more times in the last 60 minutes for the following databases: '%4'.

%1 (%2) %3Online Maintenance Database Checksumming background task has completed for database '%4'. This pass started on %5 and ran for a total of %6 seconds (over %7 days) on %8 pages.

%n

Last Runtime Scan Stats: %9

%1 (%2) %3Online Maintenance Database Checksumming background task is not finishing on time for database '%4'. This pass started on %5 and has been running for %6 seconds (over %7 days) so far.

%1 (%2) %3Database Maintenance background task for database '%4' failed to start with error %5.  

%1 (%2) %3Database Maintenance has completed a full pass on database '%4'. This pass started on %5 and ran for a total of %6 seconds (%7 days).  This database maintenance task exceeded the %8 day maintenance completion threshold.  One or more of the following actions should be taken:  increase the IO performance/throughput of the volume hosting the database, reduce the database size, and/or reduce non-database maintenance IO.

%n

%9 pages seen%n

Last Runtime Scan Stats: %10%n

%1 (%2) %3Database Maintenance is starting for database '%4'.

|%1 (%2) %3Database Maintenance has completed a full pass on database '%4'. This pass started on %5 and ran for a total of %6 seconds.

%n

%7 pages seen%n

Last Runtime Scan Stats: %8%n

(%1 (%2) %3Database Maintenance is resuming for database '%4', starting from page %5. This pass started on %6 and has been running for %7 days.

0%1 (%2) %3The NTFS file attributes size for database '%4' is %5 bytes, which exceeds the threshold of %6 bytes. The database file must be reseeded or restored from a copy or backup to prevent the database file from being unable to grow because of  a file system limitation. 

%1 (%2) %3The periodic database file trimming operation started.

%1 (%2) %3The periodic database file trimming operation finished successfully and trimmed the database file by %4 pages.

<%1 (%2) %3The periodic database file trimming operation was not able to trim the database file because there is not enough internal free space available.

%1 (%2) %3The periodic database file trimming operation was not able to trim the database file. Result %4.

 %1 (%2) %3Database Maintenance is running on database '%4'. This pass started on %5 and has been running for %6 hours.

%n

%7 pages seen%n

X%1 (%2) %3Online Maintenance Database Checksumming background task is aborted for database '%4' at page %5, due to client request (typically because of critical redo activity must be done quickly).%n

The last properly completed checksumming task was on %6.%n

%n

Last Runtime Scan Stats: %7%n

h%1 (%2) %3Online Maintenance Database Checksumming background task finished an interrupted and incomplete scan for database '%4'. Typical interruptions are due to client request (typically because of critical redo activity must be done quickly).%n

The last fully completed checksumming scan was on %5.

l%1 (%2) %3Online Maintenance is resuming Database Checksumming background task for database '%4', and in doing so has skipped %5 pages (%6%%).  prev stop: %7, this start: %8.%n

%1 (%2) %3The database file shrinkage operation completed successfully on database '%4'.%n

Duration: %5 minute(s) and %6 second(s).%n

Initial file size: %7 bytes (%8 page(s)).%n

Final file size: %9 bytes (%10 page(s)).%n

Initial owned space: %11 bytes (%12 page(s)).%n

Final owned space: %13 bytes (%14 page(s)).%n

Data moved: %15 bytes (%16 page(s)).%n

%1 (%2) %3The database file shrinkage operation failed on database '%4'.%n

Duration: %5 minute(s) and %6 second(s).%n

Initial file size: %7 bytes (%8 page(s)).%n

Final file size: %9 bytes (%10 page(s)).%n

Initial owned space: %11 bytes (%12 page(s)).%n

Final owned space: %13 bytes (%14 page(s)).%n

Data moved: %15 bytes (%16 page(s)).%n

Error code: %17.%n

%1 (%2) %3System parameter minimum cache size (%4) is less than 4 times the number of sessions (%5).

%1 (%2) %3System parameter maximum cache size (%4) is less than minimum cache size (%5).

%1 (%2) %3System parameter maximum cache size (%4) is less than stop clean flush threshold (%5).

%1 (%2) %3System parameter stop clean flush threshold (%4) is less than start clean flush threshold (%5).

 %1 (%2) %3System parameter log buffer size (%4 sectors) is greater than the maximum size of %5 k bytes (logfile size minus reserved space).

%1 (%2) %3System parameter max version pages (%4) is less than preferred version pages (%5).

%1 (%2) %3System parameter preferred version pages was changed from %4 to %5 due to physical memory limitation.

%1 (%2) %3System parameter max open tables (%4) is less than preferred opentables (%5). Please check registry settings.

0%1 (%2) %3System parameter preferred version pages (%4) is greater than max version pages (%5). Preferred version pages was changed from %6 to %7.

%1 (%2) %3The database engine failed with error %4 while trying to log the commit of a transaction. To ensure database consistency, the process was terminated. Simply restart the process to force database recovery and return the database to a Clean Shutdown state.

`%1 (%2) %3Tag: %6. Internal trace: %4 (%5).

%1 (%2) %3The database engine detected multiple threads illegally using the same database session to perform database operations.

%n%tSessionId: %4

%n%tSession-context: %5

%n%tSession-context ThreadId: %6

%n%tCurrent ThreadId: %7

%n%tSession-trace:

%n%8

%1 (%2) %3The database engine detected two different cursors of the same session illegally trying to update the same record at the same time.

%n%tSessionId: %4

%n%tThreadId: %5

%n%tDatabase: %6

%n%tTable: %7

%n%tCurrent cursor: %8

%n%tCursor owning original update: %9

%n%tBookmark size (prefix/suffix): %10

%n%tSession-trace:

%n%11

%1 (%2) %3A test API has been used to corrupt page %4 of database '%5'.

X%1 (%2) %3The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source of the corruption is likely due to faulty hardware and should be investigated.  Please contact your hardware vendor for further assistance diagnosing the problem.

%1 (%2) %3A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation.

%nSee help link for complete details of possible causes.

%nPrevious cache residency state: %4% (%5 out of %6 buffers) (%7 seconds ago)

%nCurrent cache residency state:  %8% (%9 out of %10 buffers)

%nCurrent cache size vs. target:  %11% (%12 MBs)

%nPhysical Memory / RAM size:     %13 MBs

%1 (%2) %3A transient memory corruption was detected.  Please run the Windows Memory Diagnostics Tool and/or investigate hardware issues.

%1 (%2) %3Terminating process due to non-recoverable failure: %4 (%5). Tag: %6.

%1 (%2) %3Terminating process due to non-recoverable failure: %4 (%5) in operation on database '%6'.

%1 (%2) %3The database cache size maintenance task has taken %4 seconds without completing. This may result in severe performance degradation.

Current cache size is %5 buffers above the configured cache limit (%6 percent of target).

Cache size maintenance evicted %7 buffers, made %8 flush attempts, and successfully flushed %9 buffers. It has run %10 times since maintenance was triggered.

d%1 (%2) %3The database engine repaired corruption on pages %4 - %5 of database '%6'. Although the corruption has been repaired, the source of the corruption is likely due to faulty hardware and should be investigated.  Please contact your hardware vendor for further assistance diagnosing the problem.

@%1 (%2) %3A portion of the database buffer cache has been restored from the system paging file and is now resident again in memory. Prior to this, a portion of the database buffer cache had been written out to the system paging file resulting in performance degradation.

%nPrevious cache residency state: %4% (%5 out of %6 buffers) (%7 seconds ago)

%nCurrent cache residency state: %8% (%9 out of %10 buffers)

%1 (%2) %3The parameter %4 was not set to one value by the previous ESE application instance, but set to a different value from the current ESE application. This is a system parameter mismatch, all ESE applications must agree on all global system parameters.

%1 (%2) %3The parameter %4 was not set via the previous ESE application instance, but is set in the current ESE application. This is a system parameter mismatch, all ESE applications must agree on all global system parameters.

%1 (%2) %3The parameter %4 was set via the previous ESE application instance, but is not set in the current ESE application. This is a system parameter mismatch, all ESE applications must agree on all global system parameters.

%1 (%2) %3The beta feature %4 is enabled in %5 due to the beta site mode settings %6.

%1 (%2) %3Resource failure simulation was activated with the following settings:

\t\t%4:\t%5

\t\t%6:\t%7

\t\t%8:\t%9

\t\t%10:\t%11

x%1 (%2) %3Resource failure simulation %4 is permitted.

p%1 (%2) %3Resource Failure Simulation %4 is denied.

l%1 (%2) %3JET call %4 returned error %5. %6 (%7)

|%1 (%2) %3JET inline error %4 jumps to label %5. %6 (%7)

\%1 (%2) %3Shadow copy function %4() = %5.

l%1 (%2) %3Shadow copy instance %4 freeze started.

%1 (%2) %3Shadow copy instance %4 encountered error %5 on freeze.

h%1 (%2) %3Shadow copy instance %4 freeze ended.

%1 (%2) %3Shadow copy instance %4 freeze timed-out (%5 ms).

%1 (%2) %3Shadow copy instance %4 starting. This will be a Full shadow copy.

|%1 (%2) %3Shadow copy instance %4 completed successfully.

`%1 (%2) %3Shadow copy instance %4 aborted.

%1 (%2) %3Shadow copy instance %4 starting. This will be an Incremental shadow copy.

%1 (%2) %3Shadow copy instance %4 starting. This will be a Copy shadow copy.

%1 (%2) %3Shadow copy instance %4 starting. This will be a Differential shadow copy.

(%1 (%2) %3An attempt to initialize the FPGA failed with error %4. Please make sure that the FPGA hardware is present and configured correctly.

\%1 (%2) %3An attempt to acquire an FPGA slot during initialization failed. This indicates that there are more processes trying to use the FPGA than the available slots.

%1 (%2) %3An FPGA operation failed with error %4. This error was classified as a transient failure. The engine has encountered the following FPGA failures since it started:

Permanent = %5, Transient = %6, HEX Resets = %7

%1 (%2) %3An FPGA operation failed with error %4. This error was classified as a permanent FPGA failure. The engine has encountered the following FPGA failures since it started:

Permanent = %5, Transient = %6, HEX Resets = %7

%1 (%2) %3An attempt to acquire an FPGA slot event during initialization failed with system error %4: "%5".

0NOOP_FAILURE_TAG_ID

%1 (%2) %3A configuration error is preventing proper operation of database '%4' ('%5').  The error may occur because of a database misconfiguration, a permission problem, or a storage-related problem.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3A read verification or I/O error is preventing proper operation of database '%4' ('%5'). Review the event logs and other log data to determine if your system is experiencing storage-related problems.%n%nAdditional diagnostic information:  %6 %7

%1 (%2) %3Lack of free space for the database or log files is preventing proper operation of database '%4' ('%5').  Review the database and log volume's free space to identify the specific problem.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3An I/O error is preventing proper operation of database '%4' ('%5').  Review events logs and other log data to determine if your system is experiencing storage problems.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3A passive copy has detected a corruption in the mounted copy of database '%4' ('%5'). This error might be the result of a storage-related problem.%n%nAdditional diagnostic information:  %6 %7

%1 (%2) %3Corruption has been detected in database '%4' ('%5').  The error may occur because of human errors, system, or storage problems.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3Resources or an operating error is preventing proper functioning of database '%4' ('%5').  Review the application and system event logs for failures of the database or its required system components.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3A serious error is preventing proper operation of database '%4' ('%5').  Review the application and system event logs for failures of the database or its required system components.

%n

%nAdditional diagnostic information:  %6 %7

x%1 (%2) %3Problems are preventing proper operation of database '%4' ('%5').  The failure may be corrected by remounting the database.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3In a log shipping environment, a passive copy has detected an error that is preventing proper operation of database '%4' ('%5').  Review the application and system event logs for failures of the database or its required system components.

 %1 (%2) %3A performance problem is affecting proper operation of database '%4' ('%5').  The error may occur due to misconfiguration, storage problems, or performance problems on the computer.  Review the performance counters and application event logs associated with the database, its storage, and the computer to identify the specific problems.

%n

%nAdditional diagnostic information:  %6 %7

%1 (%2) %3An unusually large amount of normal load is preventing proper operation of database '%4' ('%5').  The load on this database should be reduced to restore proper operation.

%n

%nAdditional diagnostic information:  %6 %7

,%1 (%2) %3The system is experiencing memory allocation failures that are preventing proper operation of database '%4' ('%5').  The error could occur due to a mis-configuration or excessive memory consumption on the machine.

%n

%nAdditional diagnostic information:  %6 %7

DCATALOGRESEED_FAILURE_TAG_ID

0MAX_FAILURE_TAG_ID

4VS_VERSION_INFO
cE
cE?&StringFileInfo040904B0LCompanyNameMicrosoft Corporation6FileDescriptionExtensible Storage Engine for Microsoft(R) Windows(R)h$FileVersion10.0.17763.1 (WinBuild.160101.0800)4
InternalNameesent.dll.LegalCopyright Microsoft Corporation. All rights reserved.DOriginalFilenameesent.dll.muij%ProductNameMicrosoft Windows Operating System>
ProductVersion10.0.17763.1DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING

Hacked By AnonymousFox1.0, Coded By AnonymousFox