TFB210610: 'MSTest.exe' returned '128' - by Sander van deVelde

Status : 


Sign in
to vote
ID 525409 Comments
Status Active Workarounds
Type Bug Repros 1
Opened 1/17/2010 2:35:05 PM
Access Restriction Public


When running a build on TFS 2010 (Beta 2 - Basic installation) i get 

TFB210610: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '128'.

The build is then "partially succeeded" in stead of (fully) succeeded


Full Summary:
Mixed Platforms | Debug
 0 error(s), 0 warning(s)
 1 projects/solutions compiled
 1 test run(s) completed - 100% average pass rate
 2 binaries instrumented - 52% of all code blocks covered
Other Errors and Warnings
 1 error(s), 0 warning(s)
 TFB210610: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '128'.
Sign in to post a comment.
Posted by Andy Hennah on 9/14/2011 at 2:40 AM
I get the same error, but it is intermittant.
I am using MSBuild version 4.0.30319 and MSTest version 10.0.30319.1
Triggering a new build will usually work.
Posted by ScottSt on 7/14/2010 at 5:45 AM
Here is the text from the bottom of the log file from the nightly build:

     [exec] 964/964 test(s) Passed
     [exec] Summary
     [exec] -------
     [exec] Test Run Completed.
     [exec] Passed 964
     [exec] -----------
     [exec] Total 964
     [exec] Results file: D:\NightlyBuild\CSharp\Veera\VeeraServer.Tests\VeeraServerTestResults.trx
     [exec] Test Settings: Default Test Settings


External Program Failed: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe (return code was 128)

Total time: 241.5 seconds.
Posted by ScottSt on 7/14/2010 at 5:38 AM
I ran into this issue during our company's nightly build last night.
We used to use NUnit, but switched to MSTest when we moved to VS2010 and Framework 4.0 when it was released.
We don't use TFS, our build scripts pre-exist TFS and are still written in NAnt, but someday when I get time ...
From NAnt we directly call (i.e. use <exec>) MSBuild to compile projects, and MSTest to run the tests.

Last night all the tests passed but we got a return code of 128 which caused the build to fail.
The build machine is/has:
* Windows Server 2003 Std x64 SP2
* VS 2010 Premium
* All .Net Frameworks with latest service packs
* Microsoft Windows SDK for Windows Server 2008 (6001.18000.367)

Based on logs it appears the it uses:
* MSBuild 4.0.30319.1
* MSTest 10.0.30319.1
Posted by Microsoft on 1/20/2010 at 7:13 AM
Thanks for reporting this issue. We had found it earlier in testing and have a fix in the release candidate.
Posted by Microsoft on 1/19/2010 at 1:25 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(