Cached cookie has expired or new PID is available

[Troy Bruder]

Anyone have any idea what this error means? Suddenly my WSUS 3.0 updates
have stopped on 1/2 my Win2k3 servers:

WARNING: Cached cookie has expired or new PID is available

Troy

[Harry Johnston [MVP]]

Post by Troy Bruder
Anyone have any idea what this error means? Suddenly my WSUS 3.0 updates
WARNING: Cached cookie has expired or new PID is available

This message doesn't usually indicate an error condition.

Type this at the command line on an affected system:

wuauclt /detectnow

wait ten minutes, then post the contents of WindowsUpdate.log starting at the
time the command was issued.

Harry.

[Troy Bruder]

Here you go:

2008-01-10 13:22:15:792 984 1440 AU #############
2008-01-10 13:22:15:792 984 1440 AU ## START ## AU: Search for updates
2008-01-10 13:22:15:792 984 1440 AU #########
2008-01-10 13:22:15:792 984 1440 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {A4524B58-A50A-432A-AA68-ACAD2B3EC57F}]
2008-01-10 13:22:15:792 984 13b8 Agent *************
2008-01-10 13:22:15:792 984 13b8 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-01-10 13:22:15:792 984 13b8 Agent *********
2008-01-10 13:22:15:792 984 13b8 Agent * Online = Yes; Ignore download
priority = No
2008-01-10 13:22:15:792 984 13b8 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2008-01-10 13:22:15:792 984 13b8 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-01-10 13:22:15:792 984 13b8 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-01-10 13:22:15:823 984 13b8 Misc Microsoft signed: Yes
2008-01-10 13:22:16:620 984 13b8 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-01-10 13:22:16:620 984 13b8 Misc Microsoft signed: Yes
2008-01-10 13:22:16:636 984 13b8 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-01-10 13:22:16:652 984 13b8 Misc Microsoft signed: Yes
2008-01-10 13:22:16:652 984 13b8 Setup *********** Setup: Checking whether
self-update is required ***********
2008-01-10 13:22:16:652 984 13b8 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-01-10 13:22:16:667 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version
= 7.0.6000.374
2008-01-10 13:22:16:667 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:683 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:698 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:714 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:714 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:730 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:745 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:745 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:745 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:745 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:761 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:761 984 13b8 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
2008-01-10 13:22:16:761 984 13b8 Setup * IsUpdateRequired = No
2008-01-10 13:22:22:730 984 13b8 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-01-10 13:22:22:730 984 13b8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.precision.com:8530/ClientWebService/client.asmx
2008-01-10 13:22:24:073 984 13b8 PT WARNING: Cached cookie has expired or
new PID is available
2008-01-10 13:22:24:073 984 13b8 PT Initializing simple targeting cookie,
clientId = 578f6cc7-97a6-442e-a304-0867a8958994, target group = Servers, DNS
name = atnrt.precision.com
2008-01-10 13:22:24:073 984 13b8 PT Server URL =
http://wsus.precision.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-01-10 13:22:50:995 984 13b8 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-01-10 13:22:50:995 984 13b8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.precision.com:8530/ClientWebService/client.asmx
2008-01-10 13:22:53:495 984 13b8 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2008-01-10 13:22:53:495 984 13b8 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2008-01-10 13:22:53:511 984 13b8 Agent WARNING: Fail to download eula file
http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt
with error 0x80244019
2008-01-10 13:22:54:589 984 13b8 Agent * Found 0 updates and 39
categories in search; evaluated appl. rules of 541 out of 738 deployed
entities
2008-01-10 13:22:54:589 984 13b8 Agent *********
2008-01-10 13:22:54:589 984 13b8 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-01-10 13:22:54:589 984 13b8 Agent *************
2008-01-10 13:22:54:636 984 13cc AU >>## RESUMED ## AU: Search for
updates [CallId = {A4524B58-A50A-432A-AA68-ACAD2B3EC57F}]
2008-01-10 13:22:54:636 984 13cc AU # 0 updates detected
2008-01-10 13:22:54:636 984 13cc AU #########
2008-01-10 13:22:54:636 984 13cc AU ## END ## AU: Search for updates
[CallId = {A4524B58-A50A-432A-AA68-ACAD2B3EC57F}]
2008-01-10 13:22:54:636 984 13cc AU #############
2008-01-10 13:22:54:651 984 13cc AU AU setting next detection timeout to
2008-01-10 19:15:26
2008-01-10 13:22:59:620 984 13b8 Report REPORT EVENT:
{A3453703-B499-4298-8A5C-57068578E1AF} 2008-01-10 13:22:54:589-0500 1 147
101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 0
updates.
2008-01-10 13:22:59:620 984 13b8 Report REPORT EVENT:
{E3A6CAF1-BE71-44C4-898B-A13F74D4858E} 2008-01-10 13:22:54:589-0500 1 156
101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Pre-Deployment Check Reporting client status.
2008-01-10 13:25:07:744 984 13b8 Report Uploading 2 events using cached
cookie, reporting URL =
http://wsus.precision.com:8530/ReportingWebService/ReportingWebService.asmx
2008-01-10 13:25:07:775 984 13b8 Report Reporter successfully uploaded 2
events.

