Automatic updates stopped working after SP3 has been installed

Alexander

unread,

Jun 3, 2008, 11:21:50 AM6/3/08

to

Hello,

We have a corporate WSUS server that all workstations use for getting
updates.

After installing SP3 on a new Windows XP box, that box stopped getting
updates. Its WindowsUpdate.log contains SOAP errors:
...
2008-06-03 19:07:43:222 1052 2f8 Setup * IsUpdateRequired = No
2008-06-03 19:07:43:300 1052 2f8 PT +++++++++++ PT: Synchronizing
server updates +++++++++++
2008-06-03 19:07:43:300 1052 2f8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://sus:8530/ClientWebService/client.asmx
2008-06-03 19:07:43:300 1052 2f8 Agent Switching to hardware-verified
ClientId.
2008-06-03 19:07:43:316 1052 2f8 PT WARNING: Cached cookie has expired
or new PID is available
2008-06-03 19:07:43:628 1052 2f8 Agent Created new random SusClientId
cf9b00aa-97a6-4a28-94e2-efdc0c094a7e. Old Id:
71b1e082-140e-45da-ad43-ba80b1e0cb59.
2008-06-03 19:07:43:628 1052 2f8 PT Initializing simple targeting
cookie, clientId = cf9b00aa-97a6-4a28-94e2-efdc0c094a7e, target group = ,
DNS name = comp.domain.biz
2008-06-03 19:07:43:628 1052 2f8 PT Server URL =
http://sus:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-06-03 19:07:46:472 1052 2f8 PT WARNING: SyncUpdates failure, error
= 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code
= 200
2008-06-03 19:07:46:472 1052 2f8 PT WARNING: SOAP Fault: 0x000190
2008-06-03 19:07:46:472 1052 2f8 PT WARNING: faultstring:Fault
occurred
2008-06-03 19:07:46:472 1052 2f8 PT WARNING:
ErrorCode:InternalServerError(5)
2008-06-03 19:07:46:472 1052 2f8 PT WARNING: Message:(null)
2008-06-03 19:07:46:487 1052 2f8 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-03 19:07:46:487 1052 2f8 PT WARNING:
ID:31d3d97a-8284-4b2e-8e15-5996cf6d9576
2008-06-03 19:07:46:487 1052 2f8 PT WARNING: PTError: 0x8024400e
2008-06-03 19:07:46:487 1052 2f8 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x8024400e
2008-06-03 19:07:46:487 1052 2f8 PT WARNING: Sync of Updates: 0x8024400e
2008-06-03 19:07:46:487 1052 2f8 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-06-03 19:07:46:487 1052 2f8 Agent * WARNING: Failed to
synchronize, error = 0x8024400E
2008-06-03 19:07:46:503 1052 2f8 Agent * WARNING: Exit code =
0x8024400E
2008-06-03 19:07:46:503 1052 2f8 Agent *********
2008-06-03 19:07:46:503 1052 2f8 Agent ** END ** Agent: Finding
updates [CallerId = AutomaticUpdates]
2008-06-03 19:07:46:503 1052 2f8 Agent *************
2008-06-03 19:07:46:503 1052 2f8 Agent WARNING: WU client failed
Searching for update with error 0x8024400e
2008-06-03 19:07:46:503 1052 d10 AU >>## RESUMED ## AU: Search for
updates [CallId = {B28CD805-76E7-42F9-8F75-84ADA98269AC}]
2008-06-03 19:07:46:503 1052 d10 AU # WARNING: Search callback failed,
result = 0x8024400E
2008-06-03 19:07:46:503 1052 d10 AU # WARNING: Failed to find updates
with error code 8024400E
2008-06-03 19:07:46:503 1052 d10 AU #########
2008-06-03 19:07:46:503 1052 d10 AU ## END ## AU: Search for updates
[CallId = {B28CD805-76E7-42F9-8F75-84ADA98269AC}]
2008-06-03 19:07:46:503 1052 d10 AU #############
2008-06-03 19:07:46:503 1052 d10 AU AU setting next detection timeout to
2008-06-03 20:07:46
2008-06-03 19:07:51:502 1052 2f8 Report REPORT EVENT:
{5692A6B9-F894-4200-8B1F-C337D541B484} 2008-06-03 19:07:46:503+0400 1 148
101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates
Failure Software Synchronization Windows Update Client failed to detect
with error 0x8024400e.

WSUS server's SoftwareDistribution.log contains:

2008-06-03 15:07:46.561 UTC Error w3wp.6 ClientImplementation.SyncUpdates
System.ArgumentException: Item has already been added. Key in dictionary:
'19202' Key being added: '19202'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean
add)
at System.Collections.Hashtable.Add(Object key, Object value)
at
Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(DataAccess
dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean
haveGroupsChanged, Boolean doChunking)
at
Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess
dataAccess, UnencryptedCookieData cookieData, Int32[]
installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged,
Boolean expressQuery)
at
Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie
cookie, SyncUpdateParameters parameters)
at
Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie
cookie, SyncUpdateParameters parameters)
at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie,
SyncUpdateParameters parameters)
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target,
Object[] values)
at System.Web.Services.Protocols.WebServiceHandler.Invoke()
at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
at
System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext
context)
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
at
System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception
error)
at
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext
context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32
iWRType)
2008-06-03 15:07:46.576 UTC Warning w3wp.6 SoapUtilities.CreateException
ThrowException: actor = http://sus:8530/ClientWebService/client.asmx,
ID=31d3d97a-8284-4b2e-8e15-5996cf6d9576, ErrorCode=InternalServerError,
Message=, Client=?

I've tried to delete SusCliendId from workstation's registry,
SoftwareDistribution folder from workstation's Windows folder - nothing
helps.

All other workstations in AD domain are updating from that WSUS server
perfectly.

Please, help!

Eddie Bowers [MSFT]

unread,

Jun 3, 2008, 12:44:58 PM6/3/08

to

Try this.
net stop wuauserv
net stop bits
rename the c:\windows\software distribution folder
net start bits
net start wuauserv

If this doesn't fix it, then force a reinstall of the agent by downloading
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.6
5/WindowsUpdateAgent30-x86.exe
and installing with the /wuforce switch

Eddie Bowers
Security Support
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

PA Bear [MS MVP]

unread,

Jun 3, 2008, 4:50:48 PM6/3/08

to

Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services

NB: Eddie Bowers [MSFT] posted a reply to this thread in WU NG:

<QP>

Try this.
net stop wuauserv
net stop bits
rename the c:\windows\software distribution folder
net start bits
net start wuauserv

If this doesn't fix it, then force a reinstall of the agent by downloading
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x86.exe
and installing with the /wuforce switch

</QP>
--
~PA Bear

