Application Server 2017 UPDATE 1 (v17.1) Readme

Posted on 228 views
About This Readme

This Readme provides information about important resolved and known issues for Wonderware® Application Server 2017 UPDATE 1 (v17.1).

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

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

Resolved Issues

This section describes important resolved issues in Wonderware Application Server 2017 UPDATE 1. The following list is not a comprehensive list of all resolved issues.

Original Change Request

Related Change Requests

Description

L00138816

L00144400

SR 103137251: In a script that uses buffered values, only the last calculated value was historized; interim values were not historized.

L00138837

SR 19912411: Scripts that made calls to various FactMES APIs resulted in access violation exceptions in the aaEngine and application processes.

L00140432

SR 45511048: At run time, some text in the Embedded Alarm Client (EAC) did not display as localized (translated) text. The text was displayed in the wrong language.

L00140609

SR 103139461: When used to reference arrays, the IsBad() and IsGood() functions sometimes exhibited inconsistent behavior, depending on whether the referenced array was on the same or a different engine.

L00140958

SR 22111349: In certain circumstances, when a GR dump was executed, the process completed but the file write did not finish, and an out of storage exception was logged.

L00141999

SR 103139772: Events were logged for a Boolean attribute when a momentary loss of communication with the PLC occurred (for example, true to false and then false to true), even though the value did not change in the PLC or in Application Server.

L00142511

SR 103140938: When an attribute was renamed, its extended attributes, such as the description and eng units were not taken renamed, and these remained tied to the original attribute name.

L00142772

SR 44710563; 43612066: Communication errors between the primary and backup galaxies appeared in the logger (Multigalaxy Communication Error: “aaMxDataConsumer” Unknown error 0xC0000005).

L00143462

SR 22111381: After upgrading or migrating an InTouch application to Wonderware System Platform 2014 R2 SP1, symbols did not appear unless the ViewApp platform was redeployed.

L00143652

SR 103143536: The script function StringChar() did not recognize extended ASCII values (128-255).

L00143659

L00145094

Opening an object in editing mode took more than 10 seconds longer than opening the same object in read-only mode.

L00143744

SR 103142966: CPU usage and AppEngine scan overruns increased after a script containing buffered data was processed.

L00143799

SR 22111369: The memory used by the aaGR.exe and aaIDE.exe processes significantly increased after a system was upgraded from Wonderware System Platform 2014 R2 P01 to 2014 R2 SP1.

L00143931

SR 22210325: ArchestrA graphics were missing in published InTouch applications, and a ViewAppCategory exception (CreateDisplayFilesFirInTouchForExport=Timeout expired) appeared in the logger.

L00144001

L00142167 L00145612

SR 103143782; SR 37114322; SR 22319851: After switching to the backup Redundant DI Object because of bad quality from the primary DI Object, both the value and quality from the DI source was not updated correctly if the primary object had a more recent timestamp than the new value from the backup object.

L00144033

SR 103139544: After redundant AppEngines failed-over, some attribute references remained in the initializing state.

L00144244

Under certain circumstances, when an object assigned to an area was imported into another galaxy, the object’s version number was incremented when it should not. The version change occurred only when the object included graphics that had some unbound visual elements (missing contained object), the object was contained in an area, and the object included self-referencing attributes (me.attribute).

L00144289

SR 43612110: Intermittently, after executing a galaxy dump, some object-level scripts were missing.

L00144344

SR 40710108: After migrating a galaxy, some AppEngines consumed an excessive amount of memory after deployment.

L00144530

L00137737

SR45110893: When a symbol that used the wwcontrol ‘lmxproxy.dll’ was opened in the Graphic Editor, the IDE stopped responding and a message appeared in the logger that multiple threads were calling the CLMXProxyServer.

L00144601

SR 10512580: When the ServerNode attribute was changed for an OPCClient connected to a Kepware server, the number of handles increased when the platform was deployed.

L00144652

SR 103143134: The quality of a buffered attribute in a Redundant DIObject remained at “20: Initializing” until the value of the attribute changed.

L00144789

SR 37612964; SR 103145274: After changing the ArchestrA user password with the change Network Account Utility, remote platforms could not be deployed.

L00144805

SR 48310022: Templates and instances were quarantined, and error messages were sent to the SMC logger stating that alarm aggregation and write attempts to the common primitive from the scheduler failed.

L00144848

SR 54810329: Unnecessary information messages related to the GR Browsing Service were posted when the Galaxy Browser was used in the Graphic Editor to locate a reference.

L00145472

Certain events were written in the AlarmDB (OAJ) as successful even when the DI object reported a warning.

L00145585

SR 20115136: During an AppEngine failover, a warning message, “Failover engine x is marked as restarting” was displayed (where x is then engine number).

L00145730

L00142368 L00145831

After applying HotFix L00142638 to improve display update times, occasionally data did not load and WindowViewer did not function correctly after it was reopened.

L00145820

SR 51313135: The attribute description on an instance was grayed-out (locked) if the attribute value was locked on the template.

L00145993

SR 103144938: The value quality of a buffered user defined attribute remained good and the attribute valued remained constant after its deployed object was disconnected from the OI server.

L00146128

L00146275

When the ShowGraphic() method was called on a graphic that was already open, references remained stuck with the “initializing” status.

775165

In some instances, when an object’s owned graphic was embedded inside another graphic and the contained name of the object was changed, the Graphic Editor displayed “Graphic not Available”, even though the graphic was displayed correctly at run time.

779110

When two or more symbols with configured Object Wizard overrides were linked to an object template that had a derived instance, the symbol overrides did not always display correctly at run time.

782071

When an override was reverted for the EngUnits or Description setting of an object that did not have an initial value for these settings, the setting value did not revert to the expected value.

794579

If the watchdog was restarted or lost connection to the IOMBLS service before any of the IDE popup editors were opened, the Toolbox of the popup editor did not work.

Known Issues

This section describes known issues that remain in Wonderware Application Server 2017 UPDATE 1.

Change Request

Description

L00139852

GRAccess does not support Enhanced Security Mode in the following scenarios:

  • Creating a Galaxy using a .cab file from a previous Application Server release.
  • Restoring a .cab created with a previous Application Server release.

    We recommend not using GRAccess to perform these operations.

L00144613

When Application Server has been installed/upgraded to Wonderware 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):

  4. On the DA Server node, open the Registry editor and navigate to key path

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA

  5. Create a REG_DWORD value named UseMachineID and set the value to 1.
  6. 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.
  2. In the Open line, copy and paste the following text:
  3. shell:::{80F3F1D5-FECA-45F3-BC32-752C152E456E}
  4. Click OK.
  5. This starts the Tablet PC Settings configuration dialog, even if you are not working on a Tablet PC.
  6. Select the Other tab.
  7. In the Handedness section, select the Left Handed option.
  8. Click OK.

772561

When a scaling factor of 125 or 150 percent is chosen in Windows 10, and then use the selection tool in the Graphic Editor, the selection box appears with a offset from the pointer.

773741

Warning messages appear in the SMC log file when migrating an application created with Wonderware System Platform R2 SP1 to Wonderware 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 Wonderware System Platform 2017 ViewApp.

789337

After deploying an engine with about 25,000 IO, the objects are not set on-scan, and a timeout warning is logged for each object.

Workaround: After the deployment fails, restart the AppEngine on-scan. To avoid the problem, you can set the NMXMsgMxTimeout attribute for the WinPlatform object from the default value of 30 seconds (30,000 msec) to 60 seconds or more. You can also set the value of the attribute by changing the Message Timeout parameter (General tab > Message Exchange).

Note: Setting the engine off-scan and then on-scan again will not work; you must restart the engine.

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 intall 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.

932052

In a Multi-Galaxy environment, where one node is running Wonderware System Platform 2017, and another node is upgraded to Wonderware System Platform 2017 UPDATE 1, some ASB services are not immediately deployed after the upgrade. This results in multiple “Failed to connect” warnings in the logger.

Workaround: These connection issues can be corrected by deploying the upgraded node one more time, after the initial redeployment.

  1. Undeploy the Galaxy prior to upgrading the node to Wonderware System Platform 2017 UPDATE 1.
  2. Upgrade the undeployed node.
  3. After the upgrade completes, restart the node and redeploy the Galaxy.
  4. Check the Log Viewer. If you see “Failed to connect warnings,” deploy the Galaxy again. This second deployment will correct the connection issues.

The same issue can occur when a run-time node is added to the Galaxy Repository, and the node is not detected as online when the attempt is made to deploy ASB services.

Workaround: These connection issues can be corrected by deploying the added node one more time, after the initial deployment.

  • If you see “Failed to connect warnings,” deploy the Galaxy again to correct the connection issues.

Leave a Reply

Your email address will not be published. Required fields are marked *

53 + = 56