This site requires JavaScript to be enabled


Dear Tricentis qTest users,

If you would like to submit a Tricentis qTest ticket,

please use this support request form.

Tosca Version
IncidentLookup using list
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

Troubleshooting: Distributed Execution (DEX)

This article is to aid in gathering information and analysing issues in a proactive and efficient manner


Log Locations

RDP: C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution\Rdp
DEX server: C:\ProgramData\TRICENTIS\ToscaServer\DistributionServer\logs
DEX Agent: C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution\Agent


Config file locations

DEX Agent:

  • C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution\Agent\ToscaDistributionAgent.exe.config\
    • This config file is used upon initial load of Agent files
  • C:\Users\<user>AppData\Local\Tricentis_GmbH\ToscaDistributionAgent\<Tosca Version>\user.config
    • This specified settings in this config file override the above config
  • C:\ProgramData\TRICENTIS\TOSCA Testsuite\7.0.0\DistributedExecutionAgent
  • C:\Users\<user>\AppData\Roaming\TRICENTIS\TOSCA TestSuite\7.0.0\Settings\ToscaDistributionAgent\user.<Tosca version>.config




Apply DEBUG levels to logs


To remedy this apply debug-level to the configuration files of components involved:


  • DEX Server: C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXServer\Web.config
  • DEX Agent: C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution\Agent\ToscaDistributionAgent.exe.config
  • RDP ServerC:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution\Rdp\ToscaRdpServer.exe.config


In each of the above files, access the <level> tag under the <log4net> tag and change INFO to DEBUG or ALL

Note: The DEX Agent provides the the log level setting in the Agent Configuration GUI.




The errors and differences environment may not offer a clear root cause for an issue.


There are varying stages of complexity involving DEX. It would be best to look for an issue by reducing the complexity involved, identifying stability there, and moving to the next stage. 


When remoting, or messaging, with a customer, use the below Levels and their respective verification procedures to eliminate potential causes:


Complexity Level 1: DEX Agent and Server


Ensure that Agent and Server can talk directly to each other. Create a new simple test step (e.g. Buffer Test Step) and run the Test Event - this should verify successful interaction.


Complextiy Level 2: DEX Agent, DEX Server, and RDP Server


Ensure that the RDP server is on. This time, create a new simple test step that has a {Click} action, and run the test event. This is to ensure that RDP itself is working when a machine is locked for unattended execution

This should verify successful interaction among the 3 components


Note: The Agent must be restarted if you make changes to the configuration file.

0 0

Jay Reyes

Created: 2018-05-24 20:35:01

It's important to note that DEX Server logs are stored in what seems to be an atypical location... I updated the KB article with its location.


Tosca is the perfect solution

Optimize - Manage - Automate

Download Trial