Errors 28 and 68 refer to the situation where a user stops or cancels a transfer while it is occurring. Transfers can be stopped from both the client and the server sides.
Examples of this error
This error can manifest itself in several ways, including in the GUI application for your server, the command line if you’re transferring with ascp, and in the transfer log file.
GUI and ascp
When transferring files to or from a server and a user on the server side cancels the transfer, you will see the following error message:
User aborted session (server)
When transferring files to or from a server and the client cancels the transfer, you will see the following error message:
User aborted session (client)
Below is an example of these errors as they can be recorded in the logs. The aspera-scp-transfer.log file records helpful information for each attempted transfer, labelled by the date and time attempted. For a reference of the location of this log file on your system, please see this article (Where are the Client or Server logs located?).
2015-09-21 11:59:23 [2590-0000160c] ERR FASP sender had error, errcode 68 errstr [User aborted session (server)]
2015-09-21 11:59:23 [2590-0000160c] ERR Peer FASP receiver had error, errcode 68 errstr [User aborted session]
2015-09-21 11:59:23 [2590-00002b70] LOG FASP Session Stop uuid=58241a46-511b-48e1-9baf-cb78401bfc88 op=send
status=failed errcode=28 errstr="Cancelled by user"
Contact your server administrator if someone on the server side is cancelling your transfers. If the client is the one cancelling the transfers, ensure they allow the transfers to complete before clearing the transfer from the GUI list of transfers.