|
| |||||||||
| Tags: 0x80244019, wsus 2, wsus 3 |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| clients not reporting status after updating WSUS 2 to WSUS 3.0
After i upgraded to WSUS 3.0, my client computers are no longer reporting status in WSUS. In console, they are all listed with yellow triangle and exclamation point. How can i fix that? Thank you! |
|
#2
| |||
| |||
| RE: clients not reporting status after updating WSUS 2 to WSUS 3.0 This is from "windows update.log": Windows Update Client failed to detect with error 0x80244019 Thank you! |
|
#3
| |||
| |||
|
An HTTP '404' error, suggesting that the clients are pointed to the wrong URL. Describe to me the complete background of this WSUS server, and how it came to be a WSUS 3.0 server. |
|
#4
| |||
| |||
| Re: clients not reporting status after updating WSUS 2 to WSUS 3.0
Thanks for reply, Lawrence > What else is installed on this server? > > The most likely cause is a defect in the clients' ability to access the > /selfupdate tree on the Default Web Site. Server is W2K3 DC, Backup Exec 11d with SQL express 2005, Symantec AV 10 with System Mgr, HP Sys. Mgmt. > > Exception message: The type > > 'Microsoft.UpdateServices.Internal.Global' is ambiguous: > > it could come from assembly > > 'C:\Program Files\Update\Services\WebServices > > \ClientWebService\bin\microsoft.updateservices.webservices.client.DLL' > > or from assembly > > 'C:\Program Files\Update > > Services\WebServices\ClientWebService\bin\clientws.DLL'. > This latter path ~\ClientWebService\bin\clientws.DLL is an invalid > reference. This is the WSUS 2.0 library. Certainly this reference > should > have been authoritatively resolved after a successful upgrade. I while back I forced out WSUS 2 but the reference is not in the registry. is it in a .net config file? I checked the file, and clientws.DLL is ver. 2 dated 5/26/2006! It must have been leftover. Can I fix this, or need to uninstall, delete 'C:\Program Files\Update Services\' and reinstall? Thanks again. |
|
#5
| |||
| |||
| Re: clients not reporting status after updating WSUS 2 to WSUS 3.0
I removed WSUS3, deleted c:\program files\update sevices , and deleted all clientws.DLL clientws.DLL ver.2 was in deep subfolder of: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\clientwebservice\21f2d155\... clientws.DLL ver.3 was in deep subfolder of: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\clientwebservice\48cba74c\... I reinstalled WSUS3 successfully. The console shows clients reporting with last date/time, but the updates show as installed/not applicable , or updates with no status. no clients show any updates needed, but they are not current. No clients show a yellow exclamation. I tried the client fix on a few- remove susclid reg entries, restart wuau. I think I have sufficient permissions on the server. Anything to check on server or clients? |
|
#6
| |||
| |||
| re; clients not reporting status after updating WSUS 2 to WSUS 3.0
All appears well. clients started reporting ater the client fix. Thank you all contributors. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "clients not reporting status after updating WSUS 2 to WSUS 3.0" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WSUS 3.0 clients not updating status | Brandon | Server Update Service | 6 | 23-03-2011 12:49 AM |
| Clients not reporting to WSUS server | Andrew Story | Server Update Service | 10 | 10-11-2009 09:35 PM |
| 1 Out Of 30+ Clients Not Reporting In WSUS - Error 8007007a | Gramps98 | Server Update Service | 6 | 08-07-2009 01:23 AM |
| WSUS 3.0 SP1: Vista Clients not reporting | Terry | Windows Update | 3 | 19-11-2008 11:29 PM |
| WSUS upgrade from 2.0 - 3.0 and now only some clients reporting | crazdt | Server Update Service | 21 | 16-08-2008 02:55 AM |