Troubleshooting Deployment Capability

[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]

This topic describes some common problems you might encounter when you deploy your application to virtual machines and offers some suggestions for solving them.

  • Deployment fails and returns a message that access is denied.

    The build agent is used to run the deployment workflow activities in the VM. If the deployment scripts fail because access is denied, then the account under which the build agent is running might not:

    • Have access to the build drop location.

    • Have permissions to run the deployment scripts (SQL changes, IIS changes, and so forth).

    • Be a member of the Administrators group on the machine. Deployment scripts typically require higher level permissions.

  • The deployment capability does not come online. Because of intermittent conditions, it is possible that the environment is not ready to run the workflow activities. When this happens, click Repair workflow capability.

  • The deployment workflow fails in the build stage. The build agent doubles as both the compilation agent and the deployment agent. When Team Foundation Server chooses the deployment entity to perform the build, the build fails. To workaround this issue, when queuing the build, specify the Name Filter to uniquely identify the compilation agent.