http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/knowledge-base/scheduling/resolve-common-scheduling-issues.aspx
It is highly outdated though. I checked out these files/folders on the scheduling server:
* C:\Program Files (x86)\Telerik\Test Studio\Bin\SchedulingServerConfig.log => 2 lines:
====== ======
====== Log Started ====== 23-10-2013 13:59:19
* C:\Program Files (x86)\Telerik\Test Studio\Logs => completely empty directory
How can we get decent logs or enable logging?
Thanks!
3 Answers, 1 is accepted
You will need to manually edit the Registry on the remote machine.
Please check out the second part of this article to get detailed information.
Hope this helps.
Boyan Boev
Telerik
Rank 1
The most common cause of the symptom you describe is a blocked port (port 8032 being the most common one that is blocked). The ports we use is documented here:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/scheduling-test-runs.aspx
In short we use these ports:
- Scheduling Server: 8009
- Storage Server: 8492
- Execution Machine(s): 55555, 8030-8039 (and sometimes a range of ports from 8040 upward)
If this information doesn't help you'll need to enable logging on the Scheduling Server machine by setting 2 registry keys as documented in the top half of this page:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/load-testing/load-troubleshooting.aspx
Reproduce the problem then send us the generated log file for analysis.
Regards,
Telerik