Application Server 2017

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

Wonderware Application Server 2017 Readme

Wonderware Application Server 2017 Readme

Last revision: 4/26/2017

In This Document

About This Readme

Resolved Issues

Known Issues

Documentation Issues

About This Readme

This Readme provides information about important resolved and known issues for Wonderware® Application Server 2017 Preview.

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. The following list is not a comprehensive list of all resolved issues.

Original Change Request

Related Change Requests

Description

L00128537

 

When pairing Galaxies in an environment with a case-sensitive SQL Server installation, the Cross-Galaxy Server Primary node name would not consistently populate on the remote machine automatically .

L00138741

 

SR 51610008: Changes to DIObject template attributes were not reflected in galaxy browser.

L00138831

L00142463

SR 103136837; SR 103141617: Licensing did not count items that were IO auto-assigned.

L00139092

L00139485

SR 103137442; SR 52311919 : Using Block Read, DWord and unsigned long data type values were incorrectly read by OPCClient objects.

L00139101

 

SR 40217591: Alarms and events were not being logged from areas running under one engine.

L00139108

L00137401
L00136956
L00141524

SR 48910970; SR 19912528; SR 103134978: The feature pane was not shown when the Attributes tab of the Object Editor was selected.

L00139152

 

SR 14414018: When a second OPC UA Client was added, it was flagged as a duplicate and could not communicate with the OPC UA Server.

L00139226

L00134995
L00137254

SR 48910783; SR 40710064; SR 103135777: Remove "Everyone" share permissions on all Wonderware share names.

L00139461

 

SR 48911012: When a string attribute value was overridden, a space was not allowed in the middle of the string.

L00139476

L00144872

SR 103137996; SR 42410532: Localized alarm messages could not be not exported.

L00139489

L00141262

SR 48911221: Communication loss occurred every 10 minutes between paired galaxies in an MGC setup in an Azure Cloud environment.

L00139603

 

SR 51310999: During a Galaxy dump, the IDE hung and the dump file that was created did not have any content.

L00139638

L00140378

SR 54810118: Red error messages were logged during galaxy backup, although the. CAB files generated were good.

L00139652

 

When objects containing Field Attributes were imported to Wonderware Application Server versions 2014R2 Patch 01 and 2014R2 Service Pack 1, and had three-level hierarchies (grandparent, parent, and child relationships) and overwriting objects having only two-level hierarchies (parent and child relationships), various issues were sometimes observed (errors in the Logger; some inherited field attributes were displayed twice, some inherited attributes were not displayed, or the attributes tab would not display any information).

L00139813

 

Warnings were logged from the ViewAppCategory while deploying InTouchViewApp with an aaHistClientTrend control.

L00139850

 

SR 103137218: The CEM engine terminated abnormally and a warning message appeared in the logger. The CEM meter license state appeared as undefined.

L00139967

L00140030

SR 10512511: A memory leak occurred when an AppEngine hosted a Redundant DIObject that accessed IO strings.

L00139978

 

SR 52311395: A memory leak was causing the system to stop operating.

L00140036

 

SR 40710078; SR 40710064: System speed was slower after upgrading to 2014 R2 P01.

L00140237

L00140412
L00141161

SR 51010768; SR 51010812; SR 12613764: Discrete attributes unexpectedly went into UNACK_RTN state, and then lost ACK status upon failover.

L00140241

 

SR 39911259: The BindTo API retrieved only the value and quality properties, but not timestamp, for an indirect variable.

L00140291

L00140384

SR 103138843: When a published Managed InTouch application was migrated from WindowMaker to Wonderware System Platform 2014 SP1 without migrating the Galaxy first, any graphics called by the ShowGraphic() method were no longer present in the application.

L00140512

 

SR 19912465; SR 103137244: User was unable to browse the Galaxy from Taglinker after upgrading to WSP 2104R2 SP1.

L00140517

L00142444

SR 48911112; SR 103141258: Attributes resolved to incorrect references.

L00140605

L00139755

SR 48911074; SR 48911137; SR 103138064: It was not possible to configure OPCUAClient Service to allow communication with an eATM OPC UA Server, and the Galaxy Browser was unable to browse the items in the OPC UA Server.

L00140623

 

SR 103139134: Pokes to read-only items in a DI Object resulted in errors in the Logger.

L00140701

L00144353

SR 103139279; SR 22111428: Changes to parent template attributes overwrote attribute descriptions in derived templates when a containment relationship existed.

L00140717

 

