Geek Answers Handbook

Failed to start test run: unable to start agent process (Visual Studio 2010)

When I try to run all the unit tests in my solution (Visual Studio 2010), I get "Error starting test run xxxx @MACHINENAME 2010-06-23 14:01:36": the agent process cannot start 'error. Does anyone know what causes this particular error, and how to resolve it so that I can run my unit tests?

thanks

+6
unit-testing visual-studio-2010 ide mstest
source share
5 answers

I don’t know if this is still the case for Visual Studio 2010, but you can have the same scenario in Visual Studio 2008. If you cancel the unit test run (that is, if an error code is found while debugging the unit test), it will leave the process neglected.

A process that impedes execution for Visual Studio 2008 and needs to be killed in order to be able to unit test again is VSPerfMon.exe. Maybe it is a must to look for VS2010.

+3
source share

I know this question was asked long before .NET 4.5, but I found that I was getting this error on VS2010 after installing .NET 4.5.

The "solution" (not the most useful, I know) is obviously to remove .NET 4.5. I assume / hope that at some point there will be an update for Visual Studio 2010 to solve this problem.

UPDATE

I had a similar error while trying to run tests that used TypeMock. To solve the problem, I opened my solution in Visual Studio and selected Test Test Test Settings. In the Test Parameters dialog box, I selected Hosts and switched it to Run Tests in a 64-bit process on a 64-bit machine.

+3
source share

Perhaps this is due to the fact that you previously ran the tests and stopped them before they were completed (perhaps due to the fact that you debugged and you hit the breakpoint), leaving the test agent process still running, then you cannot start the second one instance. The process name is eluding me at the moment, but if you find the process in the task manager and kill it, I hope this will solve your problem.

0
source share

I had a similar problem in VS 2008. I only solved it after disconnecting the second network adapter (or all adapters except one). Try it, it can help for VS 2010.

0
source share

I get this error in VS 2013 RC (in beta) and found that closing and reopening VS makes it go away.

0
source share

More articles:


All Articles