SMS WSUS Synchronization failed – SCCM Software Update Point


Using SCCM Software Update Point in combination with a proxy server can lead to WSUS synchronization problems. Synchronization
problems can be identified by the following status messages

SMS_WSUS_SYNC_MANAGER Message ID: 6703

SMS WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates

and by wsyncmgr.log:

Failed to sync update e5077be1-da82-4c15-82d1-e4e8ff0a1264. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas

You may experience this problem if a computer is behind a firewall or behind a proxy server. This problem occurs if one of the following conditions is true:

  • The proxy server environment does not support the HTTP 1.1 range request
    feature.
  • You are behind a SonicWALL firewall device, and the Enable HTTP Byte-Range request with Gateway AV setting is
    not enabled for the device.

When you copy a file by using BITS in background mode, the file is copied in multiple small parts. To perform this kind of copy operation, BITS uses the HTTP 1.1 Content-Range header. If you are behind a proxy server or behind a firewall that removes this header, the file copy operation is unsuccessful.

Note When BITS copies files in foreground mode, BITS does not use this header.

You may experience this problem if a computer is behind a firewall or behind a proxy server. This problem occurs if one of the following conditions is true:

  • The proxy server environment does not support the HTTP 1.1 range request
    feature.
  • You are behind a SonicWALL firewall device, and the Enable HTTP Byte-Range request with Gateway AV setting is
    not enabled for the device.

When you copy a file by using BITS in background mode, the file is copied in multiple small parts. To perform this kind of copy operation, BITS uses the HTTP 1.1 Content-Range header. If you are behind a proxy server or behind a firewall that removes this header, the file copy operation is unsuccessful.

Note When BITS copies files in foreground mode, BITS does not use this header.

If you are using WSUS 3.0 with a Windows Internal Database that was created by a default WSUS installation, type the following command:

%programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername%\MICROSOFT##SSEE -d “SUSDB” -Q “update tbConfigurationC set BitsDownloadPriorityForeground=1”

If you configured WSUS 3.0 to use an existing installation of SQL Server, type the following command:

%programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d “SUSDB” -Q “update tbConfigurationC set BitsDownloadPriorityForeground=1”
Restart the Update Services service and reset wsus by : wsusutil.exe reset
I’m running up against this problem with a McAfee Web Gateway 6.8.7 Build 8378
Advertisements

One thought on “SMS WSUS Synchronization failed – SCCM Software Update Point

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s