Application Server 2017 Update3 SP1 Patch01

Материал из archestra.info
Перейти к: навигация, поиск

AVEVA™ Application Server 2017 Update 3 SP1 Patch 01 Readme

AVEVA™ Application Server 2017 Update 3 SP1 Patch 01 Readme

Last revision: 5/26/2020

In This Document

About this Readme

About this Patch Release

Applying Application Server 2017 Update 3 SP 1 Patch 01

About this Readme

This document includes information about AVEVA™ Application Server 2017 Update 3 SP1 Patch 01. It updates the previous Readme file included with Application Server 2017 Update 3 SP 1. The entire Application Server 2017 Update 3 SP 1 Readme is included in this document. It follows the Patch 01 sections.

About this Patch Release

The System Platform 2017 Update 3 SP 1 Patch 01 release resolves a number of issues, documented in each product Readme file. This Patch release also provides new functionality. For a description of the new functionality, see the System Platform 2017 Update 3 SP 1 Patch 01 Readme, available for download with the Patch Manager.

Important!

  • Installation - Application Server 2017 Update 3 SP 1 must be installed before you can install this patch.
  • Coexistence - If Application Server and InTouch HMI are installed on the same node, they both must be upgraded to version 2017 Update 3 SP 1 Patch 01.

If you plan on upgrading to System Platform 2020:

  • Some Resolved Issues (Hot Fix CRs) included in this patch are not built into System Platform 2020. This can cause previously resolved issues to reoccur if you upgrade to System Platform 2020 after applying this patch. Therefore, if you upgrade to System Platform 2020 after applying this patch, you may need to apply specific Hot Fixes to correct issues that occur within your upgraded System Platform 2020 machine. Contact AVEVA Global Customer Support (GCS) to obtain the applicable Hot Fix(es).
  • Resolved Issues for this patch that are NOT INCLUDED in System Platform 2020 contain a note in the description of the issue stating that the issue may require a separate Hot Fix. See Resolved Issues - Application Server 2017 Update 3 SP 1 Patch 01 for more information.

    IMPORTANT: This patch cannot be applied to System Platform 2020. Instead, contact AVEVA Global Customer Support (GCS) for the specific Hot Fix(es) that are applicable to your installation.

    Note: The Resolved Issues in this Patch that are not built into System Platform 2020 will be included in the follow-on release, System Platform 2020 R2.

Applying Application Server 2017 Update 3 SP 1 Patch 01

Close any anti-virus programs running on the computer before you update Application Server with Patch 01.

Apply this patch only to Application Server 2017 Update 3 SP 1 (version 17.3.100). You can check the version number of Application Server in the Control Panel from Control Panel by selecting Programs and Features.

Important!

This patch must be installed on all Application Server nodes. On nodes where both Application Server and InTouch are installed, you must install Application Server 2017 Update 3 SP 1 Patch 01 and InTouch 2017 Update 3 SP 1 Patch 01 in order for them to coexist.

This patch can only be applied to Application Server 2017 Update 3 SP. It cannot be applied to any other version.

Before installing the patch, make sure you have created known good backups of all installed Galaxies. To create a backup of your Galaxy:

  1. Access the Galaxy Database Manager in the System Platform Management (SMC) console.
  2. Expand the Galaxy Database Manager and select the Galaxy.
  3. On the Action menu, click Backup. Follow the prompts to complete the backup operation for each Galaxy.

If the System Platform IDE connects remotely to the Galaxy Repository on another computer, apply Patch 01 to both nodes. A remote connection between the IDE and the Galaxy Repository fails if the nodes are at different versions of Application Server.

As a general workflow, patch the GR node first, followed by the run-time nodes.

  • A System Platform IDE node still at version 17.3.100 cannot connect to a remote GR node updated with Patch 01 (version 17.3.101).
  • A System Platform IDE node updated with Patch 01 cannot connect to a remote GR node that has not been updated with the patch.
  • Prior to running the patch installer, you must undeploy the platform or stop the platform from Platform Manager in the SMC. Exit all applications including the System Platform IDE, InTouch OMI ViewApps, the InTouch OMI Application Manager, and/or InTouch WindowMaker and InTouch WindowViewer, if installed and running.

    IMPORTANT: When you reboot a platform, you must set each engine OnScan. Failing to set engines OnScan can result in reference resolution issues.

  • Prior to applying Patch 01 on the GR node, check that any active remote IDE sessions are disconnected. Patch 01 requires that all System Platform-related processes are shut down and may require a reboot.

