Hi @yazhang , if you bought the license for Linux ARM64 then the same keys should work to build the kit. If not, please get in touch with your CSM or account manager so that they can assist you in acquiring the license for Linux ARM64.
... View more
Hi @BrennanT ,
Can you please remove the port values from the license file and later check if you are able to start the server? If this does not resolve the issue please raise a case for us so that we can get on a call and look into this. Regards, Yashwanth
... View more
Summary
FlexNet Publisher (FNP) 11.19.6.0 has been validated on macOS Sequoia with the latest Xcode through ATS and sanity executions.
The kit can be built by simply updating MAX_MAC_SUPPORTED_VERSION=24 in the makefile and makefile.act files. There are some known warnings with ld and ranlib for certain files during the build process, but these can be safely ignored. Overall, the results confirm the qualification of FNP 11.19.6.0 on macOS 15.
Steps to Build the Kit
To build the kit:
Extract the kit and update the lmcode.h file with the vendor keys, seeds, and TRL values.
Open the makefile (for the license file) or makefile.act (for trusted storage) and update the MAX_MAC_SUPPORTED_VERSION from 23 to 24.
Example Warnings
A few warnings related to ld and ranlib may appear during the build, but these can be ignored. Example warnings are:
ld: warning: no platform load command found in '<path>/libcrvs.a[x86_64][2](ec163a02.o)', assuming: macOS
ld: warning: no platform load command found in '<path>/libcrvs.a[x86_64][3](ec239a03.o)', assuming: macOS
ld: warning: no platform load command found in '<path>/libcrvs.a[x86_64][5](sect113r1.o)', assuming: macOS
/
clang: warning: argument unused during compilation: '-stdlib=libc++' [-Wunused-command-line-argument] lipo -create -o lmcode.o lmcode_x86_64.o lmcode_arm64.o rm lmcode_x86_64.o lmcode_arm64.o
... View more
Hi @vgresende80 , From the errors file shared it looks like you are using an OPT file with INCLUDE statements for the users who have access to the features and yours seems to be missing.
I would request you to check the OPT file and see if there is an entry for your USER if not please add and run lmreread or restart the server. That should solve the issue.
... View more
Hi @angel329623 , from the image shared I can see that it is the correct 11.19.6 version that is downloaded. Maybe you are getting confused with the hotfix number 2. There was a fix on the lmadmin side as a result the exe is named 11.19.6.2.
... View more
In your case, I do not think they signify any kind of info. But generally, when the check-outs check-ins are happening it does signify the last few request processing time.
... View more
Hi @jjardine , You can use the TZ option in the license file. TZ Syntax: TZ=[SERVERTZ | <[+-]hh<.30|.45><:[+-]hh<.30|.45>>>]
Enables you to enforce license usage for a feature relative to a time zone; where the time zone is specified and measured relative to Greenwich Mean Time (GMT). For more info on this please refer to page 137 of FNP_PF_LF.pdf from the attached doclib.
... View more
Hi @benFlex , If the license is being returned (checked-in) once the client application is closed then there will be no communication between the license server and the client.
... View more
Hi @npenneti , To use lmreported a special verbose logging is required to be enabled for the vendors. I do not think the mvsn vendor shared with IA/IS has that enabled as a result you will not be able to use lmreporter with the normal debug log.
... View more
HI @madaraszb ,
The -97 error is due to the server not being up and running. From the lmgrd log shared above, I see that the server has not started properly due to the non-availability of the feature on the server. This mostly looks like a License file issue. Do you see any INVALID/INCONSISTENCY error in the lmgrd log? If yes, can you please raise a support ticket and attach the complete lmgrd log so that we can look into it?
... View more
Hi Mike, Can you please raise a support ticket for this issue along with steps to replicate and screenshots of the issue so that I can look into it?
Thanks, Yashwanth
... View more
Summary
Customers experienced an issue with their application due to unsigned FNP DLLs in the latest release. They reported receiving the following error message in their logs when starting their application:
The digital signature of the Xalan-C_1_12.dll is not matching. Thus, the application cannot be started.
Symptoms
Upon investigation, it was discovered that in the most recent release, version 11.19.6, the following DLLs are not digitally signed:
Xalan-C_1_12.dll
XalanMessages_1_12.dll
xerces-c_3_2.dll
All prior versions of these DLLs were digitally signed, indicating a change in the latest release that is causing the application to fail to start due to mismatched digital signatures.
Fix Version and Resolution
We have a new 11.19.6.2 lmadmin kit available in the PLC for download, which includes the correctly signed DLLs. If you face this issue please download and use this updated version.
... View more
Hi, You can use the -f flag along with the feature name to query a certain feature.
Eg:
lmutil lmstat -c 29000@licserver -f <feature name>
... View more
Summary
There is an issue where using the LM_A_LINGER attribute on the client side, combined with the TIMEOUT/TIMEOUTALL option in the OPTIONS file on the server side, causes the Vendor Daemon to crash when the server reclaims the license due to the client's inactivity. This issue affects producers using FlexNet Publisher versions 11.19.4.1 up to 11.19.6.0. The article below provides details about the known issue and the available resolution.
Symptoms
End users may experience frequent license server crashes and attempts to restart if the vendor daemon is configured with the TIMEOUT/TIMEOUTALL option in the OPTIONS file and the client uses the LM_A_LINGER attribute to create a client-side linger.
Steps to Reproduce
The issue can be observed by following the steps below:
1. Update the value ls_minimum_user_timeout to 90 in lsvendor.c file and build the kit.
2. Create an options file and add TIMEOUTALL=130.
3. Start the server with below license file:
SERVER this_host ANY
VENDOR <vendor>
USE_SERVER
#a counted license
FEATURE f1 <vendor>1.0 permanent 4 SIGN="CCCCCC"
4. Edit the default lmflex.c file shared in the kit with the below config to create 3 different client applications:
#Client 1:
(void)lc_set_attr(lm_job, LM_A_LINGER, (LM_A_VAL_TYPE)700);
lc_set_attr(lm_job, LM_A_CHECK_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_COUNT, (LM_A_VAL_TYPE) -1);
#Client 2:
(void)lc_set_attr(lm_job, LM_A_LINGER, (LM_A_VAL_TYPE)600);
lc_set_attr(lm_job, LM_A_CHECK_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_COUNT, (LM_A_VAL_TYPE) -1);
#Client 3:
lc_set_attr(lm_job, LM_A_CHECK_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_INTERVAL, (LM_A_VAL_TYPE) -1);
lc_set_attr(lm_job, LM_A_RETRY_COUNT, (LM_A_VAL_TYPE) -1);
#...(Other code here)...
sleep(150);
getchar();
lc_checkin(lm_job, feature, 0);
5. When the clients are created, run the clients in the following order a -> b -> c and maintain a 1-minute gap between each client checkout.
6. A crash will occur when the server reclaims the license due to client inactivity:
21:52:58 (YYYY) OUT: "f1" zzzz@aaaa
21:53:34 (YYYY) OUT: "f1" zzzz@aaaa
21:53:54 (YYYY) OUT: "f1" zzzz@aaaa
21:56:58 (YYYY) IN: "f1" zzzz@aaaa (INACTIVE)
21:56:58 (lmgrd) YYYY exited with status 5 signal = bbbb
21:56:58 (lmgrd) Since this is an unknown status, license server
21:56:58 (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.
21:56:58 (lmgrd) REStarted YYYY (pid XXXX)
21:56:58 (YYYY) FlexNet Licensing version v11.19.6.0 x64_n6
Fix Version and Resolution
A fix for this issue is available as a hotfix in FlexNet Publisher 11.19.6.1. If the issue is being observed, please contact Revenera Technical Support for assistance with accessing the hotfix. The fix will be incorporated in the FlexNet Publisher 2024 R2 (11.19.7.0) GA release targeted for December 2024.
... View more
