Last revision: 10/25/2024
This document contains important information about AVEVA Enterprise Licensing version 4.1. This Readme documents the system requirements, known issues, resolved issues, and changes, if any, to the AVEVA Enterprise Software documentation included with the AVEVA Enterprise Licensing components
Important: 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 EnterpriseLicensing platform version 4.1 could interfere with the functionality of those products. To upgrade to version 4.1 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.1 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 and 4.0. Licensing versions earlier than 3.0 require upgrade to version 3.0 before upgrading to version 4.1.
Note: You can find information and procedures for installing and upgrading AVEVA Enterprise Licensing, License Manager, and License Server in the AVEVA Enterprise Licensing Installation online help, available from the installation utility.
Note: When you upgrade to AVEVA Enterprise Licensing 4.1 from an older version, the AVEVA Enterprise License Server Legacy Support checkbox is unselected by default. However, you may select the AVEVA Enterprise License Server Legacy Support checkbox , as it is recommended that all nodes be upgraded to 4.1, unless your nodes have version 4.0 installed.
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:
This version incorporates the following components and enhancements:
Important! There is a backward compatibility issue with historian 2020 and 2023. For more information, refer to the Known Issues of Version 4.1.
This version of AVEVA Enterprise Licensing incorporates several bug fixes.
This version incorporates the following components and enhancements:
This version incorporates redistributable updates.
This version incorporates the following components and enhancements:
Upgrading AVEVA Enterprise Licensing
Uninstalling AVEVA 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.
You can install AVEVA Enterprise Licensing with AVEVA Enterprise products or you can install as a standalone. Different types of installation that you can install as a standalone are:
This section describes the operating system, hardware, and software requirements to install AVEVA Enterprise Licensing.
Below are the Operating System minimum requirements:
For more information about supported operating systems, refer to the AVEVA System Platform 2023 R2 Readme.
.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.
Below are the basic hardware requirements to install AVEVA Enterprise Licensing:
The following ports are used by default:
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.
This section describes the installation steps of AVEVA Enterprise Licensing.
Note: All installed products should be shut down before upgrading. This will release all the licenses so that when the products are re-started licenses will be acquired correctly.
To install the AVEVA Enterprise Licensing standalone
The License Agreement screen appears.
Note: When you upgrade to AVEVA Enterprise Licensing 4.1 from an older version, the AVEVA Enterprise License Server Legacy Support checkbox is unselected by default. However, you may select the AVEVA Enterprise License Server Legacy Support checkbox , as it is recommended that all client nodes be upgraded to 4.1, unless your client nodes have version 4.0 installed. To have only secure communication, once all the client nodes are updated you can uninstall legacy support.
If an older version of the Licensing API is not installed, then the Licensing API option will be disabled and will not be selected to install.
The Ready to Install the Application screen appears.
Once the installation is complete, the Installation successful dialog box appears.
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
"C:\...\CD-AELicensingPackage\Setup.exe"/silent"C:\Response.txt"
"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.
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" for both 32- and 64-bit systems.
The following table describes different upgrade scenarios of AVEVA Enterprise Licensing to version 4.1. In some upgrade scenarios, licenses will enter the grace period. You can resume normal licensing functionality when the grace period ends. Refer to the AVEVA Enterprise Licensing Help, "Working with the Grace Period" topic for more information.
Product Node Upgrade Scenarios |
Description |
Upgrade a product on the same node as an installed version of License Manager earlier than 4.1. |
License Manager and the AVEVA Enterprise Licensing components will upgrade to version 4.1 automatically. |
Upgrade a product on the same node as an installed version of License Server earlier than 4.1. |
License Server and the AVEVA Enterprise Licensing Components will upgrade to version 4.1 automatically. |
Upgrade a product on the same node as installed versions of both License Manager and License Server earlier than 4.1. |
License Manager, License Server, and the AVEVA Enterprise Licensing Components will upgrade to version 4.1 automatically. |
Upgrade a product on a node that has no License Manager or License Server installed. |
The AVEVA Enterprise Licensing components will upgrade to version 4.1 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 version 4.1 from 3.3 or lower 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. See the AVEVA Enterprise Licensing Guide for the procedure of syncing licenses. Important Note: To avoid entering the Grace Period, deactivate all licenses on the license server prior to upgrade in this scenario. |
Upgrade to version 4.1 from 3.5.1 or lower in Physical machines. |
|
Licensing Version Upgrade Scenarios |
Description |
Upgrade from version 3.0 to 4.1 |
The license server will enter the Grace Period upon upgrade. End this grace period by syncing the licenses in the License Server. See the AVEVA Enterprise Licensing Guide for the procedure of syncing licenses. 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. |
Upgrade from version 3.1 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.2 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.3 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.4 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.5 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.5.1 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.6 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.7 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.7.001 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Upgrade from version 3.7.002 to 4.1 |
The license server will not enter a Grace Period upon upgrade. |
Note: You can resume normal licensing functionality once the Grace Period is ended. See the AVEVA Enterprise Licensing Guide for the detailed procedure. Since all licenses should be removed from the server prior to ending the Grace Period, no licenses will be lost due to this action.
To 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.
An alert message with the list of products that will be upgraded appears.
The License Agreement screen appears.
Follow the steps from step 2, in the Installing AVEVA Enterprise Licensing section.
Note: After you upgrade to AVEVA Enterprise Licensing 4.1 from an older version, 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.
Note: You cannot uninstall the product licensing if there is a product currently installed or when other products are currently using it.
To uninstall an AVEVA Enterprise Licensing Component
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.
To modify an installation
Note: The name of the Uninstall/Change option may vary depending on which Windows operating system is installed on your computer.
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.
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.
To repair an installation
Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.
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.
Defect ID |
Description |
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. |
Defect ID |
Description |
2833220 |
[Intouch][Intermittent] When user opened the Intouch Window Viewer / Window Maker application from Application Manager, a pop-up displayed with text "License could not be acquired. Click Retry to check for a License". |
2779009 |
Check-in of last part number from one device through checkout utility was deleting checkout data of all other devices on the License Server. |
2830578 |
Was unable to run License Manager on custom secure port. |
2853753 |
The count column changed to a number from partial when the total count of a part number was reserved for different devices. |
2833220 |
[Intouch][Intermittent] When the user opened the Intouch Window Viewer / Window Maker application from Application Manager, a pop-up was displayed with the text "License could not be acquired. Click Retry to check for a License." |
2869192 |
Port issue for AVEVA Enterprise License Agent Service when not configured as secure. |
2869225 |
[License] LicAPI did NOT release the license from local trust storage when the license server was changed while the license was in use. |
2876461 |
[User Reservation] The import functionality displayed "Not a valid file to import" if the total available count in the file was reserved. |
2877449 |
[Checkout] A green color status was displayed near the checkout checkbox when an invalid device name was provided in the case of Partial Selection. |
2877530 |
The "Quantity Activated" checkbox was disabled, and the activated count still displayed in the License Activation form after the License Server was marked as obsolete in the FNE Server. |
2879100 |
[Upgrade] Operations Control Logger was not selected by default during the upgrade from older versions of Licensing to 4.0.1. |
2894451
|
The import functionality did not work for device reservation when all the features of the part number were selected and reserved partially to devices. |
2903529 |
When a partial reservation was exported and imported by changing the checkout value from False to True, it was not checked out. |
Defect ID |
SR/Case Number |
Description |
1874011 |
960176054 |
Some handheld devices that consume client licenses were not able to properly acquire licenses. |
1914329 |
960169985 |
A user from a different domain, who is also a member of a group that is part of the AELicMgr group, could not access the License Server. |
2283934 |
960253090 |
InTouch HMI stations were unable to acquire licenses. |
1899352 |
960172546 |
The license was getting acquired from both primary and secondary servers. |
Defect ID |
SR/Case Number |
Description |
629131 |
96002347 |
Local License Viewer was updated to populate the Trial License duration period and Trial start date. |
691497 |
- |
LicAPI logged all the custom messages with the wrong log flag. |
845084 |
- |
The avevalic file did not work accurately and interfered with other products acquiring the license. |
849803 |
- |
After upgrading to 3.7, license acquisition from the checked-out store failed. |
924324 |
960044145 |
The domain user <DomainUserName> could not access the license server <LicenseServerName>. |
924928 |
960046418 |
After upgrading to 3.7, the Checkout operation took a long time to complete. |
This section describes known issues in AVEVA Enterprise Licensing.
Defect Number |
Description |
3496090 |
Not able to open Historian after upgrading SP2020 and SP2023 with 4.1.0 LicAPI. |
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++ 2022*86 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.1 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.1 is installed. |
Defect Number |
Description |
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". |
2655456
|
License Server Agent gRPC Service Port is not configurable from the Configurator tool. Workaround: By default the Agent Port displays as "59201". Update the "ServerConfig.xml" file from the locationSS C:\ProgramData\AVEVA\Licensing\ServerConfig.xml with the LicenseServerASgentServicePort as " " from "59201". For more information, see Changing the Default License Server Agent Port in AVEVA™ Enterprise Licensing Guide. (This guide can be accessed from the AVEVA Enterprise License Manager) |
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. |
2482176 |
[LM Web]: Shortcut update of License Manager from HTTPS to HTTP when PCS is removed from the machine. Workaround: Update the protocol of the License Manager shortcut manually to HTTP |
2624751
|
[Intermittent][Windows 10] Unable to automatically install the Pre-requisite Microsoft Visual Studio C++ 2022*86 Runtime Redistributable Workaround: Manually install from the location "AELicensingStandalone\InstallFiles\Redist\VC2022". |
2606294
|
[Intermittent] License Server is not added to License Manager after installing the Standalone 4.0 build. Workaround: Restart the service "License Server Agent Service". |
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". |
2962487
|
[HTTPS] License acquired details are not Synchronized to Back up server in redundancy pair server. |
Defect Number |
Description |
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". |
2655456
|
License Server Agent gRPC Service Port is not configurable from the Configurator tool. Workaround: By default the Agent Port displays as "59201". Update the "ServerConfig.xml" file from the location C:\ProgramData\AVEVA\Licensing\ServerConfig.xml with the LicenseServerASgentServicePort as " " from "59201". For more information, see Changing the Default License Server Agent Port in AVEVA™ Enterprise Licensing Guide. (This guide can be accessed from the AVEVA Enterprise License Manager) |
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. |
2482176 |
[LM Web]: Shortcut update of License Manager from HTTPS to HTTP when PCS is removed from the machine. Workaround: Update the protocol of the License Manager shortcut manually to HTTP |
2624751
|
[Intermittent][Windows 10] Unable to automatically install the Pre-requisite Microsoft Visual Studio C++ 2022*86 Runtime Redistributable Workaround: Manually install from the location "AELicensingStandalone\InstallFiles\Redist\VC2022". |
2606294
|
[Intermittent] License Server is not added to License Manager after installing the Standalone 4.0 build. Workaround: Restart the service "License Server Agent Service". |
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". |
2779009 |
Check-in of last part number from one device through checkout utility is deleting checkout data of all other devices on the License Server. |
2833220 |
[Intouch][Intermittent] When the user opens the Intouch Window Viewer / Window Maker application from Application Manager, a pop-up is displayed with text " License could not be acquired. Click Retry to check for a License". Workaround: Click the Retry option to acquire license. |
Defect Number |
Description |
693546 |
Localization Issue- Assert Failure when launching the aaIDE.exe on the Chinese Operating System |
The system requirements for AVEVA Enterprise Licensing components are the same as those for the products you have purchased and installed. See the Readme file and the installation guide associated with your specific product for more information.
Browser Settings- Security
AVEVA Enterprise License Manager is accessed through the browser installed on any computer on your network. License Manager is compatible with the major browsers including Microsoft Internet Explorer, Firefox, and Chrome. Each browser has its own security features and configuration.
For example, using Internet Explorer to access License Manager requires setting the following options:
See the Internet Explorer documentation for information about how to configure trusted sites.
For additional information on browser-based web help and active content, see Web Help Display and Video Playback.
Browser Settings- Animation Display
Browser-specific settings need to be configured to enable animation display within AVEVA Enterprise License Manager. Setting details for each browser are described below.
Internet Explorer
Animation display is not enabled by default for Internet Explorer. To enable animation, do the following:
The Internet Options dialog box appears.
Firefox
Animation display is enabled by default in Firefox. If animated content such as progress meters is not displaying, do the following:
Acknowledge the warning to proceed.
The image.animation_mode setting will appear.
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help displays in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your default browser without requiring an Internet connection. You can invoke the help by right-clicking a context menu item, a symbol, or another UI element, or otherwise invoking help using elements contained in your specific UI.
Browser Permissions for Displaying Web Help
Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.
Playback of Tutorial Videos
The web help may contain a number of brief tutorial videos. To play these videos:
The AVEVA Enterprise Licensing documentation includes the following:
To view the online help content, select the Help icon when the License Manager is active in your browser.
Alternatively, you can go to the Windows Start menu, select the AVEVA folder, and then select AVEVA Help.
The web help opens in a browser window.
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:
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.
To view the Readme file, double-click the "Readme-Licensing.html" file installed on your computer with the AVEVA Enterprise Licensing components.
To view the Checkout Utility Help file, double-click the "AELicensingCheckoutUtilityHelp.htm" file installed on your computer with the AVEVA Enterprise License API components.
© 2015-2024 AVEVA Group Limited or its subsidiaries. All rights reserved. | Contact Us |