none
6703 - Failed to sync some of the updates.

    Question

  • Hi guys,

     

    I am seeing the following error status message:

     

    ID 6703: "MS WSUS Synchronization failed. Message: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates."

     

    wsyncmgr.log shows:

     

    "Synchronizing update 0c9f4827-4f1e-4563-b557-7431f70dd6ce:  Windows Internet Explorer 7.0 for Windows XP 10.12.2007 15:52:11 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)
    Failed to sync update 0c9f4827-4f1e-4563-b557-7431f70dd6ce. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas 10.12.2007 15:52:12 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)

    [...]

    Synchronizing update fd11f1d0-8576-4ca9-a9eb-bc3223f7987d:  Windows Internet Explorer 7.0 for Windows Server 2003 10.12.2007 15:52:15 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)
    Failed to sync update fd11f1d0-8576-4ca9-a9eb-bc3223f7987d. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas 10.12.2007 15:52:15 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)
    [...]

    Failed to sync update 0c9f4827-4f1e-4563-b557-7431f70dd6ce. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas 10.12.2007 15:58:44 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)
    Failed to sync update fd11f1d0-8576-4ca9-a9eb-bc3223f7987d. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas 10.12.2007 15:58:44 SMS_WSUS_SYNC_MANAGER 13488 (0x34B0)
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates 10.12.2007 15:58:45 SMS_WSUS_SYNC_MANAGER 15604 (0x3CF4)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xyz SITE=xxx PID=14424 TID=15604 GMTDATE=Mo Dez 10 14:58:45.337 2007 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 10.12.2007 15:58:45 SMS_WSUS_SYNC_MANAGER 15604 (0x3CF4)
    Sync failed. Will retry in 60 minutes 10.12.2007 15:58:45 SMS_WSUS_SYNC_MANAGER 15604 (0x3CF4)
    Updated 12187 items in SMS database, new update source content version is 3 10.12.2007 15:58:45 SMS_WSUS_SYNC_MANAGER 15604 (0x3CF4)"

     

    It's only 2 of the updates that are failing. The rest work fine. Any ideas?

     

    Thanks,

    Torsten

     

     

     

    Monday, December 10, 2007 3:33 PM

Answers

  • Hi Torsten,

     

    Are you still having this issue?  When we synchronize updates and when clients scan for updates, access to the EULA (license terms) is required, when there is one associated with the update.  When the "Store updates locally" setting is configured in WSUS (which it should be) then the EULA is copied to the local WSUS content share and the site accesses the share to get the EULA during the synchronization process.  If it can't find the EULA then you will get the error you are seeing.  Sometimes, this is a timing issue and during the next synchronization it will complete successfully.

     

    Hope this helps!

     

    Thanks,

     

    Doug

     

    Friday, December 14, 2007 11:23 PM

