clients not reporting status after updating WSUS 2 to WSUS 3.0 Veronika 6/22/2007 9:20:00 PM 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!

RE: clients not reporting status after updating WSUS 2 to WSUS 3.0 Veronika 6/22/2007 9:34:01 PM This is from "windows update.log": Windows Update Client failed to detect with error 0x80244019 Thank you!

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/23/2007 12:20:51 AM "Veronika" <Veronika[ at ]discussions.microsoft.com> wrote in message news:578A9A03-5F98-4018-9E23-6CAB6BF335AC[ at ]microsoft.com... [Quoted Text] > > This is from "windows update.log": > Windows Update Client failed to detect with error 0x80244019 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. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 Veronika 6/23/2007 4:45:01 AM "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Veronika" <Veronika[ at ]discussions.microsoft.com> wrote in message > news:578A9A03-5F98-4018-9E23-6CAB6BF335AC[ at ]microsoft.com... > > > > This is from "windows update.log": > > Windows Update Client failed to detect with error 0x80244019 > > 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. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > Lawrence, It is a Windows 2k3 Server SE Service Pack 1. Server name: ENTITSUS01. It originally was a SUS server, then i upgraded to WSUS, then to WSUS 2, and then WSUS 3 now running on port 8530. The server has now problem syncronizing with MS Update service and gets all updates downloaded to it. Group policy for all clients sets WSUS server to: http://entitsus01:8530 I upgraded to WSUS 3 on 5/23. That is the last time all computers with yellow exclamation marks are showing they talked to the server (last reported status). Here are some lines from the most recent windowsupdate.log on my client machine: 2007-06-22 22:55:12:125 1148 9cc Misc = Process: C:\WINDOWS\System32\svchost.exe 2007-06-22 22:55:12:125 1148 9cc Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2007-06-22 22:55:12:046 1148 9cc Service ************* 2007-06-22 22:55:12:125 1148 9cc Service ** START ** Service: Service startup 2007-06-22 22:55:12:125 1148 9cc Service ********* 2007-06-22 22:55:13:531 1148 9cc Agent * WU client version 7.0.6000.374 2007-06-22 22:55:13:531 1148 9cc Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2007-06-22 22:55:13:562 1148 9cc Agent * Access type: No proxy 2007-06-22 22:55:13:562 1148 9cc Agent * Network state: Connected 2007-06-22 22:56:00:015 1148 9cc Agent *********** Agent: Initializing Windows Update Agent *********** 2007-06-22 22:56:00:015 1148 9cc Agent *********** Agent: Initializing global settings cache *********** 2007-06-22 22:56:00:015 1148 9cc Agent * WSUS server: http://entitsus01 2007-06-22 22:56:00:015 1148 9cc Agent * WSUS status server: http://entitsus01 2007-06-22 22:56:00:015 1148 9cc Agent * Target group: Charlotte 2007-06-22 22:56:00:015 1148 9cc Agent * Windows Update access disabled: No 2007-06-22 22:56:00:015 1148 9cc DnldMgr Download manager restoring 0 downloads 2007-06-22 22:56:00:031 1148 9cc AU ########### AU: Initializing Automatic Updates ########### 2007-06-22 22:56:00:031 1148 9cc AU # WSUS server: http://entitsus01 2007-06-22 22:56:00:031 1148 9cc AU # Detection frequency: 22 2007-06-22 22:56:00:031 1148 9cc AU # Target group: Charlotte 2007-06-22 22:56:00:031 1148 9cc AU # Approval type: Scheduled (Policy) 2007-06-22 22:56:00:031 1148 9cc AU # Scheduled install day/time: Saturday at 3:00 2007-06-22 22:56:00:031 1148 9cc AU # Auto-install minor updates: Yes (Policy) 2007-06-22 22:56:00:046 1148 9cc AU Setting AU scheduled install time to 2007-06-23 07:00:00 2007-06-22 22:56:00:046 1148 9cc Report *********** Report: Initializing static reporting data *********** 2007-06-22 22:56:00:046 1148 9cc Report * OS Version = 5.1.2600.2.0.65792 2007-06-22 22:56:00:750 1148 9cc Report * Computer Brand = Dell Inc. 2007-06-22 22:56:00:750 1148 9cc Report * Computer Model = Latitude D810 2007-06-22 22:56:00:765 1148 9cc Report * Bios Revision = A02 2007-06-22 22:56:00:765 1148 9cc Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A02 2007-06-22 22:56:00:765 1148 9cc Report * Bios Release Date = 2005-02-25T00:00:00 2007-06-22 22:56:00:765 1148 9cc Report * Locale ID = 1049 2007-06-22 22:56:00:984 1148 9cc AU AU finished delayed initialization 2007-06-22 22:56:00:984 1148 9cc AU ############# 2007-06-22 22:56:00:984 1148 9cc AU ## START ## AU: Search for updates 2007-06-22 22:56:00:984 1148 9cc AU ######### 2007-06-22 22:56:00:984 1148 9cc AU <<## SUBMITTED ## AU: Search for updates [CallId = {6EB19D5D-478A-476C-BFEF-3529762A908F}] 2007-06-22 22:56:02:437 1148 dd4 PT WARNING: Cached cookie has expired or new PID is available 2007-06-22 22:56:02:437 1148 dd4 PT Initializing simple targeting cookie, clientId = 78fbbc8b-f146-48f0-b015-29ced87f882d, target group = Charlotte, DNS name = vrobinsonltopxp.amcity.com 2007-06-22 22:56:02:437 1148 dd4 PT Server URL = http://entitsus01/SimpleAuthWebService/SimpleAuth.asmx 2007-06-22 22:56:15:812 1148 dd4 Misc WARNING: Send failed with hr = 80072ee7. 2007-06-22 22:56:15:812 1148 dd4 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2007-06-22 22:56:15:812 1148 dd4 PT + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0 2007-06-22 22:56:15:812 1148 dd4 PT + Caller provided credentials = No 2007-06-22 22:56:15:812 1148 dd4 PT + Impersonate flags = 0 2007-06-22 22:56:15:812 1148 dd4 PT + Possible authorization schemes used = 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: GetAuthorizationCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402c 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: PopulateAuthCookies failed: 0x8024402c 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: RefreshCookie failed: 0x8024402c 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: RefreshPTState failed: 0x8024402c 2007-06-22 22:56:15:812 1148 dd4 PT WARNING: PTError: 0x8024402c 2007-06-22 22:56:15:812 1148 dd4 Report WARNING: Reporter failed to upload events with hr = 8024402c. 2007-06-22 22:56:15:937 1148 dd4 PT WARNING: Cached cookie has expired or new PID is available 2007-06-22 22:56:15:937 1148 dd4 PT Initializing simple targeting cookie, clientId = 78fbbc8b-f146-48f0-b015-29ced87f882d, target group = Charlotte, DNS name = vrobinsonltopxp.amcity.com 2007-06-22 22:56:15:937 1148 dd4 PT Server URL = http://entitsus01/SimpleAuthWebService/SimpleAuth.asmx 2007-06-22 22:56:18:187 1148 dd4 Misc WARNING: Send failed with hr = 80072ee7. 2007-06-22 22:56:18:187 1148 dd4 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2007-06-22 22:56:18:187 1148 dd4 PT + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0 2007-06-22 22:56:18:187 1148 dd4 PT + Caller provided credentials = No 2007-06-22 22:56:18:187 1148 dd4 PT + Impersonate flags = 0 2007-06-22 22:56:18:187 1148 dd4 PT + Possible authorization schemes used = 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: GetAuthorizationCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402c 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: PopulateAuthCookies failed: 0x8024402c 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: RefreshCookie failed: 0x8024402c 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: RefreshPTState failed: 0x8024402c 2007-06-22 22:56:18:187 1148 dd4 PT WARNING: PTError: 0x8024402c 2007-06-22 22:56:18:187 1148 dd4 Report WARNING: Reporter failed to upload events with hr = 8024402c. Does this info shed more light on the issue? Thank you! - Veronika

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/23/2007 2:41:52 PM "Veronika" <Veronika[ at ]discussions.microsoft.com> wrote in message news:A66FCA54-2BBA-487F-A002-61FB73D2AB03[ at ]microsoft.com... [Quoted Text] >> > This is from "windows update.log": >> > Windows Update Client failed to detect with error 0x80244019 >> 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. > It is a Windows 2k3 Server SE Service Pack 1. Server name: ENTITSUS01. It > originally was a SUS server, then i upgraded to WSUS, then to WSUS 2, and > then WSUS 3 now running on port 8530 That's the answer I thought I might get. I'm currently working with the WSUS dev team to work out this quirk in the upgrade process from SUS 1.0 to WSUS 2.0 to WSUS 3.0. Essentially, as you note, the WSUS server got moved to port 8530 when you upgraded to WSUS 3.0. This is because the SUS-to-WSUS migration procedures had you stop the Default Web Site to disable SUS, and reset the WSUS v2 server to port 80. SUS 1.0 was never uninstalled. The Release Notes document that SUS 1.0 must not be present, but I think they're a bit inadequate in explaining the true nature of the situation for those who migrated from SUS to WSUS 2.0. The problem is that the WSUS 3.0 installer (a) can't use the Default Web Site because it stopped or (b) sees the SUS install on the Default Web Site (I'm not sure which exactly it is), so it 'upgrades' WSUS 2 on the alternate virtual server, starts the DWS (to support selfupdate on port 80), and resets the alternate virtual server to port 8530. > Group policy for all clients sets WSUS server to: http://entitsus01:8530 > I upgraded to WSUS 3 on 5/23. That is the last time all computers with > yellow exclamation marks are showing they talked to the server (last > reported > status). > Here are some lines from the most recent windowsupdate.log on my client > machine: > 2007-06-22 22:56:00:015 1148 9cc Agent * WSUS server: http://entitsus01 > 2007-06-22 22:56:00:015 1148 9cc Agent * WSUS status server: > http://entitsus01 We see here that your policy is not being correctly applied. The client is not addressed to the correct URL. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 dreamsplc <dreamsplc.2sqgng[ at ]DoNotSpam.com> 6/25/2007 11:37:27 AM After following the same SUS1 > WSUS2 > WSUS3 upgrade path, the WSUS server here has the same error message. However I note that the default website is on port 80 (thouh WSUS Administration is on 8530/8531). What I did not see on this thread was a fix. Is there a method for getting the clients to "GetAuthorizationCookie" again? I would be grateful for your help since I now have >600 unpatched clients. I post a copy of the WindowsUpdate.log 's most recent entries after using "wuauclt.exe /resetauthorization /detectnow" at the commandline of an XP SP2 client: 2007-06-25 11:29:12:484 1520 774 AU Triggering AU detection through DetectNow API 2007-06-25 11:29:12:484 1520 774 AU Triggering Online detection (non-interactive) 2007-06-25 11:29:12:484 1520 b90 AU ############# 2007-06-25 11:29:12:484 1520 b90 AU ## START ## AU: Search for updates 2007-06-25 11:29:12:484 1520 b90 AU ######### 2007-06-25 11:29:12:484 1520 b90 AU <<## SUBMITTED ## AU: Search for updates [CallId = {7179AA2E-5EF1-449D-8CB3-E347EAE4ECA2}] 2007-06-25 11:29:12:484 1520 5b4 Agent ************* 2007-06-25 11:29:12:484 1520 5b4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2007-06-25 11:29:12:484 1520 5b4 Agent ********* 2007-06-25 11:29:12:484 1520 5b4 Agent * Online = Yes; Ignore download priority = No 2007-06-25 11:29:12:484 1520 5b4 Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1" 2007-06-25 11:29:12:484 1520 5b4 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2007-06-25 11:29:12:484 1520 5b4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: 2007-06-25 11:29:12:500 1520 5b4 Misc Microsoft signed: Yes 2007-06-25 11:29:12:515 1520 5b4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: 2007-06-25 11:29:12:531 1520 5b4 Misc Microsoft signed: Yes 2007-06-25 11:29:12:593 1520 5b4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab: 2007-06-25 11:29:12:593 1520 5b4 Misc Microsoft signed: Yes 2007-06-25 11:29:12:656 1520 5b4 Setup *********** Setup: Checking whether self-update is required *********** 2007-06-25 11:29:12:656 1520 5b4 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf 2007-06-25 11:29:12:671 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:671 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:671 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:671 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:687 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:703 1520 5b4 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-06-25 11:29:12:703 1520 5b4 Setup * IsUpdateRequired = No 2007-06-25 11:29:17:828 1520 5b4 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2007-06-25 11:29:17:828 1520 5b4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://SUS/ClientWebService/client.asmx 2007-06-25 11:29:18:234 1520 5b4 PT WARNING: Cached cookie has expired or new PID is available 2007-06-25 11:29:18:234 1520 5b4 PT Initializing simple targeting cookie, clientId = 79d9dc4b-7855-4fee-baa3-3c04db4d3e69, target group = Managed XP Desktops, DNS name = hw95.dreamsplc.com 2007-06-25 11:29:18:234 1520 5b4 PT Server URL = http://SUS/SimpleAuthWebService/SimpleAuth.asmx 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: PopulateAuthCookies failed: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: RefreshCookie failed: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: RefreshPTState failed: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: Sync of Updates: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019 2007-06-25 11:29:18:250 1520 5b4 Agent * WARNING: Failed to synchronize, error = 0x80244019 2007-06-25 11:29:18:343 1520 5b4 Agent * WARNING: Exit code = 0x80244019 2007-06-25 11:29:18:343 1520 5b4 Agent ********* 2007-06-25 11:29:18:343 1520 5b4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2007-06-25 11:29:18:343 1520 5b4 Agent ************* 2007-06-25 11:29:18:343 1520 5b4 Agent WARNING: WU client failed Searching for update with error 0x80244019 2007-06-25 11:29:18:359 1520 be0 AU >>## RESUMED ## AU: Search for updates [CallId = {7179AA2E-5EF1-449D-8CB3-E347EAE4ECA2}] 2007-06-25 11:29:18:359 1520 be0 AU # WARNING: Search callback failed, result = 0x80244019 2007-06-25 11:29:18:359 1520 be0 AU # WARNING: Failed to find updates with error code 80244019 2007-06-25 11:29:18:359 1520 be0 AU ######### 2007-06-25 11:29:18:359 1520 be0 AU ## END ## AU: Search for updates [CallId = {7179AA2E-5EF1-449D-8CB3-E347EAE4ECA2}] 2007-06-25 11:29:18:359 1520 be0 AU ############# 2007-06-25 11:29:18:359 1520 be0 AU AU setting next detection timeout to 2007-06-25 15:29:18 2007-06-25 11:29:18:359 1520 be0 AU Setting AU scheduled install time to 2007-06-26 02:00:00 2007-06-25 11:29:23:343 1520 5b4 Report REPORT EVENT: {E193D248-D542-47E0-8734-F1EDBA8963B3} 2007-06-25 11:29:18:343+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019. -- dreamsplc ------------------------------------------------------------------------ dreamsplc's Profile: http://forums.techarena.in/member.php?userid=27111 View this thread: http://forums.techarena.in/showthread.php?t=771044 http://forums.techarena.in

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 setca <setca.2squjg[ at ]DoNotSpam.com> 6/25/2007 5:05:53 PM I have the same problem, deleted reg keys on client PC for susclientid,restart update service, > wuauclient /resetauth /detectnow etc..... PT +++++++++++ PT: Synchronizing server updates +++++++++++ :601 1084 c34 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://gen2k3/ClientWebService/client.asmx :632 1084 c34 PT WARNING: Cached cookie has expired or new PID is available :632 1084 c34 PT Initializing simple targeting cookie, clientId = a9f8099a-17bf-4c80-9c5b-c6d055a9604a, target group = genComp, DNS name = chris-xp.k.ca :632 1084 c34 PT Server URL = http://g2k3/SimpleAuthWebService/SimpleAuth.asmx :051 1084 c34 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200 :051 1084 c34 PT WARNING: PTError: 0x80244008 :051 1084 c34 PT WARNING: GetCookie_WithRecovery failed : 0x80244008 :051 1084 c34 PT WARNING: RefreshCookie failed: 0x80244008 :051 1084 c34 PT WARNING: RefreshPTState failed: 0x80244008 :051 1084 c34 PT WARNING: Sync of Updates: 0x80244008 :051 1084 c34 PT WARNING: SyncServerUpdatesInternal failed: 0x80244008 :051 1084 c34 Agent * WARNING: Failed to synchronize, error = 0x80244008 :051 1084 c34 Agent * WARNING: Exit code = 0x80244008 :051 1084 c34 Agent ********* :051 1084 c34 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] :051 1084 c34 Agent ************* :051 1084 c34 Agent WARNING: WU client failed Searching for update with error 0x80244008 :051 1084 5c8 AU >>## RESUMED ## AU: Search for updates [CallId = {598D92DD-0F7E-4E39-BEB1-C3ECA7724BDC}] :051 1084 5c8 AU # WARNING: Search callback failed, result = 0x80244008 :051 1084 5c8 AU # WARNING: Failed to find updates with error code 80244008 :051 1084 5c8 AU ######### :051 1084 5c8 AU ## END ## AU: Search for updates [CallId = {598D92DD-0F7E-4E39-BEB1-C3ECA7724BDC}] :051 1084 5c8 AU ############# :051 1084 5c8 AU AU setting next detection timeout to 2007-06-25 18:15:55 :051 1084 5c8 AU Setting AU scheduled install time to 2007-06-25 20:00:00 :019 1084 c34 Report REPORT EVENT: {4A29E422-8742-4318-A7E2-904054734971} :051 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244008 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244008. .... -- setca ------------------------------------------------------------------------ setca's Profile: http://forums.techarena.in/member.php?userid=27126 View this thread: http://forums.techarena.in/showthread.php?t=771044 http://forums.techarena.in

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 dreamsplc <dreamsplc.2sse3g[ at ]DoNotSpam.com> 6/26/2007 1:02:59 PM Thanks for the reply, however my problem is different: Your log reports: 051 1084 c34 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200 whereas my log reports: 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404 My clients cannot even see the objects on the virtual directory (hence the 404 error/status code) Your problem may be fixed with the following script: :-------------------------- reg delete \\%computername%\HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f wuauclt.exe /resetauthorization /detectnow net stop wuauserv net start wuauserv :-------------------------- edit: please note when I posted this it seemed to add a space into the reg key, you will need to remove. According to Lawrence Garvin (the MVP in this thread), I should uninstall/ whilst preserving the database. Regards to all. -- dreamsplc ------------------------------------------------------------------------ dreamsplc's Profile: http://forums.techarena.in/member.php?userid=27111 View this thread: http://forums.techarena.in/showthread.php?t=771044 http://forums.techarena.in

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 ak47m92fglock18[ at ]yahoo.co.jp 6/27/2007 6:12:11 AM [Quoted Text] > > 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: GetAuthorizationCookie > failure, error = 0x80244019, soap client error = 10, soap error code = > 0, HTTP status code = 404 I fixed this ploblem. WSUS installer changed the wsus TCP port 8530. place back 80 in IIS service manager. Then MMC reconnect the server. Hiroshima Japan. hope help this.

Re: clients not reporting status after updating WSUS 2 to WSUS 3.0 ak47m92fglock18[ at ]yahoo.co.jp 6/27/2007 6:16:38 AM [Quoted Text] > 2007-06-25 11:29:18:250 1520 5b4 PT WARNING: GetAuthorizationCookie > failure, error = 0x80244019, soap client error = 10, soap error code = > 0, HTTP status code = 404 I fixed this ploblem. WSUS installer changed the wsus TCP port 8530. place back 80 in IIS service manager. Then MMC reconnect the server. Hiroshima Japan. hope help this.