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
CMS-XML SLM HotFix for lmgrd crashes on Solaris
SLM HotFix for lmgrd crashes on Solaris
CMS-XML Serena License Manager: HotFix for SLM 2.2.0 to remediate two security vulnerabilities in FlexNet Publisher
Serena License Manager: HotFix for SLM 2.2.0 to remediate two security vulnerabilities in FlexNet Publisher
CMS-XML SLM 2.2.0.1: HotFix for SLM 2.2.0 to remediate two security vulnerabilities in FlexNet Publisher
SLM 2.2.0.1: HotFix for SLM 2.2.0 to remediate two security vulnerabilities in FlexNet Publisher
CMS-XML Hotfix for SLM 2.1.5 on Windows when the license server becomes unresponsive and the merant.exe process uses near 100% of a CPU core
Hotfix for SLM 2.1.5 on Windows when the license server becomes unresponsive and the merant.exe process uses near 100% of a CPU core
CMS-XML SLM: How to determine your version of Serena License Manager
- Starting with SLM 2.1.5 Hotfix DEF199803 ( P2624 ), the SerenaLicenseServer.log file, or its successor SLM.log, contains the SLM version as part of the vendor daemon initialization. Example:
CMS-XML SLM 2.2.0 fails to start merant vendor daemon with EXITING DUE TO SIGNAL 30 Exit reason 7
We recommend doing the following: Check if the SLM 2.2.0.1 HotFix from KB doc P2761 has been installed.
CMS-XML Serena License Manager 2.2.0 (SLM 2.2.0)
After installing SLM 2.2.0, also install the security from HotFix from KB document P2761 . On Operating Systems using UAC (Windows Server 2016, Windows 7, Windows 8, Window 10), use run right-click | Run as administrator to both install SLM and launch its GUI (serenalm.exe).

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs