- This topic has 18 replies, 3 voices, and was last updated 5 years, 1 month ago by .
-
Posts
-
Hello Expert
I Got an error when I use BatchPatch to patch our servers. I failed to download latest patches from WSUS server via BatchPatch. But before 2-3 months I could use BatchPatch to patch these servers. It’s wired. Hope you can help me to find out the root cause. Thanks
****************************************************************
****************************************************************
PRODL1 05/30/2017 08:24:12
::Begin online search
-102: Failed to execute the search. HRESULT: -2145107934
****************************************************************
****************************************************************
PRODL1 05/30/2017 08:32:11
::Begin online search
-102: Failed to execute the search. HRESULT: -2145107934
Matt – The HRESULT that you received translates to:
0x80244022 -2145107934 SUS_E_PT_HTTP_STATUS_SERVICE_UNAVAIL Http status 503 - temporarily overloadedThis indicates that the issue is likely something with your WSUS server or it possibly could be network related. The target computer tries to execute a search for updates on the WSUS / Windows Update server but receives back HTTP 503. If you are not using a WSUS but instead are having your computers search against Microsoft’s Windows Update or Microsoft Update servers, then most likely you would simply need to try again at a later time because their server is overloaded.
I hope this helps.
-Doug
Matt – This sounds like an issue with your WSUS. It does not sound like an issue with BatchPatch. I would expect that regardless of whether or not you use BatchPatch or instead use the Windows Update control panel GUI on an affected target computer, in either case you will receive the error.
As indicated in my previous posting, the error is
0x80244022 -2145107934 SUS_E_PT_HTTP_STATUS_SERVICE_UNAVAIL Http status 503 - temporarily overloadedAccording to this link ( https://social.technet.microsoft.com/Forums/office/en-US/7d6986cf-9110-4dc5-927e-7097e9efc943/error-0x80244022?forum=winserverwsus ):
“The question is why do only some systems get the HTTP 503 error. The first step in troubleshooting this is to find out what type of HTTP 503 error is being returned. Reviewing the IIS logs (on your WSUS) for the connection attempts from one of the affected clients will allow you to obtain the subcode, which will provide more detail.
Then refer to KB943891 for information about that specific error.
503 – Service unavailable.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 503 error:
503.0 – Application pool unavailable.
503.2 – Concurrent request limit exceeded.
503.3 – ASP.NET queue full”
Do you have a proxy? I wonder if possibly this could be a proxy issue? Just in case, you might also check this link:
Excellent. Glad you got it figured out. Thanks for confirming.
-Doug
Hi Expert,
Previously I was able to use the BatchPatch without any issues but recently I have been running into the below errors;
Thu-09:56:31> Windows Update: Error 1611: 5. Failure
Thu-09:56:31> Windows Update: Failed to obtain result. Could not find file ‘\computernameC$Program FilesBatchPatchBatchPatchTempResult.log’.
Thu-09:56:31> Windows Update: Could not find file ‘\computernameC$Program FilesBatchPatchBatchPatchTempHistory.log’. HRESULT: -2147024894
Thu-09:56:26> Windows Update: Executing BatchPatchRemoteAgent.exe…
Thu-09:56:22> Windows Update: Attempting to initiate Windows Update (Action: Retrieve update history) …
Thu-09:56:22> Windows Update: Establishing connection…
Thu-09:56:22> Windows Update: Initializing…
Thu-09:56:22> Windows Update: Queued…
Please help
Regarding Windows Update: Error 1611: 5. Failure
This likely means that PsExec is failing to work properly.
1. If all target computers are affected then first try ‘Tools > Settings > Remote Execution > Use PsExec -r switch…’ and provide a name in that field such as BatchPatchExeSvc.
If the suggestion in 1. works, then it indicates that probably the issue is being caused by anti-virus or HIPS or other security software in your environment that is blocking PsExec from working. If it does not work, then try 2.
2. Try running BatchPatch from a different computer. If this works, then it indicates that PsExec has somehow broken or failed on the original computer. If this does not work try 3.
3. Try substituting PaExec for PsExec by renaming PaExec to PsExec. See if it also fails. Frequently when PsExec “breaks” on a computer, PaExec also breaks, further indicating something is not functioning properly in the system.
4. If you’re still stuck, try the BatchPatch troubleshooting guide to narrow down the source of the problem.
For all other -102 HRESULT values, please see batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
- You must be logged in to reply to this topic.