Summary This article will explain how to enable baddate checking. Synopsis There are two things that need to be done in order to enable the check baddate option to the vendor daemon and the flexnenabled client application. Discussion 1. Vendor Daemon: Change the value of ls_a_check_baddate variable form 0 to 1 from lsvendor.c. This file is located in the <platform>machind directory. 2. Flexenabled Application: +++ FLEXible API +++ (File-Based Licensing) Add LM_A_CHECK_BADDATE attribute to your application. i.e. lc_set_attr(lm_job, LM_A_CHECK_BADDATE, (LM_A_VAL_TYPE) 1); (Trusted Storage based Licensing) Add LM_TS_BADDATE attribute to your application. i.e. lc_set_attr(lm_job, LM_TS_BADDATE, (LM_A_VAL_TYPE) 1); After adding the attribute to the flexenabled application and changing the 'ls_a_check_baddate' variable; both vendor daemon and the flexenabled application will need to be rebuilt to enable these options. ... View more

Summary This article will answer the question, "can the FNP license server serve a flex enabled client application over DirectAccess?" Question Can the FlexNet Publisher license server serve a flex enabled client application over DirectAccess? Answer Whilst we do not explicitly test DirectAccess, we might reasonably expect FNP to work over a number of different VPN technologies. However, we would also argue that it is not feasible to test FNP with every VPN technology. We'd recommend to perform some tests and report any issues with (expected) FNP behaviour over the VPN. We have in the past fixed issues where the VPN has exposed an underlying generic bug in FNP. ... View more

Summary This article will explain what to do if 'lm_new.obj' is missing after building the Flexnet Publisher (FNP) toolkit. Synopsis If building the FNP toolkit and the 'lm_new.obj' doesn't seem to have been created then a 'veryclean' can be performed and a rebuild of the toolkit will create the 'lm_new.obj'. Discussion In order to perform a 'veryclean' and rebuild, please run the following in a Visual Studio* command prompt: nmake -f makefile veryclean then run: nmake -f makefile *Refer to the FNP Release Notes for what Visual Studio compilers are compatible with the FNP toolkit being used. ... View more

Summary This article will explain how to overcome the linker error "unresolved external symbol __imp_PathRemoveBackslashW". Symptoms When building the v11.13.1+ with a Visual Studio 2010 compiler, the following error is displayed: "mgr.lib(flex_file.obj) : error LNK2001: unresolved external symbol __imp_PathRemoveBackslashW" Cause This is caused by missing libraries during the build process. Resolution Add the following libraries to your build: psapi.lib Shlwapi.lib dhcpcsvc.lib ... View more

Summary This article will explain how to overcome the lmadmin startup error: "Could not open configuration file C: Program Files (x86)\\ /lmadmin/conf/httpd.conf: The system cannot find the path specified." when placing files that are user customised in the ProgramData folder. Symptoms When creating an lmadmin installer that has to be compliant with Windows 7 Client Software Logo installation guidelines, files that are user customised need to be placed in the ProgramData folder. This includes the "logs" and "conf" folders. However, when moving these files and running lmadmin with the "-logDir" and "-configDir" properties, these don't seem to be updating the server.xml file with the new locations, so lmadmin won't start manually or as a service, and in the "web.log" the following error is thrown: "lmadmin: Could not open configuration file C:Program Files (x86)\\<vendorName>lmadmin/conf/httpd.conf: The system cannot find the path specified." Cause Running lmadmin with the "-logDir" and "-configDir" properties, doesn't seem to be updating the server.xml file with the new locations, and lmadmin fails to start. Resolution The latest FlexNet Publisher toolkit release (v11.13.1.3) resolves this issue by introducing a new command-line option called "cacheDir". Example of use: lmadmin -cacheDir "C:\ProgramData\<vendorName>\lmadmin" ... View more

Summary This article will explain how to overcome the (-96,491) error when using the Flexnet Publisher v11.13.1 toolkit. Symptoms When trying to connect to a license server with a client built with the Flexnet Publisher v11.13.1 toolkit, and there is latency between the two, then a "License server machine is down or not responding. (-96,491)" error may be thrown. Cause This is caused due the changes with the FLEXLM_TIMEOUT that where introduced in v11.13.1. The timeout default value for FLEXLM_TIMEOUT was set to 100,000 (0.1 second). This caused a -96,491 error when there was latency within a network. Resolution To increase the FLEXLM_TIMEOUT value to greater than 100,000 microseconds (0.1 second), for example 1500000 microseconds (1.5 second). ... View more

Summary This article will explain how to overcome the error 'Vendor daemon can't talk to lmgrd (Cannot read data from license server system. (-16,287))' Symptoms When starting the license server the following error may be produced. 18:58:06 (flexera) Vendor daemon can't talk to lmgrd (Cannot read data from license server system. (-16,287)) 18:58:06 (flexera) EXITING DUE TO SIGNAL 28 Exit reason 5 18:58:08 (lmgrd) flexera exited with status 28 (Communications error) 18:58:08 (lmgrd) Since this is an unknown status, license server Cause This can be caused by using ports in the license file that are already in use. The license server (lmgrd/lmadmin) and the vendor daemon both use ports and can be specified in the license file. For example: SERVER this_host ANY 27005 VENDOR flexera PORT=27010 USE_SERVER FEATURE... Where 27005 in the license server port and 27010 is the vendor daemon port. Resolution Change the port numbers in the license file and restart the license server. ... View more

Summary How do you repair a trusted storage activation when it's in the **DISABLED** state? Synopsis How do you repair a trusted storage activation when it's in the **DISABLED** state? Discussion If a trusted storage license is in the **DISABLED** state then the reason could be that a manual return of the license has failed, thus placing it in the **DISABLED** state. To repair this the manual return will have to be cancelled and can be done using the following command: appactutil <fulfillmentID> -return -cancel What this does is cancel the return and will enable the license, i.e. take it out of the **DISABLED** state. ... View more

Summary When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different . Synopsis When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different . Discussion When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different - INCREMENT lines form license groups, called license pools, based on the following fields and keywords: ? Feature name ? Version ? BORROW ? DUP_GROUP ? FLOAT_OK ? HOST_BASED ? HOSTID ? PLATFORMS ? TZ ? USER_BASED ? VENDOR_STRING (if configured by the vendor as a pooling component) ? VM_PLATFORMS It should also be noted that this applies to INCREMENT lines only, the following sequence involving a FEATURE line will not work (with the VENDOR_STRING pooling enabled) - FEATURE f1 flexera 1.0 permanent 3 VENDOR_STRING=Type_1 SIGN=.... INCREMENT f1 flexera 1.0 permanent 1 VENDOR_STRING=Type_2 SIGN=.... Two INCREMENT lines are needed ... View more

Summary This article will answer the question, "What does the -s option mean for lmgrd?". Question We use your installs.exe in our install and the command line is reported in the log file to be the following: -c C:\Program Files\Siemens\PLMLicenseServer\splm7.lic -l C:\Program Files\Siemens\PLMLicenseServer\splm_ugslmd.log -z -s What does the "-s" for? Answer The -s option is basically for the logfile timestamp_interval in minutes. ... View more

Summary This article will explain why Java needs to be installed before running the lmadmin installer v11.15.0. Question Why does lmadmin need a Java to be installed to run? Answer This is an excerpt from the Release Notes for v11.15.0. lmadmin installer updates: In FlexNet Publisher 11.15.0, the lmadmin InstallAnywhere installer no longer bundles the JVM. As a consequence, for Windows, there is now only one lmadmin installer (previously there were two, one for 32-bit bundled JVM, one for 64-bit bundled JVM). (FNP-15969) On OS X, an error no longer occurs where the lmadmin installer prompts the user to install legacy Java software. Now, the lmadmin installer uses the FlexNet Publisher 2017 (11.15.0) Release Notes (November 2017) Company Confidential 11 JVM that is installed on the machine (OS X requires JVM 1.7 or later). To use a different JRE version while installing/uninstalling, the desired version can be specified using the LAX_VM command. (FNP-15913, FNP-16086, Salesforce case 01112990) ... View more

Summary The article will answer the question, "What version of FlexNet Publisher provides support for Visual Studio 2015?" Question What version of FlexNet Publisher provides support for Visual Studio 2015? Answer Visual Studio 2015 is now supported in FlexNet Publisher version 11.14.. There is also a Windows only hot fix to the 11.13.1 stream, 11.13.1.4, which provides VS2015 compatibility. With this release there is a new library that needs to be added to the link list 'libredir_std.lib' ... View more

Summary This article will explain how to allow a user other than root to run lmdown, lmreread and lmremove when the license server is started with -2 -p on a Linux machine. Synopsis On a Linux machine if the license server is started with the '-2 -p' options, this disables the use of lmdown, lmreread and lmremove commands to only the root user. Discussion In order for a non-root user to be able to use the lmdown, lmreread and lmremove commands, then they'll need to be added to a group called 'lmadmin'. Log in as a root user and run the following commands in a terminal to create a group and add a non-root user. [root@JMCENTOS]# groupadd lmadmin [root@JMCENTOS]# usermod joe -g lmadmin Once the user 'joe' is added to the lmadmin group, joe will be able to run the lmdown, lmreread and lmremove commands. ... View more

Summary This article will explain how to overcome the issue where the vendor daemon is unable to start after connecting to Cisco AnyConnect Secure Mobility Client VPN. Symptoms When starting the license server after connecting through a VPN using Cisco AnyConnect Secure Mobility Client the following error is displayed: 9:15:09 (lmgrd) Can't connect to the license server system. Shutdown flexera failed. 9:15:09 (lmgrd) Cannot connect to license server system. (-15,578:10049"WinSock: Invalid address") 9:15:09 (lmgrd) Can't shutdown the license server system. Shutdown flexera failed. 9:15:09 (lmgrd) EXITING DUE TO SIGNAL 2 Cause The problem appears to be that the Automatic Metric setting for the Cisco VPN connection (IPV4/IPV6) is set to a manual Interface Metric value of 1 instead of the Automatic metric checkbox enabled default. Since getaddrinfo on Windows prioritises interfaces with the smallest metric, this means FNP hostname resolution attempt will fail. Resolution Set the Automatic Metric setting for IPV4 and IPV6 Cisco VPN back to the Automatic metric checkbox enabled default, this should resolves the issue. To do this go to Control Panel\Network and Internet\Network Connections\Cisco AnyConnect Secure Mobility Client Connection 1. Right click and select properties. 2. Select IPv4 and properties. 3. Select Advanced.. button. 4. Check the Automatic Metric checkbox. 5. Repeat the steps for IPv6 as well. ... View more

Summary This article will answer the question, "How many reservation lists can the Local License Server manage?" Question How many reservation lists can the Local License Server manage? Answer Our engineering team have perform reservation test and 14050 reservation work fine. However, if they try to reserve 14051 they observed the error message: ?Error occurred: Please contact the administrator with the detailed steps to reproduce this issue.? At this point in time the Local License Server has a maximum of 14050 reservations. ... View more