AVEVA™ Application Server and OMI 2023 R2 Patch 01 Readme

Original Issue

Related Issues

Case/SR Number

Description

IMS 2985894

960354373

When using the warm redundancy option, the aaCALWrap.exe process consumed a great deal of memory.

IMS 3018396

960341870

In some cases, after failover from the primary server to the backup server, some shelved alarms did not show in the shelved alarm list. The status of these alarms was still "shelved," they just did not appear when listing shelved alarms.

IMS 3023716

960375402

In a Multi-Galaxy configuration, the warning message Asb.Configuration SystemAuthenticationService.GetServiceBusPlatformConfiguration : Error occurred while communicating with database... was logged continuously on the GR node. This happened because the passphrase solution could not be found.

IMS 3039913

960380498

When System Platform was installed in a non-default location, such as on the D: drive, deploying WinPlatforms caused errors and warnings in the log and the platforms were not available in the OCMC Platform Manager.

IMS 3040483

960381315

Importing objects via a package (.aaPKG) file incremented the objects' versions by two steps.

IMS 3046335

960376548

Alarms which did not return to normal for a very long time (approximately one month) appeared in Historian with a negative duration.

IMS 3067809

960390378

Improved performance when deleting objects.

IMS 3081734

960352243

Objects that were set to Scan on Demand were not always added to the list for OI Server. As a result, these items were sometimes not scanned.

IMS 3109688

960387634

GRAccess could not write to any attribute that had a description field. Therefore, it could not create any object that contained any attribute with a description field.

IMS 3166242

960392759

In a warm redundancy configuration, after failover occurred, the EngineObjects[] attribute no longer contained a list of deployed objects.

IMS 3198388

960395617

When deploying an OMI ViewApp that included object wizards, the PCS Framework used more than 90% of the server's CPU.

IMS 3201271

960390809

If a galaxy was backed up using the Operations Control Management Console (OCMC), then a new galaxy was created from the backup, you could no longer connect to the original galaxy.

IMS 3242289

960400382

Collecting diagnostic information using the default configuration could create an unlimited number of files in the ArchestrA temp folder.

IMS 3259264

960403401

If an exported CSV file contains two objects which have attributes with the same name but different types (for example, one is Boolean and the other is a string), trying to import the CSV file fails with an error message.

IMS 3260947

960396305

Low priority alarms were being historized even though the galaxy was configured not to do so.

IMS 3261424

960404170

If you created an instance from a master template, then changed the default settings for an object wizard in the master template, you could not edit the instance or export it to a CSV file.

IMS 3264570

960404338

If the input source and output destination for an attribute associated with an object wizard were different, the output destination was set to --- if a change was made to the object template. This occurred even if the attribute was created in the object instance and did not exist in the template.

IMS 3270224

960405891

Importing a package file containing a graphic with multiple client controls which used the same dependent DLLs failed.

IMS 3270262

960405918

With multiple people using the IDE at the same time, the aaGR service crashed every 15 to 25 minutes.

IMS 3270629

3065034

960390172

Enabling the System Management Server slows down log in to OMI ViewApps at runtime.

IMS 3278545

960407805

Longer than expected time to failover from one server to another caused unacceptably long gaps in historized data.

IMS 3279907

960407298

There was a small memory leak in the module aaGlobalDataCacheMonitorSrv. Eventually, this caused the following warning to be written to the log repeatedly: Warning GlobalDataDistributionClientRuntime Synchronizing local data cache with global data repository has failed for 20 consecutive times. As the memory leak was very small, it could take several months before this warning appeared.

IMS 3281737

960406315

Post-upgrade from System Platform 2023 P02 to System Platform 2023 R2, AVEVA.IOMBLS.ServiceHost.exe caused memory leak and then stopped responding.

IMS 3282637

960407900

When using the Assign to option to assign an object to an area, typing in the list box the on the dialog did not move the list to match your entry.

IMS 3293455

None

Validating a large object sometimes caused a System.OutOfMemoryException and could cause the IDE to crash. For example, this could happen when migrating a galaxy that contained large objects.

IMS 3303557

960411247

The I/O Mapping view showed attributes for an instance even if those attributes were excluded by object wizard choices.

IMS 3318750

960391528

Closing and reopening the IDE caused deployed VIewApps to incorrectly show that they needed to be redeployed, even though they had not changed.

