| Previous | Next |
| COMADMIN_E_REGDB_SYSTEMERR | COMADMIN_E_MIG_VERSIONNOTSUPPORTED |
COMADMIN_E_REGDB_ALREADYRUNNING
COMADMIN_E_REGDB_ALREADYRUNNING is the failure HRESULT 0x80110475 (signed decimal -2146368395, unsigned decimal 2148598901). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0475.
COM+ registration database lifecycle: exact meaning of COMADMIN_E_REGDB_ALREADYRUNNING
The COM+ registration database is already running when an operation expects it to be stopped or newly started. Catalog lifecycle management detects an incompatible existing RegDB state.
AllStat records this condition as “The COM+ registry database is already running”.
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 requested lifecycle action, service/process ownership, session count, and concurrent management activity.
Evidence to collect before repair
- Evidence for it 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.
- The result investigation needs underlying system status and disk health so the exact failing boundary remains reconstructable.
- preserve administration session timing and concurrent maintenance; it anchors the failure to the real administration object.
Diagnostic sequence
- At the boundary, stop unsupported direct catalog access.
- The next this result 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.
- At the boundary, use supported backup/restore or deployment recovery.
Difference from nearby COMADMIN results
COMADMIN_E_REGDB_NOTOPEN reports the opposite availability state for normal catalog work.
Retry and recovery
Avoid duplicate startup/control operations and coordinate catalog maintenance through supported service management.
Practical administration scenario
A recovery script starts RegDB explicitly even though COM+ initialization already brought it online.
RegDB-specific interpretation
The important transition is an attempted start or recovery action against an already active database. Verify which service or maintenance process owns the running state before stopping anything, since normal catalog clients require RegDB to remain online.
Official Microsoft references
- Microsoft: COMADMIN error codes
- Microsoft: the COM+ catalog
- Microsoft: automating COM+ administration
- Microsoft: COM+ administration catalog example
- Microsoft: COM+ administration collections
Looking for a different code? Search another status or error code.