On the “Jobs” page within the Web Interface, jobs appears under the Queued tab. When a Job is run, it does not complete.
The FME Engines are unavailable. Possible reasons include:
Please check the following in order to activate the FME Engines.
For FME Server 2015 and newer:
Within the top menu in the web user interface, select Manage > Administration to go to the Engine Management page. If the number of engines is set to zero, try changing the number of engines. If there are no engines listed at all, restart all FME services using the directions listed here: Working with the System Services. Then check the Engine Management page again to see if the engines are activated.
For FME Server 2014 and older:
Within the web user interface, select the “Engines” Tab to view the Engine Management page. The status of each engine is displayed. If the engine count is zero, try changing the number of engines. If the engines are stopped, restart all FME services using directions listed here: Working with the System Services. Check the FME Server homepage to see if the engines are activated.
If you do have a FME floating license available and the Engine Management page lists the engines as unlicensed, run the FME Licensing Assistant and point FME to your floating license server. On Windows, the Licensing Assistant is available by going to:
Programs -> FME Server -> Install -> FME Licensing Assistant
On Linux there is a command line FME Licensing Assistant available here:
For additional assistance with the FlexNet License Server see: Floating License Troubleshooting. Once licensing is complete, check the FME Server homepage to see if the engines are activated.
Confirm the paths to the FME Engines are valid by looking in the process monitor configuration file here:
FME Server 2015 and newer: <FMEServer>\Server\processMonitorConfigEngines.txt
FME Server 2014 and older: <FMEServer>\Server\processMonitorConfig.txt
The paths to the FME Engines are visible near the end of the file:
FME Server 2015 and newer:
FME Server 2014 and older:
Verify that these paths exist on the system and are correct. If they are not correct, change the paths. Restart all FME services and then check the FME Server homepage to see if the engines have been activated.
This issue may occur on a custom installation only. If you have engines on a separate system from the FME Server Core, make sure that a firewall is not blocking access. Refer to the FME Server Architecture Diagram to see the necessary ports to allow. It may be helpful to use a network monitoring tool to check the status of each port, (open, closed or filtered) as an open port is required.
If the account that is running the FME Server Engines Service does not have the proper read/write permissions to access the files it needs, the Engines will fail to start up properly. Try changing the account running the FME Server Engines Service to your own user account and restart the services to see if that helps.
If you have completed these steps and still do not see active FME Engines in the Web User Interface, send the following information to Safe Support by filing a support request:
No one has followed this yet.