Closed without indication
Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.
7 posts
Page 1 of 1
- Support Specialist
- Posts: 590
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
-
Roc,
This could be one of many reasons. Dropped line, server IPL, Router or Switch issue.
We have no way of determining that unless we get information from the Target Server.
-R
This could be one of many reasons. Dropped line, server IPL, Router or Switch issue.
We have no way of determining that unless we get information from the Target Server.
-R
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
- Support Specialist
- Posts: 590
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
-
Get a detailed log from the Customer/Trading Partner indicating the reason for the dropped connection would be the best place to start.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
- Support Specialist
- Posts: 590
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
-
Roc,
What I'm saying is .. there's no way, just from that message, to determine what the exact reason was for disconnecting.
What I will say (and my assumption is that you are trying to FTP a document to some Resource) is that, setting up your Resource to perform Retries with a Delay will usually keep these types of issues from happening.
On your CONNECTION Tab inside your FTP Resource, change your Retries to 5 and your Retry Interval to 20 or 30 or even 60. This means, when you get that error, it will wait "x" time then try again, picking up where it left off. If (after 5 retries) you're still having an issue during transfer, then there will be logged information in your Job Log that will give you more reasons as to why .. if you have the "DEBUG" enabled on the FTP Task you are executing.
What I'm saying is .. there's no way, just from that message, to determine what the exact reason was for disconnecting.
What I will say (and my assumption is that you are trying to FTP a document to some Resource) is that, setting up your Resource to perform Retries with a Delay will usually keep these types of issues from happening.
On your CONNECTION Tab inside your FTP Resource, change your Retries to 5 and your Retry Interval to 20 or 30 or even 60. This means, when you get that error, it will wait "x" time then try again, picking up where it left off. If (after 5 retries) you're still having an issue during transfer, then there will be logged information in your Job Log that will give you more reasons as to why .. if you have the "DEBUG" enabled on the FTP Task you are executing.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
- Posts: 8
- Joined: Thu Feb 16, 2017 11:03 am
The most common issue with FTP/S resources to fail with the "Closed without indication" is the resource is not set to passive and implicit.
7 posts
Page 1 of 1