Results 1 to 4 of 4

Thread: wsus clients not contact wsus server error = 0x80244023 and 0x8019

  1. #1
    Join Date
    Aug 2006
    Posts
    253

    wsus clients not contact wsus server error = 0x80244023 and 0x8019

    I have checked out different of my WSUS client but not all, that do not contact WSUS server since last 30 days or so and the below error list are generating in the windowsupdate.log

    ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-03-02 15:31:52:242 1876 101c Agent *********
    2009-03-02 15:31:52:242 1876 101c Agent * Online = Yes;
    Ignore download priority = No
    2009-03-02 15:31:52:242 1876 101c 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"
    2009-03-02 15:31:52:242 1876 101c Agent * ServiceID =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-03-02 15:31:52:242 1876 101c Misc Validating signature
    for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-03-02 15:31:52:273 1876 101c Misc Microsoft signed: Yes
    2009-03-02 15:31:52:648 1876 101c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x801901f8
    2009-03-02 15:31:52:648 1876 101c Misc WARNING: WinHttp:
    ShouldFileBeDownloaded failed with 0x801901f8
    2009-03-02 15:31:52:882 1876 101c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x801901f8
    2009-03-02 15:31:52:882 1876 101c Misc WARNING: WinHttp:
    ShouldFileBeDownloaded failed with 0x801901f8
    2009-03-02 15:31:53:148 1876 101c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x801901f8
    2009-03-02 15:31:53:148 1876 101c Misc WARNING: WinHttp:
    ShouldFileBeDownloaded failed with 0x801901f8
    2009-03-02 15:31:53:320 1876 101c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x801901f8
    2009-03-02 15:31:53:335 1876 101c Misc WARNING: WinHttp:
    ShouldFileBeDownloaded failed with 0x801901f8
    2009-03-02 15:31:53:335 1876 101c Misc WARNING:
    DownloadFileInternal failed for http://altiris:8530/selfupdate/wuident.cab:
    error 0x801901f8
    2009-03-02 15:31:53:335 1876 101c Setup FATAL:
    IsUpdateRequired failed with error 0x80244023
    2009-03-02 15:31:53:335 1876 101c Setup WARNING: SelfUpdate:
    Default Service: IsUpdateRequired failed: 0x80244023
    2009-03-02 15:31:53:335 1876 101c Setup WARNING: SelfUpdate:
    Default Service: IsUpdateRequired failed, error = 0x80244023
    2009-03-02 15:31:53:335 1876 101c Agent * WARNING: Skipping
    scan, self-update check returned 0x80244023
    2009-03-02 15:31:54:617 1876 101c Agent * WARNING: Exit
    code = 0x80244023
    2009-03-02 15:31:54:617 1876 101c Agent *********
    2009-03-02 15:31:54:617 1876 101c Agent ** END ** Agent:
    Finding updates [CallerId = AutomaticUpdates]
    2009-03-02 15:31:54:617 1876 101c Agent *************
    2009-03-02 15:31:54:617 1876 101c Agent WARNING: WU client
    failed Searching for update with error 0x80244023
    2009-03-02 15:31:54:617 1876 11fc AU >>## RESUMED ## AU:
    Search for updates [CallId = {5267A692-AE8B-4851-88BA-E1F5EE0A3A2B}]
    2009-03-02 15:31:54:617 1876 11fc AU # WARNING: Search
    callback failed, result = 0x80244023
    2009-03-02 15:31:54:617 1876 11fc AU # WARNING: Failed to
    find updates with error code 80244023
    2009-03-02 15:31:54:617 1876 11fc AU #########
    2009-03-02 15:31:54:617 1876 11fc AU ## END ## AU: Search
    for updates [CallId = {5267A692-AE8B-4851-88BA-E1F5EE0A3A2B}]
    2009-03-02 15:31:54:617 1876 11fc AU #############
    2009-03-02 15:31:54:617 1876 11fc AU AU setting next
    detection timeout to 2009-03-02 18:29:11
    2009-03-02 15:31:54:617 1876 11fc AU Setting AU scheduled
    install time to 2009-03-03 15:00:00
    2009-03-02 15:46:25:685 1876 101c PT WARNING: Cached cookie
    has expired or new PID is available
    2009-03-02 15:46:25:685 1876 101c PT Initializing simple
    targeting cookie, clientId = d99edd47-3265-414c-b14a-e2a65fa35c55, target
    group = , DNS name = mv-oap-ws085.nonstoptv.com.ar
    2009-03-02 15:46:25:685 1876 101c PT Server URL =
    http://altiris:8530/SimpleAuthWebSer...impleAuth.asmx
    2009-03-02 15:46:25:919 1876 101c PT WARNING:
    GetAuthorizationCookie failure, error = 0x80244023, soap client error = 10,
    soap error code = 0, HTTP status code = 504
    2009-03-02 15:46:25:919 1876 101c PT WARNING: Failed to
    initialize Simple Targeting Cookie: 0x80244023

    Can anyone please help me sort out this problem?

  2. #2
    Join Date
    Dec 2004
    Posts
    420

    Re: wsus clients not contact wsus server error = 0x80244023 and 0x8019

    The error 0x801901F8 - 2145844744 BG_E_HTTP_ERROR_504 the request was timed out waiting for a gateway can be typically a DNS issue. The error 0x80244023 WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT HTTP 504, looks to me like the client will not be able to find the WSUS server as named. Either hostname is not in the DNS service or the IP Address given by the DNS is on an not reachable network.

  3. #3
    Join Date
    Aug 2006
    Posts
    253

    Re: wsus clients not contact wsus server error = 0x80244023 and 0x

    Thanks for the reply but if I am trying to ping the hostnam from the WSUS client, then the dns returns me the correct ip and if I am opening the hostname by the browser then I dont get the problem. So, I cant understand what is the issue here.

  4. #4
    Join Date
    Aug 2006
    Posts
    253
    I have now changed the DNS name for the ip address and WSUS client connected ok with WSUS server. But I cannot understand why it stopped working one day to the other?

Similar Threads

  1. Clients not reporting to WSUS server
    By Leland in forum Server Update Service
    Replies: 10
    Last Post: 10-11-2009, 08:35 PM
  2. WSUS 3.0 Clients are not showing in wsus admin console
    By Rock41 in forum Windows Update
    Replies: 7
    Last Post: 25-09-2009, 12:28 AM
  3. Replies: 3
    Last Post: 07-01-2009, 09:45 AM
  4. Replies: 2
    Last Post: 15-08-2008, 12:18 AM
  5. clients not reporting status after updating WSUS 2 to WSUS 3.0
    By Dhananjay in forum Server Update Service
    Replies: 4
    Last Post: 17-07-2007, 09:37 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •