Some Clients not reporting back or detecting updates
Martin Searle
Some clients are reporting back with the following error:
Windows Update Client failed to detect with error 0x8024400e.
I have done all the usual fixes ie Reset the ID registry keys and then run
WUAUCLT /RESETAUTHORIZATION /DETECTNOW, all too no avail. It would appear
from the log that the cookie isn't being created so I cleared out all cookies
and tried again but same result.
I attach the relevant section of the log:
2008-05-30 12:24:29:124 1120 cb8 Setup * IsUpdateRequired = No
2008-05-30 12:24:29:843 1120 cb8 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-05-30 12:24:29:843 1120 cb8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.kent.ac.uk/ClientWebService/client.asmx
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: SyncUpdates failure, error =
0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
200
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: SOAP Fault: 0x000190
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: faultstring:Fault occurred
2008-05-30 12:24:30:530 1120 cb8 PT WARNING:
ErrorCode:InternalServerError(5)
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: Message:(null)
2008-05-30 12:24:30:530 1120 cb8 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-05-30 12:24:30:530 1120 cb8 PT WARNING:
ID:88825c8a-5457-4867-ba1e-d34298ca944b
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: PTError: 0x8024400e
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x8024400e
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: Sync of Updates: 0x8024400e
2008-05-30 12:24:30:530 1120 cb8 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-05-30 12:24:30:530 1120 cb8 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-05-30 12:24:30:562 1120 cb8 Agent * WARNING: Exit code = 0x8024400E
2008-05-30 12:24:30:562 1120 cb8 Agent *********
2008-05-30 12:24:30:562 1120 cb8 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-05-30 12:24:30:562 1120 cb8 Agent *************
2008-05-30 12:24:30:562 1120 cb8 Agent WARNING: WU client failed Searching
for update with error 0x8024400e
2008-05-30 12:24:30:562 1120 6b4 AU >>## RESUMED ## AU: Search for updates
[CallId = {98F7884B-6AB2-4ABE-95D0-48DEF15032B6}]
2008-05-30 12:24:30:562 1120 6b4 AU # WARNING: Search callback failed,
result = 0x8024400E
2008-05-30 12:24:30:562 1120 6b4 AU # WARNING: Failed to find updates with
error code 8024400E
2008-05-30 12:24:30:562 1120 6b4 AU #########
2008-05-30 12:24:30:562 1120 6b4 AU ## END ## AU: Search for updates
[CallId = {98F7884B-6AB2-4ABE-95D0-48DEF15032B6}]
2008-05-30 12:24:30:562 1120 6b4 AU #############
2008-05-30 12:24:30:562 1120 6b4 AU AU setting next detection timeout to
2008-05-30 16:24:30
2008-05-30 12:24:30:562 1120 6b4 AU Setting AU scheduled install time to
2008-05-31 06:00:00
2008-05-30 12:24:35:562 1120 cb8 Report REPORT EVENT:
{F80C9D71-3D2D-4291-A7E5-DB77C0A51EA5} 2008-05-30
12:24:30:562+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x8024400e.
Any help would be gratefully received,
Martin Searle
University of Kent
Martin Searle
Further to my message earlier:
On one of the problem clients (note there are several thousand machines
working fine with WSUS its just a few machines with this issue) I managed to
get it too talk with the server and it reported the following (there were
about 40 of these referencing different updates):
Update {C96C35FC-A21F-481B-917C-10C4F64792CB}.101 has no local extended
metadata. Not returning it.
It returned 4 updates where I know the machine should report 45 updates
required.
Is this an indication of a corruption in the WSUS database?
Lawrence Garvin
news:089221F5-2A9A-4D57...@microsoft.com...
> Hi,
>
> Some clients are reporting back with the following error:
>
> Windows Update Client failed to detect with error 0x8024400e.
0x8024400e - SUS E PT SOAP SERVER
The message was OK but server couldn't process at the moment
> Any help would be gratefully received,
That's all I got... it's a hard one to track down.
--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Martin Searle
I found that updating my WSUS 3.0 server to SP1 resolved this issue for me.
I guess something on the server went a bit haywire and the service pack stuck
it back together again!
The problematic clients can now talk to the server no problems and report
back correctly. I dare say the re-installation of the client helps.
Martin Searle
Computing Service,
University of Kent
Lambaek@discussions.microsoft.com Soeren Lambaek
I am experiencing the same sort of behavior. Only thing is i am already
running wsus 3 sp1 :-(
Status is:
Some client's work, but it seems that if i add new client pc's they show up
in wsus and fetches the first bunch of about 75 updates and installs these.
But after rebooting the client they are no longer able to connect to the
wsus server.
If i delete the computer from the wsus console it won't get back into wsus
console when issuing 'wuauclt /detectnow' on the client.
I am really stuck on this one! But i am pretty sure that it is a server issue!
Soeren Lambaek
The client does get into wsus console again, only it has a status of "not
reported yet" so it didn't get into the "needed" filter in the console dahhhh
:-)
tdoan
deployments. We have approx 3000 other existing clients that are functioning
properly with WSUS.
For troubleshooting, we pointed one of the problem machines temporarily to a
second WSUS server in the environment by changing the WUServer and
WUStatusServer keys to that URL. It was then able to obtain updates and
report status to that server. We then allowed the group policy to refresh on
the machine to point it back to the original WSUS server, and it appears to
be able to report status there now as well.
Lawrence, what does this indicate? Is there possibly a file or handshake
that is required from the server to allow WSUS communication to initiate?
Could it be that our primary server is unable to do so for these clients, but
once the secondary server does it, the primary can take over from there? How
can we resolve the issue?
Thanks as always.
Tommy
Lawrence Garvin
news:AE2F3356-F4A6-4F06...@microsoft.com...
>> > > > 0x8024400e - SUS E PT SOAP SERVER
>> > > > The message was OK but server couldn't process at the moment
>> > > >
>> > > > > Any help would be gratefully received,
>> > > >
>> > > > That's all I got... it's a hard one to track down.
> For troubleshooting, we pointed one of the problem machines temporarily to
> a
> second WSUS server in the environment by changing the WUServer and
> WUStatusServer keys to that URL. It was then able to obtain updates and
> report status to that server.
This would seem to suggest that the issue is some difference between the two
servers.
> We then allowed the group policy to refresh on
> the machine to point it back to the original WSUS server, and it appears
> to
> be able to report status there now as well.
So, one possibility, which is the "first choice" in the detailed
documentation for this error code, is that it's a transient error, and to
wait a while and try again.
Looks like that worked.
> Lawrence, what does this indicate? Is there possibly a file or handshake
> that is required from the server to allow WSUS communication to initiate?
It could simply be a busy server.
As noted in the error text... "nothing is wrong; the server just couldn't
respond".
> Could it be that our primary server is unable to do so for these clients,
> but
> once the secondary server does it, the primary can take over from there?
> How
> can we resolve the issue?
Here's something to ponder.
How many clients are assigned to this server?
What is the detection interval of these clients?
How many of these clients had XP SP3 approved for installation?
How many of these clients might have been actively transferring the SP3
bits?
Does your server have sufficient hardware resources to handle that load?
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
tdoan
"Lawrence Garvin" wrote:
> "tdoan" <td...@discussions.microsoft.com> wrote in message
> news:AE2F3356-F4A6-4F06...@microsoft.com...
>
> >> > > > 0x8024400e - SUS E PT SOAP SERVER
> >> > > > The message was OK but server couldn't process at the moment
> >> > > >
> >> > > > > Any help would be gratefully received,
> >> > > >
> >> > > > That's all I got... it's a hard one to track down.
>
>
> > For troubleshooting, we pointed one of the problem machines temporarily to
> > a
> > second WSUS server in the environment by changing the WUServer and
> > WUStatusServer keys to that URL. It was then able to obtain updates and
> > report status to that server.
>
> This would seem to suggest that the issue is some difference between the two
> servers.
>
> > We then allowed the group policy to refresh on
> > the machine to point it back to the original WSUS server, and it appears
> > to
> > be able to report status there now as well.
>
> So, one possibility, which is the "first choice" in the detailed
> documentation for this error code, is that it's a transient error, and to
> wait a while and try again.
>
> Looks like that worked.
The error happens consistently with all new XP computers we join to the
domain and bring under WSUS 3.0 SP1 management.
> > Lawrence, what does this indicate? Is there possibly a file or handshake
> > that is required from the server to allow WSUS communication to initiate?
>
> It could simply be a busy server.
>
> As noted in the error text... "nothing is wrong; the server just couldn't
> respond".
The server is a dual-core 3.2Ghz machine with 2GB of RAM and a 1Gb NIC
supporting just over 3000 clients. The issue does not seem to affect existing
clients.
> > Could it be that our primary server is unable to do so for these clients,
> > but
> > once the secondary server does it, the primary can take over from there?
> > How
> > can we resolve the issue?
>
> Here's something to ponder.
>
> How many clients are assigned to this server?
3000
> What is the detection interval of these clients?
Most are the default 22 hours. Our approx 200 servers are at 8 hours.
> How many of these clients had XP SP3 approved for installation?
Zero. We have not approved XP SP3 for installation via WSUS (and typically
do not deploy SPs via WSUS at all).
> How many of these clients might have been actively transferring the SP3
> bits?
Zero.
> Does your server have sufficient hardware resources to handle that load?
Yes.
Let me provide some log information from one of the problem machines.
2008-06-21 00:08:49:015 768 548 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: -0500) ===========
2008-06-21 00:08:49:015 768 548 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2008-06-21 00:08:49:015 768 548 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-21 00:08:49:000 768 548 Service *************
2008-06-21 00:08:49:015 768 548 Service ** START ** Service: Service startup
2008-06-21 00:08:49:015 768 548 Service *********
2008-06-21 00:08:49:015 768 548 Agent * WU client version 7.1.6001.65
2008-06-21 00:08:49:015 768 548 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-06-21 00:08:49:015 768 548 Agent * Access type: No proxy
2008-06-21 00:08:49:015 768 548 Agent * Network state: Connected
2008-06-21 00:08:51:359 768 6ec Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-06-21 00:08:51:359 768 6ec Agent *********** Agent: Initializing
global settings cache ***********
2008-06-21 00:08:51:359 768 6ec Agent * WSUS server:
https://primaryserver.msft
2008-06-21 00:08:51:359 768 6ec Agent * WSUS status server:
https://primaryserver.msft
2008-06-21 00:08:51:359 768 6ec Agent * Target group: ITS Servers
2008-06-21 00:08:51:359 768 6ec Agent * Windows Update access disabled: No
2008-06-21 00:08:51:359 768 6ec DnldMgr Download manager restoring 0
downloads
2008-06-21 00:08:51:359 768 6ec AU ########### AU: Initializing Automatic
Updates ###########
2008-06-21 00:08:51:375 768 6ec AU AU setting next detection timeout to
2008-06-21 05:08:51
2008-06-21 00:08:51:375 768 6ec AU # WSUS server:
https://primaryserver.msft
2008-06-21 00:08:51:375 768 6ec AU # Detection frequency: 8
2008-06-21 00:08:51:375 768 6ec AU # Target group: ITS Servers
2008-06-21 00:08:51:375 768 6ec AU # Approval type: Pre-install notify
(User preference)
2008-06-21 00:08:51:375 768 6ec AU # Auto-install minor updates: No (User
preference)
2008-06-21 00:08:51:375 768 6ec AU # Auto update required (cannot be
disabled)
2008-06-21 00:08:51:375 768 6ec AU AU finished delayed initialization
2008-06-21 00:08:51:375 768 6ec AU Triggering AU detection through
DetectNow API
2008-06-21 00:08:51:375 768 6ec AU Triggering Online detection
(non-interactive)
2008-06-21 00:08:51:421 768 548 Report *********** Report: Initializing
static reporting data ***********
2008-06-21 00:08:51:421 768 548 Report * OS Version = 5.2.3790.2.0.196880
2008-06-21 00:08:51:453 768 548 Report * Computer Brand = HP
2008-06-21 00:08:51:453 768 548 Report * Computer Model = ProLiant DL380 G4
2008-06-21 00:08:51:453 768 548 Report * Bios Revision = P51
2008-06-21 00:08:51:453 768 548 Report * Bios Name = Default System BIOS
2008-06-21 00:08:51:453 768 548 Report * Bios Release Date =
2005-10-10T00:00:00
2008-06-21 00:08:51:453 768 548 Report * Locale ID = 1033
2008-06-21 00:08:51:453 768 548 AU #############
2008-06-21 00:08:51:453 768 548 AU ## START ## AU: Search for updates
2008-06-21 00:08:51:453 768 548 AU #########
2008-06-21 00:08:51:453 768 548 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {AE36B3E8-2A79-4B79-A9A3-F980B2E24D1A}]
2008-06-21 00:08:51:515 768 294 Report Uploading 7 events using cached
cookie, reporting URL =
https://primaryserver.msft/ReportingWebService/ReportingWebService.asmx
2008-06-21 00:08:58:312 768 294 PT WARNING: ReportEventBatch failure, error
= 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code
= 200
2008-06-21 00:08:58:312 768 294 PT WARNING: SOAP Fault: 0x00012c
2008-06-21 00:08:58:312 768 294 PT WARNING: faultstring:Fault occurred
2008-06-21 00:08:58:312 768 294 PT WARNING: ErrorCode:InvalidCookie(1)
2008-06-21 00:08:58:312 768 294 PT WARNING: Message:(null)
2008-06-21 00:08:58:312 768 294 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
2008-06-21 00:08:58:312 768 294 PT WARNING:
ID:d2601bff-0095-4623-a73f-b7112a9fd3f0
2008-06-21 00:08:58:312 768 294 Report WARNING: Reporter failed to upload
events with hr = 8024400d.
2008-06-21 00:08:58:343 768 294 Report Uploading 7 events using cached
cookie, reporting URL =
https://primaryserver.msft/ReportingWebService/ReportingWebService.asmx
2008-06-21 00:08:58:375 768 294 PT WARNING: ReportEventBatch failure, error
= 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code
= 200
2008-06-21 00:08:58:375 768 294 PT WARNING: SOAP Fault: 0x00012c
2008-06-21 00:08:58:375 768 294 PT WARNING: faultstring:Fault occurred
2008-06-21 00:08:58:375 768 294 PT WARNING: ErrorCode:InvalidCookie(1)
2008-06-21 00:08:58:375 768 294 PT WARNING: Message:(null)
2008-06-21 00:08:58:375 768 294 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
2008-06-21 00:08:58:375 768 294 PT WARNING:
ID:dd768b8c-323e-46d1-89de-f5c5879452bc
2008-06-21 00:08:58:375 768 294 Report WARNING: Reporter failed to upload
events with hr = 8024400d.
2008-06-21 00:08:58:406 768 294 Report Uploading 7 events using cached
cookie, reporting URL =
https://primaryserver.msft/ReportingWebService/ReportingWebService.asmx
2008-06-21 00:08:58:421 768 294 PT WARNING: ReportEventBatch failure, error
= 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code
= 200
2008-06-21 00:08:58:421 768 294 PT WARNING: SOAP Fault: 0x00012c
2008-06-21 00:08:58:421 768 294 PT WARNING: faultstring:Fault occurred
2008-06-21 00:08:58:421 768 294 PT WARNING: ErrorCode:InvalidCookie(1)
2008-06-21 00:08:58:421 768 294 PT WARNING: Message:(null)
2008-06-21 00:08:58:421 768 294 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
2008-06-21 00:08:58:421 768 294 PT WARNING:
ID:6ecc4cf4-153a-4246-a030-7d9058cdd45f
2008-06-21 00:08:58:421 768 294 Report WARNING: Reporter failed to upload
events with hr = 8024400d.
2008-06-21 00:08:58:421 768 294 Agent *************
2008-06-21 00:08:58:421 768 294 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-21 00:08:58:421 768 294 Agent *********
2008-06-21 00:08:58:421 768 294 Agent * Online = Yes; Ignore download
priority = No
2008-06-21 00:08:58:421 768 294 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-21 00:08:58:421 768 294 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-21 00:08:58:437 768 294 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-21 00:08:58:437 768 294 Misc Microsoft signed: Yes
2008-06-21 00:08:58:453 768 294 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-21 00:08:58:468 768 294 Misc Microsoft signed: Yes
2008-06-21 00:08:58:468 768 294 Setup *********** Setup: Checking whether
self-update is required ***********
2008-06-21 00:08:58:468 768 294 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-21 00:08:58:484 768 294 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2008-06-21 00:08:58:484 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:08:58:484 768 294 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-21 00:08:58:484 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:08:58:484 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:08:58:500 768 294 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-21 00:08:58:500 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:08:58:500 768 294 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-21 00:08:58:500 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:08:58:515 768 294 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-21 00:08:58:515 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:08:58:515 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:08:58:531 768 294 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:08:58:531 768 294 Setup * IsUpdateRequired = No
2008-06-21 00:08:59:046 768 294 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-21 00:08:59:046 768 294 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://primaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:09:00:640 768 294 PT WARNING: SyncUpdates failure, error =
0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
200
2008-06-21 00:09:00:640 768 294 PT WARNING: SOAP Fault: 0x00012c
2008-06-21 00:09:00:640 768 294 PT WARNING: faultstring:Fault occurred
2008-06-21 00:09:00:640 768 294 PT WARNING: ErrorCode:InvalidCookie(1)
2008-06-21 00:09:00:640 768 294 PT WARNING: Message:(null)
2008-06-21 00:09:00:640 768 294 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-21 00:09:00:640 768 294 PT WARNING:
ID:1a6c41cd-b85b-4c39-b96f-31a9aa8a8058
2008-06-21 00:09:00:640 768 294 PT WARNING: PTError: 0x80244015
2008-06-21 00:09:00:640 768 294 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x80244015
2008-06-21 00:09:00:640 768 294 PT WARNING: Sync of Updates: 0x80244015
2008-06-21 00:09:00:703 768 294 PT WARNING: Cached cookie has expired or
new PID is available
2008-06-21 00:09:00:703 768 294 PT Initializing simple targeting cookie,
clientId = 70351342-9801-44d1-9121-ada7ed3701b2, target group = ITS Servers,
DNS name = anotherserver.msft
2008-06-21 00:09:00:703 768 294 PT Server URL =
https://primaryserver.msft/SimpleAuthWebService/SimpleAuth.asmx
2008-06-21 00:09:00:859 768 294 Agent * WARNING: Failed to synchronize,
error = 0x80244015
2008-06-21 00:09:00:859 768 294 DnldMgr File locations for service
3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2008-06-21 00:09:00:859 768 294 Agent Server changed and need resyncing
with server
2008-06-21 00:09:00:953 768 294 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-21 00:09:00:953 768 294 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://primaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:09:02:703 768 294 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-06-21 00:09:02:703 768 294 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://primaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:09:02:812 768 294 Agent * Found 0 updates and 35 categories
in search; evaluated appl. rules of 632 out of 397 deployed entities
2008-06-21 00:09:02:812 768 294 Agent *********
2008-06-21 00:09:02:812 768 294 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-21 00:09:02:812 768 294 Agent *************
2008-06-21 00:09:02:812 768 1ec AU >>## RESUMED ## AU: Search for updates
[CallId = {AE36B3E8-2A79-4B79-A9A3-F980B2E24D1A}]
2008-06-21 00:09:02:812 768 1ec AU # 0 updates detected
2008-06-21 00:09:02:812 768 1ec AU #########
2008-06-21 00:09:02:812 768 1ec AU ## END ## AU: Search for updates
[CallId = {AE36B3E8-2A79-4B79-A9A3-F980B2E24D1A}]
2008-06-21 00:09:02:812 768 1ec AU #############
2008-06-21 00:09:02:812 768 1ec AU AU setting next detection timeout to
2008-06-21 12:51:38
2008-06-21 00:09:07:812 768 294 Report REPORT EVENT:
{6B8A12EC-1990-494E-81D3-8CCCA5DC5CF5} 2008-06-21
00:09:02:812-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2008-06-21 00:09:07:812 768 294 Report REPORT EVENT:
{E1D40261-3417-45AB-9123-32C4C930F35D} 2008-06-21
00:09:02:812-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2008-06-21 00:10:29:937 768 548 AU ########### AU: Uninitializing
Automatic Updates ###########
2008-06-21 00:10:29:968 768 548 Service *********
2008-06-21 00:10:29:968 768 548 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2008-06-21 00:10:29:968 768 548 Service *************
Then I can point the client to the secondary WSUS server with this result.
2008-06-21 00:13:12:781 768 1ac Misc =========== Logging initialized
(build: 7.1.6001.65, tz: -0500) ===========
2008-06-21 00:13:12:781 768 1ac Misc = Process:
C:\WINDOWS\System32\svchost.exe
2008-06-21 00:13:12:781 768 1ac Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-21 00:13:12:781 768 1ac Service *************
2008-06-21 00:13:12:781 768 1ac Service ** START ** Service: Service startup
2008-06-21 00:13:12:781 768 1ac Service *********
2008-06-21 00:13:12:781 768 1ac Agent * WU client version 7.1.6001.65
2008-06-21 00:13:12:781 768 1ac Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-06-21 00:13:12:781 768 1ac Agent * Access type: No proxy
2008-06-21 00:13:12:781 768 1ac Agent * Network state: Connected
2008-06-21 00:13:15:046 768 350 Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-06-21 00:13:15:046 768 350 Agent *********** Agent: Initializing
global settings cache ***********
2008-06-21 00:13:15:046 768 350 Agent * WSUS server:
http://secondaryserver.msft
2008-06-21 00:13:15:046 768 350 Agent * WSUS status server:
http://secondaryserver.msft
2008-06-21 00:13:15:046 768 350 Agent * Target group: ITS Servers
2008-06-21 00:13:15:046 768 350 Agent * Windows Update access disabled: No
2008-06-21 00:13:15:046 768 350 DnldMgr Download manager restoring 0
downloads
2008-06-21 00:13:15:046 768 350 AU ########### AU: Initializing Automatic
Updates ###########
2008-06-21 00:13:15:046 768 350 AU AU setting next detection timeout to
2008-06-21 05:13:15
2008-06-21 00:13:15:046 768 350 AU # WSUS server:
http://secondaryserver.msft
2008-06-21 00:13:15:046 768 350 AU # Detection frequency: 8
2008-06-21 00:13:15:046 768 350 AU # Target group: ITS Servers
2008-06-21 00:13:15:046 768 350 AU # Approval type: Pre-install notify
(User preference)
2008-06-21 00:13:15:046 768 350 AU # Auto-install minor updates: No (User
preference)
2008-06-21 00:13:15:046 768 350 AU # Auto update required (cannot be
disabled)
2008-06-21 00:13:15:062 768 350 AU AU finished delayed initialization
2008-06-21 00:13:15:062 768 350 AU Triggering AU detection through
DetectNow API
2008-06-21 00:13:15:062 768 350 AU Triggering Online detection
(non-interactive)
2008-06-21 00:13:15:078 768 1ac Report *********** Report: Initializing
static reporting data ***********
2008-06-21 00:13:15:078 768 1ac Report * OS Version = 5.2.3790.2.0.196880
2008-06-21 00:13:15:125 768 1ac Report * Computer Brand = HP
2008-06-21 00:13:15:125 768 1ac Report * Computer Model = ProLiant DL380 G4
2008-06-21 00:13:15:125 768 1ac Report * Bios Revision = P51
2008-06-21 00:13:15:125 768 1ac Report * Bios Name = Default System BIOS
2008-06-21 00:13:15:125 768 1ac Report * Bios Release Date =
2005-10-10T00:00:00
2008-06-21 00:13:15:125 768 1ac Report * Locale ID = 1033
2008-06-21 00:13:15:125 768 1ac AU #############
2008-06-21 00:13:15:125 768 1ac AU ## START ## AU: Search for updates
2008-06-21 00:13:15:125 768 1ac AU #########
2008-06-21 00:13:15:125 768 1ac AU <<## SUBMITTED ## AU: Search for updates
[CallId = {E6337340-1E82-49E6-AA5F-CFEDB314047B}]
2008-06-21 00:13:15:171 768 6b4 Agent *************
2008-06-21 00:13:15:171 768 6b4 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-21 00:13:15:171 768 6b4 Agent *********
2008-06-21 00:13:15:171 768 6b4 Agent * Online = Yes; Ignore download
priority = No
2008-06-21 00:13:15:171 768 6b4 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-21 00:13:15:171 768 6b4 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-21 00:13:15:171 768 6b4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-21 00:13:15:171 768 6b4 Misc Microsoft signed: Yes
2008-06-21 00:13:21:937 768 6b4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-21 00:13:21:937 768 6b4 Misc Microsoft signed: Yes
2008-06-21 00:13:21:984 768 6b4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-21 00:13:21:984 768 6b4 Misc Microsoft signed: Yes
2008-06-21 00:13:21:984 768 6b4 Setup *********** Setup: Checking whether
self-update is required ***********
2008-06-21 00:13:21:984 768 6b4 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 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-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 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-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 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-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 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-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-21 00:13:21:984 768 6b4 Setup * IsUpdateRequired = No
2008-06-21 00:13:22:156 768 6b4 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-21 00:13:22:156 768 6b4 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://secondaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:13:26:718 768 6b4 PT WARNING: SyncUpdates failure, error =
0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
200
2008-06-21 00:13:26:718 768 6b4 PT WARNING: SOAP Fault: 0x00012c
2008-06-21 00:13:26:718 768 6b4 PT WARNING: faultstring:Fault occurred
2008-06-21 00:13:26:718 768 6b4 PT WARNING: ErrorCode:InvalidCookie(1)
2008-06-21 00:13:26:718 768 6b4 PT WARNING: Message:(null)
2008-06-21 00:13:26:718 768 6b4 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-21 00:13:26:718 768 6b4 PT WARNING:
ID:9c920566-0a44-403b-9f1d-18d01bc4727b
2008-06-21 00:13:26:718 768 6b4 PT WARNING: PTError: 0x80244015
2008-06-21 00:13:26:718 768 6b4 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x80244015
2008-06-21 00:13:26:718 768 6b4 PT WARNING: Sync of Updates: 0x80244015
2008-06-21 00:13:26:765 768 6b4 PT WARNING: Cached cookie has expired or
new PID is available
2008-06-21 00:13:26:765 768 6b4 PT Initializing simple targeting cookie,
clientId = 70351342-9801-44d1-9121-ada7ed3701b2, target group = ITS Servers,
DNS name = sfcs2.systems.smu.edu
2008-06-21 00:13:26:765 768 6b4 PT Server URL =
http://secondaryserver.msft/SimpleAuthWebService/SimpleAuth.asmx
2008-06-21 00:13:28:078 768 6b4 Agent * WARNING: Failed to synchronize,
error = 0x80244015
2008-06-21 00:13:28:078 768 6b4 DnldMgr File locations for service
3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2008-06-21 00:13:28:078 768 6b4 Agent Server changed and need resyncing
with server
2008-06-21 00:13:28:140 768 6b4 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-21 00:13:28:140 768 6b4 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://secondaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:13:30:046 768 6b4 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-06-21 00:13:30:046 768 6b4 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://secondaryserver.msft/ClientWebService/client.asmx
2008-06-21 00:13:30:187 768 6b4 Agent * Found 0 updates and 35 categories
in search; evaluated appl. rules of 632 out of 397 deployed entities
2008-06-21 00:13:30:187 768 6b4 Agent *********
2008-06-21 00:13:30:187 768 6b4 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-21 00:13:30:187 768 6b4 Agent *************
2008-06-21 00:13:30:187 768 67c AU >>## RESUMED ## AU: Search for updates
[CallId = {E6337340-1E82-49E6-AA5F-CFEDB314047B}]
2008-06-21 00:13:30:187 768 67c AU # 0 updates detected
2008-06-21 00:13:30:187 768 67c AU #########
2008-06-21 00:13:30:187 768 67c AU ## END ## AU: Search for updates
[CallId = {E6337340-1E82-49E6-AA5F-CFEDB314047B}]
2008-06-21 00:13:30:187 768 67c AU #############
2008-06-21 00:13:30:187 768 67c AU AU setting next detection timeout to
2008-06-21 12:15:16
2008-06-21 00:13:35:187 768 6b4 Report REPORT EVENT:
{A2923778-0F80-42D4-B5C5-5FACDB42D526} 2008-06-21
00:13:30:187-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2008-06-21 00:13:35:187 768 6b4 Report REPORT EVENT:
{9F771D38-9C02-4C61-AB16-1C0B0304AA0A} 2008-06-21
00:13:30:187-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2008-06-21 00:16:01:690 768 1ac AU ########### AU: Uninitializing
Automatic Updates ###########
2008-06-21 00:16:01:721 768 1ac Service *********
2008-06-21 00:16:01:721 768 1ac Service ** END ** Service: Service exit
[Exit code = 0x240001]
2008-06-21 00:16:01:721 768 1ac Service *************
And the issue appears to be resolved. I can then point the client back to
the primary server and all is well.
Thanks for any help you can provide.
Lawrence Garvin
> The server is a dual-core 3.2Ghz machine with 2GB of RAM and a 1Gb NIC
> supporting just over 3000 clients. The issue does not seem to affect
> existing
> clients.
>> How many clients are assigned to this server?
>
> 3000
>
>> What is the detection interval of these clients?
>
> Most are the default 22 hours. Our approx 200 servers are at 8 hours.
So, you have 3,000 clients plus 200 servers @ 8 hours, which is equivalent
to 600 clients @ 22 hours,
making an effective load of 3600 clients.
> Let me provide some log information from one of the problem machines.
> 2008-06-21 00:08:51:375 768 6ec AU # Detection frequency: 8
> 2008-06-21 00:08:51:375 768 6ec AU # Target group: ITS Servers
One of the problem machines is a =server=???
> 2008-06-21 00:08:51:515 768 294 Report Uploading 7 events using cached
> cookie, reporting URL =
> https://primaryserver.msft/ReportingWebService/ReportingWebService.asmx
> 2008-06-21 00:08:58:312 768 294 PT WARNING: ReportEventBatch failure,
> error
> = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status
> code
> = 200
> 2008-06-21 00:08:58:312 768 294 PT WARNING: SOAP Fault: 0x00012c
> 2008-06-21 00:08:58:312 768 294 PT WARNING: faultstring:Fault occurred
> 2008-06-21 00:08:58:312 768 294 PT WARNING: ErrorCode:InvalidCookie(1)
> 2008-06-21 00:08:58:312 768 294 PT WARNING: Message:(null)
> 2008-06-21 00:08:58:312 768 294 PT WARNING:
> Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
> 2008-06-21 00:08:58:312 768 294 PT WARNING:
> ID:d2601bff-0095-4623-a73f-b7112a9fd3f0
> 2008-06-21 00:08:58:312 768 294 Report WARNING: Reporter failed to upload
> events with hr = 8024400d.
> Then I can point the client to the secondary WSUS server with this result.
Shall we make a critical note at this point that the first server appears to
be confgured to use =SSL=,
and yet, your second server, that works, is not using SSL.
> 2008-06-21 00:08:51:359 768 6ec Agent * WSUS server:
> https://primaryserver.msft
> 2008-06-21 00:08:51:359 768 6ec Agent * WSUS status server:
> https://primaryserver.msft
> 2008-06-21 00:13:15:046 768 350 Agent * WSUS server:
> http://secondaryserver.msft
> 2008-06-21 00:13:15:046 768 350 Agent * WSUS status server:
> http://secondaryserver.msft
So, given that _DIFFERENCE_,
and my very first question in this thread which was:
WHAT'S DIFFERENT between the two servers.
Now we know the answer.
1. Remove the =SSL= configuration from your primary server.
2. Retest, note that first-time clients now have no issues connecting.
3. Then, properly reconfigure the SSL environment for your primary WSUS
Server
Dollars-to-donuts says your first-time clients are having issues because
they don't have the proper certificates in place in order to successfully
communicate with httpS://primaryserver.msft
> And the issue appears to be resolved. I can then point the client back to
> the primary server and all is well.
At which time, somewhere along the way, the first-time clients successfully
obtained the necessary certificates in order to conduct an SSL session with
the primary WSUS Server.