JRE Update: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
== After updating Java to a newer major version SEP sesam Server will not | == After updating Java to a newer major version SEP sesam Server will not start == | ||
{{Box Hint|Note|This mostly concerns customers with SEP sesam installations on Windows based operating systems.}} | {{Box Hint|Note|This mostly concerns customers with SEP sesam installations on Windows based operating systems.}} | ||
Line 6: | Line 6: | ||
=== Indication === | === Indication === | ||
After a customer has updated his Java installation from major version 6 to version 7, the SEP sesam Server cannot | After a customer has updated his Java installation from major version 6 to version 7, the SEP sesam Server cannot start. This manual explains how to fix this issue. | ||
=== Cause of the problem === | === Cause of the problem === | ||
Line 20: | Line 20: | ||
java_interpreter=C:\Program Files\Java\jre6\bin\java | java_interpreter=C:\Program Files\Java\jre6\bin\java | ||
After the update from JRE 6 to JRE 7, the configured path is not present on the system anymore; this causes the SEP sesam | After the update from JRE 6 to JRE 7, the configured path is not present on the system anymore; this causes the SEP sesam start to fail. | ||
=== Solution === | === Solution === | ||
Line 36: | Line 36: | ||
Starting the SEP sesam Service should work after the change has been saved to the configuration file. | Starting the SEP sesam Service should work after the change has been saved to the configuration file. | ||
Further steps include changing the Start menu items as well as the desktop icons. Both include the JRE installation path and have to be changed to make the GUI | Further steps include changing the Start menu items as well as the desktop icons. Both include the JRE installation path and have to be changed to make the GUI start possible, compare the following screenshot: | ||
[[File:jreupdate.jpg]] | [[File:jreupdate.jpg]] |
Revision as of 15:38, 22 January 2014
After updating Java to a newer major version SEP sesam Server will not start
Note: |
This mostly concerns customers with SEP sesam installations on Windows based operating systems. |
Indication
After a customer has updated his Java installation from major version 6 to version 7, the SEP sesam Server cannot start. This manual explains how to fix this issue.
Cause of the problem
The SEP sesam Server configuration file:
<sesam_install_dir>\var\ini\sm.ini
It includes a configuration section which initializes the path to the JRE virtual machine detected during installation of SEP sesam:
[JAVA] java_exit_on_fail=no java_interpreter=C:\Program Files\Java\jre6\bin\java
After the update from JRE 6 to JRE 7, the configured path is not present on the system anymore; this causes the SEP sesam start to fail.
Solution
In order to resolve the issue edit this configuration file and change the path pointing to the old Java to the path of the new Java installation. Usually this Path is:
C:\Program Files\Java\jre7\bin\java
Change the configuration file to something like this:
[JAVA] java_exit_on_fail=no java_interpreter=C:\Program Files\Java\jre7\bin\java
Starting the SEP sesam Service should work after the change has been saved to the configuration file.
Further steps include changing the Start menu items as well as the desktop icons. Both include the JRE installation path and have to be changed to make the GUI start possible, compare the following screenshot:
After updating Java to a newer version SEP sesam RMI (GUI) Server will not startup
Solution
- Open the file <SESAM_ROOT>/var/ini/sm_java.policy
- Go to the section
// NET permission java.net.SocketPermission "*:*", "connect,resolve"; permission java.net.SocketPermission "*:11301", "connect,accept,resolve"; permission java.net.SocketPermission "*:11401", "connect,accept,resolve"; permission java.net.SocketPermission "*:21", "connect,accept,resolve";
- Change the line
permission java.net.SocketPermission "*:11401", "connect,accept,resolve";
- to
permission java.net.SocketPermission "*:11401", "connect,accept,resolve,listen";