Documentation

I need explicit directions for how to configure the Recovery First Failure and Second Failure settings for a Windows service I am installing. I have tried to follow the documentation provided for the Services settings, but have been unsuccessful. I need more specific instructions or an example. My service installs fine. I cannot set the Recovery settings for the service. 

As a user, I have been using the Express version for several years. Thus, I am new to the professional version and the options are a bit daunting.

My normal installs work great. No problem. I need to execute the "silent install" for my administrators.

I am performing a Basic MSI Install build using the resulting executable (setup.exe). I have studied the great documentation that is provided. Still, my experience testing the resulting installer in a VM shows the Silent switch is ignored. There is no log file (that is supposed to be there...) for me to view so something must be wrong.

What am I missing? I am hoping I am overlooking a simple thing.

Thanks for what ever help that can be provided.

I have successfully built and tested my vendor daemon on Linux. Now, I need to share it with customers so they can use the license without rebuilding it. I plan to provide:

Vendor daemon binary (<vendor>) 

License file (.lic) 

lmgrd

Could you confirm if these are the essential files? Also, are there any key steps, best practices, or documentation sections I should refer to for proper deployment on Linux?

Thanks!

Hi, I am currently doing a capacity test on the FlexNet Publisher 2024R1 server On-Premise Linux machine.

I submitted one checkout job every 2 seconds and each job I intentionally put it to sleep for 2 hours (PS: On the client side of code due to business needs, the socket connection to the server is made long-lived. It means that the socket connection are kept open during the entire life cycle of a job. Here, the connection is kept open for 2 hours). The result is that, after submitting ~1000 jobs I started to receive these error messages from the server:

Failed to obtain license for feature ***, version ***, status: -15, reason: Cannot connect to server

Failed to obtain license for feature ***, version ***, status: -16, reason: Cannot read from server

Failed to obtain license for feature ***, version ***, status: -5, reason: No such feature exists (Not expected since checkout successfully below ~1000 jobs)

Failed to obtain license for feature ***, version ***, status: -139, reason: a timeout has occured

Based on the FNP documentation(2024R1, Page 121), it seems that both the lmgrd and the vendor daemon are overwhelmed. However, the documentation also said, the max default connection limit of lmgrd is 1000, but the max connection limit of vendor daemon is 10,000.

I've checked `ulimit -n` is 8192.

So I have 2 questions here:

1. If the server keeps as default configuration, is the capacity limit ~1000 expected due to the long-lived socket connections?

2. Is there a way to adjust the server's configuration in order to reach the 10,000 max concurrent connections as stated in the Documentation (or even as high as 120k showed in recent Webinar slides below)?

Thank you!

I am working on setting up a vendor daemon for a 64-bit Linux CLI-based machine using FlexNet Publisher. Currently, I am referring to the fnp_devenv.pdf documentation, but most of the steps seem to be focused on GUI-based environments.

Can I follow the same steps for a CLI-based setup just by converting GUI actions to CLI commands?

Upgrade code and ProductCode is the same.

Package code is different.

Each key file for each component has a later version number than the installed version.

According to all documentation this is enough for files to be overwritten during a small update. Any ideas as to what could be wrong ?