Troubleshooting for Administrators

This section shows a few basic troubleshooting techniques in case of emergency.

FME Workbench-FME Server Connection

If you are unable to connect from FME Workbench to FME Server then the following suggestions may be of help.

Check if there is a firewall running on either your computer or the FME Server. If so, you must open port 80 (or 8080) to use the Web Connection.
Restart the FME Server Services. On Windows, go to Start > FME Server > Restart FME Server

If you are unable to access the FME Server web interface then the following suggestions may be of help.

Confirm that FME Server is running! The easiest way is to restart the FME Server Services (as above).
Check whether FME Server was installed using an application server port other than 80. For example, if port 80 was already being used the installer might have used a different port; 8080 is most common. To check, try entering the URL with this syntax http://<host>:<port>/fmeserver - for example http://localhost:8080/fmeserver

If a workspace appears in the FME Server queue, but is never executed, then it may be because no engines are running.

Check the Web Interface (Admin > Engines and Licensing) to confirm engine status. If no engines are available then update licensing as necessary. Once a license is available the engines should restart automatically.

If a workspace fails when it is being run, then the following suggestions may help.

Run the workspace first on FME Desktop. If it does not work there, it will not work on FME Server.
Check the FME log file using the Jobs page in the Web Interface. The log may help to explain why there is a problem.
Data paths can cause problems when moving from a local Desktop machine to a Server environment. Check the dataset parameters (Reader and Writer) to ensure they are not referring to a local path that does not exist on the Server. You may need to change the parameter to use the Resources filesystem and not a file path dialog.
If you are trying to read data with a UNC path, ensure that the FME Server Windows Service is being run by a user with the proper domain access permissions.
If you are using an FMEServerJobSubmitter transformer, be sure to check the server connection when porting from a test environment to a live environment.

If a scheduled workspace appears to have not been run at the expected time, then the following suggestions may be of help.

Ensure an engine is available, and that the scheduled job is not in a queue.
Check the date and time very carefully to ensure the correct values were entered.
Check the timezone is correct. The web interface operates on local timezone, which is not necessarily the same timezone as the server is physically located.