Resolved Issues - Application Server 2017 Update 3 SP 1 Patch 01

Application Server 2017 Update 3 SP 1 Patch 01 resolves the following issues:

Originating Issue

Related Issues

Description

L00150650

 

SR 59010331: The NmxSvc service was not able to communicate with remote platforms and appeared hung, even though the binding order appeared to be correct.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00151080

L00152339 L00152645 L00152893

SR 103154517; SR 75710006: Deployment of an InTouchViewApp required up to several hours to complete.

L00151129

 

SR 59210153: When changes were made to a master template that had multiple derived templates and instances, checking in the master template could take hours to complete.

L00152735

 

SR 103156900: When an AppEngine object that hosted multiple objects was deployed numerous times in a testing scenario, deployment of the AppEngine, occasionally, was not successful. However, even when deployment was not successful, the IDE showed that the AppEngine was deployed.

L00152893

L00152339 L00152645 L00152645 L00153024

SR 75710006; SR 103155283; 103157273:  Deployment of an InTouchViewApp, or restoration of a .CAB file, required up to several hours to complete.

L00153503

 

SR 48912544: Migrating a Galaxy from version 2014 R2 SP1 to version 2017 Update 2 resulted in "load failed" errors in the logger related to the Graphic Library.

L00153635

 

SR 76410095: An attribute configured as write-only on a Redundant IO object could not be written to and displayed a configuration error. If the attribute was configured as read/write, the attribute worked correctly.

L00153714

 

SR 39911566; SR 39911558: In multi-galaxy environments, logging off from the system sometimes caused a memory leak in a aaServiceHost32.exe process related to MxDataProvider.DLL. The memory leak could cause the system to stop responding.

L00153750

 

SR 103167531: The Embedded Alarm Client (EAC) did not include Russian language support.

L00153797

 

SR 198110153: Memory utilization of the IOMBLS service was not optimized, which could result in out-of-memory exceptions and deployment issues.

L00153841

 

SR 103159886: Faceplate mode behavior and inheritance at run time did not function as it was documented.

L00153888

 

SR 57211165: A user could only use Smart Card Authentication to log into an InTouch application if the user was already logged into machine with same account used for the ArchestrA UserValidator service.

L00153954

 

SR 103160473: An updated script did not propagate after saving and checking in the object. An error message was logged that "Sql Command failed when execute storage procedure internal_delete_old_packages_after_checkin."

L00154032

 

SR 103160469: Many error messages were logged after making a change to, and then checking in a symbol. Error messages included messages about overridden custom properties, general load failures, invalid parameters, etc.

L00154035

L00156848

SR 63511036; SR 49911254: When a User Defined object was first deployed, the EngUnits value was empty when viewed in the Object Viewer (quality was good). The issue could be resolved by making a change to the object and redeploying it.

L00154049

 

SR 39911602: Using a GRAccess API call to deploy all instances resulted in only one instance being deployed.

L00154075

 

SR 103161062: Entering a very large value for the Rollover value property under History Extension caused a constraint violation in the Historian.

L00154081

L00156451

SR 63912311; SR 63913352: An IO object with the output extension configured resulted in the following error message to be displayed in the logger: INVARIANT_FAILED - line 1324 file OutputExtensionRuntime.cpp

L00154105

 

SR 59514096: After making changes to a template with a large number of derived instances, deployment of the application objects stopped part way through the deployment.

L00154241

 

SR 54411541: If the initial value PV.Description of an AnalogDevice was left blank, and PV was configured for historization, the objectname.Shortdesc was not set as Description in the HIstorian (Shortdesc should have been used if Description was blank).

L00154301

 

SR 103158084: While creating a new galaxy on fresh install, errors were logged, and the new galaxy could not be opened or edited. Related errors were found while running Change Network User, in addition to aaPIM problems with fully-qualified domain names or non-flat domain names.

L00154350

 

SR 103162044: In the Assign To Device dialog box used for assigning DI objects to an IO device, the DI objects were not listed alphabetically, making it difficult to find the applicable object.

L00154357

 

SR 103161805; SR 103161861: ShowSymbol action, in either an animation or a script, did not function within an Industrial Graphic embedded in any native or third-party InTouch OMI app.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00154361

 

