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.0 to WSUS 3.0
- System Center Essentials 2007
- System Center Configuration Manager 2007
For more information, see the advisory.
When this problem occurs, a message that resembles the following message 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.asmx
Date Time 788 ee4 PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
Date Time 788 ee4 PT WARNING: SOAP Fault: 0x000190
Date Time 788 ee4 PT WARNING: faultstring:Fault occurred
Date Time 788 ee4 PT WARNING: ErrorCode:InternalServerError(5)
Date Time 788 ee4 PT WARNING: Message:(null)
Date Time 788 ee4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
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 message is logged in the WSUS log file (%ProgramFiles%\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 removed
Date 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 a Microsoft Office 2003 Service Pack 1 (SP1) 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.
We recommend that you upgrade to WSUS 3.0 SP1 and receive update 954960. If you do not want to upgrade to WSUS 3.0 SP1 at this time, follow the procedure in this section to manually reset the approvals to a consistent state on the WSUS server.
- On the WSUS Administration console, in the Updates list, locate the Office 2003 Service Pack 1 update.
- Confirm that the update is Declined. If the update is not declined, right-click the update, and then click Decline.
- Approve the update. To do this, right-click the update, click Approve, and then click OK. Do not make any changes to the approval settings in the Approve Updates dialog box.
- Decline the update. To do this, right-click the update, and then click Decline.
- Computers should now successfully complete detection against the WSUS server and receive any applicable updates. To verify that a computer can synchronize:
- Open a command prompt.
- Type the following command:
wuauclt.exe/detectnow
- Press ENTER.
- Review the WindowsUpdate.log file to verify that the synchronization is successful. You may have to run the detectnow command two times. Some customers reported that the first synchronization fails but that successive synchronizations succeed.
- If you have a hierarchy of WSUS servers, repeat this procedure on each server. Start with the top-level server. If any of the servers is a replica child server, change it to be autonomous by using the Options/Update Source and Proxy Server dialog box. Follow the procedure steps, and then change the autonomous server back to a replica child server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 954960 - Last Review: May 5, 2009 - Revision: 7.0
APPLIES TO
- Windows Server Update Services 3.0
- Windows Server Update Services 3.0 Service Pack 1
| kbinfo kbbug kbexpertiseinter kbpubtypekc kbsecurity kbsecvulnerability kbsecadvisory KB954960 |