System Error Codes 6000-8199
The following table provides a list of system error codes (errors 6000 to 8199). These values are defined in the WinError.h header file. They are returned by the GetLastError function when many functions fail. To retrieve the description text for the error in your application, use the FormatMessage function with the FORMAT_MESSAGE_FROM_SYSTEM flag.【下表列出了系统错误代码(错误6000到8199)。这些值在WinError.h头文件中定义。当许多函数失败时,GetLastError函数返回它们。要检索应用程序中错误的描述文本,请使用FormatMessage函数和FORMAT_MESSAGE_FROM_SYSTEM 标志。】
If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to http://support.microsoft.com.【
如果正在安装或运行的应用程序遇到困难,请与客户支持联系以获取显示错误消息的软件。要获得对Microsoft产品的支持,请转到http://support.microsoft.com。】
ERROR_ENCRYPTION_FAILED | 6000 | The specified file could not be encrypted.【无法加密指定的文件。】 |
ERROR_DECRYPTION_FAILED | 6001 | The specified file could not be decrypted.【无法解密指定的文件。】 |
ERROR_FILE_ENCRYPTED | 6002 | The specified file is encrypted and the user does not have the ability to decrypt it.【指定的文件已加密,用户无法解密。】 |
ERROR_NO_RECOVERY_POLICY | 6003 | There is no valid encryption recovery policy configured for this system.【没有为此系统配置有效的加密恢复策略。】 |
ERROR_NO_EFS | 6004 | The required encryption driver is not loaded for this system.【没有为此系统加载所需的加密驱动程序。】 |
ERROR_WRONG_EFS | 6005 | The file was encrypted with a different encryption driver than is currently loaded.【使用与当前加载的加密驱动程序不同的加密驱动程序对文件进行了加密。】 |
ERROR_NO_USER_KEYS | 6006 | There are no EFS keys defined for the user.【没有为用户定义EFS密钥。】 |
ERROR_FILE_NOT_ENCRYPTED | 6007 | The specified file is not encrypted.【指定的文件未加密。】 |
ERROR_NOT_EXPORT_FORMAT | 6008 | The specified file is not in the defined EFS export format.【指定的文件不是定义的EFS导出格式。】 |
ERROR_FILE_READ_ONLY | 6009 | The specified file is read only.【指定的文件是只读的。】 |
ERROR_DIR_EFS_DISALLOWED | 6010 | The directory has been disabled for encryption.【该目录已被禁用加密。】 |
ERROR_EFS_SERVER_NOT_TRUSTED | 6011 | The server is not trusted for remote encryption operation.【不信任服务器进行远程加密操作。】 |
ERROR_BAD_RECOVERY_POLICY | 6012 | Recovery policy configured for this system contains invalid recovery certificate.【为此系统配置的恢复策略包含无效的恢复证书。】 |
ERROR_EFS_ALG_BLOB_TOO_BIG | 6013 | The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.【源文件上使用的加密算法需要比目标文件上使用的加密算法更大的密钥缓冲区。】 |
ERROR_VOLUME_NOT_SUPPORT_EFS | 6014 | The disk partition does not support file encryption.【磁盘分区不支持文件加密。】 |
ERROR_EFS_DISABLED | 6015 | This machine is disabled for file encryption.【此计算机已禁用文件加密。】 |
ERROR_EFS_VERSION_NOT_SUPPORT | 6016 | A newer system is required to decrypt this encrypted file.【需要更新的系统来解密此加密文件。】 |
ERROR_CS_ENCRYPTION_INVALID_SERVER_RESPONSE | 6017 | The remote server sent an invalid response for a file being opened with Client Side Encryption.【远程服务器为正在使用客户端加密打开的文件发送了无效响应。】 |
ERROR_CS_ENCRYPTION_UNSUPPORTED_SERVER | 6018 | Client Side Encryption is not supported by the remote server even though it claims to support it.【尽管远程服务器声称支持客户端加密,但它不支持客户端加密。】 |
ERROR_CS_ENCRYPTION_EXISTING_ENCRYPTED_FILE | 6019 | File is encrypted and should be opened in Client Side Encryption mode.【文件已加密,应以客户端加密模式打开。】 |
ERROR_CS_ENCRYPTION_NEW_ENCRYPTED_FILE | 6020 | A new encrypted file is being created and a E F S n e e d s t o b e p r o v i d e d . 【 正 在 创 建 新 的 加 密 文 件 , 需 要 提 供 EFS needs to be provided.【正在创建新的加密文件,需要提供 EFSneedstobeprovided.【正在创建新的加密文件,需要提供EFS。】 |
ERROR_CS_ENCRYPTION_FILE_NOT_CSE | 6021 | The SMB client requested a CSE FSCTL on a non-CSE file.【SMB客户端在非CSE文件上请求了CSE FSCTL。】 |
ERROR_NO_BROWSER_SERVERS_FOUND | 6118 | The list of servers for this workgroup is not currently available【此工作组的服务器列表当前不可用】 |
SCHED_E_SERVICE_NOT_LOCALSYSTEM | 6200 | The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.【任务计划程序服务必须配置为在系统帐户中运行才能正常运行。可以将单个任务配置为在其他帐户中运行。】 |
ERROR_LOG_SECTOR_INVALID | 6600 | Log service encountered an invalid log sector.【日志服务遇到无效的日志扇区。】 |
ERROR_LOG_SECTOR_PARITY_INVALID | 6601 | Log service encountered a log sector with invalid block parity.【日志服务遇到块奇偶校验无效的日志扇区。】 |
ERROR_LOG_SECTOR_REMAPPED | 6602 | Log service encountered a remapped log sector.【日志服务遇到重新映射的日志扇区。】 |
ERROR_LOG_BLOCK_INCOMPLETE | 6603 | Log service encountered a partial or incomplete log block.【日志服务遇到部分或不完整的日志块。】 |
ERROR_LOG_INVALID_RANGE | 6604 | Log service encountered an attempt access data outside the active log range.【日志服务遇到访问活动日志范围之外的数据的尝试。】 |
ERROR_LOG_BLOCKS_EXHAUSTED | 6605 | Log service user marshalling buffers are exhausted.【日志服务用户封送缓冲区已用完。】 |
ERROR_LOG_READ_CONTEXT_INVALID | 6606 | Log service encountered an attempt read from a marshalling area with an invalid read context.【日志服务遇到从具有无效读取上下文的编组区域读取的尝试。】 |
ERROR_LOG_RESTART_INVALID | 6607 | Log service encountered an invalid log restart area.【日志服务遇到无效的日志重新启动区域。】 |
ERROR_LOG_BLOCK_VERSION | 6608 | Log service encountered an invalid log block version.【日志服务遇到无效的日志块版本。】 |
ERROR_LOG_BLOCK_INVALID | 6609 | Log service encountered an invalid log block.【日志服务遇到无效的日志块。】 |
ERROR_LOG_READ_MODE_INVALID | 6610 | Log service encountered an attempt to read the log with an invalid read mode.【日志服务遇到尝试以无效的读取模式读取日志。】 |
ERROR_LOG_NO_RESTART | 6611 | Log service encountered a log stream with no restart area.【日志服务遇到没有重新启动区域的日志流。】 |
ERROR_LOG_METADATA_CORRUPT | 6612 | Log service encountered a corrupted metadata file.【日志服务遇到损坏的元数据文件。】 |
ERROR_LOG_METADATA_INVALID | 6613 | Log service encountered a metadata file that could not be created by the log file system.【日志服务遇到日志文件系统无法创建的元数据文件。】 |
ERROR_LOG_METADATA_INCONSISTENT | 6614 | Log service encountered a metadata file with inconsistent data.【日志服务遇到数据不一致的元数据文件。】 |
ERROR_LOG_RESERVATION_INVALID | 6615 | Log service encountered an attempt to erroneous allocate or dispose reservation space.【日志服务遇到错误分配或处置保留空间的尝试。】 |
ERROR_LOG_CANT_DELETE | 6616 | Log service cannot delete log file or file system container.【日志服务无法删除日志文件或文件系统容器。】 |
ERROR_LOG_CONTAINER_LIMIT_EXCEEDED | 6617 | Log service has reached the maximum allowable containers allocated to a log file.【日志服务已达到分配给日志文件的最大允许容器数。】 |
ERROR_LOG_START_OF_LOG | 6618 | Log service has attempted to read or write backward past the start of the log.【日志服务试图在日志开始后向后读取或写入。】 |
ERROR_LOG_POLICY_ALREADY_INSTALLED | 6619 | Log policy could not be installed because a policy of the same type is already present.【无法安装日志策略,因为已存在相同类型的策略。】 |
ERROR_LOG_POLICY_NOT_INSTALLED | 6620 | Log policy in question was not installed at the time of the request.【请求时未安装有问题的日志策略。】 |
ERROR_LOG_POLICY_INVALID | 6621 | The installed set of policies on the log is invalid.【日志上安装的策略集无效。】 |
ERROR_LOG_POLICY_CONFLICT | 6622 | A policy on the log in question prevented the operation from completing.【有关登录的策略阻止操作完成。】 |
ERROR_LOG_PINNED_ARCHIVE_TAIL | 6623 | Log space cannot be reclaimed because the log is pinned by the archive tail.【无法回收日志空间,因为日志已被存档尾部固定。】 |
ERROR_LOG_RECORD_NONEXISTENT | 6624 | Log record is not a record in the log file.【日志记录不是日志文件中的记录。】 |
ERROR_LOG_RECORDS_RESERVED_INVALID | 6625 | The number of reserved log records or the adjustment of the number of reserved log records is invalid.【保留日志记录数或保留日志记录数的调整无效。】 |
ERROR_LOG_SPACE_RESERVED_INVALID | 6626 | Reserved log space or the adjustment of the log space is invalid.【保留的日志空间或日志空间的调整无效。】 |
ERROR_LOG_TAIL_INVALID | 6627 | An new or existing archive tail or base of the active log is invalid.【活动日志的新的或现有的存档尾部或基部无效。】 |
ERROR_LOG_FULL | 6628 | Log space is exhausted.【日志空间已用尽。】 |
ERROR_COULD_NOT_RESIZE_LOG | 6629 | The log could not be set to the requested size.【无法将日志设置为请求的大小。】 |
ERROR_LOG_MULTIPLEXED | 6630 | Log is multiplexed, no direct writes to the physical log is allowed.【日志是多路复用的,不允许直接写入物理日志。】 |
ERROR_LOG_DEDICATED | 6631 | The operation failed because the log is a dedicated log.【操作失败,因为日志是专用日志。】 |
ERROR_LOG_ARCHIVE_NOT_IN_PROGRESS | 6632 | The operation requires an archive context.【该操作需要存档上下文。】 |
ERROR_LOG_ARCHIVE_IN_PROGRESS | 6633 | Log archival is in progress.【正在进行日志存档。】 |
ERROR_LOG_EPHEMERAL | 6634 | The operation requires a non-ephemeral log, but the log is ephemeral.【该操作需要非临时日志,但该日志是临时日志。】 |
ERROR_LOG_NOT_ENOUGH_CONTAINERS | 6635 | The log must have at least two containers before it can be read from or written to.【日志必须至少有两个容器才能读取或写入。】 |
ERROR_LOG_CLIENT_ALREADY_REGISTERED | 6636 | A log client has already registered on the stream.【日志客户端已在流上注册。】 |
ERROR_LOG_CLIENT_NOT_REGISTERED | 6637 | A log client has not been registered on the stream.【尚未在流上注册日志客户端。】 |
ERROR_LOG_FULL_HANDLER_IN_PROGRESS | 6638 | A request has already been made to handle the log full condition.【已发出处理日志已满情况的请求。】 |
ERROR_LOG_CONTAINER_READ_FAILED | 6639 | Log service encountered an error when attempting to read from a log container.【日志服务在尝试读取日志容器时遇到错误。】 |
ERROR_LOG_CONTAINER_WRITE_FAILED | 6640 | Log service encountered an error when attempting to write to a log container.【日志服务在尝试写入日志容器时遇到错误。】 |
ERROR_LOG_CONTAINER_OPEN_FAILED | 6641 | Log service encountered an error when attempting open a log container.【日志服务在尝试打开日志容器时遇到错误。】 |
ERROR_LOG_CONTAINER_STATE_INVALID | 6642 | Log service encountered an invalid container state when attempting a requested action.【日志服务在尝试请求的操作时遇到无效的容器状态。】 |
ERROR_LOG_STATE_INVALID | 6643 | Log service is not in the correct state to perform a requested action.【日志服务的状态不正确,无法执行请求的操作。】 |
ERROR_LOG_PINNED | 6644 | Log space cannot be reclaimed because the log is pinned.【无法回收日志空间,因为日志已固定。】 |
ERROR_LOG_METADATA_FLUSH_FAILED | 6645 | Log metadata flush failed.【日志元数据刷新失败。】 |
ERROR_LOG_INCONSISTENT_SECURITY | 6646 | Security on the log and its containers is inconsistent.【日志及其容器的安全性不一致。】 |
ERROR_LOG_APPENDED_FLUSH_FAILED | 6647 | Records were appended to the log or reservation changes were made, but the log could not be flushed.【记录已附加到日志或进行了保留更改,但无法刷新日志。】 |
ERROR_LOG_PINNED_RESERVATION | 6648 | The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.【由于保留占用了大部分日志空间,日志被固定。释放一些保留的记录以腾出空间。】 |
ERROR_INVALID_TRANSACTION | 6700 | The transaction handle associated with this operation is not valid.【与此操作关联的事务句柄无效。】 |
ERROR_TRANSACTION_NOT_ACTIVE | 6701 | The requested operation was made in the context of a transaction that is no longer active.【请求的操作是在不再活动的事务上下文中执行的。】 |
ERROR_TRANSACTION_REQUEST_NOT_VALID | 6702 | The requested operation is not valid on the Transaction object in its current state.【请求的操作对处于当前状态的事务对象无效。】 |
ERROR_TRANSACTION_NOT_REQUESTED | 6703 | The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.【调用者调用了一个响应API,但由于TM没有向调用者发出相应的请求,因此响应不是预期的。】 |
ERROR_TRANSACTION_ALREADY_ABORTED | 6704 | It is too late to perform the requested operation, since the Transaction has already been aborted.【执行请求的操作为时已晚,因为事务已中止。】 |
ERROR_TRANSACTION_ALREADY_COMMITTED | 6705 | It is too late to perform the requested operation, since the Transaction has already been committed.【执行请求的操作为时已晚,因为事务已提交。】 |
ERROR_TM_INITIALIZATION_FAILED | 6706 | The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.【无法成功初始化事务管理器。不支持事务处理操作。】 |
ERROR_RESOURCEMANAGER_READ_ONLY | 6707 | The specified ResourceManager made no changes or updates to the resource under this transaction.【指定的ResourceManager未对此事务下的资源进行任何更改或更新。】 |
ERROR_TRANSACTION_NOT_JOINED | 6708 | The resource manager has attempted to prepare a transaction that it has not successfully joined.【资源管理器试图准备尚未成功加入的事务。】 |
ERROR_TRANSACTION_SUPERIOR_EXISTS | 6709 | The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.【事务对象已具有上级登记,调用方尝试了一个本应创建新上级的操作。只允许一个上级入伍。】 |
ERROR_CRM_PROTOCOL_ALREADY_EXISTS | 6710 | The RM tried to register a protocol that already exists.【RM尝试注册已存在的协议。】 |
ERROR_TRANSACTION_PROPAGATION_FAILED | 6711 | The attempt to propagate the Transaction failed.【尝试传播事务失败。】 |
ERROR_CRM_PROTOCOL_NOT_FOUND | 6712 | The requested propagation protocol was not registered as a CRM.【请求的传播协议未注册为CRM。】 |
ERROR_TRANSACTION_INVALID_MARSHALL_BUFFER | 6713 | The buffer passed in to PushTransaction or PullTransaction is not in a valid format.【传递给PushTransaction或PullTransaction的缓冲区格式无效。】 |
ERROR_CURRENT_TRANSACTION_NOT_VALID | 6714 | The current transaction context associated with the thread is not a valid handle to a transaction object.【与线程关联的当前事务上下文不是事务对象的有效句柄。】 |
ERROR_TRANSACTION_NOT_FOUND | 6715 | The specified Transaction object could not be opened, because it was not found.【无法打开指定的事务对象,因为找不到它。】 |
ERROR_RESOURCEMANAGER_NOT_FOUND | 6716 | The specified ResourceManager object could not be opened, because it was not found.【无法打开指定的ResourceManager对象,因为找不到它。】 |
ERROR_ENLISTMENT_NOT_FOUND | 6717 | The specified Enlistment object could not be opened, because it was not found.【无法打开指定的登记对象,因为找不到该对象。】 |
ERROR_TRANSACTIONMANAGER_NOT_FOUND | 6718 | The specified TransactionManager object could not be opened, because it was not found. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.【无法打开指定的TransactionManager对象,因为找不到它。在打开事务或ResourceManager命名空间中的对象之前,必须通过调用RecoverTransactionManager将TransactionManager恢复到其日志文件的末尾,使其完全联机。此外,将记录写入其日志文件的错误会导致TransactionManager脱机。】 |
ERROR_TRANSACTIONMANAGER_NOT_ONLINE | 6719 | The object specified could not be created or opened, because its associated TransactionManager is not online.【无法创建或打开指定的对象,因为其关联的TransactionManager未联机。】 |
ERROR_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION | 6720 | The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.【指定的TransactionManager无法在Ob命名空间中创建其日志文件中包含的对象。因此,TransactionManager无法恢复。】 |
ERROR_TRANSACTION_NOT_ROOT | 6721 | The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior.【无法完成对此事务对象创建上级登记的调用,因为为此登记指定的事务对象是该事务的下级分支。只有事务的根才能登记为上级。】 |
ERROR_TRANSACTION_OBJECT_EXPIRED | 6722 | Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.【由于关联的事务管理器或资源管理器已关闭,因此句柄不再有效。】 |
ERROR_TRANSACTION_RESPONSE_NOT_ENLISTED | 6723 | The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.【无法对此上级登记执行指定的操作,因为登记不是使用NotificationMask中相应的完成响应创建的。】 |
ERROR_TRANSACTION_RECORD_TOO_LONG | 6724 | The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.【无法执行指定的操作,因为要记录的记录太长。出现这种情况的原因有两种:此事务中的登记太多,或者代表这些登记记录的组合RecoveryInformation太长。】 |
ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED | 6725 | Implicit transactions are not supported.【不支持隐式事务。】 |
ERROR_TRANSACTION_INTEGRITY_VIOLATED | 6726 | The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.【内核事务管理器不得不中止或忘记事务,因为它阻止了向前的进程。】 |
ERROR_TRANSACTIONMANAGER_IDENTITY_MISMATCH | 6727 | The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager’s log file.【提供的TransactionManager标识与TransactionManager日志文件中记录的标识不匹配。】 |
ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT | 6728 | This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.【此快照操作无法继续,因为事务性资源管理器无法在其当前状态下冻结。请再试一次。】 |
ERROR_TRANSACTION_MUST_WRITETHROUGH | 6729 | The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.【无法使用指定的登记掩码登记该事务,因为该事务已完成预准备阶段。为了确保正确性,ResourceManager必须切换到直写模式,并停止在该事务中缓存数据。仅登记后续事务阶段仍可能成功。】 |
ERROR_TRANSACTION_NO_SUPERIOR | 6730 | The transaction does not have a superior enlistment.【事务没有上级登记。】 |
ERROR_TRANSACTIONAL_CONFLICT | 6800 | The function attempted to use a name that is reserved for use by another transaction.【函数试图使用为另一个事务保留的名称。】 |
ERROR_RM_NOT_ACTIVE | 6801 | Transaction support within the specified file system resource manager is not started or was shutdown due to an error.【指定的文件系统资源管理器中的事务支持未启动或由于错误而关闭。】 |
ERROR_RM_METADATA_CORRUPT | 6802 | The metadata of the RM has been corrupted. The RM will not function.【RM的元数据已损坏。RM将不起作用。】 |
ERROR_DIRECTORY_NOT_RM | 6803 | The specified directory does not contain a resource manager.【指定的目录不包含资源管理器。】 |
ERROR_TRANSACTIONS_UNSUPPORTED_REMOTE | 6805 | The remote server or share does not support transacted file operations.【远程服务器或共享不支持事务文件操作。】 |
ERROR_LOG_RESIZE_INVALID_SIZE | 6806 | The requested log size is invalid.【请求的日志大小无效。】 |
ERROR_OBJECT_NO_LONGER_EXISTS | 6807 | The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.【事务保存点回滚已删除与句柄对应的对象(文件、流、链接)。】 |
ERROR_STREAM_MINIVERSION_NOT_FOUND | 6808 | The specified file miniversion was not found for this transacted file open.【找不到此事务处理文件打开的指定文件迷你版本。】 |
ERROR_STREAM_MINIVERSION_NOT_VALID | 6809 | The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.【找到了指定的文件迷你版本,但已无效。最可能的原因是事务保存点回滚。】 |
ERROR_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION | 6810 | A miniversion may only be opened in the context of the transaction that created it.【迷你版本只能在创建它的事务的上下文中打开。】 |
ERROR_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT | 6811 | It is not possible to open a miniversion with modify access.【无法使用“修改”访问权限打开迷你版本。】 |
ERROR_CANT_CREATE_MORE_STREAM_MINIVERSIONS | 6812 | It is not possible to create any more miniversions for this stream.【无法再为此流创建任何迷你版本。】 |
ERROR_REMOTE_FILE_VERSION_MISMATCH | 6814 | The remote server sent mismatching version number or Fid for a file opened with transactions.【远程服务器为用事务打开的文件发送了不匹配的版本号或Fid。】 |
ERROR_HANDLE_NO_LONGER_VALID | 6815 | The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint.【句柄已被事务作废。最可能的原因是当事务结束或回滚到保存点时,文件或打开的句柄上存在内存映射。】 |
ERROR_NO_TXF_METADATA | 6816 | There is no transaction metadata on the file.【文件上没有事务元数据。】 |
ERROR_LOG_CORRUPTION_DETECTED | 6817 | The log data is corrupt.【日志数据已损坏。】 |
ERROR_CANT_RECOVER_WITH_HANDLE_OPEN | 6818 | The file can’t be recovered because there is a handle still open on it.【无法恢复该文件,因为该文件上仍有一个句柄处于打开状态。】 |
ERROR_RM_DISCONNECTED | 6819 | The transaction outcome is unavailable because the resource manager responsible for it has disconnected.【事务结果不可用,因为负责它的资源管理器已断开连接。】 |
ERROR_ENLISTMENT_NOT_SUPERIOR | 6820 | The request was rejected because the enlistment in question is not a superior enlistment.【请求被拒绝,因为所讨论的入伍不是上级入伍。】 |
ERROR_RECOVERY_NOT_NEEDED | 6821 | The transactional resource manager is already consistent. Recovery is not needed.【事务性资源管理器已经一致。不需要恢复。】 |
ERROR_RM_ALREADY_STARTED | 6822 | The transactional resource manager has already been started.【事务性资源管理器已启动。】 |
ERROR_FILE_IDENTITY_NOT_PERSISTENT | 6823 | The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.【无法以事务方式打开文件,因为其标识取决于未解析事务的结果。】 |
ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY | 6824 | The operation cannot be performed because another transaction is depending on the fact that this property will not change.【无法执行该操作,因为另一个事务取决于此属性不会更改的事实。】 |
ERROR_CANT_CROSS_RM_BOUNDARY | 6825 | The operation would involve a single file with two transactional resource managers and is therefore not allowed.【该操作将涉及一个带有两个事务性资源管理器的文件,因此不允许。】 |
ERROR_TXF_DIR_NOT_EMPTY | 6826 | The T x f d i r e c t o r y m u s t b e e m p t y f o r t h i s o p e r a t i o n t o s u c c e e d . 【 Txf directory must be empty for this operation to succeed.【 Txfdirectorymustbeemptyforthisoperationtosucceed.【Txf目录必须为空,此操作才能成功。】 |
ERROR_INDOUBT_TRANSACTIONS_EXIST | 6827 | The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.【该操作将使事务性资源管理器处于不一致的状态,因此不允许。】 |
ERROR_TM_VOLATILE | 6828 | The operation could not be completed because the transaction manager does not have a log.【操作无法完成,因为事务管理器没有日志。】 |
ERROR_ROLLBACK_TIMER_EXPIRED | 6829 | A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.【无法计划回滚,因为以前计划的回滚已执行或已排队等待执行。】 |
ERROR_TXF_ATTRIBUTE_CORRUPT | 6830 | The transactional metadata attribute on the file or directory is corrupt and unreadable.【文件或目录的事务元数据属性已损坏且不可读。】 |
ERROR_EFS_NOT_ALLOWED_IN_TRANSACTION | 6831 | The encryption operation could not be completed because a transaction is active.【由于事务处于活动状态,加密操作无法完成。】 |
ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED | 6832 | This object is not allowed to be opened in a transaction.【不允许在事务中打开此对象。】 |
ERROR_LOG_GROWTH_FAILED | 6833 | An attempt to create space in the transactional resource manager’s log failed. The failure status has been recorded in the event log.【尝试在事务性资源管理器的日志中创建空间失败。故障状态已记录在事件日志中。】 |
ERROR_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE | 6834 | Memory mapping (creating a mapped section) a remote file under a transaction is not supported.【内存映射(创建映射节)不支持事务下的远程文件。】 |
ERROR_TXF_METADATA_ALREADY_PRESENT | 6835 | Transaction metadata is already present on this file and cannot be superseded.【此文件中已存在事务元数据,不能被替代。】 |
ERROR_TRANSACTION_SCOPE_CALLBACKS_NOT_SET | 6836 | A transaction scope could not be entered because the scope handler has not been initialized.【无法输入事务作用域,因为尚未初始化作用域处理程序。】 |
ERROR_TRANSACTION_REQUIRED_PROMOTION | 6837 | Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.【需要升级才能允许资源管理器登记,但事务被设置为不允许。】 |
ERROR_CANNOT_EXECUTE_FILE_IN_TRANSACTION | 6838 | This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.【此文件在未解析事务中打开以进行修改,并且只能由事务读取器打开以执行。】 |
ERROR_TRANSACTIONS_NOT_FROZEN | 6839 | The request to thaw frozen transactions was ignored because transactions had not previously been frozen.【解冻冻结的事务的请求被忽略,因为以前没有冻结过事务。】 |
ERROR_TRANSACTION_FREEZE_IN_PROGRESS | 6840 | Transactions cannot be frozen because a freeze is already in progress.【无法冻结事务,因为冻结已在进行中。】 |
ERROR_NOT_SNAPSHOT_VOLUME | 6841 | The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.【目标卷不是快照卷。此操作仅在作为快照装载的卷上有效。】 |
ERROR_NO_SAVEPOINT_WITH_OPEN_FILES | 6842 | The savepoint operation failed because files are open on the transaction. This is not permitted.【保存点操作失败,因为事务上的文件已打开。这是不允许的。】 |
ERROR_DATA_LOST_REPAIR | 6843 | Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.【Windows发现了一个文件中的损坏,该文件已被修复。可能发生了数据丢失。】 |
ERROR_SPARSE_NOT_ALLOWED_IN_TRANSACTION | 6844 | The sparse operation could not be completed because a transaction is active on the file.【稀疏操作无法完成,因为文件上的事务处于活动状态。】 |
ERROR_TM_IDENTITY_MISMATCH | 6845 | The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.【创建TransactionManager对象的调用失败,因为存储在日志文件中的Tm标识与作为参数传入的Tm标识不匹配。】 |
ERROR_FLOATED_SECTION | 6846 | I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.【尝试对由于事务结束而浮动的节对象进行I/O。没有有效数据。】 |
ERROR_CANNOT_ACCEPT_TRANSACTED_WORK | 6847 | The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.【事务性资源管理器当前无法接受事务性工作,因为存在暂时性情况,例如资源不足。】 |
ERROR_CANNOT_ABORT_TRANSACTIONS | 6848 | The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manager has been shut down.【事务性资源管理器有太多无法中止的未完成事务。事务性资源管理器已关闭。】 |
ERROR_BAD_CLUSTERS | 6849 | The operation could not be completed due to bad clusters on disk.【由于磁盘上的群集不正确,操作无法完成。】 |
ERROR_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION | 6850 | The compression operation could not be completed because a transaction is active on the file.【压缩操作无法完成,因为文件上的事务处于活动状态。】 |
ERROR_VOLUME_DIRTY | 6851 | The operation could not be completed because the volume is dirty. Please run chkdsk and try again.【由于卷脏,操作无法完成。请运行chkdsk并重试。】 |
ERROR_NO_LINK_TRACKING_IN_TRANSACTION | 6852 | The link tracking operation could not be completed because a transaction is active.【由于事务处于活动状态,链接跟踪操作无法完成。】 |
ERROR_OPERATION_NOT_SUPPORTED_IN_TRANSACTION | 6853 | This operation cannot be performed in a transaction.【不能在事务中执行此操作。】 |
ERROR_CTX_WINSTATION_NAME_INVALID | 7001 | The specified session name is invalid.【指定的会话名称无效。】 |
ERROR_CTX_INVALID_PD | 7002 | The specified protocol driver is invalid.【指定的协议驱动程序无效。】 |
ERROR_CTX_PD_NOT_FOUND | 7003 | The specified protocol driver was not found in the system path.【在系统路径中找不到指定的协议驱动程序。】 |
ERROR_CTX_WD_NOT_FOUND | 7004 | The specified terminal connection driver was not found in the system path.【在系统路径中找不到指定的终端连接驱动程序。】 |
ERROR_CTX_CANNOT_MAKE_EVENTLOG_ENTRY | 7005 | A registry key for event logging could not be created for this session.【无法为此会话创建事件日志记录的注册表项。】 |
ERROR_CTX_SERVICE_NAME_COLLISION | 7006 | A service with the same name already exists on the system.【系统上已存在同名服务。】 |
ERROR_CTX_CLOSE_PENDING | 7007 | A close operation is pending on the session.【会话上挂起关闭操作。】 |
ERROR_CTX_NO_OUTBUF | 7008 | There are no free output buffers available.【没有可用的输出缓冲区。】 |
ERROR_CTX_MODEM_INF_NOT_FOUND | 7009 | The MODEM.INF file was not found.【这个调制解调器.INF找不到文件。】 |
ERROR_CTX_INVALID_MODEMNAME | 7010 | The modem name was not found in MODEM.INF.【在中找不到调制解调器名称调制解调器.INF.】 |
ERROR_CTX_MODEM_RESPONSE_ERROR | 7011 | The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.【调制解调器不接受发送给它的命令。验证配置的调制解调器名称是否与连接的调制解调器匹配。】 |
ERROR_CTX_MODEM_RESPONSE_TIMEOUT | 7012 | The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.【调制解调器没有响应发送给它的命令。验证调制解调器是否已正确连接并通电。】 |
ERROR_CTX_MODEM_RESPONSE_NO_CARRIER | 7013 | Carrier detect has failed or carrier has been dropped due to disconnect.【载波检测失败或由于断开而导致载波丢失。】 |
ERROR_CTX_MODEM_RESPONSE_NO_DIALTONE | 7014 | Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.【在要求的时间内未检测到拨号音。验证电话线是否正确连接并正常工作。】 |
ERROR_CTX_MODEM_RESPONSE_BUSY | 7015 | Busy signal detected at remote site on callback.【回拨时在远程站点检测到忙信号。】 |
ERROR_CTX_MODEM_RESPONSE_VOICE | 7016 | Voice detected at remote site on callback.【回拨时在远程站点检测到语音。】 |
ERROR_CTX_TD_ERROR | 7017 | Transport driver error【传输驱动程序错误】 |
ERROR_CTX_WINSTATION_NOT_FOUND | 7022 | The specified session cannot be found.【找不到指定的会话。】 |
ERROR_CTX_WINSTATION_ALREADY_EXISTS | 7023 | The specified session name is already in use.【指定的会话名称已在使用中。】 |
ERROR_CTX_WINSTATION_BUSY | 7024 | The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation.【无法完成请求的操作,因为终端连接当前正忙于处理连接、断开连接、重置或删除操作。】 |
ERROR_CTX_BAD_VIDEO_MODE | 7025 | An attempt has been made to connect to a session whose video mode is not supported by the current client.【试图连接到当前客户端不支持其视频模式的会话。】 |
ERROR_CTX_GRAPHICS_INVALID | 7035 | The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.【应用程序试图启用DOS图形模式。不支持DOS图形模式。】 |
ERROR_CTX_LOGON_DISABLED | 7037 | Your interactive logon privilege has been disabled. Please contact your administrator.【您的交互式登录权限已被禁用。请与管理员联系。】 |
ERROR_CTX_NOT_CONSOLE | 7038 | The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access.【请求的操作只能在系统控制台上执行。这通常是驱动程序或系统DLL需要直接访问控制台的结果。】 |
ERROR_CTX_CLIENT_QUERY_TIMEOUT | 7040 | The client failed to respond to the server connect message.【客户端未能响应服务器连接消息。】 |
ERROR_CTX_CONSOLE_DISCONNECT | 7041 | Disconnecting the console session is not supported.【不支持断开控制台会话的连接。】 |
ERROR_CTX_CONSOLE_CONNECT | 7042 | Reconnecting a disconnected session to the console is not supported.【不支持将断开连接的会话重新连接到控制台。】 |
ERROR_CTX_SHADOW_DENIED | 7044 | The request to control another session remotely was denied.【远程控制另一个会话的请求被拒绝。】 |
ERROR_CTX_WINSTATION_ACCESS_DENIED | 7045 | The requested session access is denied.【请求的会话访问被拒绝。】 |
ERROR_CTX_INVALID_WD | 7049 | The specified terminal connection driver is invalid.【指定的终端连接驱动程序无效】 |
ERROR_CTX_SHADOW_INVALID | 7050 | The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on.【无法远程控制请求的会话。这可能是因为会话已断开连接或当前没有用户登录。】 |
ERROR_CTX_SHADOW_DISABLED | 7051 | The requested session is not configured to allow remote control.【请求的会话未配置为允许远程控制。】 |
ERROR_CTX_CLIENT_LICENSE_IN_USE | 7052 | Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.【您连接到此终端服务器的请求已被拒绝。您的终端服务器客户端许可证号当前正被其他用户使用。请致电系统管理员以获取唯一的许可证号码。】 |
ERROR_CTX_CLIENT_LICENSE_NOT_SET | 7053 | Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator.【您连接到此终端服务器的请求已被拒绝。尚未为该终端服务器客户端副本输入您的终端服务器客户端许可证号。请与系统管理员联系。】 |
ERROR_CTX_LICENSE_NOT_AVAILABLE | 7054 | The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.【到这台计算机的连接数是有限的,所有连接现在都在使用中。请稍后尝试连接或与系统管理员联系。】 |
ERROR_CTX_LICENSE_CLIENT_INVALID | 7055 | The client you are using is not licensed to use this system. Your logon request is denied.【您使用的客户端没有使用此系统的许可证。您的登录请求被拒绝。】 |
ERROR_CTX_LICENSE_EXPIRED | 7056 | The system license has expired. Your logon request is denied.【系统许可证已过期。您的登录请求被拒绝。】 |
ERROR_CTX_SHADOW_NOT_RUNNING | 7057 | Remote control could not be terminated because the specified session is not currently being remotely controlled.【无法终止远程控制,因为当前未远程控制指定的会话。】 |
ERROR_CTX_SHADOW_ENDED_BY_MODE_CHANGE | 7058 | The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported.【由于显示模式已更改,控制台的远程控制已终止。不支持在远程控制会话中更改显示模式。】 |
ERROR_ACTIVATION_COUNT_EXCEEDED | 7059 | Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.【激活已重置此安装的最大次数。您的激活计时器将不会被清除。】 |
ERROR_CTX_WINSTATIONS_DISABLED | 7060 | Remote logins are currently disabled.【远程登录当前已禁用。】 |
ERROR_CTX_ENCRYPTION_LEVEL_REQUIRED | 7061 | You do not have the proper encryption level to access this Session.【您没有访问此会话的正确加密级别。】 |
ERROR_CTX_SESSION_IN_USE | 7062 | The user %s\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.【用户%s\%s当前已登录到此计算机。只有当前用户或管理员才能登录到此计算机。】 |
ERROR_CTX_NO_FORCE_LOGOFF | 7063 | The user %s\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\%s and have them log off.【用户%s\%s已登录到此计算机的控制台。您现在没有登录权限。若要解决此问题,请与%s\%s联系并让他们注销。】 |
ERROR_CTX_ACCOUNT_RESTRICTION | 7064 | Unable to log you on because of an account restriction.【由于帐户限制,您无法登录。】 |
ERROR_RDP_PROTOCOL_ERROR | 7065 | The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.【RDP协议组件%2在协议流中检测到错误,已断开客户端的连接。】 |
ERROR_CTX_CDM_CONNECT | 7066 | The Client Drive Mapping Service Has Connected on Terminal Connection.【客户端驱动器映射服务已在终端连接上连接。】 |
ERROR_CTX_CDM_DISCONNECT | 7067 | The Client Drive Mapping Service Has Disconnected on Terminal Connection.【客户端驱动器映射服务已在终端连接上断开连接。】 |
ERROR_CTX_SECURITY_LAYER_ERROR | 7068 | The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.【终端服务器安全层在协议流中检测到错误,并已断开客户端的连接。】 |
ERROR_TS_INCOMPATIBLE_SESSIONS | 7069 | The target session is incompatible with the current session.【目标会话与当前会话不兼容。】 |
FRS_ERR_INVALID_API_SEQUENCE | 8001 | The file replication service API was called incorrectly.【文件复制服务API调用不正确。】 |
FRS_ERR_STARTING_SERVICE | 8002 | The file replication service cannot be started.【无法启动文件复制服务。】 |
FRS_ERR_STOPPING_SERVICE | 8003 | The file replication service cannot be stopped.【无法停止文件复制服务。】 |
FRS_ERR_INTERNAL_API | 8004 | The file replication service API terminated the request. The event log may have more information.【文件复制服务API终止了请求。事件日志可能包含更多信息。】 |
FRS_ERR_INTERNAL | 8005 | The file replication service terminated the request. The event log may have more information.【文件复制服务终止了请求。事件日志可能包含更多信息。】 |
FRS_ERR_SERVICE_COMM | 8006 | The file replication service cannot be contacted. The event log may have more information.【无法联系文件复制服务。事件日志可能包含更多信息。】 |
FRS_ERR_INSUFFICIENT_PRIV | 8007 | The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.【文件复制服务无法满足请求,因为用户没有足够的权限。事件日志可能包含更多信息。】 |
FRS_ERR_AUTHENTICATION | 8008 | The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.【文件复制服务无法满足请求,因为经过身份验证的RPC不可用。事件日志可能包含更多信息。】 |
FRS_ERR_PARENT_INSUFFICIENT_PRIV | 8009 | The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information.【文件复制服务无法满足该请求,因为用户在域控制器上没有足够的权限。事件日志可能包含更多信息。】 |
FRS_ERR_PARENT_AUTHENTICATION | 8010 | The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information.【文件复制服务无法满足该请求,因为已验证的RPC在域控制器上不可用。事件日志可能包含更多信息。】 |
FRS_ERR_CHILD_TO_PARENT_COMM | 8011 | The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.【文件复制服务无法与域控制器上的文件复制服务通信。事件日志可能包含更多信息。】 |
FRS_ERR_PARENT_TO_CHILD_COMM | 8012 | The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information.【域控制器上的文件复制服务无法与此计算机上的文件复制服务通信。事件日志可能包含更多信息。】 |
FRS_ERR_SYSVOL_POPULATE | 8013 | The file replication service cannot populate the system volume because of an internal error. The event log may have more information.【由于内部错误,文件复制服务无法填充系统卷。事件日志可能包含更多信息。】 |
FRS_ERR_SYSVOL_POPULATE_TIMEOUT | 8014 | The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.【由于内部超时,文件复制服务无法填充系统卷。事件日志可能包含更多信息。】 |
FRS_ERR_SYSVOL_IS_BUSY | 8015 | The file replication service cannot process the request. The system volume is busy with a previous request.【文件复制服务无法处理该请求。系统卷正忙于前一个请求。】 |
FRS_ERR_SYSVOL_DEMOTE | 8016 | The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.【由于内部错误,文件复制服务无法停止复制系统卷。事件日志可能包含更多信息。】 |
FRS_ERR_INVALID_SERVICE_PARAMETER | 8017 | The file replication service detected an invalid parameter.【文件复制服务检测到无效参数。】 |