Application Server 2023 R2 release notes
- Last UpdatedOct 02, 2026
- 19 minute read
Application Server 2023 R2 includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.
New features and enhancements
Operations Control and connected experience
Operations Control is a way to license Application Server and other AVEVA System Platform products. It is a subscription license for either or both of the AVEVA Operations Control packages, Edge and Supervisory. Operations Control includes unlimited use of all products in the product package for your defined set of users. If you use Operations Control, you can also enable connected experience.
Connected experience enables Single Sign-on (SSO) for all Operations Control products on a given node. It supports common user authentication, authorization, and access entitlements across AVEVA Operations Control products. It includes:
-
User authentication via a single common user ID, configured and managed within AVEVA Connect.
-
User authorization via roles, groups, and rules (allow/deny).
-
Single Sign On: After you sign on to a supported product, subsequent sign ons to that product or other supported products on the node are automatic.
Connected experience requires access to the AVEVA Connect cloud repository from each node where you want to use it.
Support for import of SVG as an Industrial Graphic
The Industrial Graphic Editor supports import of Scalable Vector Graphics (SVG) as Industrial Graphics. You can perform the following:
-
Import an SVG into the Industrial Graphic Editor. The graphic elements automatically get converted to an Industrial Graphic, which can include many primitives.
-
Insert the SVG while using the Image icon from the Tools panel of the Industrial Graphic Editor.
-
Use SVG for the UpImage and DownImage on a button.
-
Use SVG for the Quality & Status display icons under Styles configuration.
Improved user interface
The System Platform IDE has an improved user interface that provides object status at a glance.
New OMI Web Client
The web client for use with OMI ViewApps is completely new. The new client offers better performance, a look and feel more like the desktop client, and an easier way to make ViewApps available from a browser: you just assign them to an instance of the new WebViewEngine object type.
OPC UA scripting
You can now use Application Server object scripts and/or Industrial Graphics scripts to call OPC UA servers. Method calls are executed in the OPC UA server through the OPC UA client, are supported through the OPC client in the OI Gateway Communication Driver.
Alarm latching and alarm dismiss
Latching is a new alarm state that can be enabled for a Galaxy. When latching is enabled, an acknowledged alarm that has returned to a normal value will continue to be displayed in the LATCHED alarm state. Alarms go to the LATCHED state if you ACK an alarm from UNACK_RTN state or return an alarm from ACK state. LATCHED alarms continue to be displayed to show that the alarms did occur. A dismiss command will return alarms that are in the LATCHED state to normal.
Application Server gRPC support
To enhance the security of Galaxy Repository operations, gRPC can be enabled for the System Management Server. This allows all GR-related operations, such as deploy/undeploy and start/stop to be executed over a secure channel.
Application Server resolved issues
|
Original Issue |
Related Issues |
Case/SR Number |
Description |
|
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. |
|
|
1860423 |
960174949 |
Intermittently, the Secured Write "Retrieving Reason Description" timed out and displayed the message |
|
|
1877088 |
960176481 |
In dynamic text referencing for Integer alarms, comment did not work with String arrays. |
|
|
1888024 |
960161993 |
While importing objects from a specific CSV file, the IDE closed with the message . |
|
|
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. |
|
|
1911736 |
960166135 |
While deploying a redundant engine, the bootstrap service encountered an error, stopping the engine and the platform. The error message generated was |
|
|
1914761 |
960180506 |
Some objects were not updating dynamic data on the Application Object Server. Redeploying the objects fixed the issue. |
|
|
1926125 |
960179494 |
Changing the SQL Server Compatibility level to 2019 made importing objects unacceptably slow. |
|
|
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). |
|
1939546 |
960191284 |
InTouch values were not being updated due to an issue with the NmxSvc service. |
|
|
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. |
|
|
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. |
|
|
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. |
|
|
1988488 |
2118272 |
960200700 |
After upgrading AVEVA System Platform, a Galaxy which had not shown any object errors or warnings showed over 3000. |
|
1991737 |
960201613 |
In some cases, after aaGR.exe was restarted, it took up to ten minutes to restart the IDE or OCMC (formerly SMC). |
|
|
1992148 |
960192426 |
The search feature in the System Platform IDE was unacceptably slow in certain system configurations. |
|
|
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. |
|
|
2024863 |
960206498 |
Using the mouse to select part of the text in a field did not work. |
|
|
2068077 |
960216050 |
When using Azure AD as the authentication provider, the IDE could not retrieve roles from Azure AD. Instead, it displayed the message . |
|
|
2074106 |
960194657 |
One customer's Application Servers were having a number of consistency issues, including an inability to deploy OMI applications. |
|
|
2086283 |
960188670 |
Intermittently, data and graphics were loading slowly in OMI applications. |
|
|
2101753 |
2287792 2130255 |
960221853 |
The OPC client failed when browsing items from the OPC server. |
|
2127825 |
960111993 |
There were delays in data updates in an OMI application when switching between primary and backup servers. |
|
|
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. |
|
|
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. |
|
|
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. |
|
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. |
|
|
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. |
|
|
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. |
|
|
2171127 |
960218196 |
The .AlarmInhibit setting was not retained when an Engine was redeployed. |
|
|
2178063 |
On a Japanese operating system, the Graphic Editor Save Confirmation dialog shows overlapped message text while saving a graphic. |
||
|
2178106 |
The AVEVA System Platform 2023 IDE became sluggish and unstable when creating 30 instances of an Operations Capability Object with PEM enabled. |
||
|
2179834 |
960238000 |
Deploying an OMI ViewApp after importing new objects into the working Galaxy failed with the message |
|
|
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. |
|
|
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. |
|
|
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. |
||
|
2184681 |
960235646 |
When using Azure AD as the authentication provider, only groups without a space in their names were listed when adding new roles. |
|
|
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. |
|
|
2192057 |
960230061 |
With several remote users connected to the GR node and using the IDE, the IDE would sometimes crash. |
|
|
2197662 |
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. |
|
2199153 |
960214756 |
At times, the ConnectionStatus of an RDIObject was Disconnected despite one of the DIObject being Connected. This occurred randomly. |
|
|
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. |
|
|
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. |
|
|
2292916 |
960253318 |
When using a redundant AppEngine, the View In Object Viewer feature did not automatically focus on the selected object. |
|
|
2293862 |
960245764 |
The Cross Reference tab for an object did not always show all cross references. |
|
|
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. |
|
|
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. |
|
|
2320864 |
960262032 |
During some installations, the AVEVA NmxSvc service was not set up properly. |
|
|
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 . |
|
|
2325393 |
960256256 |
Enhanced the logging of the application category component to better troubleshoot object deployment issues. |
|
|
2329110 |
960259732 |
Improved check-in performance after adding options to a template. |
|
|
2338358 |
960263766 |
In the galaxy browser, filtering by attribute did not work for device integration objects or RDI objects. |
|
|
2354864 |
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. |
|
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. |
|
|
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). |
|
|
2372346 |
960270563 |
Under certain conditions, when checking in a template that had had unrelated changes made, the AlarmSourceAttr attribute was locked in error. |
|
|
2384675 |
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. |
|
2396741 |
960275948 |
When "Enable advanced communication management" is enabled in the IDE, values for attributes stop updating when written to with a different datatype. |
|
|
2396784 |
2339386 |
960278840 |
The AVEVA Galaxy Repository Service (aaGR.exe) was sometimes crashing randomly. |
|
2412334 |
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. |
|
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. |
|
|
2422899 |
960284673 |
The Change Network Account dialog box was unreadable on a Chinese Operating System after upgrading to 2023 Patch 01. |
|
|
2422443 |
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. |
|
2435545 |
960278150 |
For some Galaxies, Galaxy load and validation took much longer after an upgrade to a newer version of AVEVA System Platform. |
|
|
2442091 |
960265213 |
In the IDE, the properties window for an attribute was always too small when it first opened and needed to be resized. |
|
|
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. These events did not cause any problem with using the IDE. |
|
|
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. |
|
|
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. |
|
|
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. |
|
|
2473677 |
960295264 |
In some cases, after an upgrade from 2014 P01 to 2023, customized alarm severity images appeared enlarged and distorted. |
|
|
2476051 |
960297286 |
The IDE opens the wrong object in the Object Editor if you perform these actions, in order:
|
|
|
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. |
|
|
2489138 |
960281235 |
Importing previously exported alarm messages sometimes failed with a timeout error reported in the log. |
|
|
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. |
|
|
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. |
|
|
2535753 |
960300675 |
Importing a template with I/O enabled overrode existing instances' settings for invertvalue and deadband. |
|
|
2564110 |
960303538 |
Restoring a Galaxy .cab file failed if there was more than one .mdf file in the database. |
|
|
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 . |
|
|
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 ". |
|
|
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. |
|
|
2588645 |
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. |
|
2620934 |
960327401 |
Deploying certain objects failed with this error in the OCMC log: . The engine became unresponsive and needed restarted. |
|
|
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. |
AVEVA OMI resolved issues
This table describes important resolved issues in AVEVA OMI. Many of these issues were also included in Patch Releases 01 and 02 of System Platform 2023. Some issues that have been fixed in this release may not be listed.
|
Original Issue |
Related Issues |
Case/SR Number |
Description |
|
1311645 |
1404698 |
960078748 |
Data in faceplate graphics was slow to update. |
|
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. |
|
1932837 |
960186425 |
Embedded vertical fonts appeared distorted in OMI ViewApps. |
|
|
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. |
|
|
1989797 |
960191143 |
Using a list view control to display users and groups in an OMI ViewApp actually displayed only users. Groups were not shown. |
|
|
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. |
|
|
2047527 |
960211554 |
An OMI ViewApp was sometimes crashing at runtime with an OWS09 error when a user clicked a layout. This behavior appeared random. |
|
|
2070745 |
960214465 |
If a pane was defined as multiple/tabbed, displayed values were disappearing when a different asset was selected in the ViewApp. |
|
|
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. |
|
|
2117058 |
2167966 |
960223948 |
Changing the graphics used in an OMI ViewApp and deploying the changes did not always update the graphics in the ViewApp. |
|
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. |
|
|
2167300 |
960227733 |
The MyPlatform attribute sometimes resolved to one of the other platforms in the Galaxy instead of to the current platform. |
|
|
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. |
|
|
2199335 |
960241624 |
After importing updated graphics into a Galaxy, the affected OMI ViewApps could not be deployed. The deployment failed with the message error event in the Galaxy node. |
|
|
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 was written to the log. |
|
|
2217089 |
960225037 |
When trying to show more than 100 items, the Content Presenter app had unacceptably poor performance and high CPU usage. |
|
|
2228133 |
960240919 |
Right-clicking on particular graphics in an OMI ViewApp caused the ViewApp to crash with the warning message |
|
|
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. |
|
|
2269408 |
960246297 |
You could not copy and paste text from a web site using the WebBrowser control in an OMI ViewApp. |
|
|
2283646 |
960253037 |
Some OMI VIewApps crashed during use with the message . |
|
|
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. |
|
|
2288058 |
960246824 |
When previewing an OMI ViewApp, selecting an asset that was not in the current area of the ViewApp caused OMI to crash. |
|
|
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. |
|
|
2311590 |
960257093 |
When a graphic was configured using Symbol Wizard options, animations in the graphic did not work in an OMI ViewApp. |
|
|
2314502 |
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. |
|
2330844 |
960254124 |
Under some conditions, it took a long time (more than five minutes) to deploy an OMI application. |
|
|
2359835 |
960271578 |
When opened in the InTouch web client, objects which contained duplicate references were not initializing correctly. |
|
|
2363862 |
None |
When invalid license information is entered in the Configurator, running an OMI application should write a message in the logger. This message was not being generated. |
|
|
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. |
|
|
2429049 |
960285754 |
When opening a third-party web site using the OMI WWWebAppCoontrols, a blank page was displayed after the login page. |
|
|
2489836 ] |
960296777 |
When using the .NET calendar app in an OMI ViewApp, the assigned background color did not appear in preview or at runtime. |
|
|
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. |
|
2590504 |
960322009 |
The Login popup was not accessible when the popup was opened with the ShowGraphic API with topmost configuration. |
|
|
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: . This was an intermittent timing issue which happened only rarely. |
|
|
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. |
|
|
3302427 |
960403458 |
Some graphics and associated text display incorrectly upon initial loading due to a slow callup time. |
|
|
3476032 |
The MDM process selection was unavailable when it should have been. |
||
|
3476046 |
960438667 |
The OMI application could not be properly started in read-only mode. |
|
|
3337425 |
960410447 |
For popup windows in the OMI application, the "HideSelf" button functioned incorrectly by instantly reopening popup windows that the user had closed. |
|
|
3413020 |
960408823 |
When using SSRS, the web browser in OMI is flipping back to the original date setting instead of using the updated date setting. |
|
|
3455483 |
960437228 |
After importing of a translation file, OMI did not start properly on request. |
Known issues
This section describes known issues that remain in Application SAerver 2023 R2 and in AVEVA OMI 2023 R2.
|
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:
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:
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:
|
|
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. |
|
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. |
|
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.
|
|
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." |
|
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. |