SR 57211319: The Alarm and Events configuration settings were not retained in a Galaxy created from CAB backup, and instead, the settings were reset to their defaults.

L00154449

 

SR 103161036: A large number of duplicate event entries were generated in the Alarms and Events viewer in the EAC, if communication with the PLC was interrupted.

L00154732

 

There were several issues related to the first release of the AVEVA Telemetry Server in System Platform update 3 SP1. These involved showing the wrong data data quality when a network connection was disabled, and failure to receive buffered data after a deploy/redeploy operation, as follows:

  • A User Defined attribute configured for buffered I/O from the Telemetry Server did not receive buffered data after the User Defined Object was undeployed and then redeployed.
  • The quality of a Telemetry Server reference remained good when the network adapter on the Telemetry Server node was disabled.

    A Field Attribute configured for buffered I/O with deadband on a Telemetry Server data point did not show bad quality when the network was disconnected.

L00154777

 

SR 103162743: After upgrading from System Platform 2017 Update 3 to System Platform 2017 Update 3 SP1, the behavior changed for a graphic called by the ShowContent() function. After the upgrade, the graphic would close, instead of being shown, when navigating between two objects.

L0155150

 

SR 103162348: ShowGraphic script that was using an On MouseOver Action script did not show the graphic where it was configured to show.

L00155185

 

SR 48912696; SR 48912612: Deploying an $InTouchViewApp took much longer in System Platform 2017 Update 3 SP1 compared to System Platform 2017 Update 2.

L00155240

 

SR 103159957: A graphics-related error message was displayed after a Galaxy backup was restored and an Intouch ViewApp was deployed to a remote node. The message "Graphic not available" was shown in the Intouch application. Some .vef files were missing on the GR node as well as on the remote node.

L00155272

 

SR 103163841: When the order of script execution was changed and then the object containing the script was deployed, the script execution order was not updated at runtime.

L00155276

L00155440

SR 103163522; SR 103164254: After a Microsoft API was used in an action script, the existing content of the Industrial Graphic was lost.

L00155352

 

SR 63511231: In a large galaxy with more than 100 platform nodes, creating a single new object instance was very slow.

L00155455

 

SR 10419182: It took longer than expected to check in an object that was associated with a device through IO Auto Assignment, in a galaxy with multiple nested levels of objects, and with a large number of instances and templates.

L00155609

 

SR 51513684; SR 103160723: An aaBootstrap memory and handle leak was associated with InTouch for System Platform 17 Update 2, especially on Windows 10 systems.

L00155743

 

SR 103164614: After a varying number of reboots of the primary Application Object Server, the Standby engines kept restarting but never reached the standby-ready mode.

L00155774

 

SR 103162435; SR 103162436: Chinese characters sometimes appeared in the log viewer instead of English text.

L00155858

 

SR 103164347: When Hierarchy Navigation buttons were enabled, and a slide-in pane was added, the navigation buttons moved from the bottom-center to the bottom-right of the pane.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00155863

 

SR 103164207: When an InTouch run-time node was restarted, it resulted in both the WinPlatform and AppEngine crashing. Both would then have to be restarted manually from Platform Manager.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00155899

L00156311

SR 103166318: The StartTime property of the Trend Pen graphic could not be set at run time.

L00155932

 

SR 103165395: The InTouch OMI WebApp did not use the regional operating system setting for displaying decimal values (a period was used as the separator instead of a comma).

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156242

 

SR 103164938: Performing a Galaxy Load broke the link between symbol wizards and the graphics as displayed in the InTouch OMI run time.

L00156333

 

SR 103165980: The on-screen keyboard for InTouch OMI ViewApps could present security concerns, depending on how InTouch Access Anywhere was deployed and network topology.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156334

 

SR 103165479: After upgrading from System Platform Update 3 to Update 3 SP1, InTouch OMI ViewApps would sometimes fail to launch, and an accompanying warning related to the ViewApp navigation model was logged.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156431

 

SR 103165982: Using WWWebAppControls introduced a security issue.

L00156473

 

SR 103166596: After a user entered their credentials and logged in to an InTouch OMI ViewApp, User Logon popup closed, but any panes that were populated by using a ShowContent script were then hidden.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156474

 

SR 103166255: With several InTouch OMI ViewApps were running on different screens, popups were not displayed on the correct screen when the popups were opened via Show Symbol.

