Troubleshoot > Troubleshooting: Server startup > Troubleshooting: The server will not start

Troubleshooting: Server will not start

Possible causes:

  • Incorrect database connection configuration
  • Unsupported JRE version
  • License issues: The license has expired or is not valid

Incorrect database connection configuration

If you are unable to start Service Manager from the command prompt, review your configuration in the sm.ini file and confirm that you have the correct database connection information, login, and password, using the instructions in Service Manager Installation.

Tip Make sure that the following parameters are configured correctly in the sm.ini file: sqldb, sqllogin, and sqldictionary.

The Service Manager server starts as a Windows service by default. If the server starts from the command line, but not as a Windows service, uncomment the following line in the sm.cfg file to produce an output file which may contain some information from the Java JVM.

#cmd /c "sm" > C:\\process_stdout 2>&1

You can change the name and location of the output file by changing "C:\\process_stdout" to the path and file name you prefer. Using "C:\\process_stdout.log" creates a file called process_stdout.log at the root of the C drive. Once you have done this, try starting the server as a service. Any Java errors that occur will show up in the file and folder you specified.

Unsupported version of JRE

If you have installed a version of Java Runtime Environment (JRE) that is not supported, the server displays the following error message:

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file

Install a supported version of the JRE as indicated in the Service Manager Support Matrix.

License issues

The IP address of the first host on which the Service Manager Server starts up must be defined in the grouplicenseip parameter in the sm.ini file, and the license must be bound to this IP address.

Review the sever log file (sm.log) to check for license issues. A typical eye catcher is that shared memory could not be created, which may be a consequence of license issues.

Related topics

Startup and shutdown
Starting Service Manager on Windows
Stopping Service Manager on Windows

Related topics

Start the server from the Windows command prompt
Start the server from Windows services
Stop the server from the Windows command prompt
Stop the server from Windows services

Related topics

Troubleshooting: Bad version number in .class file