Share via

Troubleshooting errors in Test Runner

  • Article

Welcome to the troubleshooting page for Test Runner in Visual Studio 2010. This is a repository of errors we have seen in different scenarios and the ways to fix it. You can either search for your error or browse by category. If your error is not on this list, please take a minute and report it to us by filing a bug.

You encountered an error in:

1. Data Collectors

2.

1. Data Collectors

1.1 Issues with initializing diagnostic data adapters if MTM is running on a box which is connected through VPN

1.2

Details and troubleshooting steps

1. Data Collectors

Title

1.1. Issues with initializing diagnostic data adapters if MTM is running on a box which is connected through VPN

Version

Beta 2, RC

Operating Systems

All

Symptoms and impact

1) You’ll get this message box while starting test case in Test Runner:

Data and diagnostics cannot be collectedAn error occurred while initializing diagnostic data adapters.Timed out while initializing data and diagnostics adapters.To increase the timeout values for all diagnostic data adapters, see the following link: https://go.microsoft.com/fwlink/?LinkId=169311 .

2) Event viewer in Test Controller box will have this entry:

(QTController.exe, PID 4660, Thread 26) ControllerExecution: Exception: System.Net.Sockets.SocketException (0x80004005): No such host is known

Server stack trace: at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostAddresses(String hostNameOrAddress) at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket() at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket() at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew) at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream) at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.VisualStudio.TestTools.Controller.IControllerEvents.ControllerEvent(TestMessage report) at Microsoft.VisualStudio.TestTools.Controller.ControllerExecution.<>c__DisplayClass1d.<CallListeners>b__19(IControllerEvents eventListener) at Microsoft.VisualStudio.TestTools.Execution.RemoteObjectContainer`1.InvokeAsRemoteUser(Action`1 invoke) at Microsoft.VisualStudio.TestTools.Controller.ControllerExecution.CallListeners(TestMessage

Possible cause(s)

VPN properties are not set properly

Resolution

1) Set the VPN properties to register that machine in DNS on connect as shown below:

2) If you don’t want to do 1st solution mentioned above then you can work around the issue by running MTM from a box which is not on VPN and present inside office network