FlexNet Publisher Knowledge Base

SummaryUsing the RESERVE keyword with multiple licensing pools in the license file.SynopsisWhen there is more than one licensing pool for a given feature, such as having multiple INCREMENT lines, some confusion can occur when customers make use of th...

Summary This is the list of FlexNet Publisher 2014 R2 (11.13.0) resolved issues, released on November 25, 2014. Synopsis This release of the FlexNet Publisher Licensing Toolkit resolves the following issues. (Numbers in parentheses indicate the Reven...

SummaryThis article will explain what to do if 'lm_new.obj' is missing after building the Flexnet Publisher (FNP) toolkit.SynopsisIf building the FNP toolkit and the 'lm_new.obj' doesn't seem to have been created then a 'veryclean' can be performed a...

SummaryFlexNet Publisher 2015 Security Update 1 (11.13.1.2) Release NotesSynopsisBelow are the Table of Contents from the attached FlexNet Publisher 2015 Security Update 1 (11.13.1.2) Release Notes.This is meant to act as a reference for KnowledgeBas...

SummaryFlexNet Publisher 2014 (11.12.1.5) SP5 Release NotesSynopsisBelow are the Table of Contents from the attached FlexNet Publisher 2014 (11.12.1.5) Release Notes.This is meant to act as a reference for KnowledgeBase Article search return results....

SummaryA possible security vulnerability has been reported in the FlexNet Publisher lmadmin License Server Manager.SynopsisA possible security vulnerability has been reported in the FlexNet Publisher lmadmin License Server Manager. More specifically...

SummaryWhen attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the follow...

SummaryThe lmremove functionality does not terminate lingered licenses.SynopsisIt has been noted that the lmremove functionality, whether implemented via an API call or the lmremove (lmutil) utility does not free lingered licenses.DiscussionThat woul...