Exit Code:6

[DaveD]

Trying to run a Deployment. Getting Exit Code:6.

Have verified that the PC is online. I have proper administrative rights. I have verified the path to the executable.

What does Exit Code 6 indicate?

[doug]

If the same deployment is working on other computers but failing on just the one computer, then it’s likely an issue with psexec not being able to properly/successfully run on that particular computer.

If the same deployment fails on all computers, then the exit code 6 is likely being produced by the actual setup/installer that you are deploying. In that case you would need to refer to the vendor’s guide for what each exit code means.

Another thing you can test is just running ‘Check for available updates’ on the computer that is generating the exit code 6. See if it also fails with the same error, which would indicate that the issue is psexec. Also you can check ‘Check for available updates’ on all computers to further confirm the exact source of the issue.

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.

[DavidS]

I’ve known PsExec fail when PsExec is already running on the remote device.

Happened a lot with XP and not so much with W7, maybe add a task to kill remote psexec if running.

Also check usual services are running like RPC, remote registry, etc.

Has the BatchPatch folder been created?

[DaveD]

Thanks for all the suggestions.

Unfortunately, I have not had an success with them.

One additional piece of the puzzle…It is one specific deployment that is not working. There are 2 other deployments I’ve created that work, but the on is giving me problems. It works on some PCs but not others. Haven’t been able to figure out why the other 2 work and this one does not.

[doug]

Under normal circumstances when performing a deployment, the exit code is actually coming from the setup/installer application, not from psexec or BatchPatch. So if BatchPatch ‘check for available updates’ runs successfully on that same target computer where your deployment fails, then you’ll know that the issue is nothing to do with psexec but rather is due to either a problem with the deployment configuration or is the return code that the setup/installer is returning. Since you said you can successfully run the same deployment on other computers, then that would imply that there could just be an error running the setup/installer on this particular computer. In that case I would remove BatchPatch from the equation and run the setup manually on that target computer and see what it says.

[Author]

Posts