WSUS Product Team Blog

WSUS Product Team thoughts, information, tips and tricks and beyond :-)

Client/Server Synchronization issues

Client/Server Synchronization issues

  • Comments 146
  • Likes

Good morning!

Now that you are all back from TechEd, I wanted to address an issue that a couple of folks contacted us about regarding some client/server synchronization issues they were experiencing in their WSUS environment.



Computers that have Office 2003 or components of Office 2003 installed fail to run a detection against a WSUS server that has the latest Office updates. This prevents the computers from receiving any updates from the WSUS server.


Affected products:

·         WSUS 3.0 Server (RTM or SP1)

·         Computers with Office 2003 or components of Office 2003 installed.



Automatic updates fails detection against the WSUS server.


1.       On the client side, the automatic updates log file (%windir%\WindowsUpdate.log) has an entry similar to below during the detection phase:

2008-06-13    19:59:53:383  788   ee4    PT     +++++++++++  PT: Synchronizing server updates  +++++++++++

2008-06-13    19:59:53:383  788   ee4    PT       + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://<WSUS Server>/ClientWebService/client.asmx

2008-06-13    19:59:56:617  788   ee4    PT     WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

2008-06-13    19:59:56:617  788   ee4    PT     WARNING: SOAP Fault: 0x000190

2008-06-13    19:59:56:617  788   ee4    PT     WARNING:     faultstring:Fault occurred

2008-06-13    19:59:56:617  788   ee4    PT     WARNING:     ErrorCode:InternalServerError(5)

2008-06-13    19:59:56:617  788   ee4    PT     WARNING:     Message:(null)

2008-06-13    19:59:56:617  788   ee4    PT     WARNING:     Method:""

2008-06-13    19:59:56:617  788   ee4    PT     WARNING:     ID:c0a7445f-b989-43fa-ac20-11f8ca65fa8c


2.       On the WSUS server, the WSUS log file (%Program Files%\Update Services\Log Files\SoftwareDistribution.log) has an entry similar to below, which one can find by searching on the ID obtained from the client log:

2008-06-14 02:59:57.642 UTC Error  w3wp.12       ClientImplementation.SyncUpdates       System.ArgumentException: Item has already been added. Key in dictionary: '8862'  Key being added: '8862'

   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)

   at System.Collections.Hashtable.Add(Object key, Object value)

   at Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(DataAccess dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean haveGroupsChanged, Boolean doChunking)

   at Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess dataAccess, UnencryptedCookieData cookieData, Int32[] installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged, Boolean expressQuery)

   at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)

   at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)

   at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)

       <lines removed>

2008-06-14 02:59:57.642 UTC Warning       w3wp.12       SoapUtilities.CreateException     ThrowException: actor = http://wsusebc/ClientWebService/client.asmx, ID=c0a7445f-b989-43fa-ac20-11f8ca65fa8c, ErrorCode=InternalServerError, Message=, Client=?


Root Cause:

A recent revision to the ‘Office 2003 Service Pack 1’ update has resulted in some WSUS 3.0 servers syncing

the revised update to enter an inconsistent state with respect to the update’s approvals. When computers with products related to Office 2003 communicate with such a server, the Web service is unable to process the approvals resulting in the detection failure.



In order to reset the approvals to a consistent state on the WSUS server, follow these steps from the WSUS Administration Console:

1.       Find the Office 2003 Service Pack 1 update in the updates list, UpdateID: D359F493-0AAD-43FA-AF5C-6763326CD98F. This may involve changing the Status and Approval filters. Set Status to Any and Approval to Declined; if you still do not see the update, set Approval to Any Except Declined.

2.       Perform the following steps:

a.        Ensure the update is already declined.

                                                                                       i.      If the update is not already declined, right-click on the update and then click Decline in the shortcuts menu.

b.       Cause the update not to be declined.

                                                                                       i.            Right-click the update and then click Approve in the shortcuts menu.

                                                                                     ii.            In the Approve Updates dialog that opens, just click OK without making any changes to the approval settings.

c.        Decline the update.

                                                                                       i.       Right-click the update and then click Approve in the shortcuts menu.

                                                                                     ii.       In the Approve Updates dialog that opens, just click OK. Dismiss the Approval Progress dialog that appears.


The computers that were failing detection will now successfully complete detection against the server and receive any applicable updates.


