Summary Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a service Question With FlexNet Publisher 2015 (11.13.1), if you install lmadmin on a 64bit Windows system under "Program Files (x86)" folder (since it's a 32bit program), and then try installing it as a service, there is returned the following error "System error 1067 has occurred. The process terminated unexpectedly." If you install lmadmin directly under "C:\lmadmin" then you don't get that error. Why? Answer This is a permissions issue, tracked as FNP-11155. To work around it, the folder permission of the "lmadmin" folder needs to be changed to "Full control" for all users of the Windows system that is being used. Once this workaround is applied, the lmadmin service starts up successfully. Additional Information If you use our lmadmin installer to install lmadmin, then the installer ensures the directory its installed to receives the correct permissions. In 11.13.1 we made the important change to run lmadmin with least privilege, per issue FNP-10475 (please see the release notes for details). The pattern is that one-time operations that require elevated privilege should be done an installer. If using trusted storage, you need the FlexNet Licensing Service. Our best practice is to install the FlexNet Licensing Service first, and then have lmadmin 'run as administrator' when it installs itself as a service. The above error should not occur in this case. ... View more

Summary Is there an API that can get the time each user of a feature acquired the license? Question We're trying to figure out how to get the time each use of a feature actually acquired the license. When they have a feature, the users consuming that feature's license are returned from the line below: users = lc_userlist(lm_job, feature); This is a list of structures of type LM_USERS which has a member time. This timestamp would be helpful for reports if it is the time the particular user checked out the license. However, it appears the value of the timestamp is basically unpredictable and there doesn't appear to be any documentation regarding what it really is. We're interested in the time each particular user of a feature acquired the license to that feature from the server. Can we get it from the lc_userlist? If not, any other API? Does LM_A_VD_GENERIC_INFO provide the information we require? Please note, this detail is available via LMTools under Server Status-> Individual Feature -> Perform Status Enquiry. Answer You can get the desired information using the below code snippet. users = lc_userlist(lm_job, feature); printf("Start time = %s", ctime(&users->next->time)); printf("Feature = %s\n", feature); printf("User = %s\n", users->next->name); Additional Information The list of users returned by lc_userlist() includes a special record, indicated by an empty user name (name[0]==0), which contains the total number of licenses supported by the daemon for the specified feature (in the nlic field), and the daemon?s idea of the current time (in the time field). To obtain the vendor daemon?s current time you have to specifically reference that special record. For example: users = lc_userlist(lm_job, feature); while (users) { if (users->time != 0 && users->name[0] != 0) { printf("%s, %s, %ld\n", users->name, users->node); time (&rawtime); t = localtime (&rawtime); strftime(buffer, 80, "Checkout time: %I:%M%p\n", t); puts (buffer); } users=users->next; } Also, you can obtain the timestamp using LM_A_VD_GENERIC_INFO, for example: c = (CONFIG *)0; for (conf = lc_next_conf(lm_job, feature, &c);conf; conf=lc_next_conf(lm_job, feature, &c)) { gi.feat = conf; if (lc_get_attr(lm_job, LM_A_VD_GENERIC_INFO, (short *)&gi)) { lc_perror(lm_job, "LM_A_VD_GENERIC_INFO"); } else { server_time = gi.server_current_time; t = localtime(&server_time); printf("License was checked out at %d:%d:%d\n", t->tm_hour, t->tm_min, t->tm_sec); } } ... View more

Summary Why does setting LM_A_VENDOR_ID_DECLARE after a checkout fail with a -5 error? Question Why does setting LM_A_VENDOR_ID_DECLARE after a checkout fail with a -5 error? Answer The job license refresh is part of LM_A_VENDOR_ID_DECLARE and a few other attribute (e.g. LM_A_DISABLE_ENV). If test checkout is moved after LM_A_VENDOR_ID_DECLARE attribute setting both checkouts are successful (LM_A_VENDOR_ID_DECLARE is being set. test checkout out of f1 ... SUCCESS. f1 checked out...) The failure is not limited to test checkout alone and it holds good with any checkout (f1 checked out...LM_A_VENDOR_ID_DECLARE is being set., (-5, 414) error). To avoid this, set LM_A_VENDOR_ID_DECLARE before doing any checkouts. Additional Information For example: lmflex (LM_A_VENDOR_ID_DECLARE is not set) 1.Test_checkout (f1) <<<=== connection is made here, job has a valid socket, job->daemon->server is populated in connection) 2.// lc_set_attr(LM_A_VENDOR_ID_DECLARE) <<<==== this attribute is not set 3.Regular checkout (f1) <<<=== Uses the same connection from first checkout because server conf->server and job->daemon->server (populated in connection) are same. 4.So, subsequent checkouts are successful. Lmflex 1 ==> (LM_A_VENDOR_ID_DECLARE is SET) 1.Test_checkout (f1) <<<=== connection is made here, job has a valid socket, job->daemon->server is populated in connection) 2.lc_set_attr(LM_A_VENDOR_ID_DECLARE) <<<=== this attribute is set <<<=== the attribute makes the job license to be refreshed so job->daemon->socket is released as part of this <<<=== the job->socket is still retained 3.Regular checkout () <<<=== Since conf->server and job->daemon->server (is null now) are not same, try to attempt a new connection but this job already has a valid connection the connection routine fails with -5. ... View more

