有谁遇到过“Win32错误:找不到网络路径”吗?尝试使用 FinalBuilder 6 复制文件?
我有一个 FinalBuilder 作业,作为最后一步,将编译的应用程序和 DLL 部署到另一台服务器上的网络共享。
大约 50% 的情况下,它只是失败
Win32 错误:找不到网络路径
将目标从 \\myserver\myshare 更改为 \\myserver.mydomain.com\myshare 通常会暂时修复它 - 修改构建文件后的前 2-3 次运行将起作用,之后运行它会再次开始失败。
FinalBuilder 任务正在使用授予目标框管理员访问权限的域凭据运行;通过 Windows 资源管理器将文件复制到该服务器上的共享或从该服务器上的共享复制文件可以可靠地工作。
我完全被难住了。
I have a FinalBuilder job that, as a final step, deploys the compiled app and DLLs to a network share on another server.
About 50% of the time, it just fails with
Win32 Error : The network path was not found
Changing the target from \\myserver\myshare to \\myserver.mydomain.com\myshare will often fix it temporarily - the first 2-3 runs after modifying the build file will work, after which it'll start failing again.
The FinalBuilder task is running with domain credentials granting admin access on the target box; and copying files to/from shares on that server via Windows Explorer works reliably.
I'm completely stumped.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
终于查到了这一点。目标服务器是虚拟机,并且 Hyper-V 主机网络设置设置为“虚拟网络”而不是“虚拟分组网络”
我不知道这意味着什么,但是将其更改为虚拟分组网络后,它可以完美运行。奥奥
Finally tracked this down. The target server was a virtual machine, and the Hyper-V host network settings were set to "Virtual Network" instead of "Virtual Teamed Network"
I have no idea what that means, but having changed it to Virtual Teamed Network, it works flawlessly. O_o
未找到网络路径。
这与 DNS/WINS 无法查找名称有关。当我看到这个时,我们的 DNS 服务器出现了问题。
在lmhost 文件中添加条目将阻止系统在 DNS/WINS 中查找。
如果这不起作用,可以考虑的另一个选择是增加操作的重试次数。这可以通过单击“计时属性”在操作的“运行时”选项卡中完成
The network path was not found.
This is related to DNS/WINS not being able to look up the name. When I have seen this there are problems with our DNS servers.
Adding an Entry into the lmhost file would prevent the system from looking in DNS/WINS.
If that does not work, another option to consider is to increase the number of retries on the Action. This can be done from the "Runtime" tab of the action by clicking on "Timing Properties"