none
SCCM Software Updates fail with error = 0x80244022, soap client error = 10, soap error code = 0, HTTP status code = 503

    Question

  • Hello,

    I have one client that i just upgrade to SCCM 2007 client and i am running into issues on on server.  It fails to complete the scan with the following error showing up in the WindowsUpdates.log

    2012-02-08 09:52:00:734 7840 1250 COMAPI WARNING: Operation failed due to earlier error, hr=80244022
    2012-02-08 09:52:00:734 7840 1250 COMAPI FATAL: Unable to complete asynchronous search. (hr=80244022)
    2012-02-08 09:52:05:719 900 1b84 Report REPORT EVENT: {9B30FCE5-3034-458B-A510-E37B4BD3C01A} 2012-02-08 09:52:00:719-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244022 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244022.
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: GetConfig failure, error = 0x80244022, soap client error = 10, soap error code = 0, HTTP status code = 503
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: PTError: 0x80244022
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: GetConfig_WithRecovery failed: 0x80244022
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: RefreshConfig failed: 0x80244022
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: RefreshPTState failed: 0x80244022
    2012-02-08 10:06:50:939 900 1b84 PT WARNING: PTError: 0x80244022
    2012-02-08 10:06:50:939 900 1b84 Report WARNING: Reporter failed to upload events with hr = 80244022.

    All other aspects of the SCCM client are heathly - its reporting up inventory nicely, etc.  Just having an issues with the Software Updates portions of the SCCM client.

    Can  anyone tell me what the soap error 10 is?

    UpdateDeployments.log file shows:

    <![LOG[Job error (0x80244022) received for assignment ({E69129FC-60FE-41BB-841B-A8BF4083E666}) action]LOG]!><time="09:52:00.859+300" date="02-08-2012" component="UpdatesDeploymentAgent" context="" type="3" thread="7696" file="updatesassignment.cpp:1995">
    <![LOG[Updates will not be made available]LOG]!><time="09:52:00.859+300" date="02-08-2012" component="UpdatesDeploymentAgent" context="" type="2" thread="7696" file="updatesassignment.cpp:1999">
    <![LOG[Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SMS_SUMAgentAssignmentError_EvaluationJob
    {
    AssignmentId = "{E69129FC-60FE-41BB-841B-A8BF4083E666}";
    ClientID = "GUID:4A844CF7-3623-404F-96BB-6935F0EC611C";
    DateTime = "20120208145200.953000+000";
    insAssignmentId = "{E69129FC-60FE-41BB-841B-A8BF4083E666}";
    MachineName = "XXXX";
    ProcessID = 7840;
    SiteCode = "ABC";
    ThreadID = 7696;
    Win32ErrorCode = 2149859362;
    };
    ]LOG]!><time="09:52:00.953+300" date="02-08-2012" component="UpdatesDeploymentAgent" context="" type="1" thread="7696" file="event.cpp:525">

    ScanAgent.log shows

    <![LOG[Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SMS_SUMScanAgentError_ScanFailed
    {
    ClientID = "GUID:4A844CF7-3623-404F-96BB-6935F0EC611C";
    DateTime = "20120208145200.750000+000";
    ExitCode = 16418;
    MachineName = "XXX";
    ProcessID = 7840;
    SiteCode = "ABC";
    ThreadID = 4148;
    UpdateSourceUniqueID = "{0AEA745D-CD5C-4479-8240-17203D56A189}";
    UpdateType = "Microsoft Update";
    };
    ]LOG]!><time="09:52:00.766+300" date="02-08-2012" component="ScanAgent" context="" type="1" thread="4148" file="event.cpp:525">
    <![LOG[- - - - - -Scan Failed for ToolUniqueID={0AEA745D-CD5C-4479-8240-17203D56A189}, with Error=0x80244022]LOG]!><time="09:52:00.766+300" date="02-08-2012" component="ScanAgent" context="" type="3" thread="4148" file="scantool.cpp:659">

    WAUHandler.log shows

    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="09:52:00.609+300" date="02-08-2012" component="WUAHandler" context="" type="1" thread="4688" file="cwuahandler.cpp:587">
    <![LOG[Async searching completed.]LOG]!><time="09:52:00.734+300" date="02-08-2012" component="WUAHandler" context="" type="1" thread="6584" file="cwuahandler.cpp:2099">
    <![LOG[OnSearchComplete - Failed to end search job. Error = 0x80244022.]LOG]!><time="09:52:00.734+300" date="02-08-2012" component="WUAHandler" context="" type="3" thread="4688" file="cwuahandler.cpp:2966">
    <![LOG[Scan failed with error = 0x80244022.]LOG]!><time="09:52:00.734+300" date="02-08-2012" component="WUAHandler" context="" type="3" thread="4688" file="cwuahandler.cpp:3223">

    Thanks,


    • Edited by MikeSimon Thursday, February 9, 2012 3:19 AM
    Thursday, February 9, 2012 3:08 AM