SR 103138982: When loading Galaxy objects from a dump file, some of the objects were created without an associated Security Group.

L00140813

 

SR 48110075: The value of a a field attribute pointing to an attribute would remain as initializing after failover to the Backup Engine, unless the field attribute was shown in graphics. This did not occur when running on the Primary AppEngine.

L00140991

L00141485
L00142049
L00142070
L00142368

SR 56510199; SR 34211548; SR 103141273; SR 19819220: The initial graphic call up for an InTouch application window was very slow due to the time needed to resolve external attribute references.

L00140993

L00141156

SR 38910512: After migrating a Galaxy, the CPU utilization rate increased to a higher than normal level.

L00141232

 

When Substitute References was used to update an expression on an ArchestrA Graphic object, the parentheses around the custom property were missing in the new expression. This stopped the expression from working at run time.

L00141248

L00143327

SR 52313212; SR 51311349: Automation objects were inserted into the intouchviewapptemplate_allsymbols table after importing an object into the Galaxy.

L00141285

 

SR 55110167: Redundant AppEngines could be active simultaneously, on both the primary and backup Winplatforms.

L00141367

SR 45711460: A user working on a node other than the GR node was not able to publish managed applications to a mapped network drive if the user did not have full permissions, and the following warning was logged:

CreateDisplayFilesForInTouchForExport -> C:\Program Files (x86)\ArchestrA\Framework\Bin\aaDCM.msm not found.

L00141741

L00143316

SR 103139220; SR 24413334: When a forced failover was done several times, the values in an InTouch application stopped updating.

L00141827

L00141845

SR 103140728: If an attribute with I/O linked to an OPC UA client was created after deploying the OPC UA client, its quality would not update from bad.

L00142079

L00142455

SR 54810222: An alarm with an assigned priority that was not mapped to an Alarm Severity level resulted in Severity 1 warnings being logged in the Historian. The expected behavior is for an unmapped alarm to be displayed as a Severity 0 alarm with no historization.

L00142128

 

SR 103141003: Failed logon attempts were being counted multiple times by the operating system, which resulted in user accounts being locked too early.

L00142166

 

SR 37114322: When data quality was bad, the OPCClient used the timestamp from the local computer instead of using the KepServer OPC Server timestamp.

L00142587

L00140660

SR 103141224: When a Field Attribute was converted to an attribute, the State Alarm default setting changed from false to true.

L00142250

 

SR 24516917: When objects containing graphics were imported back into a Galaxy, the graphics did not import with the objects..

L00142328

 

SR 55110542: Communication was lost between the PLC and existing instances when derived objects were migrated to a newer base template.

L00142627

 

SR 41910256: Delays in authenticating user that was a member of many security groups caused writes to attributes to fail.

L00142659

 

SR41910263: When an attribute with a bad IO reference was written to, the write was reported as successful.

L00142779

 

SR 17115299; SR 103139220: An AppEngine had a memory leak, which continually consumed resources until out of memory.

L00143316

L00141741

SR 24413334; SR 103139220: After a failover, some attributes remained in "initializing" state when viewed in the Object Viewer.

L00143327

 

 

L00143435

 

SR:22210313: When logging in to InTouch and starting a Terminal Server session, the login name was occasionally displayed instead of the user's full name.

L00143785

L00144000

SR 54810298: When an InTouch application that contained symbols with .NET controls (such as Alarm Objects, Trend Objects, or SQL Grids) was published from the ArchestrA IDE, the .NET controls were stored in a .tmp folder under C:\Windows\Temp and not automatically deleted after publishing.

Known Issues

This section describes known issues that remain in Wonderware Application Server 2014R2 SP1 (version 4.1.12).

CR

Description

L00123504

Unexpected and misleading errors can appear in the logger while migrating particularly large galaxies because the transaction log for the galaxy database has reached its maximum allocated size.

Example error: "Error 80040E2F: Description 'Violation of PRIMARY KEY constraint 'PK__#0489BFA__6B888F1106720818'. Cannot insert duplicate key in object 'dbo.@checked_in_non_relative_unbound_elements_to_bind'. The duplicate key value is (15767, 25329, 420, 1),'".

Example error: "Query returned more than one row".

