What to do if your protocol bridge agent reports that a file is not found

When the protocol bridge agent reports that the SFTP or FTP server that the protocol bridge connects to returns a File not found error message, this message can mean that one of a number of different error cases has occurred.

• The file does not exist. Check that the file we are attempting to transfer exists on the system hosting the SFTP or FTP server.
• The file path does not exist. Check that the file path exists on the system hosting the SFTP or FTP server. Check that we have entered the file path correctly into the transfer request. If necessary, correct the file path and submit the transfer request again.
• The file is locked by another application. Check whether the file is locked by another application. Wait until the file is no longer locked then submit the transfer request again.
• The file permissions do not allow the file to be read. Check whether the file has the correct file permissions. If necessary, change the file permissions and submit the transfer request again.
• The SFTP or FTP server uses a virtualized root path. If a relative file path is specified in a transfer request, the protocol bridge agent will attempt to convert the relative path into an absolute file path based on the home directory used to login to the protocol server. The Managed File Transfer protocol bridge agent can support only SFTP or FTP servers that allow files to be accessed by their absolute file path. Those protocol servers that allow access to files based only on the current directory are not supported by the protocol bridge agent.

Parent topic: MFT general troubleshooting

Related information

• The protocol bridge