Answers

  • OK -- got a little deeper -- i used the netsh winhttp show proxy command and i saw what proxy it was using and i noticed the listing for FQDNs for bypass the proxy for.  I added the domain suffix of my SCCM Server into this this -- and now it gets farther -- it actually starts to scan.  Now it looks like its erroring on with some soft of EULA message 

    2012-02-13 16:20:47:906 2488 bf4 COMAPI WARNING: ISusInternal::GetEulaText failed, hr=80240033

    Is there someway to determine what this update is?

    It doesn't seem to be a fatal error -- my WindowsUpdate.log finished with a status code of all 00000000

    • Marked as answer by MikeSimon Tuesday, February 14, 2012 4:21 PM
    Monday, February 13, 2012 9:23 PM

All replies

  • Check whether do you've any connectivity issue between the server and client?

    Also check the proxy or firewall settings.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Proposed as answer by Sabrina Shen Friday, February 10, 2012 8:50 AM
    Thursday, February 9, 2012 7:42 AM
  • check/repair the BITS on the client?
    http://support.microsoft.com/kb/836941

    Don

    Thursday, February 9, 2012 8:19 AM
  • The error presented as HTTP 503 – service unavailable

    You may also refer to the following links:

    Ports Used in Software Updates

    Examining some common problems for the Software Updates Client Agent


    Sabrina

    TechNet Community Support

    Friday, February 10, 2012 8:55 AM
  • I turned off firewall - BITS is cool -- I am able to access the SCCM/WSUS server over needed ports -- the SCCM servers is perfectly healthly otherwise -- the only thing i am seeing (common across all 3 servers failing) is this in the WindowsUpdate.log

    2012-02-13 15:45:46:109 808 898 PT WARNING: PTError: 0x80244022
    2012-02-13 16:08:05:171 808 d20 Report WARNING: Reporter failed to upload events with hr = 80244022.


    Monday, February 13, 2012 9:09 PM
  • OK -- got a little deeper -- i used the netsh winhttp show proxy command and i saw what proxy it was using and i noticed the listing for FQDNs for bypass the proxy for.  I added the domain suffix of my SCCM Server into this this -- and now it gets farther -- it actually starts to scan.  Now it looks like its erroring on with some soft of EULA message 

    2012-02-13 16:20:47:906 2488 bf4 COMAPI WARNING: ISusInternal::GetEulaText failed, hr=80240033

    Is there someway to determine what this update is?

    It doesn't seem to be a fatal error -- my WindowsUpdate.log finished with a status code of all 00000000

    • Marked as answer by MikeSimon Tuesday, February 14, 2012 4:21 PM
    Monday, February 13, 2012 9:23 PM
  • I Had this exact issue and PFB is the fix...

    http://eskonr.com/2014/02/configmgr-onsearchcomplete-failed-to-end-search-job-error-0x80244022-wuahandler-log/ 


    https://mycomputerbytes.wordpress.com/2012/07/27/http-error-503-the-service-is-unavailable/ 

    HTTP Error 503. The service is unavailable.

    27JUL

    I run a Microsoft IIS server that hosts a student application. When it was installed by a third party vendor, I gave them a specific username and password that was a Domain Admin on our Active Directory network. They installed various application pools and other items under this username.

    Once they were finished and everything was up and running, I disabled that account. Little did I know, they had installed an application pool with these credentials. So once I rebooted the server, the application pool did not start and I received a HTTP Error 503 – The service is unavailable error code.

    Once I found the application pool, I performed the following:

    1. Open IIS Manager
    2. Click on the Application Pools option in the left menu
    3. Found the application pool that was stopped, right mouse clicked and chose Advanced Settings
    4. Under the Process Model section, under the identity option, I clicked the “” button and then clicked on the SET button. I then entered the correct username and password.

    Once this was done, I right clicked the application pool and selected START. It started immediately and the 503 error was no longer a problem.

    • Edited by AdminofCM Sunday, February 18, 2018 6:43 AM
    Sunday, February 18, 2018 6:41 AM
  • I also had the same issue so I followed the below article and it worked. 

    http://eskonr.com/2014/02/configmgr-onsearchcomplete-failed-to-end-search-job-error-0x80244022-wuahandler-log/

    https://mycomputerbytes.wordpress.com/2012/07/27/http-error-503-the-service-is-unavailable/


    HTTP Error 503. The service is unavailable.

    I run a Microsoft IIS server that hosts a student application. When it was installed by a third party vendor, I gave them a specific username and password that was a Domain Admin on our Active Directory network. They installed various application pools and other items under this username.

    Once they were finished and everything was up and running, I disabled that account. Little did I know, they had installed an application pool with these credentials. So once I rebooted the server, the application pool did not start and I received a HTTP Error 503 – The service is unavailable error code.

    Once I found the application pool, I performed the following:

    Open IIS Manager
    Click on the Application Pools option in the left menu
    Found the application pool that was stopped, right mouse clicked and chose Advanced Settings
    Under the Process Model section, under the identity option, I clicked the “…” button and then clicked on the SET button. I then entered the correct username and password.
    Once this was done, I right clicked the application pool and selected START. It started immediately and the 503 error was no longer a problem.

    Sunday, February 18, 2018 7:18 AM