Troubleshooting ConfigMgr 2012 software update synchronization issues

What does this guide do?

Helps you diagnose and resolve issues with software update synchronization for System Center 2012 Configuration Manager.

Who is it for?

Admins of System Center 2012 Configuration Manager who help resolve issues with software update synchronization.

How does it work?

We’ll begin by asking if the prerequisites for software update synchronization are met. If the prerequisites are met and you’re still facing the issue, we’ll take you through a series of steps to resolve your issue.

Estimated time of completion:

15-30 minutes.

Verify the Prerequisites

The first step in troubleshooting synchronization issues is to verify that the following prerequisites are met:

  • If using WSUS 3.0 SP2, KB2734608 must be installed on the WSUS server. You can verify this by looking at the server version. To do this, launch the WSUS console and click on the server name. You will find the server version under Overview -> Connection -> Server Version. Make sure the version is 3.2.7600.256 or later.
  • When the Software Update Point is installed on a remote site system server, the WSUS Administration console must be installed on the site server. If using WSUS 3.0 SP2, KB2734608 needs to be installed on the WSUS Administration console as well.
  • After installing KB2734608 (remote or local), a reboot is required. Reboot the server and verify whether the issue still exists.
  • Verify that WSUS running on a Software Update Point is not configured to be a Replica. To check this, open the WSUS console on the Software Update Point and click Options in the console tree pane, then select Update Source and Proxy Server in the display pane.
  • Verify that the Update Services service is running on the WSUS server.
  • Verify that the Default Website or WSUS Administration website is running on the WSUS server.

Did this solve your problem?

Verify the Prerequisites

The first step in troubleshooting synchronization issues is to verify that the following prerequisites are met:

  • If using WSUS 3.0 SP2, KB2734608 must be installed on the WSUS server. You can verify this by looking at the server version. To do this, launch the WSUS console and click on the server name. You will find the server version under Overview -> Connection -> Server Version. Make sure the version is 3.2.7600.256 or later.
  • When the Software Update Point is installed on a remote site system server, the WSUS Administration console must be installed on the site server. If using WSUS 3.0 SP2, KB2734608 needs to be installed on the WSUS Administration console as well.
  • After installing KB2734608 (remote or local), a reboot is required. Reboot the server and verify whether the issue still exists.
  • Verify that WSUS running on a Software Update Point is not configured to be a Replica. To check this, open the WSUS console on the Software Update Point and click Options in the console tree pane, then select Update Source and Proxy Server in the display pane.
  • Verify that the Update Services service is running on the WSUS server.
  • Verify that the Default Website or WSUS Administration website is running on the WSUS server.

Did this solve your problem?

Synchronization fails with “WSUS server not configured”

WSUS Configuration Manager (WCM) configures the WSUS server once every hour in order to ensure that the settings configured in WSUS match the setting specified in the Configuration Manager console. If WCM fails to configure the WSUS Server properly, synchronization attempts can fail with an error similar to the following:

3867_image4
 

You will also find the following error in the WsyncMgr.log file on the Site Server (located in \Logs):

Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details. Source: CWSyncMgr::DoSync

Sync failed. Will retry in 60 minutes


Are you experiencing an error similar to this?

Synchronization fails due to Authentication and Proxy Issues

Synchronization may fail due to authentication or proxy issues. When this occurs you will see an error similar to the following in the WCM.LOG file:

System.Net.WebException: The request failed with HTTP status 502

Note that the error may not always be HTTP status 502, and may in fact be one of the following:

  • HTTP Status 401 Unauthorized
  • HTTP Status 403 Forbidden
  • HTTP Status 407 Proxy Authentication Required
  • HTTP Status 502 Proxy Error

You could also see errors similar to the following:

  • No connection could be made because the target machine actively refused it
  • Authentication failed because the remote party has closed the transport stream

If you are seeing one of these errors, select it below.

Fixing authentication and proxy issues

