Sunny-Brussels
asked on
Copied repaired SAM to system32\config - SBS not loading it
I had a lsass.exe error yesterday on boot (SBS 2003), not virus related. After a few hours I realised i had a registry backup from a few weeks ago in the repair directory. I booted with Ultimate Boot CD, renamed the original SAM in the system32\config folder to SAM.bak and copied over the old SAM from the repair directory.
Worked great and before I knew it i was in Safe mode, but my Applying Computer Settings issue was still there in normal mode so I thought I'd try a Last Known Config, bad idea! I was back to the lsass.exe error once again.
No worries I thought, I'll just repeat the procedure as mentioned above and it will be fine. Hmmm, not the case, I still get the lsass.exe error.
I went back into the system32\config folder and saw that the date of my SAM file is still time stamped as being two weeks old. Strange I thought, I deleted it and booted with no SAM file. Once again i went back into system32\config and saw that a new SAM had been created with the correct date and time. I copied over this with my old SAM but still the same issue, it seems that SBS is grabbing the SAM info from somewhere else. Is this possible?
After I originally copied the SAM over at the beginning of this story (and it worked) I went back into system32\config and saw that the file date and time had changed to the present, so I know there must be an issue now with why the system is not picking up the SAM I copied over.
Any ideas anyone?
Thanks.
Worked great and before I knew it i was in Safe mode, but my Applying Computer Settings issue was still there in normal mode so I thought I'd try a Last Known Config, bad idea! I was back to the lsass.exe error once again.
No worries I thought, I'll just repeat the procedure as mentioned above and it will be fine. Hmmm, not the case, I still get the lsass.exe error.
I went back into the system32\config folder and saw that the date of my SAM file is still time stamped as being two weeks old. Strange I thought, I deleted it and booted with no SAM file. Once again i went back into system32\config and saw that a new SAM had been created with the correct date and time. I copied over this with my old SAM but still the same issue, it seems that SBS is grabbing the SAM info from somewhere else. Is this possible?
After I originally copied the SAM over at the beginning of this story (and it worked) I went back into system32\config and saw that the file date and time had changed to the present, so I know there must be an issue now with why the system is not picking up the SAM I copied over.
Any ideas anyone?
Thanks.
ASKER
Hi Jeff,
Thanks for the reply.
To be honest I read the hell out of anything I could find relating to the subject, MS K base, these forums and Googled until I couldn't see anymore. I saw the post you refer to but our issues were similar but not the same.
Problem with me was that I was completely locked out of the system, no Safe mode, no Directory Services Restore Mode, no Repair (OEM) so I was pretty much screwed. The only way was to try replacing the SAM, which originally did work.
I'd just love to find out why it didn't a second try!
In the end I've re-installed, enough time was wasted.
Thanks for the reply.
To be honest I read the hell out of anything I could find relating to the subject, MS K base, these forums and Googled until I couldn't see anymore. I saw the post you refer to but our issues were similar but not the same.
Problem with me was that I was completely locked out of the system, no Safe mode, no Directory Services Restore Mode, no Repair (OEM) so I was pretty much screwed. The only way was to try replacing the SAM, which originally did work.
I'd just love to find out why it didn't a second try!
In the end I've re-installed, enough time was wasted.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Forced accept.
Computer101
EE Admin
Computer101
EE Admin
This is the proper way to fix that problem: http://support.microsoft.com/kb/258062
It really would always be a good idea to check the MS Knowledge Base first. :-) It would save a lot of time... but it seems I'm saying that to a lot of folks these days because someone had this EXCACT same issue a couple weeks ago and also didn't look up how to fix it before trudging ahead.
Hopefully though you can gain some insight from reviewing his jouney to fixing the problem: http:Q_22074580.html
Jeff
TechSoEasy