Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML DA: Install error (1720) when upgrading from DA 6.2.2 to 6.3.1
The root cause is the common tools registry has been deleted: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Serena\CommonToolsTo resolve the recreate this key with the following fields : ... A reg file has been attached, it can be modified to suit the specific version & installation location for the user.
CMS-XML What is the SLM License Server HOSTID value for the Locking information field on the SLD site, and how should the generated key be applied to SLM?
is used to generate a new SLM license key, the Locking information field is requesting an SLM License Server HOSTID What value should be put there, and how should the generated license be applied to the SLM License Server?
CMS-XML Disaster Recovery: Creating a new license key
If the License Manager server needs to be replaced (or if any component of the hardware is replaced, causing the HostID value to change ), you can "rehost" your existing license key. This will generate a new license key and legally invalidate the original license key.
CMS-XML Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
value. The HostID is encoded in each key, and by changing the value on the SERVER line you will invalidate the keys in the file. Based on your knowledge of your environment, you will need to decide what to do next.
CMS-XML SLM - How to use the Serena License Server with an existing installation of FLEXlm/FlexNet used by other applications
This document describes how to change an existing (Enterprise) FLEXlm / FlexNet installation, already used by other applications, such that it can also serve SLM-based licenses. The information contained in this document is provided for your convenience, and assumes that you are familiar with supporting FLEXlm / FlexNet based solutions. W
CMS-XML The "Auto-add user IDs for named licenses" checkbox intermittently does not work
When that happens, the change to the checkbox did not 'take', meaning it didn't get written out to licmgr.ini (so the SLM server will not honor it) nor did it get saved into memory: if you switch to another license type and come back, the checkbox will be back in the state it had before you clicked it.
CMS-XML The Windows SLM service is not being removed during the uninstall
The SLM service is not being removed by the standalone SLM windows installer which creates an orphaned service and when a reinstall occurs the service has the potential of breaking if SLM is installed to a different directory. A manual change to the registry fixes the problem
CMS-XML SLM: There is no way to specify port number when setting email Admin notifications
field in the Notification tab. You can also specify whether or not SSL needs to be used, and provide a username and password for SMTP servers requiring authentication.
CMS-XML In v7.1.x the delivered LICTEST CNTL references PRODUCT=205' in parms
Because of this the ‘PRODUCT=’ parm in the LICTEST CNTL member for v7.1.x needs to be changed from this: //TEST EXEC PGM=LICTEST, // PARM='PRODUCT=205,VERSION=5.5'
CMS-XML SLM 2.2.0 does not enforce Administrative execution level for its GUI (SerenaLM.EXE)
users.lst and licmgr.ini files in its installation directory, as well as the ability to restart the Serena License Manager service (after making changes to the configuration).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs