Installation, upgrade, and galaxy migration issues
- Last UpdatedJan 28, 2025
- 5 minute read
|
Issue Number |
Description |
|
IMS 3541417 |
After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required DLL file is not installed. IMS 3540900 and IMS 3519786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then:
|
|
IMS 3540900 |
After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required DLL file is not installed. IMS 3541417 and IMS 3529786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then:
|
|
IMS 3523525 |
After upgrading a node that contains both Application Server and Historian from System Platform 2020 R2 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required. |
|
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 3519786 |
After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required. |
|
IMS 3509408 |
After upgrading from System Platform 2023 R2 SP1 from System Platform 2023 R2, data cannot be read from written to the OPC UA Service deployed from the IDE through the DDESuiteLink object. This occurs when using 128 character names for instances of the UserDefined object, combined with user defined attributes that also have 128 character names. |
|
IMS 2967085 |
During an upgrade to System Platform 2023 R2, you may receive an error message from the LicAPISvcProxy.NET service that starts: Failed to communicate with AVEVA Enterprise License Product Service. This is caused by an upgraded component trying to acquire a license before the licensing service has started. Workaround: None needed. The error will resolve itself once the upgrade is complete and the node is rebooted. |
|
IMS 2917871 |
After an upgrade, the AVEVA Insight Supervisor service is not set to start automatically. Workaround: After the upgrade, open the Windows Services dialog box. In the list of services, right-click the AVEVA Insight Supervisor service. Select Properties and, on the General tab, set the Startup type to Automatic. |
|
IMS 2840477 |
When you run setup to upgrade from System Platform 2023 or other version to System Platform 2023 R2 and reach the Ready to Upgrade the Application form, but then select Back, setup may not navigate to the previous page. This happens because the previous page is a prerequisite check. Since all prerequisites have been satisfied, the setup program remains on the Ready to Upgrade form. Workaround: If you wish to return to a prior point in the upgrade process, select Cancel and restart the setup program. |
|
IMS 1958954 |
After upgrading from a prior version to System Platform 2023, Windows start menu icons from the prior version of System Platform may be displayed instead of the new System Platform icons. This may affect the icons for all System Platform products and components, including the Operations Control Management Console, Trend App, and InTouch HMI WindowMaker. This is an operating system cache issue that affects newer versions of Windows. There is no impact to the functionality of the products, and all new System Platform features will work as expected. Workaround: You can clear the Windows cache. Note that the cache is owned and managed by the Windows operating system. Therefore, we recommend that you contact Microsoft before using this procedure.
|
|
IMS 1925046 |
After installing or upgrading to System Platform 2023, and then completing configuration of the System Monitor Manager, icons and the UI title bar from the previous version of System Platform are shown for the Operations Control Management Console (OCMC), even if this is a new installation. This also occurs when installing OCMC Standalone and then installing any product that has an older version of OCMC (SMC). The icon in the title bar of the OCMC and the task bar icon revert to old icon. Workaround: Use Programs and Features in the Control Panel to repair the Operations Control Management Console. |
|
IMS 1758909/ |
MDT AutoSave 5.01a is not supported on System Platform 2023 and System Platform Enterprise 2023. |
|
TFS 1249251 |
Upgrading to System Platform 2020 or later from a prior version does not succeed if the prior version used a 32-bit version of SQL Server. Support for 32-bit SQL Server was discontinued for the System Platform 2020 release. Workarounds: Two methods for upgrading System Platform and migrating galaxies are listed below. Use the first method if you will be using SQL Server Express, included with System Platform. Use the second method if you will be installing a 64-bit full version of SQL Server in place of a 32-bit version. Method 1 (Install SQL Server Express as part of System Platform installation):
|