QT Agent32已停止工作 [英] QT Agent32 has stopped working

问题描述

< o：p>< / o：p>

我使用Windows server2012使用VS2013 / MTM远程运行测试时遇到困难得到以下错误

我似乎无法通过图片但是其他人在这篇文章中遇到了同样的问题

如果对您有所帮助，请随意告诉我。谢谢。

祝你好运，

Fletch

Hi,<o:p></o:p>

I have been having difficulty running tests remotely using VS2013/MTM using windows server2012 I get the following error

I cant seem to past the image in but someone else is having the same issue in this post

https://social.msdn.microsoft.com/Forums/vstudio/en-US/cd7a8324-8d8f-4ed8-8cf5-3f781a829862/qtagent-32exe-has-stopped-working?forum=vstest

As the tests run locally fine I'm guessing its an issue with the test agent, I have run a repair of the environment/agent and still get the same result. I have accesses the test log but can only include and extract of it due to its size (the exceptions thrown all appear to be very similar) let me know if you need the whole thing or any other info

Many Thanks

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.IControllerCallback.ConnectAgent(String agentName, String machineName, String domainName, Boolean canPerformUITesting, String configuredUserName, String agentVersion, IAgentService agentObject)
   at Microsoft.VisualStudio.TestTools.Agent.AgentService.ConnectToController(Boolean shouldThrow)
I, 4972, 6, 2017/05/10, 10:08:52.336, V7AS02\QTAgentService.exe, AgentService: Connection to controller is down. Reconnecting...
V, 4972, 6, 2017/05/10, 10:08:52.336, V7AS02\QTAgentService.exe, AgentStatusAggregator.ControllerDisconnected: Connection to controller v7bc01.dev.simba.local:6901 has been lost.
I, 4972, 6, 2017/05/10, 10:08:52.336, V7AS02\QTAgentService.exe, AgentService: connecting to controller using uri: tcp://v7bc01.dev.simba.local:6901/ControllerAccessManager.rem
I, 4972, 6, 2017/05/10, 10:08:52.336, V7AS02\QTAgentService.exe, ExecutionUtilits.UpdateRemotingCredentials Invoked
I, 4972, 6, 2017/05/10, 10:08:52.336, V7AS02\QTAgentService.exe, ExecutionUtilits.UpdateRemotingCredentials : Domain simbadev User tfslabuser
I, 4972, 6, 2017/05/10, 10:08:52.352, V7AS02\QTAgentService.exe, GetControllerObject : Controller Version : 12.0
I, 4972, 6, 2017/05/10, 10:08:52.368, V7AS02\QTAgentService.exe, ExecutionUtilits.UpdateRemotingCredentials Invoked
I, 4972, 6, 2017/05/10, 10:08:52.368, V7AS02\QTAgentService.exe, ExecutionUtilits.UpdateRemotingCredentials : Domain simbadev User tfslabuser
I, 4972, 6, 2017/05/10, 10:08:52.368, V7AS02\QTAgentService.exe, AgentService: obj is Microsoft.VisualStudio.TestTools.Controller.ControllerObject
I, 4972, 6, 2017/05/10, 10:08:52.368, V7AS02\QTAgentService.exe, AgentService: Connecting to controller. Using AgentName: vstfs:///LabManagement/TestMachine/58 : Domain : dev.simba.local
V, 4972, 25, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, AgentService: calling AgentObject.Hello
V, 4972, 25, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, AgentProcessManager.WaitForDataCollectionAgentProcessToStart: waiting for agents to start.
V, 4972, 25, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, AgentProcessManager.WaitForDataCollectionAgentProcessToStart: Agents started.
W, 4972, 25, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, EqtException: AgentProcessManager : Hello : There are no test agents running
E, 4972, 25, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, AgentService: Exception while calling Hello on agent object: Microsoft.VisualStudio.TestTools.Exceptions.EqtException: AgentProcessManager : Hello : There are no test agents running
   at Microsoft.VisualStudio.TestTools.Agent.AgentProcessManager.Microsoft.VisualStudio.TestTools.Agent.IAgentObject.Hello()
   at Microsoft.VisualStudio.TestTools.Agent.AgentService.Microsoft.VisualStudio.TestTools.Agent.IAgentObject.Hello()
I, 4972, 6, 2017/05/10, 10:08:52.414, V7AS02\QTAgentService.exe, AgentService: Failed to connect to controller. Microsoft.VisualStudio.TestTools.Exceptions.EqtException: The agent can connect to the controller but the controller cannot connect to the agent because of following reason: AgentProcessManager : Hello : There are no test agents running

Server stack trace:
   at Microsoft.VisualStudio.TestTools.Controller.AgentMachine.VerifyAgentConnection(Int32 timeout)
   at Microsoft.VisualStudio.TestTools.Controller.AgentManager.BeforeConnectAgent(String agentName, String machineName, Boolean canPerformUITesting, IAgentService agentService, WindowsIdentity remoteIdentity)
   at Microsoft.VisualStudio.TestTools.Controller.ControllerConfiguration.ConnectAgent(String agentName, String machineName, Boolean canPerformUITesting, String configuredUserName, String agentVersion, IAgentService agentService, WindowsIdentity remoteIdentity)
   at Microsoft.VisualStudio.TestTools.Controller.ControllerObject.ConnectAgent(String agentName, String machineName, String domainName, Boolean canPerformUITesting, String configuredUserName, String agentVersion, IAgentService agentService)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

<o:p></o:p>

解决方案

Hi friend,

Welcome to MSDN forum.

>>I have been having difficulty running tests remotely using VS2013/MTM using windows server2012 I get the following error

Do you run test via VS 2013 test agent and test controller? And there is a MTM in Windows server2012?  You use test controller with MTM? Not very sure how you run your test remotely? Could you please share us the details?

>> AgentStatusAggregator.ControllerDisconnected: Connection to controller v7bc01.dev.simba.local:6901 has been lost.

According this log, it could be caused by not correct connection the test controller. Please refer to following steps troubleshooting:

1. Using the lab service account to connection.
2. Open your Test Controller, under the controller name you should write the <machineName>:port (if you want to use MTM, please enter the TFS server address that MTM specified). The default port is 6901.

  3. Please also restart your Controller and Agent machine after you setup them.

Reference: https://msdn.microsoft.com/en-us/library/hh546460.aspx

Please free feel let me know if it helps you, thanks.

Best regards,

Fletch

这篇关于QT Agent32已停止工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！