none
Errors after KB 2720211/ KB2734608

    Question

  • I recently installed the famed WSUS update, KB 2720211, and the update installed properly with no errors.  However, the update caused my WSUS server to fail synchronization.  After a little reading, I then applied update/hotfix KB 2734608.  After rebooting from this update, my synchronization would succeed, but I’m seeing the following errors in the event logs:

    Event ID

    Description

    12002

    The Reporting Web Service is not working.

    12012

    The API Remoting Web Service is not working.

    12022

    The Client Web Service is not working.

    12032

    The Server Synchronization Web Service is not working.

    12042

    The SimpleAuth Web Service is not working.

    12052

    The DSS Authentication Web Service is not working

    13042

    Self-update is not working.

    I will note that the client machines did update to 7.6.7600.256 and they are able to contact and send status reports to the WSUS server.  I’m just a little worried over the above errors.  Any help would be appreciated to cleanup my event logs.

    Cheers

    -Little Richard. 

    Friday, July 26, 2013 7:35 PM

Answers

  • These errors are a manifestation of the WSUS Health Monitoring Service (HMS) unable to communicate with the WSUS server at the URL it thinks the WSUS server has been installed to.

    Typically this occurs when the WSUS server is manually migrated from one v-root to another, e.g. manually creating the "WSUS Administration" v-root, setting it to port 8530, and moving the apps/v-dirs from the "Default Web Site", or vice versa.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, July 26, 2013 10:48 PM
    Moderator

All replies

  • These errors are a manifestation of the WSUS Health Monitoring Service (HMS) unable to communicate with the WSUS server at the URL it thinks the WSUS server has been installed to.

    Typically this occurs when the WSUS server is manually migrated from one v-root to another, e.g. manually creating the "WSUS Administration" v-root, setting it to port 8530, and moving the apps/v-dirs from the "Default Web Site", or vice versa.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, July 26, 2013 10:48 PM
    Moderator
  • Lawrence

    What would I need to look at to fix this issue?

    Thursday, August 01, 2013 1:51 AM
  • What would I need to look at to fix this issue?

    First step is to determine where the WSUS server is actually installed, then compare that with where the WSUS server is supposed to be installed, and was originally installed.

    If the HMS is failing attempting to monitor the server, there's a good chance the clients aren't communicating either (such is the primary purpose of the HMS). However, if the clients are working, it's also possible that the HMS has always been throwing errors -- if the WSUS server were installed and then 'reconfigured' for the other port.

    Once you know the answers to those questions, it's possible that fixing it is as simple as using the wsusutil usecustomwebsite utility.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, August 02, 2013 2:08 PM
    Moderator