Lost_Beny
asked on
Cannot repair Active Directory
Hi everyone,
I have encountered the famous Active Directory 0xc00002e1 error in Windows 2003 Server after resizing a partition on the hard disk. Now, plenty information is given on how to recover everything. You have to run the server in Directory Services Repair Mode, then use ntdsutil.
The problem is, when I run the Directory Services Repair Mode and log in as Administrator, the system logs in normally and then after showing the "Applying Computer Settings", it simply logs off by itself before I can do anything. I've spent the whole day reading and trying things, but I'm strongly limited by the fact that I don't have a single way of logging to the server (no safe mode, no command prompt, no directory services repair mode, etc.)
If anyone has a clue, it would really be appreciated!
Thanks,
Beny
I have encountered the famous Active Directory 0xc00002e1 error in Windows 2003 Server after resizing a partition on the hard disk. Now, plenty information is given on how to recover everything. You have to run the server in Directory Services Repair Mode, then use ntdsutil.
The problem is, when I run the Directory Services Repair Mode and log in as Administrator, the system logs in normally and then after showing the "Applying Computer Settings", it simply logs off by itself before I can do anything. I've spent the whole day reading and trying things, but I'm strongly limited by the fact that I don't have a single way of logging to the server (no safe mode, no command prompt, no directory services repair mode, etc.)
If anyone has a clue, it would really be appreciated!
Thanks,
Beny
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, it doesn't work!
There's no network support in DSRM.
I'm really getting despaired...
There's no network support in DSRM.
I'm really getting despaired...
At first have a full backup of the system (clonning the disk might be a good idea) because if you follow the steps bellow you'll modify many things and it might be not possible to go back. So, in that case, a backup would be handy ;)
Then try replacing the Administrators profile with the contents of the default profile. You can do that by using the recovery console (boot from Windows CD and at some point you get an option of repairing, choose recovery console). The administrator's profile can be found at C:\Documents and Settings\Administrator. Try replacing everything in that folder with the contents of the C:\Documents and Settings\Default User folder.
If it is a profile problem this should fix it.
Then try replacing the Administrators profile with the contents of the default profile. You can do that by using the recovery console (boot from Windows CD and at some point you get an option of repairing, choose recovery console). The administrator's profile can be found at C:\Documents and Settings\Administrator. Try replacing everything in that folder with the contents of the C:\Documents and Settings\Default User folder.
If it is a profile problem this should fix it.
ASKER
This is a good idea.
I have also found a way to load the registry hive from another partition. Changing to cmd.exe like you said did not work, there was simply no more screen saver.
If your solution doesn't work, someone suggested it might be the following key:
HKEY_LOCAL_MACHINE\SOFTWAR
which causes the problem. There are a few others which could make my logon do this in the Winlogon keys.
I'll tell you the results later.
Thanks a lot...
I have also found a way to load the registry hive from another partition. Changing to cmd.exe like you said did not work, there was simply no more screen saver.
If your solution doesn't work, someone suggested it might be the following key:
HKEY_LOCAL_MACHINE\SOFTWAR
which causes the problem. There are a few others which could make my logon do this in the Winlogon keys.
I'll tell you the results later.
Thanks a lot...
ASKER
I've found the answer! After a week, believe me I'm quite happy.
After browsing through the registry, I finally found that the problem was in the HKEY_LOCAL_MACHINE\System\
Since I had resized the partition from another OS, the keys hadn't been updated to reflect the change and the new partitions weren't associated to their corresponding letters. Therefore the system couldn't find anything and the first thing to bug was lsass.exe.
I copied the binary values of the other OS and it worked right after.
Thanks a lot for your help, I wouldn't have thought of checking the registry if you hadn't suggested it!
Beny
After browsing through the registry, I finally found that the problem was in the HKEY_LOCAL_MACHINE\System\
Since I had resized the partition from another OS, the keys hadn't been updated to reflect the change and the new partitions weren't associated to their corresponding letters. Therefore the system couldn't find anything and the first thing to bug was lsass.exe.
I copied the binary values of the other OS and it worked right after.
Thanks a lot for your help, I wouldn't have thought of checking the registry if you hadn't suggested it!
Beny
I have the same problem. I ghosted a server 2003 disk to a larger hard drive so now the partitions are larger. When I start up I get the same error as above. I dont have an alternate OS to copy the binary information from. Does anyone have a suggestion on how I could get this to work?
Dear Beny:
I encountered the same problem.
Would you please tell me how to load the registry hive from another partition?
Thank you so much!!
I encountered the same problem.
Would you please tell me how to load the registry hive from another partition?
Thank you so much!!
Hey Lost Beny
Could you share How Did you accesses Win2k3 from Other operating system ??? or How Did you do Following,
"I copied the binary values of the other OS and it worked right after."
Thanks,
AD
Could you share How Did you accesses Win2k3 from Other operating system ??? or How Did you do Following,
"I copied the binary values of the other OS and it worked right after."
Thanks,
AD
ASKER