Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML SLM: Running License Manager in a cluster (fail over / high availability / redundant / quorum) environment FAQ
If the auto-add feature is turned on, and the primary server is accepting activity, then that user will be auto-added to the primary server's users.lst file. However, if the primary server is down and activity is going to the secondary server, any new users will be added to the secondary server.
CMS-XML SLM: Certain clients sometimes/consistently cannot connect to the License Server, especially from remote locations
vmreg New users will automatically use the SLM server reference from the license.ini template file.
HTML Serena License Manager Version 2.1.4 Readme, Edition 1.1
4.6 New User Names Appear Incorrect in DBCS Environments
CMS-XML TRK: Tracker user logs on, the License Manager adds another entry to SQL Server licenses
TRK: Tracker user logs on, the License Manager adds another entry to SQL Server licenses
CMS-XML Does SSM 3.0 add a new license type to the Serena License Manager
Licensing is not different from SBM's perspective. The license manager will still use the Seat or Occasional license for SSM or SRC
CMS-XML License Manager does not auto-add users even though the checkbox is enabled in the Serena License Manager UI
Manually update the licmgr.ini file in the License Manager directory. Look for the section: [AUTOADD_FEATURES] Add the feature(s) desired and set to "true" Example: For Version Manager named licenses, add: VersionManager_named=true Save the changes and restart the Serena License Manager.
CMS-XML SLM 2.1.1 user names with umlaut cause problems when added manually
This is fine as long as the username is created in uppercase only in Version Manager. If the user in VM is created in lower or mixed case a new named license (if available) or a concurrent license will be used, as the username passed to license server is not being translated into uppercase correctly.
CMS-XML Dim12: License Manager: User is not on the include list and cannot be added because Auto-Add is not turned on for this feature.
If the above does not lead to results, run a procmon trace during the startup of the License Server and when the first DIM Named licenses should be consumed, this should show what file access issues there are. Please provide the procmon trace as well as the SerenaLicenseServer.log file to Serena Support for further review.
CMS-XML SLM GUI includes unusable licenses in the available count
When a license is added for a HOSTID that does not match that of the host, the license count is still added to the total of available licenses in the SLM GUI. Likewise, temporary licenses that have expired remain included in the total as well.
CMS-XML SBM Seat and Content licenses show as Concurrent licenses in SLM
When SBM Seat licenses or Contents licenses are added to SLM , their count shows up in the SLM UI in the column for Concurrent licenses. This can lead customers to believe that they have concurrent licenses when in fact they do not.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs