ESENT.dll.mui Microsoft(R) Windows(R) 的可扩展存储引擎 1f372af514a4a1f56bd0c45281686a00

File name:	ESENT.dll.mui
Size:	61952 byte
MD5:	1f372af514a4a1f56bd0c45281686a00
SHA1:	bc33031217d4b320ad28c791291fa1d2f56c3b7a
SHA256:	fc55f1cf5c465d5fc60dfab0958917ee9e67f0143c3bc448af3ffde78059439c
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in Chinese (Simplified) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	Chinese (Simplified)	English
0x0	%1 (%2) %3%4	%1 (%2) %3%4
0x1	常规	General
0x2	数据库页面缓存	Database Page Cache
0x3	日志记录/恢复	Logging/Recovery
0x4	空间管理	Space Management
0x5	表/列/索引定义	Table/Column/Index Definition
0x6	记录操作	Record Manipulation
0x7	性能	Performance
0x8	数据库修复	Database Repair
0x9	数据库转换	Database Conversion
0xA	联机碎片整理	Online Defragmentation
0xB	系统参数设置	System Parameter Settings
0xC	数据库损坏	Database Corruption
0xD	数据库零位调整	Database Zeroing
0xE	事务管理器	Transaction Manager
0xF	资源故障模拟	Resource Failure Simulation
0x10	卷影副本	ShadowCopy
0x11	失败项	Failure Items
0x12
0x13	System Device	System Device
0x64	%1 (%2) %3数据库引擎 %4.%5.%6.%7 已启动。	%1 (%2) %3The database engine %4.%5.%6.%7 started.
0x65	%1 (%2) %3数据库引擎已停止。	%1 (%2) %3The database engine stopped.
0x66	%1 (%2) %3数据库引擎(%5.%6.%7.%8)正在启动新实例(%4)。	%1 (%2) %3The database engine (%5.%6.%7.%8) is starting a new instance (%4).
0x67	%1 (%2) %3数据库引擎已停止实例(%4)。%n%n异常关闭: %6%n%n内部计时序列: %5	%1 (%2) %3The database engine stopped the instance (%4).%n%nDirty Shutdown: %6%n%nInternal Timing Sequence: %5
0x68	%1 (%2) %3数据库引擎已停止实例(%4)，出现错误(%5)。%n%n内部计时序列: %6	%1 (%2) %3The database engine stopped the instance (%4) with error (%5).%n%nInternal Timing Sequence: %6
0x69	%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 database engine started a new instance (%4). (Time=%5 seconds)%n%nAdditional Data:%n%7%n%nInternal Timing Sequence: %6
0x6A	%1 (%2) %3参数 %4 已尝试设置为 %5，但是已被注册表设置(%7 处)替代为 %6。	%1 (%2) %3The parameter %4 was attempted to be set to %5, but was overridden to %6 by the registry settings (at %7).
0x6B	%1 (%2) %3已从注册表设置(%7 处)中读取参数 %4，但是 ESE 引擎已拒绝值 %5，错误 %6。	%1 (%2) %3The parameter %4 was read from the registry settings (at %7), but the ESE engine rejected the value %5 with err %6.
0x6C	%1 (%2) %3特定 ESE 配置存储已锁定为禁止读取状态，请清除 %1 注册表值来启用 ESE 以继续，并利用配置存储。	%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.
0xC8	%1 (%2) %3数据库引擎正在启动完整备份。	%1 (%2) %3The database engine is starting a full backup.
0xC9	%1 (%2) %3数据库引擎正在启动增量备份。	%1 (%2) %3The database engine is starting an incremental backup.
0xCA	%1 (%2) %3数据库引擎已成功完成备份过程。	%1 (%2) %3The database engine has completed the backup procedure successfully.
0xCB	%1 (%2) %3数据库引擎已停止备份，错误 %4。	%1 (%2) %3The database engine has stopped the backup with error %4.
0xCC	%1 (%2) %3数据库引擎正在从备份中还原。还原时，将开始重放文件夹 %4 中的日志文件，并继续前滚文件夹 %5 中的日志文件。	%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.
0xCD	%1 (%2) %3数据库引擎已停止还原。	%1 (%2) %3The database engine has stopped restoring.
0xCE	%1 (%2) %3无法对数据库 %4 执行增量备份。进行增量备份之前，必须首先执行完整备份。	%1 (%2) %3Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup.
0xCF	%1 (%2) %3由于被客户端终止或者与客户端的连接失败，数据库引擎已停止备份。	%1 (%2) %3The database engine has stopped backup because it was halted by the client or the connection with the client failed.
0xD2	%1 (%2) %3正在启动完整备份。	%1 (%2) %3A full backup is starting.
0xD3	%1 (%2) %3正在启动增量备份。	%1 (%2) %3An incremental backup is starting.
0xD4	%1 (%2) %3正在启动卷影副本备份。	%1 (%2) %3A shadow copy backup is starting.
0xD5	%1 (%2) %3已成功完成备份过程。	%1 (%2) %3The backup procedure has been successfully completed.
0xD6	%1 (%2) %3备份已停止，错误 %4。	%1 (%2) %3The backup has stopped with error %4.
0xD7	%1 (%2) %3由于被客户端终止或者与客户端的连接失败，备份已停止。	%1 (%2) %3The backup has been stopped because it was halted by the client or the connection with the client failed.
0xD8	%1 (%2) %3检测到数据库位置从“%4”更改为“%5”。	%1 (%2) %3A database location change was detected from '%4' to '%5'.
0xD9	%1 (%2) %3备份数据库(文件 %5)时出现错误(%4)。数据库无法还原。	%1 (%2) %3Error (%4) during backup of a database (file %5). The database will be unable to restore.
0xDA	%1 (%2) %3复制或备份文件 %5 时出现错误(%4)。	%1 (%2) %3Error (%4) during copy or backup of file %5.
0xDB	%1 (%2) %3使用备份信息更新数据库标题时出现错误(%4)。	%1 (%2) %3Error (%4) occured during database headers update with the backup information.
0xDC	%1 (%2) %3开始复制或备份文件 %4 (大小为 %5)。	%1 (%2) %3Starting the copy or backup of the file %4 (size %5).
0xDD	%1 (%2) %3结束复制或备份文件 %4。	%1 (%2) %3Ending the copy or backup of the file %4.
0xDE	%1 (%2) %3结束备份文件 %4。并未读取文件中的所有数据(总共 %6 字节，读取了 %5 字节)。	%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).
0xDF	%1 (%2) %3开始备份日志文件(范围 %4 - %5)。	%1 (%2) %3Starting the backup of log files (range %4 - %5).
0xE0	%1 (%2) %3删除日志文件 %4 到 %5。	%1 (%2) %3Deleting log files %4 to %5.
0xE1	%1 (%2) %3无法截断任何日志文件。	%1 (%2) %3No log files can be truncated.
0xE2	%1 (%2) %3备份已经被永久停止(可能因为此实例中止)。	%1 (%2) %3The backup has been stopped prematurely (possibly because the instance is terminating).
0xE3	%1 (%2) %3在我们尝试截断的日志范围中有 %4 个日志文件找不到。	%1 (%2) %3There were %4 log file(s) not found in the log range we attempted to truncate.
0xF0	%1 (%2) %3正在开始内部复制(供种子设定或分析之用)。流 ESE 备份 API 正在用于传输方法。	%1 (%2) %3An internal copy (for seeding or analysis purposes) is starting. The streaming ESE backup APIs are being used for the transfer method.
0xF3	%1 (%2) %3内部数据库复制(出于种子设定或分析目的)过程已成功完成。	%1 (%2) %3The internal database copy (for seeding or analysis purposes) procedure has been successfully completed.
0xF4	%1 (%2) %3内部数据库复制(出于种子设定或分析目的)已停止。错误: %4。	%1 (%2) %3The internal database copy (for seeding or analysis purposes) has stopped. Error: %4.
0xF5	%1 (%2) %3内部数据库复制(出于种子设定或分析目的)已停止，因为它已被客户端终止或与客户端的连接失败。	%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.
0xFC	%1 (%2) %3结束文件 %4 的内部复制(出于种子设定或分析目的)。并未读取该文件中的所有数据(共 %6 字节，读取了 %5 字节)。	%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).
0x100	%1 (%2) %3内部数据库复制(出于种子设定或分析目的)已提前停止，可能是因为实例正在终止。	%1 (%2) %3The internal database copy (for seeding or analysis purposes) has been stopped prematurely, possibly because the instance is terminating.
0x12C	%1 (%2) %3数据库引擎正在初始化恢复步骤。	%1 (%2) %3The database engine is initiating recovery steps.
0x12D	%1 (%2) %3The database engine has begun replaying logfile %4.%n%nPrevious Log Processing Stats: %5	%1 (%2) %3The database engine has begun replaying logfile %4.%n%nPrevious Log Processing Stats: %5
0x12E	%1 (%2) %3数据库引擎已成功完成恢复步骤。	%1 (%2) %3The database engine has successfully completed recovery steps.
0x12F	%1 (%2) %3出现数据库引擎错误 %4。	%1 (%2) %3Database engine error %4 occurred.
0x130	%1 (%2) %3数据库引擎已成功完成重播步骤。	%1 (%2) %3The database engine has successfully completed replay steps.
0x145	%1 (%2) %3The database engine created a new database (%4, %5). (Time=%6 seconds)%n%nAdditional Data: %9%n%nInternal Timing Sequence: %7	%1 (%2) %3The database engine created a new database (%4, %5). (Time=%6 seconds)%n%nAdditional Data: %9%n%nInternal Timing Sequence: %7
0x146	%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	%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
0x147	%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 detached a database (%4, %5). (Time=%6 seconds)%n%nRevived Cache: %8%nAdditional Data: %9%n%nInternal Timing Sequence: %7
0x148	%1 (%2) %3在日志位置 %5 恢复期间，数据库引擎触发了回调操作以便连接数据库 %4。回调返回了 %6。	%1 (%2) %3The database engine has fired callback for attach of database %4 during recovery at log position %5. The callback returned %6.
0x149	%1 (%2) %3在日志位置 %5 恢复期间，数据库引擎触发了回调操作以便分离数据库 %4。回调返回了 %6。	%1 (%2) %3The database engine has fired callback for detach of database %4 during recovery at log position %5. The callback returned %6.
0x14A	%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] format version is being held back to %6 due to application parameter setting of %5. Current default engine version: %7.
0x14B	%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 was upgraded from %5 to %6. Current engine format version parameter setting: %7
0x14C	%1 (%2) %3数据库 [%4] 版本 %5 高于引擎 %6 解析的最高版本。	%1 (%2) %3The database [%4] version %5 is higher than the maximum version understood by the engine %6.
0x14D	%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] version %5 is higher than the maximum version configured by the application %6. Current engine format version parameter setting: %7
0x14E	%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) %3The database [%4] has completed incremental reseed page patching operations for %5 pages.%n%nDetails:%nRange of Patching: %6%nTiming: %7
0x14F	%1 (%2) %3Replay of a %4 for database \"%5\" at log position %6 was deferred due to %7. Additional information: %8	%1 (%2) %3Replay of a %4 for database \"%5\" at log position %6 was deferred due to %7. Additional information: %8
0x18E	%1 (%2) %3从文件“%4”中偏移量 %5 (数据库第 %9 页)读取的 %6 字节的数据库页面验证失败。位 %8 已损坏并已进行更正，但页面验证失败，错误为 %7。此问题可能是由于硬件故障引起的，并一直存在。这种瞬间错误预示着包含此文件的存储子系统可能会发生灾难性失败。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x18F	%1 (%2) %3从文件“%4”中偏移量 %5 (数据库第 %8 页)读取的 %6 字节的数据库页面验证失败。位 %7 已损坏并已进行更正。此问题可能是由于硬件故障引起的，并一直存在。这种瞬间错误预示着包含此文件的存储子系统可能会发生灾难性失败。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x190	%1 (%2) %3出现同步重叠读取页面时间错误 %4。如果此错误持续存在，请从以前的备份中还原数据库。	%1 (%2) %3Synchronous overlapped read page time error %4 occurred. If this error persists, please restore the database from a previous backup.
0x191	%1 (%2) %3出现同步重叠写入页面发布错误 %4。	%1 (%2) %3Synchronous overlapped write page issue error %4 occurred.
0x192	%1 (%2) %3出现同步重叠写入页面错误 %4。	%1 (%2) %3Synchronous overlapped write page error %4 occurred.
0x193	%1 (%2) %3出现同步重叠修补文件写入页面错误 %4。	%1 (%2) %3Synchronous overlapped patch file write page error %4 occurred.
0x194	%1 (%2) %3出现同步读取页面校验和错误 %4。如果此错误持续存在，请从以前的备份中还原数据库。	%1 (%2) %3Synchronous read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.
0x195	%1 (%2) %3出现预读取页面校验和错误 %4。如果此错误持续存在，请从以前的备份中还原数据库。	%1 (%2) %3Pre-read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup.
0x196	%1 (%2) %3直接读取发现损坏的页面 %4，错误 %5。如果此错误持续存在，请从以前的备份中还原数据库。	%1 (%2) %3Direct read found corrupted page %4 with error %5. If this error persists, please restore the database from a previous backup.
0x197	%1 (%2) %3出现缓冲区 I/O 线程终止错误 %4。	%1 (%2) %3Buffer I/O thread termination error %4 occurred.
0x198	%1 (%2) %3无法写入日志文件 %4。错误 %5。	%1 (%2) %3Unable to write to logfile %4. Error %5.
0x199	%1 (%2) %3无法写入日志文件 %4 的标头。错误 %5。	%1 (%2) %3Unable to write to the header of logfile %4. Error %5.
0x19A	%1 (%2) %3无法读取日志文件 %4。错误 %5。	%1 (%2) %3Unable to read logfile %4. Error %5.
0x19B	%1 (%2) %3日志文件 %4 的日志版本标记与数据库引擎版本标记不匹配。对于数据库，日志文件的版本可能不正确。	%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.
0x19C	%1 (%2) %3无法读取日志文件 %4 的标头。错误 %5。	%1 (%2) %3Unable to read the header of logfile %4. Error %5.
0x19D	%1 (%2) %3无法创建新的日志文件，因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 %4。	%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.
0x19E	%1 (%2) %3刷新日志文件 %4 时无法写入 0 扇区。错误 %5。	%1 (%2) %3Unable to write to section 0 while flushing logfile %4. Error %5.
0x19F	%1 (%2) %3刷新日志文件 %4 时无法写入 1 扇区。错误 %5。	%1 (%2) %3Unable to write to section 1 while flushing logfile %4. Error %5.
0x1A0	%1 (%2) %3刷新日志文件 %4 时无法写入 2 扇区。错误 %5。	%1 (%2) %3Unable to write to section 2 while flushing logfile %4. Error %5.
0x1A1	%1 (%2) %3刷新日志文件 %4 时无法写入 3 扇区。错误 %5。	%1 (%2) %3Unable to write to section 3 while flushing logfile %4. Error %5.
0x1A2	%1 (%2) %3打开新建的日志文件 %4 时出现错误 %5。	%1 (%2) %3Error %5 occurred while opening a newly-created logfile %4.
0x1A3	%1 (%2) %3无法读取数据库 %4 中的页面 %5。错误 %6。	%1 (%2) %3Unable to read page %5 of database %4. Error %6.
0x1A4	%1 (%2) %3无法读取数据库 %4 的标头。错误 %5。数据库可能已被移动，因此可能不再位于日志预期的位置。	%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.
0x1A5	%1 (%2) %3没有恢复在 %5 创建的数据库 %4。已在 %5 创建恢复的数据库。	%1 (%2) %3The database %4 created at %5 was not recovered. The recovered database was created at %5.
0x1A6	%1 (%2) %3没有恢复在 %5 创建的数据库 %4。	%1 (%2) %3The database %4 created at %5 was not recovered.
0x1A7	%1 (%2) %3数据库引擎发现了一个坏的页面。	%1 (%2) %3The database engine found a bad page.
0x1A8	%1 (%2) %3数据库磁盘已满。如果数据库文件不是处于干净关闭状态，则删除日志文件以恢复磁盘空间可能会使数据库无法启动。如果数据库文件处于干净关闭状态，也只有当数据库文件处于干净关闭状态下，编号的日志文件可能被移动但不是删除。切勿移动 %4。	%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.
0x1A9	%1 (%2) %3数据库签名与数据库 %4 的日志签名不匹配。	%1 (%2) %3The database signature does not match the log signature for database %4.
0x1AA	%1 (%2) %3数据库引擎无法找到称为 %4 的文件或文件夹。	%1 (%2) %3The database engine could not find the file or folder called %4.
0x1AB	%1 (%2) %3数据库引擎无法访问称为 %4 的文件。	%1 (%2) %3The database engine could not access the file called %4.
0x1AC	%1 (%2) %3由于日志磁盘上的可用磁盘空间太少，数据库引擎拒绝更新操作。	%1 (%2) %3The database engine is rejecting update operations due to low free disk space on the log disk.
0x1AD	%1 (%2) %3数据库引擎日志磁盘已满。如果数据库文件不是处于干净关闭状态，则删除日志文件以恢复磁盘空间可能会使数据库无法启动。如果数据库文件处于干净关闭状态，也只有当数据库文件处于干净关闭状态下，编号的日志文件可能被移动但不是删除。切勿移动 %4。	%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.
0x1AE	%1 (%2) %3数据库 %4 与其修补文件不匹配。	%1 (%2) %3Database %4 and its patch file do not match.
0x1AF	%1 (%2) %3起始还原日志文件 %4 太高。应该从日志文件 %5 开始。	%1 (%2) %3The starting restored logfile %4 is too high. It should start from logfile %5.
0x1B0	%1 (%2) %3终止还原日志文件 %4 太低。应该在日志文件 %5 终止。	%1 (%2) %3The ending restored logfile %4 is too low. It should end at logfile %5.
0x1B1	%1 (%2) %3还原的日志文件 %4 没有正确的日志签名。	%1 (%2) %3The restored logfile %4 does not have the correct log signature.
0x1B2	%1 (%2) %3还原日志文件 %4 的时间戳与前一个日志文件中记录的时间戳不匹配。	%1 (%2) %3The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it.
0x1B3	%1 (%2) %3丢失还原的日志文件 %4。	%1 (%2) %3The restored logfile %4 is missing.
0x1B4	%1 (%2) %3日志文件 %4 的签名与其他日志文件的签名不匹配。除非所有签名都相互匹配，否则恢复无法成功完成。日志文件 %5 至 %6 已被删除。	%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.
0x1B5	%1 (%2) %3日志文件 %4 与其前面的日志文件之间的序列号中有间隔。为完成恢复，日志文件 %5 至 0x%6 已被删除。	%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.
0x1B6	%1 (%2) %3备份数据库 %4 必须是 4KB 的倍数。	%1 (%2) %3The backup database %4 must be a multiple of 4 KB.
0x1B7	%1 (%2) %3无法写入文件 %4 的阴影标头。错误 %5。	%1 (%2) %3Unable to write a shadowed header for file %4. Error %5.
0x1B8	%1 (%2) %3日志文件 %4 已损坏、无效或不可访问(错误 %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.
0x1B9	%1 (%2) %3IO 期间，数据库 %4 上出现文件系统错误 %5。如果此错误持续存在，数据库文件可能已损坏，而且可能需要从以前的备份中还原。	%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.
0x1BA	%1 (%2) %3数据库 %4 上的 IO 大小不匹配。预期的 IO 大小为 %5，而返回的大小为 %6。	%1 (%2) %3IO size mismatch on database %4, IO size %5 expected while returned size is %6.
0x1BB	%1 (%2) %3File system error %5 during IO or flush on logfile %4.	%1 (%2) %3File system error %5 during IO or flush on logfile %4.
0x1BC	%1 (%2) %3日志文件 %4 上的 IO 大小不匹配。预期的 IO 大小为 %5，而返回的大小为 %6。	%1 (%2) %3IO size mismatch on logfile %4, IO size %5 expected while returned size is %6.
0x1BD	%1 (%2) %3数据库 %4 已达到其最大大小 %5MB。如果数据库无法重新启动，可以执行脱机碎片整理以减小数据库大小。	%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.
0x1BE	%1 (%2) %3重建日志文件 %4 (%5,%6)时，数据库恢复异常停止。自此之后的日志可能无法识别且不会被处理。	%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.
0x1BF	%1 (%2) %3在数据库 %7 (%8 = %9, %10)的 B-目录树(ObjectId: %5, PgnoRoot: %6)中检测到无效页面链接(错误 %4)。	%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).
0x1C0	%1 (%2) %3在数据库 %5 (%6,%7)的表 %4 中检测到数据不一致。	%1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).
0x1C1	%1 (%2) %3检测到流数据分配不一致(%4,%5)。	%1 (%2) %3Streaming data allocation inconsistency detected (%4,%5).
0x1C2	%1 (%2) %3在日志文件序列中检测到间隔。丢失日志文件 %4。可能还需要此日志文件后面的其他日志文件。如果未还原丢失的日志文件，可能会再次显示此消息。	%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.
0x1C3	%1 (%2) %3刷新日志文件 %4 时，无法写入扇区 4。错误 %5。	%1 (%2) %3Unable to write to section 4 while flushing logfile %4. Error %5.
0x1C4	%1 (%2) %3数据库 %4 需要日志文件 %5-%6 才能成功恢复。恢复只能定位开始于 %7 的日志文件。	%1 (%2) %3Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7.
0x1C5	%1 (%2) %3数据库 %4 需要日志文件 %5-%6 (%8 - %9)才能成功恢复。恢复最多只能定位 %7 (%10)个日志文件。	%1 (%2) %3Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to %7 (%10).
0x1C6	%1 (%2) %3数据库恢复/还原失败，出现意外错误 %4。	%1 (%2) %3Database recovery/restore failed with unexpected error %4.
0x1C7	%1 (%2) %3打开日志文件 %4 时出现错误 %5。	%1 (%2) %3Error %5 occurred while opening logfile %4.
0x1C8	%1 (%2) %3文件 %4 的主标头页已损坏。使用的是阴影标头页(%5 字节)。	%1 (%2) %3The primary header page of file %4 was damaged. The shadow header page (%5 bytes) was used instead.
0x1C9	%1 (%2) %3现有日志文件 %4 的日志签名与备份集中的日志文件不匹配。只有所有的签名都匹配，日志文件重放才能成功完成。	%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.
0x1CA	%1 (%2) %3日志文件 %4 和 %5 未在有效序列中。如果可用日志文件序列中存在间隔，日志文件重放将失败。	%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.
0x1CB	%1 (%2) %3丢失文件 %4，无法备份。	%1 (%2) %3The file %4 is missing and could not be backed-up.
0x1CC	%1 (%2) %3从备份集的日志文件 %4 中的备份进行还原时检测到断写。失败的校验和记录位于位置 %5。此日志文件已损坏且无法使用。	%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.
0x1CD	%1 (%2) %3在日志文件 %4 中进行硬恢复时检测到断写。失败的校验和记录位于位置 %5。此日志文件已损坏且无法使用。	%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.
0x1CE	%1 (%2) %3在日志文件 %4 中进行软恢复时检测到断写。失败的校验和记录位于位置 %5。日志文件中的损坏将被修复，同时恢复将继续进行。	%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.
0x1CF	%1 (%2) %3从备份日志文件 %4 进行还原时检测到已发生损坏。失败的校验和记录位于位置 %5。与日志文件填充模式不匹配的数据首先出现在 %6 扇区。此日志文件已损坏且无法使用。	%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.
0x1D0	%1 (%2) %3在日志文件 %4 中进行硬恢复时检测到已发生损坏。失败的校验和记录位于位置 %5。与日志文件填充模式不匹配的数据首先出现在 %6 扇区。此日志文件已损坏且无法使用。	%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.
0x1D1	%1 (%2) %3在日志文件 %4 中进行软恢复时检测到已发生损坏。失败的校验和记录位于位置 %5。与日志文件填充模式不匹配的数据首先出现在扇区 %6。此日志文件已损坏且无法使用。	%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.
0x1D2	%1 (%2) %3使用日志文件 %4 中的阴影扇区副本来修补其中无效的校验和记录。	%1 (%2) %3An invalid checksum record in logfile %4 was patched using its shadow sector copy.
0x1D3	%1 (%2) %3数据库 %6: 表 %5 的索引 %4 被损坏(%7)。	%1 (%2) %3Database %6: Index %4 of table %5 is corrupted (%7).
0x1D4	%1 (%2) %3刷新日志文件 %4 时无法写入 5 扇区。错误 %5。	%1 (%2) %3Unable to write to section 5 while flushing logfile %4. Error %5.
0x1D6	%1 (%2) %3数据库 %4 被部分附加。附件阶段: %5。错误: %6。	%1 (%2) %3Database %4 is partially attached. Attachment stage: %5. Error: %6.
0x1D7	%1 (%2) %3在数据库 %5 上无法进行回滚操作 #%4。错误: %6。未来所有数据库更新都将被拒绝。	%1 (%2) %3Unable to rollback operation #%4 on database %5. Error: %6. All future database updates will be rejected.
0x1D8	%1 (%2) %3文件 %4 的阴影标头页已损坏。使用的是主标头页(%5 字节)。	%1 (%2) %3The shadow header page of file %4 was damaged. The primary header page (%5 bytes) was used instead.
0x1D9	%1 (%2) %3数据库 %4 被部分分离。更新数据库的标头时遇到错误 %5。	%1 (%2) %3Database %4 was partially detached. Error %5 encountered updating database headers.
0x1DA	%1 (%2) %3由于页面校验和不匹配，从文件“%4”中偏移量 %5 (数据库第 %10 页)读取的 %6 字节的数据库页面验证失败。存储的校验和是 %8，而计算的校验和是 %9。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份中还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x1DB	%1 (%2) %3由于页码不匹配，从文件“%4”中偏移量 %5 读取的 %6 字节数据库页面验证失败。预期的页码是 %8，而存储的页码是 %9。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x1DC	%1 (%2) %3由于数据库页不包含页数据，从文件“%4”中偏移量 %5 (数据库第 %8 页)读取的 %6 字节数据库页验证失败。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x1DD	%1 (%2) %3由于范围校验和不匹配，在文件“%4”中偏移量 %5 读取的 %6 字节日志范围验证失败。预期的校验和是 %8，而实际的校验和是 %9。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份还原日志文件。	%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.
0x1DE	%1 (%2) %3由于页面校验和不匹配，因此从文件“%4”中偏移量 %5 读取的 %6 字节数据流页面验证失败。预期的校验和是 %8，而实际的校验和是 %9。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份还原数据库。	%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.
0x1DF	%1 (%2) %3由于页面校验和不匹配，因此从文件“%4”中偏移量 %5 读取的 %6 字节修补页面验证失败。预期的校验和是 %8，而实际的校验和是 %9。读取操作将失败，并出现错误 %7。如果此情况持续存在，请使用以前的备份集还原。	%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.
0x1E0	%1 (%2) %3由于页码不匹配，从文件“%4”中偏移量 %5 读取的 %6 字节的修补页面验证失败。预期的页码是 %8，而实际的页码是 %9。读取操作将失败，出现错误 %7。如果此情况持续存在，请使用以前的备份集还原。	%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.
0x1E1	%1 (%2) %3系统错误 %8: \"%9\" 发生 %10 秒后，从文件 \"%4\" 中偏移量 %5 读取 %6 字节的尝试失败。读取操作将失败，并出现错误 %7。如果此错误持续存在，文件可能会被损坏，并可能需要从以前的备份中还原。	%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.
0x1E2	%1 (%2) %3系统错误 %8: \"%9\" 发生 %10 秒后，在文件 \"%4\" 中偏移量 %5 写入 %6 字节的尝试失败。写入操作将失败，并出现错误 %7。如果此错误持续存在，文件可能会被损坏，并可能需要从以前的备份中还原。	%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.
0x1E3	%1 (%2) %3由于系统错误 %6: \"%7\"，创建文件夹 \"%4\" 的尝试失败。创建文件夹操作将失败，错误 %5。	%1 (%2) %3An attempt to create the folder \"%4\" failed with system error %6: \"%7\". The create folder operation will fail with error %5.
0x1E4	%1 (%2) %3由于系统错误 %6:“%7”，移除文件夹“%4”的尝试失败。移除文件夹操作将失败，并出现错误 %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.
0x1E5	%1 (%2) %3由于系统错误 %6:“%7”，删除文件“%4”的尝试失败。删除文件操作将失败，并出现错误 %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.
0x1E6	%1 (%2) %3由于系统错误 %7:“%8”，将文件“%4”移动到“%5”的尝试失败。移动文件操作将失败，并出现错误 %6。	%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.
0x1E7	%1 (%2) %3由于系统错误 %7:“%8”，将文件“%4”复制到“%5”的尝试失败。复制文件操作将失败，并出现错误 %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.
0x1E8	%1 (%2) %3由于系统错误 %6:“%7”，创建文件“%4”的尝试失败。创建文件操作将失败，并出现错误 %5。	%1 (%2) %3An attempt to create the file \"%4\" failed with system error %6: \"%7\". The create file operation will fail with error %5.
0x1E9	%1 (%2) %3由于系统错误 %6:“%7”，打开文件“%4”进行只读访问的尝试失败。打开文件操作将失败，并出现错误 %5。	%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.
0x1EA	%1 (%2) %3由于系统错误 %6:“%7”，打开文件“%4”进行读/写访问的尝试失败。打开文件操作将失败，并出现错误 %5。	%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.
0x1EB	%1 (%2) %3由于系统错误 %7:“%8”，确定包含“%5”的卷“%4”的最小 I/O 块大小的尝试失败。此操作将失败，并出现错误 %6。	%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.
0x1EC	%1 (%2) %3由于严重错误，“%4”中的日志文件序列中断。对于使用此日志文件序列的数据库，将不再进行进一步的更新。请纠正此问题，并从备份重新启动或还原。	%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.
0x1ED	%1 (%2) %3在最终成功前，在文件“%4”中以偏移量 %5 读取 %6 字节的操作失败了 %7 次，每次间隔 %8 秒。以前已报告过此类失败更详细的信息。诸如这种短暂的失败可能是包含此文件的存储子系统彻底失败的先兆。	%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.
0x1EE	%1 (%2) %3由于引用了不存在的数据库“%5”，数据库恢复失败，错误为 %4。数据库被删除(也可以是移动或重命名)前，不会处于干净关闭状态。只有重新设置丢失的数据库，数据库引擎才允许完成对此实例的恢复。如果此数据库不再可用且不再需要，则 Microsoft 知识库中提供了从此错误恢复的过程，也可按照此消息底部的“详细信息”链接中的内容进行操作。	%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.
0x1EF	%1 (%2) %3“%5”上的数据库恢复失败，错误为 %4。数据库没有处于首次在日志文件中引用此数据库时的预期状态。很可能是因为已还原此数据库的某个文件副本，而非制作文件副本以后的所有日志文件在当前都可用。Microsoft 知识库中提供了从此错误恢复的过程，也可按照此消息底部的“详细信息”链接中的内容进行操作。	%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.
0x1F0	%1 (%2) %3为了成功恢复，数据库 %4 需要在 %6 处创建的日志文件 %5。恢复找到了在 %7 处创建的日志文件。	%1 (%2) %3Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7.
0x1F1	%1 (%2) %3从 %4 的标头提供的信息可看出，此文件不是数据库文件。文件的标头可能已损坏。	%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.
0x1F2	%1 (%2) %3日志序列号中存在空缺，最后使用的日志文件具有版本 %4。日志文件 %5 到 %6 已被删除，这样即可完成恢复。	%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.
0x1F3	%1 (%2) %3日志序列号中存在空缺，最后使用的日志文件具有版本 %4。日志文件 %5 (版本 %6)已被删除，这样即可完成恢复。	%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.
0x1F4	%1 (%2) %3数据库引擎丢失一页无效数据。强烈建议对数据库进行应用程序级别的完整性检查，以确保应用程序级别数据的完整性。	%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.
0x1F5	%1 (%2) %3数据库引擎修复了一个页面链接。	%1 (%2) %3The database engine repaired one page link.
0x1F6	%1 (%2) %3数据库引擎丢失了一个记录中的一列或多列无效数据。强烈建议对数据库运行应用程序级别的完整性检查，以确保应用程序级别数据的完整性。	%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.
0x1F7	%1 (%2) %3数据库引擎丢失了一个无效的数据记录。强烈建议对数据库运行应用程序级别的完整性检查，以确保应用程序级别数据的完整性。	%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.
0x1F8	%1 (%2) %3数据库引擎丢失了一个称为 %4 的表。强烈建议对数据库运行应用程序级别的完整性检查，以确保应用程序级别数据的完整性。	%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.
0x1F9	%1 (%2) %3试图打开压缩文件“%4”进行读取/写入访问时失败，因为无法将该文件转换为正常文件。打开文件操作将失败，返回错误 %5。为了防止将来出现这种错误，可以手动解压缩此文件，并将包含文件夹的压缩状态更改为未压缩。文件被压缩时无法进行写操作。	%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.
0x1FA	%1 (%2) %3试图确定包含 \"%5\" 的卷 \"%4\" 中的可用磁盘空间/总磁盘空间时失败，返回系统错误 %7: \"%8\"。此操作将失败并返回错误 %6。	%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.
0x1FB	%1 (%2) %3从文件 \"%4\" 中偏移量 %5 读取 %6 字节的请求成功，但是花费了 OS 异常的长时间(%7 秒)。此问题可能是硬件故障造成的。请与您的硬件供应商联系获得进一步协助诊断此问题。	%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.
0x1FC	%1 (%2) %3向文件 \"%4\" 中偏移量 %5 写入 %6 字节的请求成功，但是花费了 OS 异常的长时间(%7 秒)。此问题可能是硬件故障造成的。请与您的硬件供应商联系获得进一步协助诊断此问题。	%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.
0x1FD	%1 (%2) %3从文件 \"%4\" 中偏移量 %5 读取 %6 字节的请求成功，但是花费了 OS 异常的长时间(%7 秒)。另外，自 %9 秒前关于此问题的上一个消息张贴后，%8 其他对此文件的 I/O 请求也花费了异常的长时间。此问题可能是硬件故障造成的。请与您的硬件供应商联系获得进一步协助诊断此问题。	%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.
0x1FE	%1 (%2) %3向文件 \"%4\" 中偏移量 %5 写入 %6 字节的请求成功，但是花费了 OS 异常的长时间(%7 秒)。另外，自 %9 秒前关于此问题的上一个消息张贴后，%8 其他对此文件的 I/O 请求也花费了异常的长时间。此问题可能是硬件故障造成的。请与您的硬件供应商联系获得进一步协助诊断此问题。	%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.
0x200	%1 (%2) %3系统已为 %4 任务提供服务，但花费了异常多的时间(调度用了 %5 秒，执行用了 %6 秒)。	%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).
0x201	%1 (%2) %3系统已为 %4 任务提供服务，但花费了异常多的时间(调度用了 %5 秒，执行用了 %6 秒)。此外，自 %8 秒前上一个关于此问题的消息投递以来，另外还有 %7 个 %4 任务也花费了异常多的时间等待服务。	%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.
0x202	%1 (%2) %3此实例的日志序列号几乎已完全用尽。当前日志版本是接近最大日志版本 %5 的 %4，还有 %6 个要使用的日志版本。若要从版本 1 开始重新编号，必须彻底关闭该实例并删除所有日志文件。备份将变得无效。	%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.
0x203	%1 (%2) %3数据库 %4: 页 %5 验证失败，原因是刷新顺序相关性不匹配。此页应先于页 %6 刷新，而后者却先行刷新。恢复/还原将失败，并出现错误 %7。如果此情况持续存在，请从以前的备份还原数据库。引起此问题的原因可能是由于硬件出现故障而导致过去某一时间“漏掉”了一次或多次对这些页面的刷新操作。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x204	%1 (%2) %3数据库 %4: 页 %5 验证失败，原因是日志位置 %10 的时间戳不匹配。保存到日志记录的“之前”时间戳是 %6，而页上的实际时间戳是 %7。页时间戳的“之后”时间戳已更新为 %9。恢复/还原将失败，出现错误 %8。如果此情况持续存在，请从以前的备份还原数据库。此问题可能是因硬件故障引起的，过去某个时间此页上“丢失”一次或多次刷新。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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 sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.
0x205	%1 (%2) %3由于引用了与当前日志集不匹配的数据库“%5”，数据库恢复失败，并出现错误 %4。只有重新设置不匹配的数据库，数据库引擎才允许完成对此实例的恢复。如果此数据库不再可用且不再需要，则可从 Microsoft 知识库或按照此消息底部的“详细信息”链接获取从该错误进行恢复的步骤。	%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.
0x206	%1 (%2) %3日志文件 %4 丢失(错误 %5)，因此无法使用。如果此日志文件是进行恢复所必需的，则需要此日志文件的完好副本才能成功完成恢复。	%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.
0x207	%1 (%2) %3日志文件的范围 %4 到 %5 丢失(错误 %6)，因此无法使用。如果这些日志文件是进行恢复所必需的，则需要这些日志文件的完好副本才能成功完成恢复。	%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.
0x208	%1 (%2) %3日志截断失败，原因是并非进行恢复所必需的所有日志文件均已成功复制。	%1 (%2) %3Log truncation failed because not all log files required for recovery were successfully copied.
0x209	%1 (%2) %3无法计划日志文件 %4 的日志写入。错误 %5。	%1 (%2) %3Unable to schedule a log write on log file %4. Error %5.
0x20A	%1 (%2) %3尝试打开包含“%5”、名称为“%4”的设备时失败，出现系统错误 %7:“%8”。操作将失败，出现错误 %6。	%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.
0x20B	%1 (%2) %3数据库 %4 需要日志文件 %5-%6，以恢复所有已提交的数据。恢复操作只能找到 %7 之前的日志文件，找不到日志生成 %8。如果找不到该日志文件，则可手动恢复数据库，但这将导致丢失已提交的数据。%n详细信息:%n%t日志目录: %9	%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
0x20C	%1 (%2) %3数据库 %4 已丢失 %5 个提交的日志文件(%6-%7)。丢失日志弹性使 ESE 可以将此数据库恢复为一致的状态，但将丢失数据。恢复操作只能找到 %8 之前的日志文件。%n详细信息:%n%t日志目录: %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
0x20D	%1 (%2) %3日志文件 %4 已损坏、无效或无法访问(错误 %5)，因此无法使用。如果找不到该日志文件，则仍可手动恢复数据库，但这将导致丢失已提交的数据。%n详细信息:%n%t日志目录: %6	%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
0x20E	%1 (%2) %3日志文件 %5 (生成 %6)的日志(%7)已损坏或无效，由于这些提交的日志已指定为不需要的日志，因此，ESE 已删除了损坏的日志部分，从而 ESE 可以(通过生成 %4)将附加的任何数据库恢复到一致状态，但将丢失数据。	%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.
0x20F	%1 (%2) %3ESE 已删除了 %4 个提交的日志文件(%5-%6)以保持有序的日志流。丢失日志弹性使 ESE 可以恢复为一致的状态，但将丢失数据。恢复操作最多只能恢复到 %7 之前的日志文件。%n详细信息:%n%t日志目录: %8	%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
0x210	%1 (%2) %3检测到日志无序之前，恢复操作最多只能找到 %4 (生成 %5)之前的日志文件，找不到日志文件 %6 (生成 %7)。如果找不到该日志文件，则可以手动恢复数据库，但这将导致丢失已提交的数据。%n详细信息:%n%t日志目录: %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
0x211	%1 (%2) %3由于某个校验和日志记录已损坏，从文件“%4”中偏移量 %5 读取的 %6 字节日志范围验证失败。读取操作将失败，出现错误 %7。如果此情况持续存在，请从以前的备份还原日志文件。	%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.
0x212	%1 (%2) %3由于丢失的刷新检测时间戳不匹配，从文件“%4”读取的数据库页(数据库页 %8，%6 字节，偏移量 %5)验证失败。读取操作将失败，出现错误 %7。%n数据库页 %8 上的刷新状态为 %9，而刷新映射页 %10 上的刷新状态为 %11。%n如果此情况持续存在，请从以前的备份还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，以寻求诊断该问题的进一步协助。	%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.
0x213	%1 (%2) %3数据库引擎尝试在数据库 %5 的页面 %4 上进行全新写入操作。此操作的目的是为了更正先前读取该页的问题。	%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.
0x214	%1 (%2) %3从文件“%4”中偏移量 %5 读取 %6 字节的请求在 %7 秒内未完成。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x215	%1 (%2) %3在文件“%4”中偏移量 %5 写入 %6 字节的请求在 %7 秒内未完成。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x216	%1 (%2) %3对文件“%4”中页码“%5”处的修补程序请求失败，出现错误 %6。如果此情况持续存在，请使用早期的备份集执行还原。	%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.
0x217	%1 (%2) %3尝试确定包含“%4”的卷的最小 I/O 块大小失败。将使用 512 字节的默认扇区大小。	%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.
0x218	%1 (%2) %3尝试创建临时数据库 %4 失败，错误为 %5。	%1 (%2) %3An attempt to create temporary database %4 failed with error %5.
0x219	%1 (%2) %3已为数据库 %8 的 B 树(ObjectId: %5，PgnoRoot: %6)请求空白页面(Pgno: %7)上的节点(错误 %4)。这通常是由于存储硬件的 I/O 丢失导致的。请咨询您的硬件供应商以获取最新固件版本，对控制器的缓存参数进行更改，使用支持强制单元访问的崩溃状态一致硬件，和/或替换出现故障的硬件。	%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 ForcedUnit Access support, and/or replace faulty hardware.
0x21A	%1 (%2) %3数据库 %4: 页 %5 验证失败，原因是日志位置 %10 的时间戳不匹配。保留在日志记录中的远程(“之前”)时间戳是 %6，但页面上的实际时间戳是 %7 (注意: DbtimeCurrent = %9)。这表示主动节点丢失了刷新(错误 %8)。此问题可能是硬件故障造成的，即过去某一时间，硬件在主动节点上“漏掉”了一次或多次对此页面的刷新操作。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x21B	%1 (%2) %3数据库 %4: 页 %5 验证失败，原因是日志位置 %10 的时间戳不匹配。保留在日志记录中的远程(“之前”)时间戳是 %6，但页面上的实际时间戳是 %7 (注意: DbtimeCurrent = %9)。这表示被动节点丢失了刷新(错误 %8)。此问题可能是硬件故障造成的，即过去某一时间，硬件在被动节点上“漏掉”了一次或多次对此页面的刷新操作。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x21C	%1 (%2) %3数据库 %4: 第 %5 页逻辑数据校验和 %6 无法匹配日志位置 %9 处记录的扫描检查 %7 校验和(种子 %8)。	%1 (%2) %3Database %4: Page %5 logical data checksum %6 failed to match logged scan check %7 checksum (seed %8) at log position %9.
0x21D	%1 (%2) %3数据库 %4: 第 %5 页在日志位置 %8 处显示为未初始化，而保留在日志记录中的远程(\"之前\")时间戳是 %6(注意: DbtimeCurrent = %7)。	%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).
0x21E	%1 (%2) %3Database %4: Page %5 (objid %6) has a logical corruption of type '%7'.%nDetails: %8	%1 (%2) %3Database %4: Page %5 (objid %6) has a logical corruption of type '%7'.%nDetails: %8
0x21F	%1 (%2) %3日志文件 %4 中前一个日志的累积段校验和不匹配，预期: %5，实际: %6。	%1 (%2) %3Previous log's accumulated segment checksum mismatch in logfile %4, Expected: %5, Actual: %6.
0x220	%1 (%2) %3由于存在的丢失刷新检测时间戳不匹配，从文件“%4”读取的数据库页(数据库页 %8，%6 字节，偏移量 %5)验证失败。读取操作将失败，出现错误 %7。%n数据库页 %8 上的刷新状态为 %9，而刷新映射页 %10 上的刷新状态为 %11。%n如果此情况持续出现，请从以前的备份还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，以寻求诊断该问题的进一步协助。	%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.
0x221	%1 (%2) %3数据库 %4: 页面 %5 似乎未在远程节点上的日志位置 %10 处进行初始化。日志记录中存在的远程(“之前”)时间戳为 %6，但该页面上的实际时间戳为 %7 (注意: DbtimeCurrent = %9)。这表明活动节点丢失了刷新(错误 %8)。此问题可能是因硬件故障引起的，即过去某一时间，硬件在活动节点上“漏掉”了一次或多次对此页面的刷新操作。请与硬件供应商联系，以寻求诊断该问题的进一步协助。	%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.
0x222	%1 (%2) %3日志生成(%4)太小(%5)，此数据库引擎不支持或无法重播(支持的最小值为 %6)。	%1 (%2) %3The log generation (%4) is too low (%5) to be supported or replayed by this database engine (min supported %6).
0x223	%1 (%2) %3日志生成(%4)太大(%5)，此数据库引擎不支持或无法重播(支持的最大值为 %6)。	%1 (%2) %3The log generation (%4) is too high (%5) to be supported or replayed by this database engine (max supported %6).
0x224	%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) %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
0x225	%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) %3A Database %4 has a page (pgno %5) with too few lines, operation attempted on line %6, actual number of lines on page %7.
0x226	%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) %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.
0x227	%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.	%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.
0x258	%1 (%2) %3数据库引擎在表 %4 中遇到意外的重复关键字。已丢弃一条记录。	%1 (%2) %3The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped.
0x259	%1 (%2) %3数据库引擎无法在文件 %5 中找到入口点 %4。	%1 (%2) %3The database engine could not find the entrypoint %4 in the file %5.
0x25A	%1 (%2) %3数据库“%4”: 后台清除跳过的页面。非高峰期扩展联机的维护窗口，可能对数据库比较有利。如果此消息持续存在，可能需要运行脱机碎片整理，从数据库中删除所有跳过的页面。	%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.
0x25B	%1 (%2) %3数据库“%4”: 尝试回收 B-目录树(ObjectId %7)上的空间时，数据库引擎丢失了未使用的页面 %5-%6。只有执行脱机碎片整理之后，才能重新回收空间。	%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.
0x25C	%1 (%2) %3区域设置 ID %4 (%5 %6)无效、未安装在此计算机上或无法进行验证，出现系统错误 %7:“%8”。操作将失败，出现错误 %9。	%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.
0x25D	%1 (%2) %3表“%5”中的列“%4”已转换为一个标记的列。	%1 (%2) %3Column '%4' of Table '%5' was converted to a Tagged column.
0x25E	%1 (%2) %3表“%5”中的列“%4”已转换为一个未标记的列。	%1 (%2) %3Column '%4' of Table '%5' was converted to a non-Tagged column.
0x25F	%1 (%2) %3表“%5”中的列“%4”已从二进制转换为长二进制。	%1 (%2) %3Column '%4' of Table '%5' was converted from Binary to LongBinary.
0x260	%1 (%2) %3表“%5”中的列“%4”已从文本转换为长文本。	%1 (%2) %3Column '%4' of Table '%5' was converted from Text to LongText.
0x261	%1 (%2) %3由于 Windows 版本已经从 %5.%6.%7 SP%8 升级至 %9.%10.%11 SP%12，数据库引擎正开始对数据库“%4”进行索引清除。此消息是通知性的，并没有指出数据库中的问题。	%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.
0x262	%1 (%2) %3由于 Windows 版本已经升级至 %5.%6.%7 SP%8，数据库引擎正开始对数据库“%4”进行索引清除。此消息是通知性的，并没有指出数据库中的问题。	%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.
0x263	%1 (%2) %3数据库“%4”: 此系统中的 Windows 版本升级之后，作为一种预防措施，将重建表“%6”中的二级索引“%5”。此消息是通知性的，并没有指出数据库中的问题。	%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.
0x264	%1 (%2) %3数据库引擎已成功完成对数据库“%4”的索引清除。	%1 (%2) %3The database engine has successfully completed index cleanup on database '%4'.
0x265	%1 (%2) %3数据库“%4”: 表“%6”的主索引“%5”与排序库过期。如果在这种状态(即未重建)下使用，则可能会损坏或进一步损坏。如果没有后续事件显示此索引正在重建，请对数据库进行碎片整理以重建索引。	%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.
0x266	%1 (%2) %3数据库“%4”: 表“%6”的辅助索引“%5”与排序库过期。如果在这种状态(即未重建)下使用，则可能会损坏或进一步损坏。如果没有后续事件显示此索引正在重建，请对数据库进行碎片整理以重建索引。	%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.
0x267	%1 (%2) %3数据库引擎正在将数据库“%4”从格式 %5 转换为格式 %6。	%1 (%2) %3The database engine is converting the database '%4' from format %5 to format %6.
0x268	%1 (%2) %3数据库引擎已成功地将数据库“%4”从格式 %5 转换为格式 %6。	%1 (%2) %3The database engine has successfully converted the database '%4' from format %5 to format %6.
0x269	%1 (%2) %3已尝试使用数据库“%4”，但此数据库上的转换没有成功完成。请从备份中还原，然后重新运行数据库转换。	%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.
0x26A	%1 (%2) %3数据库“%4”: 数据库引擎在 B-目录树(ObjectId: %6, PgnoRoot: %7)上建立了 %5 空间目录树节点的内存缓存，以优化此 B-目录树的空间请求。空间缓存的建立花费了 %8 毫秒。此消息是通知性的，并没有指出数据库中的问题。	%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.
0x26B	%1 (%2) %3尝试附加数据库“%4”，但它是从备份集还原而来的，而该备份集上未启动硬恢复或硬恢复未成功完成。	%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.
0x26C	%1 (%2) %3无法转换记录 %4:%5:%6 的记录格式。	%1 (%2) %3Unable to convert record format for record %4:%5:%6.
0x26D	%1 (%2) %3数据库“%4”: B-目录树 ID (ObjectID)已用完。可用/未使用的 B-目录树 ID 可以通过对数据库执行脱机碎片整理而回收。	%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.
0x26E	%1 (%2) %3数据库“%4”: 可用 B-目录树 ID (ObjectID)几乎被完全消耗。可用/未使用的 B-目录树 ID 可以通过对数据库执行脱机碎片整理而回收。	%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.
0x26F	%1 (%2) %3用于此示例(%4)的版本存储已达到其最大值 %5Mb。很可能是因为长时间运行的事务阻碍了版本存储的清除而导致了版本存储增大。直到长时间运行的事务完全提交或回滚后才能进行更新。。%n可能的长时间运行事务处理:%n%t会话 ID: %6%n%t会话上下文: %7%n%t会话上下文线程 ID: %8%n%t清理: %9%n%t会话跟踪:%n%10	%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
0x270	%1 (%2) %3此实例(%4)的版本存储无法增长，因为接收到了来自 OS 的“内存不足”错误。很可能是因为长时间运行的事务阻碍了版本存储的清除而导致了版本存储增大。直到长时间运行的事务完全提交或回滚后才能进行更新。%n此示例的当前版本存储大小: %5Mb%n此示例的最大版本存储大小: %6Mb%n为所有版本存储预留的全局内存: %7Mb%n可能长时间运行的事务: %n%t会话 ID: %8%n%t会话上下文: %9%n%t会话上下文线程 ID: %10%n%t清理: %11%n%t会话跟踪:%n%12	%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
0x271	%1 (%2) %3数据库引擎不支持 LCMapString() 标志 %4。	%1 (%2) %3The database engine does not support the LCMapString() flags %4.
0x272	%1 (%2) %3数据库引擎更新了数据库 %5 中的 %4 索引项，因为 NLS 版本中的更改。此消息仅供参考，并不表示数据库中存在问题。	%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.
0x273	%1 (%2) %3数据库引擎无法更新数据库 %5 中的索引项，因为数据库是只读的。	%1 (%2) %3The database engine was unable to updated index entries in database %5 because the database is read-only.
0x274	%1 (%2) %3数据库“%4”: 尝试移动到 B 树中的下一个或上一个节点时，数据库引擎花了 %17 毫秒(出现故障时等待 %18 毫秒)跳过 %8 个页面(%19 个页面出现故障)中的 %7 个不可见节点。这些不可见节点很可能是已标记为删除但还没有清除的节点。该数据库可能需要在非工作高峰期间内扩大联机维护时间范围，以便清除这样的节点，并回收它们的空间。如果此消息再次出现，可以运行脱机碎片整理，删除已标记为删除但还没有从数据库中清除的节点。%n%t名称: %5%n%t所属表: %6%n%tObjectId: %9%n%tPgnoRoot: %10%n%t类型: %11%n%t非版本控制删除: %12%n%t未提交的删除: %13%n%t已提交的删除: %14%n%t不可见的插入: %15%n%t已筛选: %16%n%tDbtime 分散: %20	%1 (%2) %3Database '%4': While attempting to move to the next orprevious node in a B-Tree, the database engine took %17 milliseconds (waiting %18 milliseconds on faults) to skip over %7non-visible nodes in %8 pages (faulting in %19 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%n%tFiltered: %16%n%tDbtime Distrib: %20
0x275	%1 (%2) %3数据库“%4”: 尝试移动到 B 树中的下一个或上一个节点时，数据库引擎花了 %21 毫秒(出现故障时等待 %22 毫秒)跳过 %8 个页面(%23 个页面出现故障)中的 %7 个不可见节点。此外，由于此消息上次在 %16 小时之前报告，在此 B 树中的导航期间遇到过多不可见节点的 %17 个其他事件(跳过 %19 页中总共 %18 个节点)。这些不可见节点很可能是已标记为删除但还没有清除的节点。该数据库可能需要在非工作高峰期间内扩大联机维护时间范围，以便清除这样的节点，并回收它们的空间。如果此消息再次出现，可以运行脱机碎片整理，删除已标记为删除但还没有从数据库中清除的节点。%n%t名称: %5%n%t所属表: %6%n%tObjectId: %9%n%tPgnoRoot: %10%n%t类型: %11%n%t非版本控制删除: %12%n%t未提交的删除: %13%n%t已提交的删除: %14%n%t不可见的插入: %15 %n%t已筛选: %20%n%tDbtime 分散: %24	%1 (%2) %3Database '%4': While attempting to move to the next orprevious node in a B-Tree, the database engine took %21 milliseconds (waiting %22 milliseconds on faults) to skip over %7non-visible nodes in %8 pages (faulting in %23 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%n%tFiltered: %20%n%tDbtime Distrib: %24
0x276	%1 (%2) %3此实例(%4)的版本存储具有超过最大事务大小的长时间运行的事务。%n此实例的当前版本存储大小: %5Mb%n此实例的最大事务大小: %6Mb%n此实例的最大版本存储大小: %7Mb%n长时间运行的事务:%n%t会话 ID: %8%n%t会话上下文: %9%n%t会话上下文线程 ID: %10%n%t清理: %11%n%t会话跟踪:%n%12	%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
0x277	%1 (%2) %3文件系统报告 %4 处的数据库文件的扇区大小为 %5，大于页面大小 %6。这可能会导致较高的断写损坏发生率和/或导致数据库因丢失刷新而损坏。	%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.
0x278	%1 (%2) %3文件系统报告 %4 处的日志文件的扇区大小为 %5，这不受支持，改用扇区大小 4096。这可能会导致事务持久性丢失。	%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.
0x279	%1 (%2) %3恢复必须暂停(%4 毫秒)以允许较旧的只读事务完成。如果此情况持续出现，则可能产生过时的副本。	%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.
0x27A	%1 (%2) %3恢复必须暂停很长一段时间(%4 毫秒)以允许较旧的只读事务完成。如果此情况持续出现，则可能产生过时的副本。	%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.
0x27B	%1 (%2) %3无法附加刷新映射文件“%4”，出现错误 %5。	%1 (%2) %3Failed to attach flush map file \"%4\" with error %5.
0x27C	%1 (%2) %3刷新映射文件“%4”将被删除。原因: %5。	%1 (%2) %3Flush map file \"%4\" will be deleted. Reason: %5.
0x27D	%1 (%2) %3将创建新的刷新映射文件“%4”以启用持久丢失刷新检测。	%1 (%2) %3New flush map file \"%4\" will be created to enable persisted lost flush detection.
0x27E	%1 (%2) %3验证刷新映射文件“%6”上的页面 %5 时出现错误 %4。数据库页面的刷新类型将设置为“未知”状态。	%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.
0x27F	%1 (%2) %3在刷新映射文件“%5”的页面 %4 上检测到不一致的时间戳(如果刷新映射持久性已禁用则为空)。刷新映射上的最大时间戳是 %6，但数据库页 %7 的时间戳是 %8。如果刷新映射持久性已启用，则此问题可能是由硬件故障造成的。请与硬件供应商联系，以寻求诊断问题的进一步协助。	%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.
0x280	%1 (%2) %3验证刷新映射文件“%5”上的标头页时出现错误 %4。刷新映射文件将失效。%n其他信息: %6	%1 (%2) %3Error %4 validating header page on flush map file \"%5\". The flush map file will be invalidated.%nAdditional information: %6
0x281	%1 (%2) %3由于当前日志格式为 %6 (由参数 %4 控制)，因此无法使用日志格式功能版本 %5。	%1 (%2) %3The log format feature version %5 could not be used due to the current log format %6, controlled by the parameter %4.
0x282	%1 (%2) %3由于当前数据库格式为 %6 (由参数 %4 控制)，因此无法使用数据库格式功能版本 %5。	%1 (%2) %3The database format feature version %5 could not be used due to the current database format %6, controlled by the parameter %4.
0x2BC	%1 (%2) %3联机碎片整理正开始全面检查数据库“%4”。	%1 (%2) %3Online defragmentation is beginning a full pass on database '%4'.
0x2BD	%1 (%2) %3联机碎片整理已完成对数据库“%4”的全面检查，释放了 %5 个页面。此检查开始于 %6，总共运行了 %7 秒，在 %9 天内要求进行 %8 次调用。自该数据库创建以来，已对其进行了 %10 次完全的碎片整理。	%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.
0x2BE	%1 (%2) %3联机碎片整理正在恢复对数据库“%4”的全面检查。此检查开始于 %5，已运行了 %6 天。	%1 (%2) %3Online defragmentation is resuming its pass on database '%4'. This pass started on %5 and has been running for %6 days.
0x2BF	%1 (%2) %3联机碎片整理已完成对数据库“%4”的继续检查，释放了 %5 个页面。此检查开始于 %6，总共运行了 %7 秒，在 %9 天内要求进行 %8 次调用。自该数据库创建以来，已在对其进行了 %10 次完全的碎片整理。	%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.
0x2C0	%1 (%2) %3对数据库“%4”进行的联机碎片整理被中断并已终止。下次在此数据库上启动联机碎片整理时，将从中断点恢复整理。	%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.
0x2C1	%1 (%2) %3由于遇到意外错误 %5，对数据库“%4”进行的联机碎片整理被提前终止。下次在此数据库上启动联机碎片整理时，将从中断点恢复整理。	%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.
0x2C2	%1 (%2) %3已开始对数据库 %4 进行联机零位调整	%1 (%2) %3Online zeroing of database %4 started
0x2C3	%1 (%2) %3%5 秒后，完成对数据库 %4 进行的联机零位调整，出现错误 %6%n%7 页面%n%8 空白页面%n%9 上一次零位调整后未更改的页面%n%10 未使用的零位调整页面%n%11 发现已使用的页面%n%12 删除的零位调整记录%n%13 没有涉及的数据块零位调整	%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
0x2C4	%1 (%2) %3联机碎片整理正开始全面检查数据流文件“%4”。	%1 (%2) %3Online defragmentation is beginning a full pass on streaming file '%4'.
0x2C5	%1 (%2) %3联机碎片整理已完成对数据流文件“%4”的全面检查。	%1 (%2) %3Online defragmentation has completed a full pass on streaming file '%4'.
0x2C6	%1 (%2) %3对数据流文件“%4”进行的联机碎片整理将此文件缩小了 %5 字节。	%1 (%2) %3Online defragmentation of streaming file '%4' has shrunk the file by %5 bytes.
0x2C7	%1 (%2) %3由于遇到意外错误 %5，对数据流文件“%4”进行的联机碎片整理被提前终止。	%1 (%2) %3Online defragmentation of streaming file '%4' terminated prematurely after encountering unexpected error %5.
0x2C8	%1 (%2) %3已开始对数据流文件“%4”进行联机零位调整。	%1 (%2) %3Online zeroing of streaming file '%4' started.
0x2C9	%1 (%2) %3%5 秒后，完成了对数据流文件 '%4' 的联机零位调整，出现错误 %6%n%7 页面%n%8 未使用的零位调整页面%n	%1 (%2) %3Online zeroing of streaming file '%4' finished after %5 seconds with err %6%n%7 pages%n%8 unused pages zeroed%n
0x2CA	%1 (%2) %3成功停止了对数据流文件“%4”执行的联机碎片整理。	%1 (%2) %3Online defragmentation has successfully been stopped on streaming file '%4'.
0x2CB	%1 (%2) %3在过去 60 分钟内，以下数据库的联机碎片整理已暂停一次或多次:“%4”。ESE 数据库缓存不足，无法针对列出的数据库同时运行联机碎片整理。操作: 将与列出的数据库相对应的联机维护时间窗口错开，或增加服务器中物理 RAM 的数量。	%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.
0x2CC	%1 (%2) %3在过去 60 分钟内，以下数据库的联机碎片整理已恢复一次或多次:“%4”。	%1 (%2) %3Online defragmentation has resumed one or more times in the last 60 minutes for the following databases: \"%4'.
0x2CD	%1 (%2) %3联机维护正在为数据库“%4”启动数据库校验和检查后台任务。	%1 (%2) %3Online Maintenance is starting Database Checksumming background task for database '%4'.
0x2CE	%1 (%2) %3联机维护正在为数据库“%4”启动数据库页清零后台任务。	%1 (%2) %3Online Maintenance is starting Database Page Zeroing background task for database '%4'.
0x2CF	%1 (%2) %3联机维护正在为数据库“%4”恢复数据库校验和检查后台任务。此任务开始于 %5 并已运行了 %6 天。	%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.
0x2D0	%1 (%2) %3联机维护正在为数据库“%4”恢复数据库页清零后台任务。此任务开始于 %5 并已运行了 %6 天。	%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.
0x2D1	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务已完成。此任务开始于 %5，总共运行了 %6 秒，在 %8 天内要求进行 %7 次调用。操作摘要:%n%9 个页被显示%n%10 个不正确校验和%n%11 个未初始化页	%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
0x2D2	%1 (%2) %3数据库“%4”的联机维护数据库清零后台任务已完成。此任务开始于 %5，总共运行了 %6 秒，在 %8 天内要求进行 %7 次调用。操作摘要:%n%9 个页被显示%n%10 个不正确校验和%n%11 个未初始化页%n%12 个页自上次清零后未更改%n%13 个未使用的页被清零%n%14 个已使用的页被显示%n%15 条已删除的记录被清零%n%16 个未引用的数据块被清零	%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
0x2D3	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务在 %6 秒后遇到错误 %5。	%1 (%2) %3Online Maintenance Database Checksumming background task for database '%4' encountered error %5 after %6 seconds.
0x2D4	%1 (%2) %3数据库“%4”的联机维护数据库清零后台任务在 %6 秒后遇到错误 %5。	%1 (%2) %3Online Maintenance Database Zeroing background task for database '%4' encountered error %5 after %6 seconds.
0x2D5	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务已中断并已终止。下一次在此数据库上启动联机维护数据库校验和检查时，该校验和检查将从中断点恢复。	%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.
0x2D6	%1 (%2) %3数据库“%4”的联机维护数据库清零后台任务已中断并已终止。下一次在此数据库上启动联机维护数据库校验和检查时，该校验和检查将从中断点恢复。	%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.
0x2D7	%1 (%2) %3由于页校验和不匹配，因此从文件“%4”中偏移量 %5 (数据库第 %6 页)读取的数据库页验证失败。如果此情况持续存在，请从以前的备份还原数据库。此问题可能是因硬件故障引起的。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x2D8	%1 (%2) %3联机碎片整理已经对数据库“%4”中表“%5”的索引“%6”进行碎片整理。此任务开始于 %7。%n%8 个页被访问%n%9 个页被释放%n%10 次部分合并%n%11 个页被移动	%1 (%2) %3Online 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
0x2D9	%1 (%2) %3在过去 60 分钟内，以下数据库的联机维护数据库清零已暂停一次或多次:“%4”。ESE 数据库缓存不足，无法针对列出的数据库同时运行联机页清零。操作: 将与列出的数据库相对应的联机维护时间窗口错开，或增加服务器中物理 RAM 的数量。	%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.
0x2DA	%1 (%2) %3在过去 60 分钟内，以下数据库的联机维护数据库清零已恢复一次或多次:“%4”。	%1 (%2) %3Online maintenance database zeroing has resumed one or more times in the last 60 minutes for the following databases: '%4'.
0x2DC	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务已完成。此任务开始于 %5，在 %8 个页上总共运行了 %6 秒(在 %7 天之内)。	%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.
0x2DD	%1 (%2) %3对数据库“%4”的联机维护数据库校验和检验后台任务没有准时完成。此任务开始于 %5，到目前为止连续运行了 %6 秒(超过 %7 天)。	%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.
0x2DE	%1 (%2) %3数据库“%4”的数据库维护后台任务无法启动，错误为 %5。	%1 (%2) %3Database Maintenance background task for database '%4' failed to start with error %5.
0x2DF	%1 (%2) %3数据库“%4”的数据库维护任务已完全完成。此任务开始于 %5，总共运行了 %6 秒(在 %7 天之内)。此数据库维护任务超过了 %8 天维护完成阈值。应执行以下一项或多项操作: 提高承载数据库的卷的 IO 性能/吞吐量，减小数据库大小，和/或减少非数据库维护 IO。%n%9 个页被显示%n	%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
0x2E0	%1 (%2) %3数据库“%4”的数据库维护正在启动。	%1 (%2) %3Database Maintenance is starting for database '%4'.
0x2E1	%1 (%2) %3数据库“%4”的数据库维护任务已完全完成。此任务开始于 %5，总共运行了 %6 秒。%n%7 个页被显示%n	%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
0x2E2	%1 (%2) %3数据库“%4”的数据库维护正在继续，从页面 %5 开始。此任务开始于 %6，已经运行了 %7 天。	%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.
0x2E3	%1 (%2) %3数据库“%4”的 NTFS 文件属性大小为 %5 字节，超过了阈值 %6 字节。数据库文件必须重新设定种子或从副本或备份还原，以防止因文件系统限制而使数据库文件无法增长。	%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.
0x2E4	%1 (%2) %3定期数据库缩减文件操作已启动。	%1 (%2) %3The periodic database shrink file operation started.
0x2E5	%1 (%2) %3定期数据库缩减文件操作已成功完成，将数据库文件缩减了 %4 个页面。	%1 (%2) %3The periodic database shrink file operation finished successfully and shrunk the database file by %4 pages.
0x2E6	%1 (%2) %3定期数据库缩减文件操作无法缩减数据库文件，因为没有足够的内部可用空间。	%1 (%2) %3The periodic database shrink file operation was not able to shrink the database file because there is not enough internal free space available.
0x2E7	%1 (%2) %3定期数据库缩减文件操作无法缩减数据库文件。结果为 %4。	%1 (%2) %3The periodic database shrink file operation was not able to shrink the database file. Result %4.
0x2E8	%1 (%2) %3数据库“%4”的数据库维护正在运行。此任务开始于 %5，已经运行了 %6 小时。%n%7 个页被显示%n	%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
0x2E9	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务在第 %5 页中止，由于客户端请求(通常因为关键恢复活动必须快速执行)。%n上次正确完成的校验和检查任务位于 %6 上。	%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).%nThe last properly completed checksumming task was on %6.
0x2EA	%1 (%2) %3数据库“%4”的联机维护数据库校验和检查后台任务已完成中断且不完整的扫描。中断通常是因为客户端请求(通常因为关键恢复活动必须快速执行)导致的。%n上次正确完成的校验和检查扫描位于 %5 上。	%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).%nThe last fully completed checksumming scan was on %5.
0x2EB	%1 (%2) %3联机维护正在为数据库“%4”恢复数据库校验和检查后台任务，已跳过 %5 页(%6%%)。上次停止: %7，此次开始: %8。%n	%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
0x320	%1 (%2) %3系统参数缓存最小值(%4)小于会话数量(%5)的 4 倍。	%1 (%2) %3System parameter minimum cache size (%4) is less than 4 times the number of sessions (%5).
0x321	%1 (%2) %3系统参数缓存最大值(%4)小于缓存最小值(%5)。	%1 (%2) %3System parameter maximum cache size (%4) is less than minimum cache size (%5).
0x322	%1 (%2) %3系统参数缓存最大值(%4)小于停止清理刷新阈值(%5)。	%1 (%2) %3System parameter maximum cache size (%4) is less than stop clean flush threshold (%5).
0x323	%1 (%2) %3系统参数停止清理刷新阈值(%4)小于起始清理刷新阈值(%5)。	%1 (%2) %3System parameter stop clean flush threshold (%4) is less than start clean flush threshold (%5).
0x324	%1 (%2) %3系统参数日志缓冲区大小(%4 个扇区)大于最大值 %5KB(日志文件大小减去保留空间)。	%1 (%2) %3System parameter log buffer size (%4 sectors) is greater than the maximum size of %5 k bytes (logfile size minus reserved space).
0x325	%1 (%2) %3系统参数最大版本页面(%4)小于首选版本页面(%5)。	%1 (%2) %3System parameter max version pages (%4) is less than preferred version pages (%5).
0x326	%1 (%2) %3由于物理内存的限制，系统参数首选版本页面已从 %4 更改为 %5。	%1 (%2) %3System parameter preferred version pages was changed from %4 to %5 due to physical memory limitation.
0x327	%1 (%2) %3系统参数最大打开表(%4)少于首选打开表(%5)。请检查注册表设置。	%1 (%2) %3System parameter max open tables (%4) is less than preferred opentables (%5). Please check registry settings.
0x328	%1 (%2) %3系统参数首选版本页面(%4)大于最大版本页面(%5)。首选版本页面从 %6 更改为 %7。	%1 (%2) %3System parameter preferred version pages (%4) is greater than max version pages (%5). Preferred version pages was changed from %6 to %7.
0x384	%1 (%2) %3数据库引擎尝试记录事务提交时出现故障，错误为 %4。为确保数据库一致性，此进程被终止。只需重新启动进程，即可强制恢复数据库，并将数据库返回到干净关闭状态。	%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.
0x385	%1 (%2) %3内部跟踪: %4 (%5)	%1 (%2) %3Internal trace: %4 (%5)
0x386	%1 (%2) %3数据库引擎检测到多个线程正非法使用相同的数据库会话执行数据库操作。%n%t会话 ID: %4%n%t会话上下文: %5%n%t会话上下文线程 ID: %6%n%t当前线程 ID: %7%n%t会话跟踪:%n%8	%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
0x387	%1 (%2) %3数据库引擎检测到同一会话中两个不同的游标试图在同一时间非法更新同一记录。%n%t会话 ID: %4%n%t线程 ID: %5%n%t数据库: %6%n%t表: %7%n%t当前游标: %8%n%t拥有最初更新的游标: %9%n%t书签大小(前缀/后缀): %10%n%t会话跟踪:%n%11	%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
0x388	%1 (%2) %3测试 API 已用于损坏数据库“%5”的页面 %4。	%1 (%2) %3A test API has been used to corrupt page %4 of database '%5'.
0x389	%1 (%2) %3数据库引擎已修复数据库“%5”中损坏的页面 %4。尽管已修复损坏，但损坏的来源可能来自出故障的硬件，应加以调查。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x38A	%1 (%2) %3有相当大的一部分数据库缓冲区缓存已写入到系统页面文件。这可能导致严重的性能降级。%n有关可能原因的完整详细信息，请参阅帮助链接。%n之前的缓存驻留状态: %4% (%5 个缓冲区，共 %6 个) (%7 秒之前)%n当前的缓存驻留状态: %8% (%9 个缓冲区，共 %10 个)%n当前缓存大小与目标: %11% (%12 MB)%n物理内存/RAM 大小: %13 MB	%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
0x38B	%1 (%2) %3检测到暂时性内存损坏。请运行 Windows 内存诊断工具和/或调查硬件问题。	%1 (%2) %3A transient memory corruption was detected. Please run the Windows Memory Diagnostics Tool and/or investigate hardware issues.
0x38C	%1 (%2) %3因不可恢复的失败而终止进程: %4 (%5)	%1 (%2) %3Terminating process due to non-recoverable failure: %4 (%5)
0x38D	%1 (%2) %3因不可恢复的失败而终止进程: 对数据库“%6”执行操作 %4 (%5)。	%1 (%2) %3Terminating process due to non-recoverable failure: %4 (%5) in operation on database '%6'.
0x38E	%1 (%2) %3数据库缓存大小维护任务已用了 %4 秒，但没有完成。这可能会导致服务器性能下降。当前缓存大小为 %5 个缓冲区，超过配置的缓存限制(目标百分比为 %6)。缓存大小维护已逐出 %7 个缓冲区，进行了 %8 次刷新尝试，成功刷新了 %9 个缓冲区。自触发维护以来，它已运行了 %10 次。	%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.
0x38F	%1 (%2) %3数据库引擎已修复数据库“%6”中损坏的页面 %4 - %5。尽管已修复损坏，但损坏的来源可能来自出故障的硬件，应加以调查。请与硬件供应商联系，寻求进一步的问题诊断帮助。	%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.
0x390	%1 (%2) %3一部分数据库缓冲区缓存已从系统页面文件还原，现在再次驻留在内存中。在这之前，一部分数据库缓冲区缓存已写出到系统页面文件，导致性能下降。%n之前的缓存驻留状态: %4% (%5 个缓冲区，共 %6 个) (%7 秒之前)%n当前的缓存驻留状态: %8% (%9 个缓冲区，共 %10 个)	%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)
0x391	%1 (%2) %3以前的 ESE 应用程序实例未设置参数 %4 为单一值，但当前 ESE 应用程序已设置为不同的值。这是系统参数不匹配，所有 ESE 应用程序的所有全局系统参数必须相同。	%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.
0x392	%1 (%2) %3以前的 ESE 应用程序实例未设置参数 %4，但当前 ESE 应用程序已设置该参数。这是系统参数不匹配，所有 ESE 应用程序的所有全局系统参数必须相同。	%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.
0x393	%1 (%2) %3以前的 ESE 应用程序实例已设置参数 %4，但当前 ESE 应用程序未设置该参数。这是系统参数不匹配，所有 ESE 应用程序的所有全局系统参数必须相同。	%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.
0x394	%1 (%2) %3由于 Beta 网站模式设置 %6，%5 中已启用 Beta 功能 %4。	%1 (%2) %3The beta feature %4 is enabled in %5 due to the beta site mode settings %6.
0x3E8	%1 (%2) %3使用以下设置激活资源故障模拟:\\t\\t%4:\\t%5\\t\\t%6:\\t%7\\t\\t%8:\\t%9\\t\\t%10:\\t%11	%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
0x3E9	%1 (%2) %3允许资源故障模拟 %4。	%1 (%2) %3Resource failure simulation %4 is permitted.
0x3EA	%1 (%2) %3拒绝资源故障模拟 %4。	%1 (%2) %3Resource Failure Simulation %4 is denied.
0x3EB	%1 (%2) %3JET 调用 %4 返回错误 %5。%6 (%7)	%1 (%2) %3JET call %4 returned error %5. %6 (%7)
0x3EC	%1 (%2) %3JET 嵌入错误 %4 跳至标签 %5。%6 (%7)	%1 (%2) %3JET inline error %4 jumps to label %5. %6 (%7)
0x7D0	%1 (%2) %3卷影副本功能 %4() = %5。	%1 (%2) %3Shadow copy function %4() = %5.
0x7D1	%1 (%2) %3卷影副本实例 %4 冻结已开始。	%1 (%2) %3Shadow copy instance %4 freeze started.
0x7D2	%1 (%2) %3卷影副本实例 %4 冻结时出错 %5。	%1 (%2) %3Shadow copy instance %4 encountered error %5 on freeze.
0x7D3	%1 (%2) %3卷影副本实例 %4 冻结已停止。	%1 (%2) %3Shadow copy instance %4 freeze ended.
0x7D4	%1 (%2) %3卷影副本实例 %4 冻结超时(%5 ms)。	%1 (%2) %3Shadow copy instance %4 freeze timed-out (%5 ms).
0x7D5	%1 (%2) %3卷影复制实例 %4 正在启动。这将是一次完整的卷影复制。	%1 (%2) %3Shadow copy instance %4 starting. This will be a Full shadow copy.
0x7D6	%1 (%2) %3卷影复制实例 %4 已成功完成。	%1 (%2) %3Shadow copy instance %4 completed successfully.
0x7D7	%1 (%2) %3卷影复制实例 %4 已终止。	%1 (%2) %3Shadow copy instance %4 aborted.
0x7D8	%1 (%2) %3卷影复制实例 %4 正在启动。这将是一次增量卷影复制。	%1 (%2) %3Shadow copy instance %4 starting. This will be an Incremental shadow copy.
0x7D9	%1 (%2) %3卷影复制实例 %4 正在启动。这将是一次副本卷影复制。	%1 (%2) %3Shadow copy instance %4 starting. This will be a Copy shadow copy.
0x7DA	%1 (%2) %3卷影复制实例 %4 正在启动。这将是一次差异卷影复制。	%1 (%2) %3Shadow copy instance %4 starting. This will be a Differential shadow copy.
0x9C4	%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 initialize the FPGA failed with error %4. Please make sure that the FPGA hardware is present and configured correctly.
0x9C5	%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 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.
0x9C6	%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 transient failure. The engine has encountered the following FPGA failures since it started:Permanent = %5, Transient = %6, HEX Resets = %7
0x9C7	%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 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
0x9C8	%1 (%2) %3An attempt to acquire an FPGA slot event during initialization failed with system error %4: \"%5\".	%1 (%2) %3An attempt to acquire an FPGA slot event during initialization failed with system error %4: \"%5\".
0xBB8	NOOP_FAILURE_TAG_ID	NOOP_FAILURE_TAG_ID
0xBB9	%1 (%2) %3因配置错误导致数据库“%4”无法正常操作(“%5”)。出现该错误的可能原因有: 数据库配置不正确、权限问题或存储相关问题。%n%n其他诊断信息: %6 %7	%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
0xBBA	%1 (%2) %3因读取验证或 I/O 错误导致数据库“%4”无法正常操作(“%5”)。请查看事件日志和其他日志数据，以确定您的系统是否遇到了存储相关的问题。%n%n其他诊断信息: %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
0xBBB	%1 (%2) %3数据库或日志文件缺少可用空间，导致数据库“%4”无法正常操作(“%5”)。请检查数据库和日志卷的可用空间以确定具体问题。%n%n其他诊断信息: %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
0xBBC	%1 (%2) %3因 I/O 错误导致数据库“%4”无法正常操作(“%5”)。请查看事件日志和其他日志数据，以确定您的系统是否遇到了存储问题。%n%n其他诊断信息: %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
0xBBD	%1 (%2) %3被动副本检测到数据库“%4”的已装载副本损坏(“%5”)。此错误可能因存储相关问题所致。%n%n其他诊断信息: %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
0xBBE	%1 (%2) %3在数据库“%4”中检测到损坏(“%5”)。出现此错误的可能原因有人为错误、系统或存储问题。%n%n其他诊断信息: %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
0xBBF	%1 (%2) %3因资源或操作错误导致数据库“%4”无法正常工作(“%5”)。请查看应用程序和系统事件日志，了解数据库的失败情况或其所需的系统组件。%n%n其他诊断信息: %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
0xBC0	%1 (%2) %3因严重错误导致数据库“%4”无法正常操作(“%5”)。请查看应用程序和系统事件日志，了解数据库的失败情况或其所需的系统组件。%n%n其他诊断信息: %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
0xBC1	%1 (%2) %3因问题导致数据库“%4”无法正常操作(“%5”)。通过重新装载数据库可能会更正此失败。%n%n其他诊断信息: %6 %7	%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
0xBC2	%1 (%2) %3在日志传送环境中，被动副本检测到有错误导致数据库“%4”无法正常操作(“%5”)。请查看应用程序和系统事件日志，了解数据库的失败情况或其所需的系统组件。	%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.
0xBC3	%1 (%2) %3性能问题正在影响数据库“%4”的正常操作(“%5”)。出现此错误的可能原因有: 配置不正确、存储问题或计算机上的性能问题。请检查与数据库关联的性能计数器和应用程序事件日志、数据库存储以及计算机，以确定具体问题。%n%n其他诊断信息: %6 %7	%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
0xBC4	%1 (%2) %3因异常大的正常负载导致数据库“%4”无法正常操作(“%5”)。应减少此数据库上的负载以还原正常操作。%n%n其他诊断信息: %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
0xBC5	%1 (%2) %3系统遇到了内存分配失败问题，导致数据库“%4”无法正常操作(“%5”)。出现此错误的可能原因有配置不正确或计算机上过多的内存消耗。%n%n其他诊断信息: %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
0xBC6	CATALOGRESEED_FAILURE_TAG_ID	CATALOGRESEED_FAILURE_TAG_ID
0xBC7	MAX_FAILURE_TAG_ID	MAX_FAILURE_TAG_ID

File Name:	ESENT.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-e..gine-isam.resources_31bf3856ad364e35_10.0.15063.0_zh-cn_dc73d1a2951c85ee\
File Size:	60 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	61440
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	Chinese (Simplified)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	Microsoft(R) Windows(R) 的可扩展存储引擎
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	esent.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	esent.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Directory:	%WINDIR%\WinSxS\x86_microsoft-windows-e..gine-isam.resources_31bf3856ad364e35_10.0.15063.0_zh-cn_8055361edcbf14b8\

ESENT.dll.mui is Multilingual User Interface resource file that contain Chinese (Simplified) language for file ESENT.dll (Microsoft(R) Windows(R) 的可扩展存储引擎).

File Description:	Microsoft(R) Windows(R) 的可扩展存储引擎
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	esent.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	esent.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x804, 1200