Error: Cannot start process because a file name has not been provided.

[vinceco]

Greetings and thanks for BatchPatch!

We are experiencing an issue on some of the computers we are managing with BatchPatch 2014.10.2.12.39

We can run pretty much any action on these computers that are logging errors when we issue Remote Command 1.

The majority of our computers run the same remote command just fine.

We are trying to execute . . . gpupdate.exe /force

Please advise and thanks for your time . . . Vince

[doug]

Vince – This is peculiar. I’m not sure what to make of it, and I can’t quite decipher what you are describing.

Are you saying that the error is related to where BatchPatch.exe runs? Or are you saying that the error is related to specific target computers that have been added to a BatchPatch grid, regardless of what computer runs BatchPatch.exe?

Thanks,

Doug

[vinceco]

Hi Doug,

The error is related to specific target computers that have been added to a BatchPatch grid, regardless of what computer runs BatchPatch.exe.

Thanks . . . Vince

[doug]

Vince – this is very odd. What happens if you try to use psexec manually from the command line?

Launch a cmd on the BP computer and type the following command, where targetComputer is one of the computers that you’re getting the “Error: Cannot start process because a file name has not been provided.”

psexec \targetComputer gpupdate.exe /force

[vinceco]

Doug – This runs fine with an exit code of 0 from the BP computer and a target that fails otherwise.

[doug]

Vince – I’m at a loss here. I don’t understand what could possibly cause this to happen, and it doesn’t make any sense that it occurs on only some targets when using BP but not other targets. And then it also makes no sense that it doesn’t occur when running psexec from the command line against the targets that produce the error in BP.

What happens when you execute Remote Command 3/4 instead of 1/2 ? Any differences?

Can you confirm that PsExec is in your Windows PATH environment variable? As a test, please also try putting a copy of PsExec in the same directory as the BatchPatch.exe. Let me know if that has any impact.

Thanks,

Doug

[vinceco]

Good Mornin’ Doug!

Questions in order asked. . .

Remote Command 3/4 worked fine.

PsExec is in the PATH as I can run it from a command prompt opened in any folder.

Copied PsExec to BP folder . . . ALL IS WELL

Let’s leave it at that . . . Thanks for your time!

[doug]

No problem, Vince. I’m happy to hear that works! Very strange.

Even though it’s unclear why/how this happens, we actually have some ideas on preventing this problem from being able to occur in the first place, which we expect to add in a future build.

Thanks,

Doug

[Author]

Posts