L00156542

 

SR 73610137: When a three-finger swipe gesture was used in a touch-enabled InTouch OMI ViewApp to slide in a pane with WWWebAppControls, closing the pane caused the cursor to disappear.

L00156633

 

SR 73610144: A button triggering a script to change a custom property value in an embedded symbol did not update the value of a custom property i n the container graphic, as the script was designed to do. Instead, a message was logged.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156802

 

SR 63212608: Using redundant AppEngines in Application Server 2017 Update 3 SP1 resulted in issues reading attribute values correctly.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156825

 

SR 103166683: The source topic items sent via MQTT had a different syntax than the topic items received by the OI Gateway; all letters were capitalized on the OI Gateway, while MQTT is case-sensitive).

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156834

 

SR 63810143: No all communications quality codes were transferred from the AVEVA Telemetry Server to Application Server; only good (192) and bad (0) quality codes were sent.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156841

 

SR 22210557: The addition of new users to a Galaxy (security enabled) was not propagated to client nodes.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156915

 

SR 101364576; SR 27811645: An AppEngine stopped working infrequently and randomly, and an error message, NmxCallback->DataReceived to local engine 4 failed with error 0x800706be. Engine <number> is unavailable. Please restart the engine."

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00156998

 

SR 103167805: In System Platform 2017 Update 3 SP1, when objects containing duplicated friendly names/aliases were imported into a galaxy, the import did not succeed and a message, "Unable to update the friendly name during import" was logged.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L000157041

 

SR 103168029: Attempting to backup a Galaxy with GRAccess when the logged-in user belongs to the aaConfigTools group but not Administrators did not succeed, and an error, "cmdNoSuchGRNode "Operation failed because the given GR Node is invalid"" was logged.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157103

 

SR 24414237: In the Trend Pen, attempting to write to the TimeMode property to set a fixed time mode did not succeed, and the Trend Pen instead behaved as if it was in moving mode.

L00157107

 

SR 103167824: The MapApp did not start at run time. This was caused by an inability to start the HTML5 graphics web server.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157206

 

SR 103168446: When the ShowGraphic() script function was used to open an Industrial Graphic in an InTouch OMI ViewApp, the graphic opened with a thin blue border.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157256

 

SR 103168239: The SendKeys() script function generates a "File Not Found" exception when executed from an Industrial Graphic.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157305

 

SR 103169185: When a gradient color was used, the gradient rendered differently at run time in an InTouch OMI ViewApp than it appeared during development. The gradient rendered correctly in both WindowMaker and WindowViewer.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157330

 

SR 103167351: Redundant platforms did not failover, and if a deployed platform was stopped, it became unavailable and could not be restarted.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157396

 

SR 103168721: When the ShowGraphic() script function was used with a layout name configured as the GraphicName property, it did not open the layout as a modeless window.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157417

 

SR 40711173: Show Halo remained visible around a Hotlink for a prior graphic, even after the symbol was no longer being displayed.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157420

 

SR 40711172: In an InTouch OMI Application copied to a node without a System Platform product installed, navigation worked but action was delayed.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157432

 

SR 103169178: Even though pane borders in a layout with multiple panes were set to be invisible, borders appeared during runtime.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157533

 

SR 22210576: Nodes in a network configured with a DHCP server were sometimes assigned a partial IP address through the NMXService, even though they had not yet received an address from the DHCP server.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157567

 

SR 78610061: After an embedded graphics was deleted from a container graphic, references to the deleted graphic still remained. The references also remained if the owning object was imported.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00157669

 

SR 51316633: After upgrading from System Platform 2014 to System Platform 2017 and later, scripts that used "==" for string comparison were no longer valid when used with dynamic arrays. (However, the StringCompare() method did work.)

L00157708

 

SR 103169334: When using a template with an object wizard and a linked symbol that contains scripts referencing an embedded symbol within the linked symbol, warnings were logged that references from the embedded symbol were missing.

L00157731

 

SR 12615055: While navigating the asset hierarchy using the BreadCrumb App or NavTree app, a warning that the "Hierarchy item for the given hierarchy path "XXXXX" is not found," and it was not possible to navigate the application.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158019

 

78610069: After failover, the InvertValue of an attribute was set to true, and thus, did no longer reflected the correct attribute configuration.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158022

 

