How to Resolve WSUS Failures Related to "services not working"?

Points of my Scenario:
1. I'm admin for a single-forest, single-domain, Windows Server 2003 domain.
2. I have WSUS running on a member server.
3. WSUS started to fail and several errors appear in the application event log every 6 hours:
   Error1 - The DSS Authentication Web Service is not working. (EventID:12052)
   Error2 - The SimpleAuth Web Service is not working.  (EventID: 12042)
   Error3 - The Client Web Service is not working.  (EventID: 12022)
   Error4 - The Server Synchronization Web Service is not working.  (EventID: 12032)
   Error5 - The API Remoting Web Service is not working.  (EventID: 12012)
   Error6 - The Reporting Web Service is not working.  (EventID: 12002)
These errors all appear together in the event log (on separate lines of course).
How can I resolve these errors in order to restore WSUS functionality?

waforbes100Senior IT SpecialistAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shreedhar EtteCommented:
0
Shreedhar EtteCommented:
The WSUS clientdiag.exe tool said everything was fine from the client end, but there were no updates to see. Do the following to fix the problem: Open IIS Manager, right click the Default Web Site, and look at the properties tab. The port should be 80, or whatever you use as the default http port. I was not using https. Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications. You should also check that the selfupdate subdirectory has this unchecked if you are using http and not https. Now go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup. Check that the PortNumber is set to 80 (Decimal) or 50 (Hex). Check that UsingSSL is set to 0 (if you are not using SSL). Restart the services and the problem should be solved.

Extracted from:
http://www.eventid.net/display.asp?eventid=13042&eventno=8857&source=Windows%20Server%20Update%20Services&phase=1
0
DonNetwork AdministratorCommented:
Use this to verify your wsus settings
 
http://technet.microsoft.com/en-us/library/cc708545(WS.10).aspx 
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

waforbes100Senior IT SpecialistAuthor Commented:
To shreedhar: all the settings mentioned in your link hold true for my configuration.
To dstewartjr: I've gone through the WSUS config checklist, without making any changes. However, my WSUS Administration console fails (see attached JPEG named "WSUS-Console-Error.JPG"). You may examine the attached error dump file (labelled "WSUS-Error-dump(04-06-2010).log"). It was acquired by clicking the button labelled "Copy to Clipboard" seen in the attached JPEG.
WSUS-Console-Error.JPG
WSUS-Error-dump-04-06-2010-.log
0
DonNetwork AdministratorCommented:
0
Shreedhar EtteCommented:
Hi,

I suspect that the WSUS database is corrupted.

You need to uninstall/reinstall  WSUS and manually.
http://www.computersplace.com/how-to-uninstall-wsus-30-after-you-have-removedfucked-up-the-database-manually/msi 

Also refer this: http://blogs.technet.com/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx

I hope this helps,
Shree
0
DonNetwork AdministratorCommented:
Btw Event ID's: 12052, 12042, 12022, 12032, 12012 and/or 12002. are security related not corruption. Run  IISRESET  to reset the IUSR account
 
http://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-guide-for-issues-where-wsus-clients-are-not-reporting-in.aspx 
0
DonNetwork AdministratorCommented:
This is also a cause:
 
HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup is set to the correct
port (the one your WSUS site is on)
 
0
DonNetwork AdministratorCommented:
Lastly if none of the above helps, reinstall .Net Framework 2.0 and asp.net 2.0
0
waforbes100Senior IT SpecialistAuthor Commented:
To dstewartjr: I have ensured that HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup is set to the correct port.
To both shreedhar & dstewartjr: before making any changes, I wish to point up a few NEW observations (which are also new events):
1. The following error appeared and repeated 9 (nine) times within the same minute:
Event Source:MSSQLSERVER/Event ID:17055 (4/6/2010@5:48:xy PM)/ -> "CREATE/ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 2048 MB per database".
2. I started the SQLSERVERAGENT using SQL Management Studio from a different domain member server, which produced the following information events in Event Viewer:
    A. Event Source:MSSQLSERVER/Event ID:17055 (4/6/2010@5:49:38 PM)/ -> "8128 :Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'."
    B. Event Source:SQLSERVERAGENT/Event ID:101 (4/6/2010@5:49:39 PM)/ -> "SQLServerAgent service successfully started."
However, even after this apparent success, the error I reported in previously attached file "WSUS-Error-dump-04-06-2010.log" prior error appears in Event Viewer:
"The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service."
I suspect that the error in point #1 is quite significant.
0
DonNetwork AdministratorCommented:
At this point I would then go ahead with the reinstall, I will repost the steps that shree copied from another one of my post's including a missed step.(that shows how to remove WSUS if it gives you a hassle)

http://blogs.technet.com/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx 

In addition to the blog above, the following will need to be run to remove WID

On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
waforbes100Senior IT SpecialistAuthor Commented:
I exclaim "Wonderful! - but with the following questions":
1. Does this mean that I must abandon the current database? - this is acceptable.
2. Will I have to re-download all Windows Updates software via the new WSUS? - this is acceptable.
3. If 1 & 2 are true, should I be concerned about WSUS clients - will they be able to pickup where they left off, or will they be confused?
0
DonNetwork AdministratorCommented:
1. yes
2. yes
3. dont be concerned.
0
waforbes100Senior IT SpecialistAuthor Commented:
Thanks guys for all your persistence through this tough issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps

From novice to tech pro — start learning today.