| Previous | Next |
| ERROR_DS_CANT_START | ERROR_DS_NO_PKT_PRIVACY_ON_CONNECTION |
ERROR_DS_INIT_FAILURE
Directory Services did not complete its startup sequence
AD DS startup must open the directory database and logs, initialize directory and security subsystems, load schema and configuration state, and establish the local DSA runtime. This code reports that the sequence did not finish; the diagnostic cause is normally a preceding event with a more specific storage, database, schema, configuration, or security status.
Preserve the first NTDS startup errors and the embedded status values. If normal boot repeatedly reaches the same failure, use Directory Services Restore Mode for offline diagnosis rather than making speculative changes while AD DS is partially initialized. Microsoft supports DSRM specifically because AD DS is stopped there and local authentication is handled separately, allowing database or restore operations against an offline directory.
What to inspect
- Find the earliest NTDS startup error, not only the final service-termination event.
- Check database paths, transaction logs, storage, schema, and configuration statuses reported before this code.
- Use DSRM when the directory must remain offline for repair or restore.
References
- Microsoft: AD and AD LDS diagnostic event logging
- Microsoft: restore an Active Directory server
- Microsoft: dcdiag
Looking for a different code? Search another status or error code.