IMS 3324307

960417221

Checking in changes to a template and propagating the changes to its children could take hours and then fail, even though the IDE showed that it had completed successfully. When this occurred, the template remained checked out and error messages were written to the logger, starting with something like: Error WWCdi Error 80040E14: Description 'Violation of PRIMARY KEY constraint 'PK__#trimatt__38174EC39114E2BF'. Cannot insert duplicate key in object 'dbo.#trimattr'. The duplicate key value is (512616, 1041602300). Line:308, Store proc:internal_ow_streamline_dynamic_a appeared

Original Issue

Related Issues

Case/SR Number

Description

IMS 839617

960372244

If you performed these steps:

1. Created a layout and exported it to a package (.aaPKG) file.
2. Imported the package file to a galaxy that used a different regional setting--for example, if the original GR node was set to Dutch(Belgium) and the new GR node was set to English.
3. Tried to open the layout in the IDE.

   The layout would not open and you would see a message similar to this in the log: System: 221; 0; 0; 0 is not a valid value for Int32.

IMS 2507960

None

Faceplate popup graphics opened using ShowGraphic appeared at the top-right corner of the window instead of in the center.

IMS 2623094

960329675

Certain OMI ViewApps would sometimes freeze for five to ten seconds while a user was browsing object attributes.

IMS 2865278

960346739

When using Multi-Galaxy Communication, running an OMI ViewApp that retrieved data from another galaxy failed if Remote Desktop Services was installed and enabled on the node where the ViewApp was running. A warning was written to the log.

IMS 3023269

960368607

If more than 30 users were connected to OMI using RDP sessions, the following warning messsage was logged when a user closed an application: Release of global semaphore for the view application <app_name> failed. Deploy/undeploy operation may be blocked.

IMS 3031945

960379257

Addressed issues with tooltip text wrapping and combo box size when viewing OMI VIewApps in the OMI web client.

IMS 3032032

960379261

In the OMI web client, when interaction animation was applied to both an outer object and an inner object, the animation for the outer object overlapped the animation for the inner object. This could make it impossible to select the inner object.

IMS 3037177

960383529

Changing the background color for the ScreenCaptureAndPrint App at design time did not change the color when the ViewApp was opened in runtime.

IMS 3040067

960383669

When opening a faceplate graphic in a popup in the OMI web client, the popup window included a minimize button.

IMS 3046276

None

Changes made to graphics contained in a ViewApp were not always reflected at runtime after the ViewApp was redeployed.

IMS 3060440

None

After migrating a galaxy from 2023 Patch 02 to 2023R2, an exception could occur when previewing a ViewApp. A warning was written to the logger:

IMS 3060445

960385565

Content displayed through the ShowContent script in a tabbed multi-content layout pane with autofill enabled was not cleared when you changed the navigation node.

IMS 3061706

960386804

When a custom property was assigned with System.DateTime.Now and the SetCustomPropertyValue script was simultaneously called on the same custom property, it caused a memory leak. Eventually, this caused the viewer to crash with a SystemOutOfMemoryException error.

IMS 3199437

960392885

Switching between navigation items in the NavTree app in a ViewApp could caused the ollowing message in the log: System.ArgumentNullException: Value cannot be null.

Issue Number

Description

IMS 2918856

Note: This is an update to information found in the System Platform 2023R2 Readme file.

If the Trend Pen graphic element and the HistoricalTrendApp OMI ViewApp cannot retrieve historical data in the OMI web client, the reason may be that the Historian Server node name and port are not set in the AppSettings.json file on the node hosting the WebViewEngine. Unless the Historian Server is on the same node as the WebViewEngine, you must define the Historian Server system name and port number in AppSettings.json. Follow the procedure below.

IMPORTANT: You must follow these steps even if you already did so before installing the patch. Because we have added support for multiple Historian Servers to the web client, the format of the AppSettings.json file is changed in Patch 01. An AppSettings.json file from the 2023R2 release will not work with 2023R2 Patch 01.

For your reference, the patch installation makes a copy of the existing AppSettings.json file with a .bak extension. Do not just rename or copy this file for use with Patch 01. Because of the file format change, it will not work.

