Windows Server TechCenter > Windows Server Forums > WSUS > Windows Server Update Error
Ask a questionAsk a question
 

QuestionWindows Server Update Error

All Replies

  • Monday, October 26, 2009 10:39 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Run the Client Diagnostic Tool and inspect the results.

    But if you truly did follow the instructions in the cited article and verified that the WUServer and WUStatusServer registry values are correct, then there's nothing the CDT is going to do for you at this point.

    The better place to diagnose a "not reporting" issue is the WindowsUpdate.log  -- are there calls to the ReportingEventWebService?
    * If so, are they successful, or are errors being recorded.
    * If not, what else is installed in your environment -- like SCCM 2007?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Monday, October 26, 2009 10:59 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am getting alot of 80244019 error just checking the logs right now.
    I do get that Report Uploading 14 events using cached cookie, reporting URL = http://servername:8530/ReportingWebService/ReportingWebService.asmx
  • Monday, October 26, 2009 11:04 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am getting alot of 80244019 error just checking the logs right now.
    I do get that Report Uploading 14 events using cached cookie, reporting URL = http://servername:8530/ReportingWebService/ReportingWebService.asmx

    0x80244019 is an HTTP 404 error. Please post the segment of the log starting with the beginning of the detection event that includes these error codes, and analyzing the log in context will likely identify the specific source of your issue.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Monday, October 26, 2009 11:13 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    for some reason the clients are just not finding the server:

    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-10-26 15:44:00:071  936 7b0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://servername/ClientWebService/client.asmx
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: PTError: 0x80244019
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: GetConfig_WithRecovery failed: 0x80244019
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: RefreshConfig failed: 0x80244019
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: RefreshPTState failed: 0x80244019
    2009-10-26 15:44:00:071  936 7b0 PT WARNING: Sync of Updates: 0x80244019
    2009-10-26 15:44:00:086  936 7b0 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
    2009-10-26 15:44:00:086  936 7b0 Agent   * WARNING: Failed to synchronize, error = 0x80244019
    2009-10-26 15:44:00:086  936 7b0 Agent   * WARNING: Exit code = 0x80244019
    2009-10-26 15:44:00:086  936 7b0 Agent *********
    2009-10-26 15:44:00:086  936 7b0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-26 15:44:00:086  936 7b0 Agent *************
    2009-10-26 15:44:00:086  936 7b0 Agent WARNING: WU client failed Searching for update with error 0x80244019
    2009-10-26 15:44:00:086  936 c08 AU >>##  RESUMED  ## AU: Search for updates [CallId = {738F8BED-0AA9-43DE-B932-CF61707F02CD}]
    2009-10-26 15:44:00:102  936 c08 AU   # WARNING: Search callback failed, result = 0x80244019
    2009-10-26 15:44:00:102  936 c08 AU   # WARNING: Failed to find updates with error code 80244019
    2009-10-26 15:44:00:102  936 c08 AU #########
    2009-10-26 15:44:00:102  936 c08 AU ##  END  ##  AU: Search for updates [CallId = {738F8BED-0AA9-43DE-B932-CF61707F02CD}]
    2009-10-26 15:44:00:102  936 c08 AU #############
    2009-10-26 15:44:00:102  936 c08 AU AU setting next detection timeout to 2009-10-26 23:43:06
    2009-10-26 15:44:00:102  936 c08 AU Setting AU scheduled install time to 2009-10-27 10:00:00
    2009-10-26 15:44:05:086  936 7b0 Report REPORT EVENT: {0E7D15C9-1344-4288-8EF5-CEE198F750DE} 2009-10-26 15:44:00:086-0700 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
  • Monday, October 26, 2009 11:29 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    and this is what i get from the server, and it just goes on and on like that:

    2009-10-25 20:38:28:607 1100 3844 DnldMgr   * BITS job initialized, JobId = {8BC1F323-A483-4195-9B53-580E0FACBA8E}
    2009-10-25 20:38:28:607 1100 3844 DnldMgr   * Downloading from http://servername:8530/Content/79/B65495BD42C584D905A9A4C5E4D643BD75D5A679.exe to C:\WINDOWS\SoftwareDistribution\Download\a6e4ed99177b5f95ba446c3066c7e5e3\WindowsServer2003-KB968816-x86-ENU.exe (full file).
    2009-10-25 20:38:28:607 1100 3844 Agent *********
    2009-10-25 20:38:28:607 1100 3844 Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2009-10-25 20:38:28:607 1100 3844 Agent *************
    2009-10-25 20:38:31:170 1100 3ce0 DnldMgr WARNING: BITS job {FD881466-3DBA-406B-80A3-84A74968AC45} failed, updateId = {87BE6BB0-DEE3-4FFC-88F8-9F749DA78E7E}.101, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:31:170 1100 3ce0 DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:31:170 1100 3ce0 DnldMgr   Failed job file: URL = http://servername:8530/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\2f74ee982ee5e98ef63f2e309e8c53cf\WindowsServer2003-KB973346-x86-ENU.exe
    2009-10-25 20:38:31:170 1100 3ce0 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:36:889 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {78AB071D-096A-48AA-BE36-A74D55FBC047}]
    2009-10-25 20:38:36:889 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:36:889 1100 1dec DnldMgr WARNING: BITS job {4F048619-C64E-4991-B9EA-160F22CF3E29} failed, updateId = {B9EA7807-4095-49BE-8E85-3AF943123177}.100, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:36:889 1100 1dec DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:36:889 1100 1dec DnldMgr   Failed job file: URL = http://servername:8530/Content/E3/606124C5BF0341BEF494034B5820EB96786B45E3.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\268403b346af32b9db23b86012bd1876\WindowsServer2003-KB973815-x86-ENU.exe
    2009-10-25 20:38:36:889 1100 1dec DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:36:904 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {62C31B2C-BC81-4C7C-BF4F-6D75C3FEF5C5}]
    2009-10-25 20:38:36:904 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:37:233 1100 3f98 DnldMgr WARNING: BITS job {9764175F-3096-45DB-8E93-6A190992B20D} failed, updateId = {45CDD13B-8525-46E2-B998-DB4D9DC328C4}.101, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:37:233 1100 3f98 DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:37:233 1100 3f98 DnldMgr   Failed job file: URL = http://servername:8530/Content/B7/E6FE894A7B5D49759CD1AF5FED0668C85783A7B7.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\e43f388aa160bd3b776d7854bbebf8ea\WindowsServer2003-KB971657-x86-ENU.exe
    2009-10-25 20:38:37:233 1100 3f98 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:37:233 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {901CC533-EEE0-493A-812C-B9104AC311AA}]
    2009-10-25 20:38:37:233 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:40:264 1100 1dec DnldMgr WARNING: BITS job {99DE61AA-1548-4533-9FCB-0E072883F67F} failed, updateId = {71F57409-497E-4E46-BA7B-CBC152616029}.101, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:40:264 1100 1dec DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:40:264 1100 1dec DnldMgr   Failed job file: URL = http://servername:8530/Content/1D/5B459DAB51504018FE1AEE3C4C9AA8D08BC00F1D.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\7f2204cbdd636b3eab4913701b312049\WindowsServer2003-KB971633-x86-ENU.exe
    2009-10-25 20:38:40:264 1100 1dec DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:40:264 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {9BA1663D-827C-4FAF-8A46-C610E155623A}]
    2009-10-25 20:38:40:264 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:41:889 1100 155c AU WARNING: AU found no suitable session to launch client in
    2009-10-25 20:38:41:889 1100 3844 Report REPORT EVENT: {43B6948A-A1CC-41EB-98D5-654F1304B941} 2009-10-25 20:38:36:889-0700 1 161 101 {78AB071D-096A-48AA-BE36-A74D55FBC047} 101 80244019 AutomaticUpdates Failure Content Download Error: Download failed.
    2009-10-25 20:38:41:889 1100 3844 Report REPORT EVENT: {B89F1C29-0885-4E2E-9386-BB99881C8246} 2009-10-25 20:38:36:889-0700 1 161 101 {62C31B2C-BC81-4C7C-BF4F-6D75C3FEF5C5} 100 80244019 AutomaticUpdates Failure Content Download Error: Download failed.
    2009-10-25 20:38:41:889 1100 3844 Report REPORT EVENT: {E783EB1A-A875-4DAD-9727-31D7C949A329} 2009-10-25 20:38:37:233-0700 1 161 101 {901CC533-EEE0-493A-812C-B9104AC311AA} 101 80244019 AutomaticUpdates Failure Content Download Error: Download failed.
    2009-10-25 20:38:41:889 1100 3844 Report REPORT EVENT: {6DB435D2-6AB0-48BB-A45D-B67D97F511ED} 2009-10-25 20:38:40:264-0700 1 161 101 {9BA1663D-827C-4FAF-8A46-C610E155623A} 101 80244019 AutomaticUpdates Failure Content Download Error: Download failed.
    2009-10-25 20:38:44:295 1100 3f98 DnldMgr WARNING: BITS job {7ADE3410-1CBC-4BE7-8BA7-695807035E06} failed, updateId = {87EC2E8A-9B76-49C3-AFCD-AB1DE796CFD6}.101, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:44:295 1100 3f98 DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:44:295 1100 3f98 DnldMgr   Failed job file: URL = http://servername:8530/Content/F9/CEF55A0F6292FF278B2C61692488EE7BA6861CF9.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\58d43c598b94fd83cd83f51e6c052c9a\WindowsServer2003-KB956844-x86-ENU.exe
    2009-10-25 20:38:44:295 1100 3f98 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:44:295 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {AA73E543-51D9-4FFC-A7BD-C17E5AFC6A89}]
    2009-10-25 20:38:44:295 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:48:326 1100 3f98 DnldMgr WARNING: BITS job {7F9C7499-B444-48B1-AA91-829A46A310BE} failed, updateId = {AB14BA6D-D5D5-423A-A374-42732F8E839A}.100, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2009-10-25 20:38:48:326 1100 3f98 DnldMgr   Progress failure bytes total = 0, bytes transferred = 0
    2009-10-25 20:38:48:326 1100 3f98 DnldMgr   Failed job file: URL = http://servername:8530/Content/5D/ADFE4F7410D3633E51F8CE7A7346FB52CA6A345D.exe, local path = C:\WINDOWS\SoftwareDistribution\Download\75e822d69e8a1da6af968df52c21f121\WindowsServer2003-KB968389-x86-ENU.exe
    2009-10-25 20:38:48:326 1100 3f98 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2009-10-25 20:38:48:326 1100 88c AU >>##  RESUMED  ## AU: Download update [UpdateId = {78B86D45-2B71-447D-AE7B-CEDF21E63416}]
    2009-10-25 20:38:48:326 1100 88c AU   # WARNING: Download failed, error = 0x80244019
    2009-10-25 20:38:48:326 1100 3844 Report REPORT EVENT: {8CEF6346-3237-4872-8771-26AA7329F92C} 2009-10-25 20:38:44:295-0700 1 161 101 {AA73E543-51D9-4FFC-A7BD-C17E5AFC6A89} 103 80244019 AutomaticUpdates Failure Content Download Error: Download failed.
    2009-10-25 20:38:48:326 1100 88c AU AU checked download status and it changed: Downloading is paused
    2009-10-25 20:38:52:358 1100 1dec DnldMgr WARNING: BITS job {DF7955F3-B7A3-489C-ACFA-51AFDB67DB5D} failed, updateId = {3AF1286F-79CA-4E09-88D7-3

  • Tuesday, October 27, 2009 4:20 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Well....

    since you've masked the servername in the URL, there's not much I can help you with...

    but you've generally got the right answer: The Clients are not finding the Server!

    But let's compare the two log files....

    From the client: Server URL = http://servername/ClientWebService/client.asmx
    From the server: Failed job file: URL = http://servername:8530/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe

    So you have two different logs, with two different URLs, and both of them are failing.

    I'd say either the WSUS server isn't at "servername", or DNS isn't properly resolving the correct IP Address for "servername".

    And, to repeat myself, albeit with a bit wider scope -- all of this seems pretty ODD to me if you really did follow the instructions, as written, in the cited Technet article. I would suggest working through those instructions again paying particular attention to the steps listed in this section:

    Check connectivity from the client computer to the WSUS server and debug any issue found.
    a. Open a command window.
    b. Verify the client computer has a valid IP address: type ipconfig /all
    c. Verify the client computer can reach the WSUS server: type ping <:server name or IP address>
    d. Verify the client computer can reach the WSUS HTTP server: type http://<servername>/selfupdate/iuident.cab. This will return with the option to download the cab file.

    I'd just about stake my rep on the fact that one of those three steps above (b, c, d) results in a failure.



    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Tuesday, October 27, 2009 4:41 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    O ok, sry about that.
    servername is nl-sbs-srv

    but all a,b,c,d do work and I quadriple checked.
  • Tuesday, October 27, 2009 6:36 PMcdobbs Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Have you read this article yet? It relates to your error code and it may be the mime type psf didn't get registered in the IIS Manager.  http://forums.techarena.in/server-update-service/462360.htm
  • Tuesday, October 27, 2009 8:47 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I just read it thanks for the heads up. I registered the mime type and then restarted the  Windows Update but its comming up with the same error.
  • Tuesday, October 27, 2009 9:09 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    O ok, sry about that.
    servername is nl-sbs-srv

    but all a,b,c,d do work and I quadriple checked.
    Okay.. so.. if all of [b], [c], and [d] were successful....

    We need to find an explanation for this:
    [1] A client machine returns an HTTP 404 error from this URL:
    >>Server URL = http://servername/ClientWebService/client.asmx
    >>2009-10-26 15:44:00:071  936 7b0 PT WARNING: GetConfig failure, error = 0x80244019

    [2] A server (the WSUS Server?) returns an HTTP 404 error from this URL:
    >>URL = http://servername:8530/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe,
    >>2009-10-25 20:38:31:170 1100 3ce0 DnldMgr Error 0x80244019 occurred while downloading update

    Now, assuming there really is a WSUS Server functioning at http://nl-sbs-srv (and OH! how it would have helped to have known 24 hours ago that this machine is a Domain Controller -- and an SBS server to boot! -- I'm going to assume SBS2003, but please correct me if that assumption is incorrect).... So...

    Now knowing that, the client's HTTP 404 error is perfectly expected, because http://servername (e.g. http://nl-sbs-srv) is an invalid URL for WSUS. The correct URL for WSUS on an SBS server is *always* port 8530 -- http://servername:8530 (e.g. http://nl-sbs-srv:8530).

    So, with that, we can focus on why the "server" (and now it's critical to know - is this log from the SBS/WSUS server, itself, or from a different server) is getting HTTP 404 errors.

    The other thing I note is that the "server" log is from SUNDAY around 8:40pm (local), and the "client" log is from MONDAY around 3:45pm (local), so the other question I want to ask is this: Did you change any Group Policies or other WSUS/WUAgent configuration settings between 8:30pm Sunday and 3:30pm Monday? How is is that the server has the correct URL on Sunday, but the client has an incorrect URL on Monday?

    And, just to cover all bases, because I don't see in the thread where this fact has been established --- does the ~\WSUS\WSUSContent\DE folder actually have a file named B845647F10064A40AEA18E231AABB4B80644F1DE.exe? (or any of the other files listed in the logfile as being "missing"?)

    Or, did you by any chance, MOVE the ~\WSUS\WSUSContent folder to a new location recently?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Tuesday, October 27, 2009 9:43 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Yup! Sry I left out this important information, but you are correct, its running sbs2003.

    Very interesting though, can't believe I missed that:

    1. This server log was taken from the sbs/wsus server that's getting the http 404 errors

    2. It was like that since I am not sure when when I now look back at the logs that is not pointing to port 8530, and I did not change any group policies, but we did have to reconfigure our IIS some time ago

    3. The files are still there, fortunately/unfortunately , and I just checked the folder is in the correct location ~\WSUS\WsusContent\


  • Tuesday, October 27, 2009 9:47 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    i meant 2. it was not pointing to the correct port 8530 since the beginning
  • Wednesday, October 28, 2009 4:12 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    If you plug this URL into Internet Explorer on the SBS/WSUS server, what results do you get?:
    http://nl-sbs-srv:8530/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Wednesday, October 28, 2009 3:41 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    No I can't access the file through http for some reason. I can get into the directory ~\contents\DE but can't load the exe file. Cab files are ok, txt files are ok, but can't find the exe files.
  • Wednesday, October 28, 2009 8:57 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I just went into the physical folder and all the exe files are there and I can run them
  • Wednesday, October 28, 2009 9:33 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    ok I think I got the executable running by changing execute permissions to scripts only
  • Wednesday, October 28, 2009 10:05 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    and then i went into the registry and changed it to point to port 8530. So it seems to be talking now. But now I have to do that to every computer in the office?
  • Thursday, October 29, 2009 6:27 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    ok I think I got the executable running by changing execute permissions to scripts only

    The execute permissons on the CONTENT v-dir should be *NONE*.

    See Appendix C: IIS Settings for Web Services in the WSUS Operations Guide for the correct IIS permissions for WSUS resources.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Thursday, October 29, 2009 6:27 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    and then i went into the registry and changed it to point to port 8530.
    Went into the registry on what machine?
    And changed *what* to point to port 8530?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Tuesday, November 03, 2009 5:11 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    on the client machine, because it was just pointing to the server with out the '8530' for instance that's why its not finding it: http://nl-sbs-srv/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe



    The client though, now is still getting an error

    {51F4E0CF-B8AC-452A-9995-D16851A80196} 2009-11-03 08:46:26:655-0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 c80003fa AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0xc80003fa.
  • Tuesday, November 03, 2009 10:47 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    and I 've checked and corrected all the permissions required in the v-directory, thanks for the link.
  • Wednesday, November 04, 2009 6:03 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    on the client machine, because it was just pointing to the server with out the '8530' for instance that's why its not finding it: http://nl-sbs-srv/Content/DE/B845647F10064A40AEA18E231AABB4B80644F1DE.exe



    The client though, now is still getting an error

    {51F4E0CF-B8AC-452A-9995-D16851A80196} 2009-11-03 08:46:26:655-0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 c80003fa AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0xc80003fa.
    Changing the port on the URL configured in the client's registry will not repair/remediate defective URLs provided by the WSUS Server for download locations of binary packages.

    The URL used to specify the download location is initialized at installation time and stored in the database. If the correct WSUS Server URL is port 8530, then it would appear to have been manually changed since WSUS was installed; but since this is an SBS server, we know, factually, that the installation point has always been 8530, so the above URL simply isn't possible to be served up on an SBS machine unless you've run the 'wsusutil usecustomwebsite' command inappropriately and made the WSUS server believe it now exists on port 80.

    Please run wsusutil usecustomwebsite true to ensure that the WSUS server is properly configured =internally= to use the port 8530 URL.
    Then purge the download queue on the client using bitsadmin /reset /allusers
    And rerun the detection on this client


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Wednesday, November 04, 2009 6:07 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    No I can't access the file through http for some reason. I can get into the directory ~\contents\DE but can't load the exe file. Cab files are ok, txt files are ok, but can't find the exe files.

    1. What is the exact, full, pathname of the location of the ~\DE subfolder containing this content file?

    2. What is the exact, full, pathname configured for the 'Content' v-dir in the "WSUS Administration" website in IIS?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Wednesday, November 04, 2009 9:29 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    On the server its just : E:\WSUS\WsusContent\DE, but I can run executables now, thanks.
    for the v-dir its just http://nl-sbs-srv:8530/Content/DE


    And I just reset WSUS server so that it uses port 8530 using the command you provided, thanks.

    weird thing is, i now check the client logs and i see sucessful software synchronization, BUT, on the server in the event logs I still see that all the clients have not reported back in the last 30days, why's that?

  • Thursday, November 05, 2009 7:43 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    On the server its just : E:\WSUS\WsusContent\DE, but I can run executables now, thanks.


    But you're not supposed to *RUN* executables from the web server.

    They're supposed to DOWNLOAD and be installed by the WUAgent.


    for the v-dir its just http://nl-sbs-srv:8530/Content/DE

    The virtual directory should be pointing to E:\WSUS\WSUSContent; I asked about the *pathname* configure for the v-dir, not the URL.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
  • Thursday, November 05, 2009 10:32 PMwamo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Yes, that's correct the pathname is E:\WSUS\WSUSContent.

    but, I am continuing to get event ID 13032 from Windows Server Update: Many client computers have not reported back to the server in the last 30 days. 42 have been detected so far.

    Which is weird because when i look at the windowsupdate.log and reportingevents.log on the client side, i do see that it is synchronizing.