Alexander

unread,

Jun 4, 2008, 6:29:11 AM6/4/08

to

Thanks for your such a fast answer, Eddie!

Unfortunately, both of your suggestions didn't help.

I suppose, this is a problem on a server side, since it looks like a
duplicate key in database:

2008-06-03 15:07:46.561 UTC Error w3wp.6 ClientImplementation.SyncUpdates
System.ArgumentException: Item has already been added. Key in dictionary:
'19202' Key being added: '19202'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean
add)

...

If you have any other suggestions, please, let me know!

"Eddie Bowers [MSFT]" <edd...@online.microsoft.com> wrote in message
news:afaVwkZx...@TK2MSFTNGHUB02.phx.gbl...

Eddie Bowers [MSFT]

unread,

Jun 4, 2008, 4:46:22 PM6/4/08

to

How about this:

net stop wuauserv

Delete the following registry keys:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDomainSi
d

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId

net start wuauserv
wuauclt.exe /resetauthorization /detectnow

Alexander

unread,

Jun 5, 2008, 4:58:43 AM6/5/08

to

Just tried your suggestion. Since there are no PingID and AccountDomainSid,
I've deleted SusClientId only.
Not helped either :(

Looks like I've discovered the sequence of actions that led to the current
issue:
1. After installing SP3 warnings and soap errors came up
2. One of our IT support guys deleted SusClientId instead of removing
SoftwareDistribution folder
3. And now nothing helps

Any other thoughts?

"Eddie Bowers [MSFT]" <edd...@online.microsoft.com> wrote in message

news:oF7vRQox...@TK2MSFTNGHUB02.phx.gbl...

Eddie Bowers [MSFT]

unread,

Jun 5, 2008, 12:12:11 PM6/5/08

to

Is this the ONLY client machine that has this problem?
Most of the time this is a WSUS server side problem, but that would cause
all of your clients to fail.
How many computers check into your WSUS server?

Alexander

unread,

Jun 6, 2008, 4:20:41 AM6/6/08

to

It appears, there are two more clients that have such a problem: Windows
2000 SP4 and Windows XP SP1.
In total, there are approx. 50 computers that use WSUS server.

"Eddie Bowers [MSFT]" <edd...@online.microsoft.com> wrote in message

news:0nXHwbyx...@TK2MSFTNGHUB02.phx.gbl...

Eddie Bowers [MSFT]

unread,

Jun 9, 2008, 6:55:30 PM6/9/08

to

OK, well lets try the shotgun approach to see what happnes. Run my tool
from:
http:\\www.codeplex.com\aureset

Alexander

unread,

Jun 10, 2008, 5:40:52 AM6/10/08

to

Hi Eddie,

This didn't help unfortunately. Do you need me to send generated log files
somewhere?

Please, mention, that couple of antiviruses thinks your software is a virus:
http://www.virustotal.com/analisis/e23a9b0bebcada0986f8502edd0fa454

"Eddie Bowers [MSFT]" <edd...@online.microsoft.com> wrote in message

news:FsjMtPoy...@TK2MSFTNGHUB02.phx.gbl...

Eddie Bowers [MSFT]

unread,

Jun 11, 2008, 3:58:40 PM6/11/08

to

Are the machines getting the error below on the same network segment as
those not getting the error?
( WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7,
soap error code = 400)

The logs that the tool generates probably are not going to help with this.
I think at this point we would have to get a network trace and have you
open a case with us so we can really dig into it.

Thanks for the VirusTotal link. Thats interesting. I can see how what it
does would look suspect.

Eddie Bowers
Security Support
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Eddie,

APlus

unread,

Jun 15, 2008, 5:00:00 AM6/15/08

to

I have the same problem:

WindowsUpdate.log shows:

WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7,
soap error code = 400, HTTP status code = 200

WARNING: SOAP Fault: 0x000190

SoftwareDistribution.log shows:
Error w3wp.5 ClientImplementation.SyncUpdates System.ArgumentException:
Item has already been added. Key in dictionary: '8135' Key being added:
'8135'

Nothing helps, already tried:
1) wuauclt.exe /resetauthorization /detectnow
2) Deleted SoftwareDistribution Folder
3) WindowsUpdateAgent30-x86.exe /wuforce
4) Deleted SusClientId and Validation Registry Keys

It looks like a server side problem...

Any help is appreciated!

groovyf

unread,

Jun 17, 2008, 8:25:01 AM6/17/08

to

Also now have the same. PC was XP2 and not on the domain. Installed SP3, then
joined domain and used wuauclt /detectnow to force a check-in.

Getting SOAP errors, etc and "duplicate key" in softwaredistribution.log on
WSUS server

Tried the usual steps... resetauth, delete SusclientID, etc, etc.
reinstalled Update Agent

Any known fix for this?

[PC is being set-up for a user who's current PC has issues. So renamed PC
for them so I could create a new one. Have named the 'new' PC the same as the
one with issues used to be called. I suspect the issue may lie with this in
the WSUS db?]

Christopher Hill

unread,

Jun 17, 2008, 9:48:01 AM6/17/08

to

I was having the same problems, but managed to fix the problem by
reinstalling the WUA with /wuforce, as per Eddie's first set of instructions.
However, please note that the download locations that Eddie provided for the
WUA are for the very latest version of WUA, 7.1.6001.65:

http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x86.exe
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x64.exe

