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?
Solved
Why does my workspace on FME Server hang when using the FMEServerJobSubmitter?
+21- Safer
Best answer by jlutherthomas
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
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2This 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