VSP10041: EXCEPTION_XSHAREDMEMORYCOULDNOTMAP

Question

We semi-frequently see this message in local builds and the automated build:

TESTTOOLSTASK : Code coverage collection warning : Collection engine threw exception:
  The previous error was converted to a warning because the task was called with ContinueOnError=true.
TESTTOOLSTASK : warning VSP10041: EXCEPTION_XSHAREDMEMORYCOULDNOTMAP
  The previous error was converted to a warning because the task was called with ContinueOnError=true.
  .
  The test run execution on that machine cannot continue.

It occurs after the unit tests have been run and while the code coverage is being processed. Any ideas as to what is causing this and what needs to be done to keep it from happening?

 

Thanks!

Answer 1

Hi,

Do you have VS 2010 Ultimate installed on the build agent. Ultimate version is the requirement for code coverage.

Thanks,

Anuj

Answer 2

Hello Quenby,

Thanks for your post.

In order to helping you solve your issue, it is better that if you can provide us the detailed error messages. So please set the ContinueOnError property to false, and if a task fails the remaining tasks in the Target element are not executed and the entire Target element is considered to have failed. Then please post us the error message you got.

Please see the following article for further information about ContinueOnError.

http://msdn.microsoft.com/en-us/library/77f2hx1s.aspx

Thanks,

---

Vicky Song [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 3

We are using VS 2008 and MSBuild 3.5. I changed the ContinueOnError attribute for the TestToolsTask to false, but it didn't result in better error messages.

 

TESTTOOLSTASK : Code coverage collection error : Collection engine threw exception:
TESTTOOLSTASK : error VSP10041: EXCEPTION_XSHAREDMEMORYCOULDNOTMAP
  .
  The test run execution on that machine cannot continue.
Done Building Project "c:\TFS\***\TeamBuildTypes\CI_ComponentBuilds\TfsBuild.proj" (TestConfiguration target(s)) -- FAILED
Done Building Project "c:\TFS\***\TeamBuildTypes\CI_ComponentBuilds\TfsBuild.proj" (RunTest target(s)) -- FAILED.
Done Building Project "c:\TFS\***\TeamBuildTypes\CI_ComponentBuilds\TfsBuild.proj" (default targets) -- FAILED.

Build FAILED

 

 

Answer 4

Hello Quenby,

Thank you for your response.

I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

Thank you for your understanding and support.

---

Vicky Song [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 5

Hi Quenby,

Let's turn on vstesthost logging as described here  

http://blogs.msdn.com/b/yutong/archive/2006/10/03/how-to-enable-vsts-logging_3f00_.aspx

Run another build to see if we get additional information.

We might also want to check if this reproduces in a command line scenario.  The easiest way is to search your buildlog.txt for the mstest command line launched by the testtoolstask.  Logon to the build machine with the same account the tfsbuildservice is using, run the mstest command line.  Do we get the same error?

If the vstesthost log doesn't give us the clues we need, we might need to open a support case so we can capture a dump to do some analysis of the state of vstesthost e.g. are we getting into an outofmemory situation, etc?

---

--Trevor H.
Send files to Hotmail.com: "MS_TREVORH"