You can do the following steps to remove restrictions on the size of the galaxy database transaction log:

  1. Scan windows events (in the Event Viewer) for evidence that the transaction log is in fact full.
  2. If you confirm that the transaction log has exceeded size restrictions, do the following to remove the restriction:
    1. In SQL Server Management Studio, right click the galaxy database, then click Properties on the context menu.
    2. In the Database Properties dialog, select the Files page.
    3. Locate Log ... in the File Type column, then click the ellipsis (...) button in the Autogrowth column on the same line.
    4. In the Change Autogrowth for Base_Application_Server_log dialog, click the Unrestricted File Growth radio button under the Maximum File Size parameter. Click OK.
  3. Complete the galaxy migration, then repeat these steps to reinstate a file size ceiling on the transaction log.

L00129132

Application Server does not support the FIPS (Federal Information Processing Standards) security policy option in Microsoft Windows.The Federal Information Processing Standards are United States Government standards that provide a benchmark for implementing cryptographic software. If your system has FIPS enabled, you should disable it. The security setting for FIPS is listed under Security Settings> Local Policies> Security Options> System cryptography, or as part of Group Policy.

L00131542

The status of the OPC Client Proxy block read connection is different in Object Viewer than in Log Viewer. After deploying an OPC client proxy object, the script attempts a block read, which results in the following error in the Log Viewer: "aaBlockReadRuntime2 - Read Transactions are not allowed if the object is in Disconnected State," even though the connection status of the OCP client proxy in Object Viewer shows it is connected.

L00132251

SR 103131984: The EngineFailureTimeout attribute displays as 10000 ms in the AppEngine object editor but consistently displays as 30000 ms after deploying the AppEngine object. This occurs because the Application Server run time overrides any value less than 30000.

L00132965

If a Galaxy includes certain EOM related templates, the Galaxy migration operation will fail. Ensure that these objects (both templates and instances) are removed from the Galaxy before upgrading the software. These objects are no longer supported and will not allow the Galaxy to migrate. Remove the following templates, along with any derived templates and instances:

 

$FormulaManager

$MaterialMovedActual

$EquipmentActual

$MaterialConsumableActual

$MaterialConsumedActual

$MaterialProducedActual

$PersonnelActual

$ProductionData

 

L00133194

Importing a FieldReference package exported from Application Server 3.1 SP2 P01 to a Galaxy created under Wonderware System Platform 2014 R2 with the <FieldReference>.PV.LogDataChangeEvent attribute value set to True will trigger a software error message.

To avoid this issue, first import the most recent FieldReference package into the new Galaxy, and then import the exported package. The FieldReference package path is:

 

C:\Program Files (x86)\ArchestrA\Framework\Bin\FieldReference.aaPKG

L00134029

Importing an aaPKG from Wonderware Application Server 2014 to Wonderware Application Server 2014 R2 that has already been imported once, updated on the older version, then re-imported to the newer version, does not update any UDA History descriptions that might have been configured on the older version. As a workaround, you can delete the object instance on the newer version machine, then re-import. The updated attributes will then appear in the Galaxy on the newer version of Application Server.

L00134193

Under certain circumstances, you may receive an error message when using I/O auto assignment and you press the Validate References button in the IO Device Mapping view. This can happen if the IDE is running on a deployed remote platform. Instead of validating the references, the error message "Please deploy the platform object to validate the references" is displayed, even though the local and remote platforms are deployed.

Workaround: Restart the IDE on the remote platform and then validate the references again.

L00134322

The ASBGRBrowsing service is used for browsing objects and attributes on the local Galaxy, as well as for browsing in multi-galaxy environments. If you undeploy the ASBGRBrowsing service, browsing in the local Galaxy will result in error messages.

L00134383

When a saved script is renamed in the Object Editor, the script's contents appear to have been removed and the script editor is grayed-out. As a workaround, save and close the object, then reopen it. The script's contents will once again be displayed in the editor.

L00134390

When an existing Galaxy created from Base_InTouch.cab is migrated to Wonderware System Platform 2014 R2, $Sequencer and $SQLData objects are created that did not exist in the non-migrated Galaxy. As a workaround, manually delete the added objects from the migrated Galaxy.

L00134493

OPCClient DI objects have a naming limitation when used with the I/O assignment feature. I/O auto assignment uses the syntax <DI Object.ScanGroup>.<Field Reference>. However, to fulfill the OPC hierarchical path, a port and device must also be specified; for example, <DI Object.ScanGroup>.<PortName>.<DeviceName>.<Field Reference>.

