In fact, deactivation of previous version (2024R2) is not possible due to "maximum number of returns is reached", according to the error message.We would really like to upgrade from 2024R2 version to 2025R1 in order to take advantage of the new features. Our licence is valid until December 2025, so it should be possible to upgrade.

What can i do to fix this problem ?

Thank you for help.

Hi Community,

I'm working with an InstallShield 2024 R2 project that uses chained .msi packages. In the Release > chained .msi > Packages view, I'm passing several properties to the child MSIs using the Installshield Property Manager field.

Properties are passed as chained ism in following way.

Example : Main application Installer (Main.ism) -> Installer1.ism (Where the properties are passed)

Main application Installer (Main.ism) -> Installer2.ism (Where the properties are passed)

Some of these properties are sensitive, such as passwords. However, I’ve noticed that these values are being logged in plain text in the installer MSI logs, which is a security concern.

What I’ve Tried:

I’ve defined the sensitive properties in the Installer1.ism & Installer2.ism Property Table.

I’ve added those property names to the SecureCustomProperties and MSIHiddenProperties property in the Installer1.ism & Installer2.ism

Despite this, the values still appear in the install logs when I run the installer.

My Questions:

Is there a reliable way to prevent sensitive properties passed through chain installer from being logged?

Any examples would be greatly appreciated!

Thanks!

We are using Flexnet publisher 11.19.6 for Java SDK. 

To access the trusted storage from a Java based application, we have to put the mandatory dll files for native access to the trusted storage into the working directory.

Loading the dll files is NOT the problem. 

They are properly found and loaded. 

But when checking out a feature, then we get the following result:

Error List Returned (-513,7) ; Native Method Call Failed (-530,3103) (tsGetFeatureLines: flxInitLoad failed.: 1); Error List Returned (-513,4050)

We already tried to change the current working directory to the folder containing the dlls. 

Then the checkout works properly.

However this is not suitable for our Eclipse RCP based Java Application.

Is there a way to tell the Flexnet SDK for Java applications, that the dlls are in a certain location?

Or get it somehow else to work?

Several end users of our FNE XT protected software on Windows 10 have reported being unable to activate licenses since the Feb 4th certificate update. We are able to resolve by instructing customers to manually install AWS trust certificates on their affected machines, however, the situation is far from ideal.

I wonder if anyone else has experienced this. Does anyone have in-depth knowledge as to why some client machines (not all) would not automatically get the required certificates in the chain?

The required certificates can be found here

https://community.revenera.com/s/article/FlexNet-Operations-SSL-Certificates