Skip to main content

I have an FME workbench set up in Flow that grabs an XML file from an HTTP location - in that application the access is denied and no features are read. This same workspace when downloaded into a desktop workspace and when run with FME Form has no problem reading the XML into features and I can run the process successfully. What gives?

 

Edit - I noticed the client was using the FME Server 2022.2 but provided me with FME Desktop version 2022.1. I updated the FME Desktop version to 2022.2 and now the HTTP requests register 401 unauthorized in both applications so I think this is less about any issue between Form and Flow and more about some nuance between versions... I can still connect to HTTP just fine in 2022.1 on same machine, same creds in a variety of transformers\\readers - but in 2022.2 no dice. Something changed between point versions but do not see this in Issues documentation.

How are you authenticating the service? Are you using a web connection or some other authentication method?

 

You can try to turn on debug logging to see if there are any differences in there. Debug logging can be helpful with HTTP stuff as it gives a few more details.


Thanks Matt. I think i resolved this. The client had parameters in the schedule using http protocol that I overlooked. While the workspace utilized https protocol in the source path, the sequence of workspaces were using these outdated path strings in Server. Got rid of the schedule-level parameters and all is well.


Thanks Matt. I think i resolved this. The client had parameters in the schedule using http protocol that I overlooked. While the workspace utilized https protocol in the source path, the sequence of workspaces were using these outdated path strings in Server. Got rid of the schedule-level parameters and all is well.

Ahhh that old chestnut - great to hear that it's not a bug


Reply