Search

VSTTExecution failure. by aractnido

Closed
as Not Reproducible Help for as Not Reproducible

30
0
Sign in
to vote
Type: Bug
ID: 543848
Opened: 3/22/2010 8:28:33 PM
Access Restriction: Public
1
Workaround(s)
24
User(s) can reproduce this bug
----
Microsoft Visual Studio 2010
Version 10.0.30306.1 **RTMRel**
Microsoft .NET Framework
Version 4.0.30306 RTMRel

Installed Version: Ultimate
----

I have tons of the following errors in the Event Log:


The description for Event ID 0 from source VSTTExecution cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

(devenv.exe, PID 5196, Thread 1) TmiDataManager.TryConvertPropertyValueToDisplayText: Failed to convert property value using the property descriptor's type converter. System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.String.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider)
at System.String.System.IConvertible.ToType(Type type, IFormatProvider provider)
at System.ComponentModel.EnumConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
at System.ComponentModel.TypeConverter.ConvertToString(Object value)
at Microsoft.VisualStudio.TestTools.TestCaseManagement.TmiDataManager`3.TryConvertPropertyValueToDisplayText(DataRow dataRow, PropertyDescriptor propertyDescriptor, Object propertyValue, String& displayText)

the message resource is present but the message is not found in the string/message table
Details (expand)

Product Language

English

Version

Visual Studio 2010 Release Candidate

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

See callstack.

Actual Results

See callstack.

Expected Results

See callstack.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by jhewett on 2/7/2011 at 2:37 PM
Same here. A plethora of VSTTExecution and VSTTAgentProcess errors. Right now I can't run any regression or unit tests because I'm not sure if my latest changes are bad or if it's just the (putrid) QTAgent32.exe barfing on the rug.
Posted by Nils Lande on 2/5/2011 at 12:00 AM
Microsoft Visual Studio 2010
Version 10.0.30319.1 RTMRel
Microsoft .NET Framework
Version 4.0.30319 RTMRel

81 error messages from VSTTExecution in 5 days. The content is one of the following:

"(devenv.exe, PID 1196, Thread 42) OutOfProcessStrategy.ProcessMonitorThread: Agent process was shut down unexpectedly; will attempt to restart."

"(devenv.exe, PID 3556, Thread 1) StringToVariantHelper.WriteSafeArrayToVariant: Failed to clear the variant. Exception message: Bad variable type. (Exception from HRESULT: 0x80020008 (DISP_E_BADVARTYPE))."

"(devenv.exe, PID 3556, Thread 5) ControllerExecution: Received exception calling StopTestRun on collector machine KBG4837: System.Runtime.Remoting.RemotingException: Failed to read from an IPC Port: The pipe has been ended."

"(QTAgent32.exe, PID 6704, Thread 16) Unit Test Adapter threw exception: System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.RunClassInitializeMethod()
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.Initialize(UnitTestResult result, UnitTestRunner runner, ConsoleOutputRedirector redirector)
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestRunner.Run(UnitTestElement test, ITestContext testContext, Boolean isLoadTest, Boolean useMultipleCpus)."

"(QTAgent32.exe, PID 6704, Thread 16) Unit Test Executor threw an exception. Most likely the test run was aborted by the user or the framework:System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.RunClassInitializeMethod()
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.Initialize(UnitTestResult result, UnitTestRunner runner, ConsoleOutputRedirector redirector)."

Comment: I did actually experience some really wird behaviour related to Console.WriteLine and the Test Result Details window one day.

"(devenv.exe, PID 6676, Thread 36) AgentProcessManager.PerformActionIgnoringExceptions: Lost connection to the test agent."

"(devenv.exe, PID 6676, Thread 36) AgentProcessManager.PerformActionIgnoringExceptions: Error occurred while calling 'Cleanup' on the test agent. System.Runtime.Remoting.RemotingException: Failed to read from an IPC Port: The pipe has been ended.
"

"(QTAgent32.exe, PID 4012, Thread 29) Unit Test Adapter threw exception: System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.RunTestMethod()
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.ExecuteTest()
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestExecuter.Execute(UnitTestResult result)
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestRunner.ExecuteSingleTest(UnitTestExecuter executer, UnitTestElement test, ITestContext testContext, UnitTestAdapterContext userContext, Boolean isLoadTest)
at Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestRunner.Run(UnitTestElement test, ITestContext testContext, Boolean isLoadTest, Boolean useMultipleCpus)."








Posted by posy_74 on 1/20/2011 at 6:02 AM
I too am experiencing this problem exactly the same as zen.... There must be some workaround?!
Posted by Austin Dimmer on 12/16/2010 at 5:04 PM
Pretty much the same thing here for me (498 errors in the event log in the last 7 days) so I thought I'd post my error message. I hope it helps.

The description for Event ID 0 from source VSTTExecution cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

(devenv.exe, PID 12844, Thread 1) HierarchyOutputCollection.GetOutputGroup: either buildManager.FindActiveProjectCfg or projectCfg[0].OpenOutputGroup failed: System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at Microsoft.VisualStudio.TestTools.Vsip.HierarchyOutputCollection.GetOutputGroup(IServiceProvider serviceProvider, IVsHierarchy hierarchy)


the message resource is present but the message is not found in the string/message table
Posted by Mark Sh on 9/23/2010 at 12:38 PM
I concur, this is still an issue and should be re-evaluated.
Posted by yufisch on 6/29/2010 at 11:23 AM
Please re-open. I'm seeing the same error in the event log after updgrading a test project from VS 2008 to VS 2010 and running my tests:

Microsoft Visual Studio 2010
Version 10.0.30319.1 RTMRel
Microsoft .NET Framework
Version 4.0.30319 RTMRel
Installed Version: Ultimate


If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

(devenv.exe, PID 6668, Thread 1) TmiDataManager.TryConvertPropertyValueToDisplayText: Failed to convert property value using the property descriptor's type converter. System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.String.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider)
at System.String.System.IConvertible.ToType(Type type, IFormatProvider provider)
at System.ComponentModel.EnumConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
at System.ComponentModel.TypeConverter.ConvertToString(Object value)
at Microsoft.VisualStudio.TestTools.TestCaseManagement.TmiDataManager`3.TryConvertPropertyValueToDisplayText(DataRow dataRow, PropertyDescriptor propertyDescriptor, Object propertyValue, String& displayText)

