The client cannot obtain an update error from the WSUS server.

Recently, I checked the running status of the WSUS server and found that two computers are still in the "not reported" status. Because these two computers are far away from each other, therefore, the information cannot be seen from the log file, and the log on the WSUS server is too complex, so it gives up. However, this problem also occurs on a computer in my house two days ago. So I checked windowsupdate. log in the windows directory and found the following error during update Detection:

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

No matter how you configure the server or use the wuauclt command on the client to clear the database or change the settings, this problem still exists. No way, you can only seek help from the omnipotent googlebaidu, because no one in China has reported this problem), and finally found the relevant content on the Microsoft WSUS Team Blog. Originally, this problem was caused by the installation of Office 2003 or components related to Office 2003 on the client computer. This problem is not all, but may occur on some computers. Follow the solution described in WSUS Team Blog-find the update for Office 2003 SP1, change the status from "deny" to "allow", and then "deny" again. However, I cannot change from "deny" to "allow ". Even more strange, the update date of the Office 2003 SP1 file is June 11, 3008. No way, you can only uninstall Office 2003 first, and then run wuauclt/detectnow to locate the problem. But what should I do with Office 2003? Later, I found an Office 2003 without any patch and installed it so that it could automatically obtain the SP3 patch from the WSUS server. After the patch is completed, everything is normal and I can freely receive updates.

Today, I happened to think about this problem. So I went to Microsoft's website and found that Microsoft released the KB954960 patch for WSUS 3.0 SP1 today, which corrected the above error. So download the package and report an error during installation, indicating that the version is incorrect. Take a closer look at the updated description file and find that the required version is WSUS 3.0 SP1, and the version I use is WSUS 3.0. Download the SP1 Patch in a hurry. The speed is good. It is 350 k/s. After installing the SP1 Patch, the system will automatically uninstall WSUS 3.0 and install WSUS 3.0 SP1.) then, call the KB954960 patch, OK. According to Microsoft's method, the version of the patched file has changed to 3.1.6001.66, while the versions of other files are 3.1.6001.65. The patch takes effect.

After completing the patch, I will try again later. The two computers in the "not reported" status can now report the status normally and obtain updates freely.