Yikes - These settings are edited in the Windows Registry when you change the setting here in workbench options.
Have you tried restarting the computer at all? I know you shouldn't have to and it's not a solution, it would just be an interesting test.
You could also try running FME Workbench as an administrator and changing the setting there to see if that has an effect, although I suspect that it wouldn't help.
If you have access to Window Registry you can go to:
Computer\\HKEY_CURRENT_USER\\Software\\Safe Software Inc.\\FME Workbench\\Settings
and then find the entries which start with Proxy and delete them. There should be 5 entries. This should clear any information FME has about proxies. Please note that I have tested this in FME 2020 myself just now without issue. If you edit the proxy settings again in FME Setting then FME will recreate the entries.
Yikes - These settings are edited in the Windows Registry when you change the setting here in workbench options.
Have you tried restarting the computer at all? I know you shouldn't have to and it's not a solution, it would just be an interesting test.
You could also try running FME Workbench as an administrator and changing the setting there to see if that has an effect, although I suspect that it wouldn't help.
If you have access to Window Registry you can go to:
Computer\\HKEY_CURRENT_USER\\Software\\Safe Software Inc.\\FME Workbench\\Settings
and then find the entries which start with Proxy and delete them. There should be 5 entries. This should clear any information FME has about proxies. Please note that I have tested this in FME 2020 myself just now without issue. If you edit the proxy settings again in FME Setting then FME will recreate the entries.
Well, that's the next thing I'm going to do.
Meanwhile, I just noticed that it's only the ArcGIS Online Feature Service Writer that's using it: I happened to run part of the workbench - the part that reads the features from an online source - and it worked. But as soon as I ran the whole workbench, with the AGOL writer, that's when the proxy was invoked and the connection failed.
I'll reboot my computer soon and keep you informed.
Thanks.
Well, that's the next thing I'm going to do.
Meanwhile, I just noticed that it's only the ArcGIS Online Feature Service Writer that's using it: I happened to run part of the workbench - the part that reads the features from an online source - and it worked. But as soon as I ran the whole workbench, with the AGOL writer, that's when the proxy was invoked and the connection failed.
I'll reboot my computer soon and keep you informed.
Thanks.
Yeah - As I understand it (don't quote me) is there are (at least) two different methods which FME gets proxy stuff. Python based and presumably C++ based. I think the C++ stuff has the best support, the HTTPCaller uses this and is usually pretty solid.
Python based formats include ArcGIS online and WFS stuff as well as background maps and a few other formats. If I'm right you might find that background maps in the data inspector also will try the proxy.
There used to be issues with NTLM authentication with the python based formats but that might be fixed now.
Well, that's the next thing I'm going to do.
Meanwhile, I just noticed that it's only the ArcGIS Online Feature Service Writer that's using it: I happened to run part of the workbench - the part that reads the features from an online source - and it worked. But as soon as I ran the whole workbench, with the AGOL writer, that's when the proxy was invoked and the connection failed.
I'll reboot my computer soon and keep you informed.
Thanks.
Rebooted the computer, problem solved. Go figure.
Thanks! 👍