Common SFTP Issues
1. SSH_FX_NO_SUCH_FILE: Invalid Path
This is one of the most frequent errors.
Possible causes:
- Incorrect directory path configured
- Case sensitivity issues (
/psrvs/PSR) - Directory does not exist on the server
- Path mismatch (relative vs absolute path)
Resolution:
- Confirm exact path with bank
- Validate path using SFTP client (FileZilla/WinSCP)
- Ensure correct configuration in MBC
2. Connection Timeout
Symptoms:
- Unable to connect to SFTP server
- Request times out
Possible causes:
- Firewall restrictions
- IP not allowlisted
- Port 22 not open
Resolution:
- Ask bank to allowlist SAP MBC IPs
- Verify external access to SFTP server
- Confirm port accessibility
3. Files Not Visible in Directory
Symptoms:
- Bank confirms files are available
- MBC does not pick up files
Possible causes:
- Missing permissions (LIST/READ)
- Wrong directory path
- Files placed in different folder
Resolution:
- Verify user permissions
- Confirm correct directory
- Test using same credentials externally
4. Authentication Failure
Symptoms:
- Login failure to SFTP server
Possible causes:
- Incorrect credentials
- Key mismatch
- Expired credentials
Resolution:
- Revalidate username/password or key
- Ensure correct key is configured on both sides
Key Points to Remember
- SAP MBC does not generate or modify files
- MBC only accesses directories provided by the bank
- Most SFTP issues are due to:
- Path mismatch
- Permission issues
- Network restrictions
Conclusion
SFTP issues in SAP MBC are usually not complex but require careful validation of connectivity, directory structure, and permissions.
Understanding these common patterns can significantly reduce troubleshooting time and avoid unnecessary configuration changes on the SAP side.
