| Previous | Next |
| hrFileNotFound | hrLogCorrupted |
hrAfterInitialization
Interpretation in ESE terms
hrAfterInitialization means restore processing was requested after the ESE instance had already initialized.
This is the legacy Directory Service backup/restore HRESULT form of JET_errAfterInitialization (0xC800073A).
The key comparison is: hrAlreadyInitialized is general duplicate initialization; this result specifically blocks restore-after-start ordering. The first useful observation is to trace the ordering of restore preparation, parameter configuration, and JetInit. This evidence shows whether startup, normal operation, shutdown, or restore ordering is the actual boundary.
The ESE objects in play
| Diagnostic layer | ESE instance state and call ordering |
|---|---|
| Typical API surface | JetCreateInstance, JetSetSystemParameter, JetInit, JetTerm, and restore entry points |
| Code-specific condition | restore processing was requested after the ESE instance had already initialized |
| First corrective direction | perform restore before instance initialization and keep normal startup from racing the restore controller |
Restore workflows have stricter ordering than ordinary open/attach calls. Initialization parameters are generally established before JetInit.
Comparison with adjacent failures
hrTermInProgress | the instance teardown boundary: new work reached ESE after termination had begun |
|---|---|
hrAlreadyInitialized | initialization-only work was attempted after the instance had already entered the running state |
hrNotInitialized | an ESE call requiring a running instance was made before successful initialization |
What to capture before retrying
- Code-specific observation: trace the ordering of restore preparation, parameter configuration, and JetInit.
- the successful or failed JetInit/JetTerm sequence and the component that owns it.
- all still-live sessions and child handles at the transition.
- the first request accepted after shutdown or before initialization completed.
Actions that can hide or worsen the problem
- Do not reuse instance-derived handles after the lifecycle transition.
- Do not start a second initializer to work around an ordering defect.
Operational response
- Freeze the failing request context and record
0xC800073A, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: trace the ordering of restore preparation, parameter configuration, and JetInit.
- Apply the targeted fix: perform restore before instance initialization and keep normal startup from racing the restore controller.
- Before retrying the operation, reconcile instance state, admission control, and child-handle cleanup.
Technical references
Looking for a different code? Search another status or error code.