Summary Why is FUSE required with FNP 11.14.1.1 install_fnp.sh on Linux? Question We noticed that the FNP 11.14.1.1 install_fnp.sh script on Linux errors out if FUSE support is not detected. Have the requirements here changed between 11.13.0 and 11.14.1.1? It appears that licensing works with and without FUSE on both versions. Answer The FUSE component, which is typically present on supported RHEL and SLES distributions, has provided Activation Secure File Anchors since FNP 11.11.1. (Some customers have managed to run Activation applications with them, but it's not recommended.) FNP 11.14.1 introduced the FNP Licensing Service Daemon (see Release Notes) to provide fast access to VM detection results and potentially, in the future, other system related information. It is now a requirement that the FUSE subsystem is installed and correctly running on the host machine in order to run the FNP Licensing Service daemon. FNP 11.14.1.1's install_fnp.sh script was modified to notify if it isn't to help enforce this new requirement. Additional Information To install FUSE onto an RHEL/Centos machine, run the following command as root (or with sudo): $ yum install fuse-devel fuse-libs fuse gvfs-fuse For SLES the command will be: $ apt-get install fuse-devel fuse-libs fuse gvfs-fuse On older RHEL & SLES systems, you might also need to run (as root/sudo): $ modprobe fuse ... View more

Summary Where is the logfile created if none is specified within lmtools? Question When you open FNP 11.14.1 lmtools on Windows, the Config Services tab | "Path to the debug log file" entry contains a default entry of C:\ProgramData\FNP_DIR\debug.log Is that the location where the default logfile is created? I.e., if that field is emptied, where will the logfile be created for lmtools? Answer The default location is ?C:\ProgramData\FNP_DIR\debug.log? where the log file will be created. However, if the log file location is made NULL (i.e. empty by someone intentionally removing the contents of that field), Lmtools will throw a warning dialog box and in this case, "no" log file will be created and server will start up (on Start Server) without a log file. Please be advised that this default location will change starting with FNP 11.15.0.0 to ?C:\ProgramData\FLEXlm\lmgrd\debug.log? ... View more

Summary Does FlexNet Publisher provide a Java obfuscator? Question Is there a tool similar to the FlexNet preptool for C/C++ in the FlexNet Java toolkit that would obsfucate symbols? Answer You need to run your Java application and components through an obfuscator to avoid symbol collisions (as well as add a layer of security). The lmstrip utility is available for our C/C++ toolkit, but FlexNet Publisher does not include a built-in tool for obfuscating the Java binary's symbols. My understanding is we don't provide one because there are so many obfuscators already available. ... View more

Summary Can you lmstrip a shared object? Question I'm trying to run the 'lmstrip' utility on a shared object and unfortunately I get the following message: "error: parsing ELF OBJECT xyz.so: can not obfuscate object with a dynamic section." Is there a way for lmstrip utility to work on shared objects? We'd rather have it work than spend the time making our project build a static library. Answer Unfortunately, as indicated in the Development Environment Guide (under "Securing the Object Library), lmstrip for UNIX (ELF Platforms) only supports stripping static libraries that included external FlexNet Publisher Licensing symbols. ... View more

Summary Has there been any changes between FNP 11.9 and 11.13 in terms of attribute LM_A_CHECKOUT_DATA? Question With FlexNet Publisher (FNP) 11.9, the lc_set_attr() attribute LM_A_CHECKOUT_DATA data would show up in the vendor log. With current versions of FNP, that doesn't appear to be the case. For example, the following is a snippet from an FNP 11.13 vendor log file. 10:15:24 (demo) OUT: "demoONE" user@MYCOMPUTER (5 licenses) 10:15:24 (demo) Acquired 5 licenses for Group demoONE (Users View) 10:16:03 (demo) OUT: "demoONE" user@MYCOMPUTER (2 licenses) 10:16:03 (demo) Acquired 2 licenses for Group demoONE (Users Users Product) 10:16:04 (demo) IN: "demoONE" user@MYCOMPUTER (2 licenses) 10:16:42 (demo) IN: "demoONE" user@MYCOMPUTER (5 licenses) Whereas the following is a similar snipped from an FNP 11.9 vendor log file. 10:27:36 (demo) OUT: "demoONE" user@MYCOMPUTER [demoONE:USERS_VIEW] (5 licenses) 10:27:36 (demo) Acquired 5 licenses for Group demoONE (Users View) 10:28:00 (demo) OUT: "demoONE" user@MYCOMPUTER [demoONE:Other_Product] (2 licenses) 10:28:00 (demo) Acquired 2 licenses for Group demoONE (Users Users Product) 10:28:01 (demo) IN: "demoONE" user@MYCOMPUTER [demoONE:Other_Product] (2 licenses) 10:28:11 (demo) IN: "demoONE" user@MYCOMPUTER [demoONE:USERS_VIEW] (5 licenses) In FNP 11.9, the [GROUP:FEATURE] info is listed in the line with the OUT/IN start. Is this configurable? Answer You just need to configure this with your build. Please check the customization attribute ls_show_vendor_def. Here's a debug log snippet from a configured FNP 11.14.1 vendor daemon: 10:24:34 (demo) OUT: "f1" user@MYCOMPUTER [CKOUT-DATA-1] (2 licenses) 10:24:34 (demo) OUT: "f1" user@MYCOMPUTER [CKOUT-DATA-2] (2 licenses) ... View more

Summary Detecting HASP or WIBU flexid may take more than 30 seconds per request Question We're using FNP 2016 R2 SP1 on Windows and run our software in a closed network environment behind a restrictive firewall. We noticed that, under certain circumstances, the lmhostid tool can take a long time (up to 30 seconds or longer) to detect a FLEX9 or Wibu dongle. After troubleshooting the problem and checking the network logs, we noticed that lmhostid sends requests to an external website. The DNS is owned by a known corporation and is used as an OCSP endpoint and appears to be a part of PKIX infrastructure to check for the validity of code signing certificates. Is this something FNP controls? Answer FNP uses dynamic linking to dongles, which means that for both SafeNet and Wibu there is user space shared object that needs to be present ? haspsrm_win32/64.dll in the case of SafeNet. That dll is digitally signed. To prevent spoofing, we do an explicit check of the digital signature. ... View more

Summary FlexNet Publisher 2015 Security Update 1 (11.13.1.2) Release Notes Synopsis Below 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 KnowledgeBase Article search return results. Discussion FlexNet Publisher 2015 Security Update 1 (11.13.1.2) Release Notes November 2015 Overview....................................................................................................................................................... 2 Resolved Issues in FlexNet Publisher 2015 Security Update 1 (11.13.1.2) ........................................... 2 New Features and Enhancements in FlexNet Publisher 2015 Service Pack 1 (11.13.1.1) ................... 3 Resolved Issues in FlexNet Publisher 2015 Service Pack 1 (11.13.1.1) ................................................. 5 General Issues .............................................................................................................................................................5 lmadmin Issues ...........................................................................................................................................................7 Virtualization detection updates for 11.13.1.1 .......................................................................................................7 Known Issues in FlexNet Publisher 2015 Security Update 1 (11.13.1.2)............................................... 8 Supported Platforms.................................................................................................................................10 Platform Notes ........................................................................................................................................................ 10 Legal Information......................................................................................................................................11 ... View more

Summary Is there a public API available to obtain the license file and/or options file location from the vendor daemon? Question Is there a public API available to obtain the license file and/or options file location from the vendor daemon? Answer There is no current public API available to obtain the license file and/or options file location from the vendor daemon. Additional Information Producer may opt to use environment variables, but this adds a collection of maintenance issues that they would much like to avoid, as things break if a customer decides to make changes via lmtools instead of the producer's ones. Enhancement request FNP-18795 was filed petitioning to include such an API with a future release of FNP. ... View more

Summary What would happen if the trusted configuration file was missing during the build? Question Can a trusted storage (TS) enabled exe be build without a trusted configuration file? What would happen if the trusted configuration file was missing during the build? Answer Preptool will report an error if the file is missing... Unable to open the trusted config file : 'publisher\DemoTrustedConfigOutXXX.xml' XML FATAL ERROR: parsing aborted at line 4 XML parse of configuration file failed. NMAKE : fatal error U1077: '.\preptool.exe' : return code '0x1' Stop. Or if it is for the wrong publisher (e.g. not changed from "Demo" when building with production keys)... Trusted config procesing failed : 'publisher\DemoTrustedConfigOut.xml : PublisherId in trusted config does not match that in activation settings XML FATAL ERROR: parsing aborted at line 4 XML parse of configuration file failed. NMAKE : fatal error U1077: '.\preptool.exe' : return code '0x1' Stop. ... View more

Summary Explanation of swidtag file with lmadmin installer Question The lmadmin installer on both Windows and Linux installs the file 'README-swidtag-lmadmin.txt' to the installed directory. The file describes creating a directory and moving the included *.swidtag file to that directory. These instructions are not found in the FlexNet Publisher Doc library nor indicated by the installer on either Windows or Linux platforms. Our lmadmin installation instructions to our users had included instructions to configure the *.swidtag file on the Linux platform, but not the Windows platform...and our Windows users have not experienced any problems. So here are my questions: 1) What is the purpose of the swidtag file? 2) Is the swidtag file configuration still relevant? 3) What is the effect of configuring or not configuring the swidtag file as instructed? Answer Please find the answers to your questions below... 1) What is the purpose of the swidtag file? Answer: Organization that use a software asset management tool are able to recognized software asset inventory by parsing the software tag identify by the vendor. These software tags are industry set standard to identify software components. 2) Is the swidtag file configuration still relevant? Answer: If you're using tools that use software asset management, then yes. Otherwise, no. 3) What is the effect of configuring or not configuring the swidtag file as instructed? Answer: None. This is solely for software asset management. ... View more

