VSTS任务:窗口机器文件复制:系统错误53 [英] VSTS Task: Window machine file copy: system error 53

查看:76
本文介绍了VSTS任务:窗口机器文件复制:系统错误53的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试从VSTS释放到运行IIS的VM(在AWS上运行).为此,我使用三个任务.

I'm trying to make a release from VSTS to a VM(running on AWS) that is running an IIS. For that I use three tasks.

  1. Windows机器文件复制
  2. 管理IIS应用
  3. 部署IIS应用

在发布之前,我正在运行一个构建管道,该管道为我提供了一个包含Web应用程序(webapp.zip)的工件. 当我手动将其放在服务器上时,我可以运行发行版的第2步和第3步,并且该应用程序可以运行.我的问题是我没有使Windows Machine File Copy正常工作.它总是抛出异常,给出系统错误53:未找到网络路径".当然,这些机器不是域加入的,因为我正在VSTS上运行发行版,并且需要AWS VM上的文件.我试图打开端口445(用于文件共享),并确保用户具有目标计算机上目标路径的权限. 所以我的问题是:如果未将两台计算机连接在一起,我该如何真正将文件从VSTS移至AWS VM.

Before the release I'm running a build pipeline that that gives me an artifact containing the web app (webapp.zip). When I manually put it on the server I can run step 2 and 3 of my release and the application works. The problem I have is that I don't get the Windows Machine File Copy to work. It always throws an exception giving a 'System Error 53: The network path was not found'. Of course the machines are not domain joined, because I'm running my release on VSTS and need the files on a AWS VM. I tried to open port 445 (for file sharing) and made sure the user has rights for the destination path on the target machine. So my question is: How can I actually move the files from VSTS to the AWS VM if the two machines are not joined.

推荐答案

使用 FTP上传关于如何创建FTP站点,可以参考本文:

Regarding how to create FTP site, you can refer to this article: Creating a New FTP Site in IIS 7.

这篇关于VSTS任务:窗口机器文件复制:系统错误53的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