Client Error 8024400E when trying to sync to WSUS 3.1 (SP1)
- Hi,
I recently have found that one of my clients (Windows 2003 Server SP2, which is a member server) has stopped reporting in to the WSUS server. I checked the windowsupdate.log and found that the dreaded 8024400E error has occured.
So far I have:-
i) Renamed the softwareupdates folder (after stopping and starting the update service) - No fix
ii) Deleted the HKLM registry key and run the resetauthorization switch on wuauclt. - No Fix
iii) Downgraded the WU agent to version 2 and then let it update manually. - No Fix.
I am now at a loss as to how to fix this. Anyone got any ideas as I would rather not rebuild this machine to make this work.
PS. It will connect to the Internet correctly and download and patch the machine, so that portion of the system works.
Nathan.
Answers
- I contacted Microsoft about this issue last week. And this is the solution they came with:
Perform the following steps:
a. First make sure the update is declined. If the update is not yet declined, right click on the update and decline it.
b. Next, approve the update.Right click on the update and select the ‘Approve…’ option in the context menu. In the ‘Approve Updates’ dialog that opens, just click ‘OK’. Dismiss the ‘Approval Progress’ dialog that appears.
c. Next, decline the update. Right click on the update and select the ‘Approve…’ option in the context menu. In the ‘Approve Updates’ dialog that opens, just click ‘OK’. Dismiss the ‘Approval Progress’ dialog that appears.
I tried it, and now the server starts reporting.- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorWednesday, June 25, 2008 9:36 AM
All Replies
- Just letting you know, I have the same problem over here. Please let me know if you have a solution. I tried several thing:
- Installing the Windows Update Agent manually
- Stop "Automatic Updates" service, delete the content of c:\windows\softwaredistribution, delete SusID from registry, start "Automatic Updates"
Problem still exist, unfortunatly. - I contacted Microsoft about this issue last week. And this is the solution they came with:
Perform the following steps:
a. First make sure the update is declined. If the update is not yet declined, right click on the update and decline it.
b. Next, approve the update.Right click on the update and select the ‘Approve…’ option in the context menu. In the ‘Approve Updates’ dialog that opens, just click ‘OK’. Dismiss the ‘Approval Progress’ dialog that appears.
c. Next, decline the update. Right click on the update and select the ‘Approve…’ option in the context menu. In the ‘Approve Updates’ dialog that opens, just click ‘OK’. Dismiss the ‘Approval Progress’ dialog that appears.
I tried it, and now the server starts reporting.- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorWednesday, June 25, 2008 9:36 AM
- Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
--------------------
Regards,
Eric Zhang
