Failed to distribute artifact to execution server
search cancel

Failed to distribute artifact to execution server


Article ID: 107543


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


We're getting the following error when initiating a deployment in our new RA environment: Failed to distribute artifact [artifact_store/releaseId_<releaseId>/...] to execution server [es_<ExecutionServername>].


CA Release Automation 5.x and 6.x


Configuration Related

The job's artifact package was being delivered to an agent reporting to one execution server from a retrieval agent that reports to a different execution server. Based on this finding we looked and confirmed that the two execution servers weren't configured to communicate with each other (which is necessary to get a file/artifact across).


Not Configuration Related

The error is often associated with NES Servers not being configured to properly communicate with each other. However, this error has also been seen (as seen in NES logs appearing with a message: Could not create proxy file sender for.*with id [.*_es_<remote_Nes_Hostname>] already exist) while running on versions earlier than When this message is present, it is not a configuration problem. 



Configuration Related

There are a few solutions to this kind of problem:

  1. Configure the execution servers to communicate with each other. Instructions for establishing this connection can be found here: Create Sibling Connections Between Execution Servers
  2. If configuring two remote execution servers to communicate with each other is not possible due to network restrictions then and you have three or more execution servers you can configure one execution to act as a routing execution server by configuring that one connect to all other execution servers. There are some different architectures discussed/described in the Architecture and Implementation Best Practice Guide.
  3. Duplicate your artifacts - one for each location that has connectivity between the retrieval agent, its execution server, and the agent machines included in the deployment. 


Not Configuration Related

If you're getting this error(s) then be sure you're using version or greater. If not, apply cumulative fix 10228 or greater if you're on Nolio version 6.6. Or, apply the latest cumulative fix if you're on 6.7. Then, if the error(s) continues and you're sure it is not a configuration issue (especially if you're getting the "sender for.*with id.*already exist" message) then please open an issue with Technical Support.