Specific transfer failures

To contact your local tech support administrator, click in the banner and select "Technical support".

Aspera Connect is unavailable

• Recommended action: Download and install IBM Aspera Connect. See Installing Aspera Connect.
• More information: See Select a transfer method.

Session data transfer timeout

• Recommended action: Verify network connectivity, then retry the transfer.
• More information: This error typically indicates a UDP timeout. The most likely cause is a network interruption for more than 60 seconds.

Session shutdown failed

• Recommended action: Verify network connectivity, then retry the transfer.
• More information: The session did not shut down properly, and the channel data could not be sent. The most likely cause is a network timeout.

Destination path directory does not exist

• Recommended action: Verify that the destination folder exists, then retry the transfer.
• More information: The target folder cannot be found. Verify that the folder name is accurate and that the folder exists at the expected path. If it does not, create the destination folder at the expected path, then try the transfer again.

Network down

• Recommended action: Verify network connectivity, then retry the transfer.
• More information: The network layer of the operating system may return this error when the Aspera tries to send to a destination that can't be reached because of a disabled or disconnected network interface or router.

Server aborted session: Could not validate bearer token

• Recommended action: Create a new transfer and try again. A simple retry of the same transfer usually does not succeed.
• More information: The security token may have expired. The AoC admin should check configurations in Organization > Security. See Configuring Organization Security Settings.

Server aborted session: Failed to extract JSON data from bearer token

• Recommended action: Log out of Aspera on Cloud, then log in again. Retry the transfer. If the issue persists, create a new transfer and try again after logging out and back in to AoC.
• More information: The security token may have expired. The AoC admin should check configurations in Organization > Security. See Configuring Organization Security Settings.