Results 1 to 6 of 6

Thread: 0x80244019 error on update.microsoft.com

  1. #1
    nerochen Guest

    0x80244019 error on update.microsoft.com

    Windows Server 2003 SP1, few hotfixes were installed OK afterwards... WSUS is
    not used. ISA 2004 firewall is used on intranet (without proxy), however
    problem remains when I set the server to a public IP.

    It runs SharePoint Services 2.0 + Project Server 2003, can this be a
    problem? It was OK for a few months after I put Windows Server 2003 SP1
    though... No configuration changes were done afterwards. It just stopped
    accepting more hotfixes a while ago :(

    I was able to open http://.../muredir.cab from IE directly.

    2005-12-05 18:15:41 2848 b24 COMAPI -------------
    2005-12-05 18:15:41 2848 b24 COMAPI -- START -- COMAPI: Search [ClientId =
    MicrosoftUpdate]
    2005-12-05 18:15:41 2848 b24 COMAPI ---------
    2005-12-05 18:15:41 2848 b24 COMAPI - Online = Yes; Ignore download
    priority = No
    2005-12-05 18:15:41 2848 b24 COMAPI - Criteria = "IsInstalled=0 and
    IsHidden=1"
    2005-12-05 18:15:41 2848 b24 COMAPI - ServiceID =
    {7971F918-A847-4430-9279-4A52D1EFE18D}
    2005-12-05 18:15:41 2848 b24 COMAPI <<-- SUBMITTED -- COMAPI: Search
    [ClientId = MicrosoftUpdate]
    2005-12-05 18:15:41 852 d0c Agent *************
    2005-12-05 18:15:41 852 d0c Agent ** START ** Agent: Finding updates
    [CallerId = MicrosoftUpdate]
    2005-12-05 18:15:41 852 d0c Agent *********
    2005-12-05 18:15:42 852 d0c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x80190194
    2005-12-05 18:15:42 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    failed with 0x80190194
    2005-12-05 18:15:42 852 d0c Misc WARNING: DownloadFileInternal failed for
    http://download.windowsupdate.com/v6...r/muredir.cab: error
    0x80190194
    2005-12-05 18:15:43 852 d0c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x80190194
    2005-12-05 18:15:43 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    failed with 0x80190194
    2005-12-05 18:15:43 852 d0c Misc WARNING: DownloadFileInternal failed for
    http://download.microsoft.com/v6/mic...r/muredir.cab: error
    0x80190194
    2005-12-05 18:15:44 852 d0c Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x80190194
    2005-12-05 18:15:44 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    failed with 0x80190194
    2005-12-05 18:15:44 852 d0c Misc WARNING: DownloadFileInternal failed for
    http://update.microsoft.com/v6/micro...r/muredir.cab: error
    0x80190194
    2005-12-05 18:15:44 852 d0c Agent * WARNING: Failed to synchronize, error
    = 0x80244019
    2005-12-05 18:15:44 852 d0c Agent * WARNING: Exit code = 0x80244019
    2005-12-05 18:15:44 852 d0c Agent *********
    2005-12-05 18:15:44 852 d0c Agent ** END ** Agent: Finding updates
    [CallerId = MicrosoftUpdate]
    2005-12-05 18:15:44 852 d0c Agent *************
    2005-12-05 18:15:44 852 d0c Agent WARNING: WU client failed Searching for
    update with error 0x80244019
    2005-12-05 18:15:44 2848 b9c COMAPI >>-- RESUMED -- COMAPI: Search
    [ClientId = MicrosoftUpdate]
    2005-12-05 18:15:45 2848 b9c COMAPI - Updates found = 0
    2005-12-05 18:15:45 2848 b9c COMAPI - WARNING: Exit code = 0x00000000,
    Result code = 0x80244019
    2005-12-05 18:15:45 2848 b9c COMAPI ---------
    2005-12-05 18:15:45 2848 b9c COMAPI -- END -- COMAPI: Search [ClientId =
    MicrosoftUpdate]
    2005-12-05 18:15:45 2848 b9c COMAPI -------------
    2005-12-05 18:15:45 2848 b24 COMAPI WARNING: Operation failed due to earlier
    error, hr=80244019
    2005-12-05 18:15:45 2848 b24 COMAPI FATAL: Unable to complete asynchronous
    search. (hr=80244019)
    2005-12-05 18:15:50 852 d0c Report REPORT EVENT:
    {7E350DDD-4F3B-4642-ADD6-510B03BD1E99} 2005-12-05
    18:15:44+0300 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 MicrosoftUpdate Failure Software
    Synchronization Error: Agent failed detecting with reason: 0x80244019



  2. #2
    SteveL Guest

    RE: 0x80244019 error on update.microsoft.com

    You may want to ask this question in the SERVER group not XP, you may get a
    faster responce..

    "nerochen" wrote:

    > Windows Server 2003 SP1, few hotfixes were installed OK afterwards... WSUS is
    > not used. ISA 2004 firewall is used on intranet (without proxy), however
    > problem remains when I set the server to a public IP.
    >
    > It runs SharePoint Services 2.0 + Project Server 2003, can this be a
    > problem? It was OK for a few months after I put Windows Server 2003 SP1
    > though... No configuration changes were done afterwards. It just stopped
    > accepting more hotfixes a while ago :(
    >
    > I was able to open http://.../muredir.cab from IE directly.
    >
    > 2005-12-05 18:15:41 2848 b24 COMAPI -------------
    > 2005-12-05 18:15:41 2848 b24 COMAPI -- START -- COMAPI: Search [ClientId =
    > MicrosoftUpdate]
    > 2005-12-05 18:15:41 2848 b24 COMAPI ---------
    > 2005-12-05 18:15:41 2848 b24 COMAPI - Online = Yes; Ignore download
    > priority = No
    > 2005-12-05 18:15:41 2848 b24 COMAPI - Criteria = "IsInstalled=0 and
    > IsHidden=1"
    > 2005-12-05 18:15:41 2848 b24 COMAPI - ServiceID =
    > {7971F918-A847-4430-9279-4A52D1EFE18D}
    > 2005-12-05 18:15:41 2848 b24 COMAPI <<-- SUBMITTED -- COMAPI: Search
    > [ClientId = MicrosoftUpdate]
    > 2005-12-05 18:15:41 852 d0c Agent *************
    > 2005-12-05 18:15:41 852 d0c Agent ** START ** Agent: Finding updates
    > [CallerId = MicrosoftUpdate]
    > 2005-12-05 18:15:41 852 d0c Agent *********
    > 2005-12-05 18:15:42 852 d0c Misc WARNING: WinHttp:
    > SendRequestToServerForFileInformation failed with 0x80190194
    > 2005-12-05 18:15:42 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    > failed with 0x80190194
    > 2005-12-05 18:15:42 852 d0c Misc WARNING: DownloadFileInternal failed for
    > http://download.windowsupdate.com/v6...r/muredir.cab: error
    > 0x80190194
    > 2005-12-05 18:15:43 852 d0c Misc WARNING: WinHttp:
    > SendRequestToServerForFileInformation failed with 0x80190194
    > 2005-12-05 18:15:43 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    > failed with 0x80190194
    > 2005-12-05 18:15:43 852 d0c Misc WARNING: DownloadFileInternal failed for
    > http://download.microsoft.com/v6/mic...r/muredir.cab: error
    > 0x80190194
    > 2005-12-05 18:15:44 852 d0c Misc WARNING: WinHttp:
    > SendRequestToServerForFileInformation failed with 0x80190194
    > 2005-12-05 18:15:44 852 d0c Misc WARNING: WinHttp: ShouldFileBeDownloaded
    > failed with 0x80190194
    > 2005-12-05 18:15:44 852 d0c Misc WARNING: DownloadFileInternal failed for
    > http://update.microsoft.com/v6/micro...r/muredir.cab: error
    > 0x80190194
    > 2005-12-05 18:15:44 852 d0c Agent * WARNING: Failed to synchronize, error
    > = 0x80244019
    > 2005-12-05 18:15:44 852 d0c Agent * WARNING: Exit code = 0x80244019
    > 2005-12-05 18:15:44 852 d0c Agent *********
    > 2005-12-05 18:15:44 852 d0c Agent ** END ** Agent: Finding updates
    > [CallerId = MicrosoftUpdate]
    > 2005-12-05 18:15:44 852 d0c Agent *************
    > 2005-12-05 18:15:44 852 d0c Agent WARNING: WU client failed Searching for
    > update with error 0x80244019
    > 2005-12-05 18:15:44 2848 b9c COMAPI >>-- RESUMED -- COMAPI: Search
    > [ClientId = MicrosoftUpdate]
    > 2005-12-05 18:15:45 2848 b9c COMAPI - Updates found = 0
    > 2005-12-05 18:15:45 2848 b9c COMAPI - WARNING: Exit code = 0x00000000,
    > Result code = 0x80244019
    > 2005-12-05 18:15:45 2848 b9c COMAPI ---------
    > 2005-12-05 18:15:45 2848 b9c COMAPI -- END -- COMAPI: Search [ClientId =
    > MicrosoftUpdate]
    > 2005-12-05 18:15:45 2848 b9c COMAPI -------------
    > 2005-12-05 18:15:45 2848 b24 COMAPI WARNING: Operation failed due to earlier
    > error, hr=80244019
    > 2005-12-05 18:15:45 2848 b24 COMAPI FATAL: Unable to complete asynchronous
    > search. (hr=80244019)
    > 2005-12-05 18:15:50 852 d0c Report REPORT EVENT:
    > {7E350DDD-4F3B-4642-ADD6-510B03BD1E99} 2005-12-05
    > 18:15:44+0300 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 MicrosoftUpdate Failure Software
    > Synchronization Error: Agent failed detecting with reason: 0x80244019
    >
    >


  3. #3
    nerochen Guest

    RE: 0x80244019 error on update.microsoft.com

    This is OK. I found the problem. The last hotfix installed correctly was the
    one with WinHTTP 5.1. It all broke after it.

    Looks like this version of WinHTTP uses proxy settings in some way, I mean
    those set by proxycfg command. And WSS+ProjectServer use them as well to
    communicate to each other. Setting "proxycfg -d" solved the problem with
    Microsoft Update.


  4. #4
    mimi Guest

    RE: 0x80244019 error on update.microsoft.com

    Thank you,

    i' have the same problem from 2 week.

    "nerochen" wrote:

    > This is OK. I found the problem. The last hotfix installed correctly was the
    > one with WinHTTP 5.1. It all broke after it.
    >
    > Looks like this version of WinHTTP uses proxy settings in some way, I mean
    > those set by proxycfg command. And WSS+ProjectServer use them as well to
    > communicate to each other. Setting "proxycfg -d" solved the problem with
    > Microsoft Update.
    >


  5. #5
    Chringram Guest

    RE: 0x80244019 error on update.microsoft.com

    I did see that the old project server set a PROXYcfg - and did a
    START>RUN>CMD and then typed in proxycfg -d to delete it. I was still getting
    the same error, until I went into the browser's TOOLS>Internet Options and
    under CONNECTIONS and LAN SETTINGS I checked the 'Automatically detect
    settings' box

    Then I was able to receive updates. Damn project server!!

    "nerochen" wrote:

    > This is OK. I found the problem. The last hotfix installed correctly was the
    > one with WinHTTP 5.1. It all broke after it.
    >
    > Looks like this version of WinHTTP uses proxy settings in some way, I mean
    > those set by proxycfg command. And WSS+ProjectServer use them as well to
    > communicate to each other. Setting "proxycfg -d" solved the problem with
    > Microsoft Update.
    >


  6. #6
    Devanz Guest

    RE: 0x80244019 error on update.microsoft.com



    "Chringram" wrote:

    > I did see that the old project server set a PROXYcfg - and did a
    > START>RUN>CMD and then typed in proxycfg -d to delete it. I was still getting
    > the same error, until I went into the browser's TOOLS>Internet Options and
    > under CONNECTIONS and LAN SETTINGS I checked the 'Automatically detect
    > settings' box
    >
    > Then I was able to receive updates. Damn project server!!
    >
    > "nerochen" wrote:
    >
    > > This is OK. I found the problem. The last hotfix installed correctly was the
    > > one with WinHTTP 5.1. It all broke after it.
    > >
    > > Looks like this version of WinHTTP uses proxy settings in some way, I mean
    > > those set by proxycfg command. And WSS+ProjectServer use them as well to
    > > communicate to each other. Setting "proxycfg -d" solved the problem with
    > > Microsoft Update.
    > >


Similar Threads

  1. Vista Update (error found: Code 0x80244019)
    By Prijesh in forum Windows Update
    Replies: 2
    Last Post: 03-12-2008, 02:25 AM
  2. Replies: 1
    Last Post: 11-11-2008, 10:17 AM
  3. WSUS 3.0 clients failed with error 0x80244019
    By Delil in forum Server Update Service
    Replies: 1
    Last Post: 08-03-2008, 12:06 AM
  4. Replies: 3
    Last Post: 20-02-2006, 10:16 PM
  5. Error: Download Failed 0x80244019
    By elander in forum Server Update Service
    Replies: 9
    Last Post: 14-12-2005, 07:32 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,712,487.51398 seconds with 17 queries