Mingw is yet not a supported compiler and no there is no plan to add it to the list of supported compilers - just yet. Having said that in past, i have seen publishers building FNP toolkit for cross compilation using mingw. It was a hectic process TBH, but it is possible to build the FNP toolkit using mingw compiler - post few tweaks in makefile and compiler setting changes. ... View more

Absolutely. There is a list of supported virtualization platforms available with each FNP toolkit release notes. For example in the latest FNP-11.16.4 release. the list is as: Google cloud, Azure, Amazon EC2, VMware ESXi 6.5 and 6.7, Citrix XenServer 7.6 and 8.0, VMware Workstation 14.1.1, Oracle VirtualBox 5.2.18, PARALLELS, QEMU_KVM   ... View more

Hi There, You can set this attribute in client application code (for example lmflex.c), as: (void)lc_set_attr(lm_job, LM_A_PORT_HOST_PLUS, (LM_A_VAL_TYPE)1); Post which you can make other API queries like "lc_feat_list" OR "lc_next_conf" - to get the authenticated info from license server. Kindly be advised that if using this attribute in client application, the license file must have the USE_SERVER keyword.   Client code example: ================ lc_set_attr(lm_job, LM_A_PORT_HOST_PLUS, (LM_A_VAL_TYPE)1); (void) lc_set_attr(lm_job, LM_A_LICENSE_DEFAULT, (LM_A_VAL_TYPE)"@localhost"); for (feats = lc_feat_list(lm_job, LM_FLIST_ALL_FILES, NULL); feats && *feats; feats++) { ret = lc_checkout(lm_job, *feats, "1.0", 1, LM_CO_NOWAIT, &code, LM_DUP_NONE); if (ret == 0) { pos = 0; conf = 0; while (conf = lc_next_conf(lm_job, *feats, &pos)) { printf("Feature: %s\n", conf->feature); printf(" Package Mask: %#x\n", conf->package_mask); } lc_checkin(lm_job, *feats, 1); } //else { printf("Feature: %s (CHECKOUT FAILED: %d)\n", *feats, ret); } } ====================================== Hope it helps. ... View more

Can you check the license search path set on those systems? An output of "lmutil.exe lmpath -status" . If there are multiple paths set then insure they are separated by ","?  ... View more

Can you share the exact error that you are observing on the Mac? ... View more

I am afraid that based on past interactions the support for dockers/Kubernetes is neither available nor in any immediate plans. ... View more

On the top (middle of the page) in your community login, you should see a drop down option as "Get Support". Click on that and choose "open a new case". Kindly set the product as "Flexnet Publisher" and appropriate version against it (the one in use at your end). Also, kindly provide the tsf files for further analysis. ... View more

It would a good place to start -  lmgrd log and also the error that you are seeing on client, because of which a re authentication is needed. ... View more

There are couple of things that needs to be analysed here. For example, the Lmtools version in use is v11.5, which is no more supported. Also, by the version compatibility rule that FNP follows: ========== The rules about FlexNet Licensing component version compatibility are summarized as:• Version of lmutil/lmtools must be >= • Version of lmadmin (or lmgrd), which must be >=         Note • lmadmin can only be used with components with a version of 9.2 or later. • Version of vendor daemon, which must be >= • Version of the client library linked to the FlexEnabled application, which must be >= • Activation utility, which must be >= • Version of license file format ========== So, we need to confirm that the Lmtools version in use is greater than lmgrd as well as vendor daemon version. Over that, could you also elaborate on the issue that you are facing? ... View more

Hello,  The error SIGNAL 37 and the error of "Heartbeat timeout is 300 seconds. Elapsed time is 1615 seconds." means that vendor daemon was busy with other works (checkouts in this case i believe) and because of that it wasn't able to respond back to pre-checked out client as well no response to the server heartbeat response on time, which lead to this behavior.  In recent times, we have done some work with enhancing the server experience and the server performance up-gradation is in progress. That could help. ... View more

Could you share the error details that you are seeing on test machine? Also please confirm if you have followed the steps as advised in the product document? ... View more

There is a detailed document "Driver Installation Guide for Flexnet ID Dongles" - i have shared the same documentation library with you on this case. Kindly refer the same to install the dongle drivers. hasp_rt.exe is the SafeNet external license manager. ... View more

You would need to make sure that when using FNP-11.11.1.2 SDK, appropriate version of hasprt.exe and libraries are placed at the appropriate folder and the dongle library shared with FNP kit is installed. To specify the location of the FLEXID9 dongle library, Do one of the following: • Define the FlexNet environment variable FLEXID_LIBRARY_PATH to point to the location of the dongle shared object, haspsrm_win32.dll or haspsrm_win64.dll (depending on your architecture). • Manually copy the DLLs to the Windows installation System32 or SysWOW64 directory (depending on your architecture). The relevant DLLs should be copied to the folder: • On a 64-bit system, publishers using the x64_n6 kit should install haspsrm_win64.dll to %windir%/System32. • On a 64-bit system, publishers using the i86_n3 kit should install haspsrm_win32.dll to %windir%/SysWOW64. Can you confirm if you are using the above mentioned settings? If yes, then i would advise opening a support ticket for concerned team to look into this. ... View more

Answering this query through another thread. ... View more