| Previous | Next |
| CO_E_NOTCONSTRUCTED | CO_E_ISOLEVELMISMATCH |
CO_E_NOSYNCHRONIZATION
CO_E_NOSYNCHRONIZATION is the failure HRESULT 0x8004E02E (signed decimal -2147164114, unsigned decimal 2147803182). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xE02E.
The class depends on COM+ serialized context access that its activation lacks
This HRESULT means the COM+ component requires synchronization and the effective configuration does not provide it. The component cannot safely rely on activity locking, serialized access, or related JIT and transaction dependencies.
AllStat describes the result as “The COM+ component requires synchronization, and it is not configured for it.” for it, this wording identifies the immediate COM+ condition, while surrounding context and earlier events determine why it was reached.
Contract boundary
COM+ synchronization is a declarative context service, not an ordinary critical section inside the DLL. A class can contain native locks and still fail this requirement.
Causes that fit this specific result
- The Synchronization attribute is Disabled, Not Supported, or otherwise weaker than the implementation requires.
- Deployment changes transaction or JIT settings without preserving synchronization dependencies.
- The class activates in a different COM+ application with default attributes.
- A package import omits component-level synchronization configuration.
Evidence to preserve before changing the system
- Record effective synchronization, JIT, and transaction attributes for the CLSID.
- Capture context and activity IDs at activation.
- Compare Component Services settings with the package manifest and design requirements.
- Verify whether direct activation bypassed the configured COM+ component.
Diagnostic sequence
- Determine whether the class owns mutable state that truly requires serialized context access.
- Configure Required or Requires New synchronization as designed.
- Review call graphs for blocking work before enabling serialization under production load.
- Test contention, callbacks, and transaction behavior after the setting changes.
Retry and recovery
Restore the required synchronization service or make the implementation independently thread-safe and remove the dependency. Retrying in the same unsynchronized context will not help.
What the result does not establish
The result does not report a current deadlock or timeout. It identifies missing configuration before synchronized behavior can be relied upon.
Difference from nearby HRESULT values
CONTEXT_E_WOULD_DEADLOCK and CONTEXT_E_SYNCH_TIMEOUT occur when synchronization exists but call admission fails. CONTEXT_E_NOJIT concerns JIT activation.
Practical scenario
A stateful legacy component is imported with Synchronization set to Not Supported. It refuses activation with this HRESULT; the deployment restores Required and a load test confirms that long calls do not create unacceptable contention.
Developer and telemetry guidance
Validate synchronization as part of package installation and include effective attributes in startup diagnostics. Do not “fix” the error by adding random internal locks without reviewing COM+ context semantics.
Official Microsoft references
- Microsoft: COM transaction and context error codes
- Microsoft: COM+ synchronization concepts
- Microsoft: configuring COM+ applications
- Microsoft: COM+ contexts
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.