Article ID: 954960 - View products that this article applies to.
Technical update: August 1, 2008Microsoft 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:
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:
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: 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: 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.
To resolve this issue on a server that is running WSUS 3.0 SP1
To resolve this issue on a server that is running WSUS 3.0 RTMDo one of the following:
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.
Known issues with this update
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.