Error 1611: 233. Failure

[jparis]

On 2 servers, I am receiving this same error on both.

Server 1:

Windows Update: Error 1611: 233. Failure

Fri-16:42:16> Windows Update: Failed to obtain result. Could not find file ‘\redactedC$Program FilesBatchPatchBatchPatchTempResult.log’.

Fri-16:41:51> Windows Update: Executing BatchPatchRemoteAgent.exe…

If I try to view the batchpatch log file, it can’t find the file (no file is present in the directory), showing this error:

Fri-16:57:34> View log: Error: Could not find file ‘\redactedC$Program FilesBatchPatchBatchPatch.log’.

Fri-16:57:34> View log: Retrieving \redactedC$Program FilesBatchPatchBatchPatch.log

Server 2:

Fri-16:51:00> Windows Update: Error 1611: 233. Failure

Fri-16:51:00> Windows Update: Failed to obtain result. Could not find file ‘\redacted2C$Program FilesBatchPatchBatchPatchTempResult.log’.

Fri-16:50:35> Windows Update: Executing BatchPatchRemoteAgent.exe…

Although, this one I can view the batchpatch log file and it shows available updates (the command I previously ran).

[doug]

Sounds like an issue with PsExec not working properly on those two machines. The 233 is a Windows system error code:

ERROR_PIPE_NOT_CONNECTED
233 (0xE9)
No process is on the other end of the pipe.

I would first just test psexec at the cmd prompt from the BP computer to the problematic target computer by doing the following from the cmd prompt of the BP computer:

psexec \\targetComputer cmd

And then see if you are able to issue commands successfully. Check for the existence of the psexesvc process on the target computer.

In some cases where psexec isn’t working quite right to a particular target computer, sometimes you can simply run it from a different computer, and similarly you can end up successfully running BP from a different computer.

In other cases switching the version of psexec can seem to help. If you can find a copy of an old version (ideally v1.98), you might have luck using that instead. We’ve even heard of a couple of cases where switching to an old version of psexec and then switching back to the latest version works.

Another option is to try paexec (a clone of psexec), and see if it works in place of psexec.

-Doug

[julientheriaultACGA]

I’m also getting this error trying to push a Google Chrome install remotely on 3 devices, all giving me back the same 233 error.

I am able to issue commands remotely such as get OS version, get logged on users, but remote installations aren’t working.

Any thoughts?

[doug]

1. What version of PsExec are you using? If you have version 2.21 or 2.30, go get the latest v2.32 from Microsoft (or get previous version 2.20 if you have it saved somewhere). PsExec versions 2.21 and 2.3 contain bugs, so you should not use those versions.

2. Then on the target system, look in the services console (start > run > services.msc). If you see an orphaned PsExeSvc service, stop it. Then delete it. (If you previously were using the -r switch by enabling it in BatchPatch Tools > Settings > Remote Execution > Use psexec -r switch’, then look for orphaned services under the name that you specified there instead of under ‘PsExeSvc’). You can stop the orphaned service(s) using the GUI, but then you can delete it/them at an administrator command prompt with the following command:

sc delete psexesvc

or if you had specified a value for -r then it would instead be:

sc delete WhateverValueYouHadSpecifiedGoesHere

3. Then on the BatchPatch computer make sure you are using the new PsExec v2.32 (or use the older version 2.20 if you have it, but do NOT use the version 2.21 or 2.30.).

4. If you are using PsExec v2.32, in BatchPatch go to ‘Tools > Settings > Remote Execution’ and select ‘SYSTEM’ for all.

[julientheriaultACGA]

Sorry for the late reply, got caught up on other projects.

1) I’ve updated to the latest PsExec : 2.33
2) I’ve selected one target computer and did as you suggested, stopped and deleted “PSEXESVC” from it.
3) Ran BatchPatch one more time and I’m still getting “Exit Code: 233”

[doug]

I would suggest that you try enabling the setting:

‘Tools > Settings > Remote Execution > Use PsExec -r switch’

You can use a name like BatchPatchExeSvc or similar. See if that resolves the issue for you. Normally the cause of 233 ERROR_PIPE_NOT_CONNECTED is due to anti-virus or HIPS or similar security software running on the target computer. It severs the connection that PsExec makes. If the above-mentioned setting ‘Use PsExec -r switch’ does not work, then I would suggest you either disable the AV software (or similar software) altogether, or try whitelisting the name that you use such as BatchPatchExeSvc or whichever name you have used.

[Author]

Posts