Note: If you have a hierarchy of WSUS servers, these steps must be performed on each server, starting with the top-level server. If one of the servers is a replica child, one must first change it to be autonomous, then perform the steps above, then change it back to being a replica. This can be done from the Options/Update Source and Proxy Server dialog box.


Thank you.


Cecilia Cole

WSUS Program Manager 


  • I seem to have had exactly this problem, with one exception, and one problem with the resolution given. The exception is that my SoftwareDistribution.log shows:

    "Key in dictionary: '8915'  Key being added: '8915'"

    Rather than the

    "Key in dictionary: '8862'  Key being added: '8862'"

    Listed here. Maybe that doesn't matter? I'm afraid I don't know enough about WSUS to know if it does or doesn't.

    The problem I have with the resolution is that I don't have an update called "Office 2003 Service Pack 1" in my list of updates.  It is not listed under "Declined" and it is not listed under "Any Except Declined". I do have Office 2003 Service Pack 2 and 3, and I have "Office 2003 Service Pack 1 for English User Interface Pack" and "...for Multilingual Interface Pack" and "...for Proofing Tools" but nothing with the update ID you specified.

    However... I did a search for the update by name and it appeared in the results. I was able to decline the update, and then it appeared in the list of updates in the WSUS console. I followed the instructions given above except that in step C. I right clicked and selected "Decline" then pressed "Yes".

    And that fixed the problem! Thanks!

  • I have the same problem.  I followed the steps above several times. For some reason, the service pack "Has expired" and is being superseded by something, not allowing it to be approved.  At this point, I still cannot get  workstations to talk to the server.  Has a magic fix been implemented to correct the 3008 Office 2003 Service Pack 1 error?

    Help and Thanks.

  • I went into WSUS, did a search for Office 2003, right clicked on Service Pack 1 and choose revisions.  From that screen, I right clicked on each revision, chose approved for install. After approving each one (even the ones that were expired) I then declined each one (even the ones that would not approve).  I then did a manual synchro, then they SLOWLY started coming back to the server.

  • After a full day of researching this problem I stumbled onto this site & saw Cecilia's post & thankfully it has resolved the issue where all other attempts had failed. Thanks Cecilia.

  • WOO! Hopefully this fixes the issues I have been having running updates after Office 2003 installs.

    Reloading a computer tomorrow to find out.

  • Where is the KB article for this problem?

    Do we really have to resort to blog entries to fix faults in Microsoft's software?

  • I spent hours looking for a fix for this. Ten mins after reading this WSUS was working again.  Nice one, thanks

  • Wow did this save me from slitting my wrist. Shoot microsoft this week admits to the issue and a hot fix in a couple of weeks.

    Decline office SP1 and shazam.


  • @Michael,


    Title: Microsoft Security Advisory Notification

    Issued: June 30, 2008


    Security Advisories Updated or Released Today ==============================================

    * Microsoft Security Advisory (954960)

     - Title: Microsoft Windows Server Update Services

       (WSUS) Blocked from Deploying Security Updates


     - Revision Note: Advsiory published.    

  • C'&#232; purtroppo l'evidenza di un problema non-security analogo negli effetti a quello descritto dallo

  • Hi,

    I guess that i have a similar issue with another update :

    WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

    PT WARNING: SOAP Fault: 0x000190

    WARNING:     Method:""

    PT WARNING:     ID:2a7512fe-2d8f-4c3b-a586-1ce1197cb468

    Can you tell which update shall i decline ???

    Many thanks in advance


  • Hi,

    I have WSUS 3.0 SP1 and SCCM 2007 SP1 in the same server. 95% of all our machines have Office 2003 SP3 and the rest Office 2007 or no Office at all.

    Only machines without Office 2003 scan and synchronize OK with SCCM 2007 SP1 while all the rest 95 % of machines with Office 2003 won't synchronize at all. WindowsUpdate-logs show no errors on clientside.

    In SCCM 2007 Software Update console show "Not Required" for all those machines with office 2003. I have used all the known tricks to start synchronizing but no avail. This has been like few weeks. I removed Office 2003 fram one computer and rebooted and synchronizing started for that machine.

    Now I cant deliver any updates for those 95 % of machines and I haven't seen any  advertisement from Microsoft to resolve this major problem.

  • Update available now

  • The WSUS Team finally posted word that an update/hotfix is now available (KB954960) for public download

  • Dear all,

    That has fixed my issue (after applying SP1 and KB954960)

    Many thanks

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment