System error codes will appear in software programs and in various areas within the Windows operating system after certain errors occur.
Important: A system error code is not the same as a Device Manager
error code or a browser error code, even though the error numbers may sometimes be the same.
Below is a list of system error codes from Code 6700 to Code 6799, along with a description of what the error code means.
Looking for system error codes outside of this range? See my
Complete List of System Error Codes for error code details from Code 1 to Code 15299.
Error Code 6720
System error code 6720 means "The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore the TransactionManager was unable to recover." This error code may also display as "ERROR_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION" or as the value 0x1A40.Error Code 6721
System error code 6721 means "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." This error code may also display as "ERROR_TRANSACTION_NOT_ROOT" or as the value 0x1A41.Error Code 6722
System error code 6722 means "Because the associated transaction manager or resource manager has been closed the handle is no longer valid." This error code may also display as "ERROR_TRANSACTION_OBJECT_EXPIRED" or as the value 0x1A42.Error Code 6723
System error code 6723 means "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." This error code may also display as "ERROR_TRANSACTION_RESPONSE_NOT_ENLISTED" or as the value 0x1A43.Error Code 6724
System error code 6724 means "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." This error code may also display as "ERROR_TRANSACTION_RECORD_TOO_LONG" or as the value 0x1A44.Error Code 6725
System error code 6725 means "Implicit transactions are not supported." This error code may also display as "ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED" or as the value 0x1A45.Error Code 6726
System error code 6726 means "The kernel transaction manager had to abort or forget the transaction because it blocked forward progress." This error code may also display as "ERROR_TRANSACTION_INTEGRITY_VIOLATED" or as the value 0x1A46.Error Code 6727
System error code 6727 means "The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file." This error code may also display as "ERROR_TRANSACTIONMANAGER_IDENTITY_MISMATCH" or as the value 0x1A47.Error Code 6728
System error code 6728 means "This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again." This error code may also display as "ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT" or as the value 0x1A48.Error Code 6729
System error code 6729 means "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." This error code may also display as "ERROR_TRANSACTION_MUST_WRITETHROUGH" or as the value 0x1A49.Error Code 6730
System error code 6730 means "The transaction does not have a superior enlistment." This error code may also display as "ERROR_TRANSACTION_NO_SUPERIOR" or as the value 0x1A4A.