This is *not* the version of the WUA standalone executable that most people
have. Most people are still using version 7.0.6000.381, which is the one that
Microsoft are still distributing via Wuredist.cab (see
http://msdn.microsoft.com/en-us/library/aa387285(VS.85).aspx).

When I tried installing version 7.1.6001.65 with /wuforce, it fixed the
problem for me.

Regards,
--
Chris Hill
ICT Technician - Colchester Royal Grammar School

"Alexander" wrote:

> Hello,
>
> We have a corporate WSUS server that all workstations use for getting
> updates.
>
> After installing SP3 on a new Windows XP box, that box stopped getting
> updates. Its WindowsUpdate.log contains SOAP errors:

> ....

groovyf

unread,

Jun 17, 2008, 12:29:02 PM6/17/08

to

Thanks for the info, Chris.
I'll give that a go when I'm back in work tomorrow.
I do know that my client PCs are on 7.1.6001.65 as .log file states no
update required for Agent files.

I'll respond tomorrow with results.

Thanks
Craig

Chris

unread,

Jun 18, 2008, 3:56:02 AM6/18/08

to

Hi,

I have the same issues with the duplicate key being created with a new
laptop joining the network. I tried reinstalling the client OS and rejoining
but with the same results, admitedly I gave the client the same machine name.
This is the 50th client to join the WSUS server. Anyone found a fix yet?

Thanks

Chris

"Alexander" wrote:

> Hello,
>
> We have a corporate WSUS server that all workstations use for getting
> updates.
>
> After installing SP3 on a new Windows XP box, that box stopped getting
> updates. Its WindowsUpdate.log contains SOAP errors:

> ....

groovyf

unread,

Jun 18, 2008, 4:10:01 AM6/18/08

to

It was looking good up until I forced a detection using wuauclt /detectnow....

Once I'd installed (using /wuforce) the Agent update, the PC checked into
WSUS, yet reported 0 Updates Required (which was odd, as I'd just approved a
whole bunch load of June's updates yesterday morning)
Then I forced a checkin, and it failed with the same error as before.
This was done on a totally different PC (using a toally different image that
I'd pushed out to 3 PCs last week with problems)
The PC appears in WSUS with status as "Not reported in yet"

WindowsUpdate.log: (sorry for large log spam)

2008-06-18 08:49:57:875 1028 5ac Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-06-18 08:49:57:875 1028 5ac Agent *********** Agent: Initializing
global settings cache ***********
2008-06-18 08:49:57:875 1028 5ac Agent * WSUS server: http://wsus-01
2008-06-18 08:49:57:875 1028 5ac Agent * WSUS status server:
http://ukmy-wsus-01
2008-06-18 08:49:57:875 1028 5ac Agent * Target group: UKMY Computer
Accounts
2008-06-18 08:49:57:875 1028 5ac Agent * Windows Update access disabled: No
2008-06-18 08:49:58:406 1028 538 Report *********** Report: Initializing
static reporting data ***********
2008-06-18 08:49:58:406 1028 538 Report * OS Version = 5.1.2600.2.0.65792
2008-06-18 08:49:58:500 1028 538 Report * Computer Brand = Dell Computer
Corporation
2008-06-18 08:49:58:500 1028 538 Report * Computer Model = OptiPlex SX270

2008-06-18 08:49:58:500 1028 538 Report * Bios Revision = A06
2008-06-18 08:49:58:500 1028 538 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A06
2008-06-18 08:49:58:500 1028 538 Report * Bios Release Date =
2004-09-29T00:00:00
2008-06-18 08:49:58:500 1028 538 Report * Locale ID = 1033
2008-06-18 08:50:00:656 3708 e80 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: +0100) ===========
2008-06-18 08:50:00:656 3708 e80 Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2008-06-18 08:50:00:656 3708 e80 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-18 08:50:00:656 3708 e80 DtaStor Default service for AU is
{00000000-0000-0000-0000-000000000000}
2008-06-18 08:50:00:719 3708 e80 DtaStor Default service for AU is
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2008-06-18 08:50:00:734 1028 5ac Agent WARNING: Failed to read the service
id for re-registration 0x80070002
2008-06-18 08:50:00:734 1028 5ac Agent WARNING: Missing service entry in the
backup data store; cleaning up
2008-06-18 08:50:00:734 1028 5ac DnldMgr Download manager restoring 0
downloads
2008-06-18 08:50:00:734 1028 5ac AU ########### AU: Initializing Automatic
Updates ###########
2008-06-18 08:50:00:734 1028 5ac AU # WSUS server: http://wsus-01
2008-06-18 08:50:00:734 1028 5ac AU # Detection frequency: 22
2008-06-18 08:50:00:734 1028 5ac AU # Target group: UKMY Computer Accounts
2008-06-18 08:50:00:734 1028 5ac AU # Approval type: Scheduled (Policy)
2008-06-18 08:50:00:734 1028 5ac AU # Scheduled install day/time: Every
day at 5:00
2008-06-18 08:50:00:734 1028 5ac AU # Auto-install minor updates: Yes
(Policy)
2008-06-18 08:50:00:734 1028 5ac AU # Will interact with non-admins
(Non-admins are elevated)
2008-06-18 08:50:00:781 1028 5ac AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:50:00:781 1028 5ac AU AU finished delayed initialization
2008-06-18 08:50:00:781 1028 538 AU #############
2008-06-18 08:50:00:781 1028 538 AU ## START ## AU: Search for updates
2008-06-18 08:50:00:781 1028 538 AU #########
2008-06-18 08:50:00:781 1028 538 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {07050A77-AAAC-4E4A-990F-7E234A90D619}]
2008-06-18 08:50:00:781 1028 d4c Agent *************
2008-06-18 08:50:00:781 1028 d4c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:50:00:781 1028 d4c Agent *********
2008-06-18 08:50:00:781 1028 d4c Agent * Online = No; Ignore download
priority = No
2008-06-18 08:50:00:781 1028 d4c 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-18 08:50:00:781 1028 d4c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-18 08:50:00:922 1028 d4c Agent * Found 0 updates and 0 categories
in search; evaluated appl. rules of 0 out of 0 deployed entities
2008-06-18 08:50:00:922 1028 d4c Agent *********
2008-06-18 08:50:00:922 1028 d4c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:50:00:922 1028 d4c Agent *************
2008-06-18 08:50:00:922 1028 ec0 AU >>## RESUMED ## AU: Search for updates
[CallId = {07050A77-AAAC-4E4A-990F-7E234A90D619}]
2008-06-18 08:50:00:922 1028 ec0 AU # 0 updates detected
2008-06-18 08:50:00:922 1028 ec0 AU #########
2008-06-18 08:50:00:922 1028 ec0 AU ## END ## AU: Search for updates
[CallId = {07050A77-AAAC-4E4A-990F-7E234A90D619}]
2008-06-18 08:50:00:922 1028 ec0 AU #############
2008-06-18 08:50:01:734 1028 538 AU ########### AU: Uninitializing
Automatic Updates ###########
2008-06-18 08:50:01:766 1028 538 Report REPORT EVENT:
{A704EAAA-BF7C-4946-BD37-2500A585E0C8} 2008-06-18
08:50:00:781+0100 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
2008-06-18 08:50:01:781 1028 538 Service *********
2008-06-18 08:50:01:781 1028 538 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2008-06-18 08:50:01:781 1028 538 Service *************
2008-06-18 08:50:45:468 1068 108 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: +0100) ===========
2008-06-18 08:50:45:484 1068 108 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2008-06-18 08:50:45:500 1068 108 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-18 08:50:45:468 1068 108 Service *************
2008-06-18 08:50:45:500 1068 108 Service ** START ** Service: Service startup
2008-06-18 08:50:45:500 1068 108 Service *********
2008-06-18 08:50:45:843 1068 108 Misc Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups.dll"
2008-06-18 08:50:46:468 1068 108 Misc Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"
2008-06-18 08:50:46:890 1068 108 Agent * WU client version 7.1.6001.65
2008-06-18 08:50:46:890 1068 108 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-06-18 08:50:46:953 1068 108 Agent * Access type: No proxy
2008-06-18 08:50:46:953 1068 108 Agent * Network state: Connected
2008-06-18 08:51:32:583 1068 108 Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-06-18 08:51:32:583 1068 108 Agent *********** Agent: Initializing
global settings cache ***********
2008-06-18 08:51:32:583 1068 108 Agent * WSUS server: http://wsus-01
2008-06-18 08:51:32:583 1068 108 Agent * WSUS status server:
http://ukmy-wsus-01
2008-06-18 08:51:32:583 1068 108 Agent * Target group: UKMY Computer
Accounts
2008-06-18 08:51:32:583 1068 108 Agent * Windows Update access disabled: No
2008-06-18 08:51:32:598 1068 108 DnldMgr Download manager restoring 0
downloads
2008-06-18 08:51:32:598 1068 108 AU ########### AU: Initializing Automatic
Updates ###########
2008-06-18 08:51:32:598 1068 108 AU # WSUS server: http://wsus-01
2008-06-18 08:51:32:598 1068 108 AU # Detection frequency: 22
2008-06-18 08:51:32:598 1068 108 AU # Target group: UKMY Computer Accounts
2008-06-18 08:51:32:598 1068 108 AU # Approval type: Scheduled (Policy)
2008-06-18 08:51:32:598 1068 108 AU # Scheduled install day/time: Every
day at 5:00
2008-06-18 08:51:32:598 1068 108 AU # Auto-install minor updates: Yes
(Policy)
2008-06-18 08:51:32:598 1068 108 AU # Will interact with non-admins
(Non-admins are elevated)
2008-06-18 08:51:32:598 1068 108 AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:51:33:114 1068 108 Report *********** Report: Initializing
static reporting data ***********
2008-06-18 08:51:33:114 1068 108 Report * OS Version = 5.1.2600.2.0.65792
2008-06-18 08:51:33:145 1068 108 Report * Computer Brand = Dell Computer
Corporation
2008-06-18 08:51:33:145 1068 108 Report * Computer Model = OptiPlex SX270

