| Bingdom |
| Newbie |
|
| Australia |
|
|
| None Specified |
|
| Monday, May 17, 2021 |
| Wednesday, February 2, 2022 12:48:07 AM |
4
[0.02% of all post / 0.00 posts per day] |
|
Ok, tried sending with windows firewall off- eliminates issues with a per-application firewall.
Still no luck and have the same error. I suspect at this point it's a bug with the application itself.
|
Hello
It seems like we're unable to establish an FTP session to a particular FTP server.
I tried connecting to the same server with a different client (WinSCP) and it works perfectly fine.
The FlowForce server seems to have no issues connecting to the other servers, which is strange.
The error I get is
Step FlowForce.ftpstor failed: Failed uploading a file to FTP server: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Is there an FTP debug option that I could use to help figure this one out?
Both FlowForce and WinSCP are using passive mode, so this currently isn't making much sense for me.
|
wriley wrote:You should be able to get the output of the Error Handling step by declaring a variable (for lack of a better word), in the 'Assign this step's result to field. This screenshot shows an example of it. Hope this helps
Hey, Thanks for the tip.
Doesn't help too much, unfortunately.
I've noticed I can move it out of the error handling, and the variable would carry over.
I don't want to introduce the error handling through the program I wrote. It would be nice to keep everything as close to the Altova products as possible (don't need some else to specialise in both Altova and programming if I were to leave).
Maybe I should report it as a bug.
I noticed I can retrieve the variable from when it's outside the scope of the error handling. Very weird.
|
Hey all,
Essentially, it appears that the result for the first execution step doesn't pass down to the handler as the image depicts below.
Is there an existing workaround?
|
|
