Application Server resolved issues - SP 2023 R2 SP1 Patch 01
- Last UpdatedMar 20, 2025
- 4 minute read
This table describes important resolved issues in AVEVA OMI. Some issues that have been fixed in this release may not be listed.
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
3436650 |
960441148 |
When an AppEngine that hosted a remote response object (RRO) was deployed, various errors from both the Bro network traffic analyzer and the Object Sync Manager were displayed in the Operations Control Management Console (OCMC) Logger. |
|
|
3446427 |
960436229 |
Importing an AppEngine object from a galaxy stored in a CSV file resulted in Package Manager errors being logged in the OCMC Logger. Despite the errors, there was no functional impact. |
|
|
3504158 |
960454815 |
After migrating a galaxy from System Platform 2020 R2 SP1 P01 to 2023 P03, check-out and check-in operations for OMI ViewApps took much longer than normal. |
|
|
3509530 |
960459801 |
The IDE would stop responding after the user selected multiple attributes and attempted to link content to them. |
|
|
3539806 |
3631902 |
960464536 960497479 |
Despite security settings that did not allow a user to edit galaxy styles, a user could do so anyways. Although an error message was displayed that stated the user could not save the edits, the user could also do so anyways. |
|
3561126 |
960464964 |
The Graphic Editor did not allow a user to duplicate or create new graphics in an existing folder. A pop-up error message, "Failed to create graphic element - target graphic toolset does not exist" was displayed, and an error was sent to the OCMC Logger. |
|
|
3579076 |
960457536 |
When a template with a modified object wizard option was imported, the value of a Boolean attribute tied to the wizard option was inverted. |
|
|
3579833 |
960457652 |
After deployment, an Application Object Server stopped working after a period of time, and the redundant engines did not sync with the partner engines. |
|
|
3589947 |
960430302 |
Shelved alarms across two redundant systems did not synchronize correctly between alarm providers. |
|
|
3593363 |
3423855 |
960477838 960438566 |
After the import of objects with object wizards, scripts for some of the instances did not appear until after the objects were validated. |
|
3615543 |
960490669 960502341 |
The cursor position jumped unexpectedly between the attribute search field and the Choices and Options "Prompt" field. |
|
|
3648115 |
960436136 |
A faceplate graphic displayed "###" instead of showing the actual runtime values. |
|
|
3662357 |
960474819 |
When the value for an object wizard option was edited, the value of an unrelated option changed improperly when the object was saved. |
|
|
3515435 |
960452287 |
On Windows Server 2016, exported AppEngines that were subsequently imported were not being assigned to the correct platform. |
|
|
3684129 |
960520184 |
Upon creation of a new UserDefined derived template, the addition of an "Object writable" string attribute with an initial value to the template, and then the export of the template to a CSV file, the string's initial value was not included in the export. |
|
|
3672192 |
3649364 |
960502679 |
A status-handling error in the code base relating to communications resulted in ViewEngine and ViewApp objects not working properly on some machines. |
|
3604926 |
960484877 |
In a multi-galaxy environment, the addition of a new user into a OS security group having permissions to read/write to all galaxies resulted in a delay of those permissions being granted to the new user. |
|
|
3696628 |
3692747 |
N/A |
Due to an error in a DLL, startup of the Batch Management 13.1 IBMX service took too long. |
|
3565713 |
960462302 |
On a system using Application Server 2023 R2 P01 and SQL Server 2019 Standard (10.0), some templates failed to be checked in upon user request. |
|
|
3670746 |
960511388 |
Object Viewer showed incorrect values for a platform object's operating system. |
|
|
3610445 |
960477653 |
In SP 2023 R2, an auto-assignment input/output (I/O) update to a parent object caused an incorrect shift in its children's I/O assignments. |
|
|
3676886 |
960516692 |
Alarms that fell outside configured severity ranges were not logged in the event table and could not be queried by the historian. |
|
|
3635818 |
960481852 |
After deploying a ViewApp deployment, some system processes timed out, which resulted in undeployed communications objects and the system becoming unresponsive. |
|
|
3683117 |
960513654 |
After migration to SP2023 R2 SP1, all instance objects having graphics referring to an attribute in a namespace had warnings that the namespace references could not be resolved. The template objects had no warnings. |
|
|
3522547 |
960454407 |
After an upgrade from SP2020 R2 SP1 P01, language translations for alarms were not working in OMI. Only the original English text was provided. |
|
|
3701446 |
960519093 |
For a few object instances, the database issued a primary key violation. |
|
|
3696446 |
960451958 |
Danish language localization files were not working properly. Some of the "PhraseID" was missing after export of the localization file for an object. |
|
|
3685712 |
960477838 |
Scrolling through the Object List in the "Find" window resulted in a memory leak in the IDE. |
|
|
3708169 |
960533955 |
HF IMS 3607136 was ported to SP2023 R2 SP1. The HF addressed an issue where the user was seeing an error when "Advanced Communication" was turned on. |
|
|
3742415 |
960540946 |
An instance deployment failure occurred after the user made changes to the corresponding template. |
|
|
3618647 |
960491382 |
Instances created from a user-defined template did not display in the IO Devices View. The IDE had to be restarted for the instances to display in the IO Devices View so they could be assigned to a scan group. |