SCCM and WSUS error

[tmcd35]

Hi,

 

I'm having a SCCM problem, won't be the last I'm sure. I've tried googling and registering over at windows-noob but so far no joy. Since I know there's a few sccm experts in these parts I thought I'd see what you guys could come up with

 

I've set up the software update point role but I'm getting errors. I think it is downloading some windows updates, either that or it just found them in the WSUS server. But when I do a sync I get the following errors:

 

Severity Type Site code Date / Time System Component Message ID Description

Error Milestone CM1 04/03/2013 10:23:22 SCCM.CHAOS.LOCAL SMS_WSUS_SYNC_MANAGER 6703 WSUS Synchronization failed. Message: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.

 

Looking in the wsyncmgr log file I have:

 

Failed to sync update a024086f-17fd-4875-8d84-a5d9a6811ed4. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow $$<03-04-2013 08:12:52.488+00>

Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<03-04-2013 08:12:53.363+00>

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCM.CHAOS.LOCAL SITE=CM1 PID=2388 TID=3632 GMTDATE=Mon Mar 04 08:12:53.363 2013 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<03-04-2013 08:12:53.364+00>

Sync failed. Will retry in 60 minutes $$<03-04-2013 08:12:53.381+00>

Setting sync alert to active state on site CM1 $$<03-04-2013 08:12:53.381+00>

Sync time: 0d00h08m02s $$<03-04-2013 08:12:53.386+00>

 

Anyone with any ideas?

[AliG]

SNAP! Turned on SUP on Friday been investigating this error throughout the day some mention of accepting EULA's?

[tmcd35]

Yep, can't find anywhere to accept EULA's. I look at the patch list, added the "Licence Type" column, and non of the listed patches have a licence that needs accepting?!?

[screendj]

Hi all,

 

we're seeing the same error:

The Microsoft Software License Terms have not been completely downloaded and cannot be accepted.

 

This occurs multiple times in the wsyncmgr.log. then the process bombs out with:

Too many consecutive failures. Aborting sync.

 

Did you guys find a solution or workaround for this?

 

Cheers, Simon.

[sonofsanta]

Have you got any auto deployments set up at all? The Deployment Settings tab of an auto deploy rule has a radio button to approve any licence agreements. If you've set up an ADR for endpoint protection it may be blocking other updates from downloading.

 

I can't see anything in Admin > Site Config > Sites > Configure Site Components > Software Update Point, which is where I'd expect something though.

[forrager]

Recently had this error and in my case it was due to moving the WSUS content to a new location.

 

Scratched my head for a while with this one but what resolved it for me was this.

 

Edit SUP configuration

Deselect ALL classifications

Run wsusutil /reset

Manually initiate sync all

(Note that this may timeout)

Add back in your classifications to SUP

Manually sync again

 

This should clear the issue for you and in my case it also prevented the autorun rules from running after every sync attempt.

[forrager]

Recently had this error and in my case it was due to moving the WSUS content to a new location.

 

Scratched my head for a while with this one but what resolved it for me was this.

 

Edit SUP configuration

Deselect ALL classifications

Run wsusutil /reset

Manually initiate sync all

(Note that this may timeout)

Add back in your classifications to SUP

Manually sync again

 

This should clear the issue for you and in my case it also prevented the autorun rules from running after every sync attempt.

 

Edit: Should have read

 

This should clear the issue for you and in my case it also prevented the autorun rules from running after every failed sync attempt

Edited June 20, 2013 by forrager