AVEVA™ Enterprise Licensing version 4.2 Readme

Last revision: 9/17/2025

In This Document

About this Readme

New features and enhancements

Before you Install Enterprise Licensing

Resolved Issues

Known Issues

AVEVA Enterprise Licensing Documentation

About this Readme

This document contains important information about AVEVA Enterprise Licensing 4.2 application.

Carefully review this Readme for issues that have been resolved in this release, and some known issues you may encounter while using AVEVA Enterprise Licensing.

For details on the different functionalities of AVEVA Enterprise Licensing and how to work with them, refer to the AVEVA Enterprise Licensing User Guide located in the License Manager folder (Program Files\Common Files\ArchestrA\Licensing Framework\License Manage\AELicenseManagerGuide) or AVEVA Documentation portal.

New features and enhancements

This section describes the new and enhanced functionality available in AVEVA Enterprise Licensing, providing an overview of the most significant changes, in the following versions:

Version 4.2

Support to import the same license multiple times with varying counts using Entitlement XML.
Delivered License Manager as a 64-bit product running as an ASP .NET Core service. Removed dependency on OWIN.
Delivered AVEVA Enterprise Licensing Platform as a single deliverable, replacing separate 32-bit and 64-bit packages.
Removed PCS consumption from the licensing framework.
Enhanced performance for license check-out and reservation operations.
Updated dependencies to their latest versions.
Enabled auto-secure configuration for enhanced security.
This release includes several bug fixes. For more information, refer to the Resolved Issues of Version 4.2.
AVEVA Enterprise Licensing documentation is now available on AVEVA Documentation portal.

Version 4.1

Support to acquire an alternate license if the previously acquired license had expired.
Support to notify users with an error message regarding activation of an expired license in offline mode.
Updated technology related to licensing, including:
- gRPC components to the latest version.
- .Net Core to latest version
- PCS framework to latest version.
- Shared and third-party components to their latest versions across all licensing components.
Enhanced License Configurator to run AELicWorkgroup utility in workgroup environments.
Reduced SDL debt.
This release includes several bug fixes. For more information, refer to the Resolved Issues of Version 4.1.

Important! There is a backward compatibility issue with historian 2020 and 2023. For more information, refer to the Known Issues of Version 4.1.

Before you Install Enterprise Licensing

The AVEVA Enterprise Licensing system is a common platform that allows you to effectively and efficiently manage AVEVA Enterprise Software product licenses. It is composed of a browser-based License Manager and a License Server that together allow you to share and deliver licenses for your installed products.

Before you install AVEVA Enterprise Licensing, review the information in this section.

AVEVA Enterprise Licensing platform version 3.7.002 is not compatible with versions 2.0 or earlier. Versions 2.0 and earlier were installed with Recipe Manager Plus 2014 R3 and earlier, Alarm Adviser 2014 R2 SP1 and earlier, and Intelligence 2014 R3 and earlier. Upgrading to AVEVA Enterprise Licensing platform version 4.2 could interfere with the functionality of those products. To upgrade to version 4.2 when you have versions 2.0 and earlier already installed on your system, you need to apply a hotfix. Contact AVEVA Technical Support to obtain the hotfix, and reference change request L00152975.
You can upgrade to version 4.2 directly from versions 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.5.1, 3.6, 3.7, 3.7.001, 3.7.002, 4.0, 4.0.1 and 4.1. Licensing versions earlier than 3.0 require upgrade to version 3.0 before upgrading to version 4.2.

Note: For information on installing and upgrading AVEVA Enterprise Licensing, License Manager, and License Server, refer to the AVEVA Enterprise Licensing User Guide located in the License Manager folder (Program Files\Common Files\ArchestrA\Licensing Framework\License Manage\AELicenseManagerGuide) or AVEVA Documentation portal.

Install Enterprise Licensing

You can install Enterprise Licensing with AVEVA Enterprise products or you can install just the Licensing system as a standalone.

You can install standalone versions of the following types:

