WSUS Support Forums: Failed to Synchronize Error 0x8024400E - WSUS Support Forums

Jump to content

  • (2 Pages)
  • +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

Failed to Synchronize Error 0x8024400E

#1 User is offline   tesham 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 09-Jun-08

Posted 09 Jun 2008, 08:14

We have been using WSUS 3 with all updates and SPs for a long time. Recently 27 systems stopped reporting their status and show their status as not reported yet. All have the following excerpt from their WindowsUpdate log. I have tried to delete the softwaredistribution folder as well as the windowsupdate log to no avail. Any help would be greatly appreciated.

Thanks, Terri

Excerpt from log....

WARNING: WU client failed Searching for update with error 0x8024400e
2008-06-09 10:44:36:171 1028 a84 AU >>## RESUMED ## AU: Search for updates [CallId = {4E22BC21-2259-4CC1-939B-AE79D6823657}]
2008-06-09 10:44:36:171 1028 a84 AU # WARNING: Search callback failed, result = 0x8024400E
2008-06-09 10:44:36:171 1028 a84 AU # WARNING: Failed to find updates with error code 8024400E
2008-06-09 10:44:36:171 1028 a84 AU #########
2008-06-09 10:44:36:171 1028 a84 AU ## END ## AU: Search for updates [CallId = {4E22BC21-2259-4CC1-939B-AE79D6823657}]
2008-06-09 10:44:36:171 1028 a84 AU #############
2008-06-09 10:44:36:187 1028 a84 AU AU setting next detection timeout to 2008-06-09 16:44:36
2008-06-09 10:44:36:187 1028 a84 AU Setting AU scheduled install time to 2008-06-10 06:00:00
2008-06-09 10:44:41:171 1028 278 Report REPORT EVENT: {A1BA0EE4-1BBE-4EA6-9AF1-45A08082FDDD} 2008-06-09 10:44:36:171-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400e.
2008-06-09 10:45:04:156 1028 214 AU AU received policy change subscription event
2008-06-09 10:53:37:221 1028 278 PT WARNING: Cached cookie has expired or new PID is available
2008-06-09 10:53:37:237 1028 278 PT Initializing simple targeting cookie, clientId = 52069dc3-e3bc-476c-9b67-a2286759b44e, target group = , DNS name = swise.ncdc.noaa.gov
2008-06-09 10:53:37:237 1028 278 PT Server URL = http://192.67.134.67...SimpleAuth.asmx
2008-06-09 10:53:37:268 1028 278 Report Uploading 1 events using cached cookie, reporting URL = http://192.67.134.67...WebService.asmx
2008-06-09 10:53:37:300 1028 278 Report Reporter successfully uploaded 1 events.
0

#2 User is offline   DavidGayler 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 37
  • Joined: 30-Mar-07

Posted 09 Jun 2008, 15:48

Have a look at the Update Servers softwaredistribution.log and post it here.
0

#3 User is offline   groovyf 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 290
  • Joined: 05-Feb-04

Posted 17 Jun 2008, 05:10

I've just got this error on a newly setup PC (from a cloned image - I have a rigorous process for creating images to make sure duplicates aren't created, and been using this process faultlessly for 3+ years)
PC was XP SP2 and not on the domain. I upgraded it to SP3 via a local install, then once done, went to Windows Update to install any additional updates.

Added the PC to the domain, whereupon it picked up my Group Policy for WSUS, and promptly failed to do anything. Not had any problems with XP SP2 PCs, nor any issues with PCs that had previously reported into WSUS and now been upgraded to SP3 via a local install. These XP SP3 PCs are reporting normally.

However, this new PC (new to domain and WSUS) isn't playing ball at all. ClientDiags passes on all
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy
10.223.251.144:8080
User IE ProxyByPass<
local>
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://wsus-01
WUStatusServer = http://wsus-01
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS


Any ideas?


2008-06-17 12:59:18:483 1044 984 AU Triggering AU detection through DetectNow API
2008-06-17 12:59:18:483 1044 984 AU Triggering Online detection (non-interactive)
2008-06-17 12:59:18:483 1044 72c AU #############
2008-06-17 12:59:18:483 1044 72c AU ## START ## AU: Search for updates
2008-06-17 12:59:18:483 1044 72c AU #########
2008-06-17 12:59:18:483 1044 72c AU <<## SUBMITTED ## AU: Search for updates [CallId = {2284ADC4-7D04-4C96-BC35-3C3055F3FBE9}]
2008-06-17 12:59:18:483 1044 afc Agent *************
2008-06-17 12:59:18:483 1044 afc Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-17 12:59:18:483 1044 afc Agent *********
2008-06-17 12:59:18:483 1044 afc Agent * Online = Yes; Ignore download priority = No
2008-06-17 12:59:18:483 1044 afc 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"
2008-06-17 12:59:18:483 1044 afc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-17 12:59:18:483 1044 afc Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-17 12:59:18:499 1044 afc Misc Microsoft signed: Yes
2008-06-17 12:59:18:499 1044 afc Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-17 12:59:18:499 1044 afc Misc Microsoft signed: Yes
2008-06-17 12:59:18:530 1044 afc Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-17 12:59:18:545 1044 afc Misc Microsoft signed: Yes
2008-06-17 12:59:18:545 1044 afc Setup *********** Setup: Checking whether self-update is required ***********
2008-06-17 12:59:18:545 1044 afc Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-17 12:59:18:545 1044 afc Setup * IsUpdateRequired = No
2008-06-17 12:59:18:686 1044 afc PT +++++++++++ PT: Synchronizing server updates +++++++++++
2008-06-17 12:59:18:686 1044 afc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ukmy-wsus-01/...ice/client.asmx
2008-06-17 12:59:19:139 1044 afc PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2008-06-17 12:59:19:139 1044 afc PT WARNING: SOAP Fault: 0x000190
2008-06-17 12:59:19:139 1044 afc PT WARNING: faultstring:Fault occurred
2008-06-17 12:59:19:139 1044 afc PT WARNING: ErrorCode:InternalServerError(5)
2008-06-17 12:59:19:139 1044 afc PT WARNING: Message:(null)
2008-06-17 12:59:19:139 1044 afc PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-17 12:59:19:139 1044 afc PT WARNING: ID:a54769af-713a-43f3-a8d1-4cc2caaf8a1d
2008-06-17 12:59:19:139 1044 afc PT WARNING: PTError: 0x8024400e
2008-06-17 12:59:19:139 1044 afc PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e
2008-06-17 12:59:19:139 1044 afc PT WARNING: Sync of Updates: 0x8024400e
2008-06-17 12:59:19:139 1044 afc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
2008-06-17 12:59:19:139 1044 afc Agent * WARNING: Failed to synchronize, error = 0x8024400E
2008-06-17 12:59:19:139 1044 afc Agent * WARNING: Exit code = 0x8024400E
2008-06-17 12:59:19:139 1044 afc Agent *********
2008-06-17 12:59:19:139 1044 afc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-17 12:59:19:139 1044 afc Agent *************
2008-06-17 12:59:19:139 1044 afc Agent WARNING: WU client failed Searching for update with error 0x8024400e
2008-06-17 12:59:19:139 1044 2f4 AU >>## RESUMED ## AU: Search for updates [CallId = {2284ADC4-7D04-4C96-BC35-3C3055F3FBE9}]
2008-06-17 12:59:19:139 1044 2f4 AU # WARNING: Search callback failed, result = 0x8024400E
2008-06-17 12:59:19:139 1044 2f4 AU # WARNING: Failed to find updates with error code 8024400E
Cloned PCs not appearing in WSUS? Missing client PCs? Read this thread!
0

#4 User is offline   groovyf 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 290
  • Joined: 05-Feb-04

Posted 17 Jun 2008, 05:49

A quick check in softwaredistribution.log on the WSUS server reveals:

### Item has already been added. Key in dictionary: '9181' Key being added: '9181'
Cloned PCs not appearing in WSUS? Missing client PCs? Read this thread!
0

#5 User is offline   mendocinosunrise 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 18-Jun-08

Post icon  Posted 18 Jun 2008, 14:47

I fought with the same error, then gave up & emailed MS.
NOTE: the workaround below didn't work at first because the problem update was expired. However, I ran through the steps a couple of times & then manually resynchronized the WSUS server. After that, clients started synchronizing correctly.

Here's their workaround from the MS tech:
Thank you for the log. The error you see repeated in the log, 0x8024400E, is consistent with an issue that has been appearing recently. I've posted some root cause information and steps to resolve below. Please review the information and apply the workaround. This is a new problem, so a KB article has not yet been released.

<snip>

" Root Cause:
A recent revision to the 'Office 2003 Service Pack 1' update has resulted in some WSUS 3.0 servers syncing that revision to enter an inconsistent state with respect to the update's approvals. When computers with products related to Office 2003 talk to such a server, the web service is unable to process the approvals resulting in the detection failure.

Workaround:
In order to reset the approvals to a consistent state on the WSUS server, follow these steps from the WSUS Administration Console
1. Find the 'Office 2003 Service Pack 1' update in the updates list. This may involve changing the Approval and Status filters in the update UI (set the Status to "Any" and the Approval to "Declined" - if you don't see it then set the Approval to "Any except Declined"
2. Perform the following steps:
a. First make sure the update is declined.
i. If the update is not yet declined, right click on the update and decline it.
b. Next, approve the update.
i. Right click on the update and select the 'Approve...' option in the context menu.
ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the 'Approval Progress' dialog that appears.
c. Next, decline the update.
i. Right click on the update and select the 'Approve...' option in the context menu.
ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the 'Approval Progress' dialog that appears.

The computers that were failing detection will now successfully complete detection against the server and receive any applicable updates.

Note: If you have a hierarchy of WSUS servers, these steps must be performed on each server, starting with the top-level server. If one of the servers is a replica child, one must first change it to be autonomous, then perform the steps above, then change it back to being a replica. This can be done from the Options/Update Source and Proxy Server Dialog."
0

#6 User is offline   groovyf 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 290
  • Joined: 05-Feb-04

Posted 18 Jun 2008, 15:36

I'd read on another forum that someone had figured out/been told it was something to do with Office, but nothing as specific as your info, mendocinosunrise

I was going to have another crack at things tomorrow before getting in touch with our MS contact, but shall instead go through your provided steps.
Thanks in advance should it work!
Cloned PCs not appearing in WSUS? Missing client PCs? Read this thread!
0

#7 User is offline   MadsBen 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 23-Jun-08

Posted 23 Jun 2008, 04:01

View Postmendocinosunrise, on Wed 18th Jun 2008, 11:47 pm, said:

I fought with the same error, then gave up & emailed MS.
NOTE: the workaround below didn't work at first because the problem update was expired. However, I ran through the steps a couple of times & then manually resynchronized the WSUS server. After that, clients started synchronizing correctly.

Here's their workaround from the MS tech:
Thank you for the log. The error you see repeated in the log, 0x8024400E, is consistent with an issue that has been appearing recently. I've posted some root cause information and steps to resolve below. Please review the information and apply the workaround. This is a new problem, so a KB article has not yet been released.

<snip>

" Root Cause:
A recent revision to the 'Office 2003 Service Pack 1' update has resulted in some WSUS 3.0 servers syncing that revision to enter an inconsistent state with respect to the update's approvals. When computers with products related to Office 2003 talk to such a server, the web service is unable to process the approvals resulting in the detection failure.

Workaround:
In order to reset the approvals to a consistent state on the WSUS server, follow these steps from the WSUS Administration Console
1. Find the 'Office 2003 Service Pack 1' update in the updates list. This may involve changing the Approval and Status filters in the update UI (set the Status to "Any" and the Approval to "Declined" - if you don't see it then set the Approval to "Any except Declined"
2. Perform the following steps:
a. First make sure the update is declined.
i. If the update is not yet declined, right click on the update and decline it.
b. Next, approve the update.
i. Right click on the update and select the 'Approve...' option in the context menu.
ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the 'Approval Progress' dialog that appears.
c. Next, decline the update.
i. Right click on the update and select the 'Approve...' option in the context menu.
ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the 'Approval Progress' dialog that appears.

The computers that were failing detection will now successfully complete detection against the server and receive any applicable updates.

Note: If you have a hierarchy of WSUS servers, these steps must be performed on each server, starting with the top-level server. If one of the servers is a replica child, one must first change it to be autonomous, then perform the steps above, then change it back to being a replica. This can be done from the Options/Update Source and Proxy Server Dialog."


Thanks! This problem has been bothering me for some days now.
it worked, although the guide is not 100% correct. If it is declined, you cannot Approve the Office 2003 Service Pack 1 because it is experied. You have to set it to Not approved and you have to do it manually for each computer group. Then you can decline it and run a "wuauclt /detectnow" on the clients.
0

#8 User is offline   milkmantep 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 5
  • Joined: 11-Jun-08

Posted 01 Jul 2008, 10:00

I just want to second MadsBen's post above. This fix worked brilliantly! Special thanks to mendocinosunrise for biting the bullet for all of us!
0

#9 User is offline   jpblazek 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 2
  • Joined: 02-Jun-08

Posted 01 Jul 2008, 14:10

The firm I work for also had the same issue. The fix above is exactly what I got from MS. The problem had to do with the Office 2003 Sp1 Update metadata being corrupt. Once you change the approval it changes the metadata and all my machines reported status. This is what I got from MS.

Root Cause:

A recent revision to the ‘Office 2003 Service Pack 1’ update has resulted in some WSUS 3.0 servers syncing

the revised update to enter an inconsistent state with respect to the update’s approvals. When computers with products related to Office 2003 communicate with such a server, the Web service is unable to process the approvals resulting in the detection failure.

Workaround:

In order to reset the approvals to a consistent state on the WSUS server, follow these steps from the WSUS Administration Console:

1. Find the Office 2003 Service Pack 1 update in the updates list, UpdateID: D359F493-0AAD-43FA-AF5C-6763326CD98F. This may involve changing the Status and Approval filters. Set Status to Any and Approval to Declined; if you still do not see the update, set Approval to Any Except Declined.

2. Perform the following steps:

a. Ensure the update is already declined.

i. If the update is not already declined, right-click on the update and then click Decline in the shortcuts menu.

b. Cause the update not to be declined.

i. Right-click the update and then click Approve in the shortcuts menu.

ii. In the Approve Updates dialog that opens, just click OK without making any changes to the approval settings.

c. Decline the update.

i. Right-click the update and then click Approve in the shortcuts menu.

ii. In the Approve Updates dialog that opens, just click OK. Dismiss the Approval Progress dialog that appears.



The computers that were failing detection will now successfully complete detection against the server and receive any applicable updates.



Note: If you have a hierarchy of WSUS servers, these steps must be performed on each server, starting with the top-level server. If one of the servers is a replica child, one must first change it to be autonomous, then perform the steps above, then change it back to being a replica. This can be done from the Options/Update Source and Proxy Server dialog box.
0

#10 User is offline   Ketter 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 02-Jul-08

Posted 02 Jul 2008, 08:16

So ultimately you want it to be approved or declined? It won't approve for me as it is superseded by SP2 and 3. Forgive me. I'm a Newbie.

This post has been edited by Ketter: 02 Jul 2008, 08:17

Thanks,
Ketter
0

#11 User is offline   AlanK 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 5
  • Joined: 16-Jun-06

Posted 02 Jul 2008, 10:38

View PostKetter, on Wed 2nd Jul 2008, 10:16 am, said:

So ultimately you want it to be approved or declined? It won't approve for me as it is superseded by SP2 and 3. Forgive me. I'm a Newbie.

The same fix worked for me.

1. Find the update. Decline it.
2. Select Approve, click All Computers and select "Approve for Install", but don't click OK.
3. Click All Computers again and change selection to "Not Approved", Click OK.
4. Dismiss the approval message.
5. Decline the update.
0

#12 User is offline   Ketter 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 02-Jul-08

Posted 03 Jul 2008, 08:38

View PostAlanK, on Wed 2nd Jul 2008, 01:38 pm, said:

View PostKetter, on Wed 2nd Jul 2008, 10:16 am, said:

So ultimately you want it to be approved or declined? It won't approve for me as it is superseded by SP2 and 3. Forgive me. I'm a Newbie.

The same fix worked for me.

1. Find the update. Decline it.
2. Select Approve, click All Computers and select "Approve for Install", but don't click OK.
3. Click All Computers again and change selection to "Not Approved", Click OK.
4. Dismiss the approval message.
5. Decline the update.



Yep. It worked. That's insane.
Thanks,
Ketter
0

#13 User is offline   Ketter 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 02-Jul-08

Posted 03 Jul 2008, 08:39

View PostAlanK, on Wed 2nd Jul 2008, 01:38 pm, said:

View PostKetter, on Wed 2nd Jul 2008, 10:16 am, said:

So ultimately you want it to be approved or declined? It won't approve for me as it is superseded by SP2 and 3. Forgive me. I'm a Newbie.

The same fix worked for me.

1. Find the update. Decline it.
2. Select Approve, click All Computers and select "Approve for Install", but don't click OK.
3. Click All Computers again and change selection to "Not Approved", Click OK.
4. Dismiss the approval message.
5. Decline the update.



That's craziness. It worked though. Thanks everyone.
Thanks,
Ketter
0

#14 User is offline   milkmantep 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 5
  • Joined: 11-Jun-08

Posted 08 Jul 2008, 05:27

FYI, Microsoft has now released an official bulletin about this:
http://www.microsoft...ory/954960.mspx
0

#15 User is offline   kane77573 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 5
  • Joined: 25-Jun-08

Posted 22 Jul 2008, 09:51

Worked for me also
Thanks
0

#16 User is offline   MaryC 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 08-Aug-08

Post icon  Posted 08 Aug 2008, 05:53

View Postkane77573, on Tue 22nd Jul 2008, 11:51 am, said:

Worked for me also
Thanks

Hi.. i have 26 clients that have quit reporting. I no longer have SP1 available to me to decline since it has expired. I have done the MS KB article ..no dice. now what? what do you do when SP1 is no longer available on the WSUS server for you to decline??
0

#17 User is offline   wsushatesme 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 2
  • Joined: 21-Dec-08

Posted 21 Dec 2008, 13:39

I am beside myself that this actually worked... I've been searching this problem now for a while and figured I would give this a try and boom, good to go, all clients are reporting.
0

#18 User is offline   wuzzle 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 21-Dec-08

Posted 22 Dec 2008, 11:09

Hello

I am having the same issue as the poster. I ran clientdiag



WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://updateserver.domain.name
WUStatusServer = http://updateserver.domain.name
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

VerifyWUServerURL() failed with hr=0x80190193

No Error description could be found

Press Enter to Complete

Here is my windowsupdate.log

2008-12-21 17:46:39:508 1104 5f4 AU Triggering AU detection through DetectNow API
2008-12-21 17:46:39:508 1104 5f4 AU Triggering Online detection (non-interactive)
2008-12-21 17:46:39:524 1104 208 AU #############
2008-12-21 17:46:39:524 1104 208 AU ## START ## AU: Search for updates
2008-12-21 17:46:39:524 1104 208 AU #########
2008-12-21 17:46:39:524 1104 208 AU <<## SUBMITTED ## AU: Search for updates [CallId = {42E90CCE-5F8C-46FC-89D9-6D1975ADB22D}]
2008-12-21 17:46:39:524 1104 a8c Agent *************
2008-12-21 17:46:39:524 1104 a8c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-12-21 17:46:39:524 1104 a8c Agent *********
2008-12-21 17:46:39:524 1104 a8c Agent * Online = Yes; Ignore download priority = No
2008-12-21 17:46:39:524 1104 a8c 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"
2008-12-21 17:46:39:524 1104 a8c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-12-21 17:46:39:524 1104 a8c Agent * Search Scope = {Machine}
2008-12-21 17:46:39:524 1104 a8c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-12-21 17:46:39:539 1104 a8c Misc Microsoft signed: Yes
2008-12-21 17:46:39:555 1104 a8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-12-21 17:46:39:555 1104 a8c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-12-21 17:46:39:555 1104 a8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-12-21 17:46:39:555 1104 a8c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-12-21 17:46:39:570 1104 a8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-12-21 17:46:39:570 1104 a8c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-12-21 17:46:39:570 1104 a8c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-12-21 17:46:39:570 1104 a8c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-12-21 17:46:39:570 1104 a8c Misc WARNING: DownloadFileInternal failed for http://updateserver....te/wuident.cab: error 0x80190193
2008-12-21 17:46:39:570 1104 a8c Setup FATAL: IsUpdateRequired failed with error 0x80244018
2008-12-21 17:46:39:570 1104 a8c Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80244018
2008-12-21 17:46:39:570 1104 a8c Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80244018
2008-12-21 17:46:39:570 1104 a8c Agent * WARNING: Skipping scan, self-update check returned 0x80244018
2008-12-21 17:46:40:508 1104 a8c Agent * WARNING: Exit code = 0x80244018
2008-12-21 17:46:40:508 1104 a8c Agent *********
2008-12-21 17:46:40:508 1104 a8c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-12-21 17:46:40:508 1104 a8c Agent *************
2008-12-21 17:46:40:508 1104 a8c Agent WARNING: WU client failed Searching for update with error 0x80244018
2008-12-21 17:46:40:508 1104 b2c AU >>## RESUMED ## AU: Search for updates [CallId = {42E90CCE-5F8C-46FC-89D9-6D1975ADB22D}]
2008-12-21 17:46:40:508 1104 b2c AU # WARNING: Search callback failed, result = 0x80244018
2008-12-21 17:46:40:508 1104 b2c AU # WARNING: Failed to find updates with error code 80244018
2008-12-21 17:46:40:508 1104 b2c AU #########
2008-12-21 17:46:40:508 1104 b2c AU ## END ## AU: Search for updates [CallId = {42E90CCE-5F8C-46FC-89D9-6D1975ADB22D}]
2008-12-21 17:46:40:508 1104 b2c AU #############
2008-12-21 17:46:40:508 1104 b2c AU AU setting next detection timeout to 2008-12-22 06:46:40
2008-12-21 17:46:40:508 1104 b2c AU Setting AU scheduled install time to 2008-12-22 11:00:00
2008-12-21 17:46:44:571 1104 a8c Report REPORT EVENT: {E410BEA1-08E5-430D-B79A-E388BE44D0F3} 2008-12-21 17:46:39:570-0800 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244018 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80244018.




The WSUS admin said he can see my test client. Do I have a corrupted WU client?

Thanks ahead of time
0

#19 User is offline   sexydeli 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 27-Jan-09

Posted 27 Jan 2009, 11:16

i racked my brains for 10 hours straight trying to figure this out on my own. Thank you so much! I even registered here just to post this, haha =)
0

#20 User is offline   flexitech 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 16-Feb-09

Posted 17 Feb 2009, 12:48

Just wanted to say THANK YOU! This just resolved an issue I had after a failed SQL Server 2005 SP3 update attempt. Following these steps worked, although I don't see how the SQL and Office updates are at all related.
0

  • (2 Pages)
  • +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users