Windows desktop/laptop scan fails with windows update server in SCCM 2012 with error message 0x80072ee2
Issues: We are facing issues with SCCM 2012 client scan(windows 7) with windows update server. The error message in Wuahandler.log is "OnSearchComplete - Failed to end search job. Error = 0x80072ee2.".
Environment detail:
PSS - we have a single primary site server SCCM 2012 R2 with SP1 in datacentre 1 in a virtual server (win serv 2012 R2 with 5.5 GB physical memory).
XYZ - This server in the datacentre 1 having windows server 2008 R2 with 32GB internal memory. This server is installed with distribution point, fallback status point and management point.
ABC - This server is in datacentre 2 having windows server 2008 R2 with 32GB internal memory. This server is installed with distribution point, Reporting service Point, management point and software update point.
We have around 4000 win 7 device(laptop/desktop) and 2000(win 10 device win7 and win 10), all getting patched with SCCM. We are deploying all the October month OS, .Net Framework, IE and Office patch to these win 7 and win 10 device.
Initial troubleshoot: Since most of the blogs and website point toward increasing the private memory of WSUS pool under IIS so I have changed the private memory to 0 and also the queue length to 2000. I also restarted the server ABC but no luck.
Few logs detail:
WuaHandler.log (Scan failed with error = 0x80072ee2.)
Update Store: No error found here. Querying update status completed successfully and all the missing and installed updates are reflecting here.#
Windowsupdate.log - WARNING: Send failed with hr = 80072ee2. WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
One strange thing is the patch deployed successfully over the weekend. But during weekdays this gives us scan error.
Environment detail:
PSS - we have a single primary site server SCCM 2012 R2 with SP1 in datacentre 1 in a virtual server (win serv 2012 R2 with 5.5 GB physical memory).
XYZ - This server in the datacentre 1 having windows server 2008 R2 with 32GB internal memory. This server is installed with distribution point, fallback status point and management point.
ABC - This server is in datacentre 2 having windows server 2008 R2 with 32GB internal memory. This server is installed with distribution point, Reporting service Point, management point and software update point.
We have around 4000 win 7 device(laptop/desktop) and 2000(win 10 device win7 and win 10), all getting patched with SCCM. We are deploying all the October month OS, .Net Framework, IE and Office patch to these win 7 and win 10 device.
Initial troubleshoot: Since most of the blogs and website point toward increasing the private memory of WSUS pool under IIS so I have changed the private memory to 0 and also the queue length to 2000. I also restarted the server ABC but no luck.
Few logs detail:
WuaHandler.log (Scan failed with error = 0x80072ee2.)
Update Store: No error found here. Querying update status completed successfully and all the missing and installed updates are reflecting here.#
Windowsupdate.log - WARNING: Send failed with hr = 80072ee2. WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
One strange thing is the patch deployed successfully over the weekend. But during weekdays this gives us scan error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ok - cool - i had assumed that the WSUS server itself was up to date - but good point, i didnt think of that.
glad that you found the solution.
glad that you found the solution.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: 'tif tif' (https:#a42723115)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: 'tif tif' (https:#a42723115)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
This is most commonly caused by the WSUS application pool in IIS stopping / being overloaded - which in turn is caused by not cleaning out the old and unused updates out of the WSUS database.
Please refer to my blog article @ https://blog.adexis.com.au/2018/05/26/the-importance-of-cleaning-up-wsus-even-if-your-are-only-using-it-for-sccm/ for approaches you can take to fix this.
You will see that at the moment your w3wp.exe process is likely utilizing high CPU and 3-6GB of RAM
Once you decline all the un-needed updates, we generally see this drop dramatically and the client timeout issues no longer occur.