Skip to main content
  • EN

Hi,

I'm experiencing an issue with SystemCaller when publishing to FME Server (2019.2 - build 19801 - 64-bit))

We're using a SystemCaller to execute a program (with some parameters supplied) which is stored on a shared network, and it works successfully on FME Desktop 2019.2 (same build number as the Server instance). The Server has access (read/write) to the same network location, but when the published workspace runs, it just stops at the SystemCaller Execution. No error, no falling over...it just hangs. We left it overnight, but it was still the same the next morning.

Things we've tried, to narrow down the issue:

  • Ran the script in SystemCaller on FME Desktop - it worked in around 30 seconds
  • Ran the same script in the cmd prompt on the Server box (as svc_fme user) - it ran successfully in 30 seconds
  • Tried hardcoding the network location into Server (rather than using $(FME_SHAREDRESOURCE_DATA)) - this didn't affect the outcome at all - still hung
  • There are additional '/'s in the UNC path (as supplied in the $(FME_SHAREDRESOURCE_DATA)) - we tried removing these but it made no difference

 

For reference, the script we're trying to run is (with the password hashed out):

//corp/Landmark/Groups/Data/FME/FME_Server_2019.2///resources/data/Putty/plink.exe -ssh genasys@exconv02 -pw ###### cp -R /storage/50kcrm-35/MERGED /imogen_raster/50kcrm/l00035 > //corp/Landmark/Groups/Data/FME/FME_Server_2019.2///resources/data/Putty/Output/OutputDEL2.txt

 

We think it might be something to do with running cmd prompts in SystemCaller using a non-Admin account - any ideas how we force FME Server to run it as Admin?

 

Or has anyone any other ideas we can try?

Thanks,

Martyn

Just to be sure: If it is an authenticated share, you need not only manage the rights of the fme server user but also fix the share configuration.

Just to be sure: If it is an authenticated share, you need not only manage the rights of the fme server user but also fix the share configuration.

Thanks - We're uploading the workspace under a user that has both admin and superuser permissions - what do you mean by 'fix the share configuration'? Thanks,

Thanks - We're uploading the workspace under a user that has both admin and superuser permissions - what do you mean by 'fix the share configuration'? Thanks,

I'm afraid I can't explain better because I did not fix it. But we recently migrated to a new environment and had issues with the systemcaller on certain paths. IT confirmed the fme server user had sufficient rights on the files.

Later we got feedback they also had to change the "sharing permissions" and our problem was gone. So I'm not sure you have the same issue, but I would like to exclude it.

Hi @mlufkin,

Just wanted to see whether you have configured the FME Server Windows Services?

https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Running_System_Services_Under_Different_Accounts.htm

Hi @mlufkin,

Just wanted to see whether you have configured the FME Server Windows Services?

https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Running_System_Services_Under_Different_Accounts.htm

Hi @chrisatsafe, yep, we've configured the FME Server Windows Services, and we can successfully read and write using FME Server to other parts of our network. We can also run the above script in cmd prompt on the Server box - both cmd prompt and Server are running from the same windows user, 'fme_svc'.

Thanks,

Hi @chrisatsafe, yep, we've configured the FME Server Windows Services, and we can successfully read and write using FME Server to other parts of our network. We can also run the above script in cmd prompt on the Server box - both cmd prompt and Server are running from the same windows user, 'fme_svc'.

Thanks,

Hi @mlufkin,

Hmm, sounds like we will need to look closer into this one. I've created a case on your behalf and sent you an email requesting additional information that will allow our server team to further investigate.

Hi all, I think we've found the reasons behind this behavious...

Basically, plink.exe (the program we are trying to fire up) requires a ‘Is this from a trusted source’ ticked box on startup, and as this is never ticked, FME Server just waits for it to be ticked…forever.

I’m still not sure why we don’t get the same dialog box when running direct from cmd (using the same user credentials), but we’re hopeful we can bypass the dialog box with a tweak to a config file.

Thanks everyone for your help!

Reply


Community Stats

30,176
Posts
114,543
Replies
37,835
Members
Terms & ConditionsCookie 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.