SR 103167644: After migrating an InTouch application from version 2014 to 2017 Update 3 SP1, issues with ArchestrA objects not working were noted occasionally after the application was deployed, and errors appeared in the logger.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158104

 

SR 57211661; SR 76410095: An attribute configured as write-only on a Redundant IO object could not be written to and displayed a configuration error. If the attribute was configured as read/write, the attribute worked correctly.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158130

 

SR 103170046: A symbol was corrupted when it was linked to from a template, which resulted in an the symbol showing as empty within the template. When an attempt was made to remove the symbol, the IDE stopped working and closed.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158159

 

While converting Field Attributes in MRO Galaxies, errors were logged from the IOMBLS service and the aaGR process restarted during the attribute conversion.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

L00158169

 

SR 37613361; SR 37613354: While importing objects, and with multiple users connected to the IDE, the IDE stopped working and an error was logged that communication to the target machine failed.

Note: If you upgrade to System Platform 2020 after applying this patch and experience this issue, contact AVEVA GCS and request the applicable HotFix (CR) number.

--- End of Patch 01 Readme ---

Application Server 2017 Update 3 Service Pack 1 Readme

Last revision: 5/31/2019

About This Readme

This Readme provides information about important resolved and known issues for Application Server 2017 Update 3 SP1 (version 17.3.100).

For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the System Platform Readme, which is located in the root folder of the System Platform installation media.

Readme files from previous releases of Application Server are posted to the Product Hub section of the Global Customer Support (GCS) web site. You must log in to access the GCS Product Hub.

Resolved Issues

This section describes important resolved issues in Application Server 2017 Update 3 SP1. The following is not a comprehensive list of all resolved issues.

Originating Issue

Related Issues

Description

L00150471

L00148617

SR 103150360: The aaGR.exe process exhibited increased memory usage when running a GRAccess Toolkit application that used the upload runtime changes method.

L00150784

 

IDE startup time increased as the size of the galaxy increased.

L00150962

 

SR 103152539: Scripts in ArchestrA graphics did not execute in run time unless a minor edit, unrelated to the script, was made to the graphic.

L00151195

L00145757 L00150787 L00150789

SR 22111511; SR 103152282; SR 103153693: When changes were made to Field Attributes on a template, and the changes were propagated to derived objects and the objects were deployed, some associated graphics in the application were shown as not available during run time.

L00151537

 

SR 63211290; SR 42410739: When the "MyArea" reference was used to specify execution order in a relative object, a warning was entered in the logger.

L00151563

L00152166

SR 103155444; SR 59513787: The number of GDI objects in an InTouch OMI application kept increasing during run time when when bitmaps were used in graphics.

L00151642

 

SR 103154684: Importing a csv galaxy dump file resulted in portions of SetAttribute failure messages being displayed out of range of the import dialog window, and could only be viewed by using Ctrl + A / Ctrl + C to select and copy the dialog to a text editor.

L00151858

L00153163

SR 48912327; SR 103159276: While using the InTouch OMI NavTreeControl or NavBreadCrumb Control at run time to navigate the asset hierarchy, navigation stopped working and the error message "Hierarchy item for the given hierarchy path xxxxx is not found" was entered in the logger.

L00151955

 

SR 57211014: In System Platform 2017 Update 2, an unconfigured IO-extended attribute with bad quality did not write the attribute value. However, in System Platform 2014 R2 SP1 the attribute value was written. Scripting behavior in System Platform 2017 Update 3 has been changed to write the attribute value and match the legacy behavior found in older releases.

L00151991

L00153112

SR 103155822; SR 103159322: Reading a MyContainer attribute from a parent object was not always successful in retrieving the data.

L00152059

 

SR 6911759: In the InTouch OMI AlarmApp, the quality of the alarms was shown as bad, but quality was good in the Object Viewer and the Intouch Alarm Viewer.

L00152139

 

SR 57211084: After migrating a galaxy from System Platform Update 2 to Update 3, deploying and undeploying the galaxy resulted in warnings and errors in the logger .

L00152161

 

SR 37115318: The ArchestrA Platform Install Manager (aaPIM) process generated errors during deployment in a workgroup-based System Platform installation.

L00152166

L00151563 L00152324

SR 59513787: A memory error occurred (OutOfMemoryException) and the InTouch OMI application stopped responding once memory consumption reached about 3200 MB.

L00152231

 

