Event logs say servers can't update from WSUS... but they do anywa

Discussion in 'Update Services' started by MS, Mar 8, 2007.

  1. MS

    MS Guest

    Hi, I'm recieving Event Id 16 every day when my servers attempt to look at my
    WSUS server for updates. The error says "Windows is unable to connect to the
    automatic updates service and therefore cannot download and install updates
    according to the set ".
    However... they all download and update the latest updates anyway.

    I'm pasting the WindowsUpdate.log from one of the servers. It seems to me
    that at 9:54, it successfully checked in. But at 15:04, it failed. It does
    this EVERY DAY, and the WSUS server does NOT go down in the evening. Also, I
    don't even have it set to check in twice a day in the GPO settings.

    Any ideas? Thanks!!

    -----------------------------------------------------------------
    2007-03-08 09:47:32:164 1268 6ec AU #############
    2007-03-08 09:47:32:164 1268 6ec AU ## START ## AU: Search for updates
    2007-03-08 09:47:32:164 1268 6ec AU #########
    2007-03-08 09:47:32:164 1268 6ec AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {C3F102AB-95A5-441E-8F46-0EADFB3B0FCE}]
    2007-03-08 09:47:32:180 1268 e6c Agent *************
    2007-03-08 09:47:32:180 1268 e6c Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-08 09:47:32:180 1268 e6c Agent *********
    2007-03-08 09:47:32:180 1268 e6c Agent * Online = Yes; Ignore download
    priority = No
    2007-03-08 09:47:32:180 1268 e6c 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"
    2007-03-08 09:47:32:180 1268 e6c Agent * ServiceID =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2007-03-08 09:47:32:180 1268 e6c Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2007-03-08 09:47:32:180 1268 e6c Misc Microsoft signed: Yes
    2007-03-08 09:47:32:430 1268 e6c Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2007-03-08 09:47:32:445 1268 e6c Misc Microsoft signed: Yes
    2007-03-08 09:47:33:336 1268 e6c PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2007-03-08 09:47:33:336 1268 e6c PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://drmon01/ClientWebService/client.asmx
    2007-03-08 09:47:33:429 1268 e6c PT WARNING: Cached cookie has expired or
    new PID is available
    2007-03-08 09:47:33:429 1268 e6c PT Initializing simple targeting cookie,
    clientId = 5b940ac8-9073-4ed9-92e1-984ea0d0e38e, target group = , DNS name =
    drsql01.westonfl.org
    2007-03-08 09:47:33:429 1268 e6c PT Server URL =
    http://drmon01/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-08 09:47:33:758 1268 e6c PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2007-03-08 09:47:33:758 1268 e6c PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://drmon01/ClientWebService/client.asmx
    2007-03-08 09:47:33:961 1268 e6c Agent * Found 0 updates and 14 categories
    in search
    2007-03-08 09:47:33:961 1268 e6c Agent *********
    2007-03-08 09:47:33:961 1268 e6c Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-08 09:47:33:961 1268 e6c Agent *************
    2007-03-08 09:47:33:976 1268 e6c AU >>## RESUMED ## AU: Search for updates
    [CallId = {C3F102AB-95A5-441E-8F46-0EADFB3B0FCE}]
    2007-03-08 09:47:33:976 1268 e6c AU # 0 updates detected
    2007-03-08 09:47:33:976 1268 e6c AU #########
    2007-03-08 09:47:33:976 1268 e6c AU ## END ## AU: Search for updates
    [CallId = {C3F102AB-95A5-441E-8F46-0EADFB3B0FCE}]
    2007-03-08 09:47:33:976 1268 e6c AU #############
    2007-03-08 09:47:33:976 1268 e6c AU AU setting next detection timeout to
    2007-03-08 21:25:03
    2007-03-08 09:47:38:976 1268 520 Report REPORT EVENT:
    {25282085-9792-436A-B5D8-0AD7BE6C36F4} 2007-03-08
    09:47:33:961-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2007-03-08 09:47:38:976 1268 520 Report REPORT EVENT:
    {C452FA91-BDEB-492B-9F2D-64EBCE86394F} 2007-03-08
    09:47:33:961-0500 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2007-03-08 09:54:26:302 1268 e6c Report Uploading 2 events using cached
    cookie, reporting URL =
    http://drmon01/ReportingWebService/ReportingWebService.asmx
    2007-03-08 09:54:26:349 1268 e6c Report Reporter successfully uploaded 2
    events.
    2007-03-08 15:04:42:362 1268 6ec AU AU was unable to detect updates for more
    than 48 hours
    2007-03-08 15:04:47:378 1268 520 Report REPORT EVENT:
    {3BC203F4-074F-497B-ABF4-9F52BA55644C} 2007-03-08
    15:04:42:362-0500 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software
    Synchronization Unable to Connect: Windows is unable to connect to the
    automatic updates service and therefore cannot download and install updates
    according to the set schedule. Windows will continue to try to establish a
    connection.
     
    MS, Mar 8, 2007
    #1
    1. Advertisements

  2. This is an error on the /client/ side, not on the WSUS server.

    My guess is that you have an errant domain policy that is disabling the
    Automatic Updates service, or has configured the AU service to run under a
    domain user account rather than the Local System account (which it must
    use).
    Really!?

    Okay.. so let me ask this again... is the Error 16 on your /WSUS/ server..
    or on the other servers?
    The AU service is obviously running... I'd check to ensure it's configured
    to logon with the Local System account.
    It definitely executed a detection event at 9:47... whether it was
    successful kinda depends on whether it should have detected any updates to
    install.
    This message should be taken at face value. It may have "reported" in the
    log that it detected -0- updates, but in reality it did not detect updates
    at all.

    --
    Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Mar 9, 2007
    #2
    1. Advertisements

  3. MS

    MS Guest

    Hi Lawrence, thanks for taking time out of your day to analyze my question!
    Yes, I am getting this error on the WSUS server itself. I think all my server
    are getting it.

    The reason I know that the servers are getting the updates is because when I
    Approve for Install, I remote into the server and the update appears. I
    install it, and WSUS says it no longer needs the update.
    So it seems that there's like a second AU running on these servers
    independantly of the servers.

    Here's a key clue I forgot to mention earlier- I had recently upgraded WSUS
    2 SP1 to WSUS 3 RC1. I didn't like WSUS 3, because it caused mayhem and I
    uninstalled it and reinstalled WSUS 2. This is when these errors began.
    Perhaps these servers are still looking for WSUS 3? (the WSUS server address
    did not change, by the way)
     
    MS, Mar 9, 2007
    #3
  4. I'd suggest dropping into the WSUSv3 beta newsgroup (instructions for access
    are available at the MSConnect website), and reviewing the various threads
    that discuss all of the complications involved in bouncing back and forth
    from WSUSv2 to WSUSv3 and back to WSUSv2.

    --
    Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Mar 9, 2007
    #4
    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.