A few different errors when attempting to run some patching on remote machines

[brad.pfeifer]

Hello

We’ve recently just purchased BatchPatch and have been patching the majority of our users workstations. It’s about a 50/50 split whether they’re going to work or not due to various errors.

Here’s what we’re getting across multiple machines using the same AV with the same rule sets.

Error 1611: -106. Failure <– This was after “Check for available updates” was ran.

Error 1611: 5. Failure <— This was also after an update check. However this was also returned in the Remote Command Output Log: Could not find file ‘\RedactedC$Program FilesBatchPatchBatchPatchRemoteProcessOutput914323758.log’.

Error 1601: Failed to retrieve WMI info. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) <– Another result after a search. We also received this message under Automatic Services: Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))

Error 1603: Initialization Failure. HRESULT -2146233080: Index was outside the bounds of the array. <– Also during a search for patches

Error 1611: 59. Failure <— This was actually during the downloading portion of the update so it might have been a user going offline.

I’ve been working specifically on error 1601, where the RPC either cancels the call or never answers. I’ve tried rebooting, restarting wuauserv, turning off all AV filters as well as stopping any firewall or av related services on the host server as well.

The account that’s logged into the host machine and running batchpatch is a domain admin which has local admin rights over all domain machines.

If there’s any further troubleshooting I could do please let me know and thank you for any help.

[doug]

Hey Brad – I’m sorry to hear that you’re encountering such difficulties.

Error 1611: -106. Failure is prob the most complicated to troubleshoot/solve error. Please see here for more:

windows-update-error-1611-106

windows-update-error-1611-106-failure

---

Error 1611: 5. Failure 5 generally means ‘Access Denied’ which is always related to permissions in some way or another. What’s strange here is where the 5 appears. Most ‘Access Denied’ errors do not occur with 1611. In this case I suspect it’s related to PsExec not having the permissions it needs on the target computer. Probably psexesvc is being blocked from running. Sometimes changing the psexec remote service name can fix this. In your case I know you have already done that, based on the forum thread that you started the other day (‘Tools > Settins > Remote execution > Use psexec -r’), so I would start by doublechecking that but also see if the issue is still related to psexec not being able to do what it needs. More here:

windows-update-error-1611-5-failure

1611-5-error-on-sccm-distribution-points

---

Error 1601: Failed to retrieve WMI info. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED)

RPC issues are usually related to firewall blocking or to inaccurate DNS or to the machine simply not existing on the network. More:

troubleshooting-common-errors-in-batchpatch

---

Error 1603: Initialization Failure. HRESULT -2146233080: Index was outside the bounds of the array. This would likely mean that something is broken with WMI on the target computer. I would start by trying ‘Actions > Get info > Get last boot time’ and ‘Actions > Get info > Get MAC address’ because both of these actions use only a WMI query. See if these actions are successful. If not then you know you probably have an issue with WMI on the target. Reboot the target and try again. If still the same issue then have a look at Microsoft’s WMI troubleshooting article here: https://msdn.microsoft.com/en-us/library/aa394603%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

---

Error 1611: 59. Failure translates to

ERROR_UNEXP_NET_ERR

59 (0x3B)

An unexpected network error occurred.

This is probably a transient error. You are correct that this might have occurred as the result of the target user going offline during the operation, especially considering that it did not happen until after the downloading had already begun.

---

[Author]

Posts