Dear community,
one of our clients has reported the attached TestStand error. We were wondering, what exactly could cause such a TestStand error. We examined the Windows Event Viewer -> Windows Logs -> Application and we can only see an exception that is caused in DotNetAdapterManagedSupport.TSAppDomainManager.a(Object).
Since we are providing our own .NET components that are being invoked by TestStand, we created a worker thread in one of our components that intentionally throws an unhandled exception. In that case, the TestStand error popup and also the Event Viewer shows that the new thread is the culprit (see the attached "Intentional TestStand fatal error.png").
The question that remains is: How can we debug the initial error, that appearantly is caused by DotNetAdapterManagedSupport.TSAppDomainManager.a(Object) ?
Help is highly appreciated
