Application Server 2017 Update3 SP1

Материал из archestra.info
Версия от 14:10, 5 августа 2019; Vasily (обсуждение | вклад) (Новая страница: « <html> <head> <title> Application Server 2017 Update 3 Service Pack 1 Readme </title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta…»)

(разн.) ← Предыдущая | Текущая версия (разн.) | Следующая → (разн.)
Перейти к: навигация, поиск

Application Server 2017 Update 3 Service Pack 1 Readme

Application Server 2017 Update 3 Service Pack 1 Readme

Last revision: 5/21/2019

In This Document

About This Readme

Resolved Issues

Known Issues

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 © 2019 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us

Источник — «http://archestra.info/index.php?title=Application_Server_2017_Update3_SP1&oldid=4420»