Problem

In some situations, a Send To Partner step might fail with the below errors logged in the TM log:

Inprocess agent execution has failed

Stack Trace:
    java.lang.SecurityException: Permission denied

AR0068: [s2p] [ar] Error occurred while sending file

Caused by: com.axway.st.server.route.api.cdi.provider.CouldNotSendFileToSiteException: Error occurred while sending file:
{.stfs/objects/8a/88b0976dee1d80176f285522c04d5/f2973717-71eb-473d-a84e-844de0af863d/b38fc10d-fef5-4819-a36b-35d76e70af29/8a688b0976dee1d80176f285526104d8/ssl.log}
using transfer site: {ssh}.
 at com.axway.st.server.route.core.cdi.provider.impl.SendToPartnerSiteImpl$SendToPartnerCallable.failPermanently(SendToPartnerSiteImpl.java:1109)
 at com.axway.st.server.route.core.cdi.provider.impl.SendToPartnerSiteImpl$SendToPartnerCallable.sendEventWithRetries(SendToPartnerSiteImpl.java:739)
 at com.axway.st.server.route.core.cdi.provider.impl.SendToPartnerSiteImpl$SendToPartnerCallable.call(SendToPartnerSiteImpl.java:682)
 at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
 ... 3 more
 Caused by: com.tumbleweed.st.server.events.AgentExitException: Exit Code -64

Resolution

If you have have configured Download Restriction rules, these might interfere with the Advanced Routing and prevent the Send To Partner step to finish.

The created Download Restrictions can be inspected from the Admin UI → Access → Restrictions → Download page. If there are active rules, you can configure ST to ignore them for the Server Initiated Transfers (SITs).

Go to the Admin UI → Operations → Server Configuration page.

Change the value for the parameter ServerInitiated.Access.Restricted to false.

Restart the TM service.

The ServerInitiated.Access.Restricted option controls whether the Upload and Download restriction would affect the Server Initiated Transfers. If the option value is set to true, they will affect both Client Initiated Transfers (CITs) and SITs. If the option value is false, they will affect only CITs.