locked
Software Updates Deployment fails after enabling HTTPS. Scan failed with error = 0x80244019 RRS feed

  • Question

  • I have just switched to SSL on an existing 1606 site installed on Server 2012 R2.  The clients have certificates installed and other HTTPS functions are working and the clients show status as PKI.

    I tried testing SUP functionality by uninstalling a couple of updates and doing a software updates deployment evaluation scan.

    Updates were not redownloaded.  So, I looked in the wuahandler.log and found the errors below.

    I tried disabling the Windows firewall on the SCCM/WSUS server just in case the new port 8531 might not be open, but the same error was written in the log even with the firewall disabled.

    What else needs to be done after enabling HTTPS?

    <![LOG[Its a WSUS Update Source type ({68DA51BA-7BA1-4FF9-8351-1F3EEBD77CBB}), adding it.]LOG]!><time="22:34:03.151+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="sourcemanager.cpp:1236">
    <![LOG[Enabling WUA Managed server policy to use server: https://CMCB.ROOT.Domain.Lab:8531]LOG]!><time="22:34:03.151+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="sourcemanager.cpp:948">
    <![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="22:34:03.172+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="sourcemanager.cpp:954">
    <![LOG[Waiting for 30 secs for policy to take effect on WU Agent.]LOG]!><time="22:34:09.841+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="sourcemanager.cpp:1018">
    <![LOG[Added Update Source ({68DA51BA-7BA1-4FF9-8351-1F3EEBD77CBB}) of content type: 2]LOG]!><time="22:34:39.845+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="sourcemanager.cpp:1269">
    <![LOG[Scan results will include superseded updates only when they are superseded by service packs and definition updates.]LOG]!><time="22:34:39.864+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="cwuahandler.cpp:3093">
    <![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="22:34:39.864+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="cwuahandler.cpp:3100">
    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="22:34:39.866+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4116" file="cwuahandler.cpp:698">
    <![LOG[Async searching completed.]LOG]!><time="22:34:39.943+420" date="10-29-2016" component="WUAHandler" context="" type="1" thread="4868" file="cwuahandler.cpp:2238">
    <![LOG[OnSearchComplete - Failed to end search job. Error = 0x80244019.]LOG]!><time="22:34:39.943+420" date="10-29-2016" component="WUAHandler" context="" type="3" thread="4124" file="cwuahandler.cpp:3248">
    <![LOG[Scan failed with error = 0x80244019.]LOG]!><time="22:34:39.943+420" date="10-29-2016" component="WUAHandler" context="" type="3" thread="4124" file="cwuahandler.cpp:3704">

    Sunday, October 30, 2016 5:59 AM

Answers

  • Whats in WCM.log on the SUP? Was KB3159706 recently installed? If you do, there is some post installation steps https://support.microsoft.com/en-au/kb/3159706
    • Edited by Nick HogarthMVP Sunday, October 30, 2016 9:39 PM .
    • Proposed as answer by Ant_G Wednesday, November 23, 2016 5:09 AM
    • Marked as answer by Gerry HampsonMVP Monday, November 28, 2016 2:10 PM
    Sunday, October 30, 2016 9:38 PM

All replies

  • For the HTTPS set up, did you add the certificate to some of the virtual directories? Ie ClientWebService; DSSAuthWebService; ServerSyncWebService; SimpleAuthWebService. See https://www.petervanderwoude.nl/post/how-to-configure-a-software-update-point-to-use-ssl-for-communicating-with-wsus/

    Is this for just one machine or quite a few if you initiate the software scan? Are the clients going through a proxy? If yes, can you test temporarily disabling proxy on a client?


    Sunday, October 30, 2016 7:47 AM
  • I did all of the above already and it is all clients having the issue.

    No proxy.

    Sunday, October 30, 2016 8:58 PM
  • Whats in WCM.log on the SUP? Was KB3159706 recently installed? If you do, there is some post installation steps https://support.microsoft.com/en-au/kb/3159706
    • Edited by Nick HogarthMVP Sunday, October 30, 2016 9:39 PM .
    • Proposed as answer by Ant_G Wednesday, November 23, 2016 5:09 AM
    • Marked as answer by Gerry HampsonMVP Monday, November 28, 2016 2:10 PM
    Sunday, October 30, 2016 9:38 PM
  • Whats in WCM.log on the SUP? Was KB3159706 recently installed? If you do, there is some post installation steps https://support.microsoft.com/en-au/kb/3159706

    Thank you so much! Works for me!

    Monday, November 21, 2016 9:37 PM
  • Hi,

     I had the same issue few days back and i tried reinstalling the client and also the deleting collection and deleting deployment packages... but didn't work.  finally i had to uninstall SUP role and install with a reboot. Now the problem is fixed.

    Sunday, December 9, 2018 5:30 AM