Hi, From the elease documents, i am not sure if VS 2015 is a supported compiler for FNP 11.14.1.1. Moreover in VS2010 - VS2012 - VS2015 there have been some fundamental changes (like location of header files and all..). So i would recommend using a supported VS compiler, for starter VS 2010 and check if build is fine. Regards, AP ... View more

I believe 'Paul Catalano' is already in touch with you. Isn't it the case? Regards, AP ... View more

Hi Bastian, My confusion here is whether the attempt is to do activation borrow or normal certificate side borrow? Reason of confusion is that, a duration of value 4380 = 1 year, such a long value can't be given for certificate borrow. So it must be an activation borrow. But, for activation borrow no registry entry is created. By any means have you been doing an activation borrow of a feature and normal borrow of another and both? Regards, AP ... View more

It looks like this is a redundant server (3 server) setup. And from the lmstat output it seems that either server is down or the specific unix system is not able to connect to the primary server here. You may try with a simple ping and check if the primary server is reachable from the problematic system here. If yes, then try with "lmstat -a -c 27018@dldeffmimp05lic,27018@dldeffmimp06lic,27018@dldeffmimp07lic" (check for the comma or semi comma in between the port@host combinations). ... View more

This could be a case of clients not able to communicate outside the network. Insure that's not the case by simply pinging the triad systems from each client (from different zones). Also insure that you are setting the license path as in designated structure for 3 server (something like port1@host1,port2@host2,poprt3@host3). This varies in case of windows and non windows. Please refer to the document, which kind of elaborates in a much better way. (helped me in past) ... View more

HI There, I believe you got confused in between BORROW and LINGER functionalities. BORROW: With this particular keyword in your licensing rights (license file), you can borrow a license from server and return it when client wishes (only if early borrow return is supported by server - through lsvendor.c) In borrow, a borrow cache is ceeated at server system as well as on client (look into the document for the locations of those files). LINGER: This functionality allows the licenses to be checked out from a particular client, even after checkin. So, unless and untill the duration is over, it can't be returned. In case of LINGER only server side borrow cache is created. So, (its a kind of hack) if you have the server hosted locally, then go to the server borrow cache location and delete the file. Restart the server. It should solve your issue. A word of advise though, only use LINGER in case of applications which take no more than 60 seconds to complete. Regards, Abhay ... View more

Hi, I believe FNP kind of always supported the conventional Ethernet interface names i.e. eth(0) to eth(9). Starting FNP 11.11 (Ladakh) release, it also started supporting non-conventional ethernet interface names (for ex: eth_pc1, nan_phys ... etc). Be advised that there were few bugs as well in FNP 11.11 (in regards to the interface hostid detection behavior), which were resolved in later releases. Regards, Abhay ... View more

Probably you mean about the diskless network, where we can either have a dedicated network storage or router storage , which means that each client doesn't have its own disk volume but shares (or not) a networked storage which boot through PXE. From my experiance, i havn't seen any notifications from Flexera about this. But i believe a carefully choosen licensing model should work with FNP and diskless environment. Howover the DISK_SER_NUM is used only in case to distinguish in between different clients, (becasue VSN are supposed to be unique). I am not sure how would using this particular attribute will help you. You might wanna try with either IP address or FQDN. Regards, Abhay ... View more

Hi ndphuong, just noticed another query from you regarding "bootroom" setup. Where we don't have an actual hard disk on clients. Are you observing the reported behavior in same setup? Regards, Abhay ... View more

HI, Since the API lc_hosid provided with argument as "DISK_SERIAL_NUM" has been conventionally providing me with the (VSN) or say hard disk serial number. So, it would be interesting to know the environment in which you can observe this error. What's the FNP API version? Also what's the environment (OS, VM/physical), if possible can you share the snippet of code ran which provides the similar outputs on 2 different systems? Regards, Abhay ... View more

Try adding the entries over server and clients systems (etc/hosts file) with FQDN or IP address. ... View more

Hi Vasanth, Although the status 5 has generally been an indicator of communication error. So, you might want to double check if publisher executable (nilm in your case) follows few basic to do's: - nlim version is >= lmgrd (licensing server executable) version - if path is in use for the publisher executable (nilm) i.e. in the licensing rights file along with "VENDOR nilm ", path is also given, the executable exists at that path. if all is well, then what lead to this error in your environment would help to make some more recommendations. Regards, Abhay ... View more

Hi, i am not sure if daemon service runner can be node locked, but from the examples which i have used, we can node lock the license server itself to a specific IP address. (i believe when you say daemon service runner, you meant vendor daemon/publisher daemon/). In fact lmgrd(license sever manager) is the one that forks the daemon runner, so if we node lock the license server runner, it should solve the issue here. Example: the server line in the license file should look like "SERVER ANY " Where syntax is "SERVER host hostid [port] [PRIMARY_IS_MASTER] [HEARTBEAT_INTERVAL=seconds]" ... View more

HI, since the query is old so probably an answer is not of that importance, but what generally i do is to refer to the FlexNet Release Documents and search for the supported environments section. It details on what can be used where. ... View more

I believe that you are using the licensing administrator console (AKA Lmadmin). If so, then historically this error code has always been there, if we have the PORT number specified in licensing file. Only way out looks to be to remove the PORT number from license file,. It's probably some kind of "avoid catch 22 situation -- according to older posts"... If we really want to change the port number, then remove the port number from license file and import it from GUI. Then you can set the port number in Server configuration tab. This will take into effect after restart of Server. ... View more