Skip to main content
Solved

HTTPCaller gets HTTP/1.1 403 RestrictedServerAccess on FME Server but not from FME Desktop

jakethepainter
Contributor
Forum|alt.badge.img+6

I have an extremely simple workspace with a creator and an HTTPCaller that just downloads a file from a fixed location to a file share. Runs on my machine in fme desktop but when I publish to server, I get an error. However, the file successfully downloads when run from server. If I set the workspace parameter for Rejected Feature Handling to "Continue Translation" the workspace is successful and I get my file.

So is this indicative of a problem? I don't want to get blocked from the wfas site if they don't like my request.

 

FME Server 2019.2.1

 

Build 19813 - win64

FME Desktop 2019.2.1.0

Build 19813 - win32

 

52HTTPCaller (HTTPFactory): HTTP/FTP Transfer: Downloading resource 'https://wfas.net/google-earth/wfas_nfdr.kmz' to local file '\\\\blah\\blah\\wfas_nfdr.zip'53HTTPCaller (HTTPFactory): HTTP transfer summary - status code: 403, download size: '3496 bytes', DNS lookup time: '0.001847 seconds', total transfer time: '0.214343 seconds', url: 'https://wfas.net/google-earth/wfas_nfdr.kmz'54HTTPCaller (HTTPFactory): Received HTTP response header: 'HTTP/1.1 403 RestrictedServerAccess' from 'https://wfas.net/google-earth/wfas_nfdr.kmz'

Best answer by erik_jan

This might be a permissions issue.

The FME Server service is by default running as Local System, which account might not be able to access the service which the HTTPCaller is calling.

FME Workbench runs with the account of the user that is logged in.

So you might have to provide credentials in the HTTPCaller to have it call the service or change the owner of the FMEEngines service (see in the properties of the service).

Hope this helps.

View original
Did this help you find an answer to your question?

4 replies

erik_jan
Contributor
Forum|alt.badge.img+18
  • erik_janContributor
  • Contributor
  • Best Answer
  • June 10, 2020

This might be a permissions issue.

The FME Server service is by default running as Local System, which account might not be able to access the service which the HTTPCaller is calling.

FME Workbench runs with the account of the user that is logged in.

So you might have to provide credentials in the HTTPCaller to have it call the service or change the owner of the FMEEngines service (see in the properties of the service).

Hope this helps.

jakethepainter
Contributor
Forum|alt.badge.img+6

Thanks for responding. There aren't any credentials required by the service; it's completely public. Am I understanding your suggestion correctly?

erik_jan
Contributor
Forum|alt.badge.img+18
  • erik_janContributor
  • Contributor
  • June 10, 2020
jakethepainter wrote:

Thanks for responding. There aren't any credentials required by the service; it's completely public. Am I understanding your suggestion correctly?

The question is if the local system account has access to anything outside the computer. Normally it does not have network access.

jakethepainter
Contributor
Forum|alt.badge.img+6

Just to add a note that in our environment we had to whitelist the site because our servers only allow access to whitelisted sites.

And to clarify in case anyone was surprised by my original description of the problem, I did not get any data back from the service, as you might expect. I was misled by the fact that the datetime of the zip file I was writing to updated, but actually it just updated with no data in it.

Reply


Helpful Members This Week

Community Stats

31,261
Posts
118,550
Replies
38,855
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.