the message resource is present but the message is not found in the string/message table
Posted by robpurnell on 6/22/2010 at 1:17 AM
I too am getting a sea of red in my event log from VS2010 (version 10.0.30319.1 RTMRel).

Why has this been closed?
Posted by RichB2005 on 5/25/2010 at 5:10 PM
I can reproduce this at will. Any workarounds? Suggestions? This is a hard bug... not intermittent.

1. Create a WCF data service
2. Put an context name from a EF model in the DataService template field
3. Right click .svc file and "Run in Browser"

Watch the failure.... every time.
Posted by Microsoft on 4/8/2010 at 4:03 PM
Hello,

We were unable to repro the exception that you saw in the latest bits. We have added lines to our code just to make sure this does not happen again.

Thanks for your feedback,
Visual Studio Product Team
Posted by Microsoft on 3/23/2010 at 2:20 AM
We have asked the product unit who works on that specific feature area to review this issue. As mentioned in the invitation email and on the connect site, due to the volume and timeframe of the LCTP. Teams will be triaging these issues as though they are internal bugs/suggestions and will not be responding to individual issues.
Sign in to post a workaround.
Posted by Vinoth Muthan on 9/5/2011 at 12:01 AM
I encounter same issue when unit test cases are generated from context menu for those method marked as 'internal' or 'private'. code generation for public method is working fine.