GetCookie failure error 0x8024400D and PTError 0x80244015

miércoles, 01 de julio de 2009 15:31

LeonardoFagundes

Inicie sesión para votar

Dear Folks

Clients does not report their status, do not receive updates.

1- It's not the office 2003 issue. This is WSUS 2.0.0.2620
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

2- wuauclt /resetauthorization /detectnow did not change anything, as it only triggers a RefreshCookie, which leads to the same problem.

3- clientdiag does not report any error.

4- Not the SUSClientID issue. I have tried deleting SusclientId and the SusClientIdValidation registry keys in some clients, with no success.

5- I dont have load balanced servers
http://blogs.technet.com/sus/archive/2008/10/29/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors.aspx.

6- kb898708 is irrelevant, as I'm running Windows 2003 SP2. http://support.microsoft.com/kb/898708/en-us

7- If I direct a wsus client to a "healthy" wsus server, updates are downloaded normally

8- The process w3wp.exe for "WsusPool" is consuming a lot of CPU on the server. It's never consuming less than 50%.
If I stop application pool "WsusPool" in IIS Manager, cpu goes down to normal levels.

I'm convinced this is a server-related problem, maybe something with ASP.net... (It's in version 2.0.50727).

Any ideas?
Thanks a lot!

WindowsUpdate.log

-----------------------------------------------------------

2009-07-01	07:05:07:021	1112	92c	PT	WARNING: Cached cookie has expired or new PID is available

2009-07-01	07:05:07:021	1112	92c	PT	Initializing simple targeting cookie, clientId = 717cea0c-9ad8-4251-9216-114e412c68a5, target group = R04-Desktops, DNS name = brsao01d20516xp.dom.corp

2009-07-01	07:05:07:021	1112	92c	PT	  Server URL = http://brsao01ps01k3:8530/SimpleAuthWebService/SimpleAuth.asmx

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: SOAP Fault: 0x00012c

2009-07-01	07:05:07:067	1112	92c	PT	WARNING:     faultstring:Fault occurred

2009-07-01	07:05:07:067	1112	92c	PT	WARNING:     ErrorCode:InvalidCookie(1)

2009-07-01	07:05:07:067	1112	92c	PT	WARNING:     Message:(null)

2009-07-01	07:05:07:067	1112	92c	PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

2009-07-01	07:05:07:067	1112	92c	PT	WARNING:     ID:0890d10c-8c47-4808-8668-bfe600f9f8ef

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: PTError: 0x80244015

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: GetCookie_WithRecovery failed : 0x80244015

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: RefreshCookie failed: 0x80244015

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: RefreshPTState failed: 0x80244015

2009-07-01	07:05:07:067	1112	92c	PT	WARNING: Sync of Updates: 0x80244015

--------------------------------------------------------



SoftwareDistribution.log

-----------------------------------------------------------

2009-07-01 12:00:10.898 UTC	Error	w3wp.31	ClientImplementation.RefreshCache	System.Threading.ThreadAbortException: Thread was being aborted.

   at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)

   at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)

   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)

   at System.Threading.WaitHandle.WaitOne()

   at Microsoft.UpdateServices.Internal.SyncUpdatesHelper.RefreshClientCache(UpdateIdentity[] globalIds)

   at Microsoft.UpdateServices.Internal.ClientImplementation.RefreshCache(Cookie cookie, UpdateIdentity[] globalIds)

   at Microsoft.UpdateServices.Internal.ClientImplementation.RefreshCache(Cookie cookie, UpdateIdentity[] globalIds)

   at Microsoft.UpdateServices.Internal.Client.RefreshCache(Cookie cookie, UpdateIdentity[] globalIDs)

   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.RequestQueue.WorkItemCallback(Object state)

   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)

   at System.Threading.ExecutionContext.runTryCode(Object userData)

   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

----------------------------------------



Sometimes WindowsUpdate.log reports:

--------------------------------------------------------

2009-07-01	07:05:07:146	1112	92c	PT	WARNING: Cached cookie has expired or new PID is available

2009-07-01	07:05:07:146	1112	92c	PT	Initializing simple targeting cookie, clientId = 717cea0c-9ad8-4251-9216-114e412c68a5, target group = R04-Desktops, DNS name = brsao01d20516xp.dom.corp

2009-07-01	07:05:07:146	1112	92c	PT	  Server URL = http://brsao01ps01k3:8530/SimpleAuthWebService/SimpleAuth.asmx

2009-07-01	07:06:07:739	1112	92c	Misc	WARNING: Send failed with hr = 80072ee2.

2009-07-01	07:06:07:739	1112	92c	Misc	WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>

2009-07-01	07:06:07:739	1112	92c	PT	  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0

2009-07-01	07:06:07:739	1112	92c	PT	  + Caller provided credentials = No

2009-07-01	07:06:07:739	1112	92c	PT	  + Impersonate flags = 0

