Error 39/19: Peer aborted session

IN THIS ARTICLE:

Description

Errors 39 and 19 refer to the situation where a transfer session is stopped by the remote (peer) side. This is different than errors 28/68 in which an actual user aborts the session, such as by manually cancelling the transfer session while it is occurring. When the peer aborts the session, the session is closed on the remote side outside of the user’s control.

This error can appear for a variety of different problems, such as connection loss, improper licenses, or disk write failures, to name a few.

Examples of this error

Usually this error is seen in the transfer log file, and accompanied with other error codes to further specify the problem. The error message shown to the user is one that specifies why the peer aborted the session.

For example, a disk write failure on the remote side could cause it to terminate the transfer session. The user would see an error message “Disk write failure (server)” on the GUI or command line. The log would reveal the peer aborting problem:

2015-06-22 15:20:47 [1bbf-0xa052f1d4] ERR FASP sender had error, errcode 19 errstr [Disk write failed (server)]
2015-06-22 15:20:47 [1bbf-0xa052f1d4] ERR Peer FASP receiver had error, errcode 60 errstr [Disk write failed]
2015-06-22 15:20:47 [1bbf-0xb0103000] LOG FASP Session Stop uuid=25c77278-f842-41f4-982b-284f6bc817b1 op=send
status=failed errcode=39 errstr="Peer aborted session" [peer errcode=36 errstr="Disk write error"]

Another instance of this error could be when the remote side loses connection, such as if its internet connection goes down or its ports become blocked during a transfer. The log again reveals the peer aborting issue:

2015-09-18 13:18:07 [9dc-00000c54] ERR FASP sender had error, errcode 19 errstr [Session data transfer timeout 
(server)]
2015-09-18 13:18:07 [9dc-00000c54] ERR Peer FASP receiver had error, errcode 36 errstr [Session data transfer
timeout]
2015-09-18 13:18:07 [9dc-00001060] LOG FASP Session Stop uuid=e32d357d-450c-49cb-ae02-4756632b439e op=send
status=failed errcode=39 errstr="Peer aborted session" [peer errcode=40 errstr="Data transfer stalled, timed out"]

In some cases the remote side might not have a valid license for the type of transfer you’re trying to make, which will also cause the remote side to abort the session. For example, using the Connect browser plugin to transfer to a server requires the server to have a valid Connect server license installed:

2015-04-23 13:30:46 [a0d-0xa116d1d4] ERR FASP sender had error, errcode 40 errstr [Peer license does not support 
Connect]
2015-04-23 13:30:46 [a0d-0xa116d1d4] ERR Peer FASP receiver had error, errcode 19 errstr [Peer license does not
support Connect (client)]
2015-04-23 13:30:46 [a12-0xb0103000] LOG FASP Session Stop uuid=533b34df-d947-4e2b-a177-de7ad4a1cf5e op=recv
status=failed errcode=39 errstr="Peer aborted session" [peer errcode=38 errstr="Operation not permitted by license"]

 

Troubleshooting

The peer host you are attempting to transfer with must resolve this error, as the issue lies on their end.


Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk