azure-pipelines-agent: config.cmd throws "dotnet has stopped working"

We have a VSTS Agent running on our environment to make a continuous integration. It was working fine on the last months.

Today, Windows Server 2012 R2 performed a blue screen and now it is not working anymore. The Service is running on the windows services list as usual but on the VSTS online it shows that the agent is offline. So, we decide to try to reconfigure the agent and when we try to run the command:

PS> .\config.cmd remove

on the poweshell, we got the error message:

enter image description here

I am not sure if it is a Windows problem or the an agent setup or even a dotnet setup. Any command I try to run such as:

 PS> .\config.cmd help
 PS> .\run.cmd

I got this same message. I have tried all these commands and without success.

How can I solve this problem? It was working fine but not it just stopped because of a blue screen.

Agent version and platform

Agent 2.119.1.

VSTS type and version

On-Prem VSTS 2017

If VisualStudio.com, what is your account name? http://gantc.visualstudio.com

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

@felipeoriani can you take a process dump and share with me?