Automatic updates stopped working after SP3 has been installed

  • Thread starter Thread starter Alexander
  • Start date Start date
RE: Automatic updates stopped working after SP3 has been installed

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

> 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" wrote:
>
> > 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'
> > 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-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=?
> >
 
RE: Automatic updates stopped working after SP3 has been installed

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

> 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" wrote:
>
> > 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" wrote:
> >
> > > 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'
> > > 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-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=?
> > >
 
RE: Automatic updates stopped working after SP3 has been installed

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.

"Chris" wrote:

> 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" wrote:
>
> > 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" wrote:
> >
> > > 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" wrote:
> > >
> > > > 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'
> > > > 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-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=?
> > > >
 
RE: Automatic updates stopped working after SP3 has been installed

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

"groovyf" wrote:

> 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
>
> "Christopher Hill" wrote:
>
> > 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/W...lone/7.1.6001.65/WindowsUpdateAgent30-x86.exe
> > http://download.windowsupdate.com/W...lone/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
> >
> >
>
 
RE: Automatic updates stopped working after SP3 has been installed

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


"groovyf" wrote:

> 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.
>
> "Chris" wrote:
>
> > 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" wrote:
> >
> > > 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" wrote:
> > >
> > > > 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" wrote:
> > > >
> > > > > 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'
> > > > > 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-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=?
> > > > >
 
RE: Automatic updates stopped working after SP3 has been installed

Hi Chris, does your image have Office pre-installed?
 
RE: Automatic updates stopped working after SP3 has been installed

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?
 
Re: Automatic updates stopped working after SP3 has been installed

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/communitie...crosoft.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/W...lone/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!
> >
> >
 
RE: Automatic updates stopped working after SP3 has been installed

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?
 
RE: Automatic updates stopped working after SP3 has been installed

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?
 
RE: Automatic updates stopped working after SP3 has been installed

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?
 
RE: Automatic updates stopped working after SP3 has been installed

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?
 
Re: Automatic updates stopped working after SP3 has been installed

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/communitie...crosoft.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/W...lone/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!
> > >
> > >
 
RE: Automatic updates stopped working after SP3 has been installed

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



"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.
>
 
RE: Automatic updates stopped working after SP3 has been installed

Have just performed the above (thanks to mendocinosunrise), and all is back
to normal.
 
Re: Automatic updates stopped working after SP3 has been installed

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
> 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.
>>
 
Re: Automatic updates stopped working after SP3 has been installed

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
 
Re: Automatic updates stopped working after SP3 has been installed

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:\\www.codeplex.com\aureset
 
Re: Automatic updates stopped working after SP3 has been installed

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:\\www.codeplex.com\aureset
>
>
 
Re: Automatic updates stopped working after SP3 has been installed

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:\\www.codeplex.com\aureset
 
Back
Top