there seems more to the issue here. Probably a formal support ticket would be the best way to get Flexera Engineering people involved. Regards, Abhay ... View more

Hi I believe the default FNP toolkit comes with compiler options for "-fpic" defined as "CFLAGS". You can use the CFLAGS during compiler time (through makefile) and get the pic version for object files. Regards, Abhay ... View more

Just a word of caution. Insure the bit version (32 bit or 64 bit), as it creates some problems (based on previous experience in the forum) Regards, Abhay ... View more

Hello Eric, Error "-5" is LM_NOFEATURE . It seems either the feature you are requesting is not being served by the server. Can you check again? Also, when you mentioned "" - did you mean LM_SEEDs and LM_STRENTGH? If so, then it won't work. This is like a catch 22 , in which if you choose adding the TRL or changing the seeds/LM_STRANGTH (to add more security), we loose the backward compatibility. There is a section in document advising about it. If a TRL-enabled application attempts either to communicate with a non-TRL vendor daemon or to authenticate a non-TRL license, an error message is displayed and the application does not run. The error message informs you that either the license file and/or the vendor daemon is not TRL compliant. It’s important to remember that the TRL application itself is the trigger that requires both TRL licenses and a TRL-enabled vendor daemon in order to run. If your previous FlexNet Publisher toolkit (that includes client application, vendor daemon and license generation tool) was built with LM_STRENGTH set to LM_STRENGTH_DEFAULT ( in machind/lm_code.h), then it is not possible to upgrade to TRL. The upgraded server and the licenses will not work with older clients that were built with LM_STRENGTH_DEFAULT. If your previous toolkit was built with LM_STRENGTH set to LM_STRENGTH_LICENSE_KEY, you can perform a partial migration which maintains backward compatibility with older clients. In document "FNP_Programming Referance for License File based Licensing.pdf", the chapter -9 " License Signature Configurations" talks in details about it. Please refer to Table-9.1 and the following details (Added the document library with this chat page). It should help, if not just revert back. Regards, Abhay ... View more

Hi Eric, The reported behavior is expected, because we have changed the way clients were SIGNED (using older lm_code.h - i believe a different VENDOR_KEYS and you may also have played a bit with LM_STRENGTH/TRL keys value)) and 11.16 server (where you have bought support for Linux (so i suspecting the lm_code.h) files to be changed. As a thumb rule (all information related with lm_code.h): If LM_STRENGTH and LM_SEEDS values are same (between client and server lm_code.h files), then communication in between server (built with new VENDOR_KEYS and TRL keys) and Client application (built with old VENDOR_KEYS and TRL_KEYS) should not be an issue. If LM_SEED s are changed : Error -33,376 : Bad Encryption handshake with vendor daemon. if LM_STRENGTH is changed: Error -8,544: Invalid (inconsistent) license key. Regards, Abhay ... View more

The limitation of considering only 10 Ethernet ID's are still very much relevant. In FNP-11.12.1.2 , an issue over OS X was fixed (a crash in case of having more than 10 Ethernet adapters). Regards, Abhay ... View more

Hi, The concerned product in query is not a Flexera Product but it belongs to "OutBack Powers". you may need to redirect your query in respective forum. Regards, AP ... View more

Hi, "FLEXnet insists on demanding a license for the Ethernet-connected NIC rather than the "dongle"." - Can you elaborate? What's the observation - error? Message box? Any error code? It looks like your Ethernet cable has taken a priority over the dongle NIC, hence when Flexlm code does an IP tagging, it finds the IP of Ethernet first and NIC later - Found first will be treated as the IP address of device (Networking). I believe your license is bound with NIC IP address, which doesn't take precedence over the Ethernet one. You can play with the priority of adapter(s) or manage who gets taken first by managing the "Automatic Metric" and prioritize the dongle NIC. I doubt if it has anything to do with the FlexLM. Regards, AP ... View more

Hi, I vaguely remember from past experiences that "51315" represented the "FLX_ACT_TRAN_ERR_RSP_REQUEST_UNTRUSTED" i.e. Can't invoke non-Config response actions when matching request UNTRUSTED Hope it helps. Regards, AP ... View more

Hi Connor, I believe '51315' is the minor error code here? Would you update the entire error code (major.minor.subminor)? Also, what action lead to that specific error? These info will help to confirm if anyone has been in the same boat. Regards, AP ... View more

That's absolutely correct. For security reasons (from direct attack on VD), lmgrd kind of acts like the cover unit, hence it is in best practice to keep both the ports open. And also share only the lmgrd port to the end users to connect and fetch the licenses. Regards, Abhay ... View more

Hi, lmgrd - the license manager as the name indicates has a major purpose to manage the license communication (along with other as well). When a client sends the communication handshake to lmgrd, in response lmgrd asks the client to try on another port to fetch the license (i.e. the VD port). Now in your case, you are directly accessing the VD port, hence the lmgrd channel is given a pass and checkout succeeds. This is an expected observation. Could you elaborate on what you meant by "If it is an expected one then can we avoid this feature rather than closing the port by firewall?" Regards, Abhay ... View more

Hi Quan , I believe Carmen Man should be in touch with you by now. If that's not the case, then kindly update. Regards, Abhay ... View more

Hi franco, I believe for multiple inputs, the concept of GROUP was added. But FNP only supports GROUP for user and host names. So it looks like having different INCLUDE statements is the only way to go. Regards, AP ... View more

In my personal experience, wild char characters have always worked for Flenet Publisher (may be not in old.. very old versions). You can create 2 different lines for the INCLUDE to allow different IP sub net for a feature INCLUDE list. Regards, AP ... View more