Recently,After the Path Tuesday, None of the clients which are reporting to Primary Site did not perform a successful Scan (clients beneath secondary Site are working Good) .This leads me to look at the software update logs on the client to see what is going wrong. Since most of the clients directly reporting to Primary are having issues ,so thought of checking/troubleshoot this issue on the Primary site itself .
Browse through the wuahandler.log from Drive:\Configmr\SMS_CCM\Logs,below is what I can see.
OnSearchComplete - Failed to end search job. Error = 0x80244022.
Scan failed with error = 0x80244022.
To know the error code description about ‘0x80244022’ ,use error lookup from cmtrace (ctrl+L).
Same as HTTP status 503 - the service is temporarily overloaded.
Source: Windows Update Agent
The 503 Service Unavailable error means, the problem is usually with the web site is down which is WSUS in this case.
Tried restarting the server ,followed by WSUS service and IIS service but issue still exist.
after the search on the internet,found this article ,leads me to check the application pool in IIS.I jump into IIS to check the status of WSUS application pool which was in stopped state .
After starting the wsuspool application,sync completed successfully.
Tried to initiate software update scan cycle on the client,monitor wuahandler.log
so why does the WSUS pool in IIS stopped ? that could be because of memory limit.take a look at these blogs http://blogs.technet.com/b/configurationmgr/archive/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors.aspx and http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/
Hope it helps!
27 Comments
I had this same error. In my HQ all clients can work correctly, but another site (WAN connection has firewall between sites), I create new DP to support all clients in this site. The new DP and all clients in WAN site has same error "OnSearchComplete – Failed to end search job Error 0x80244022" in WUAHandler.log. What should I do in this case? Please advise.
did you check the wsus app pool and the client logs if there is any proxy/firewall for the update scan.
also check the scanagent.log for further troubleshooting.
Thanks,
Eswar
WSUS app pool already started, no setting for proxy and firewall already allow for any service.
scanagent.log got error as below
ScanJob({447A5316-9F8F-4BA9-94EC-3FB9B2C788E6}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle.
CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022
I checked WSUS app pool already started, I do not use proxy and FW allow any services for sccm environment. I got error on scanagent.log as
ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle.
CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022
are you able to browse the WSUS URL from the client? you can get the URL of WSUS that it is trying to scan from wuahandler.log.
Thanks,
Eswar
ํYes, I can browse from the client.
I opened http://WSUSSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx URL on a web browser and got without error, but still scan failed.
I have same issue but my wsus pool is working , I don't know what to do next , next I have many devices which are ending up with this error kindly suggest me .
Hi,
you can initiate the software update scan and monitor the logs for further troubleshooting.
The logs should help you with error codes and what is going on.
Thanks,
Eswar
I had this same error. In my HQ all clients can work correctly, but another site (WAN connection has firewall between sites), I create new DP to support all clients in this site. The new DP and all clients in WAN site has same error "OnSearchComplete – Failed to end search job Error 0x80244022" in WUAHandler.log. What should I do in this case? Please advise.
I have got the same issue. But in my case i could not find the wsus pool in IIS manger. Please advise.
Hi,
IIS is prereq for WSUS . Do you have working WSUS and configuration done correctly?
can you share the IIS screenshot that has WSUS installed.
Thanks,
Eswar
Just in case this helps someone else, I had this same error due to our Palo Alto firewall receiving an update that changed it's app filtering and thus prevented the client-server traffic from reaching SCCM/WSUS. TCP ports 80, 443, 8530, & 8531 are needed for this to work. In my case, the ports were technically open, but not for the specific application as defined by Palo Alto so I ended up turning off the application level filtering and just allowing all traffic on those ports.
Thanks Jonathan ,appreciate your help on this.
Regards,
Eswar
Pingback: Config Manager Current Branch Delta Downloads and WSUS | Confessions of a Config Manager Engineer
Pingback: Windows 10 In Place Upgrade via SCCM stuck on 75% – SCCM not so common issues
I had the same issue and looking for a solution 2 days... Hope this will fix my issue
Did it solve the problem ?
I have still this issue though the WsusPool in started status. What should I do in this case?
can you restart the WSUS IIS pool ? can you look at windowsupdate.log and get the URL of WSUS and try to access using browser if you can access it or not ?
Regards,
Eswar
Thanks Eswar this helped me too. I found the WSUS pool private memory was too less as result of that it was in stopped state. When i started it scan completed successfully.
Steps to increase WSUS pool memory:
https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/
Glad it helped, thanks for the link too!
It didn't help me, mine is in running state. Pool Memory allotted 0, server RAM 128GB.
sorry posting comment to a year old post.
Thanks. Clear and precise solution.
This post was precise. It solved my issue. That was exactly the WsusPool stopped in IIS.
I ran into this same issue, i was wondering if you know why this happened? It would be good to know why it stopped so that i can prevent it in the future.
Thanks,
this could be because of apppool memory limit in IIS.have a look at this blog http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/