Tuesday, December 6, 2016

SCCM windows update deployment failure 0x80240438

Windows update problem caused by web troubleshooting tools and system proxy. Netsh winhttp settings were creating a local proxy that was not causing any issues in the user context, but in the system context, it was breaking outbound web connections. SCCM logs only showed the error code, but not much useful information beyond that. WindowsUpdate.log contained a clear message on the attempted use (and failure) of a proxy.

wuauhandler.log

<![LOG[OnSearchComplete - Failed to end search job. Error = 0x80240438.]LOG]!><time=".." date=".." component="WUAHandler" context="" type="3" thread="2744" file="cwuahandler.cpp:3223">
<![LOG[Scan failed with error = 0x80240438.]LOG]!><time=".." date=".." component="WUAHandler" context="" type="3" thread="2744" file="cwuahandler.cpp:3679">

updateshandler.log

<![LOG[Updates scan completion received, result = 0x80240438.]LOG]!><time=".." date=".." component="UpdatesHandler" context="" type="1" thread="9884" file="capplicabilityhandler.cpp:100">


updatesdeployment.log

<![LOG[Job error (0x80240438) received for assignment ({guid}) action]LOG]!><time=".." date=".." component="UpdatesDeploymentAgent" context="" type="3" thread="7056" file="updatesassignment.cpp:2235">


scanagent.log

<![LOG[ScanJob({guid}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80240438]LOG]!><time=".." date=".." component="ScanAgent" context="" type="3" thread="11024" file="utils.cpp:537">


ciagent.log

<![LOG[Failed result received from applicability handler, error = 0x80240438]LOG]!><time=".." date=".." component="CIAgent" context="" type="3" thread="7056" file="capplicabilitybroker.cpp:79">


WindowsUpdate.log

yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: Web service call failed with hr = 80240438.
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: Current service auth scheme='None'.
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: Proxy List used: '127.0.0.1:8888', Bypass List used: '(null)', Last Proxy used: '127.0.0.1:8888', Last auth Schemes used: 'None'.
yyyy-mm-dd hh:mm:ss 1068 30a4 WS FATAL: OnCallFailure failed with hr=0X80240438
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: NWS retry 1 for transient error 0x80240438
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: Nws Failure: errorCode=0x803d0010
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: There was an error communicating with the endpoint at 'http://deploymentserver:8530/ClientWebService/client.asmx'.
yyyy-mm-dd hh:mm:ss 1068 30a4 WS WARNING: The given proxy cannot be reached.

------------------------------------------
netsh winhttp>show proxy

Current WinHTTP proxy settings:
Proxy Server(s) : 127.0.0.1:8888
Bypass List : (none)

8 comments:

  1. I run into this regularly and have to clear the proxy.

    netsh winhttp reset proxy

    ReplyDelete
  2. what if you need the proxy for some other purposes, but also want SCCM to patch the machine?

    ReplyDelete
    Replies
    1. If its proxy just for user purposes, typically that would be set inside the browser or other application, and it wouldn't be the same as what is set for winhttp. If you need it as a system wide proxy, then perhaps setting up a bypass entry for sccm related components would work. Just guessing here. I'm not an SCCM guy and rarely end up troubleshooting clients on my application servers.

      Delete
  3. i have same issue netsh showproxy resetproxy not works please provide a any other solution?

    ReplyDelete
  4. I am having the same issue, my netsh Netsh winhttp show proxy is showing Direct access (no proxy server).

    ReplyDelete
  5. following worked for me:
    netsh winhttp reset proxy

    ReplyDelete
  6. Any other solution, everything was working for me until two months ago, I started to get this error "OnSearchComplete - Failed to end search job. Error = 0x80240438.

    ReplyDelete