| Previous | Next |
| COMADMIN_E_REGDB_NOTINITIALIZED | COMADMIN_E_REGDB_SYSTEMERR |
COMADMIN_E_REGDB_NOTOPEN
COM+ registration database lifecycle: exact meaning of COMADMIN_E_REGDB_NOTOPEN
The COM+ registration database is not open. Catalog work requires an open RegDB session but the database has not opened or has been closed.
Windows describes this condition as “The COM+ registry database is not open”.
Where the result occurs
RegDB is the transactional database behind part of the COM+ catalog; initialization, open state, lifecycle, and system errors require service/catalog evidence rather than direct file manipulation. In the specific case of this result, record service state, recent shutdown/recovery events, catalog session lifetime, and the first system error in the event log.
Evidence to collect before repair
- Evidence should include COM+ System Application and service events, captured before a repair changes state.
- Collect catalog/RegDB lifecycle state when diagnosing this result; without it the symbolic HRESULT is underdetermined.
- Record underlying system status and disk health.
- Preserve administration session timing and concurrent maintenance; it anchors the failure to the real administration object.
Diagnostic sequence
- stop unsupported direct catalog access.
- The next diagnostic action is to confirm COM+ services and initialization.
- To isolate this result, create a fresh administration session.
- repair underlying system conditions or COM+ feature state.
- use supported backup/restore or deployment recovery.
Difference from nearby COMADMIN results
COMADMIN_E_REGDB_NOTINITIALIZED concerns initialization; this code concerns open state.
Retry and recovery
Restore normal COM+ service/catalog operation and create a fresh administration session.
Practical administration scenario
A long-running administration process reuses a session after COM+ catalog service restart and finds RegDB closed.
RegDB-specific interpretation
Distinguish database existence and initialization from the open handle/session required by the current operation. A fresh COMAdmin connection after service recovery is more informative than repeating work through a stale collection object.
Official Microsoft references
Looking for a different code? Search another status or error code.