Errors 4/50: No such file or directory and 43/63: Cannot collect details about file or directory

IN THIS ARTICLE:

Description

Errors 4, 43, 50 and 63 are FASP errors that refer to an attempted transfer of nonexistent files or folders, or an attempted transfer to a nonexistent destination folder.

Errors 4 and 50 directly correspond to "No such file or directory." Error 43 and 63 directly correspond to "Cannot collect details about file or directory" which also occur when the file or directory of a transfer is not found.

These errors are more likely to occur when transferring via the command line with ascp, since there is no browsing on the command line and you need to know the source and directory paths of your transfer.

Examples of this error

When a transfer is attempted on files and folders that don’t exist at the source or destination, you will see one or a combination of the following error messages:

Error 50 [Source: The system cannot find the file specified.]
Server aborted session: The system cannot find the path specified.
No such file or directory

Below are some examples 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-17 12:52:38 [2b4f-0xa11541d4] ERR No such file or directory
2015-09-17 12:52:38 [2b4f-0xa11541d4] ERR FASP receiver had error, errcode 50 errstr [No such file or directory]
2015-09-17 12:52:38 [2b4f-0xa11541d4] ERR Peer FASP sender had error, errcode 50 errstr [No such file or directory]
2015-09-17 12:52:38 [2b4f-0xb0103000] LOG FASP Session Stop uuid=45fc4dd8-eade-40bc-a528-d564dab13d23 op=recv
status=failed errcode=4 errstr="No such file or directory"
2015-09-17 15:26:15 [2dd3-0xa11541d4] ERR FASP sender had error, errcode 63 errstr [No such file or directory]
2015-09-17 15:26:15 [2dd3-0xa11541d4] ERR Peer FASP receiver had error, errcode 63 errstr [Server aborted session:
No such file or directory]
2015-09-17 15:26:15 [2dd3-0xa11541d4] ERR Failed to clean up file manifest
2015-09-17 15:26:15 [2dd3-0xb0103000] LOG FASP Session Stop uuid=214c8d2a-d19c-4c33-9ac6-dd2521df62a7 op=send
status=failed errcode=43 errstr="Cannot collect details about file or directory" 

Troubleshooting

1. Ensure you are supplying the correct paths to your source and destination if you are transferring with ascp. It can be especially tricky with supplying the remote server path information, since there is no browsing on the command line. You can try using the GUI to look through the remote directory for your files, or ask your server administrator.

On the GUI, you could try refreshing your current folder (navigate out and back in) to see if certain files or subfolders have been deleted off the server.

2. On Unix systems, check that you are not trying to transfer a special file, such as a symbolic link or a named pipe. You can check the types of files by running ls -l.

An example of output for this is the following:

-rw-r--r--   1 aspera  staff        0 Oct 12 15:50 notes.txt
drwxr-xr-x   4 aspera  staff      136 Nov 23 16:49 Project_Folder
prw-r--r--   1 aspera  staff        0 Sep 28 16:43 apipe
lrwxr-xr-x  1 aspera  staff     13 Nov 23 16:49 my_link -> my_file


You can tell the type of file by the first character of the leftmost column. - indicates a regular file, and d indicates a directory, both of which you can transfer normally. However, special files like named pipes (p) and symbolic links (l) cannot be transferred and will cause these error messages to appear.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk