Problem with remote working directory

[heckerbe]

Batch Patch halted in the middle of an execution of Windows updates script file. yesterday. Shut down BatchPatch and checked various machines and the Temp directory it created on each was empty. Now today, when I launched the command file again I get a message stating “Problem with remote working directory…(Upon deletion)…” It reads like there is a problem with the temp directory and files were not deleted (at least properly). I have tried killing PSEXESVC, WSUS, and MSIEXEC processes, but the only thing that has resolved this was to reboot everybody, and then it ran smooth. Is there a ‘smother’ way to kill processes upon script failure?

[doug]

The issue that you are describing sounds like BatchPatch was not the cause of the problem but rather was a symptom of an issue that occurred with the operating system. This is why you had to reboot the system to get things working again.

-Doug

[heckerbe]

Actually it was because of a faulty command file not having an end quote on the tail end of a wsus execute command with parameters. Once the problem was found, I had to terminate BP and run again. The question really is, Is there an easier way to recover from an execute error, other than rebooting everyone, i.e. halt BP, remove binding processes and re-run the command?

[doug]

Generally speaking, a reboot shouldn’t really ever be required. As for some kind of “smother” way to kill processes, BP can only currently do this for processes it knows about such as for the Windows Update menu actions that are built-in to BP. But when you execute custom commands and/or processes, BP doesn’t really know what exactly it would need to be killing. You can certainly use BP to kill remote processes by name, but you would have to insert the names yourself.

[Author]

Posts