2008-06-18 08:51:33:145 1068 108 Report * Bios Revision = A06
2008-06-18 08:51:33:145 1068 108 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A06
2008-06-18 08:51:33:145 1068 108 Report * Bios Release Date =
2004-09-29T00:00:00
2008-06-18 08:51:33:145 1068 108 Report * Locale ID = 1033
2008-06-18 08:51:33:223 1068 108 AU AU finished delayed initialization
2008-06-18 08:51:33:223 1068 108 AU #############
2008-06-18 08:51:33:223 1068 108 AU ## START ## AU: Search for updates
2008-06-18 08:51:33:223 1068 108 AU #########
2008-06-18 08:51:33:223 1068 108 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {2311F1DA-EA12-4B63-89F9-681032EE8496}]
2008-06-18 08:51:33:238 1068 e68 Agent *************
2008-06-18 08:51:33:238 1068 e68 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:51:33:238 1068 e68 Agent *********
2008-06-18 08:51:33:238 1068 e68 Agent * Online = No; Ignore download
priority = No
2008-06-18 08:51:33:238 1068 e68 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-18 08:51:33:238 1068 e68 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-18 08:51:33:363 1068 e68 Agent * Found 0 updates and 0 categories
in search; evaluated appl. rules of 0 out of 0 deployed entities
2008-06-18 08:51:33:363 1068 e68 Agent *********
2008-06-18 08:51:33:363 1068 e68 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:51:33:363 1068 e68 Agent *************
2008-06-18 08:51:33:363 1068 e84 AU >>## RESUMED ## AU: Search for updates
[CallId = {2311F1DA-EA12-4B63-89F9-681032EE8496}]
2008-06-18 08:51:33:363 1068 e84 AU # 0 updates detected
2008-06-18 08:51:33:363 1068 e84 AU #########
2008-06-18 08:51:33:363 1068 e84 AU ## END ## AU: Search for updates
[CallId = {2311F1DA-EA12-4B63-89F9-681032EE8496}]
2008-06-18 08:51:33:363 1068 e84 AU #############
2008-06-18 08:51:33:363 1068 e84 AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:51:38:204 1068 e68 Report REPORT EVENT:
{87F6C986-EEDB-45C7-8DBD-63396724C451} 2008-06-18
08:51:32:598+0100 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
2008-06-18 08:52:17:379 1068 55c AU Triggering AU detection through
DetectNow API
2008-06-18 08:52:17:379 1068 55c AU Triggering Online detection
(non-interactive)
2008-06-18 08:52:17:379 1068 108 AU #############
2008-06-18 08:52:17:379 1068 108 AU ## START ## AU: Search for updates
2008-06-18 08:52:17:379 1068 108 AU #########
2008-06-18 08:52:17:379 1068 108 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {381FCB21-D225-4302-9FD0-7212CB5DD64F}]
2008-06-18 08:52:17:379 1068 e68 Agent *************
2008-06-18 08:52:17:379 1068 e68 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:52:17:379 1068 e68 Agent *********
2008-06-18 08:52:17:379 1068 e68 Agent * Online = Yes; Ignore download
priority = No
2008-06-18 08:52:17:379 1068 e68 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-18 08:52:17:379 1068 e68 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-18 08:52:17:754 1068 e68 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-18 08:52:17:816 1068 e68 Misc Microsoft signed: Yes
2008-06-18 08:52:17:910 1068 e68 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-18 08:52:17:925 1068 e68 Misc Microsoft signed: Yes
2008-06-18 08:52:17:925 1068 e68 Setup *********** Setup: Checking whether
self-update is required ***********
2008-06-18 08:52:17:925 1068 e68 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-18 08:52:17:957 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2008-06-18 08:52:17:972 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:52:17:972 1068 e68 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-18 08:52:17:972 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:52:17:972 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:52:17:972 1068 e68 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-18 08:52:17:972 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:52:17:972 1068 e68 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-18 08:52:17:972 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:52:17:988 1068 e68 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-18 08:52:17:988 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:52:17:988 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:52:18:003 1068 e68 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:52:18:003 1068 e68 Setup * IsUpdateRequired = No
2008-06-18 08:52:18:128 1068 e68 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-18 08:52:18:128 1068 e68 PT + ServiceId =