2009-07-01	07:06:07:739	1112	92c	PT	  + Possible authorization schemes used = 

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: RefreshCache failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: PTError: 0x80072ee2

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: RefreshCache_WithRecovery failed: 0x80072ee2

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: SyncCache: Emergency cleanup of the ServerUpdateInfo due to failure in RefreshCache

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: SyncCache failed : 0x80072ee2

2009-07-01	07:06:07:739	1112	92c	PT	WARNING: SyncServerUpdatesInternal failed: 0x80072ee2

2009-07-01	07:06:07:739	1112	92c	Agent	  * WARNING: Failed to synchronize, error = 0x80072EE2

2009-07-01	07:06:08:396	1112	92c	Agent	  * WARNING: Exit code = 0x80072EE2

--------------------------------------------------------

Leonardo Fagundes

EditadoLeonardoFagundes miércoles, 01 de julio de 2009 17:13undisclosure...

Respuestas

miércoles, 07 de octubre de 2009 14:25Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
Hello Lawrence,

Did you get an answer?

Leonardo Fagundes

Just to close up this thread... I did get an answer.

Office 2003 SP1 was removed from the WSUS catalog entirely.

I'm told that the new policy, going forward, is that service packs which have expired mainstream support will not be maintained in the WSUS catalog.

The official "fix" for this issue is:
1. Use WSUS 3 Service Pack 1 (well, now, Service Pack 2)
2. Apply KB954960 to the WSUS 3 SP1 server.

Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com
- Marcado como respuestaLawrence GarvinMVP, Moderadormiércoles, 07 de octubre de 2009 14:25
- Responder
- Citar

Todas las respuestas

miércoles, 01 de julio de 2009 19:21Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
Dear Folks
Clients does not report their status, do not receive updates.

1- It's not the office 2003 issue. This is WSUS 2.0.0.2620
http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx

Before we go any farther.... can we get some perspective on why we're troubleshooting a =WSUS2SP1= scenario, and why the WSUS Server has not yet been upgraded to WSUS3SP1. To be honest, support for WSUS2SP1 ended sixty days go (4/30/09), and very few people here have the resources to do much diagnostics or troubleshooting on a WSUS2 scenario.

To that point, the "Office 2003" issue occurs on _ANY_ version of WSUS, but was REPAIRED in WSUS v3 SP1. So the primary fix for this issue is to upgrade to WSUS3SP1. If you choose not to upgrade, the fix is documented in KB954960 and requires performance of a manual procedure. You should perform that procedure even if you THINK it doesn't apply -- it takes 30 seconds to do -- and so far, 90% of the people who thought it wasn't applicable found out it was -- and fixed their issue.

7- If I direct a wsus client to a "healthy" wsus server, updates are downloaded normally

This statement is a pretty strong indication that the problem is with the specific WSUS Server, and is an even stronger statement as to why you should comply with KB954960.

I'm convinced this is a server-related problem

At least we do agree on this point. :-)
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
- Responder
- Citar
jueves, 02 de julio de 2009 8:07Eric Zhang - MSFTMSFT, Moderador

0
Inicie sesión para votar
Hi Leonardo,

I agreed with Lawrence, upgrading to WSUS 3.0 SP1 is good solution for your problem.

You can download WSUS 3.0 SP1 installation file from this website:

Download details: Windows Server Update Services 3.0 SP1

http://www.microsoft.com/downloads/details.aspx?FamilyID=f87b4c5e-4161-48af-9ff8-a96993c688df&DisplayLang=en
- Responder
- Citar
jueves, 02 de julio de 2009 14:19LeonardoFagundes

0
Inicie sesión para votar
Ok, I agree. I'll upgrade to WSUS 3 as soon as possible, that's certainly the best approach.

But for now I need to find a way to deliver patches in the current version.

I could not perform the workaround mentioned in KB954960. I get this error:

-----------------------------
Update: Office 2003 Service Pack 1
Computer group: All Computers
Error: The selected update has expired and cannot be approved for installation or detection. It is recommended you decline this update.
-----------------------------

Is there any flag I can manipulate in the database to allow this approval?

A further question would be: Will the workaround mentioned in KB954960 be valid for WSUS 2?

Thanks a lot for your help, you guys rock!
Leonardo Fagundes
- Responder
- Citar
jueves, 02 de julio de 2009 15:05Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
No Leonardo.. the only "supported" remediation for WSUS v2 is to upgrade.

Further, since this is a critical error in your system, there is no viable 'workaround' because until the problem is fixed, your clients will not detect and install updates. One might even say it's not a critical error.. it's a fatal error.

And, I apologize for misleading you about the manual fix.. it is limited to WSUS 3.0 RTM systems (according to the KB article).

However, the error you encountered is not expected. There are several revisions to the Office 2003 SP1 package. The original package was released in May 2005, with subsequent revisions in June 2008 and October 2008. After declining the update, if you're unable to approve it (the update is still a current update), that would suggest that perhaps you've not synchronized the most recent (Oct 2008) revision -- it's the June 2008 and May 2005 revisions that are expired.

