Skip to main content
Solved

Workbench runs in desktop mode but not when using quick translator


Forum|alt.badge.img

I have a workbench which calls a series of other workbenches. It works fine when running through Desktop mode but when running via Quick Translator it fails (see attached screenshot):

Best answer by redgeographics

FME_JOB_ID is an FME Server parameter, which should be ignored by Desktop.

Can you tell us a bit more about the workspaces (or maybe share them)? Are they meant to be run on FME Server?

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

4 replies

redgeographics
Celebrity
Forum|alt.badge.img+49
  • Celebrity
  • Best Answer
  • May 9, 2018

FME_JOB_ID is an FME Server parameter, which should be ignored by Desktop.

Can you tell us a bit more about the workspaces (or maybe share them)? Are they meant to be run on FME Server?


Forum|alt.badge.img
redgeographics wrote:

FME_JOB_ID is an FME Server parameter, which should be ignored by Desktop.

Can you tell us a bit more about the workspaces (or maybe share them)? Are they meant to be run on FME Server?

Yes, they are originally FME Server workbenches which I have reworked. The main workbench calls three separate workbenches by using Workspace Runner transformers instead of FME Server Job Submitter transformers

 

 


takashi
Contributor
Forum|alt.badge.img+21
  • Contributor
  • May 9, 2018
redgeographics wrote:

FME_JOB_ID is an FME Server parameter, which should be ignored by Desktop.

Can you tell us a bit more about the workspaces (or maybe share them)? Are they meant to be run on FME Server?

FME Quick Translator won't create FME_JOB_ID parameter. You will have to edit the workspace to remove all references to the parameter, if you need to run the workspace with Quick Translator or command line in Desktop environment.

 

FME Workbench creates FME_JOB_ID and the error won't occur, but the value will always be empty string.

 

 


Forum|alt.badge.img

Thanks for the answers. It turns that there were some references to FME_JOB_ID in Slack messages. All fixed now!


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