SR 103156171: After a ViewApp ran for several minutes, OnDataChange events no longer triggered the application to update.

L00152419

 

After migrating from Wonderware System Platform 2012 to 2014, and to then System Platform 2017 Update 1, numerous GetRepositoryTimeStampException warning messages stating that "value was either too large or too small for an Int32" were generated from the Galaxy Repository.

L00152466

 

SR 14812913: A script to reconnect a DDESuiteLink Client object to the SuiteLink Server timed out or took a long time to connect, and did not provide details in SMC Logger about the disconnect event.

L00152513

 

SR 103157500: When redundant AppEngine objects were deployed as a pair, changes made to an Area object assigned to the redundant AppEngine resulted in instances disappearing from the Object Viewer.

L00152558

 

SR 48912450: After a platform was stopped, and then the platform AppEngines were restarted, an attribute remained stuck with initializing quality, and thus could not be written to by another object.

L00152606

 

SR 103157936: Fill animation did not work properly on grouped graphic shapes in an InTouch OMI application, if the fill animation color was the same as the fill color specified for one of grouped shapes.

L00152639

 

 

 

SR 103156060: While importing an aaPKG file, attribute name conflict messages were logged for all attributes with extensions. This was followed by a warning, "Violation of PRIMARY KEY constraint."

 

L00152687

 

SR 103157793: Pane separators were visible in an InTouch OMI ViewApp even though they were configured in the layout as invisible.

L00152824

 

When some run-time nodes had been operational for a period of time without a restart, the NmxSvc service failed randomly, which resulted in lost data.

L00152850

 

SR 63510420: Attribute quality needed about 10 seconds to become good when the backup engine was deployed before the primary engine, or when only the the backup platform was active.

L00152874

 

During check-in of an ITMEViewApp derived template, a COM Error was logged: Primitive Configtime SetHandler(124.100) Failure: Unable to cast COM object.

L00153055

 

SR 951172003: A Skelta WorkflowGateway object did not work in a redundant environment if the engine was located on the GR node and engine status was Standby Ready.

L00153327

L00153384

SR 31613807; SR 10418841: A corruption in PBRefCache.bin resulted in an anonymous engine file being written to every second and updates to graphics stopped.

Known Issues

This section describes known issues that remain in Application Server 2017 Update 3 SP1.

Change Request

Description

L00144613

When Application Server has been installed/upgraded to System Platform 2017, and the ArchestrA Network User account is a local user (not a domain account), an OPCClient object cannot read from a DA Server on a remote node running Windows Server 2008 SP2.

This issue is confined to environments where a DA Server is running under the Local System Account on a Windows Server operating systems prior to the 2008 R2 release. Windows Server 2008 R2 and later are not affected by the issue.

Workarounds:

If networking is via a Windows workgroup, the only workaround you can use is to enable everyone permissions for anonymous users.

  1. On the WSP 2017 node, go to Local Security Policy > Local Policies > Security Options.
  2. Enable the security policy Network Access: Let everyone permissions apply to anonymous.
  3. Restart the computer.

If networking is domain-based, you have a choice of two workarounds.

First option (domain-based networking only):

  1. On the DA Server node, open the Registry editor and navigate to key path
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA
  1. Create a REG_DWORD value named UseMachineID and set the value to 1.
  2. Open the System Management Console (SMC), deactivate the DA Server and then activate it again.

Second option (domain-based networking only):

On the DA Server node, specify that the DAServer process runs as a domain user account.

  1. Click Windows Start, type services.msc in the Search box, and then press Enter.
  2. In the details pane, select and right-click the DAServer process, and then click Properties.
  3. Select the Log On tab.
  4. Under Log on as, select This account (do not use Local System account).
  5. Enter the domain user account name and password, and then click OK.
  6. Open the System Management Console (SMC), deactivate the DA Server and then activate it again.

624132

On some monitors, the ArchestrA IDE shortcut menus are displayed partially off-screen, making them difficult to read or make a selection.