Please verify that you have the Oct 2008 revision on your system. If not, you'll need to verify that Office 2003 is a selected Product Category and resynchronize.

Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
- Responder
- Citar
jueves, 02 de julio de 2009 17:54LeonardoFagundes

0
Inicie sesión para votar
Hey Lawrence,

I appreciate you help.

This update has two revisions:

56 Office 2003 Service Pack 1 10/9/2008 Declined
55 Office 2003 Service Pack 1 6/10/3008 Declined

The revision you mentioned is present.

Interestingly, there is also this revision No 55 from the future. Isn't it the cause of the problem?

Leonardo Fagundes
- Responder
- Citar
jueves, 02 de julio de 2009 19:21Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
Hey Lawrence,

I appreciate you help.

This update has two revisions:

56 Office 2003 Service Pack 1 10/9/2008 Declined
55 Office 2003 Service Pack 1 6/10/3008 Declined

The revision you mentioned is present.

Interestingly, there is also this revision No 55 from the future. Isn't it the cause of the problem?

Leonardo Fagundes
The package actually has four revisions in total...

Rev 52 (5/12/2005)
Rev 53 (6/10/2008)
Rev 55 (6/10/3008)
Rev 56 (10/9/2008)

I originally thought the 6/10/2008 rev was a replacement of the 6/10/3008 error (which is obviously a typo in the metadata Release Date value), but the Rev numbers contradict that thought -- since Rev 55 most certainly came after Rev 52.

The problem here, I now see, is that =Rev 56= .. the latest revision.. is EXPIRED. That shouldn't be the case, and that may still be an error in the metadata. I'll see if I can get an answer to that question. This is why you're unable to Approve the update at this time.

Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
- Responder
- Citar
lunes, 06 de julio de 2009 11:34LeonardoFagundes

0
Inicie sesión para votar
Hello Lawrence,

Did you get the chance to look into it?

Thanks in advance
Leonardo Fagundes
- Responder
- Citar
lunes, 06 de julio de 2009 22:10Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
I sent an email to my contact at the WSUS product team and I'm waiting on a response. No doubt they'll have to ask the Office team, so it could take a few days for the communications to get passed around.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
- Responder
- Citar
miércoles, 15 de julio de 2009 14:17LeonardoFagundes

0
Inicie sesión para votar
Hello Lawrence,

Did you get an answer?
Leonardo Fagundes
- Responder
- Citar
jueves, 16 de julio de 2009 6:13Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
Not yet, but thank you for the reminder. I'll bump the question and see if there's any additional information.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
- Responder
- Citar
miércoles, 07 de octubre de 2009 13:54rasczak

0
Inicie sesión para votar
I don't know if you've already found an answer to this issue but with the getCookie error = 0x822004D I did the following.

Opened IE > tools > internet options > delete all (cookies and everything else)

Opened cmd prompt > wuauclt /resetauthorization /detectnow

this cleared up my expired cookie issue. Now just trying to script this.

hope this helps.
- Responder
- Citar
miércoles, 07 de octubre de 2009 14:21Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
with the getCookie error = 0x822004D I did the following.

Opened IE > tools > internet options > delete all (cookies and everything else)

Opened cmd prompt > wuauclt /resetauthorization /detectnow

this cleared up my expired cookie issue. Now just trying to script this.

hope this helps.

The activity with IE / Cookies is not necessary. This is not an IE-type cookie.

The /resetauthorization flag is expressly designed for expiring the WUAgent cookie, so I'm glad to hear it worked for you.

I'm not sure why you're posting that to this thread, though. There are MANY possible causes for an 0x8024400D error, and this thread addresses a very specific cause, which today can be summarized as "Not having a fully patched WSUS Server"

As for scripting your command; if the WUAgent is working properly, there should be no need to script this command. The cookie is automatically expired after ~60 minutes. The only time I've seen this to be problematic is when environments are configured to use one-hour detection intervals -- which really should only be used for diagnostic purposes. A one-hour detection interval almost guarantees that the targeting cookie will never expire.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com
- Responder
- Citar
miércoles, 07 de octubre de 2009 14:25Lawrence GarvinMVP, Moderador

0
Inicie sesión para votar
Hello Lawrence,

Did you get an answer?

Leonardo Fagundes

Just to close up this thread... I did get an answer.

Office 2003 SP1 was removed from the WSUS catalog entirely.

I'm told that the new policy, going forward, is that service packs which have expired mainstream support will not be maintained in the WSUS catalog.

The official "fix" for this issue is:
1. Use WSUS 3 Service Pack 1 (well, now, Service Pack 2)
2. Apply KB954960 to the WSUS 3 SP1 server.

Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com
- Marcado como respuestaLawrence GarvinMVP, Moderadormiércoles, 07 de octubre de 2009 14:25
- Responder
- Citar