{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =

http://ukmy-wsus-01/ClientWebService/client.asmx
2008-06-18 08:52:18:222 1068 e68 PT WARNING: Cached cookie has expired or
new PID is available
2008-06-18 08:52:18:222 1068 e68 PT Initializing simple targeting cookie,
clientId = 220ce969-7480-4600-ba71-39f9e521d1fe, target group = UKMY Computer
Accounts, DNS name = ukmy-4400387.tlr.thomson.com
2008-06-18 08:52:18:222 1068 e68 PT Server URL =
http://wsus-01/SimpleAuthWebService/SimpleAuth.asmx
2008-06-18 08:52:24:796 1068 e68 PT WARNING: SyncUpdates failure, error =

0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
200

2008-06-18 08:52:24:796 1068 e68 PT WARNING: SOAP Fault: 0x000190
2008-06-18 08:52:24:796 1068 e68 PT WARNING: faultstring:Fault occurred
2008-06-18 08:52:24:796 1068 e68 PT WARNING:
ErrorCode:InternalServerError(5)
2008-06-18 08:52:24:796 1068 e68 PT WARNING: Message:(null)
2008-06-18 08:52:24:796 1068 e68 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-18 08:52:24:796 1068 e68 PT WARNING:
ID:2a7f108f-cb70-4a22-8b6d-6fa5b2b62dae
2008-06-18 08:52:24:796 1068 e68 PT WARNING: PTError: 0x8024400e
2008-06-18 08:52:24:796 1068 e68 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x8024400e
2008-06-18 08:52:24:796 1068 e68 PT WARNING: Sync of Updates: 0x8024400e
2008-06-18 08:52:24:796 1068 e68 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-06-18 08:52:24:796 1068 e68 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-06-18 08:52:24:827 1068 e68 Agent * WARNING: Exit code = 0x8024400E
2008-06-18 08:52:24:827 1068 e68 Agent *********
2008-06-18 08:52:24:827 1068 e68 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:52:24:827 1068 e68 Agent *************
2008-06-18 08:52:24:827 1068 e68 Agent WARNING: WU client failed Searching

for update with error 0x8024400e

2008-06-18 08:52:24:842 1068 e84 AU >>## RESUMED ## AU: Search for updates
[CallId = {381FCB21-D225-4302-9FD0-7212CB5DD64F}]
2008-06-18 08:52:24:842 1068 e84 AU # WARNING: Search callback failed,
result = 0x8024400E
2008-06-18 08:52:24:842 1068 e84 AU # WARNING: Failed to find updates with
error code 8024400E
2008-06-18 08:52:24:842 1068 e84 AU #########
2008-06-18 08:52:24:842 1068 e84 AU ## END ## AU: Search for updates
[CallId = {381FCB21-D225-4302-9FD0-7212CB5DD64F}]
2008-06-18 08:52:24:842 1068 e84 AU #############
2008-06-18 08:52:24:842 1068 e84 AU AU setting next detection timeout to
2008-06-18 12:52:24
2008-06-18 08:52:24:842 1068 e84 AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:52:29:823 1068 e68 Report REPORT EVENT:
{E6BA320E-698C-43C8-A404-EFC1E26B84DA} 2008-06-18
08:52:24:827+0100 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-18 08:56:12:389 1068 ddc AU AU found 0 updates for install at shutdown
2008-06-18 08:56:12:420 252 630 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: +0100) ===========
2008-06-18 08:56:12:420 252 630 Misc = Process: C:\WINDOWS\Explorer.EXE
2008-06-18 08:56:12:420 252 630 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-18 08:56:12:420 252 630 Shutdwn Install at shutdown: no updates to
install
2008-06-18 08:56:19:450 1068 108 AU ########### AU: Uninitializing
Automatic Updates ###########
2008-06-18 08:56:19:497 1068 108 Service *********
2008-06-18 08:56:19:497 1068 108 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2008-06-18 08:56:19:497 1068 108 Service *************
2008-06-18 08:57:03:203 1068 248 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: +0100) ===========
2008-06-18 08:57:03:218 1068 248 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2008-06-18 08:57:03:218 1068 248 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-06-18 08:57:03:203 1068 248 Service *************
2008-06-18 08:57:03:218 1068 248 Service ** START ** Service: Service startup
2008-06-18 08:57:03:218 1068 248 Service *********
2008-06-18 08:57:03:671 1068 248 Agent * WU client version 7.1.6001.65
2008-06-18 08:57:03:671 1068 248 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-06-18 08:57:03:687 1068 248 Agent * Access type: No proxy
2008-06-18 08:57:03:687 1068 248 Agent * Network state: Connected
2008-06-18 08:57:49:737 1068 248 Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-06-18 08:57:49:737 1068 248 Agent *********** Agent: Initializing
global settings cache ***********
2008-06-18 08:57:49:737 1068 248 Agent * WSUS server: http://wsus-01
2008-06-18 08:57:49:737 1068 248 Agent * WSUS status server:
http://ukmy-wsus-01
2008-06-18 08:57:49:737 1068 248 Agent * Target group: UKMY Computer
Accounts
2008-06-18 08:57:49:737 1068 248 Agent * Windows Update access disabled: No
2008-06-18 08:57:49:737 1068 248 DnldMgr Download manager restoring 0
downloads
2008-06-18 08:57:49:752 1068 248 AU ########### AU: Initializing Automatic
Updates ###########
2008-06-18 08:57:49:752 1068 248 AU AU setting next detection timeout to
2008-06-18 07:57:49
2008-06-18 08:57:49:752 1068 248 AU # WSUS server: http://ukmy-wsus-01
2008-06-18 08:57:49:752 1068 248 AU # Detection frequency: 22
2008-06-18 08:57:49:752 1068 248 AU # Target group: UKMY Computer Accounts
2008-06-18 08:57:49:752 1068 248 AU # Approval type: Scheduled (Policy)
2008-06-18 08:57:49:752 1068 248 AU # Scheduled install day/time: Every
day at 5:00
2008-06-18 08:57:49:752 1068 248 AU # Auto-install minor updates: Yes
(Policy)
2008-06-18 08:57:49:752 1068 248 AU # Will interact with non-admins
(Non-admins are elevated)
2008-06-18 08:57:49:752 1068 248 AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:57:49:752 1068 248 AU AU finished delayed initialization
2008-06-18 08:57:50:299 1068 248 Report *********** Report: Initializing
static reporting data ***********
2008-06-18 08:57:50:299 1068 248 Report * OS Version = 5.1.2600.2.0.65792
2008-06-18 08:57:50:393 1068 248 Report * Computer Brand = Dell Computer
Corporation
2008-06-18 08:57:50:393 1068 248 Report * Computer Model = OptiPlex SX270