Clean Install - License Manager only: installation on a machine with no previous installation of License Manager.
Clean Install - License Server only: installation on a machine with no previous installation of License Server.
Clean Install - License Manager and the License Server together: installation on a machine with no previous installation of License Manager or License Server.
Upgrade Enterprise Licensing
- Installation done on a node that has AVEVA Enterprise License Manager of any version
- Installation done on a node that has AVEVA Enterprise License Server of any version
- Installation done on a node that has AVEVA Enterprise Licensing of version greater than or equal to 3.0

Important: Machine names must not contain underscores (_). If the License Server's machine name includes an underscore, the standalone license installation will stop. Rename the machine to remove the underscore before activating the license.

Installation Requirements

This section describes the operating system, hardware, and software requirements to install AVEVA Enterprise Licensing.

Note: Ensure the MAC address remains unchanged after License Server installation; disable any "Random Hardware Addresses" settings.

Supported Operating Systems

Client Operating System (x86 and x64):
- Windows 10 and above
Server Operating System (x64 only):
- Windows Server 2016 and above

For more information about installation requirements, refer to the AVEVA System Platform 2023 R2 Readme.

Note: Microsoft Edge does not support single sign-on. Using Microsoft Edge will prompt you to sign in with your Windows credentials before launching License Manager.

.NET Requirement

AVEVA Enterprise Licensing requires .NET Framework 4.8. The licensing installation process checks if .NET version 4.8 is installed. If not, you are prompted to allow .NET installation.

Note: A system restart is required when .NET installation is complete. If the licensing installation does not automatically resume after the system restart, you can restart it manually.

Hardware Requirements

CPU Cores: 4
RAM: 4 GB

Software Requirements

A clean installation of License Manager and License Server requires .NET Framework 4.8.
An upgrade Installation of licensing components requires a previous version of licensing.
To make the licensing secure communication, the Platform Common Services (PCS) framework is required to be installed.

Port List

The following ports are used by default:

55555: AVEVA Enterprise License Server Legacy Support port.
55559: License Server Core Service Port on the License Server node.
59200 / 59201: License Server Agent Port on the License Server node and Product License Service port on the product node.
59203: AVEVA Enterprise License Product Service port.
59204: License Manager port on the License Manager node.

Important:
If you want to change the default ports, be very careful when changing port settings. Doing so may impact product operation. For more information about changing ports, see the "About Changing Default Port Settings" section in the AVEVA Enterprise Licensing Help.

Installation

This section describes the installation steps of AVEVA Enterprise Licensing.

Install standalone Enterprise Licensing

This section describes the steps involved to install AVEVA Enterprise Licensing.

Note: All products on the node that you are upgrading should be shut down. This will release all the licenses so that when the products are re-started licenses will be acquired correctly.

Install the AVEVA Enterprise Licensing standalone

Locate and right-select the setup.exe file and then select Run as administrator.
The License Agreement screen appears.
Accept the End User License Agreement and then select Next.
Select the components that you want to install:
- Select License Management to install only both the license server and license manager on the same node
- Select License Server to install the license server on the node.
  - Select AVEVA Enterprise License Server to install the secure license server.
  - Select AVEVA Enterprise License Server Legacy Support to allow support for legacy versions of Licensing on client nodes. If this checkbox is not selected, all client nodes that connect to this License Server would need to be upgraded to 4.2.
- Select AVEVA Enterprise License Manager to install the license manager on the node.
- Select Product Interface to install the Licensing API components. When upgrading, the Licensing API components that you previously installed with the product are selected automatically and are upgraded.
- Select the Operations Control Logger.
Select Next.
The Ready to Install the Application screen appears.
Select Install to start the installation.
Once the installation is complete, the Installation successful dialog box appears.
Select Finish.
Configure the License Server as needed:
- If you install License Manager only - the Configurator will not appear after installation. You will need to add a license server when you start the License Manager.
- If you upgrade, the Configurator appears after the installation is complete. Server configuration for the previously installed version of AVEVA Enterprise Licensing will be valid in most cases. Reconfigure the server name, server port, and redundancy as needed.

Install Enterprise Licensing Silently

If you are installing AVEVA Enterprise Licensing to multiple computers, you can run the installation "silently" (command line mode).

Installing AVEVA Enterprise Licensing Silently from the Command Line

Open the command prompt (cmd.exe) as Administrator.
Change the working directory to the folder where you downloaded AVEVA Enterprise Licensing Setup.exe.
Run one of the following commands, depending on whether or not you want the computer to reboot automatically:
- To automatically restart the node when installation is complete, enter the following command:
  "C:\...\CD-AELicensingPackage\Setup.exe"/silent"C:\Response.txt"
- If you do not want to automatically restart after installation, use the /Silentnoreboot option:
  "C:\...\CD-AELicensingPackage\Setup.exe" /silentnoreboot "C:\Response.txt"

Note: If you do not require Configurator as a part of Silent Installation, then you can navigate to All.txt file located in CD-AELicensingStandalone\SampleResponseFile and delete the section containing the <Configurator> tags.

Upgrade Enterprise Licensing

You can verify the version of License Manager by navigating to Control Panel and selecting Programs and Features. The installed AVEVA Enterprise License Manager, AVEVA Enterprise License Server, or AVEVA Enterprise Licensing (licensing platform components) version displays in the Version column.

Note: Licensing platform components are installed with every product, whether or not a License Manager or a License server are installed on that node. These components display in Programs and Features as "AVEVA Enterprise Licensing".

The following table describes different upgrade scenarios of AVEVA Enterprise Licensing to the latest available version. In some upgrade scenarios, licenses will enter the grace period. You can resume normal licensing functionality when the grace period ends. Refer to AVEVA Enterprise Licensing Help, Work with the grace period for more information.

Product Node Upgrade Scenarios	Description
Upgrade a product on the same node as an installed version of License Manager of earlier version.	License Manager and the AVEVA Enterprise Licensing components will upgrade to the latest version automatically.
Upgrade a product on the same node as an installed version of License Server of earlier version.	License Server and the AVEVA Enterprise Licensing Components will upgrade to the latest version automatically.
Upgrade a product on the same node as installed versions of both License Manager and License Server of earlier version.	License Manager, License Server, and the AVEVA Enterprise Licensing Components will upgrade to the latest version automatically.
Upgrade a product on a node that has no License Manager or License Server installed.	The AVEVA Enterprise Licensing components will upgrade to the latest version automatically. Will not result in an automatic upgrade of License Manager and License Server installed on remote nodes. You must upgrade your License Manager and License Server separately on the node where each is installed.
Upgrade to the latest version in Hyper-V and Azure virtual machines.	The license server will enter the Grace Period upon upgrade. End this grace period by syncing the licenses in the License Server. Important Note: To avoid entering the Grace Period, deactivate all licenses on the license server prior to upgrade in this scenario.
Licensing Version Upgrade Scenarios	Description
Upgrade from version 3.0 to the latest version.	The license server will enter the Grace Period upon upgrade. End this grace period by syncing the licenses in the License Server. Important Note: To avoid entering the Grace Period, deactivate all licenses on the license server prior to upgrade in this scenario.
Upgrade - from all versions to all versions.	If the license server is in a Grace Period prior to upgrade, it will remain in Grace Period following upgrade. To end the Grace Period after upgrading, you will need to contact Technical Support to obtain a Grace Period exit code. To avoid this scenario, end the Grace Period before upgrading to a newer License Server version. The license server will not enter a Grace Period upon upgrade.

Note: You can resume normal licensing functionality once the Grace Period has ended. Since all licenses should be removed from the server prior to ending the Grace Period, no licenses will be lost due to this action.

Upgrade AVEVA Enterprise Licensing

Note: All products should be shut down before upgrading. This will release all the licenses so that when the products are started licenses will be acquired correctly.

Right-select the setup.exe file and select Run as administrator.
An alert message with the list of products that will be upgraded appears.
Select OK.
The License Agreement screen appears.

Follow the steps from step 2, in the Install Enterprise Licensing section.

Upgrade License Server

After you upgrade to AVEVA Enterprise Licensing 4.2 from a version older than 4.0, a License Server Migration pop-up appears when you launch the License Manager.

Select the Migrate button to ensure that all data is migrated to the latest version.

Modify or repair Enterprise Licensing

Modify AVEVA Enterprise Licensing

You can change the AVEVA Enterprise Licensing components installed on your computer. You can add new components or remove the existing ones. You can modify any component of AVEVA Enterprise Licensing.

Note: You must have the installation media ready before you can modify a program.

Modify an installation

Select the Modify option from the AVEVA Enterprise Licensing Modify, Repair or Remove Installation dialog box. You can open the dialog by doing either of the following:
- Run Setup.exe from the AVEVA Enterprise Licensing installation media.
- Navigate to Uninstall or Change a Program in the Windows Control Panel. Then, select any AVEVA Enterprise Licensing component and then select Uninstall/Change.
  Note: The name of the Uninstall/Change option may vary depending on which Windows operating system is installed on your computer.
Select the Modify option, and then select Next. The list of AVEVA Enterprise Licensing components appears.
Select or clear the components that you want to add or remove, and then select Next. The verify change dialog box appears.
Select Modify. The selected components are added or removed and the complete modification dialog box appears.
Select Finish.
Note: The system may not prompt you to restart the system after Modify is successful. However, if you have added a new product or feature, a system restart is recommended.

Repair AVEVA Enterprise Licensing

You can repair the installation of any component of the AVEVA Enterprise Licensing. You can repair missing or corrupt files, registry keys or shortcuts. You can also reset the registry key to the default value.

Note: You must have the installation media ready before you repair a program.

Repair an installation

Select the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
Select the AVEVA Enterprise Licensing component that you want to repair, and then select the Uninstall/Change button. The Modify Repair or Remove Installation dialog box appears.
Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.
Select the Repair option, and then select Next. The Confirm Repair dialog box appears.
Select Repair. The complete repair dialog box appears.
Select Finish.

Uninstall Enterprise Licensing

Note: You cannot uninstall the product licensing if there is a product currently installed or when other products are currently using it.

Uninstall an AVEVA Enterprise Licensing Component

Select the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
Select the AVEVA Enterprise Licensing component that you want to uninstall, and then select Uninstall/Change. The Modify, Repair or Remove Installation dialog box appears.
Select the Remove option, and then select Next. The confirmation dialog box appears.
Select Uninstall. The component is uninstalled, and the complete uninstallation dialog box appears.
Select Finish.

Note: You cannot uninstall the License Server if it currently holds any licenses. Ensure all licenses are removed before attempting to uninstall.

Resolved Issues

This section includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.

Resolved Issues of Version 4.2

Defect ID	Description
3496090	Historian could not be opened after upgrading SP2020 and SP2023 with 4.2.0 LicAPI. A compatibility issue was observed between Licensing Platform 4.2 and Historian from SP2020 and SP2023.
3598913	The licensing installation failed when a higher version of .NET 8 was already installed.
3566572	[Intermittent] A checked-out license from License Manager was not acquired until the AECheckedoutlist command was executed from the checkout utility.
3568788	License Manager was not functioning after importation.
2655438	After installing License Manager, if PCS was configured with SMS, updated with a new SMS, or if SMS was removed, License Manager stopped working.
2655469	If License Servers were paired and after that SMS was changed, data synchronization did not happen between the servers.
2655487	Aveva Enterprise Licensing Platform (x86) alone was not working.
2655526	In HTTPS paired servers, renaming the backup server did not work.
2655533	When SMS was changed to No SMS, the Select License Server (secure) plug-in still showed a green icon until it was selected.
2624751	[Intermittent] [Windows 10] Was unable to automatically install the pre-requisite Microsoft Visual Studio C++ 2022 x86 Runtime Redistributable.
2790339	Was unable to launch License Manager if the machine name was renamed in HTTP Mode.
3534342	When a license was checked out from the License Manager (LM) and then checked out using the utility, performing check-in on one system did not check out all licenses as checked in.
3493727	[PSR] Deviation in execution time was observed in licensing 4.2 compared to version 4.0 for "Add Server", LM Refresh, and Unpair scenarios.
3561197	[Intermittent] Recipe Manager 2023 R2 was unable to acquire a license when SP2023R2P01 with Recipe Manager pointed to a remote node where AVEVA Enterprise Licensing 4.2 was installed.

Resolved Issues of Version 4.1

Defect ID	Description
3002356	The [Citect Anywhere] client did not release the license in AVEVA Enterprise Licensing.
2918166	The AVEVA Enterprise License product pervice was not running with a virtual account.
3354604	The license was not acquired for the OMI application, which operated in demo mode.
3037012	The license server was not functioning with FQDN.
3338171	Users from different domains, who were members of a group added to the AELicMgr group, could not access the license server.
2655456	License Server Agent gRPC Service Port was not configurable from the Configurator tool.
2482176	[LM Web]: Shortcut update of License Manager from HTTPS to HTTP when PCS was removed from the machine.
2606294	[Intermittent] License Server was not added to License Manager after installing the Standalone 4.0 build.
2962487	[HTTPS] License acquired details were not Synchronized to Back up server in redundancy pair server.

Known Issues

This section describes known issues in AVEVA Enterprise Licensing.

Known Issues of Version 4.2

Defect Number	Description
4098334	Error "Failed to load licensing libraries" is observed during deployment of OMI WebViewEngine on a node running SP2023R2SP1P02 with AEL upgraded to version 4.2
3439304	Unable to perform the checkout operation from the checkout utility when the license is already acquired.
3519845	The count value in "Add device" displays incorrect results when using the "Select Partial" option under Device/User Reservation.
3537851	Checkout is not synchronized with the backup server.
3544701	License expiry status mismatch is observed.
4058896	Existing checked-out licenses are removed when a new license is checked out from the checkout utility after upgrading LicAPI from SP20 and SP23 to the latest version.
4068278	Display name does not update properly after tabbing out for the second time.
4077749	License expiry details are displayed incorrectly in features.xml, although they appear correctly in LM and test applications.
4091207	The search textbox in License Summary fails when searching part numbers sequentially if all activated licenses are selected.
4105666	Sorting does not work for the quantity column in the Usage Summary.
4151121	After upgrading to the latest licensing package, migration status and license count are not displayed correctly on paired servers.
2655524	Reservations cannot be posted on the backup server.
2853783	Partitions are not created for the client license when legacy support is turned off.
3313087	The expected return period for backend licenses is shown as 14 days even when licenses with expiry within a week or more than 14 days are acquired.
3574011	The user name appears empty in the Usage Details page after releasing any client license when two or more licenses are acquired under the same user name.
4249891	Insufficient feature count exception is logged when checkout is performed for two part numbers with common feature as "intouch-tagcount".
4249871	[Intermittent] Re-importing updated reservation file causes duplicate partial reservation and incorrect pending count in DB.
4249800	Reservation count shows as 'Partial' before applying imported reservations.
4245115	Invalid device checkout creates persistent DB entry on first attempt, requires manual DB clear.
4119159	[Intermittent] InUse count in Usage Summary updates after importing only device reservations.

Known Issues of Version 4.1

