W2k Server problem
My office recently suffered a powercut and this has caused all manner of problems with one of my development servers. The server is not attached to a UPS and there is no "real" backup routine in place for the server (not connected to a tape unit).
The problem is when I boot the server up I get the black screen that says Windows 2000 loading, then the bar across the screen and then get taken to the lovely blue screen, not the Blue screen of death but the nice shade of blus you get prior to the login box appearing...that's it...nothing else comes up and the server sits for ages and does nothing else.
I booted the machine up in Safe Mode and managed to get into the Event Viewer were it mentions about Net Logon and a whole stack of services not sunning properly (in fact not running at all).
Does anyone know what could have caused this and how to rectify it?
I've tried using the recovery console (FIXBOOT for one) but this didn't appear to fix anything. I've also tried Repairing W2K and this merely overwrote the files with the initial SP (I think). I was using SP4.
Any advice as always appreciated.
The problem is when I boot the server up I get the black screen that says Windows 2000 loading, then the bar across the screen and then get taken to the lovely blue screen, not the Blue screen of death but the nice shade of blus you get prior to the login box appearing...that's it...nothing else comes up and the server sits for ages and does nothing else.
I booted the machine up in Safe Mode and managed to get into the Event Viewer were it mentions about Net Logon and a whole stack of services not sunning properly (in fact not running at all).
Does anyone know what could have caused this and how to rectify it?
I've tried using the recovery console (FIXBOOT for one) but this didn't appear to fix anything. I've also tried Repairing W2K and this merely overwrote the files with the initial SP (I think). I was using SP4.
Any advice as always appreciated.
Can you ping this server from another one?
If so, try
SCLIST \\Servername -s
(part of the Resource Kit: http://www.petri.co.il/download_free_reskit_tools.htm)
to show stopped services...
You can also do this from recovery console with
LISTSVC
If Net Logon isn't starting - try starting it remotely or enabling it from RC.
http://support.microsoft.com/?kbid=229716
If so, try
SCLIST \\Servername -s
(part of the Resource Kit: http://www.petri.co.il/download_free_reskit_tools.htm)
to show stopped services...
You can also do this from recovery console with
LISTSVC
If Net Logon isn't starting - try starting it remotely or enabling it from RC.
http://support.microsoft.com/?kbid=229716
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I take it that since it is a 'development' server that it is not a DC... Sounds to me like you will have to perform a Repair Installation on this machine...
Power outages can certainly cause havoc on a network that is not protected by a UPS.. You really do not have to purchase the top of the line model... even a $40 APC UPS will save you from this type of disaster.. It will not give you any time to save data, but it will power down automatically and prevent this from happening..
SirB.. you are sure all over the site today... Good morning to you Sir..!!
FE
Power outages can certainly cause havoc on a network that is not protected by a UPS.. You really do not have to purchase the top of the line model... even a $40 APC UPS will save you from this type of disaster.. It will not give you any time to save data, but it will power down automatically and prevent this from happening..
SirB.. you are sure all over the site today... Good morning to you Sir..!!
FE
BTW:
How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;292175
Repairing, Recovering, and Restoring an Installation of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;268106
Differences Between Manual and Fast Repair in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;238359
How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;292175
Repairing, Recovering, and Restoring an Installation of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;268106
Differences Between Manual and Fast Repair in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;238359
Good morning FE. Now that you are here - u101440 has nothing to worry about! :D
Que tenga buen dia!
Que tenga buen dia!
*grin* Just wishin it were Friday.. Then I would not have anything to worry about.. (as long as my networks are still running, right..??)
If it were Friday - I'd be home and not here building 5 new W2k3 servers (yipee)
Actually, that sounds like fun..!! Wish I were closer, I would come on over and lend a hand..!!
Pretty sweet servers too - DL380G3s...
ooooo dual 3.2 Ghz xeons... I am jealous now...
ASKER
sirbounty
Unfortunately I've had to plump for the third option you gave me (registry recovery). I've done this before with Windows XP but never W2K. I've done the first part (copying the repair SYSTEM folder) but do I need to complete anything else (Ther are a further 3 parts).
Thanx
Unfortunately I've had to plump for the third option you gave me (registry recovery). I've done this before with Windows XP but never W2K. I've done the first part (copying the repair SYSTEM folder) but do I need to complete anything else (Ther are a further 3 parts).
Thanx
hmm.. XP is a little different from W2K.. here are the directions directly from the MS Doc:
http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/fndc/FNDC_REC.doc
I suggest you go ahead and dnload this for future reference...
FE
Replacing the Registry Using the Recovery Console
If you are having problems with the registry, you can use the copy command to replace individual registry files by copying them from either the %sSystemRoot%\Repair folder or the %SystemRoot%\Repair\RegBac
Important
If you copied the files from %SystemRoot%\Repair\RegBac
If you copied the files from %SystemRoot%\Repair, your registry settings reflect those that were in effect when you installed Windows 2000.
http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/fndc/FNDC_REC.doc
I suggest you go ahead and dnload this for future reference...
FE
Replacing the Registry Using the Recovery Console
If you are having problems with the registry, you can use the copy command to replace individual registry files by copying them from either the %sSystemRoot%\Repair folder or the %SystemRoot%\Repair\RegBac
Important
If you copied the files from %SystemRoot%\Repair\RegBac
If you copied the files from %SystemRoot%\Repair, your registry settings reflect those that were in effect when you installed Windows 2000.
Bottom line here... you may have to reinstall some of the applications.. :(
ASKER
FE
Thanx for this but I've already used the Registry files from Repair (and this has resulted in me moving back to early installation as you mentioned!)
I've run into one or two other problems which I don't know if they can be answered here or if I should raise another question? They are linked so I hope you all don't mind.
Since re-installing the SYSTEM Registry files I cannot seem to pull any web pages from the machine (it's a web development server). I run the page from another machine and I'm asked for a username/password.
I've downloaded and run netdiag.exe from MS on ther server and it says that all is well except TRUST relationships. It says that it cannot get a list of trusted domains for my domain from Netlogon. This seems serious and I'd need to sort it but how?
I've also updated to SP4.
Thanx for this but I've already used the Registry files from Repair (and this has resulted in me moving back to early installation as you mentioned!)
I've run into one or two other problems which I don't know if they can be answered here or if I should raise another question? They are linked so I hope you all don't mind.
Since re-installing the SYSTEM Registry files I cannot seem to pull any web pages from the machine (it's a web development server). I run the page from another machine and I'm asked for a username/password.
I've downloaded and run netdiag.exe from MS on ther server and it says that all is well except TRUST relationships. It says that it cannot get a list of trusted domains for my domain from Netlogon. This seems serious and I'd need to sort it but how?
I've also updated to SP4.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
FE & sirbounty
Finally got it working now. I simply removed it from the DOMAIN and added it to the WORKGROUP and then brought it back in and all appears well.
One last thing though, my Office XP installation no longer works. I had to uninstall it and when I try to reinstall it I get the message:
The system administrator has set policies to prevent this installation.
I'm and admin and I've even tried the local admin account but neither work. I hear that there are many bugs in MSI Installer but do you have any suggestions?
Finally got it working now. I simply removed it from the DOMAIN and added it to the WORKGROUP and then brought it back in and all appears well.
One last thing though, my Office XP installation no longer works. I had to uninstall it and when I try to reinstall it I get the message:
The system administrator has set policies to prevent this installation.
I'm and admin and I've even tried the local admin account but neither work. I hear that there are many bugs in MSI Installer but do you have any suggestions?
Ew...
Um - try this...
Start->Run->MMC
File/Add-Remove Snap in
Add
Resultant Set of Policy
Follow the wizard to generate a policy log of all enabled settings
That might give you an idea if you've inadvertently set a restrictive policy against the admin accounts...
Glad you got it working though (wonder if we could have resolved the Office problem without an reinstall though... :D)
Um - try this...
Start->Run->MMC
File/Add-Remove Snap in
Add
Resultant Set of Policy
Follow the wizard to generate a policy log of all enabled settings
That might give you an idea if you've inadvertently set a restrictive policy against the admin accounts...
Glad you got it working though (wonder if we could have resolved the Office problem without an reinstall though... :D)
ASKER
sirbounty
Thanx for the speedy reply. Tried this but I don't have a Resultant Set of Policy when I choose Add.
Thanx for the speedy reply. Tried this but I don't have a Resultant Set of Policy when I choose Add.
Ew...
There's another way to get that list, but I don't recall how at the moment... (argh - darn memory).
Try start->Run->secpol.msc
and/or
gpedit.msc
Navigate through computer config/windows settings/security settings/local policies/
user & security folders - check for restrictions there...
Not sure why you don't have RSoP though... strange...
There's another way to get that list, but I don't recall how at the moment... (argh - darn memory).
Try start->Run->secpol.msc
and/or
gpedit.msc
Navigate through computer config/windows settings/security settings/local policies/
user & security folders - check for restrictions there...
Not sure why you don't have RSoP though... strange...
Yes.. very strange indeed... but, does W2K have RSOP..??? will have to go to another system to ck this out..
FE
FE
And I believe the reason Office is not working is that the Repair folder that you dumped into your registry is the backup of the stock install of W2K, before you installed Office.. You will have to reinstall, right, SB..??
FE
FE
>>Repair folder that you dumped into your registry <<
I thought only a domain removal/readd was performed?
I thought only a domain removal/readd was performed?
<Thanx for this but I've already used the Registry files from Repair (and this has resulted in me moving back to early installation as you mentioned!)>
Looks like the Repair files were used to replace the registry.. right...??
FE
Looks like the Repair files were used to replace the registry.. right...??
FE
ASKER
sirbounty
Yes I had to perform a Registry repair which you suggested some time ago.
Yes I had to perform a Registry repair which you suggested some time ago.
Yea.. then try reinstalling the Office Product... Let us know..
Actually - if you've got the time - I'd say restore that original SOFTWARE file from the backup.
Odds are that SYSTEM was where the problem was...
Odds are that SYSTEM was where the problem was...
ASKER
Guys
Closing off this question now (forgot about it for a while there). After offloading the material I was working on to the production server I've just rebuilt this machine.
Thanx again for all your assistance in getting me back from the brink and allowing me to complete the job I had to do.
Closing off this question now (forgot about it for a while there). After offloading the material I was working on to the production server I've just rebuilt this machine.
Thanx again for all your assistance in getting me back from the brink and allowing me to complete the job I had to do.
And thank you..
FE
FE
Boot into recovery console and try
CHKDSK /R
~sirbounty