Source: GUI Problembehebung
Probleme mit dem Graphical User Interface (GUI)
GUI Server nicht erreichbar
Problem
- SEP sesam kann nicht auf den GUI Server zugreifen.
Mögliche Ursachen
- Die Netzwerkverbindung zu SEP sesam ist abgebrochen.
- GUI-Server Prozess läuft nicht.
⇒ Lösung
- Stellen Sie sicher, dass der Computer läuft.
- Starten Sie den GUI-Server Prozess mit dem Befehl sm main reload rmi.
Verbindung zur Datenbank gescheitert
Problem
- SEP sesam kann sich nicht mit der Datenbank verbinden.
Mögliche Ursachen
- DB- oder RMI-Server laufen nicht.
⇒ Lösung
- Führen Sie die Befehle sm main reload db oder sm main reload rmi aus, um die Server neu zu starten.
GUI startet nicht
Problem
- Das Graphical User Interface (GUI) startet nicht.
Mögliche Ursachen
- Probleme mit Java-Rechten.
- Eintrag für den Computer in sm java.policy fehlt. Zum Beispiel:
// NET permission java.net.SocketPermission "'mypcname:*"', "'connect,accept,resolve"';
⇒ Solution
After updating Java from v. 6 to v. 7, the SEP sesam Server does not start
Problem
- The SEP sesam Server does not start after updating Java installation from major version 6 to version 7. This mostly concerns customers with SEP sesam installations on Windows based operating systems.
Possible causes
- The SEP sesam Server configuration file <sesam_install_dir>\var\ini\sm.ini 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.
⇒ Solution
- Edit the configuration file <sesam_install_dir>\var\ini\sm.ini.
- Typically, the path is C:\Program Files\Java\jre7\bin\java.
- Change the configuration file as follows:
[JAVA] java_exit_on_fail=no java_interpreter=C:\Program Files\Java\jre7\bin\java
Once you modified the configuration file and saved the changes, you should be able to start SEP sesam service.
- You should also check the JRE installation path, specified in the SEP sesam GUI properties in the Start menu and in the shortcut on desktop, as shown in the screenshot below.
SEP sesam RMI (GUI) Server does not start up after update to Java 7 update 51
Problem
- The SEP sesam GUI does not start after updating to Java version 7 update 51 (full version: 1.7.0_51-b13).
Possible causes
- Java policy in Java™ SE Development Kit 7, Update 51 (JDK 7u51) requires the right to listen on port 11401. For details, see Update Release Notes - Java™ SE Development Kit 7, Update 51 (JDK 7u51).
⇒ Solution
- Open the file <SESAM_ROOT>/var/ini/sm_java.policy.
- Go to 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";
⇒ Solution for new SEP sesam Server installations
- Completely uninstall SEP sesam Server.
- Completely uninstall Java JRE 7u51.
- Download an older Java JRE version (for example, Java JRE 7u45) from the Java Download Archive.
- Install an older Java JRE Version (for example: Java JRE 7u45).
- Install SEP sesam Server.
Cannot read or write to the working directory
Problem
- There is a problem with reading or writing to the working directory.
Possible causes
- The entry for the working directory in sm java.policy is missing.
- Windows example
// FILE permission java.io.FilePermission "'D:nsesamnvarn-"', "'read,write"';
- Linux/Unix/Tru64 example
// FILE permission java.io.FilePermission "'/sesam/var/-"', "'read,write"';
⇒ Solution
Online guide not available
Problem
- The online guide cannot be accessed.
Possible causes
- Adobe Acrobat Reader is not installed.
- Adobe Acrobat Reader is installed but not configured in the GUI.
- The PDF file is not configured in the GUI.
⇒ Solution
- Download Adobe Acrobat Reader from http://www.adobe.com.
Online help not available
Problem
- The online help cannot be accessed.
Possible causes
- There is no browser installed on the system.
- The browser is installed but not configured in the GUI.
- The HTML help file is not configured in the GUI.
⇒ Solution
- Install a browser.
Hinweis | |
|