Showing articles with label FlexNet Publisher 2016 (11.14.0).
Show all articles
FlexNet Publisher Knowledge Base
Error - (Version of vendor daemon is too old. (-83,21049:104 "Connection reset by peer"))
0 0 6292
SummaryThe error (Version of vendor daemon is too old. (-83,21049:104 "Connection reset by peer")) is seen after upgrading the Flex Enabled ClientSymptomsErrors similar to:"9:35:08 (flexera) Request denied: Client (11.14) newer than Vendor Daemon (11...
Why can't older clients check-out licenses borrowed by newer clients?
0 0 372
SummaryWhy can't older clients check-out licenses borrowed by newer clients?QuestionDid something change around FNP 11.14 that causes clients to not be able to use a borrowed license that was borrowed from a newer client? I?m running an 11.14.1.2 ser...
FlexNet Publisher 2016 (11.14.0) FlexNet Publisher 2016 R1 SP1 (11.14.0.1) FlexNet Publisher 2016 R1 SP2 (11.14.0.2) FlexNet Publisher 2016 R2 (11.14.1) FlexNet Publisher 2016 R2 SP1 (11.14.1.1) FlexNet Publisher 2016 R2 SP2 (11.14.1.2) FlexNet Publisher 2016 R2 SP3 (11.14.1.3) FlexNet Publisher 2017 R1 FlexNet Publisher 2018 R1 (11.15.1) Question
Why is remaining linger time in lmstat showing wrong whenever license server restarted?
0 0 1281
SummaryWhy is remaining linger time in lmstat showing wrong whenever license server restarted?QuestionWe noticed the borrow timestamp (linger countdown value) will reset on the server side when the license server restarts. The count restarts, but the...
FlexNet Publisher 2015 (11.13.1) FlexNet Publisher 2015 SP1 (11.13.1.1) FlexNet Publisher 2015 SP3 (11.13.1.3) FlexNet Publisher 2015 SU 1 (11.13.1.2) FlexNet Publisher 2016 (11.14.0) FlexNet Publisher 2016 R1 SP1 (11.14.0.1) FlexNet Publisher 2016 R1 SP2 (11.14.0.2) FlexNet Publisher 2016 R2 (11.14.1) FlexNet Publisher 2016 R2 SP1 (11.14.1.1) FlexNet Publisher 2016 R2 SP2 (11.14.1.2) FlexNet Publisher 2016 R2 SP3 (11.14.1.3) FlexNet Publisher 2017 R1 FlexNet Publisher 2018 R1 (11.15.1) Question
Flexnet Publisher 2016 R2 11.14.1 Release Notes
0 0 2957
SummaryFlexnet Publisher 2016 R2 11.14.1 Release NotesSynopsisBelow are the Table of Contents from the attached FlexNet Publisher 2016 R2 (11.14.1) Release Notes.This is meant to act as a reference for KnowledgeBase Article search return results.Disc...
Support for TLS communication in FlexNet Publisher?
0 0 903
SummaryIs there support for TLS communication in FlexNet Publisher?QuestionDoes FlexNet Publisher support TLS communication (the successor to SSL?) If so, what versions does it support (1.0, 1.1, and 1.2?)If it is supported, is there any difference i...
FNP calling IP address 169.254.169.254
0 0 1222
SummaryAs part of the Amazon EC2 detection FNP may make calls to the IP Address 169.254.169.254:80SynopsisStarting with FlexNet Publisher (FNP) 11.12 it has been noticed that FNP attempts to communicate with the IP address 169.254.169.254. Discussion...
Which version of OpenSSL is used with FNP?
0 0 339
SummaryWhich version of OpenSSL is used with FlexNet Publisher?QuestionWhich version of OpenSSL is used with FlexNet Publisher?AnswerFor FNP 11.12.1, the OpenSSL version used was 1.0.1e. For FNP 11.13.1, the OpenSSL version used was 1.0.1h. In FNP 11...
How to grant necessary permission to LOCAL_SERVICE for writing/reading debug logs?
0 0 2297
QuestionThe FNP v11.14.0 Release Notes say....In FlexNet Publisher 2015 (11.13.1), a change was made to run Windows license server services withLocalService privilege instead of LocalSystem privilege, following the least-privilege security best pract...
ERROR: flxActCommonLicSpcAddASRs - (50050,71564,0)
0 0 537
QuestionERROR: flxActCommonLicSpcAddASRs - (50050,71564,0) is returned on virtual machine when checking ASR license.AnswerBelow is copied from FlxActError.h.#define LM_TS_VIRTUALIZATION_POLICY_MISMATCH 50050 /* The ASR being used for local activat...
Module machine type 'X86' conflicts with target machine type 'x64'
0 0 338
SummaryThe error 'Module machine type 'X86' conflicts with target machine type 'x64'' experienced when building a 64 bit application/toolkit is normally due to using the wrong build environment. This can be resolved by opening a command prompt simila...