The following team project collection is stopped ... Start the collection and then try again

user_1123123 0
Viewed 2345

Background: We have an azure DevOps pipeline that we use to automatically deploy a webapp we maintain to an azure test instance.

This suddenly stopped running today with the following error.

TF24668: The following team project collection is stopped: ***********. Start the collection and then try again. Administrator Reason: abuse

where *********** is our project name.

enter image description here

It fails instantly when this happens. It doesn't appear to do anything else other than throw this error.

The developer who initially got the pipeline set up is no longer with the company.

I've looked through the DevOps interface, and I can't find what it means by this "project collection", and I can't find out how to start it.

Any ideas where I should look?

continuous-deployment azure-devops azure
4 Answers

If you are using Azure DevOps Service. This is a known issue on Azure DevOps, Microsoft Product Team has fixed it and all hosts have reboot, you could try it again and then kindly share the result here.

If you are using Azure DevOps Server, you should open Azure DevOps Server Administration Console->click the tab Team Project Collections->check the collection and ensure the state is Online, then try it again.

Note: If you do not have enough permission to do this, please contact the collection administrator to check it.

enter image description here

user_139036260

I faced the same and reported an issue on Microsoft Developer Community and got the following response

We had some bad actors using our MS-HOSTED pipelines pools in ways they should not have been, and we blocked them in order to maintain the stability of Azure Pipelines.

Full response can be found here

user_90009280
user_11231230

As stupid as it might sound there is an Azure DevOps Dashboard that states health of Azure DevOps services. I got his error on Wednesday where status of pipeline service in my region was marked as degraded. On Thursday status changed to healthy and my pipeline works!

user_20956760
Related