| |
Results |
|
DA: Install error (1720) when upgrading from DA 6.2.2 to 6.3.1
|
There is a problem with this Windows Installer package. A script required for this install to complete could not be run . Contact support personnel or package vendor.
|
|
|
|
SLM: There is no way to specify port number when setting email Admin notifications
|
script using: ... For Windows systems running SLM as an application you could add this code to the start_licenseserver.bat ... (or use the same option when running SLM as a service, shown next) For Windows systems running SLM as a service, you must create the variable _JAVA_OPTIONS as system environment variable with the value shown above and reboot your operating system.
|
|
|
|
How to automatically start the Serena License Manager (SLM) server during boot of a UNIX or Linux system
|
... , a wrapper script needs to be ... ... user designated to run SLM. Attached to this KB article is a sample script of such a wrapper. Modify the SLMDir and SLMUserID variables in the script as appropriate, copy it into the /etc/init.d ... This will start the SLM server as one of the last tasks when entering run levels 2, 3 and 5, and stop the SLM server as one of the first tasks when entering run levels S, 0 and 1. ... Note that some operating systems do not have certain run levels.
|
|
|
|
Serena License Manager GUI (serenalm) fails to launch with a Java exception on Solaris if the environment variable LD_LIBRARY_PATH_64 is defined
|
in your environment prior to running serenalm ... , or update that launcher script to do this for you (which has the advantage of only affecting the SLM GUI).
|
|
|
|
The Version Manager Desktop Client GUI and/or the Serena License Manager GUI no longer show up in Exceed
|
After installing VM 8.5.x, the VM Desktop Client GUI (pvcsvmux) no longer shows up in Exceed. After installing SLM 2.2.x, the SLM GUI (serenalm) no longer shows up in Exceed. In both scenarios the window does not appear, even though the process keeps running .
|
|
|
|
SLM: Running License Manager in a cluster (fail over / high availability / redundant / quorum) environment FAQ
|
SLM: Running License Manager in a cluster (fail over / high availability / redundant / quorum) environment FAQ
|
|
|
|
Unable to launch SLM 214 GUI on an AMD 64 Opteron CPU running Windows
|
Unable to launch SLM 214 GUI on an AMD 64 Opteron CPU running Windows
|
|
|
|
Required Operating System packages to run SLM 2.2.0 or SLM 2.3.0 on Red Hat Enterprise Linux (RHEL)
|
Required Operating System packages to run SLM 2.2.0 or SLM 2.3.0 on Red Hat Enterprise Linux (RHEL)
|
|
|
|
LIC9999E - TOKEN FAILED occurring until ser10ty LOAD CSA job run twice
|
LIC9999E - TOKEN FAILED occurring until ser10ty LOAD CSA job run twice
|
|
|
|
How to fix an SLM server that stopped working after renaming the operating system
|
If the system running the Serena License Manager (SLM) has been renamed, the license server will no longer be able to start. The SerenaLicenseServer.log file will contain something similar to:
|
|
|