Synchronization may be failing due to authentication and/or proxy issues. To verify, complete the following:

  • Verify that the Update Services service is running on the WSUS Server.
  • Verify that the Default Website or WSUS Administration website is running on the WSUS Server.
  • Verify that the fully qualified domain name (FQDN) for the software update point site system server is correct and accessible from the Site Server.
  • If the Software Update Point is remote from the Site Server, verify that you can connect to the WSUS Server from the Site Server. To do this, connect to the remote WSUS Server using the WSUS Administration Console.
  • Check the port settings configured for the Software Update Point and verify that they are the same as the port settings configured for the Web site used by WSUS running on the Software Update Point.
  • Verify that the proxy and account settings are properly configured for the Software Update Point:
  • Verify that the Software Update Point connection account is configured (if required) and that it has rights to connect to the WSUS Server.
  • Verify that the permissions on the ApiRemoting30 Virtual Directory are set correctly in IIS.
  • If the Software Update Point is configured for SSL, verify that WSUS is properly configured for SSL. For more information on how to do this, see http://technet.microsoft.com/library/dd939849(WS.10).aspx#ssl

Did this solve your problem?

Synchronization fails due to Web Service issues

Synchronization may be failing due to issues with the Web service. When this occurs you will see an error similar to the following in the WCM.LOG file:

System.Net.WebException: The request failed with HTTP status 500

or

System.Net.WebException: The request failed with HTTP status 503

If you are seeing one of these errors, select it below.

Fixing Web Service issues

When synchronization is failing due to issues with the Web Service, verify the following:

  • Verify that the Update Services service is running on the WSUS Server.
  • Verify that the Default Website or WSUS Administration website is running on the WSUS Server.
  • Check the port settings configured for the Software Update Point and verify that they are the same as the port settings configured for the Web site used by WSUS running on the Software Update Point.

Did this solve your problem?

Synchronization fails due to SSL Issues

Synchronization may be failing due to issues with SSL. If you are using SSL please verify the following:

  • Verify that the certificate configured for the WSUS website is configured with the proper FQDN. If the certificate doesn’t have the proper FQDN, refer to KB931351 for steps on adding a Subject Alternate Name to a certificate.
  • Verify that the certificate has not expired.
  • Verify that WSUS is properly configured for SSL. For more information on how to do this, see http://technet.microsoft.com/library/dd939849(WS.10).aspx#ssl

Did this solve your problem?

Synchronization fails due to issues with the EULA

Synchronization issues can often times be traced back to issues relating to the End User Licensing Agreement (EULA). To verify whether this is your issue, complete the following:

  • Review the SoftwareDistribution.log file on the WSUS Server to find out if the EULA’s are not getting downloaded, and if so, why. Look for “.txt” in the log to find relevant entries.
  • Verify that the firewall is configured to allow communication with Microsoft Update. For details on this, please see http://technet.microsoft.com/en-us/library/dd939870(WS.10).aspx
  • Verify the proxy configuration. For more information, see the “Proxy Server Settings” section at http://technet.microsoft.com/en-us/library/gg712312.aspx#BKMK_InstallSUP
  • Run “%ProgramFiles%\Update Services\Tools\wsusutil.exe reset” from a Command Prompt to have WSUS re-download missing content, including EULAs.

Did this solve your problem?

Synchronization fails due to errors communicating with Microsoft Update

Synchronization may be failing due to errors communicating with Microsoft Update. When this occurs, you will usually see errors similar to the following:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

0x80072EFE - The connection with the server was terminated abnormally

Steps to try:

Did this solve your problem?

Congratulations!

Your Software Update Synchronization Issue is resolved.

Sorry

It appears that we are unable to resolve your issue by using this guide. For more help resolving this issue please see our TechNet support forum or contact Microsoft Support.

Propriedades

ID do Artigo: 10059 - Última Revisão: 14 de abr de 2016 - Revisão: 39

Comentários