SFTP INTEGRATION ERROR

abdullahkhan852
Tera Contributor

com.glide.db.impex.datasource.DataSourceException: java.io.IOException: Problem opening a handle to remote file: /home/OUT/BFL_ETB_Movement_File.csv
Im facing issue while integrating SFTP through Data Sources .
Need help with the same.
@Ankur Bawiskar @Ravi Gaurav @Robert Perrone @Max Nowak 

 

 

abdullahkhan852_0-1748340856447.png

 

1 REPLY 1

Abbas_5
Tera Sage
Tera Sage

Hello @abdullahkhan852,

 

SFTP integration errors in ServiceNow can stem from various issues, including incorrect credentials, misconfigured paths, network connectivity problems, or firewall restrictionsTroubleshooting involves verifying credentials, checking network settings, and ensuring the SFTP server is accessible. 
 
Here are the detailed steps:
 
1. Credentials and Authentication:
  • Verify SSH Credentials:
    Ensure the username and password (or SSH key) entered in the ServiceNow data source configuration are accurate and have the necessary permissions to access the SFTP server. 
     
  • SSH Key Authentication:
    If using SSH key-based authentication, ensure the private key file path is correctly specified in the data source configuration. 
     
  • Fallback Authentication:
    In some ServiceNow versions, you might need to enable "mid.ssh.auth.fallback_to_password" to allow the MID Server to fall back to password authentication if SSH key authentication fails. 
     
2. Server and Network Configuration:
  • SFTP Server Details:
    Double-check the server address, port number, and path in the ServiceNow data source configuration with the SFTP server administrator. 
     
  • Network Connectivity:
    Ensure the ServiceNow instance (and MID Server, if applicable) can reach the SFTP server. Use a standalone SFTP client to test connectivity from a machine on the same network as the ServiceNow instance. 
     
  • Firewall and Network Settings:
    Verify that firewalls are configured to allow traffic between the ServiceNow instance and the SFTP server on the necessary ports (usually 22 for SFTP). 
     
  • Exposed Server:
    Ensure the SFTP server is accessible over the internet (or on the specific network) by verifying that the IP address is public or accessible within the network. 
     
3. Path and File Issues:
  • File Existence:
    Verify that the file you are attempting to transfer actually exists at the specified path on the SFTP server.
  • Path Accuracy:
    Ensure the path specified in the ServiceNow data source configuration or SFTP step is correct.
  • File Naming:
    If file names are dynamically generated, ensure they match the actual file names on the SFTP server. 
     
4. MID Server Configuration:
  • MID Server Capabilities:
    Ensure the MID Server used for the SFTP transfer has the correct capabilities and configurations for file transfers. 
     
  • MID Server Logs:
    Check the MID Server logs for any error messages or clues related to the SFTP transfer. 
     
     
    If it is helpful, please hit the thumbs up icon and accept the correct solution by referring to this solution in future, it will be helpful to them.
     
    Thanks & Regards,
    Abbas Shaik