Error trying to deploy files

[gulottc]

I am trying to deploy a file and I am using the /verysilent swtich for the file. But I get an error trying to copy the file locally saying the file is already in use? The file is not on the remote host. I am trying to execute this to several servers at the same time?? Am I doing something incorrectly?

This is the error–
09/20 09:43:49> Deployment: Error: The process cannot access the file ‘\\FIIMSOSTGDPBAS4\C$\Program Files\BatchPatch\Deployment\temp\VSCodeUserSetup-x64-1.71.2.exe’ because it is being used by another process.

Deployment
* Deploy vscode *
. . . . . . . . . .
FileToDeploy:: E:\InstallFiles\VSCodeUserSetup-x64-1.71.2.exe
CopyEntireFolder:: FALSE
LeaveEntireFolder:: FALSE
RetrieveConsoleOutput:: FALSE
Command:: “VSCodeUserSetup-x64-1.71.2.exe” /verysilent
Parameters:: /verysilent
All Messages
09/20 09:43:49> Deployment: Error: The process cannot access the file ‘\\FIIMSOSTGDPBAS4\C$\Program Files\BatchPatch\Deployment\temp\VSCodeUserSetup-x64-1.71.2.exe’ because it is being used by another process.
09/20 09:43:49> Deployment: Copying file(s) to FIIMSOSTGDPBAS4 …
09/20 09:43:49> Deployment: Queued file copy operation…
09/20 09:43:49> Deployment: Establishing connection…
09/20 09:43:48> Deployment: ‘Deploy vscode’ queued…
09/20 09:43:08> Deployment: Error: The process cannot access the file ‘\\FIIMSOSTGDPBAS4\C$\Program Files\BatchPatch\Deployment\temp\VSCodeUserSetup-x64-1.71.2.exe’ because it is being used by another process.
09/20 09:43:08> Deployment: Copying file(s) to FIIMSOSTGDPBAS4 …
09/20 09:43:07> Deployment: Queued file copy operation…
09/20 09:43:07> Deployment: Establishing connection…
09/20 09:43:07> Deployment: ‘Deploy vscode’ queued…
09/20 09:41:33> Deployment: Error: The process cannot access the file ‘\\FIIMSOSTGDPBAS4\C$\Program Files\BatchPatch\Deployment\temp\VSCodeUserSetup-x64-1.71.2.exe’ because it is being used by another process.
09/20 09:41:33> Deployment: Copying file(s) to FIIMSOSTGDPBAS4 …
09/20 09:41:33> Deployment: Queued file copy operation…
09/20 09:41:33> Deployment: Establishing connection…
09/20 09:41:33> Deployment: ‘Deploy vscode’ queued…
09/20 09:39:01> Deployment: Error: Failed to create remote working directory. Please check permissions on the target computer and verify your target working directory path in Actions > Deploy > Create/modify deployment: The network name cannot be found.
09/20 09:39:01> Deployment: Queued file copy operation…
09/20 09:39:01> Deployment: Establishing connection…
09/20 09:39:01> Deployment: ‘Deploy vscode’ queued…
————————————————————————-

[doug]

Something is preventing BatchPatch from copying the file to the target computer.

I would suggest you first make sure that you are not attempting to have multiple rows in BatchPatch deploy to the same target computer at the same time. Based on what you’re seeing it seems like there could be something like that occurring. BatchPatch can’t copy the file to that location because the file is already there and in use. You said the file isn’t already there, so that makes me wonder if you have two rows trying to put it there at the same time, and neither is able to do it successfully as a result.

Next I would suggest rebooting both the BatchPatch computer and the target computer.

Next I would double-check the permissions on the target computer remote working directory (C:\Program Files\BatchPatch) and make sure something didn’t get hosed up that is preventing BatchPatch from doing what it needs to do. You can also delete the BatchPatch folder, if needed, and then let BatchPatch create it again from scratch.

Next I would check to see if something on the target computer is somehow locking the file as soon as BP starts copying it there. I’m not sure exactly how this could be possible until the file copy completes successfully, but maybe there is anti-virus or similar security software locking the file for a scan.

Those are all just best guesses. I can’t really say for sure exactly what the issue would be or would be caused by because the issue that you are encountering doesn’t appear to have anything specific to do with BatchPatch. It looks like something in the environment or your particular setup or configuration is creating the block/lock, so you’ll have to examine the computers and your setup/config to see if you can determine what it might be.

[Author]

Posts