1. On the node hosting the WebViewEngine, make a copy of the file C:\Program Files (x86)\Common Files\ArchestrA\Services\proxyserver\appsettings.json for safekeeping. Then, open the original file in a text editor.
2. Find this section in the file:

    

   //"history-data-{serverName}": {

   //  "clusterId": "history-data-{serverName}",

   //  "CorsPolicy": "customPolicy",

   //  "Match": {

   //    "Path": "/history-data/{serverName}/{**catch-all}"

   //  },

   //  "Transforms": [

   //    {

   //      "PathRemovePrefix": "/history-data/{serverName}"

   //    }

   //  ]

   //},
   
   //"history-data-{serverName}": {

   //  "HttpClient": {

   //    "DangerousAcceptAnyServerCertificate": "true"

   //  },

   //  "HttpRequest": {

   //    "Version": "1.1",

   //    "VersionPolicy": "RequestVersionExact"

   //  },

   //  "Destinations": {

   //    "destination1": {

   //      "Address": "[https://https://{serverName}:32573/"

   //    }

   //  },

   //  "UseDefaultCredentials": "true"

   //},

3. Make two changes to this section:
   1. Uncomment the section by removing the // at the beginning of each line.
   2. Change each instance of {servername} to the server name of the Historian Server node. There are six, shown in bold in the sample above.
4. If you want to define more than one Historian Server so that users can choose the one they want at runtime, copy this section and change the server name to the one for the additional Historian. Repeat this as needed.
5. Save your changes and close the file.

Note: This is only one possible cause of failure for the HistoricalTrendApp and the Trend Pen element in the OMI web client. It may also be due to a security certificate issue. See the description of IMS 2918856 in the "AVEVA OMI Issues" section of the System Platform 2023 R2 Readme file for more information and the workaround steps for the security certificate issue.

IMS 3057574

Changes made to an element style (for example, adding an animation or changing the line color) are not reflected when an OMI ViewApp is opened with the web client, even if the ViewApp is redeployed, The changes do appear in the desktop client.

Workaround: Undeploy and redeploy the OMI VIewApp.

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 Unable to retrieve Reason Description.

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 Connection to the Galaxy Repository has been lost. Archestra IDE will shut down.

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 aaEngine.exe RedundancyPrimitiveRuntime2 Error INVALID HRESULT LINE 246 FILE <path>\RedundancyPrimitiveRuntime.cpp

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 Failed to retrieve groups. See logger for details.

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 Error occurred in generating the Asset Hierarchy.

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 Heap Create failed Not enough storage is available to process this command. 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 Failed to Ack the Alarm; Operational error: Alarm Acknowledged Already.

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:

1. Select an object (object A) in the Deployment pane.
2. Select an object (object B) in the Templates pane.
3. From the Home ribbon, select Open or Open read only. This correctly opens the Object Editor for object B.
4. Close the Object Editor.
5. Again, from the Home ribbon, select Open or Open read only.

   This time, the Object Editor opens for object A instead of object B, as it should.

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 Buffered enabled UDA <attribute name> does not have an input source.

IMS 2574326

960297592

After working correctly for a period of time, the Web Client display showed ###Hatch#. Restarting the ASBService service fixed the issue, but it re-occurred after periodically. Log showed Failed to connect PDMS-Web. Error description: "No connection was established at the service endpoint".

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 object is not registered to the engine 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: aaEngine.exe BaseRuntimeComponentServer INVARIANT FAILED LINE 729 .... 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.

Original Issue

Related Issues

Case/SR Number

Description

IMS 1311645

1404698

960078748

Data in faceplate graphics was slow to update.

IMS 1923348

1949157

960186853

The size of a faceplate graphic was being determined by settings in the template instead of the settings in the derived instance.

IMS 1932837

960186425

Embedded vertical fonts appeared distorted in OMI ViewApps.

IMS 1936152

960188224

When using the ShowGraphic() function to display a graphic in a popup window, the graphic was displayed correctly in an InTouch application but was shifted down in an OMI ViewApp.

IMS 1989797

960191143

Using a list view control to display users and groups in an OMI ViewApp actually displayed only users. Groups were not shown.

IMS 2034413

960195794

Using the ShowContent() function in an OnShow script to load secondary layouts into the panes of a "main" layout was unacceptably slow in some configurations, leading to time-out errors and one or more layouts failing to load.

IMS 2047527

960211554

