I am trying to run a manual test case in Microsoft Test Manager (2013) using a testing laboratory. When I run the test, it shows the following error:
Data and diagnostics can not be collected. An error occurred while starting the diagnostic data adapter. Revoke your session and start over again. Timed out while starting the data and diagnostics adapter If the Microsoft Test Manager is not included in the Windows Firewall in the exception list and is set to be enabled, the start time for data and diagnostics adapters may end. Verify that the exception list for the Windows Firewall includes Microsoft Test Manager (mtm.exe) For more information about this, see: For more information about the issues that the Data and Diagnostics Adapter can start from time to time Can cause, see:.
I am searching for an answer and for a few days now things are and can not solve this issue. With the help of 2 links you get this error, which did not help earlier and the other was not linked to the working page. Those who posted similar error in the forum have corrected their issues by correcting their firewalls, but firewalls on both their local PCs and firewalls on the virtual machine are both closed.
This is what I've checked:
- Firewalls are all closed
- My test agent has been set up on a virtual machine and Controller is correctly shown
- There is a prepared situation in the laboratory and I can see that the agent is online
- My test settings are currently set up to collect any data (Hope will help but hope this is not).
- The test environment is set to the right environment to run the environment.
- I have tried to extend the time period in mtm.exe.config and QTAgent configurations on the remote machine to close the test runner.
- I have a firewall log checked on the virtual machine when the test runner fails and there is no problem in it.
As you might say, I'm trying to fix it for a while!
Has anyone seen this error first and resolved it? To guide some things which I have not already listed, it will be really appreciated.
Thank you for your help!
I have solved this problem with a manual test test agent on the local machine as well as automation tests. Need to install on the virtual machine. This was the step I had missed. Once the test agent was installed on my local machine, this error disappeared. This is a misleading error message, but if you have this problem, make sure that the test agent is on all machines of the environment and is configured correctly. Part of this issue was my misconception because I thought I could use VM for my manual tests which is not the case.