Could not find file (…).log

[ariehm]

when attempting to perform almost any operation on a remote server (stop service, reboot, remote command, etc.), the Remote Command Output Log returns a message like:

Could not find file ‘\\myserver.mydomain.tld\C$\Program Files\BatchPatch\BatchPatchRemoteProcessOutput1884146133.log’.

this occurs on all the servers in my grid, and all of the operations i’ve tried. batchpatch used to work just fine, but i hadn’t used it in several weeks before i started getting these error messages. i can’t think of anything that’s changed recently that could be causing the issue.

[doug]

Please check the ‘Remote Execution Context’ under ‘Tools > Settings > Remote Execution’

Try setting it to just ‘SYSTEM’ *without* ‘Interactive.’ This should work for most items.

If that still gives you problems, try setting it to ‘Elevated token’ *with* ‘Interactive’ and see how that goes.

https://batchpatch.com/remote-execution-context

[ariehm]

doug,

that seems to have fixed it. the contexts in that settings panel had all been set to Elevated Token, without Interactive. i changed them all to SYSTEM, leaving Interactive un-set.

not sure how this setting got changed, but it seems okay now.

thanks!

[doug]

Glad that worked. The setting didn’t change. What prob changed is you upgraded your version of PsExec. The new PsExec now usually can’t work with ‘Elevated token’ unless also enabling ‘Interactive.’ BatchPatch tries to detect your psexec version and apply settings accordingly but it cannot always successfully detect the PsExec version, so in your case it left your previous settings intact.

[huibw]

Hi, I’m having the same issue but the above suggestions don’t work: I have (many) deployments that use the ‘Retrieve output’ function. Up until maybe a few months ago this was never an issue but now it shows ‘Could not find file’. When I middle-click on the message it shows me the path, and when I copy it and paste it into Notepad to open, it comes right up. So the file exists and there are no access issues. I’ve tried the 32 bit and 64 bit version of PsExec (v2.34) but that doesn’t make a difference. Should I try an older version? Any idea what the last known good version was?

[doug]

@huibw – The issue described by @ariehm was not with deployments, so I’m not sure it’s the same issue that you are encountering.

The version of PsExec shouldn’t matter so long as the ‘Remote Execution Context’ is set properly to use either Elevated Token AND Interactive together, or use *just* SYSTEM (without Interactive). If the settings I just mentioned aren’t working, then it seems like there might be an issue with the actual deployment configuration. Not every deployment can be used successfully with ‘Retrieve output’. Are you saying that the deployment that used to always work with ‘Retrieve output’ no longer works with ‘Retrieve output’ or are the deployments that used to work with ‘Retrieve output’ not the exact same deployments that you are currently having trouble with? Also, do the deployments work if you uncheck ‘Retrieve output’ or do they still fail? It would also be helpful to see an example of the actual, verbatim error message that you are seeing.

[huibw]

Hi Doug,
I’ve tried the Remote Execution Context combos but it doesn’t make a difference: the deployment is a success but no output. See screenshots below.

[doug]

If you have an active support contract with us please contact us directly for further troubleshooting. We’ll need to see more details to assess what’s going on.

[Author]

Posts