Defect Number	Description
3496090	Not able to open Historian after upgrading SP2020 and SP2023 with 4.2.0 LicAPI. A compatibility issue is observed between Licensing Platform 4.2 and Historian from SP 2020 and SP 2023. Workaround: To resolve this, a hotfix is available for both 2020 and 2023. Contact tech support for a hotfix for historian.
3598913	The licensing installation fails when a higher version of .NET 8 is already installed. Workaround: Uninstall the existing .NET 8 version in ARP and proceed with the installation of the licensing component.
3544701	License expiry status mismatch - Just before a license expires, the system displays inconsistent status information. Normally, the license expires at midnight UTC; however, due to this issue, the client cannot acquire the license after midnight local time, even though the license remains valid and available. This problem arises from a discrepancy between local time and UTC validity.
2655524	Reservations cannot be processed on the backup server.
3485976	The License Manager fails to launch if the machine name is renamed in HTTP Mode.
3544701	The license expiry details within the manager are incorrect.
3566572	[Intermittent] A checked-out license from License Manager is not acquired until the AECheckedoutlist command is executed from the checkout utility
3568788	The License Manager is not functioning after importation.
2655438	After installing License Manager, if PCS is configured with SMS, updated with new SMS, or if SMS is removed, License Manager stops working. Workaround: Restart the service "AVEVA Enterprise License Manager Service".
2655469	If License Servers are paired and after this SMS is changed, data synchronization will not happen between the servers. Workaround: Deactivate Licenses, unpair and pair them again. Then activate the Licenses back.
2655487	Aveva Enterprise Licensing Platform (x86) alone is not working. Workaround: Install Aveva Enterprise Licensing Platform 64 bit in the same machine.
2655524	Unable to post reservations on the Backup server.
2655526	In HTTPS pair servers, renaming the backup server will not work. Workaround: Perform Unpair from Manage License Server and use Primary server.
2655533	When SMS is changed to No SMS, the Select License Server (secure) plug-in still shows a green icon until it is selected. Workaround: Select the Secure option under Aveva Enterprise Licensing and select Configure to unsecure the License Server.
2624751	[Intermittent] [Windows 10] Unable to automatically install the Pre-requisite Microsoft Visual Studio C++ 202286 Runtime Redistributable Workaround*: Manually install from the location "AELicensingStandalone\InstallFiles\Redist\VC2022".
2790339	Unable to launch License Manager if the machine name is renamed in HTTP Mode. Workaround: Register the License Manager web url with the new machine name using the PowerShell scripting tool. For example: netsh http add url=http://<new machine name>:80/Aelicensemanager user=everyone listen=yes. Restart the service "AVEVA Enterprise License Manager Service".
3537851	Checkout is not synced to the backup server.
3534342	When a license is checked out from the License Manager (LM) and then checked out using the utility, performing check-in on one system does not check out all licenses as checked in.
3313087	There is an expected reduction in display days for backend licenses when a backend license with an expiry in a week and a license with an expiry of more than 14 days are acquired.
3519951	[Intermittent] In the case of a paired server, license deactivation does not work for backup server.
3493727	[PSR] Deviation execution time is observed in licensing 4.2 with 4.0 version for "Add Server", LM Refresh and Unpair scenarios.
3561197	[Intermittent] Recipe Manager 2023 R2 is unable to acquire a license when SP2023R2P01 with Recipe Manager points to a remote node where AVEVA Enterprise Licensing 4.2 is installed. Workaround: Restart the machine.

AVEVA Enterprise Licensing Documentation

The AVEVA Enterprise Licensing documentation includes the following:

AVEVA Enterprise Licensing Web Help: Online Help available on the AVEVA Documentation portal.
To view the online help content, select the Help icon when the License Manager is active in your browser.

The help opens in a browser window.
AVEVA Enterprise Licensing Guide: User guide containing information on AVEVA Enterprise Licensing in Portable Document File (PDF) format.
To view PDF files, you need Adobe Reader installed on your computer. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

http://get.adobe.com/reader/

After installing Adobe Reader, double-click on a PDF file to view the book with Adobe Reader. You can also open a PDF book with the Adobe Reader Open command from the File menu.
AVEVA Enterprise Licensing Readme (Release Notes): A single HTML file which opens in your default browser.
To view the Readme file, double-click the "Readme-Licensing.html" file installed on your computer with the AVEVA Enterprise Licensing components.
AVEVA Enterprise Licensing Checkout Utility Help: A single HTM file which opens in your default browser.
To view the Checkout Utility Help file, double-click the "AELicensingCheckoutUtilityHelp.htm" file installed on your computer with the AVEVA Enterprise License API components.