Source:Troubleshooting GUI
Graphical User Interface (GUI) problems
After updating SEP sesam on Windows, GUI cannot be opened
Problem
After updating SEP sesam to version ≥ 4.4.3.82 Beefalo V2 on Windows, GUI cannot be opened when the group policy option Prevent access to registry editing tools is applied.
Possible cause
This issue seems to be related to the group policy (GPO) setting: if Prevent access to registry editing tools is applied for a specific user or group, opening the GUI does not work for the users which are prevented from accessing the Registry. In most cases, users with admin privileges will still be able to run the GUI as they are typically exempt for a GPO (and are able to access the Registry). If this policy is disabled (or not configured), the users may access the GUI regardless of their privileges.
⇒ Solution
To enable access to the GUI for the affected users (typically non-admin users), disable the group policy option Prevent access to registry editing tools.
Warning | |
Only experts should edit the registry; modifying Windows Registry incorrectly might crash your Windows operating system causing data loss. |
- Press the Windows key + R to open the Run window.
- Type gpedit.msc and press Enter.
- In the Group Policy Editor -> User Configuration -> Administrative Templates -> System, double-click on Prevent access to registry editing tools setting in the right panel and select Disable. Then click Apply.
GUI Server not accessible
Problem
SEP sesam cannot access the GUI Server.
Possible causes
- The network connection to SEP sesam is broken.
- The GUI Server process is not running.
⇒ Solutions
- Make sure that the computer is running.
- Start the GUI server process by running the command sm main reload rmi.
Database connection failure
Problem
SEP sesam cannot connect to the database.
Possible cause
The DB or RMI servers are not running.
⇒ Solution
Run the commands sm main reload db or sm main reload rmi to restart the servers.
GUI does not start
Problem
The Graphical User Interface (GUI) fails to start.
Possible causes
- There is a problem with Java rights.
- A problem with the screen resolution.
⇒ Solution
In case of the screen resolution problem, set a resolution to at least 1920x1080 (full HD).
Wrong time values in the GUI
Problem
In GUI, the displayed time values may not correspond with the system's default timezone.
Possible causes
- This can be caused by exporting the system-wide environment variable TZ in the system-wide /etc/profile file, which can override the default system locales, leading to an incorrect timezone setting in the postgresql.conf file.
- On Debian, the timezone settings are stored in the /etc/timezone file. If the timezone on the system is changed using the timedatectl set-timezone command, only the /etc/localtime file is updated. The /etc/timezone file remains unchanged.
⇒ Solution
- In the /etc/profile file update the TZ environment variable and set the timezone that matches the desired system default timezone. This will ensure that the timezone setting in the postgresql.conf file is aligned with the system default timezone.
- On Debian, update the settings in /etc/timezone file to set the correct timezone.
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.
⇒ Solution
Install a browser.