Post by Harry Johnston [MVP]

Post by Troy Bruder
Anyone have any idea what this error means? Suddenly my WSUS 3.0 updates
WARNING: Cached cookie has expired or new PID is available

This message doesn't usually indicate an error condition.
wuauclt /detectnow
wait ten minutes, then post the contents of WindowsUpdate.log starting at
the time the command was issued.
Harry.

[Harry Johnston [MVP]]

Post by Troy Bruder
SendRequestToServerForFileInformation failed with 0x80190194
ShouldFileBeDownloaded failed with 0x80190194
2008-01-10 13:22:53:511 984 13b8 Agent WARNING: Fail to download eula file
http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt
with error 0x80244019

This is your problem. These are 404 (web page not found) errors.

See whether you can access the file from IE:

<http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt>

If not, look on the WSUS server to see whether that file exists.

If the file doesn't exist, you may need to run this command:

wsusutil reset

which will check for missing files as documented here

<http://technet2.microsoft.com/windowsserver/en/library/e0934a67-f0ed-41a3-bf57-78fd9ac949431033.mspx?mfr=true>

Harry.

[Lawrence Garvin [MVP]]

Post by Harry Johnston [MVP]

Post by Troy Bruder
SendRequestToServerForFileInformation failed with 0x80190194
ShouldFileBeDownloaded failed with 0x80190194
2008-01-10 13:22:53:511 984 13b8 Agent WARNING: Fail to download eula file
http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt
with error 0x80244019

This is your problem. These are 404 (web page not found) errors.

Harry, the WUA was able to find the ReportingEventWebService -- so that

Post by Harry Johnston [MVP]
2008-01-10 13:25:07:744 984 13b8 Report Uploading 2 events using cached
cookie, reporting URL =
http://wsus.precision.com:8530/ReportingWebService/ReportingWebService.asmx
2008-01-10 13:25:07:775 984 13b8 Report Reporter successfully uploaded 2
events.

Which suggests that maybe the ClientWebService virtual directory is missing
or misconfigured, or the client.asmx file is missing.

I also, for a moment, considered that it could be a defect in the WUServer
value that's not present in the WUStatusServer value, but a test on my XP
workstation just now demonstrated that the WUA v7 client doesn't even read
the WUStatusServer value -- it actually reports the WUServer value as the
WUStatusServer value! .. and then gave me an expected 0x80072ee7 error
because the bogus machine name I configured didn't actually exist.

Post by Harry Johnston [MVP]
2008-01-10 13:22:50:995 984 13b8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.precision.com:8530/ClientWebService/client.asmx
<http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt>

The EULA file might be legitimately not present (which 'wsusutil reset' will
then fix),
but that may or may not be related to the 404 error when trying to access
client.asmx.

[Harry Johnston [MVP]]

Post by Troy Bruder
2008-01-10 13:22:50:995 984 13b8 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-01-10 13:22:50:995 984 13b8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.precision.com:8530/ClientWebService/client.asmx
SendRequestToServerForFileInformation failed with 0x80190194
ShouldFileBeDownloaded failed with 0x80190194
2008-01-10 13:22:53:511 984 13b8 Agent WARNING: Fail to download eula file
http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt
with error 0x80244019

[...]

Post by Troy Bruder
Which suggests that maybe the ClientWebService virtual directory is missing
or misconfigured, or the client.asmx file is missing.

Looking at the timestamps the two WinHttp errors are 2.5s away from the
client.asmx message and only 0.006s away from the eula file message. So I
figure they belong to the latter.

Harry.

[Lawrence Garvin [MVP]]

Post by Harry Johnston [MVP]

Post by Troy Bruder
2008-01-10 13:22:50:995 984 13b8 PT +++++++++++ PT: Synchronizing
extended update info +++++++++++
2008-01-10 13:22:50:995 984 13b8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.precision.com:8530/ClientWebService/client.asmx
SendRequestToServerForFileInformation failed with 0x80190194
ShouldFileBeDownloaded failed with 0x80190194
2008-01-10 13:22:53:511 984 13b8 Agent WARNING: Fail to download eula file
http://wsus.precision.com:8530/Content/63/CB39A551C4AFA7B00769D8C225D56786FD552263.txt
with error 0x80244019

