Jump to content
Microsoft Windows Bulletin Board

Automatic updates stopped working after SP3 has been installed

Guest Alexander

By Guest Alexander
in Archives (READ ONLY)

 Share

Recommended Posts

Guest Ray Chan

Guest Ray Chan

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

Guest Chris

Posted
Posted

Hi Ray,

 

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

activated yet.

 

Why do you ask?

 

Regards

 

Chris

 

 

"Ray Chan" wrote:

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

Guest Williamt

Guest Williamt

Posted
Posted

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.

 

> "APlus" wrote:

> 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!

>

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

> > http://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:

> > > ...

> > > 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!

> >

> >

Guest Ray Chan

Guest Ray Chan

Posted
Posted

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" wrote:

> Hi Ray,

>

> Yes the laptop factory installed image has Office 2007 OEM which I haven't

> activated yet.

>

> Why do you ask?

>

> Regards

>

> Chris

>

>

> "Ray Chan" wrote:

>

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

Guest Chris

Guest Chris

Posted
Posted

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" wrote:

> 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" wrote:

>

> > Hi Ray,

> >

> > Yes the laptop factory installed image has Office 2007 OEM which I haven't

> > activated yet.

> >

> > Why do you ask?

> >

> > Regards

> >

> > Chris

> >

> >

> > "Ray Chan" wrote:

> >

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

Guest Ray Chan

Guest Ray Chan

Posted
Posted

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

for you.

 

"Chris" wrote:

> 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" wrote:

>

> > 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" wrote:

> >

> > > Hi Ray,

> > >

> > > Yes the laptop factory installed image has Office 2007 OEM which I haven't

> > > activated yet.

> > >

> > > Why do you ask?

> > >

> > > Regards

> > >

> > > Chris

> > >

> > >

> > > "Ray Chan" wrote:

> > >

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

Guest Chris

Guest Chris

Posted
Posted

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.

 

Regards

 

Chris

 

 

"Ray Chan" wrote:

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

> for you.

>

> "Chris" wrote:

>

> > 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" wrote:

> >

> > > 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" wrote:

> > >

> > > > Hi Ray,

> > > >

> > > > Yes the laptop factory installed image has Office 2007 OEM which I haven't

> > > > activated yet.

> > > >

> > > > Why do you ask?

> > > >

> > > > Regards

> > > >

> > > > Chris

> > > >

> > > >

> > > > "Ray Chan" wrote:

> > > >

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

Guest APlus

Guest APlus

Posted
Posted

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+

 

 

"Williamt" wrote:

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

>

>

> > "APlus" wrote:

>

> > 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!

> >

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

> > > http://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:

> > > > ...

> > > > 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!

> > >

> > >

Guest groovyf

Guest groovyf

Posted
Posted

Someone (mendocinosunrise) has posted something rather interesting over at

http://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."

 

 

 

"Ray Chan" wrote:

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

>

Guest groovyf

Guest groovyf

Posted
Posted

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

to normal.

Guest Alexander

Guest Alexander

Posted
Posted

This definetely works!! Thanks to everybody!

 

(Mention the misspelling in step "c": I guess the author meant to select

Decline, not Approve)

 

"groovyf" <groovyf@discussions.microsoft.com> wrote in message

news:80F74FB4-109B-4D93-87C2-30CED43615F8@microsoft.com...

> Someone (mendocinosunrise) has posted something rather interesting over at

> http://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."

>

>

>

> "Ray Chan" wrote:

>

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

>>

  • 2 weeks later...
Guest Robin Seeländer

Guest Robin Seeländer

Posted
Posted

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:\\http://www.codeplex.com\aureset

>

>

> Eddie Bowers

> Security Support

> Microsoft Corporation

>

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

Guest PA Bear [MS MVP]

Guest PA Bear [MS MVP]

Posted
Posted

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

>

> "Eddie Bowers [MSFT]" wrote:

>> OK, well lets try the shotgun approach to see what happnes. Run my tool

>> from:

>> http:\\http://www.codeplex.com\aureset

Guest Christopher Hill

Guest Christopher Hill

Posted
Posted

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:

> 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

> >

> > "Eddie Bowers [MSFT]" wrote:

> >> OK, well lets try the shotgun approach to see what happnes. Run my tool

> >> from:

> >> http:\\http://www.codeplex.com\aureset

>

>

Guest PA Bear [MS MVP]

Guest PA Bear [MS MVP]

Posted
Posted

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

>

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

>>>

>>> "Eddie Bowers [MSFT]" wrote:

>>>> OK, well lets try the shotgun approach to see what happnes. Run my tool

>>>> from:

>>>> http:\\http://www.codeplex.com\aureset

  • 4 weeks later...
Guest John

Guest John

Posted
Posted

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

 

 

 

"Alexander" wrote:

> This definetely works!! Thanks to everybody!

>

> (Mention the misspelling in step "c": I guess the author meant to select

> Decline, not Approve)

>

> "groovyf" <groovyf@discussions.microsoft.com> wrote in message

> news:80F74FB4-109B-4D93-87C2-30CED43615F8@microsoft.com...

> > Someone (mendocinosunrise) has posted something rather interesting over at

> > http://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."

> >

> >

> >

> > "Ray Chan" wrote:

> >

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

> >>

>

>

>

  • 3 weeks later...
Guest Happy russian admin

Guest Happy russian admin

Posted
Posted

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:

> ....

> 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!

>

>

>

Guest Happy russian admin

Guest Happy russian admin

Posted
Posted

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

> 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!

>

>

>

 Share
Go to topic listing
×
×
  • Create New...