TFS 2017 (on premise) vNext Build stuck with status 'cancelling'
I have configured a build server for TFS 2017 and vNext build for my web application. This was working fine until yesterday. Suddenly I started getting the message "Waiting for an available agent" when I try to queue the build. Even if I hit cancel, the build is stuck with the status 'cancelling'.
- Agent pool is green. All demands match with the build expectation.
- Have restarted the Agent service on the build server.
- Also tried restarting the "Visual studio backgroud agent job service" as suggested in this question
- Agent doesn't have any log file after build stopped working.
Has anyone faced / solved similar issue?
Just try below things to narrow down the issue:
- Check if the agent machine is out of space.
- Clean up the agent machine: Delete the file items under "
_work" folder of the build agent. - Restart the TFS Server.
- Restart the agent machine.
- Change another available account for agent service, restart the service.
- Re-configure the agent
- Deploy a new agent. See Deploy an agent on Windows
UPDATE:
Based on your clarification, seems it's caused by "Visual studio Team Foundation backgroud job Agent" service.
Generally deploy new agent will work, if it's not working, then it more likely to be the service problem. So just try to restart the "Visual studio Team Foundation backgroud job Agent" service (try this several times).
If that still not work, just try to change another vailable account for the Agent service. Then try it again.
- Change appx package version from vNext build
- How to change setup project version (in TFS 2015 [vNext build])
- force kms sync with powershell hangs
- TFVC: Deleting workspace fails during vnext build
- Associating Build Number with TFS Work Items after build using vNext
- How to copy a file from local work space to remote server (not a network shared path) with powershell
- How to include NUnit test output when publishing test results in Azure DevOps?
- Is there a standard way to add some approval procedure/or at least notification for changes in task groups/builds/etc.?
- How to spawn an offline process from a TFS vNext build step that would last beyond the build?
- How to report build progress to TFS vNext from within a powershell script?
- When to use shallow fetch different from 1
- Why one can set TFS predefined variables when they are said to be read-only?
- vNext Build pipeline to sync remote git into local repository
- Powershell script is not installing an exe while i try it runs through TFS Build
- I can start the same build definitions multiple times and they are processed parallel, how can I deny this behavior?
- TFS vNext Releases - Force Onto Specific Pipeline/Concurrent Job
- Revision number is not updated properly in VNext builds
- In TFS 2015, for failed VNext builds, are the steps (build tasks) the build failed on stored in DB anywhere
- Continuous Integration build over TFS2017
- vNext build initialize job fails with "Object reference not set to an instance of an object."
- TFS 2017 (on premise) vNext Build stuck with status 'cancelling'
- VSTest configuration in TFS 2015 for Visual Studio 2017
- TFS vNext Build: GetSources task does not get files from folder with restricted access
- Use enumerations (dropdowns) in variables of vNext build definitions (TFS)
- TFS 2017 vNext Build: Customize fields on bugs created on build failure
- TFS 2015 / vNext Build - Set Build.Clean Control Variable in a build step
- VNext optionally label a build?
- VS402325: Work item type category Microsoft.HiddenCategory does not exist in project
- TFS Release Management 2015 - How to restrict environment deployment order
- How can I run Visual Studio tests in a vNext build as a specific user