Workaround: This workaround is documented on a Microsoft Community forum and is summarized below: (see
https://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/context-menu-going-left-not-right/a09e42df-fdd0-45fc-a501-7e5e145a22b3?auth=1)

Note: This workaround is applicable to all supported Windows and Windows Server operating systems.

  1. Press the Windows logo key+R to bring up the Run dialog box.
  1. In the Open line, copy and paste the following text:
  2. shell:::{80F3F1D5-FECA-45F3-BC32-752C152E456E}
  3. Click OK.
  4. This starts the Tablet PC Settings configuration dialog, even if you are not working on a Tablet PC.
  5. Select the Other tab.
  6. In the Handedness section, select the Left Handed option.
  7. Click OK.

773741

Warning messages appear in the SMC log file when migrating an application created with Wonderware System Platform R2 SP1 to System Platform 2017. These messages are in response to symbol functionality present in the application created with Wonderware System Platform R2 SP1 that is not available with a System Platform 2017 ViewApp.

785665

Under certain circumstances, when migrating a CAB file from an older galaxy that contains ArchestrA Graphics and utilizes the Historical Trend control to System Platform 2017, the migration may stall at some point and fail to complete. No error message will be displayed.

Workarounds: The workaround varies, depending on the System Platform version that you are migrating to WSP 2017:

Migrating from WSP 2014 or WSP 2014 P01:

Copy the following HistorianClient-2014 binaries from C:\Program Files (x86)\ Common Files\ArchestrA to
C:\Program Files (x86)\ArchestrA\Framework\bin.

Note: If the same computer is upgraded to WSP 2017, the 2014 binaries can be taken from the WSP 2014 installation CD.

  • aaHistClientDatabase.dll
  • aaAFCommonTypes.dll
  • aaHistClientUtil.dll

Migrating from WSP 2014 R2:

  1. Install Wonderware System Platform 2014 R2.
  2. Re-create the backup of the galaxy.
  3. Migrate the CAB file created in step 2 to WSP 2017.

Migrating from WSP 2014 R2 P01 or WSP 2014 R2 SP1:

You can directly migrate these CAB files to WSP 2017. No intermediate steps or actions are needed.

Migrating through intermediate versions to WSP 2017: If you migrate CAB file to a version lower than WSP 2017, and then migrate the CAB file to WSP 2017, you must re-import the Historian Client controls in the intermediate version, before you migrate the CAB file to WSP 2017. See the following two examples:

Example 1: CAB file migration path: 2014 or 2014 P01 > 2014 R2 > 2017:

  1. After migrating the CAB file to 2014 R2, re-import the Historian Controls into Application Server 2014 R2.
  2. Install 2014 P01.
  3. Back up the galaxy.
  4. Migrate the CAB file to WSP 2017.

Example 2: CAB file migration path: 2014 R2 > 2014 R2 SP1 > 2017:

  1. After migrating the CAB file to 2014 R2 SP1 , re-import the Historian Controls into Application Server 2014 R2 SP1.
  2. Back up the galaxy.

Migrate the CAB file to WSP 2017.

794197

While installing the Application Object Toolkit (AOT), under certain conditions during the “Updating the system” step, the following error may be displayed by Visual Studio:

“The Add-in ‘AOT Editor’ failed to load or caused an exception. Error number: 80131604.”

Workaround:

  1. Add the following entry to the "devenv.exe.config" file:

    <dependentAssembly>

    <assemblyIdentity name="ObjectDesignServer2" publicKeyToken="23106a86e706d0ae" culture="neutral" />

    <bindingRedirect oldVersion="6.0.0.0" newVersion="7.0.0.0" />

    </dependentAssembly>

  2. Uninstall and re-install the Application Object Toolkit (AOT).
  3. Once re-installation of the AOT is complete, create a new file named "ABuilderCmd.exe.config" in the folder <AOT install path>\bin.
  4. Add the following content to the new file:

    <?xml version ="1.0"?>

    <configuration>

    <runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

    <dependentAssembly>

    <assemblyIdentity name="ObjectDesignServer2" publicKeyToken="23106a86e706d0ae" culture="neutral" />

    <bindingRedirect oldVersion="6.0.0.0" newVersion="7.0.0.0" />

    </dependentAssembly>

    </assemblyBinding >

    </runtime>

    </configuration

922856

The object name extension "_New" cannot be used if another object in the Galaxy uses the same name without the "_New" extension. For example, if you have an object named "Pump," you cannot have a second object named "Pump_New." You could, however, use "Pump_Old" and "Pump_New." Note that this restriction applies to templates as well as instances. For example, you cannot have a derived template named "$Area_New" or "$ViewApp_New" since these add the "_New" extension to a base template name.

Copyright © 2020 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us