Some client computers have not contacted the server in the last %1 days. %2 have been detected so far.

Details
Product: .NET Framework
Event ID: 13031
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthClientsSilentYellow
Message: Some client computers have not contacted the server in the last %1 days. %2 have been detected so far.
   
Explanation
Clients should check in with the server on a regular basis for updates.
   
User Action
Clients Not Reporting

Client computers are not reporting status to the WSUS server.

Possible resolutions include:

  • Review the application event log and resolve any issues related to the IIS, SQL, and WSUS server.
  • Check connectivity from the client computer to the WSUS server and debug any issue found.
  1. Open a command window.
  2. Verify the client computer has a valid IP address: type ipconfig /all
  3. Verify the client computer can reach the WSUS server: type ping &lt:server name or IP address>
  4. Verify the client computer can reach the WSUS HTTP server: type http://<servername>/selfupdate/iuident.cab. This will return with the option to download the cab file.
  5. Verify that the Automatic Update (AU) client is running: type net start wuauserv
  6. Verify the AU client is configured properly: type Reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
  7. If the reg query returns an error, the AU Group Policy has not been sent to this client computer or the client computer has not been configured for a non-domain environment. This has to be corrected before the next step. See http://go.microsoft.com/fwlink/?LinkID=41777.
  8. Verify WUServer and WUStatusServer are pointing to the WSUS server and port number (for example, http://<wsusservername or IP address>/<port number>)
  • Reset the Automatic Updates client by stopping the Automatic Updates client service and forcing a reset.
    1. Open a command window.
    2. Type Reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    3. Verify WUServer and WUStatusServer are pointing to the WSUS server and port number (for example, http://<wsusservername or IP address>/<port number>)
    4. Type gpupdate /force (if client machine is configured via domain policy).
    5. Type wuauclt.exe /resetauthorization /detectnow
    6. Wait 10 minutes for a detection cycle to finish before verification.
    7. Open the file <windir>\SoftwareDistribution\ReportingEvents.log in a text editor.
    8. Check the latest entry in the log file for “Success Software Synchronization Agent has finished detecting items.”
  • Verify

    Verify client computer and server status.

    • Check the server.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\Tools
      3. Type wsusutil checkhealth
      4. Type eventvwr
      5. Review the Application log for the most recent events from
        source Windows Server Update Services and event id 10010.
    • Go to the client computer and do the following:
      1. Open the <windir>\SoftwareDistribution\ReportingEvents.log file in a text editor.
      2. Check the latest entry in the log file for “Success Software Synchronization. The agent has finished detecting items.”

    Related:

    The last catalog synchronization attempt was unsuccessful.

    Details
    Product: .NET Framework
    Event ID: 10022
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthCoreCatalogSyncRed
    Message: The last catalog synchronization attempt was unsuccessful.
       
    Explanation
    WSUS catalog synchronization depends on connectivity to the upstream server or Microsoft Update.
       
    User Action
    Failed Catalog Synchronization

    The last catalog synchronization with the upstream WSUS server failed.

    Possible resolutions include:

    • Intermittent network connectivity loss to the upstream server. Review event logs for possible sources of the service disruption.
    • Check the update server and proxy settings in the WSUS administration console.
      1. Start WSUS 3.0: Click Start , click Administrative Tools, and then click Microsoft Windows Server Update Services v3.0.
      2. Click Options.
      3. Click Update Source and Proxy Server.
      4. Review update source settings and make changes as needed.
      5. Review proxy server settings and make changes as needed.
      6. Click Synchronization Results.
      7. In the Action pane, click Synchronize Now.

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and event id 10020.

    Related:

    Many client computers have not contacted the server in the last %1 days. %2 have been detected so far.

    Details
    Product: .NET Framework
    Event ID: 13032
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthClientsSilentRed
    Message: Many client computers have not contacted the server in the last %1 days. %2 have been detected so far.
       
    Explanation
    Clients should check in with the server on a regular basis for updates.
       
    User Action
    Clients Not Reporting

    Client computers are not reporting status to the WSUS server.

    Possible resolutions include:

    • Review the application event log and resolve any issues related to the IIS, SQL, and WSUS server.
    • Check connectivity from the client computer to the WSUS server and debug any issue found.
    1. Open a command window.
    2. Verify the client computer has a valid IP address: type ipconfig /all
    3. Verify the client computer can reach the WSUS server: type ping &lt:server name or IP address>
    4. Verify the client computer can reach the WSUS HTTP server: type http://<servername>/selfupdate/iuident.cab. This will return with the option to download the cab file.
    5. Verify that the Automatic Update (AU) client is running: type net start wuauserv
    6. Verify the AU client is configured properly: type Reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    7. If the reg query returns an error, the AU Group Policy has not been sent to this client computer or the client computer has not been configured for a non-domain environment. This has to be corrected before the next step. See http://go.microsoft.com/fwlink/?LinkID=41777.
    8. Verify WUServer and WUStatusServer are pointing to the WSUS server and port number (for example, http://<wsusservername or IP address>/<port number>)
  • Reset the Automatic Updates client by stopping the Automatic Updates client service and forcing a reset.
    1. Open a command window.
    2. Type Reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    3. Verify WUServer and WUStatusServer are pointing to the WSUS server and port number (for example, http://<wsusservername or IP address>/<port number>)
    4. Type gpupdate /force (if client machine is configured via domain policy).
    5. Type wuauclt.exe /resetauthorization /detectnow
    6. Wait 10 minutes for a detection cycle to finish before verification.
    7. Open the file <windir>\SoftwareDistribution\ReportingEvents.log in a text editor.
    8. Check the latest entry in the log file for “Success Software Synchronization Agent has finished detecting items.”
  • Verify

    Verify client computer and server status.

    • Check the server.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\Tools
      3. Type wsusutil checkhealth
      4. Type eventvwr
      5. Review the Application log for the most recent events from
        source Windows Server Update Services and event id 10010.
    • Go to the client computer and do the following:
      1. Open the <windir>\SoftwareDistribution\ReportingEvents.log file in a text editor.
      2. Check the latest entry in the log file for “Success Software Synchronization. The agent has finished detecting items.”

    Related:

    The Windows Server Update Server Service failed to start.

    Details
    Product: .NET Framework
    Event ID: 507
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: WsusServiceFailed
    Message: The Windows Server Update Server Service failed to start.
       
    Explanation
    The WSUS service must be running.
       
    User Action
    WSUS Service

    The WSUS service “Update Services” is stopped.

    Possible resolutions include:

    • The Update Services service has been manually stopped. Start the service.
    1. Open a command window.
    2. Type sc start wsusservice
  • The Update Services service is set to manual and is stopped.
    1. Open a command window.
    2. Type sc config wsusservice start= auto
    3. Type sc start wsusservice
  • The Update Services service failed to start. Review the NT event log for issues that occurred before this event (for example, the SQL database or IIS) and resolve them. Then start the service.
    1. Open a command window.
    2. Type sc start wsusservice

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and event id 501.

    Related:

    A user was authenticated, but IIS cannot retrieve details from Microsoft Active Directory. Check your Active Directory server for errors.

    Details
    Product: .NET Framework
    Event ID: 17
    Source: Microsoft MapPoint Location Server
    Version: 1.0.0.0
    Message: A user was authenticated, but IIS cannot retrieve details from Microsoft Active Directory. Check your Active Directory server for errors.
       
    Explanation
    MapPoint Location Server uses Basic authentication to authenticate users accessing MapPoint Location Server Web Service. Basic authentication requires user credentials to be validated against a valid Microsoft Windows account in Active Directory.
       
    User Action
    Make sure the domain controller is running. If the domain controller is running, check the Windows event log for errors related to Active Directory.
       
    Description
    ActiveDirectoryNoUserDetails

    Related:

    The credentials specified for connection to MapPoint Web Service are not valid. Ensure that the user name and password are correct and that the account is active.

    Details
    Product: .NET Framework
    Event ID: 15
    Source: Microsoft MapPoint Location Server
    Version: 1.0.0.0
    Message: The credentials specified for connection to MapPoint Web Service are not valid. Ensure that the user name and password are correct and that the account is active.
       
    Explanation
    To use MapPoint Location Server, you must have an active MapPoint Web Service account. Credentials are issued when you sign up to use MapPoint Web Service.
       
    User Action
    In the MapPoint Location Server management console, verify that the MapPoint Web Service account ID and password are correct. In the tree view, expand the Global Settings node, and then verify the information in the details pane. To change a value, double-click the property you want to modify, type the correct value, and then click OK. For information about how to become a MapPoint Web Service customer, visit the MapPoint Web Service home page (http://www.microsoft.com/mappoint/webservice/default.mspx).
       
    Description
    BadMapPointCredentials

    Related: