How to provide a License Configuration file when deploying the Client Networking MSI

After installing the OpenEdge Client Networking MSI Package, any client executable or batch file fails with error "The license for the client executable has expired. (4399)"

Oct 8, 2019
Knowledge

Title

URL Name

How-to-provide-a-License-Configuration-file-when-deploying-the-Client-Networking-MSI-4399

Article Number

000120012

Environment

Product: OpenEdge Version: 11.7, 12.1x OS: All supported Windows platforms Other: Client Networking MSI

Question/Problem Description

How to provide a License Configuration file when deploying the Client Networking MSI

Where and how to specify the Serial Number and Control Codes for the OpenEdge Client Networking MSI Package?
How to avoid error 4399 when deploying the OpenEdge Client Networking MSI Package to hundreds of client workstations?
When Client Networking is installed using the interactive CN MSI there is no dialogue for the Client Networking Serial Number or Control Codes
When Client Networking is installed using the silent CN MSI there are no property names available for Client Networking Serial Number or Control Codes

Why do I receive Error 4399 after installing the OpenEdge Client Networking MSI ?
After installing the OpenEdge Client Networking MSI, any client executable or batch file fails with error:

"The license for the client executable has expired. (4399)"

Steps to Reproduce

Clarifying Information

Error Message

The license for the client executable has expired. (4399)

Defect Number

Enhancement Number

Cause

Resolution

After installing the OpenEdge Client Networking MSI, the 4399 error is caused because Progress client executable's require a progress.cfg file containing Client Networking licensing information in order to run. Without the licensing information obtained from a .cfg file, the client is limited to shared memory connections only.

The OpenEdge Client Networking MSI does not require licensing information and therefore does not create a progress.cfg file containing product license information as part of the MSI install routine

The stand alone client networking installer expects that a progress.cfg file containing the required licensing information will be provided when the MSI is deployed by Active Directory, silently or interactively with an Install Wizard.

Obtaining a Client Networking progress.cfg

Apart from creating a license configuration file by running a Client Networking install, which continues to be available as part of
the OpenEdge installer, the required progress.cfg can be more easily obtained by creating a customised license file through the Customer Self Service portal. For further information refer to Article:

How to create a customised progress.cfg from existing licenses

Providing the License Configuration file when deploying the Client Networking MSI

A Client Networking cfg file can be made available for the Client Networking MSI by :

Setting the PROCFG environment variable prior to running the MSI install: set PROCFG=\\server\path\progress.cfg Note that if the progress.cfg file is placed in the Progress install directory the environment variable will not need to be set.
Copying the Client Networking progress.cfg file to the Install Directory (%DLC%) post install.

set JAVA_HOME=c:\OE121\jdk
PROGRESS_OE_12.1_WIN_64_CLIENTNETWORKING /v" /l*v c:\SilentInstall.log INSTALLDIR=C:\OE121 WRK=C:\WRKDIR PSCLANGUAGE=dut DEFAULTLANGUAGE=English DEFAULTCOUNTRY=Belgium CHARACTERSET=ISO8859-1 COLLATION=Basic CASE=Basic NUMBERFORMAT=\"1,234.56 (comma, period)\" NUMBERSEPARATOR=46 NUMBERDECIMALPOINT=44 DATEFORMAT=mdy /qb"
REM : copy the progress.cfg for CN on a mapped drive for example and copy it locally
xcopy Z:\CNMSI\progress.cfg c:\OE121\. /V /Q /Y

Workaround

Notes

Keyword Phrase

Last Modified Date

11/20/2020 6:59 AM

How to provide a License Configuration file when deploying the Client Networking MSI

Files(0)

Was this article helpful?

Was this article helpful?

How to provide a License Configuration file when deploying the Client Networking MSI

Information

Related Articles