| |
Results |
|
SBM: Users get error "InitExtension Failed" and "License server could not be contacted"
|
When connecting to the APLS, you must enter the connection URL in SBM Configurator on the License Server page. However, if this URL is entered with a trailing slash, SBM will not be able to connect. The "Test Connect" link inside Confgurator will work, but SBM Tomcat will not be able to connect.
|
|
|
|
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.
|
|
|
|
Error "InitExtension Failed" when accessing SBM (TeamTrack or Business Mashups)
|
the folder. License Server Could Not Be Contacted
|
|
|
|
Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R4
|
... TABLE"> Could not read NSInstance table ... ... PROJECT"> Failed to delete project ... ... ARCHIVE"> Failed to delete the ... ... RESOURCE"> Failed to delete resource ... ... }'' does not exist.< ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ...
|
|
|
SBM System Administrator Guide
|
If your system uses seat licenses, the number of user accounts in your system cannot exceed the number of seat licenses added to Serena License Manager . If you inadvertently exceed the number of allowed user accounts, users receive an error similar to the following example when they attempt to log in: InitExtension Failed : The number of Regular Users and Managed Administrators ... exceeds the number of User seat licenses.
|
|
|
|
SBM System Administrator Guide
|
If your system uses seat licenses, the number of user accounts in your system cannot exceed the number of seat licenses added to Serena License Manager . If you inadvertently exceed the number of allowed user accounts, users receive an error similar to the following example when they attempt to log into the SBM User Workspace: InitExtension Failed : The number of Regular Users and Managed Administrators ... exceeds the number of User seat licenses.
|
|
|
|
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 .
|
|
|
|
SLM: Error 2 the system cannot find the specified file / License manager service fails to start
|
Go to the License Manager installation directory and run the following commands to reinstall the service: remove_license_service.bat install_license_service.bat
|
|
|
|
Calling PCLI from Apache on Linux fails with Cannot connect to license server system. (-15,570:13 "Permission denied"): VersionManager (Username)
|
The .islvrc file containing the license server reference was definitely being found because removing or renaming it produced another error. There was no entry in the SerenaLicenseSerer.log file, confirming PCLI could not reach that server.
|
|
|
|
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:
|
|
|
