Microsoft error codes
Search by code or error message to find official explanations and troubleshooting or diagnostic links.
Search runs in your browser. The same number can have different meanings in different products.
Microsoft Code
3,837 results- 66310x000019E7 · 0x19E7ERROR_LOG_DEDICATED
The operation failed because the log is a dedicated log.
MicrosoftWindows Win32 - 66320x000019E8 · 0x19E8ERROR_LOG_ARCHIVE_NOT_IN_PROGRESS
The operation requires an archive context.
MicrosoftWindows Win32 - 66330x000019E9 · 0x19E9ERROR_LOG_ARCHIVE_IN_PROGRESS
Log archival is in progress.
MicrosoftWindows Win32 - 66340x000019EA · 0x19EAERROR_LOG_EPHEMERAL
The operation requires a non-ephemeral log, but the log is ephemeral.
MicrosoftWindows Win32 - 66350x000019EB · 0x19EBERROR_LOG_NOT_ENOUGH_CONTAINERS
The log must have at least two containers before it can be read from or written to.
MicrosoftWindows Win32 - 66360x000019EC · 0x19ECERROR_LOG_CLIENT_ALREADY_REGISTERED
A log client has already registered on the stream.
MicrosoftWindows Win32 - 66370x000019ED · 0x19EDERROR_LOG_CLIENT_NOT_REGISTERED
A log client has not been registered on the stream.
MicrosoftWindows Win32 - 66380x000019EE · 0x19EEERROR_LOG_FULL_HANDLER_IN_PROGRESS
A request has already been made to handle the log full condition.
MicrosoftWindows Win32 - 66390x000019EF · 0x19EFERROR_LOG_CONTAINER_READ_FAILED
Log service encountered an error when attempting to read from a log container.
MicrosoftWindows Win32 - 66400x000019F0 · 0x19F0ERROR_LOG_CONTAINER_WRITE_FAILED
Log service encountered an error when attempting to write to a log container.
MicrosoftWindows Win32 - 66410x000019F1 · 0x19F1ERROR_LOG_CONTAINER_OPEN_FAILED
Log service encountered an error when attempting open a log container.
MicrosoftWindows Win32 - 66420x000019F2 · 0x19F2ERROR_LOG_CONTAINER_STATE_INVALID
Log service encountered an invalid container state when attempting a requested action.
MicrosoftWindows Win32 - 66430x000019F3 · 0x19F3ERROR_LOG_STATE_INVALID
Log service is not in the correct state to perform a requested action.
MicrosoftWindows Win32 - 66440x000019F4 · 0x19F4ERROR_LOG_PINNED
Log space cannot be reclaimed because the log is pinned.
MicrosoftWindows Win32 - 66450x000019F5 · 0x19F5ERROR_LOG_METADATA_FLUSH_FAILED
Log metadata flush failed.
MicrosoftWindows Win32 - 66460x000019F6 · 0x19F6ERROR_LOG_INCONSISTENT_SECURITY
Security on the log and its containers is inconsistent.
MicrosoftWindows Win32 - 66470x000019F7 · 0x19F7ERROR_LOG_APPENDED_FLUSH_FAILED
Records were appended to the log or reservation changes were made, but the log could not be flushed.
MicrosoftWindows Win32 - 66480x000019F8 · 0x19F8ERROR_LOG_PINNED_RESERVATION
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
MicrosoftWindows Win32 - 67000x00001A2C · 0x1A2CERROR_INVALID_TRANSACTION
The transaction handle associated with this operation is not valid.
MicrosoftWindows Win32 - 67010x00001A2D · 0x1A2DERROR_TRANSACTION_NOT_ACTIVE
The requested operation was made in the context of a transaction that is no longer active.
MicrosoftWindows Win32 - 67020x00001A2E · 0x1A2EERROR_TRANSACTION_REQUEST_NOT_VALID
The requested operation is not valid on the Transaction object in its current state.
MicrosoftWindows Win32 - 67030x00001A2F · 0x1A2FERROR_TRANSACTION_NOT_REQUESTED
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.
MicrosoftWindows Win32 - 67040x00001A30 · 0x1A30ERROR_TRANSACTION_ALREADY_ABORTED
It is too late to perform the requested operation, since the Transaction has already been aborted.
MicrosoftWindows Win32 - 67050x00001A31 · 0x1A31ERROR_TRANSACTION_ALREADY_COMMITTED
It is too late to perform the requested operation, since the Transaction has already been committed.
MicrosoftWindows Win32 - 67060x00001A32 · 0x1A32ERROR_TM_INITIALIZATION_FAILED
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.
MicrosoftWindows Win32 - 67070x00001A33 · 0x1A33ERROR_RESOURCEMANAGER_READ_ONLY
The specified ResourceManager made no changes or updates to the resource under this transaction.
MicrosoftWindows Win32 - 67080x00001A34 · 0x1A34ERROR_TRANSACTION_NOT_JOINED
The resource manager has attempted to prepare a transaction that it has not successfully joined.
MicrosoftWindows Win32 - 67090x00001A35 · 0x1A35ERROR_TRANSACTION_SUPERIOR_EXISTS
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.
MicrosoftWindows Win32 - 67100x00001A36 · 0x1A36ERROR_CRM_PROTOCOL_ALREADY_EXISTS
The RM tried to register a protocol that already exists.
MicrosoftWindows Win32 - 67110x00001A37 · 0x1A37ERROR_TRANSACTION_PROPAGATION_FAILED
The attempt to propagate the Transaction failed.
MicrosoftWindows Win32 - 67120x00001A38 · 0x1A38ERROR_CRM_PROTOCOL_NOT_FOUND
The requested propagation protocol was not registered as a CRM.
MicrosoftWindows Win32 - 67130x00001A39 · 0x1A39ERROR_TRANSACTION_INVALID_MARSHALL_BUFFER
The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
MicrosoftWindows Win32 - 67140x00001A3A · 0x1A3AERROR_CURRENT_TRANSACTION_NOT_VALID
The current transaction context associated with the thread is not a valid handle to a transaction object.
MicrosoftWindows Win32 - 67150x00001A3B · 0x1A3BERROR_TRANSACTION_NOT_FOUND
The specified Transaction object could not be opened, because it was not found.
MicrosoftWindows Win32 - 67160x00001A3C · 0x1A3CERROR_RESOURCEMANAGER_NOT_FOUND
The specified ResourceManager object could not be opened, because it was not found.
MicrosoftWindows Win32 - 67170x00001A3D · 0x1A3DERROR_ENLISTMENT_NOT_FOUND
The specified Enlistment object could not be opened, because it was not found.
MicrosoftWindows Win32 - 67180x00001A3E · 0x1A3EERROR_TRANSACTIONMANAGER_NOT_FOUND
The specified TransactionManager object could not be opened, because it was not found.
MicrosoftWindows Win32 - 67190x00001A3F · 0x1A3FERROR_TRANSACTIONMANAGER_NOT_ONLINE
The object specified could not be created or opened, because its associated TransactionManager is not online. 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.
MicrosoftWindows Win32 - 67200x00001A40 · 0x1A40ERROR_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION
The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
MicrosoftWindows Win32 - 67210x00001A41 · 0x1A41ERROR_TRANSACTION_NOT_ROOT
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.
MicrosoftWindows Win32