Help and Support
 

powered byLive Search

Some computers do not receive updates from the WSUS server

View products that this article applies to.
Article ID:954960
Last Review:August 12, 2008
Revision:5.0

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 (http://www.microsoft.com/technet/security/advisory/954960.mspx)
On This Page

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.

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.

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 problem on a server that is running WSUS 3.0 SP1, install update 954960.

Note If you are using the RTM version of WSUS 3.0, refer to the workaround in the "Workaround" section to resolve this issue. If you use the RTM version of WSUS 3.0 and if you decide not to implement the workaround, visit the following Microsoft Web site for more information about how to upgrade to WSUS 3.0 SP1:
http://go.microsoft.com/fwlink/?linkid=93750 (http://go.microsoft.com/fwlink/?linkid=93750)
The following files are available for download from the Microsoft Download Center:

DownloadDownload the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 (KB954960) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=6AA8A49D-170C-4077-8B9B-61F7BF5A1281)
DownloadDownload the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 for x64-based Systems (KB954960) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=DBDCDB25-1097-47F4-8FD1-B1246D13C5F8)

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 (http://support.microsoft.com/kb/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.

Back to the top

WORKAROUND

To resolve this problem, we recommend that you install update 954960. However, to work around this problem if you cannot install update 954960, reset the approvals to a consistent state on the WSUS server. To do this, follow these steps on the WSUS Administration Console:
1.In the updates list, locate the Office 2003 Service Pack 1 update.

Note Because a new version of this update may be published in the future, it is important to verify that you have the correct version installed. To do this, make sure 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.Make sure that the update is already declined. If the update is not already declined, right-click the update, and then click Decline.
3.Cause the update not to be declined. 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.
After you follow these steps, computers on which detection was unsuccessful now successfully complete detection against the WSUS server, and the computers receive any applicable updates. To verify that the computer is now able to synchronize, open a command prompt, type the following command, and then press ENTER:
wuauclt.exe/detectnow
Then, examine the WindowsUpdate.log file to verify that the synchronization is successful. You may have to run detection two times. This is because some customers have reported that the first synchronization fails but that successive synchronizations succeed.

Note If you have a hierarchy of WSUS servers, you must follow these steps on each server. Start with the top-level server. If one of the servers is a replica child server, you must first change it to be autonomous. Follow the previous steps, and then change the autonomous server back to a replica child server. You can do this in the Options/Update Source and Proxy Server dialog box.

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

APPLIES TO
•Windows Server Update Services 3.0
•Windows Server Update Services 3.0 Service Pack 1

Back to the top

Keywords: 
kbinfo kbbug kbexpertiseinter kbpubtypekc kbsecurity kbsecvulnerability kbsecadvisory KB954960

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Need More Help?
    Contact a Support professional by E-mail, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.