Have you tried tweaking the parameters in the FTPCaller. That's the only thing that makes any sense to me. Can you post a screenshot of the parameters dialog perhaps?

If you are still having problems then please contact our support team (http://safe.com/support) and ask them to take a look. If you include the workspace it will be much easier for them to diagnose the problem.

Hi Luke - I'm aware of issues with the S3 transformers at the moment not honouring FME's proxy settings, but that issue is in hand and there is a possible workaround developed by Safe. When I recently came up against a similar issue to yours we put together the attached to try to identify if the FTPCaller was at fault or if it was network related. Give it a try and see if the FTPCaller in here fails and if so try the PythonCaller option by disabling the top section and enabling the bottom.

Failing that you may need to see if Safe have any tricks for testing proxy rules.

I hope it's some help at least. Cheers, Dave

Hi @markireland and @1spatialdave- Apologies only just saw these, will test and post results here. many thanks!

Luke

Hi Dave,

Many thanks for that I used your workspace which resulted in the FTPCaller not being able to connect, however The python Caller script resulted in a timeout error:

error: [Errno 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

Regards,

Luke

I'm afraid I'm not sure what is going on then, all sounds very odd. It sounds like we need a network specialist to step in here from Safe to see if they can help to debug exactly where the blockage is. I know Safe have some clever batch files that they distribute on the Knowledge Center for debugging license issues, given the prevalence of these types of issues, having something similar for network problems would be super handy. Sorry I can't be more help, but I'll see if I can forward this to someone who can.

Looks like our support team is on this and a the key issue identified is that our FtpCaller cannot make use of network proxy settings.

I'm facing a similar problem - did you get anywhere close to a solution?

Hi All,

This issue was fixed and verified in FME 2016.1 Build 1647. At time of writing FME 2016.1 is still in beta and due for release this week. The beta is available here:

http://www.safe.com/support/support-resources/fme-...

Hope this helps

Ken

So I tried the beta and this is the error I'm getting: ERROR |HTTP/FTP transfer error: 'Upload failed (at start/before it took off)'. any suggestions?