Error message :
Error status: 0x0000001. please shutdown this system and reboot into directory services restore mode
The server bluescreens, reboots into safe mode and repeats the cycle
Solution
The solution that worked was found on technet forums
1. Restart the server and press F8 key, select Directory Services restore mode.
2. Log in with the local administrator username and password
3. Type cd \windows\system32
4. type NTDSUTIL
5. type activate instance NTDS
6. type files
7. If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
8. type cd\
9. type md backupad
10. type cd \windows\ntds
11. type copy ntds.dit c:\backupad
12. type cd \windows\system32
13. type esentutl /g c:\windows\ntds\ntds.dit
14. This will perform an integrity check, (the results indicate that the jet database is corrupt)
15. Type esentutl /p c:\windows\ntds\ntds.dit
16. Agree with the prompt
17. type cd \windows\ntds
18. type move *.log c:\backupad (or just delete the log files)
2. Log in with the local administrator username and password
3. Type cd \windows\system32
4. type NTDSUTIL
5. type activate instance NTDS
6. type files
7. If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
8. type cd\
9. type md backupad
10. type cd \windows\ntds
11. type copy ntds.dit c:\backupad
12. type cd \windows\system32
13. type esentutl /g c:\windows\ntds\ntds.dit
14. This will perform an integrity check, (the results indicate that the jet database is corrupt)
15. Type esentutl /p c:\windows\ntds\ntds.dit
16. Agree with the prompt
17. type cd \windows\ntds
18. type move *.log c:\backupad (or just delete the log files)
This should complete the repair. To verify that the repair has worked successfully:
1. type cd \windows\system32
2. type ntdsutil
3. type activate instance ntds
3. type files (you should no longer get an error when you do this)
4. type info (file info should now appear correctly)
2. type ntdsutil
3. type activate instance ntds
3. type files (you should no longer get an error when you do this)
4. type info (file info should now appear correctly)
One final step, now sure if it's required:
From the NTDSUTIL command prompt:
1. type Semantic Database Analysis
2. type Go
1. type Semantic Database Analysis
2. type Go
The addition is the error fix as described on Microsoft support article
3. ntdsutil "sem d a" "go f"
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.