Workaround: Use the Object.Attribute Override column in the IO Device Mapping view to add additional OPC parameters to field references. Manually adding these parameters in the Object.Attribute Override column will result in a fully qualified I/O reference which includes all required parameters. If bulk edits are required, you can copy and paste between the IO Device Mapping view and Microsoft Excel. Refer to Application Server User's Guide for important information about editing I/O references in Excel. Note the caution about sorting references while editing.

L00138642

Attempts to pair two nodes (multi-Galaxy pairing) failed on two Galaxies, upgraded from Baktun, which were not previously paired. Errors and Warnings are logged while configuring the MGC after upgrade from Baktun PO3 to Apollo R2 SP1.

Workaround: Restart the watchdog service if errors are logged after launching the Multi Galaxy Configuration window (Galaxy > Configure > Multi-Galaxy).

L00139257

A warning message "Galaxy Restore: SQL Exception: 80043C32: Description '[Microsoft] [ODBC SQL Server Driver] [SQL Server] The user or role' NT AUTHORITY \ SYSTEM 'does not exist in this database.'" is logged when creating a galaxy.

Reason and Workaround: You cannot restore a Galaxy to a language locale that that differs from that of the Galaxy's origin. For example, if a Galaxy is created using a computer configured for English (language locale 1033), it cannot be restored using a computer configured for German (language locale 1031). You must use the same language locales when moving Galaxies, and objects within Galaxies, to different computers.

L00139425

Errors from the BRO may occur while upgrading a Galaxy Repository Node from Application Server 2014 R2 or 2014 R2 P01 to Application Server 2014 R2 SP1. These errors are related to the ViewEngine process and occur only during the upgrade process. There is no impact on functionality and the error messages can be safely ignored.

Sample log error messages (these will be highlighted in red):

4003 12/14/2015 11:55:49 AM 6264 7256 Error BRO ViewEngine_001 - CBaseRuntimeObject::SystemSetAttribute - Caught unknown exception.
4004 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 3910 FILE CBaseRuntimeObject.cpp LAST ERROR 0
4005 12/14/2015 11:55:49 AM 6264 7256 Error BRO ViewEngine_001 - CBaseRuntimeObject::BuildFullPrimitiveNames() - BuildName returned false
4006 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 364 FILE CDeploymentPrimitive.cpp LAST ERROR 11001
4007 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVALID HRESULT LINE 393 FILE CDeploymentPrimitive.cpp hResult 80001f40
4008 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVALID HRESULT LINE 466 FILE CDeploymentPrimitive.cpp hResult 80001f40
4010 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001
4011 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001
4012 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001
4013 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001
4014 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001
4015 12/14/2015 11:55:50 AM 6264 7256 Error ViewEngine_001.aaEngine Could not perform operation -- unexpected exception. Unexpected failure (8000ffff) caught at line 239 in FsEngine.cpp (in ).
4016 12/14/2015 11:55:50 AM 6264 7256 Error ViewEngine_001.aaEngine WinMain exiting error code 8000ffff

Workaround: No workaround is necessary. There is no loss of functionality either during the upgrade process, or after the upgrade process completes.

L00139639

When using Enhanced Security Mode (ESM), restoring a CAB file results in an unusable Galaxy if the BUILTIN\Administrators group has the sysadmin role.

Workaround: Log into SQL as a user with sysadmin privileges, and run the following script on the unusable Galaxy database. Replace the italicized text inside the angle brackets with the name of the restored Galaxy and with the database host name, respectively.

ALTER AUTHORIZATION ON DATABASE::<name-of-galaxy> TO [<db-server-host-name>\aaGalaxyOwner]

L00139679

Bootstrap intermittently does not start on a Windows 7 32-bit remote node after upgrading Wonderware System Platform from version 2014 R2 to version 2014 R2 Service Pack 1. It has been observed that after restarting the remote node, Gdiplus.dll, a Windows system file, was missing from C:\Windows\System32. If you have a recent version of the Gdiplus.dll installed before upgrading, greater than version 6.1, this issue does not occur.

Workaround: After upgrading the run-time node on the 32-bit system, repair the installation again before redeploying the remote platform.

L00139830

MDT AutoSave for System Platform (A4SP) does not work if Wonderware Application Server is configured to run in "Enhanced Security Mode". MDT A4SP version 3.0 still leverages SQL Server SysAdmin privileges. Support for this functionality will be added to A4SP version 3.01, with availability planned for the end of the first quarter of 2016. Please contact MDT Software for additional details at MDT Software Support.

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.

L00141283

Multi-node Application Server implementations in Windows workgroup environments are not advised; use domain-based network management instead.

