FME Server Core won't start: old classpaths present

Symptom

After a clean installation of FME Server the FME Server core won't start and the following error is present in the fmeServer.log file.

Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core java.lang.UnsatisfiedLinkError: C:\apps\FMEServer\Server\lib\fmeutil\fmeutil_java.dll: The specified network name is no longer available
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at java.lang.ClassLoader$NativeLibrary.load(Native Method)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at java.lang.ClassLoader.loadLibrary0(Unknown Source)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at java.lang.ClassLoader.loadLibrary(Unknown Source)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at java.lang.Runtime.loadLibrary0(Unknown Source)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at java.lang.System.loadLibrary(Unknown Source)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at COM.safe.fmeserver.RepositoryManager.init(RepositoryManager.java:115)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at COM.safe.fmeserver.FMEServer.init(FMEServer.java:381)
Tue-25-Jan-2011 02:27:30 PM ERROR Thread-20 Core at COM.safe.fmeserver.FMEServer.main(FMEServer.java:1861)

Access this log file from:

• 2016 and newer:
  <FMEServerSystemShare>/resources/logs/core/current/fmeServer.log
• 2015.1:
  <FMEServerSystemShare>/Logs/core/current/fmeServer.log
• 2015.0 and 2014 SP5 to SP2:
  <FMEServerInstallDir>/Logs/core/current/fmeServer.log
• 2014 SP1 and older:
  <FMEServerInstallDir>\Logs\fmeServer_xx.log

Cause

The issue is due to the fact old classpath variables still exist pointing to the wrong location. You can tell the exact classpath variables FME Server is using by looking at the classpath variable in:

• 2016 and newer:
  <FMEServerSystemShare>/resources/logs/core/current/fmeProcessMonitorCore.log
• 2015.1:
  <FMEServerSystemShare>/Logs/core/current/fmeProcessMonitorCore.log
• 2015.0 and 2014 SP5 to SP2:
  <FMEServerInstallDir>/Logs/core/current/fmeProcessMonitorCore.log
• 2014 SP1 and older:
  <FME ServerInstallDir>/Logs/processMonitorJavaState.log

Resolution

1. Control Panel >> System >> Advanced Tab >> Environment Variables
2. Double click the classpath system variable.
3. Copy the variable value into a text editor
4. Remove any references to invalid paths (the most common is paths pointing to old installation locations)
5. Once you have done this reboot the server.