Application Server resolved issues - SP 2023 R2
- Last UpdatedMar 21, 2025
- 10 minute read
|
Original Issue |
Related Issues |
Case/SR Number |
Description |
|
IMS 1848600 |
960157869 |
Creating a new instance of a working, deployed OMI application caused all of the working instances of the application to need to be redeployed. |
|
|
IMS 1860423 |
960174949 |
Intermittently, the Secured Write "Retrieving Reason Description" timed out and displayed the message |
|
|
IMS 1877088 |
960176481 |
In dynamic text referencing for Integer alarms, comment did not work with String arrays. |
|
|
IMS 1888024 |
960161993 |
While importing objects from a specific CSV file, the IDE closed with the message . |
|
|
IMS 1892267 |
960171722 |
If a platform was deployed when installing a patch for AVEVA System Platform, the AlarmClient and TrendClient controls were not updated. No warnings or error messages were written to the log. |
|
|
IMS 1911736 |
960166135 |
While deploying a redundant engine, the bootstrap service encountered an error, stopping the engine and the platform. The error message generated was |
|
|
IMS 1914761 |
960180506 |
Some objects were not updating dynamic data on the Application Object Server. Redeploying the objects fixed the issue. |
|
|
IMS 1926125 |
960179494 |
Changing the SQL Server Compatibility level to 2019 made importing objects unacceptably slow. |
|
|
IMS 1934343 |
1819846 1862300 |
960190420 |
There was a performance issue when using a derived template to create instances through GRAccess with a large Galaxy (Galaxy size over 2GB, 31K IO size). |
|
IMS 1939546 |
960191284 |
InTouch values were not being updated due to an issue with the NmxSvc service. |
|
|
IMS 1941500 |
960185850 |
When using the scan mode "Active on Demand" and warm redundancy for the backup engine, failover to the backup engine caused all items to become active. |
|
|
IMS 1949369 |
960192655 |
Changing a limit alarm value did not cause the alarm condition to be re-evaluated for buffered attributes. A buffered attribute's alarm state did not change until the next time the attribute value was updated. |
|
|
IMS 1969449 |
960196010 |
After writing to an attribute in the OPC client, the client that updated the attribute did not see the new value, while other clients did. |
|
|
IMS 1988488 |
2118272 |
960200700 |
After upgrading AVEVA System Platform, a Galaxy which had not shown any object errors or warnings showed over 3000. |
|
IMS 1991737 |
960201613 |
In some cases, after aaGR.exe was restarted, it took up to ten minutes to restart the IDE or OCMC (formerly SMC). |
|
|
IMS 1992148 |
960192426 |
The search feature in the System Platform IDE was unacceptably slow in certain system configurations. |
|
|
IMS 1998690 |
960128047 |
Under certain conditions, the AreaHierarchy.Xml could not be updated during deployment. Though this did not cause an error message, items could be missing or incorrectly marked as deployed or undeployed. This could cause, for example, alarms not to display in the EAC. |
|
|
IMS 2024863 |
960206498 |
Using the mouse to select part of the text in a field did not work. |
|
|
IMS 2068077 |
960216050 |
When using Azure AD as the authentication provider, the IDE could not retrieve roles from Azure AD. Instead, it displayed the message . |
|
|
IMS 2074106 |
960194657 |
One customer's Application Servers were having a number of consistency issues, including an inability to deploy OMI applications. |
|
|
IMS 2086283 |
960188670 |
Intermittently, data and graphics were loading slowly in OMI applications. |
|
|
IMS 2101753 |
2287792 2130255 |
960221853 |
The OPC client failed when browsing items from the OPC server. |
|
IMS 2127825 |
960111993 |
There were delays in data updates in an OMI application when switching between primary and backup servers. |
|
|
IMS 2137381 |
960226495 |
If a client computer running the alarm control was rebooted, shelved alarms appeared in the control as if they were active. To correct this, each alarm had to be unshelved, then shelved again. |
|
|
IMS 2138833 |
960214835 |
In some cases, adding a new symbol to a graphic corrupted the graphic, causing it to show a circular reference message. This could also affect other graphics in the same object. |
|
|
IMS 2139129 |
2137841 |
960228455 |
After modifying a template, the template's child objects showed warnings. There were no warnings before the template was modified. Validating the objects cleared the warning state. |
|
IMS 2145673 |
960230037 |
In AVEVA System Platform 2023, if you cleared the Associate Galaxy Graphics check box for an InTouch ViewApp template, the option remained selected when you opened the template again. |
|
|
IMS 2149159 |
960221364 |
The output destination for some instances was changed from "---" to the default when a locked property in the instance's template was changed and the template was checked in. |
|
|
IMS 2158159 |
960219741 |
Changes to a symbol that belonged to an area were not being saved correctly. When the area was closed and re-opened, the original symbol reappeared, without the editing changes. |
|
|
IMS 2171127 |
960218196 |
The .AlarmInhibit setting was not retained when an Engine was redeployed. |
|
|
IMS 2178063 |
On a Japanese operating system, the Graphic Editor Save Confirmation dialog shows overlapped message text while saving a graphic. |
||
|
IMS 2178106 |
The AVEVA System Platform 2023 IDE became sluggish and unstable when creating 30 instances of an Operations Capability Object with PEM enabled. |
||
|
IMS 2179834 |
960238000 |
Deploying an OMI ViewApp after importing new objects into the working Galaxy failed with the message |
|
|
IMS 2180111 |
960223297 |
Exporting an object to a CSV file, changing a field such as ShortDesc, and re-importing the object resulted in unexpected and incorrect changes to the object's wizard options. |
|
|
IMS 2180583 |
960238103 |
After rebooting a platform, the platform engine crashed while the application engine instance continued to run. There were no MX communications and you could not deploy or undeploy objects on the platform. |
|
|
IMS 2183152 |
Intermittently, when using a warm redundant engine, if the primary engine was disconnected from the network, causing failover to the backup engine, then reconnected to the network, the Object Viewer could not resolve references. Attributes showed bad quality with a Communication Error until the Object Viewer was closed and re-opened. This issue was specific to the Object Viewer; OMI VIewApps and InTouch Applications showed correct values. |
||
|
IMS 2184681 |
960235646 |
When using Azure AD as the authentication provider, only groups without a space in their names were listed when adding new roles. |
|
|
IMS 2219073 |
960229273 |
New users could write to an attribute from an OMI VIewApp only when on the Application Object Server where the object was running. The attempt failed with a message saying that the user did not have the needed permission. Once they had written to an attribute from that server, they could then write to attributes from any operator machine. |
|
|
IMS 2192057 |
960230061 |
With several remote users connected to the GR node and using the IDE, the IDE would sometimes crash. |
|
|
IMS 2197662 |
IMS 2384675 |
960241303 |
After a disconnection and reconnection, store-and-forward late data from MQTT was being played back through the HMI instead of going directly to the Historian. |
|
IMS 2199153 |
960214756 |
At times, the ConnectionStatus of an RDIObject was Disconnected despite one of the DIObject being Connected. This occurred randomly. |
|
|
IMS 2213923 |
960227806 |
In AVEVA System Platform 2023, you could not retrieve the value of the TYPE parameter from a DIObject. The parameter seemed to be removed by the ScanGroupRuntime. |
|
|
IMS 2219405 |
960236095 |
In AVEVA System Platform 2023, when using Azure AD as the authentication provider, once a user had logged into an OMI VIewApp using their user name and password, they could then log in to InTouch for System Platform using only their user name, without having to enter a password. |
|
|
IMS 2292916 |
960253318 |
When using a redundant AppEngine, the View In Object Viewer feature did not automatically focus on the selected object. |
|
|
IMS 2293862 |
960245764 |
The Cross Reference tab for an object did not always show all cross references. |
|
|
IMS 2296755 |
960251997 |
Deploying objects that pointed to a DDESuiteLink object on another AppEngine on the same platform caused LMX warnings during or just after deployment. In addition, some objects, not limited to the ones that received the warning, showed bad quality in the Object Viewer. |
|
|
IMS 2304964 |
960234377 |
The GR Platform aaEngine process kept using increasing amounts of memory until the system became unresponsive and showed the message . At that point, the server needed to be restarted. |
|
|
IMS 2320864 |
960262032 |
During some installations, the AVEVA NmxSvc service was not set up properly. |
|
|
IMS 2322204 |
960245921 |
If failover to a backup GR node occurred after an alarm occurred but before it was acknowledged, acknowledging the alarm sometimes failed with the message . |
|
|
IMS 2325393 |
960256256 |
Enhanced the logging of the application category component to better troubleshoot object deployment issues. |
|
|
IMS 2329110 |
960259732 |
Improved check-in performance after adding options to a template. |
|
|
IMS 2338358 |
960263766 |
In the galaxy browser, filtering by attribute did not work for device integration objects or RDI objects. |
|
|
IMS 2354864 |
IMS 2167852 |
960269666 |
An InTouch application running in a remote desktop session would freeze for a few seconds to a few minutes, then resume working normally. |
|
IMS 2357627 |
960264356 |
After turning on the Simplified Layout option in the System Platform IDE, the keyboard shortcuts for IDE features did not work. This continued until you restarted the IDE, even if you turned off Simplified Layout. |
|
|
IMS 2365598 |
960271756 |
After some AVEVA System Platform upgrades, Boolean ASP arrays stopped working. The arrays had been configured following the instructions in Tech Note TN000022758 (legacy ID TN423). |
|
|
IMS 2372346 |
960270563 |
Under certain conditions, when checking in a template that had had unrelated changes made, the AlarmSourceAttr attribute was locked in error. |
|
|
IMS 2384675 |
IMS 2197622 |
960243658 |
When using a DDESuiteLink object to read from an OI.MQTT server, after a disconnection and reconnection, store-and-forward late data was being played back through the HMI and was missing from the Historian. |
|
IMS 2396741 |
960275948 |
When "Enable advanced communication management" is enabled in the IDE, values for attributes stop updating when written to with a different datatype. |
|
|
IMS 2396784 |
IMS 2339386 |
960278840 |
The AVEVA Galaxy Repository Service (aaGR.exe) was sometimes crashing randomly. |
|
IMS 2412334 |
IMS 987524 |
960275032 |
After updating an OMI ViewApp and deploying it to two or more hosts, launching the ViewApp sometimes still launched the older version of the ViewApp. |
|
IMS 2420563 |
960282853 |
After changing a template with a large number of child objects, the changes were not always propagated to all children. In this case, the save process reported that it was successful, but errors were recorded in the logger. |
|
|
IMS 2422899 |
960284673 |
The Change Network Account dialog box was unreadable on a Chinese Operating System after upgrading to 2023 Patch 01. |
|
|
IMS 2422443 |
IMS 2380893 |
960244101 |
Using a GRAccess application to change the Symbol Wizard option descriptions of a UDO changed the OMI ViewApp runtime behavior of the embedded symbol. |
|
IMS 2435545 |
960278150 |
For some Galaxies, Galaxy load and validation took much longer after an upgrade to a newer version of AVEVA System Platform. |
|
|
IMS 2442091 |
960265213 |
In the IDE, the properties window for an attribute was always too small when it first opened and needed to be resized. |
|
|
IMS 2414287 |
960291144 |
After installing a Microsoft update, started to see "APPCRASH events for aaObjectViewer.exe and wm.exe in the Windows Logger after closing the Object Viewer. Tthese events did not cause any problem with using the IDE. |
|
|
IMS 2441229 |
960283947 |
The GalaxyBrowser pop-up window always opened to the last position it had occupied for any user. If the new user had a smaller monitor than the previous user, this sometimes caused the Galaxy Browser position to be completely off the screen of the smaller monitor. |
|
|
IMS 2452008 |
960287309 |
After exporting a Galaxy from 2014 P01 and then importing it to 2023, the default element styles were missing from the new Galaxy. |
|
|
IMS 2464781 |
960294256 |
With redundant engines deployed and redundancy alarms enabled, no alarm was generated when the primary engine shut down and the redundant engine took over. |
|
|
IMS 2473677 |
960295264 |
In some cases, after an upgrade from 2014 P01 to 2023, customized alarm severity images appeared enlarged and distorted. |
|
|
IMS 2476051 |
960297286 |
The IDE opens the wrong object in the Object Editor if you perform these actions, in order:
|
|
|
IMS 2482518 |
960290054 |
When historizing alarm data using A2ALMDB, the displayed timestamp for buffered data was incorrect. It did not take into account the time zone offset from UTC. |
|
|
IMS 2489138 |
960281235 |
Importing previously exported alarm messages sometimes failed with a timeout error reported in the log. |
|
|
IMS 2493247 |
960300171 |
When there were complex visibility expressions in the Object Wizard Visibility Settings, the choices chosen for an instance did not display in the IDE, though they worked correctly in runtime. |
|
|
IMS 2513357 |
960291831 |
After upgrading from System Platform2017 U3 SP1, when a new item was added in the PLC\OFS UPC server, the new object did not show any data until the OPCDA DI object was redeployed. |
|
|
IMS 2535753 |
960300675 |
Importing a template with I/O enabled overrode existing instances' settings for invertvalue and deadband. |
|
|
IMS 2564110 |
960303538 |
Restoring a Galaxy .cab file failed if there was more than one .mdf file in the database. |
|
|
IMS 2567323 |
960225587 |
If an Object Wizard included a User Defined Attribute (UDA) with the buffered property set to true and an option to set the UDA to Used or Not Used, creating and saving an instance with the option set to Not Used caused the warning . |
|
|
IMS 2574326 |
960297592 |
After working correctly for a period of time, the Web Client display showed . Restarting the ASBService service fixed the issue, but it re-occurred after periodically. Log showed ". |
|
|
IMS 2582433 |
960312547 |
After migrating from 2020 R2 SP1 to 2023 P01, deploying an instance created from a template that contained a series of User Defined Attributes caused multiple warning messages in the log. The deployment appeared to be successful, but attempting to undeploy the instance caused an error and sometimes hung the engine. |
|
|
IMS 2588645 |
IMS 2541429 |
960295797 |
If an Application Object Server hosting the primary object engines was unplugged from the SCADA network, then re-attached, the platform failed to restart. |
|
IMS 2620934 |
960327401 |
Deploying certain objects failed with this error in the OCMC log: . The engine became unresponsive and needed restarted. |
|
|
IMS 2632194 |
960333771 |
In some cases, checking in a large or complicated object caused other users accessing the same Galaxy through the IDE, OMI, or the Object VIewer to hang or lose their connection. |