6,220 pts.
 WSUS stopped after server reboot
I rebooted my servers after the latest updates, and suddenly my WSUS services stopped. The error messages are many and varied, and I am not getting anywhere trying to research a solution. This happened last time I rebooted this server, and was fairly simple to resolve - but I didn't document whatever I did at the time (smacking self upside the head.....) and now I cannot find the solution again. I have tried any/all suggestions I fould online, restarted every service I can find a connection to....but nothing is providing the cure just yet. Any/all suggestions welcome....

Software/Hardware used:
ASKED: December 29, 2010  7:48 PM
UPDATED: January 5, 2011  3:39 PM

Answer Wiki:
try this if you would like.. 1- You can use a sofware called WINTERNAL to restore back to last working state. Godd program to use, it allows you access all restore point unlimited comparesd to your default O.S... 2- Or may want to scanned with both malware and trojan remover, even the trial works fine after u updated. This ixes any corrupt rergistry or damaged system files altered.
Last Wiki Answer Submitted:  December 30, 2010  12:25 am  by  Rakei   3,260 pts.
All Answer Wiki Contributors:  Rakei   3,260 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

If you mean on your server that hosts WSUS, there are only 2 basic components, the SQL database and the Update services service. Check that both services restarted after the reboot.

 5,130 pts.

 

Thank you for the suggestions. I know that this is actually something in the WSUS settings, but am very new to administrating it, and am cursing myself for not noting what corrected this after the last reboot. My server connection appears to need to be reset- although this IS the server that handles WSUS. IIS, MySQL, RPC and Update Services – all checked and restarted all hoping to resolve this…..no joy so far.

 6,220 pts.

 

It was a port conflict, causing the Default Web Site to be unable to start. I closed the other process which shouldn’t have been using that port, restarted the default Web Site, and all is good now. All is also documented now, as well ;-)

 6,220 pts.