COM Error Codes (XACT, SCHED, OLE)
The following table provides a list of error codes used by COM-based APIs.
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 https://support.microsoft.com.
| Constant/value | Description |
|---|---|
|
Another single phase resource manager has already been enlisted in this transaction. |
|
A retaining commit or abort is not supported |
|
The transaction failed to commit for an unknown reason. The transaction was aborted. |
|
Cannot call commit on this transaction object because the calling application did not initiate the transaction. |
|
Instead of committing, the resource heuristically aborted. |
|
Instead of aborting, the resource heuristically committed. |
|
Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions. |
|
Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions. |
|
The requested isolation level is not valid or supported. |
|
The transaction manager doesn't support an asynchronous operation for this method. |
|
Unable to enlist in the transaction. |
|
The requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero. |
|
There is no resource presently associated with this enlistment |
|
The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers. |
|
The transaction has already been implicitly or explicitly committed or aborted |
|
An invalid combination of flags was specified |
|
The resource manager id is not associated with this transaction or the transaction manager. |
|
This method was called in the wrong state |
|
The indicated unit of work does not match the unit of work expected by the resource manager. |
|
An enlistment in a transaction already exists. |
|
An import object for the transaction could not be found. |
|
The transaction cookie is invalid. |
|
The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed |
|
A time-out was specified, but time-outs are not supported. |
|
The requested operation is already in progress for the transaction. |
|
The transaction has already been aborted. |
|
The Transaction Manager returned a log full error. |
|
The Transaction Manager is not available. |
|
A connection with the transaction manager was lost. |
|
A request to establish a connection with the transaction manager was denied. |
|
Resource manager reenlistment to determine transaction status timed out. |
|
This transaction manager failed to establish a connection with another TIP transaction manager. |
|
This transaction manager encountered a protocol error with another TIP transaction manager. |
|
This transaction manager could not propagate a transaction from another TIP transaction manager. |
|
The Transaction Manager on the destination machine is not available. |
|
The Transaction Manager has disabled its support for TIP. |
|
The transaction manager has disabled its support for remote/network transactions. |
|
The partner transaction manager has disabled its support for remote/network transactions. |
|
The transaction manager has disabled its support for XA transactions. |
|
MSDTC was unable to read its configuration information. |
|
MSDTC was unable to load the dtc proxy dll. |
|
The local transaction has aborted. |
|
The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. |
|
The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. |
|
The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions. |
|
XACT_E_CLERKNOTFOUND |
|
XACT_E_CLERKEXISTS |
|
XACT_E_RECOVERYINPROGRESS |
|
XACT_E_TRANSACTIONCLOSED |
|
XACT_E_INVALIDLSN |
|
XACT_E_REPLAYREQUEST |
|
An asynchronous operation was specified. The operation has begun, but its outcome is not known yet. |
|
XACT_S_DEFECT |
|
The method call succeeded because the transaction was read-only. |
|
The transaction was successfully aborted. However, this is a coordinated transaction, and some number of enlisted resources were aborted outright because they could not support abort-retaining semantics |
|
No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes. |
|
The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call. |
|
The sink is for the moment and wishes the transaction to proceed, but if other changes are made following this return by other event sinks then this sink wants another chance to look |
|
The transaction was successfully aborted. However, the abort was non-retaining. |
|
An abort operation was already in progress. |
|
The resource manager has performed a single-phase commit of the transaction. |
|
The local transaction has not aborted. |
|
The resource manager has requested to be the coordinator (last resource manager) for the transaction. |
|
The root transaction wanted to commit, but transaction aborted |
|
You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. |
|
There is no MTS object context |
|
The component is configured to use synchronization and this method call would cause a deadlock to occur. |
|
The component is configured to use synchronization and a thread has timed out waiting to enter the context. |
|
You made a method call on a COM+ component that has a transaction that has already committed or aborted. |
|
The specified role was not configured for the application |
|
COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator |
|
An unexpected error occurred during COM+ Activation. |
|
COM+ Activation failed. Check the event log for more information |
|
COM+ Activation failed due to a catalog or configuration error. |
|
COM+ activation failed because the activation could not be completed in the specified amount of time. |
|
COM+ Activation failed because an initialization function failed. Check the event log for more information. |
|
The requested operation requires that JIT be in the current context and it is not |
|
The requested operation requires that the current context have a Transaction, and it does not |
|
The components threading model has changed after install into a COM+ Application. Please re-install component. |
|
IIS intrinsics not available. Start your work with IIS. |
|
An attempt to write a cookie failed. |
|
An attempt to use a database generated a database specific error. |
|
The COM+ component you created must use object pooling to work. |
|
The COM+ component you created must use object construction to work correctly. |
|
The COM+ component requires synchronization, and it is not configured for it. |
|
The TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the "root" component for the transaction. The creation failed. |
|
The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope. |
|
The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning. |
|
Use the registry database to provide the requested information |
|
Success, but static |
|
Macintosh clipboard format |
|
Successful drop took place |
|
Drag-drop operation canceled |
|
Use the default cursor |
|
Data has same FORMATETC |
|
View is already frozen |
|
FORMATETC not supported |
|
Same cache |
|
Some cache(s) not updated |
|
Invalid verb for OLE object |
|
Verb number is valid but verb cannot be done now |
|
Invalid window handle passed |
|
Message is too long; some of it had to be truncated before displaying |
|
Unable to convert OLESTREAM to IStorage |
|
Moniker reduced to itself |
|
Common prefix is this moniker |
|
Common prefix is input moniker |
|
Common prefix is both monikers |
|
Moniker is already registered in running object table |
|
The task is ready to run at its next scheduled time. |
|
The task is currently running. |
|
The task will not run at the scheduled times because it has been disabled. |
|
The task has not yet run. |
|
There are no more runs scheduled for this task. |
|
One or more of the properties that are needed to run this task on a schedule have not been set. |
|
The last run of the task was terminated by the user. |
|
Either the task has no triggers or the existing triggers are disabled or not set. |
|
Event triggers don't have set run times. |
|
Trigger not found. |
|
One or more of the properties that are needed to run this task have not been set. |
|
There is no running instance of the task. |
|
The Task Scheduler Service is not installed on this computer. |
|
The task object could not be opened. |
|
The object is either an invalid task object or is not a task object. |
|
No account information could be found in the Task Scheduler security database for the task indicated. |
|
Unable to establish existence of the account specified. |
|
Corruption was detected in the Task Scheduler security database; the database has been reset. |
|
Task Scheduler security services are not available. |
|
The task object version is either unsupported or invalid. |
|
The task has been configured with an unsupported combination of account settings and run time options. |
|
The Task Scheduler Service is not running. |
|
The task XML contains an unexpected node. |
|
The task XML contains an element or attribute from an unexpected namespace. |
|
The task XML contains a value which is incorrectly formatted or out of range. |
|
The task XML is missing a required element or attribute. |
|
The task XML is malformed. |
|
The task is registered, but not all specified triggers will start the task. |
|
The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal. |
|
The task XML contains too many nodes of the same type. |
|
The task cannot be started after the trigger's end boundary. |
|
An instance of this task is already running. |
|
The task will not run because the user is not logged on. |
|
The task image is corrupt or has been tampered with. |
|
The Task Scheduler service is not available. |
|
The Task Scheduler service is too busy to handle your request. Please try again later. |
|
The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. |
|
The Task Scheduler service has asked the task to run. |
|
The task is disabled. |
|
The task has properties that are not compatible with previous versions of Windows. |
|
The task settings do not allow the task to start on demand. |
|
The combination of properties that task is using is not compatible with the scheduling engine. |
|
Attempt to create a class object failed |
|
OLE service could not bind object |
|
RPC communication failed with OLE service |
|
Bad path to object |
|
Server execution failed |
|
OLE service could not communicate with the object server |
|
Moniker path could not be normalized |
|
Object server is stopping when OLE service contacts it |
|
An invalid root block pointer was specified |
|
An allocation chain contained an invalid link pointer |
|
The requested allocation size was too large |
|
Not all the requested interfaces were available |
|
The specified machine name was not found in the cache. |
|
The activation requires a display name to be present under the CLSID key. |
|
The activation requires that the RunAs value for the application is Activate As Activator. |
|
The class is not configured to support Elevated activation. |
|
Unknown interface. |
|
Member not found. |
|
Parameter not found. |
|
Type mismatch. |
|
Unknown name. |
|
No named arguments. |
|
Bad variable type. |
|
Exception occurred. |
|
Out of present range. |
|
Invalid index. |
|
Unknown language. |
|
Memory is locked. |
|
Invalid number of parameters. |
|
Parameter not optional. |
|
Invalid callee. |
|
Does not support a collection. |
|
Division by zero. |
|
Buffer too small |
|
Buffer too small. |
|
Field name not defined in the record. |
|
Old format or invalid type library. |
|
Old format or invalid type library. |
|
Error accessing the OLE registry. |
|
Library not registered. |
|
Bound to unknown type. |
|
Qualified name disallowed. |
|
Invalid forward reference, or reference to uncompiled type. |
|
Type mismatch. |
|
Element not found. |
|
Ambiguous name. |
|
Name already exists in the library. |
|
Unknown LCID. |
|
Function not defined in specified DLL. |
|
Wrong module kind for the operation. |
|
Size may not exceed 64K. |
|
Duplicate ID in inheritance hierarchy. |
|
Incorrect inheritance depth in standard OLE hmember. |
|
Type mismatch. |
|
Invalid number of arguments. |
|
I/O Error. |
|
Error creating unique tmp file. |
|
Error loading type library/DLL. |
|
Inconsistent property functions. |
|
Circular dependency between types/modules. |
Requirements
| Requirement | Value |
|---|---|
| Header |
|
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for