2008-06-18 08:57:50:393 1068 248 Report * Bios Revision = A06
2008-06-18 08:57:50:393 1068 248 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A06
2008-06-18 08:57:50:393 1068 248 Report * Bios Release Date =
2004-09-29T00:00:00
2008-06-18 08:57:50:393 1068 248 Report * Locale ID = 1033
2008-06-18 08:57:50:455 1068 248 AU #############
2008-06-18 08:57:50:455 1068 248 AU ## START ## AU: Search for updates
2008-06-18 08:57:50:455 1068 248 AU #########
2008-06-18 08:57:50:455 1068 248 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {985EFB81-4612-41D0-840E-9BF7DE41A8E9}]
2008-06-18 08:57:50:533 1068 718 Agent *************
2008-06-18 08:57:50:533 1068 718 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:57:50:533 1068 718 Agent *********
2008-06-18 08:57:50:533 1068 718 Agent * Online = Yes; Ignore download
priority = No
2008-06-18 08:57:50:533 1068 718 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-18 08:57:50:533 1068 718 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-18 08:57:50:565 1068 718 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-18 08:57:50:643 1068 718 Misc Microsoft signed: Yes
2008-06-18 08:57:50:986 1068 718 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-18 08:57:51:002 1068 718 Misc Microsoft signed: Yes
2008-06-18 08:57:51:252 1068 718 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-18 08:57:51:267 1068 718 Misc Microsoft signed: Yes
2008-06-18 08:57:51:330 1068 718 Setup *********** Setup: Checking whether
self-update is required ***********
2008-06-18 08:57:51:330 1068 718 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-18 08:57:51:377 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2008-06-18 08:57:51:377 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:57:51:377 1068 718 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-18 08:57:51:377 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:57:51:377 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:57:51:377 1068 718 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-18 08:57:51:377 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:57:51:392 1068 718 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-18 08:57:51:392 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-06-18 08:57:51:392 1068 718 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-18 08:57:51:392 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:57:51:392 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:57:51:408 1068 718 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-06-18 08:57:51:408 1068 718 Setup * IsUpdateRequired = No
2008-06-18 08:57:52:283 1068 718 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-06-18 08:57:52:283 1068 718 PT + ServiceId =