All replies

  • Hi Torsten,

     

    Are you still having this issue?  When we synchronize updates and when clients scan for updates, access to the EULA (license terms) is required, when there is one associated with the update.  When the "Store updates locally" setting is configured in WSUS (which it should be) then the EULA is copied to the local WSUS content share and the site accesses the share to get the EULA during the synchronization process.  If it can't find the EULA then you will get the error you are seeing.  Sometimes, this is a timing issue and during the next synchronization it will complete successfully.

     

    Hope this helps!

     

    Thanks,

     

    Doug

     

    Friday, December 14, 2007 11:23 PM
  • Thanks for your reply, Doug. It seem that it's been a timing issue (or whatever). The message did no longer appear during the next sync.

     

    Monday, December 17, 2007 8:21 AM
  • Doug,

     

    Are these Eula's stored on a different url than the updates? I am seeing this issue now as well, but I am behind a pretty restrictive proxy. The catalogs and updates without eulo download just fine, all the ones with eula seem to fail.

     

    Kim Oppalfens

     

    Thursday, February 07, 2008 4:12 PM
  • Did you track the other thread on this? See if this helps: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2801399&SiteID=17

     

    I know, you were asking Doug, but hopefully he was going to point you to the same post :-) If not, sorry Doug.

    Thursday, February 07, 2008 5:53 PM
  • I am having this same issue.  It retries the synchronization every hour and I have executed the "wsusutil reset" command and I still get the same error.  The wsyncmgr.log file shows "License agreement not ready." for quite a few updates, which have all failed.

     

    Is there a way to either force or manually download the EULA's?

     

    Thanks for your help!

     

    Kevin

    Wednesday, April 30, 2008 1:25 PM
  •  

    was there a resolution to this, I'm having the same issue.

     

    I see this on quite a few updates "....transient state while WSUS is downloading the agreement"

     

     

    Failed to sync update aba4ef1a-7b73-4264-b884-3cb8390cc51c. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 6/26/2008 6:11:50 PM 5308 (0x14BC)

     

    Failed to sync update 1278a789-b29b-482d-b721-f3bc3c9ede66. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 6/26/2008 6:11:56 PM 5308 (0x14BC)

     

    Friday, June 27, 2008 4:42 PM
  • If waiting a few cycles for the synch does not resolve this issue, what are the next steps to troubleshoot?
    Monday, June 30, 2008 1:30 PM
  • I am also having the same issue.

    Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas

    In turn the clients don't seem to pick up these updates either (as they are not downloaded)

    WARNING: ISusInternal::GetEulaText failed, hr=80240033


    Ideas anyone Smile

    Ben
    Tuesday, October 14, 2008 10:02 PM
  • I had to correct this in WSUS and accept the license there and now OK Smile
    Friday, December 05, 2008 1:35 AM
  • Could you please let me know how to do that in WSUS, since I am having the same issue.

    tx
    peer
    Wednesday, May 20, 2009 7:27 AM
  • I have same issue and solve it by reading (thx Wally) http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2801399&SiteID=17

    Brief resolution:
    Check "WSUS store updat localy" is checked.
    Check permisions on wsus folder -> UpdateServicesPackages and  WsusContent -> Network Service grand modify permissions
    Check logs %systemdrive%\Program Files\Update Services\LogFiles\*.log and wsyncmgr.log
    Check if my SCCM UP can succesfuly download somthing like this http://au.download.windowsupdate.com/msdownload/update/v5/eula/2003_sp2_eula_zhtw-0593447d-ca8e-40d4-abf3-11e489e77145.txt (usinf all thous proxy setting configured in wsus sync)

    After check all this stuff I run SCCM UP Update sync but it fails, with same errors. But next scheduled sync in 1 hour download all licenses I needed.

    Monday, June 01, 2009 7:57 AM
  • I had this same error.

    Setup:

    • All servers 2008 x64, SQL 2008 x64, WSUS 3.0 SP1, CM2K7 SP1
    • 3 SUPs behind an NLB and another server with the WSUS DB on it.
    • The NLB is set as the default update point.
    • The three SUPs had a domain acct setup for the WSUS app pool and the content share for each SUP was set to the WsusContent folder (shared) on the WSUS DB server.

    Once I changed anonymous user identity in IIS7 to use the application pool identity, all the errors went away.

    I might be the only person with this oddball setup, but it's worth posting here in case I need to look it up again.
    Microsoft MVP - SCCM
    • Proposed as answer by rotem Wednesday, April 06, 2011 8:43 AM
    Wednesday, October 07, 2009 10:45 PM
  • I too had this error - the resolution for me turned out to be that the proxy server SCCM/WSUS box is behind, doesn't seem to support HTTP 1.1 range requests.

    I got around it by changing BITS to run in foreground mode, per this article: http://support.microsoft.com/kb/922330, which allowed a sync to complete successfully - inlcuding the EULAs.

    However - the next time I attempted to download updates that I was adding to an update list, I got an error "The process is not in background processing mode". So I switched BITS back to background mode, ran a couple of syncs, and then was able to download updates again.

    I guess now I need to get the Security guys to enable HTTP 1.1 range requests throught the proxy.

    Friday, March 12, 2010 4:17 AM
  • Shaun, I had the same issue.  It was BITS not being able to download the files.  I found the error in the SoftwareDistribution.log.  Side Note: if you are going to read SCCM Log File, do yourself a favor and install the Toolkit and leverage Trace32.

    To ensure that the problem was BITS related I used BITSAdmin.exe (built into windows) to try fetching the file.  I could get it through IE, but BITS failed.  The fix was indeed a change to the Fortigate firewall.

    After I got BITS working I had to run a sync twice before it got everything it needed and the errors went away.

    Some more details: http://mrshannon.wordpress.com/2010/04/21/bits-and-sccm-software-updates/

    Wednesday, April 21, 2010 6:55 PM
  • Brian Mason - Thank you for your fix! I tried everything else I found dealing with permissions and firewalls and this is what fixed it:

    Went into IIS and changed the Anonymous authentication to the application pool identity on the following sites:

    Client Web Service, DSSAuthWebService, Inventory, ReportingWebService, ServerSynceWebService, and SimpleAuthWebService. 

    These all use the WSUSPool Application Pool.  I didn't change it on the CCC or SMS sites because I didn't want to screw them up.


    Katrina
    Wednesday, August 17, 2011 6:31 PM
  • hey torsten,

     

    i am facing the same problem

    with the following populating in my wsyncmgr.log

    Failed to sync update a024086f-17fd-4875-8d84-a5d9a6811ed4. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 034e1b15-796a-4ca2-bc39-e7e7a9890b1d. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 1278a789-b29b-482d-b721-f3bc3c9ede66. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    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 SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 80426d35-deed-40db-a13e-6da7231e1e2f. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 01e9037a-d9c7-4acc-a8fa-5d7b47da193c. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 34b52415-a5ba-41e9-8072-9d2dee8b22a9. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 3331cb93-46b3-438c-a5f5-6eda6c76c50a. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 482d29fe-7a9b-46cc-a77e-0af94f146ce3. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Failed to sync update 8f771ec5-fcd3-4a6b-ada6-7d6f0927f080. Error: License agreement not ready. This is a transient state while WSUS is downloading the agreement. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.ProcessEulas SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:16 PM 6872 (0x1AD8)
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:17 PM 3928 (0x0F58)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SVDCAPSCCM01 SITE=ISD PID=2984 TID=3928 GMTDATE=Thu Jan 26 14:24:17.238 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:17 PM 3928 (0x0F58)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:17 PM 3928 (0x0F58)
    Sync time: 0d00h06m00s SMS_WSUS_SYNC_MANAGER 1/26/2012 7:24:17 PM 3928 (0x0F58)

    need your help!

     

    I have the correct configurations for native mode and have one running in my test already


    AMIM MUHAMMAD KHAN | CTTCNET USER GROUP LEAD | EVENT SPEAKER, MCT, MCTS, MCITP-ENTERPRISE, MCSA http://amimkhan.wordpress.com
    Thursday, January 26, 2012 3:06 PM
  • Ok, finally got it working!!! The issue was something that was related to

    HttpSendRequest failed HTTP_STATUS_FORBIDDEN or HTTP_STATUS_DENIED

    and

    ERROR: DownloadContentFiles() failed with hr=0x80070191.

    I saw these errors in PatchDownloader.log on SCCM server.

    Apparently the way the WSUS website was set up had incorrect settings specified for enabling Anonymous Authentication for the web site. I had to Edit Anonymous Authentication (by right clicking) and change it from a Specific User to Application pool identity.

    Once it was complete, I could download third party updates without any issue.


    Kapil Dham

    • Proposed as answer by Kapil Dham Thursday, February 28, 2013 3:40 PM
    Thursday, February 28, 2013 3:40 PM