访问被拒绝 - 从 TFS 调用 PSEXEC
我正在为 SharePoint 部署实施持续集成方案。在构建服务器上构建所有功能后，我尝试通过 PSEXEC 运行 STSADM 命令来将新功能部署到测试服务器。
当我从登录的任何计算机运行脚本时，它运行良好。当我向团队构建项目添加 exec 命令时，
<Target Name="AfterDropBuild">
<Exec Command="c:\progra~1\pstools\psexec.exe \\testserver -u mydomain\mydomainuser -p mypassword \\BuildServer\CurrentBuild\DeploymentFiles\Deploy.cmd" />
</Target>
构建部分失败，并且在构建日志中出现访问被拒绝的错误：
Task "Exec"
Command:
"c:\progra~1\pstools\psexec.exe \\testserver -u mydomain\mydomainuser -p mypassword \\BuildServer\CurrentBuild\DeploymentFiles\Deploy.cmd"
Access is denied.
我已将 TFS 服务帐户添加为构建服务器和测试上的本地管理员服务器。
为什么这可能在我作为交互式用户的任何盒子上工作，但在从构建代理运行 psexec 时却不起作用？
I'm implementing a continuous integration scenario for a SharePoint deployment. After all features have been build on the build server, I'm attempting to deploy the new features to the test server by running STSADM commands through PSEXEC.
When I run my script from any machine where I'm logged in, it runs fine. When I add an exec command to my team build project
<Target Name="AfterDropBuild">
<Exec Command="c:\progra~1\pstools\psexec.exe \\testserver -u mydomain\mydomainuser -p mypassword \\BuildServer\CurrentBuild\DeploymentFiles\Deploy.cmd" />
</Target>
The build partially fails, and I get an error that access is denied in my build logs:
Task "Exec"
Command:
"c:\progra~1\pstools\psexec.exe \\testserver -u mydomain\mydomainuser -p mypassword \\BuildServer\CurrentBuild\DeploymentFiles\Deploy.cmd"
Access is denied.
I've added the TFS Service account as a local admin on both the build server and the test server.
Any ideas of why this might be working on any box where I'm an interactive user, but not when psexec is run from the build agent?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是访问程序文件目录中的 psexec 的权限问题。我向 tfs 服务添加了读取权限，它解决了该问题。
It was a permissions issue accessing psexec in the program files directory. I added read permissions to the tfs service and it fixed the issue.