Summary Why can't older clients check-out licenses borrowed by newer clients? Question Did 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 server (also reproduced with 11.14.0.1) and borrowed a license using and 11.14.0.1 client. Then when off the network I tried to use an 11.13.1.3 client (which used a checkout version lower than the one used to borrow), but the checkout failed. I can use an 11.14.0.1 client with a lower checkout version and use the borrowed key, so it seems like a version issue between 11.13 and 11.14. When building my vendor daemon I?m adding -bfixed to the lmnewgen call, so this is supposed to work. Answer Your version of lmcrypt is actually quite old, so there is no version issue here. FNP 11.14.0 changed options available for borrow format of the data that is written in the registry (the key name now has the version number in it). Because of this, the old clients can't read this properly. If you remove the version from the name, the older clients work. ... View more

Summary FlexNet Publisher 2015 SP1 (11.13.1.1) Release Notes Synopsis Below are the Table of Contents from the attached FlexNet Publisher 2015 SP1 (11.13.1.1) Release Notes. This is meant to act as a reference for KnowledgeBase Article search return results. Discussion FlexNet Publisher 2015 Service Pack 1 (11.13.1.1) Release Notes_Rev0 October 2015 Overview....................................................................................................................................................... 2 New Features and Enhancements.............................................................................................................................2 Resolved Issues in FlexNet Publisher 2015 Service Pack 1 (11.13.1.1) ................................................. 4 General Issues .............................................................................................................................................................4 lmadmin Issues ...........................................................................................................................................................6 Virtualization detection updates for 11.13.1.1 .......................................................................................................6 Known Issues in FlexNet Publisher 2015 Service Pack 1 (11.13.1.1) .................................................... 7 Supported Platforms................................................................................................................................... 8 Platform Notes ...........................................................................................................................................................8 Legal Information........................................................................................................................................ 9 ... View more