An OMI ViewApp was sometimes crashing at runtime with an OWS09 error when a user clicked a layout. This behavior appeared random.

IMS 2070745

960214465

If a pane was defined as multiple/tabbed, displayed values were disappearing when a different asset was selected in the ViewApp.

IMS 2074100

960209524

When using the Trend Pen element in a graphic, with the FillTrend property selected, an extraneous vertical line appeared at either end of the Trend Pen element.

IMS 2117058

IMS 2167966

960223948

Changing the graphics used in an OMI ViewApp and deploying the changes did not always update the graphics in the ViewApp.

IMS 2132541

960226167

Opening an InTouch OMI application on a system that did not have InTouch installed caused multiple warning messages to appear in the logger.

IMS 2167300

960227733

The MyPlatform attribute sometimes resolved to one of the other platforms in the Galaxy instead of to the current platform.

IMS 2187523

960215199

When multiple instances in a model hierarchy contained common text in their names, the graphics contained in some of the instances did not always display correctly in an OMI ViewApp. For example, the autofill property did not work.

IMS 2199335

960241624

After importing updated graphics into a Galaxy, the affected OMI ViewApps could not be deployed. The deployment failed with the message Error occurred in generating the Asset Hierarchy error event in the Galaxy node.

IMS 2202531

960237108

Using a graphic in an OMI ViewApp to write to the Me.AlarmModeCmd attribute failed; the attribute value did not change. The message Write attempt to Me.AlarmModeCmd failed with error Operational was written to the log.

IMS 2217089

960225037

When trying to show more than 100 items, the Content Presenter app had unacceptably poor performance and high CPU usage.

IMS 2228133

960240919

Right-clicking on particular graphics in an OMI ViewApp caused the ViewApp to crash with the warning message "An unexpected error has been detected" "System.InvalidOperationException: This visual is not connected to a PresentationSource..."

IMS 2262836

960249147

In the Alarm App, the Details column and the Delete icon did not appear, making it impossible to delete or modify an existing query.

IMS 2269408

960246297

You could not copy and paste text from a web site using the WebBrowser control in an OMI ViewApp.

IMS 2283646

960253037

Some OMI VIewApps crashed during use with the message system.nullReference Exception for OnShow script on navigation to different symbol.

IMS 2286445

960247928

If a button configured with ShowContent to open the Web Browser app was added from within the ViewApp editor, the Web Browser App did not work. However, If the button was added from within the layout editor, it worked.

IMS 2288058

960246824

When previewing an OMI ViewApp, selecting an asset that was not in the current area of the ViewApp caused OMI to crash.

IMS 2290229

960254115

When an embedded graphic included a Windows Common Control (WCC), changing the embedded graphic's size also changed the embedded graphic's position in the parent graphic.

IMS 2311590

960257093

When a graphic was configured using Symbol Wizard options, animations in the graphic did not work in an OMI ViewApp.

IMS 2314502

IMS 2219591

960243452 960273575

In a multi-Galaxy environment, you could not write to a remote Galaxy attribute from a popup graphic in an OMI ViewApp.

IMS 2330844

960254124

Under some conditions, it took a long time (more than five minutes) to deploy an OMI application.

IMS 2359835

960271578

When opened in the InTouch web client, objects which contained duplicate references were not initializing correctly.

IMS 2363862

None

When invalid license information is entered in the Configurator, running an OMI application should write a Demo mode activated message in the logger. This message was not being generated.

IMS 2384559

960260957

After attempting to add an attribute with an invalid name and then deleting it, if any other attribute was duplicated, it caused the IDE to crash.

IMS 2429049

960285754

When opening a third-party web site using the OMI WWWebAppCoontrols, a blank page was displayed after the login page.

IMS 2489836 ]

960296777

When using the .NET calendar app in an OMI ViewApp, the assigned background color did not appear in preview or at runtime.

IMS 2496295

