locked
WSUS Server itself does not update, error: 80244019 RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hello,

    we have set up a new WSUS Server 2012 R 2 in order to replace our old w2k3 WSUS. The WindowsUpdate information is pushed to cleints/server via GPO's. There is one GPO for all Domain Servers (WSUS is one of them). Everything works fine so far, beside WSUS it self. I mean the OS Server where WSUS Services runs on.

    WSUS Servicees work fine, we download patches from Widnows update and they are deployed, reso. requested and downloaded by all clients from our WSUS than. But the WSUS server itself when it checks for updates,it gets notified about e.g. 70 updates to be applied. Once I say install updates it returns error code  80244019.

    I have to say that the policy sets WUServer, WUStatusServer and a TargetGroup, and some other settings like reboot yes/no, etc..... Identical settings, same GPO) works for all other servers in the network.

    Also, I have set WSUS port to 80 from 8530 or 8531, whatever it was.

    telnet wsus.domain.intra 80 works from the localhost (WSUS)

    Any idea why WSUS itself is special?

    kind regards,

    Dieter Tontsch

    PS:
    this is what I see in the Event Log, ID 1001

    Fault bucket , type 0
    Event Name: WindowsUpdateFailure2
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 7.9.9600.17031
    P2: 80244019
    P3: 34CBB58A-0567-4183-80A2-4659766883DC
    P4: Download
    P5: 101
    P6: Managed {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    P7: 0
    P8: 
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17031_7184bfc5c320c0f8948b2b3ae24749b74782586_00000000_cab_0ec23fa4

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4875146-159a-11e5-80be-00505685263b
    Report Status: 4
    Hashed bucket: 


    Thursday, June 18, 2015 9:16 AM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    ...we have set up a new WSUS Server 2012 R 2 in order to replace our old w2k3 WSUS.

    Also, I have set WSUS port to 80 from 8530 or 8531, whatever it was.

    telnet wsus.domain.intra 80 works from the localhost (WSUS)

    Any idea why WSUS itself is special?

    WSUS on WS2012/R2 does not run on port 80; it runs on port 8530 (or 8531 if you implemented SSL).
    Regardless of WSUS-as-client or other clients, WSUS v6 (WS2012/R2) does not run or port 80.

    Unless you have reconfigured it to do so - which is AFAIK totally unsupported.

    IIS will be listening on the default website on port 80 but that is not WSUS client webservice.

    For the WUAgent problem on WSUS itself, just as for any other WSUS client you must examine the c:\windows\windowsupdate.log

    It may be a name resolution or routing issue, in case your WSUS is multi-homed ?

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Thursday, June 18, 2015 10:01 AM
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    Hello,
    port 80 may not be supported, but in this case it was not the issue - since my server in charge could communicate with wsus without any issue. I have switched back to 8350 however afterwards, but my update started working again after I did once "wuauclt.exe /resetauthorization /detectnow". It only started working again after that, not after any reboot or so. I guess /resetauthorization was the key parameter.

    Monday, June 22, 2015 6:59 AM