Skip to main content
  • EN

After upgrading FME Server versions and running workspaces which have an FMEServerJobSubmitter, the parent job runs but hangs after the child workspace enters the queue. The 'Wait for Job to Complete' is set to yes, shouldn't this start the child process running at the same time?

This is caused by a hostname mismatch between the FMEServerJobSubmitter and FME Server:

https://knowledge.safe.com/articles/351/fmeserverjobsubmitter-transformer-may-cause-worksp.html

 

 

This should not be the case if you created the workspace in FME 2017, or have upgraded to the most recent version of the FMEServerJobSubmitter. If your workspace was created in FME 2016 and then opened in 2017, it likely contains an older version of the FMEServerJobSubmitter and you may wish to upgrade.

When you run the workspace again on FME Server, you should see the child job running on an extra engine, which will appear as: :ServerHost]_]EngineName]@]JobID].

 

Transformer upgrade documentation: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Workbench/Working_With_Transformer_Versions.htm

Reply


Community Stats

30,357
Posts
115,370
Replies
38,093
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.