`

960297291

When the initial state of the layout was set to full screen, a faceplate containing a graphic did not display correctly. Its appearance was deformed and too small.

IMS 2590504

960322009

The Login popup was not accessible when the popup was opened with the ShowGraphic API with topmost configuration.

IMS 2528294

960307870

If an alarm caused a popup containing the alarm control to open while the user was moving from one page of a ViewApp to another, the OMI runtime crashed with this exception: The calling thread cannot access this object because a different thread owns it. This was an intermittent timing issue which happened only rarely.

IMS 2609502

960302414

Changed the default border thickness for the ContentPresenter app from one (1) to zero (0) so if padding is set to zero, no border is shown.

Issue Number

Description

Security mismatch

Some connected experience configuration scenarios can result in unexpected behavior.

Scenario 1: Ability to access security tabs when an unsupported authentication mode has been configured.

If a galaxy using Galaxy security has been created without connected experience, and then connected experience is configured, if you:

• Connect to the galaxy and change the authentication mode to Authentication Providers.
• Add a new group and cancel the changes.
  You will be able to access the security tabs in an unsupported authentication mode.

Scenario 2: Cancelling read-only message box in the security editor closes the IDE.

If a galaxy using Galaxy security has been created without connected experience, then the IDE is closed, and then you configure connected experience and login to the IDE with an AVEVA Connect user, when you:

• Connect to the galaxy and click Yes when the dialog appears.
• Launch a second instance of the IDE and connect to the same galaxy.
• Navigate to the security page in the second IDE. A dialog opens and asks if you want to open in read-only mode.
• Click No.
  The IDE closes (the IDE should not close in this scenario).

Scenario 3: The Authentication Providers security mode can be enabled without configuring any roles.

If you connect to a galaxy and select Authentication Provider security, and then navigate to the Roles tab, but:

• You do not add any roles.
• Click Save.
  The IDE will shut down. Note that changes should not be allowed in this scenario since no role is configured and there is no Administrator login support under Operations Control mode.

IMS 2897808

The SignedAlarmAck feature is not currently supported for Application Server and AVEVA OMI when AVEVA Operations Control connected experience is configured. Attempting to sign an alarm acknowledgement fails, and an error message is generated that warns of incorrect user credentials.

IMS 1869732

If the domain controller goes down and at the same time, an IDE user attempts to perform a change user operation, there is a slight possibility that Windows will display a crash dialog for the IDE. Note: This is a very rare scenario.

Workaround: Restart the IDE to proceed.

IMS 1861501

Endpoints on remote nodes, including redundant SSO nodes, are not discovered when the Global Discovery Server is not available. As a result, logging in to a Galaxy using Azure AD credentials when the security mode is Authentication Provider is not successful.

Workaround: For discovery of any endpoints that are not on the local node, then a GDS (global discovery) server MUST be available for discovery. You can configure a secondary GDS to avoid non-discovery, which can occur when the redundant SSO is on a different node. You can configure secondary discovery servers in the System Platform IDE. See the Application Server help for instructions on configuring multi-galaxy communication. You can also configure a secondary discovery server through the PCS Configuration utility.

1. Open the PCS Services Configuration utility
   C:\Program Files (x86)\Common Files\ArchestrA\Services\aaServiceConfiguration.exe
2. Open the Configure link (near the top of the utility window), the select Discovery Service from the menu.
3. Enter a secondary node name for both the Local and Cross solution.

   "Local solution" is equivalent to Local Galaxy server in the System Platform IDE, and "Cross solution" is equivalent to Multi-Galaxy server.

IMS 1846869

When System Platform is configured with a standalone System Management Server (SMS) and Authentication Provider, other nodes pointing to the SMS node may not be able to reach the Authentication Provider on the SMS node for user authentication.

Workaround: Use one of the recommended SMS system configurations described in the System Platform Installation Guide. Refer to the section "Recommended SMS Architecture Utilizing an Authentication Provider."

IMS 1842703

If, after configuring a node to connect to an existing System Management Server, you choose to make the node a redundant SSO server, the Configurator does not indicate that the Authentication Provider configuration parameters must be configured (green checkmark is still shown and the Configure button is grayed out).

Workaround: Select the Authentication Provider configuration option and configure the parameters as described in the System Platform Installation Guide.

CR L00138837

AppEngine can crash due to calls made to API dlls even when using try/catch. This issue is specific to Nullable data types. The recommendation is to use wrapped API DLLs in Application Server scripting.

TFS 1404918

If a network failure occurs on the active engine node and Warm Redundancy is enabled, the last value is shown as NULL for slow-changing Tags.

Workaround: Perform a SQL Insert or CSV Insert for the tag in question on the Historian side. This will restore the value in the Historian trend.