{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =

http://ukmy-wsus-01/ClientWebService/client.asmx
2008-06-18 08:57:52:392 1068 718 PT WARNING: Cached cookie has expired or
new PID is available
2008-06-18 08:57:52:392 1068 718 PT Initializing simple targeting cookie,
clientId = 220ce969-7480-4600-ba71-39f9e521d1fe, target group = UKMY Computer
Accounts, DNS name = ukmy-4400387.tlr.thomson.com
2008-06-18 08:57:52:392 1068 718 PT Server URL =
http://wsus-01/SimpleAuthWebService/SimpleAuth.asmx
2008-06-18 08:57:55:156 1068 718 PT WARNING: SyncUpdates failure, error =

0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
200

2008-06-18 08:57:55:156 1068 718 PT WARNING: SOAP Fault: 0x000190
2008-06-18 08:57:55:156 1068 718 PT WARNING: faultstring:Fault occurred
2008-06-18 08:57:55:156 1068 718 PT WARNING:
ErrorCode:InternalServerError(5)
2008-06-18 08:57:55:156 1068 718 PT WARNING: Message:(null)
2008-06-18 08:57:55:156 1068 718 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-18 08:57:55:156 1068 718 PT WARNING:
ID:b031366f-4e4d-419e-803c-9d0004d26d88
2008-06-18 08:57:55:156 1068 718 PT WARNING: PTError: 0x8024400e
2008-06-18 08:57:55:156 1068 718 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x8024400e
2008-06-18 08:57:55:156 1068 718 PT WARNING: Sync of Updates: 0x8024400e
2008-06-18 08:57:55:156 1068 718 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-06-18 08:57:55:156 1068 718 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-06-18 08:57:55:172 1068 718 Agent * WARNING: Exit code = 0x8024400E
2008-06-18 08:57:55:172 1068 718 Agent *********
2008-06-18 08:57:55:172 1068 718 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-06-18 08:57:55:172 1068 718 Agent *************
2008-06-18 08:57:55:172 1068 718 Agent WARNING: WU client failed Searching

for update with error 0x8024400e

2008-06-18 08:57:55:172 1068 798 AU >>## RESUMED ## AU: Search for updates
[CallId = {985EFB81-4612-41D0-840E-9BF7DE41A8E9}]
2008-06-18 08:57:55:172 1068 798 AU # WARNING: Search callback failed,
result = 0x8024400E
2008-06-18 08:57:55:172 1068 798 AU # WARNING: Failed to find updates with
error code 8024400E
2008-06-18 08:57:55:172 1068 798 AU #########
2008-06-18 08:57:55:172 1068 798 AU ## END ## AU: Search for updates
[CallId = {985EFB81-4612-41D0-840E-9BF7DE41A8E9}]
2008-06-18 08:57:55:172 1068 798 AU #############
2008-06-18 08:57:55:172 1068 798 AU AU setting next detection timeout to
2008-06-18 12:57:55
2008-06-18 08:57:55:172 1068 798 AU Setting AU scheduled install time to
2008-06-19 04:00:00
2008-06-18 08:57:55:188 1068 718 Report REPORT EVENT:
{DB9D4172-EB8A-4DA3-B4F3-A9911B060E27} 2008-06-18
08:57:55:172+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software

groovyf

unread,

Jun 18, 2008, 4:23:01 AM6/18/08

to

I'm just in process now of tetsing a PC using a different name. But this
can't be a solution as we have to stick to specific naming conventions per
user.

If it's revolving around WSUS server's database how has this suddenly
happened? I don't recall hearing about any updates to WSUS. What will have
caused this? Can't be any client updates as a PC isn't even checking in
correctly to get up-to-date.

groovyf

unread,

Jun 18, 2008, 4:47:01 AM6/18/08

to

Update:
Have imaged another PC, and given it a new name that hasn't ever been used
before ("BADBOY"), and still getting the same error.

According to WSUS it's a duplicate and giving exactly the same "Key" as a
different PC I was using yesterday with a different name. This is causing
real headaches as I can't roll out any new PCs as they won't get updates.

This from SoftwareDistribution.log on WSUS server:

2008-06-18 08:36:00.198
UTC Error w3wp.5 ClientImplementation.SyncUpdates System.ArgumentException:
Item has already been added. Key in dictionary: '9181' Key being added:
'9181'

2008-06-18 08:36:00.198
UTC Warning w3wp.5 SoapUtilities.CreateException ThrowException: actor =
http://ukmy-wsus-01/ClientWebService/client.asmx,
ID=db611dc4-ce69-4afe-99e7-610ed31b8580, ErrorCode=InternalServerError,
Message=, Client=?

Chris

unread,

Jun 18, 2008, 5:11:01 AM6/18/08

to

Hi,

I have the same problem with the key duplication error. It must be a
database issue. Are you running your db on SQL 2005 or the internal DB?
Also is your client Vista SP1 or something else?

Regards

Chris

groovyf

unread,

Jun 18, 2008, 5:34:02 AM6/18/08

to

The WSUS server is running the internal DB that shipped with WSUS3 and my
clients are XP.
All the PCs running XP/Vista that are already listed and functioning in WSUS
are checking-in correctly. I'm finding it's only new PCs that I'm building
and adding to the domain that are causing the issue.

Has there been some essential update to WSUS that may have installed
automatically?
It can't be the client, as the image I'm working from was working fine 2
weeks ago (not added any new windows updates nor re-imaged.) And these new
PCs I'm trying to get working aren't updated as they don't check-in to WSUS.
It all points to the WSUS db, but what's happened? How has this suddenly
occurred?

Chris

unread,

Jun 18, 2008, 6:52:01 AM6/18/08

to

Yes it has 'suddenly' ocurred for me too. This is probably the first time I
have added a new client since I installed SP1 onto the WSUS server but the
existing clients are working fine. It seems as though there is an issue with
the keys in the database. Mine runs on SQL 2005 but the problem ocurrs with
the internal one too so it must be the code which is run when a new client is
created. But when has this code changed? I'd have said in SP1 but your's
isn't on SP1 so that's not it.

Are there any Microsoft employees reading this? Can you tell us if this is
a known issue or should I log it?

groovyf

unread,

Jun 18, 2008, 7:13:01 AM6/18/08

to

Actually, I should have mentioned my WSUS3 server is on SP1, and has been for
a while now, and I've certainly added new clients since upgrading to SP1.
I had a thought that maybe the internal DB had reached its limits somehow,
but it's only 1.6GB in size with around 240 clients. And now you've said
you're using SQL 2005 and getting same problems so I doubt the internal DB is
at fault.

Chan@discussions.microsoft.com Ray Chan

unread,

Jun 18, 2008, 7:57:01 AM6/18/08

to

I just ran into the same issue. Have about 70 clients all running XP SP2
connecting to a 2003 server. All of them are working fine, however, I just
started building a couple of new machines and noticed they don't report with
the same error. After some further investigating, I realized it's Office
2003 that's causing the problem. When I uninstall Office, it reports
normally and grab updates. But once I reinstall it, it can't connect. I've
even tried manually removing each part of Office to pinpoint the issue but it
appears once any part of it is installed it breaks the service. I've also
tried all the fixes mentioned here to no avail.

Please help...

Chris

unread,

Jun 18, 2008, 8:05:01 AM6/18/08

to

Thinking about when this problem started, yesterday when I was first setting
up this machine on the network, it appeared to have frozen so I hit the power
switch to force it to power down. I expect it was in the middle of creating
something in the database and because that didn't fully complete it has
caused problems, but then any stored procedures etc would have been run on
the server not the client so it shouldn't matter that the client was shut
down!!

I can still run the updates from the Microsoft website so it is the WSUS
server at fault not the client. It's just finding how to remove the
duplicated item that is causing the problem...

Ray Chan

unread,

Jun 18, 2008, 10:54:00 AM6/18/08

to

Hi Chris, does your image have Office pre-installed?

Chris

unread,

Jun 18, 2008, 11:04:01 AM6/18/08

to

Hi Ray,

Yes the laptop factory installed image has Office 2007 OEM which I haven't
activated yet.

Why do you ask?

Regards

Chris

Williamt

unread,

Jun 18, 2008, 11:20:01 AM6/18/08

to

I have exactly the same problem on a new PC, just added to the domain (SBS
2003). The PC has Windows XP and I updated it to SP2 before adding it to the
domain.
It also has MS Office 2007 on the PC (Not 2003 as others seem to mention
might be involved).

The Windows Update via the WWW still functions correctly, so I too would
assume it's a server side problem...

Any help appreciated.

Ray Chan

unread,

Jun 18, 2008, 11:30:00 AM6/18/08

to

Can you try uninstalling it and see if it'll register with WSUS? That's the
only way it works for me and I just wanted to see if others are having the
same issue.

Chris

unread,

Jun 18, 2008, 11:49:02 AM6/18/08

to

Unbelievable! I can't understand why Office is stopping it working. I
uninstalled the Office 2007 Small Business edition (and all the components
that come with it) and it now connects to the local WSUS. I am just waiting
for it to provide a status report and then will see if I can reintroduce
Office to it...

The last time we bought some PC's we had Office pre-installed and no
problems but that was probably before we upgraded to WSUS3 SP1.

Ah, it's just finished the status report. Now for Office.

Thanks Ray,

Chris

Ray Chan

unread,

Jun 18, 2008, 12:05:01 PM6/18/08

to

Reinstalling Office afterwards breaks it again for me. Hopefully it works
for you.

Chris

unread,

Jun 18, 2008, 12:27:01 PM6/18/08

to

So far so good, I have got the default installation of Word, Excel, Outlook
etc installed from disk 1 and WSUS still works. I don't want Business
Contact Manager etc so don't need to install any more of office. From
memory, Dell had installed PowerPoint Viewer, Office 2003 Web Components and
something else which just wasn't necessary. Also I've removed the SQL stuff
for BCM.

This was very weird, perhaps something affected the way the client was
posting the SOAP request to the WSUS server which made it look like a server
issue, but thankfully it is a problem with the client.

Thanks for posting your help Ray, I hope you can find the solution too, it
must be around Office for sure.

APlus

unread,

Jun 18, 2008, 2:39:04 PM6/18/08

to

My problem is addressed at:
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx.

Thx 2 Harry and Wilfried.

A+

groovyf

unread,

Jun 18, 2008, 6:42:01 PM6/18/08

to

Someone (mendocinosunrise) has posted something rather interesting over at
www.wsus.info forums. I've yet to try this, but shall do so in the morning.
I'll paste it here:

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."

groovyf

unread,

Jun 19, 2008, 3:41:01 AM6/19/08

to

Have just performed the above (thanks to mendocinosunrise), and all is back
to normal.

Alexander

unread,

Jun 19, 2008, 6:48:08 AM6/19/08

to

This definetely works!! Thanks to everybody!

(Mention the misspelling in step "c": I guess the author meant to select
Decline, not Approve)

"groovyf" <gro...@discussions.microsoft.com> wrote in message
news:80F74FB4-109B-4D93...@microsoft.com...

Seeländer@discussions.microsoft.com Robin Seeländer

unread,

Jun 27, 2008, 11:00:01 AM6/27/08

to

Hi Eddie,

i tried to load down your tool, but it is offline at the moment.
Is there a chance to get your tool soon.
We do need it urgently.
We have some clients who show the described difficulties in connecting to
the server succesfully.

here is an line from our lofgiles.

SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error
code = 400, HTTP status code = 200

Any help qould be greatly appreciated.

Regards,
Robin

"Eddie Bowers [MSFT]" wrote:

> OK, well lets try the shotgun approach to see what happnes. Run my tool
> from:
> http:\\www.codeplex.com\aureset
>
>
> Eddie Bowers
> Security Support
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no rights

PA Bear [MS MVP]

unread,

Jun 27, 2008, 11:52:01 AM6/27/08

to

Eddie's utility has been withdrawn for review.

Are your problems only on machines where WinXP SP3 has been installed (which
is the subject of this thread)?

Do the clients update via WSUS or Windows Update?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

Robin Seeländer wrote:
> i tried to load down your tool, but it is offline at the moment.
> Is there a chance to get your tool soon.
> We do need it urgently.
> We have some clients who show the described difficulties in connecting to
> the server succesfully.
>
> here is an line from our lofgiles.
> SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error
> code = 400, HTTP status code = 200
>

Christopher Hill

unread,

Jun 27, 2008, 12:31:01 PM6/27/08

to

Hi Robin,

Have you checked that your issue isn't fixed by:

http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

--
Chris Hill
ICT Technician - Colchester Royal Grammar School

"PA Bear [MS MVP]" wrote:

PA Bear [MS MVP]

unread,

Jun 27, 2008, 12:37:01 PM6/27/08

to

Do we know Robin's using WSUS?

Christopher Hill wrote:
> Hi Robin,
>
> Have you checked that your issue isn't fixed by:
>
> http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx
>

John

unread,

Jul 23, 2008, 8:04:01 PM7/23/08

to

All,

The fix in the blog was the trick for me too:
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

Thank you all. We've had our share lately!
John

Happy russian admin

unread,

Aug 14, 2008, 2:32:00 AM8/14/08

to

Hi!

The problem on the server side with declined (!) "Office 2003 Service Pack
1" update.
I've solved it by redecline the update.

http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

--
Happy russian admin

"Alexander" wrote:

> Hello,
>
> We have a corporate WSUS server that all workstations use for getting
> updates.
>
> After installing SP3 on a new Windows XP box, that box stopped getting
> updates. Its WindowsUpdate.log contains SOAP errors:

> ....

Happy russian admin

unread,

Aug 14, 2008, 2:35:01 AM8/14/08

to

Hi!

Redecline (aprove and decline) the now declined update "Office 2003 Service
Pack 1" on the server side.

http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspxHi!

--
Happy russian admin

"Alexander" wrote:

> Hello,
>
> We have a corporate WSUS server that all workstations use for getting
> updates.
>
> After installing SP3 on a new Windows XP box, that box stopped getting
> updates. Its WindowsUpdate.log contains SOAP errors:
> ....

> 2008-06-03 19:07:43:222 1052 2f8 Setup * IsUpdateRequired = No
> 2008-06-03 19:07:43:300 1052 2f8 PT +++++++++++ PT: Synchronizing
> server updates +++++++++++
> 2008-06-03 19:07:43:300 1052 2f8 PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://sus:8530/ClientWebService/client.asmx
> 2008-06-03 19:07:43:300 1052 2f8 Agent Switching to hardware-verified
> ClientId.
> 2008-06-03 19:07:43:316 1052 2f8 PT WARNING: Cached cookie has expired
> or new PID is available
> 2008-06-03 19:07:43:628 1052 2f8 Agent Created new random SusClientId
> cf9b00aa-97a6-4a28-94e2-efdc0c094a7e. Old Id:
> 71b1e082-140e-45da-ad43-ba80b1e0cb59.
> 2008-06-03 19:07:43:628 1052 2f8 PT Initializing simple targeting
> cookie, clientId = cf9b00aa-97a6-4a28-94e2-efdc0c094a7e, target group = ,
> DNS name = comp.domain.biz
> 2008-06-03 19:07:43:628 1052 2f8 PT Server URL =
> http://sus:8530/SimpleAuthWebService/SimpleAuth.asmx

> 2008-06-03 19:07:46:472 1052 2f8 PT WARNING: SyncUpdates failure, error

> = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code
> = 200

complexmind

unread,

Jan 13, 2010, 12:21:01 PM1/13/10

to

This fixed it for me!!
--
complexmind

"PA Bear [MS MVP]" wrote:

> Forwarded to WSUS newsgroup
> (microsoft.public.windows.server.update_services) via crosspost as a
> convenience to OP.
>
> On the web:
> http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services
>
> In your newsreader:
> news://msnews.microsoft.com/microsoft.public.windows.server.update_services
>
> NB: Eddie Bowers [MSFT] posted a reply to this thread in WU NG:
>
> <QP>
> Try this.
> net stop wuauserv
> net stop bits
> rename the c:\windows\software distribution folder
> net start bits
> net start wuauserv
>
> If this doesn't fix it, then force a reinstall of the agent by downloading
> http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.1.6001.65/WindowsUpdateAgent30-x86.exe
> and installing with the /wuforce switch
> </QP>
> --
> ~PA Bear
>
>

> Alexander wrote:
> > Hello,
> >
> > We have a corporate WSUS server that all workstations use for getting
> > updates.
> >
> > After installing SP3 on a new Windows XP box, that box stopped getting
> > updates. Its WindowsUpdate.log contains SOAP errors:
> > ...

PA Bear [MS MVP]

unread,

Jan 13, 2010, 1:53:05 PM1/13/10

to

Thank you for replying to a thread from June 2008.

How do I reset Windows Update components?
http://support.microsoft.com/kb/971058

...how to obtain the latest Windows Update Agent [v7.4.7600.226; Aug-09]
http://support.microsoft.com/kb/946928

complexmind wrote:
> This fixed it for me!!
>

>> ...NB: Eddie Bowers [MSFT] posted a reply to this thread in WU NG:

>>
>> <QP>
>> Try this.
>> net stop wuauserv
>> net stop bits
>> rename the c:\windows\software distribution folder
>> net start bits
>> net start wuauserv
>>
>> If this doesn't fix it, then force a reinstall of the agent by

>> downloading...
<snip>

Looneyspeaches

unread,

Jun 27, 2010, 6:40:08 PM6/27/10

to

"Alexander" wrote:

> Hello,
>
> We have a corporate WSUS server that all workstations use for getting
> updates.
>
> After installing SP3 on a new Windows XP box, that box stopped getting
> updates. Its WindowsUpdate.log contains SOAP errors:

> ....

Shenan Stanley

unread,

Jun 27, 2010, 7:23:50 PM6/27/10

to

Alexander wrote:
<snipped>

Looneyspeaches wrote:
>

Whew. Good thing "Looneyspeaches" responded or that posting (started in
June 2008) would have ended in June/August 2008 like it originally did.

Wait a minute...
http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/ab9da9bd166843c1/

Looneyspeaches,

Anything you wanted to add two years in?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html