[...]

Post by Troy Bruder
Which suggests that maybe the ClientWebService virtual directory is missing
or misconfigured, or the client.asmx file is missing.

Looking at the timestamps the two WinHttp errors are 2.5s away from the
client.asmx message and only 0.006s away from the eula file message. So I
figure they belong to the latter.

You may be right at that.

If "SendRequestToServerForFileInformation" and "ShouldFileBeDownloaded" are
both failing simply because of a missing EULA txt file, then that would be
the explanation.

But it's not impossible that this failure is a result of some larger issue
at work that's merely manifesting as a '404' response to the webservice
call.


There's also another anomaly to consider....

Post by Harry Johnston [MVP]
2008-01-10 13:22:54:589 984 13b8 Agent * Found 0 updates and 39
categories in search; evaluated appl. rules of 541 out of 738 deployed
entities
{A3453703-B499-4298-8A5C-57068578E1AF} 2008-01-10 13:22:54:589-0500 1 147
101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 0
updates.

If the detection determined an update needed a EULA downloaded...
then what exactly was that update, because the detection "Found 0
updates..."
and the WUA "...successfully detected 0 updates."

[Harry Johnston [MVP]]

Post by Lawrence Garvin [MVP]
If the detection determined an update needed a EULA downloaded...
then what exactly was that update, because the detection "Found 0
updates..."
and the WUA "...successfully detected 0 updates."

Yeah, that's odd. I'd guess that the EULA download counts as part of the
detection process, so that if it fails the update is shown as not needed in the
log; this would be similar to the case of an update that hasn't downloaded to
the WSUS server yet.

Troy, could you (a) confirm that the update (Windows 2003 service pack 2) isn't
actually installed on the affected server; and (b) tell us whether the WSUS
server says the affected server needs this update.

Harry.

[Lawrence Garvin [MVP]]

Post by Harry Johnston [MVP]

Post by Lawrence Garvin [MVP]
If the detection determined an update needed a EULA downloaded...
then what exactly was that update, because the detection "Found 0
updates..."
and the WUA "...successfully detected 0 updates."

Yeah, that's odd. I'd guess that the EULA download counts as part of the
detection process, so that if it fails the update is shown as not needed
in the log; this would be similar to the case of an update that hasn't
downloaded to the WSUS server yet.

Unfortunately, that's logically inconsistent, since in WSUS 3 all updates
are "Detect Only" by default, thus all clients have already reported as
"Needed" long before the update is marked as approved (which is what
triggers the acceptance of the EULA at the Admin Console). Until an update
is approved, the client shouldn't be downloading anything -- including the
EULA!

[Harry Johnston [MVP]]

Post by Lawrence Garvin [MVP]

Post by Harry Johnston [MVP]
Yeah, that's odd. I'd guess that the EULA download counts as part of
the detection process, so that if it fails the update is shown as not
needed in the log; this would be similar to the case of an update that
hasn't downloaded to the WSUS server yet.

Unfortunately, that's logically inconsistent, since in WSUS 3 all
updates are "Detect Only" by default, thus all clients have already
reported as "Needed" long before the update is marked as approved

Sure, but while they report to the server as needed this doesn't show up in
WindowsUpdate.log.

Harry.

[Lawrence Garvin [MVP]]

Post by Harry Johnston [MVP]

Post by Lawrence Garvin [MVP]

Post by Harry Johnston [MVP]
Yeah, that's odd. I'd guess that the EULA download counts as part of
the detection process, so that if it fails the update is shown as not
needed in the log; this would be similar to the case of an update that
hasn't downloaded to the WSUS server yet.

Unfortunately, that's logically inconsistent, since in WSUS 3 all updates
are "Detect Only" by default, thus all clients have already reported as
"Needed" long before the update is marked as approved

Sure, but while they report to the server as needed this doesn't show up
in WindowsUpdate.log.

But it would be on the server -- so a relevant question in this scenario is
whether the WSUS Server is reporting any updates Needed for this client.

Also, there's a significant difference between an update that has not
downloaded to the server, and thus the update is entirely undetectable by a
client, and the apparent inability to download a EULA TXT file to the
client. The latter implies that the EULA is physically present on the
server. If the EULA is present, and the client wants to download it it, this
implies, also, that the update has been approved for installation.

Now, if an update is "Needed", and approved for detection, then why is the
client detecting zero updates?