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 Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
In SBM System Administrator, go under Options> License Options. Verify that the Host Name is the name or IP address of the machine where the License Manager is installed.
CMS-XML PVCS Version Manager returns message that it could not connect to the specified license server, or that the license has expired
Access has been denied because the license has expired. Please contact your PVCS Version Manager administrator for further assistance.
CMS-XML Intermittently the Configuration Utility displays an error message claiming that the AE schema has not been initiated and the License Server information cannot be saved
Intermittently the Configuration Utility displays an error message claiming that the AE schema has not been initiated and the License Server information cannot be saved. This is not true as the AE schema has been initiated and it can be contacted on the Database Servers tab. One can ignore this error message and close the CU despite the error message and SBM continues to work fine.
CMS-XML SLM vendor daemon cannot use "localhost" as SERVER identifier
Unfortunately a bug in the FLEXlm code licensed by Serena, which the merant vendor daemon is using, prevents this from working. Instead of the hostname provided on the SERVER line in the license file, the vendor daemon always attempt to connect to the lmgrd process using the IP address associated with the hostname. Since that IP address may not be valid, attempt to contact the lmgrd process fail, yielding the following error in the SerenaLicenseServer.log file in the SLM directory:
CMS-XML SLM: Certain clients sometimes/consistently cannot connect to the License Server, especially from remote locations
(as defined in ISLV file C:\WINNT\islv.ini). Please contact your Serena administrator for further assistance.
CMS-XML SLM service fails to launch on UNIX - SerenaLicenseSerer.log has error "(lmgrd) merant exited with status 47 (Child cannot exec requested server)"
If Host IPS is installed, briefly disable it and retest. Should this solve the issue, check with your UNIX admin if the server has the correct group membership related to this application and correct as needed. If that does not solve the issue, contact McAfee to have them investigate and resolve the failure.
CMS-XML KM-Dim7: Error: Cannot connect to license server; (WinSock: Connection refused)
KM-Dim7: Error: Cannot connect to license server ; (WinSock: Connection refused)
CMS-XML SLM 2.1.5: Cannot launch SerenaLM GUI on Linux
SLM 2.1.5: Cannot launch SerenaLM GUI on Linux
CMS-XML SLM 2.1.5: Cannot launch SerenaLM GUI on Solaris
SLM 2.1.5: Cannot launch SerenaLM GUI on Solaris
CMS-XML SLM 2.3.0 GUI shows java.lang.UnsatisfiedLinkError: ...\SLM\lib\lm.dll: Can't find dependent libraries
SLM 2.3.0 GUI shows java.lang.UnsatisfiedLinkError: ...\SLM\lib\lm.dll: Can't find dependent libraries
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs