I try to create a release pipeline to copy my .jar file to the target machine (Windows VM). I follow the

It works fine on most VMs, however, some VMs setting up agents with error (but the installation seems to be successful, I can find the machines on Azure DevOps). Here is the log:

I have checked that all the user accounts shown on Azure DevOps deployment group are admin permission in each VM.

Any suggestion is appreciated. Thanks in prior

[Update1] I set the path like this

I login the VM with same account, and I can see that path.

I also try to downgrade "copy file to target machine" to version "1.*", still no luck

CodePudding user response：

That's access related error. Check which account is your agent using, in deployment groups.

Can either reconfigure that account to be system account with all the privileges or give that account (used by agent) read and write privileges in that folder you making the copy.

CodePudding user response：

The task error is not related to the agent, the agent is configured and started to run.

You are using UNC path for the Destination Folder, please login the agent machine with the user which is same in your task, check if the UNC path can be accessed.

If not, please check if you have shared the Drive on the target machine, and make sure the account has write permission.

It's working fine on my side with UNC path:

It's recommended to use a local path(eg: cL\testcopy) for the Destination folder for a test firstly, it will make sure the account&Password, IP/FQDN are fine and the account has enough permission to work on target machine.