Azure-pipelines-tasks: Windows Machine File Copy task fails - System error 53 has occurred. the network path was not found.

Created on 9 Mar 2017 · 4Comments · Source: microsoft/azure-pipelines-tasks

Hi
I am tried to deploy build artifacts in two different environments in VSTS using two different agents. In my DEV environment deployment is done where I am using default agent but in QA environment I am getting below error, where i am using hosted agent.

Preparing task execution handler.
2017-03-09T10:36:24.4694061Z Executing the powershell script: D:\a_tasks\WindowsMachineFileCopy_731004d4-1d66-4f70-8c05-638018b222101.0.39\WindowsMachineFileCopy.ps1
2017-03-09T10:36:31.0042843Z Copy started for - 'Machine-win8'
2017-03-09T10:36:32.1822403Z ##[error]System.Management.Automation.RuntimeException: Copying failed for resource : Machine-win8
2017-03-09T10:36:32.1822403Z
2017-03-09T10:36:32.1822403Z Failed to connect to the path \Machine-win8 with the user cybage\Machine for copying.
2017-03-09T10:36:32.1822403Z System error 53 has occurred.
2017-03-09T10:36:32.1822403Z The network path was not found.

please suggest how to resolve this issue.

Release

Source

mousumid

👍1

All 4 comments

@mousumid Thanks for reporting the issue. We dont support WindowsFileCopy task in Hosted agent as hosted agent will not able to connect to local machine. Please use private agent for this scenario.

niadak on 10 Mar 2017

😕1

I am closing the issue. Please feel free to reopen if you need any additional information.

niadak on 15 Mar 2017

👎1

@niadak So how can one copy files using a hosted server? I use the Run Script task to run a deploy script that was generated by msbuild (which works and deploys to the remote server) but I have a build folder that was created through gulp and isn't part of the deploy script (I use the windows copy task but it fails with the 53 error).

metu on 9 May 2017

Hi,
I also have the same error :
"Failed to connect to the path \IP address with the user Administrator for copying.
System error 53 has occurred.
The network path was not found."

What can the issue?
My agent is installed on my work machine and the distination machine to cope the files is a simple windows server VM on AWS.
Thanks