Windows server 2003 crash 64bit --- missing a file from the system folder
I have a Windows server 2003 ( 64bit) crashed with the following error:
--------------------------
Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\S
You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
Select 'r' at the first screen to start repair.
This problem occurs when the system hive is larger than 32 MB.
--------------------------
More background: We had problems with installing Symantec Endpoint 11 on this server. Symantec tech support had to remove the previous antivirus (10.0) manually in the effort trying to reinstall the Endpoint. The Cleanwipe tool did not do the job in this case. After he cleaned up all Symantech related files (from c: drive and registry), we need to do a system restart before reinstalling Endpoint 11 again. Then system crashed with the above error.
Symantec support said it is an know Microsft issue with 64bit server according to this article he found ---
http://support.microsoft.com/kb/919807/en-us
There is a hot fix to fix this problem, but the article does not tell me how to bring up the OS first before I can apply the fix.
Any ideas how to bring the server back without losing the current configuration and installed programs?
Thanks.
M
--------------------------
Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\S
You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
Select 'r' at the first screen to start repair.
This problem occurs when the system hive is larger than 32 MB.
--------------------------
More background: We had problems with installing Symantec Endpoint 11 on this server. Symantec tech support had to remove the previous antivirus (10.0) manually in the effort trying to reinstall the Endpoint. The Cleanwipe tool did not do the job in this case. After he cleaned up all Symantech related files (from c: drive and registry), we need to do a system restart before reinstalling Endpoint 11 again. Then system crashed with the above error.
Symantec support said it is an know Microsft issue with 64bit server according to this article he found ---
http://support.microsoft.com/kb/919807/en-us
There is a hot fix to fix this problem, but the article does not tell me how to bring up the OS first before I can apply the fix.
Any ideas how to bring the server back without losing the current configuration and installed programs?
Thanks.
M
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
arnold:
Thank you very much for the tip and links.
I did an OS repair via the 64-bit CD and a floppy SAS RAID controller driver. It fixed the problem and put it the server back to the previous state.
Thank you very much for the tip and links.
I did an OS repair via the 64-bit CD and a floppy SAS RAID controller driver. It fixed the problem and put it the server back to the previous state.
ASKER
I did download and burn a UBCD cd a few weeks ago, but I'm not familiar with the tools yet. Could you let me which tool works best for this kind of OS issue? Could you provide me step-by-step instructions?
Thanks.