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  
  Results
Article Product News
Please visit our Product News page for up to date information on your product. For particular articles regarding your issue, try making your search more specific by describing your issue and including your product version number.
CMS-XML SBM users sometimes consumes the wrong license for users that have named licenses assigned to them
SBM users of named Professional, Tracker and TrackerInet licenses can sometimes consume the wrong license type, even when these users are fully logged off the system at the time of login and their assigned named licenses are available. Scenarios for users of these license types include them sometimes: Consuming a concurrent TeamTrack license
CMS-XML Excessive e-mail notifications from License Manager
When all licenses are in use, the License Manager will e-mail the following message if the "send e-mail notification of all licensing issues" is checked - " was unable to obtain a license for Tracker -- Error: No such feature exists (-5,412): TrackerInet " " was unable to obtain a license for TrackerInet -- Error: No such feature exists (-5,412): TrackerInet "
CMS-XML Serena License Manager 2.1.5 (SLM 2.1.5)
Serena License Manager now supports native x86 64bit Windows servers and clients. 1.2 (DEF193988) SBM named license checkout may result in unnecessary calls to SLM server (client-side fix, included with SBM as of release 2009 R4 and newer) When SBM detects a named legacy user license (" Tracker ", stand-alone or as part of "Professional", and "TrackerInet" ) it requests the license with the "_named" portion added to the feature.
CMS-XML SLM: How to access the Serena License Manager through a firewall / What TCP ports are used by the Serena License Manager?
Out of the box, SLM clients (Dimensions CM, Dimensions RM, PVCS Version Manager, SBM, TeamTrack and Tracker ) connect to the lmgrd process by trying all ports in the 27000-27009 range on the specified SLM server. Once connected to lmgrd, that server informs the client on what port the merant vendor daemon is listening, after which the client connects to this port to request a license.
CMS-XML Delays in getting an SLM license causing login lag for TeamTrack/SBM
The problem is magnified if the license checkout fails, because TeamTrack / SBM will try to check out a "TeamTrack" license, then try for a " Tracker " license, then try for a "TrackerInet" license. Possible Solutions: Select "Disable NetBIOS over TCP/IP" on all
CMS-XML How can I see which licenses on the Serena License Manager (SLM) server are currently checked out by users?
For example, an SLM server with 25 Professional licenses (consisting, among others, of the license features VersionManager and Tracker ) and 50 VersionManager licenses would therefore report: Users of Professional : (Total of 25 license issued
CMS-XML How does a Product Name from the Entitlement site (FNO) map to one or more Product Features in SLM?
build_zos Tracker VersionManager
CMS-XML Serena License Server will not start and log showing garbage characters
 6:05:00 (merant) Tracker _named          Â
CMS-XML SLM 2.3.0 mlclient fails to check named licenses out if the first key in the license file for that feature is invalid
(inconsistent authentication code) 17:34:00 (merant) ==>INCREMENT Tracker _named merant 8.0 permanent 40 DUP_GROUP=U \

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs