WSUS fix for update detection issues for clients with Office 2003 SP1

Posted by bink on July 10 2008, 3:04 PM. Posted in Office, WSUS.

Consider the following situation. You use Microsoft Windows Server Update Services (WSUS) 3.0 to deploy software updates and hotfixes to computers that are in your organization. However, some computers do not receive updates from the WSUS server. This problem occurs if the computers have Microsoft Office 2003 or components of Office 2003 installed. Note This problem affects Microsoft Windows Server Update Services 3.0 and Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1). However, in some circumstances, the following products may also be affected:

Windows Small Business Server 2003 (Windows SBS) that has had the WSUS component upgraded from WSUS 2 to WSUS 3
System Center Essentials 2007
System Center Configuration Manager 2007
See the advisory for more information. When this problem occurs, a message that resembles the following is logged in the Automatic Updates log file (%windir%\WindowsUpdate.log) on the affected computer:

Date Time 788 ee4 PT +++++++++++ PT: Synchronizing server updates +++++++++++Date Time 788 ee4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS Server/ClientWebService/client.asmxDate Time 788 ee4 PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200Date Time 788 ee4 PT WARNING: SOAP Fault: 0x000190Date Time 788 ee4 PT WARNING: faultstring:Fault occurredDate Time 788 ee4 PT WARNING: ErrorCode:InternalServerError(5)Date Time 788 ee4 PT WARNING: Message:(null)Date Time 788 ee4 PT WARNING: Method:""Date Time 788 ee4 PT WARNING: ID:c0a7445f-b989-43fa-ac20-11f8ca65fa8c

This message is logged during the detection phase. Also, a message that resembles the following is logged in the WSUS log file (%Program Files%\Update Services\Log Files\SoftwareDistribution.log) on the WSUS computer:

Date Time 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 removedDate Time UTC Warning w3wp.12 SoapUtilities.CreateException ThrowException: actor = http://wsusebc/ClientWebService/client.asmx, ID=c0a7445f-b989-43fa-ac20-11f8ca65fa8c, ErrorCode=InternalServerError, Message=, Client=?

To locate this message, search the WSUS server for the ID that is obtained from the client log.

This problem occurs because a recent revision to an Office 2003 Service Pack 1 update causes some WSUS 3.0 servers to incorrectly synchronize the revised update with the update’s approvals. When the affected client computers communicate with such a server, the Web service is unable to process the approvals. Therefore, the detection is unsuccessful.

Download the Microsoft Windows Server Update Services (WSUS) (KB954960) package now. ( the Microsoft Windows Server Update Services x64 Edition (WSUS) (KB954960) package now.