| |
Results |
|
Serena License Manager GUI (serenalm) fails to launch with a Java exception on Solaris if the environment variable LD_LIBRARY_PATH_64 is defined
|
Serena License Manager GUI (serenalm) fails to launch with a Java exception on Solaris if the environment variable LD_LIBRARY_PATH_64 is defined
|
|
|
User completes interaction with SBM
|
YES Auto logout defined ? NO
|
|
|
|
Bundles with their PACKAGE line missing from a license file yield a seemingly perfect but non-functional license
|
Nothing will complain anywhere: the SLM GUI looks okay and server status is great. However, no one can use the licenses, because the PACKAGE that defines the feature set isn't in place. It can take a long time to spot this problem.
|
|
|
|
How does a Product Name from the Entitlement site (FNO) map to one or more Product Features in SLM?
|
Bundle licenses, like Professional, first show the Product Feature name, followed by a list of features typically found in the PACKAGE defining that bundle (italics). Product Name (Entitlement) Product Features (SLM)
|
|
|
|
Cannot start Serena License Manager (SLM) the catalina.out shows: hostid is (Can't get hostid of type 2 [])
|
The recommendation was for the Linux admin to reconfigure the Linux box to have eth0 be available as part of the available network interfaces. For the particular customer, there was is an eth0 adapter defined in the /etc/sysconfig/network-scripts directory, but the administrator has not enabled it.
|
|
|
|
SLM: Running License Manager in a cluster (fail over / high availability / redundant / quorum) environment FAQ
|
The three servers are defined in the serena.lic file. However, you can also open a command window, and run the command "get_concurrent_usages".
|
|
|
|
SLM 2.3.0: Collect Logs fails with error: was unexpected at this time. RC=255
|
Before: echo SERENA_LM_DATA is defined as %SERENA_LM_DATA% >> "%Dest%\licdir.txt" After:
|
|
|
|
SLM: How to access the Serena License Manager through a firewall / What TCP ports are used by the Serena License Manager?
|
... 11:47:16 (lmgrd) merant using TCP-port 2730 Despite being defined on port 27010, the merant vendor daemon ended up running on the randomly chosen port 2730 because 27010 was not available.
|
|
|
