Home Dashboard Directory Help

MSTest not working after installing vs11 next to vs10 by Lesley van Zijl


 as Duplicate Help for as Duplicate

Sign in
to vote
Type: Bug
ID: 728659
Opened: 3/4/2012 3:09:57 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
User(s) can reproduce this bug


After installing visual studio 11 beta next to my already existing visual studio 2010 ultimate I can not run any unit tests in visual studio 2010. It goes to the "Unittests In progress" state but nothing actually happens. Stopping the process is also not possible.

To decrease the scope I created a new test project in a "ConsoleAplicationX" solution with only the default test case in it and tried to run this through the command line:

C:\Users\Lesley\Documents\Visual Studio 2010\Projects\ConsoleApplication1\TestPr
oject1\bin\Debug>mstest /testcontainer:TestProject1.dll
Microsoft (R) Test Execution Command Line Tool Version 10.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.

Loading TestProject1.dll...
Starting execution...

It hangs after that.

mstest in vs11 beta do worm as expected
Sign in to post a comment.
Posted by Keith Hill MVP on 2/18/2014 at 9:27 AM
Wouldn't it be FREAKING nice to have a link to the duplicate connect issue?? I think so.
Posted by Nate Jackson on 10/1/2012 at 10:32 AM
I'm seeing this same thing with the RTM of VS2012 along side of VS2010. Does anyone know of a workaround that allows *both* MSTest 2010 and MSTest 2012 to work on the same box? Did anyone figure out what the "duplicate" connect ticket was?
Posted by Brian Lachniet on 6/26/2012 at 8:36 AM
I'm seeing the same issue after installing the VS2012 RC alongside VS2010. As GSAGranet mentioned, this has been closed as a duplicate, but there is no reference to the duplicate issue. Can we have a link to it please?
Posted by GSAGranet on 5/31/2012 at 3:40 AM
"Closed as Duplicate". Can the duplicat e be referenced here?
Posted by Microsoft on 3/13/2012 at 1:51 AM
Hello Lesley,

We looked at the dump file and observed that you are running the test from visual studio 2010's mstest.exe and not from VS 11's mstest.exe as you described. This is a known issue with Visual Studio 2010 which got fixed in 2010 SP1. Can you please try installing visual studio 2010 SP1 from the below link and see whether after that it works or not?


Visual Studio Product Team
Posted by Lesley van Zijl on 3/4/2012 at 10:56 PM
Uploaded a dump with heap made with visual studio 2010 ( FeedbackID-728659.dmp 155mb ) from the MSTest.exe process.
Posted by MS-Moderator08 [Feedback Moderator] on 3/4/2012 at 6:18 PM
Thanks for reporting the issue.
Could you please provide us with a mini dump file? You can get detailed steps about how to get the dump file at :


It would be greatly appreciated if you could provide us with that information as quickly as possible.

You can upload your dump to the workspace:

Please use "FeedbackID-728659" as the file name.

Posted by MS-Moderator01 on 3/4/2012 at 5:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by Alex2550 on 9/25/2012 at 1:49 AM
Configure the following registry values on TFS Build server:

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VisualStudio\11.0\EnterpriseTools\QualityTools\ListenPortRange\PortRangeStart HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VisualStudio\10.0\EnterpriseTools\QualityTools\ListenPortRange\PortRangeEnd

More info here: http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/df043823-ffcf-46a4-9e47-1c4b8854ca13
Posted by Alex2550 on 9/25/2012 at 1:34 AM
Open Inbound Rules in Windows Firewall with Advanced Security on the TFS Build server.
Find MSTest.exe inbound firewall rule and either change it to use 2012 version or create multiple inbound firewall rules for both 2010 and 2012 version.
Posted by GSAGranet on 5/31/2012 at 3:39 AM
Reinstall VS2010 SP1 and then MSTest works in VS2010 but breaks VS11. Looks like a shared component/setting between the 2 versions.