This site requires JavaScript to be enabled

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

"Unable to upload Config" error in Distribution Agent

Hi team,


I followed every step in the manual to setup "Distributed execution". I am facing an issue that I don't know what step I have missed. When I click on the "Distribution Agent" icon, the status is red and the error message is "Unable to upload Config". I have attached a screenshot of the issue and the config details. Could you please give me an idea of how to fix this.





0 0

Gerald Kafko

Created: 2019-06-06 14:18:45

Hello !


Please make sure that your Agent Workspace is closed when you are changing something on your Distribution Agent !

Additionally, try to restart your Distribution Agent and verify, that you do not have multiple instances running on the same machine. 

I'd suggest to start the Distribution Agent as Administrator to eliminate any permission issue.

Sara Ghanavati

2019-06-06 23:53:21

This is the error text in the log file:

2019-06-07 09:52:28,680 [1] INFO  Tricentis.DistributionAgent.DistributionAgent - Error: UpdateState on Server failed. Reason: The message with Action 'Tricentis.DistributionServer.ServiceInterface.Services/ICommunicationService/UpdateConfig' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

0 0

Sara Ghanavati

Created: 2019-06-07 00:46:52 , Updates: 1, Last Update: 2019-06-07 01:05:24

Hi Gerald,

Thanks for your reply.


I had concidered all the above points, but the issue is still in place. If you look at the log file, it states that there is contract mismatch between sender and reciver. It looks like that Agent is not able to talk to the DEXserve through CommunicationService.


Any advise is greatly appreciated.

0 0

Gerald Kafko

Created: 2019-06-07 12:00:35

Hello Sara,


I can see that you've opened up a Ticket on our Support Portal for this Issue.

Lets continue our discussion over there. One Support Agent will be with you shortly in the Ticket

0 0

Ganesh Pandian Ayyappasamy

Created: 2019-11-28 05:50:24

Please mention the Incident Details, I am also facing the same issue.

Gerald Kafko

2019-11-29 09:14:13

Please create a Ticket on our Support Portal so we can look into this issue on your side as well.

Thanks !


Tosca is the perfect solution

Optimize - Manage - Automate

Download Trial