Licensing issues

Issue Number

Description

IMS 3521148

After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, errors related to licensing and the licensing API (LicAPISvcProxy.NET) appear in the logger.

Workaround: This issue occurs when products attempt to acquire the license before the licensing service has started. This is an expected error during installation or upgrade. Once the installation or upgrade is complete, these errors will not occur.

IMS 2655533

Issue: The status symbol for the License Server security plug-in may not show the actual configured status of license server security. This can occur if:

• You change the SMS configuration.

  If you change the SMS configuration, the Configurator will continue to show the license server as configured securely (green icon). You must reconfigure secure mode by selecting Configure, even though the plug-in already shows that it is configured.

• You do not configure an SMS node.

  If you do not configure SMS, the Configurator will show that license server security is in a warning state (orange icon). Even though there is no SMS, you still must configure the secure mode by selecting Configure. This will not change the plug-in status icon; it will still show a warning state. However, this step is required to enable communication between the license server and license manager.

  Note that having an SMS configured is a requirement for secure communication between the license server and other System Platform components.

  Workaround: Always configure secure mode for the License Server security plug-in by selecting Configure.

• When you first configure the System Platform node, even if you do not configure a SMS.

• If you change the SMS configuration.

TFS 1300491

Activating OI Gateway consumes a license even though OI Gateway does not require a license, unless the MQTT component has been configured and is in use.

Workaround: Reserve a license for each Communication Driver (OI Server) that requires a license. No licenses will then be available because they are reserved to other Communication Drivers. When OI Gateway is activated but not using MQTT, no license will be consumed by OI Gateway. OI Gateway will run without interruption.

TFS 1241116

Manufacturing Execution System (MES) 2017/2017 R2 may not acquire a trial license when installed with System Platform 2020. This is due to a file path name change for the TrialLicensePool that is part of the System Platform 2020 release. This issue only occurs if you are using a trial license.

For both MES 2017 and MES 2017 R2, the file path for the TrialLicensePool folder is:
C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool

For System Platform 2020, the file path for the TrialLicensePool folder is:
C:\ProgramData\AVEVA\Licensing\TrialLicensePool

Workarounds: Use one of the following workarounds.

• If only the file path C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool is on your system, change the name of the Schneider Electric folder in the file path to AVEVA. No other change is needed.

• If both file paths exist on your system, copy the trial license from C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool to C:\ProgramData\AVEVA\Licensing\TrialLicensePool. No other change is needed

  If the AVEVA License Manager is open while you are moving the license file or renaming the file path, you may see a series of error messages. However, these will clear once the trial license is acquired. You can avoid this by closing the License Manager prior to renaming or moving the file.

TFS 793643

If no default browser is set, and you install System Platform with AVEVA Enterprise licensing selected, clicking the AVEVA Enterprise License Manager shortcut does not open the License Manager in the browser as it should. Instead, the shortcut opens in Windows Explorer. From Windows Explorer, you cannot open License Manager (the OK button is inactive).

Workaround: Follow the instructions for your operating system to set the default browser, and then open the AVEVA Enterprise License Manager from the shortcut, or:

Open your browser and copy the shortcut link, http://localhost/AELicenseManager, directly into the browser's address bar.

TFS 779958

When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to acquire additional licenses, even though the license manager may indicate that more licenses are available.