For multi-node installations in a workgroup environment, operations that require inter-node communications may not function correctly. These include:

  • Connection to a remote IDE
  • Viewing remote platform status

However, if everyone permissions are enabled for anonymous, this issue does not occur.

Workarounds: Either enable everyone permissions for anonymous users (method 1), or switch to domain-based networking (method 2).

  1. To enable everyone permissions for anonymous users, go to:
    Local Security Policy > Local Policies > Security Options > Network Access: Let everyone permissions apply to anonymous
    Right-click to open the setting dialog and select "enabled" (default is disabled).
  2. To switch to domain-based networking:
    Designate a node as the domain controller and convert to domain-based networking.

 

L00141660

In a system with two GR nodes, attempting to connect from the IDE on one node to a Galaxy on the second GR node does not succeed, and the IDE shuts down.

Workaround: Pair the GR nodes before trying to connect to the Galaxy on the other node. See "Working with Multiple Galaxies > Setting Up a Multi-Galaxy Environment" in the Application Server User Guide for information about configuring multi-Galaxy pairing.

 

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):

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

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA

  2. Create a REG_DWORD value named UseMachineID and set the value to 1.
  3. 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:

    shell:::{80F3F1D5-FECA-45F3-BC32-752C152E456E}

  3. Click OK.

    This starts the Tablet PC Settings configuration dialog, even if you are not working on a Tablet PC.

  4. Select the Other tab.
  5. In the Handedness section, select the Left Handed option.
  6. 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.

775165

In some instances, when an object’s owned graphic is embedded inside another graphic, and the contained name of the object is changed, the Graphic Editor may display “Graphic not Available”, but at runtime the graphic will be displayed correctly.

777023

After changing the attribute overrides of a deployed DI object, with more than 20,000 attributes, the attribute validation will fail, even though attribute syntax for the remaining attributes beyond 20,000 is correct.

Workaround: Re-deploy the DI Object to clear up this problem.

779110

If two or more symbols are linked to an object template from which an instance has been created, and overrides are configured for those symbols via Object Wizard options, then the symbol overrides may not appear correctly at run time.

Workaround: Open the affected template, make a small change, then save and check in the template. This will re-propagate the changes correctly.

782071

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

783145

In a galaxy with a large number of layouts, symbols, and miscellaneous objects (assets, area nodes, display controls, etc.), using arrow keys in the layout toolbox to select items from the asset search results causes a long delay in showing the content view, and causes warning messages to be logged in the System Management Console.

785665

Under certain circumstances, when migrating a CAB file from an older galaxy that contains ArchestrA Graphics and utilizes the Historical Trend control to Wonderware 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 Wonderware 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.

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.

792077

After upgrading the Galaxy Repository node to Wonderware System Platform 2017, and migrating existing galaxies to Wonderware System Platform 2017, the logger shows warning for ProcessRealtimeClerk. This does not affect functionality. You can successfully connect the IDE to migrated galaxies, and successfully redeploy the GR node without errors. All nodes will operate normally.

792311

SQL Server, and programs that call into it from Wonderware System Platform 2017, periodically (about every five minutes) spike their usage of physical and virtual memory, which degrades system performance.

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

 

794573

If the System Platform IDE is minimized, and a popup editor (for example, the Layout editor) is active, if the IDE displays a modal window, such as a Save dialog, you cannot select the IDE from the taskbar to move it and the modal window in front of the popup editor.

Workaround: Move the other editor out of the way.

794579

If you start the System Platform IDE, but then the watchdog is restarted or otherwise loses connection to IOMBLS service before any of the popup editors, such as the Layout, Screen Profile, or ViewApp editor, has been opened, the Toolbox of the popup does does not work. This happens because the toolbox is trying to use the prior connection to the IOMBLS.

Workaround: Restart the IDE.

795918

An ASBService warning message is logged if Wonderware Application Server is uninstalled while a galaxy is deployed.

Workaround: Undeploy any deployed galaxies before uninstalling Application Server.

798129

When an instance has multiple levels of containment, not all contained objects are automatically assigned to the Simulator.

Workaround: Manually assign instances to the Simulator that are not automatically assigned.

Documentation Issues

There are no known documentation issues for Wonderware Application Server 2017.

Item

Location of Change

Existing Documentation

Change

 

 

 

 

Avantis  |   Industry Software Suites   |  OASyS  |   SimSci  |   SimSuite  |   Skelta  |   Wonderware

Copyright © 2017 Schneider Electric Software, LLC.  |  Contact Us