FTP issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 09:06 AM
Hi,
We have a data source created in ServiceNow which generates a CSV file with sctask & places it in FTP server. This runs via scheduled job. This configuration has been there since long & few days back started getting below error. From firewall end the ServiceNow related IP have been whitelisted & from the server where our ServiceNow mid server is setup we are able to connect to FTP server successfully
Need help in understanding what exactly is the below error & also what can be done to resolve it
java.io.IOException: /glide/nodes/INSTANCENAME013_16010/bin/../tmp/gurl3f5b1db947a13150013bf062e36d43f9.tmp size:0
Connection properties:
connection.timeout=10000
user.login=ServiceNow
connection.type=FTP_CONNECTION
connection.passive=false
connection.port=21
user.password=**********
connection.host=ftp2.pret.com
----------------------
331 Password required for servicenow
230 Logged on
211-Features:
MDTM
REST STREAM
SIZE
MLST type*;size*;modify*;
MLSD
UTF8
CLNT
MFMT
211 End
215 UNIX emulated by FileZilla
200 Type set to I
200 Port command successful
150 Opening data channel for file transfer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 11:04 PM
Hello @Rhujuta1 ,
The most common FTP errors are related to incorrect login details supplied or an issue with the hosting server or the internet service provider. In most cases, you will see Could not connect to the server, but exact errors will vary depending on the issue.
Please refer to the below link:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB086
If it is helpful, please mark it as helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 11:13 PM
Hi Abbas,
I already referred to the article shared by you as earlier I was getting the same error as mentioned in the article. The necessary IP were whitelisted & rest of the steps as mentioned in the resolution were done then I started getting the error which has been mentioned in my question above.