superatticman Posted May 28, 2012 Posted May 28, 2012 Hiya Have been tasked with fixing a WSUS problem that is affecting a Windows 2003 SP2 Server. Opening the console reveals this: A WSUS console that is totally non functional. Decided to remove and reinstall. However, there is no sign of WSUS in control panel at all. Have tried to reinstall the WSUS executible, it executes: But first of all gives the indication that parts of the installation are present: I select all/none of the components and start the uninstall process: It thinks about it for 10 seconds or so, but returns the following cryptic error: Anyone seen this before or have any idea as to whats going on here? Can always use another server, but really want to get to the bottom of what has happened here. Regards.
Michael Posted May 28, 2012 Posted May 28, 2012 I've seen that message plenty of times on Windows Server 2003. This guide (2nd post down) should solve it for you. I find WSUS is a lot more reliable on 2008 R2 compared to 2003 - even though it's the same software! 1
superatticman Posted May 29, 2012 Author Posted May 29, 2012 Michael Thankyou for this quick link. Have managed to get the console removed and re-installed. Once again, you've been a great help in pointing me the right way Regards
Michael Posted May 29, 2012 Posted May 29, 2012 On a related subject, here's how I setup WSUS on 2003/2008/2008 R2 which has proved popular with Edugeekers.
superatticman Posted May 30, 2012 Author Posted May 30, 2012 Thanks for the above link too. Have set it all up as described, lets see what happens over the next day or two as far as the updating process goes!
plexer Posted May 30, 2012 Posted May 30, 2012 You could have probably got away without re-installing it just restart all the services for wsus including the internal database one which can be quite hidden in your services list. Ben
User3204 Posted May 30, 2012 Posted May 30, 2012 I saw that error a few times, I found in the short term restart the services, and then the server sorted it. But in the end I doubled the RAM to 2gb, which sorted it out... Yeah, apparently I was running it on a single 1gb, for 3 years before it started to complain...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now