Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Some computers do not receive updates from the WSUS server

Some computers do not receive updates from the WSUS server

Technical update: August 1, 2008

Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/advisory/954960.mspx

↑ Back to the top

Symptoms

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.


NoteThis 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.

↑ Back to the top

Cause

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.

↑ Back to the top

Resolution

To resolve this issue on a server that is running WSUS 3.0 SP1

  1. Confirm that the current Region and Language setting on the WSUS server is the same setting under which WSUS was installed. For example, if the WSUS server was set to English (United States) when WSUS was installed, and the current setting is German (Switzerland), then change the language to English (United States) before you install this update.
  2. Install update 954960. Click the applicable Microsoft Download Center link for your server:



    Download Download the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 (KB954960) package now.

    Download Download the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 for x64-based Systems package now.

    Release Date: August 1, 2008

    For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
    119591 How to obtain Microsoft support files from online services
    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
  3. If applicable, change the WSUS server language to the desired setting.

To resolve this issue on a server that is running WSUS 3.0 RTM

Do one of the following:
  • Upgrade from WSUS 3.0 RTM to WSUS 3.0 SP1 and receive update 954960 automatically. For information, visit the following Microsoft Web site:
    http://go.microsoft.com/fwlink/?linkid=93750
  • Or, if you do not want to upgrade to WSUS 3.0 SP1 at this time, follow the instructions in the "Workaround" section.


↑ Back to the top

Workaround

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.

  1. On the WSUS Administration console, in the Updates list, locate the Office 2003 Service Pack 1 update.
    • Note More than one Office 2003 Service Pack 1 update may have been published. It is important to verify that you have located the specific version of this update that is required for this procedure. Confirm that the following UpdateID is displayed at the bottom of the details pane:
      D359F493-0AAD-43FA-AF5C-6763326CD98F
    • You may have to change the filters in the Update node to see this update. To do this, set Status to Any, and set Approval to Declined. If you still do not see the update, set Approval to Any Except Declined.
  2. Confirm that the update is Declined. If the update is not declined, right-click the update, and then click Decline.
  3. 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.
  4. Decline the update. To do this, right-click the update, and then click Decline.
  5. Computers should now successfully complete detection against the WSUS server and receive any applicable updates. To verify that a computer can synchronize:
    1. Open a command prompt.
    2. Type the following command:
      wuauclt.exe/detectnow
    3. Press ENTER.
  6. 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.
  7. 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.


↑ Back to the top

More Information

Known issues with this update

  • When you install this update on a computer that is running WSUS and when the computer also hosts other Internet services such as HTTP, FTP, NNTP or SMTP, these services may be stopped and then restarted during the installation of the update.
  • This update does not support uninstallation. To remove this update, you must uninstall and then reinstall WSUS.

    If you want to remove this update, we recommend that you select the default option when you uninstall WSUS. The default option leaves the database and content on the system so that customized settings are preserved when WSUS is reinstalled.
  • After you install this update, there is no listing for the update in the Add or Remove Programs feature in Control Panel. To verify that the update was installed correctly, follow these steps:
    1. Open the following folder:

      %ProgramFiles%\Update Services\WebServices\ClientWebService\bin\
    2. Right-click the Microsoft.UpdateServices.WebServices.Client.Dll file, and then click Properties.
    3. Click the Version tab.
      • If the update was installed correctly, the file version is 3.1.6001.66.
      • If the update was installed incorrectly, the file version is 3.1.6001.65.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbentirenet, kbinfo, kbbug, kbexpertiseinter, kbmustloc, kbpubtypekc, kbsecreview, kbsecurity, kbsecvulnerability, kbsecadvisory, kb, kblangall

↑ Back to the top

Article Info
Article ID : 954960
Revision : 7
Created on : 9/7/2020
Published on : 9/8/2020
Exists online : False
Views : 105