Symptoms

For Windows only FME Server 2011 ( < 6511) will not start and the FME Server Web services do not function properly either.

The ProcessMonitor log (<FMEServer>logs\ProcessMonitor_xx. log) may have errors referring to resources which cannot be found for example:

ERROR    Thread-23   Scheduler   java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory

Also the Web Admin Interface will not function and the page returns with  404 error ...The requested resource (/fmeserver-admin) is not available.
Your own servlet engine logging may also show errors about missing resources settings or bundles for example:

SEVERE: The repository port is not a number: {SAFE{fmeserverRequestPort}}

Cause

These symptoms indicate a bad installation. There are two known issues that have caused this problem:
  1. If your Windows temp directory was defined on a drive that was not the  C:\ drive some early release builds of the FME Server 2011 installer will not work.
  2. If the path to your Windows temp directory has spaces in it the FME Server 2011 installer will not work.


Resolution

1. The issue with having a temp directory not on the C:\ has been fixed in FME Server 2011 Build 6511 or later and the problem will not occur if using the current downloadable installer of FME Server 2011.  To resolve this issue uninstall FME Server and reinstall using the currently downloadable FME Server 2011.
 
Detailed Steps:
 
  • Unistall FME Server by finding FME Server in your Windows Programs panel and right clicking to unistall.  After the restart ensure all FME Server files have been removed from your computer including your <FMEServer> install directory.  Also ensure that all of the FME Server services directories and .war files have been removed from your <WebApps> directory on your servlet engine.
  • Obtain the current FME Server 2011 installer from your Sales Manager
  • Install FME Server again
2. If you have spaces in the path to your temp directory the FME Server 2011 installer will not work. The issue has been fixed in FME Server 2012.  The work-around for FME Server 2011 is to change your Windows TEMP environment variable to a path that does not have a space.

Detailed Steps
  1. Unistall FME Server by finding FME Server in your Windows Programs panel and right clicking to unistall.  After the restart ensure all FME Server files have been removed from your computer including your <FMEServer> install directory.  Also ensure that all of the FME Server services directories and .war files have been removed from your <WebApps> directory on your servlet engine.
  2. Open the Windows Control Panel and go to System - Advanced System Settings and click on the Enviroment Variables button. Chante the TEMP environment variable to path that does not have a space for both your user and the system.
  3. Install FME Server again and go through the verification steps.
  4. Once FME Server is installed you can change your TEMP enviroment variable back to you original path if you want