Application Server 2014 R2 (4.1)
Материал из archestra.info
Wonderware Application Server 2014R2 (version 4.1) Readme
Last revision: 12/10/2014
About This Readme
This Readme provides information about important resolved and known issues for Wonderware® Application Server 2014R2 (version 4.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 Wonderware Developer Network at http://wdn.wonderware.com/Downloads.
Resolved Issues
This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.
| L00124769: | SR 45530082: An ArchestrA symbol was occasionally missing from the InTouchViewApp start up window. |
| L00128178: | SR 103126451: The GR platform restarted while performing a Galaxy load. |
| L00128246: | SR 42010070: Performing a Galaxy dump could trigger a memory exception. The Galaxy dump would then end without completing. |
| L00129575: | SR 103129209: After importing a package file that contained area objects, some graphic files were missing. |
| L00130292: | SR 103130636: The StringReplace() function did not replace a period (.) in the string. |
| L00130295: | SR 10512273: An AppEngine hosting a RedundantDIObject could develop a memory leak. | L00130333: | SR 33812522: Selecting an alternate instance of an object contained by another object within an embedded ArchestrA graphic caused WindowMaker to display a red X. |
| L00130392: | SR 103129988: A user's smart card was not recognized for access. |
| L00130600: | SR 103130791: Field Attributes configured with scaling continuously generated OnDataChange events. |
| L00130716: | SR 19818424: If a corrupted symbol was embedded in an object, it disabled the Symbol Editor. |
| L00130791: | SR 40215771: If the AlarmMode of an attribute was disabled and the instance was off scan, the alarmed attribute remained in the initializing state after the instance was set back on scan. |
| L00131155: | SR 44710384: The System Communication failure alarm was activated when no failure had occurred. |
| L00131251: | After a Galaxy was upgraded, the Built-In Administrator was not present in the security setting of the Galaxy share folder. |
| L00131268: | SR 40215638: The IDE did not add a domain user to OS security even though the user was detected. |
| L00131270: | SR 48610093; SR 41810025: AppEngine would occasionally restart during redundant pair failover or during deployment change. |
| L00131545: | SR 40215477: Using an RDP connection caused some values in an InTouch window to freeze. |
| L00131579: | SR 15317217: Field Attributes occasionally remained in the initializing state, even when a script was trying to interact with the attribute. |
| L00131583: | SR 38910487: MessageChannel GetTickCount rollover was causing connection reset and failovers. |
| L00131630: | SR 37612424: Field Attribute output values were not written to the PLC. |
| L00131684: | SR 45710969 : Alarm acknowledgement was not working correctly. |
| L00131713: | SR 49910007: The Pending Change icon was displayed for InTouchViewApp objects, even though no change was pending. |
| L00131752: | SR 51010032: When performing a CSV Galaxy load, an erroneous message about missing attributes in an object was displayed instead of an acknowledgement that the object had successfully loaded. |
| L00131971: | SR 45510721: SQL queries to the database on platforms hosting SQL Data Objects did not work correctly and resulted in an "incorrect syntax" error message. |
| L00132158: | SR 45510703: During deployment, the AppEngine crashed when the NotificationDistributor did not send events. |
| L00132169: | SR 40215786; SR 49010019: The AppEngine terminated while a script was running. |
| L00132179: | SR 37113270: The aaEngine sometimes failed to register reference calls, and valid references appeared with an invalid status. |
| L00132261: | SR 19818525: Migrating the Galaxy from Wonderware System Platform 2012 SP generated an error: "Column 'FAV_NUM_ONE' does not belong to table Table." |
| L00132734: | SR 48910402: Multiple instances of aaCALWrapper.exe were launched when WindowViewer started. |
| L00132849: | SR 45530082: Some ArchestrA graphics were occasionally missing in the InTouch ViewApp start up window. |
| L00133054: | SR 49410032: When an object with the same tagname, container and contained name was created via a Galaxy load, the object could not subsequently be edited or deleted. |
| L00133970: | SR 33812592: AppEngines were consuming excess memory and required redeployment or a system reboot. |
| L00134800: | SR 24412872: Information has been added to the Wonderware Application Server User's Guide, Chapter 4 - Managing Objects, under the heading "Importing Objects," stating that objects created in a Galaxy running a newer version of Application Server cannot be imported into a Galaxy running an older version. This object import behavior was changed in the Wonderware Application Server 2014 release. |
Known Issues
This section describes known issues that remain in Wonderware Application Server 2014R2 (version 4.1).
| 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:
|
||||||||
| L00128537: | When pairing Galaxies in an environment with a case-sensitive SQL Server installation, the Cross-Galaxy Server Primary node name may
not automatically populate on the remote machine.
Workaround: Manually enter the Primary node name or IP address in the text box on the remote machine. |
||||||||
| L00128969: | The ArchestrA IDE may take 30 seconds to open on a system that is not connected to the Internet. When the IDE starts, the operating
system attempts to verify the digital certificates for internal components against a Certificate Revocation List (CRL) located on a public
website. If your system cannot access the public site within 30 seconds, the IDE startup process resumes and completes.
Workaround: To avoid this delay, in Internet Explorer or through Control Panel, open Internet Options, Advanced Options, and uncheck the option to Check for publisher's certificate revocation. |
||||||||
| L00129132: | Application Server does not support the FIPS (Federal Information Processing Standards) security policy option in Microsoft Windows. 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. | ||||||||
| 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:
| ||||||||
| L00133173: | Creating a Galaxy does not succeed when Application Server is running in a VM on Microsoft Azure. Workaround: Execute the following SQL query before installing Application Server: EXEC sp_grantlogin 'NT Authority\System'
|
||||||||
| 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. | ||||||||
| L00134423: | When importing multiple objects that use I/O auto assignment, warnings may be displayed indicating that some of the imported objects have
unresolved I/O references. However, the references are actually valid and the warnings are displayed in error.
Workaround: Manually validate at least one object; the object does not need to be one of the objects generating a warning. If this does not clear all of the warning messages, repeat the validation until all the erroneously-displayed warnings are cleared. | ||||||||
| 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. |
||||||||
| L00134803: | If a DI object is imported and given the same name as previously deleted DI object, scan groups associated with the
deleted DI object appear under the imported, renamed DI object in the IO Devices view. Workaround: If this occurs, restarting the IDE will eliminate the scan groups associated with the deleted DI object in the IO Devices view. |
||||||||
| L00134970: | Even after unresolved references have been reconciled for an InTouchViewApp instance, the instance may continue
to show that a warning state exists.
If you check the Error/Warnings tab for the InTouchViewApp instance's properties, no errors are listed. Workaround: Restarting the IDE will clear the warning state. |
||||||||
| L00135073: | The description of inherited attributes is deleted when a new attribute is added to the parent template, or a different
attribute is deleted from the parent. The Eng Units setting of inherited attributes is also deleted under the same
conditions of adding or deleting attributes at the parent level. Workaround: Add the description and Eng Units to the object in which the attribute was created. |
Documentation Issues
The following table lists important documentation corrections.
| Item | Location of Change | Existing Documentation | Change |
| 1 | New information to be inserted into Creating and Managing ArchestrA Graphics User's Guide (AAGraphics.pdf), Chapter 3 "Managing Symbols", To edit a symbol contained in an AutomationObject procedure
Graphic editor online help (IDE.chm), "Opening Symbols for Editing" topic |
4. Edit the symbol. For specific information about using the drawing tools, see Working with Graphic Elements. | 4. Edit the symbol.
|
© 2014 Invensys Systems, Inc. All Rights Reserved. Invensys is a Schneider Electric company.
