Get rid of microsoft.com entry in WindowsUpdate.log

Discussion in 'Update Services' started by Jeff, Mar 27, 2008.

  1. Jeff

    Jeff Guest

    My clients all get the entry: WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    in the WindowsUpdate.log. This occurs after the cookie expires and after a
    GetCookie failure error. I believe this is indicating that the clients are
    going out to Microsoft's website to get the cookie, causing WAN traffic. I
    would like the clients to be able to get the cookie from the local WSUS
    server without a failure. How can I stop this www.microsoft.com entry in the
    WindowsUpdate.log?

    I have a Windows 2003 SP2 server, WSUS 3.0, and my clients have Windows XP
    SP2. I am using client side targeting. This server is a downstream server.
    The clients at the upstream site are not getting this error.

    Thank you for any help you can provide with this issue. Here's a complete
    cycle from the WindowsUpdate.log:

    2008-03-26 11:00:10:000 1156 200 AU Forced install timer expired for
    scheduled install
    2008-03-26 11:00:10:000 1156 200 AU UpdateDownloadProperties: 0 download(s)
    are still in progress.
    2008-03-26 11:00:10:046 1156 200 AU Setting AU scheduled install time to
    2008-03-27 15:00:00
    2008-03-26 13:57:32:375 1156 200 AU AU received policy change subscription
    event
    2008-03-26 14:49:07:343 1156 200 AU #############
    2008-03-26 14:49:07:343 1156 200 AU ## START ## AU: Search for updates
    2008-03-26 14:49:07:343 1156 200 AU #########
    2008-03-26 14:49:07:390 1156 200 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {2CC4A816-12B1-434C-9A88-13996A319E6E}]
    2008-03-26 14:49:07:421 1156 e70 Agent *************
    2008-03-26 14:49:07:421 1156 e70 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2008-03-26 14:49:07:421 1156 e70 Agent *********
    2008-03-26 14:49:07:421 1156 e70 Agent * Online = Yes; Ignore download
    priority = No
    2008-03-26 14:49:07:453 1156 e70 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-03-26 14:49:07:453 1156 e70 Agent * ServiceID =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2008-03-26 14:49:07:625 1156 e70 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2008-03-26 14:49:07:781 1156 e70 Misc Microsoft signed: Yes
    2008-03-26 14:49:20:312 1156 e70 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2008-03-26 14:49:20:437 1156 e70 Misc Microsoft signed: Yes
    2008-03-26 14:49:20:593 1156 e70 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2008-03-26 14:49:20:765 1156 e70 Misc Microsoft signed: Yes
    2008-03-26 14:49:20:906 1156 e70 Setup *********** Setup: Checking whether
    self-update is required ***********
    2008-03-26 14:49:20:906 1156 e70 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2008-03-26 14:49:21:578 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version
    = 7.0.6000.374
    2008-03-26 14:49:21:875 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:046 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:218 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:515 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:593 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:828 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:22:890 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:23:203 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:23:250 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:23:468 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version
    = 7.0.6000.374
    2008-03-26 14:49:23:625 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:23:875 1156 e70 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2008-03-26 14:49:23:953 1156 e70 Setup * IsUpdateRequired = No
    2008-03-26 14:50:19:062 1156 e70 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2008-03-26 14:50:19:062 1156 e70 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-dns-2/ClientWebService/client.asmx
    2008-03-26 14:50:28:890 1156 e70 PT WARNING: Cached cookie has expired or
    new PID is available
    2008-03-26 14:50:28:890 1156 e70 PT Initializing simple targeting cookie,
    clientId = 060dc8be-8e0c-4198-be4e-f3b8c21dd005, target group = CC, DNS name
    = tzw610.cc.sunywcc.edu
    2008-03-26 14:50:28:890 1156 e70 PT Server URL =
    http://cc-dns-2/SimpleAuthWebService/SimpleAuth.asmx
    2008-03-26 14:50:29:031 1156 e70 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2008-03-26 14:50:29:046 1156 e70 PT WARNING: SOAP Fault: 0x00012c
    2008-03-26 14:50:29:046 1156 e70 PT WARNING: faultstring:Fault occurred
    2008-03-26 14:50:29:046 1156 e70 PT WARNING: ErrorCode:ConfigChanged(2)
    2008-03-26 14:50:29:046 1156 e70 PT WARNING: Message:(null)
    2008-03-26 14:50:29:046 1156 e70 PT WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2008-03-26 14:50:29:093 1156 e70 PT WARNING:
    ID:4e6f5cd7-4a0c-4466-bb92-6f96a2a9291a
    2008-03-26 14:50:34:296 1156 e70 PT WARNING: Cached cookie has expired or
    new PID is available
    2008-03-26 14:50:34:296 1156 e70 PT Initializing simple targeting cookie,
    clientId = 060dc8be-8e0c-4198-be4e-f3b8c21dd005, target group = CC, DNS name
    = tzw610.cc.sunywcc.edu
    2008-03-26 14:50:34:296 1156 e70 PT Server URL =
    http://cc-dns-2/SimpleAuthWebService/SimpleAuth.asmx
    2008-03-26 14:58:33:593 1156 e70 PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2008-03-26 14:58:33:593 1156 e70 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-dns-2/ClientWebService/client.asmx
    2008-03-26 14:59:15:453 1156 e70 Agent * Found 0 updates and 40 categories
    in search; evaluated appl. rules of 932 out of 1387 deployed entities
    2008-03-26 14:59:16:328 1156 e70 Agent *********
    2008-03-26 14:59:16:328 1156 e70 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2008-03-26 14:59:16:328 1156 e70 Agent *************
    2008-03-26 14:59:16:453 1156 840 AU >>## RESUMED ## AU: Search for updates
    [CallId = {2CC4A816-12B1-434C-9A88-13996A319E6E}]
    2008-03-26 14:59:16:453 1156 840 AU # 0 updates detected
    2008-03-26 14:59:16:531 1156 840 AU #########
    2008-03-26 14:59:16:531 1156 840 AU ## END ## AU: Search for updates
    [CallId = {2CC4A816-12B1-434C-9A88-13996A319E6E}]
    2008-03-26 14:59:16:531 1156 840 AU #############
    2008-03-26 14:59:16:531 1156 840 AU AU setting next detection timeout to
    2008-03-27 13:52:46
    2008-03-26 14:59:16:531 1156 840 AU Setting AU scheduled install time to
    2008-03-27 15:00:00
    2008-03-26 14:59:21:437 1156 e70 Report REPORT EVENT:
    {9E177A69-CA6E-449C-8546-9DD947A81085} 2008-03-26
    14:59:16:296-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2008-03-26 14:59:21:437 1156 e70 Report REPORT EVENT:
    {A95B5AEC-999D-4341-BA0A-F92A694DB095} 2008-03-26
    14:59:16:328-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2008-03-26 15:02:15:187 1156 e70 Report Uploading 2 events using cached
    cookie, reporting URL =
    http://cc-dns-2/ReportingWebService/ReportingWebService.asmx
    2008-03-26 15:02:15:359 1156 e70 Report Reporter successfully uploaded 2
    events.
     
    Jeff, Mar 27, 2008
    #1
    1. Advertisements

  2. The *only* place a WSUS client can get information for the cookie is from
    the assigned WSUS Server.


    The cookie expires after an hour (give or take). If you have a detection
    interval of 1 hour, the cookie may never expire.
    When the cookie "expires" it is reinitialized.




    Now, having said that.... let's talk about the *real* error you have..
    The SOAP 0x12c error has been around a while.

    Try here for some ideas:

    http://www.wsuswiki.com/SOAPFault0x00012c

    http://www.wsuswiki.com/AgentFailedDetecting0x8024400d

    http://www.wsuswiki.com/OldWSUSIssues

    --
    Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Mar 28, 2008
    #2
    1. Advertisements

  3. Jeff

    Jeff Guest

    I've tried all the linked solutions a number of times in the past and they
    didn't work. I don't think it's a client issue because if I get the updates
    directly from the upstream server, I don't get the errors. Could you please
    tell me how I can set the cookie detection interval to an hour?

    Do you know what the www.microsoft.com log entry means?
    WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    Why would the www.microsoft.com website be listed if the clients aren't
    going to the website?

    Thanks again for your help.
     
    Jeff, Mar 28, 2008
    #3
  4. The cookie =expiration= interval is not configurable. It's "60 minutes" and
    hardcoded in the Windows Update Agent.

    The =detection= interval is configured in the policy setting "Automatic
    Updates detection frequency" by setting the policy to Enabled, and choosing
    the desired detection frequency (1-22 hours).
    I'm sorry, I didn't see that entry in your logfile. Can you show me the
    exact timestamp where this item appears.

    =Context= is everythng! :)

    --
    Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Mar 28, 2008
    #4
  5. Jeff

    Jeff Guest

    Jeff, Mar 29, 2008
    #5
  6. Jeff

    Jeff Guest

    Jeff, Apr 1, 2008
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.