Application Server 2014 R2 Patch 01 (4.1 patch 01)
Материал из archestra.info
Last revision: 6/4/2015
About This Readme
This document includes information about Wonderware® Application Server 2014R2 (version 4.1) Patch 01. It updates the previous Readme file included with Wonderware Application Server 2014R2 (version 4.1). The entire Wonderware Application Server 2014R2 Readme is included in this document, following the Patch 01 sections.
About this Patch Release
The Wonderware System Platform 2014R2 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 "Wonderware System Platform 2014R2 Patch 01 Readme", available for download with the Patch Manager.
Important!
- Installation - Wonderware Application Server 2014R2 must be installed before you can install this patch.
Installing Application Server on a computer used as a domain controller is not supported. - Coexistence - If more than one Wonderware System Platform 2014 R2 product is installed on a node, the Patch Manager will select all the products for upgrade to Patch 01 by default. This is the recommended setting.
Wonderware Application Server 2014R2 Patch 01 Information
Applying Patch 01 to Wonderware Application Server Version 2014R2
Resolved Issues - Wonderware Application Server 2014R2 Patch 01
Known Issues - Wonderware Application Server 2014R2 Patch 01
Wonderware Application Server 2014R2 Information
Wonderware Application Server 2014R2 Readme
Resolved Issues - Wonderware Application Server 2014R2
Known Issues - Wonderware Application Server 2014R2
Known Documentation Issues - Wonderware Application Server 2014R2
Applying Wonderware Application Server 2014R2 Patch 01
Close any anti-virus programs running on the computer before you update Wonderware Application Server with Patch 01.
Apply this patch only to Application Server 2014R2 version 4.1. You can check the version number in the Control Panel. For example, from Control Panel, select Uninstall or change a program from the Programs and Features section, then select Wonderware Application Server.
Important!
This patch must be installed on all Wonderware Application Server nodes. On nodes where both Wonderware Application Server and InTouch are installed, you must install Wonderware Application Server 2014R2 Patch 01 and InTouch 2014R2 Patch 01 in order for them to coexist.
- Before installing the patch, ensure you have created known good backups of all installed Galaxies. To create a backup of your Galaxy, access the Galaxy Database Manager in the ArchestrA® System Management (SMC) console. Expand the Galaxy Database Manager and select the Galaxy. On the Action menu, click Backup. Follow the prompts to complete the backup operation for each Galaxy.
- If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Patch 01 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.
- An ArchestrA IDE node still at version 4.1 cannot connect to a remote GR node updated with Patch 01.
- An ArchestrA IDE node updated with Patch 01 cannot connect to a remote GR node still at version 4.1.
NOTE: As a general workflow, patch the GR node first, followed by the run-time nodes.
- 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 ArchestrA IDE, 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, ensure any active remote IDE sessions are disconnected. Patch 01 requires ArchestrA-related processes be shut down and may require a reboot.
Resolved Issues - Wonderware Application Server 2014R2 Patch 01
This section describes issues that have been resolved in Wonderware Application Server 2014R2 Patch 01. These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column lists subsequent change requests that are related to the original change request.
| Original Change Request | Related Change Requests | Description |
|---|---|---|
| L00119440 | L00133653 L00134710 |
SR 103124254: Recreating a Galaxy from the cab file created redundant folders of deployed InTouch Applications on the Galaxy Repository. |
| L00120671 | L00132022 | SR 31711844; SR 48910371: A message was displayed that the OPCClient Target node could not be found. |
| L00126108 | L00136278 | SR 10916638: Objects could not be configured, deployed, or undeployed with customer GPO enabled due to insufficient permissions in the objects "...\CheckedIn" and "...\CheckedOut" folders. |
| L00126276 | L00131581 | SR 37113036: The description could not be defined for the scan group item error count alarms (scangroup.ItemErrorCntAlarm.DescAttrName). |
| L00129452 | L00136409 | SR 103128626; SR 103134169: Entering a DeadBand Value in the Field Attribute tab did not have any effect. |
| L00129575 | L00132211 | SR 103129209; SR 103131806: After importing a package file that contained area objects, some graphic files were missing. |
| L00130392 | L00132202 | SR 103129988; SR 103132058: A user could not gain access using a Smart Card and received the message, "User does not belong to any of the configured Roles." |
| L00130716 | L00135193 | SR 19818424; SR 10417719: If a corrupted symbol was embedded in an object, it disabled the Symbol Editor. |
| L00131155 | L00132335 L00135132 |
SR 44710384; SR 12613067; SR 103133171: The System Communication failure alarm was activated even though no failure occurred. |
| L00131405 | L00131406 | Importing an InTouch View Application into a lower product version from a higher product version caused WindowMaker to stop. |
| L00131545 | L00135690 L00135691 |
SR 40215477: Using an RDP connection caused some values in an InTouch window to freeze. |
| L00131579 | L00135191 | SR 15317217; SR 10417719: Field Attributes occasionally remained in the initializing state, even when a script was trying to interact with the attribute. |
| L00131583 | L00132245 L00132302 L00132356 L00134797 |
SR 38910487; SR 19818538; SR 50810081; SR 22210159: MessageChannel GetTickCount rollover was causing connection reset and failovers. |
| L00131713 | L00132744 L00133823 L00134320 L00136190 |
SR 103131703; SR 49910007; SR 43110490: The Pending Change icon was shown for InTouch View applications, even though no changes had been made. |
| L00131752 | L00131885 | 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. |
| L00131793 | SR 48910335: An error message was logged from WWCdi after checking in a template, stating that an invalid length parameter was passed to the RIGHT() function. | |
| L00131844 | L00132800 | SR 43110407; SR 49410030: Platform names shorter than 14 chars were not displayed in the System Management Console log navigation tree. |
| L00132179 | L00135192 | SR 37113270; SR 10417719: The aaEngine sometimes failed to register reference calls, and valid references appeared with an invalid status. |
| L00132255 | L00132348 L00132797 L00134890 |
SR 45110495; SR 47910035; SR 49410030: Importing an object into a previous version of Application Server worked with no errors or warnings, and resulted in some DLL files being changed. |
| L00132477 | SR 22318648: Two systems were successfully time synchronized after drifting out of synchronization, but an excessive number of messages were reported to the OPC client. These messages were benign, but had the potential to fill the log. | |
| L00132976 | SR 52310005: When an object was deployed on a system running Microsoft Windows Server 2012, the AppEngine stopped working. | |
| L00133054 | L00133143 L00133144 |
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. |
| L00133154 | SR 103132532: If a string UDA was empty, zero would be inserted into the Value or CheckValue columns of v_EventHistory. | |
| L00133173 | Creating a Galaxy did not succeed when Application Server was running in a VM on Microsoft Azure. | |
| L00133458 | L00134674 | SR 103132521; SR 37510653: When provisioning was performed using the ArchestrA WorkFlow object, it slowed down the response time of the object. |
| L00133478 | SR 22318522; SR 103130791: A Field Attribute did not show the correct value for the PLC unless the Buffered Data option was enabled. | |
| L00133482 | L00134870 | SR 46110712; SR 103133232: The value of AppEngine attribute, Scheduler.InputQueueSizeAvg, was increasing over time. |
| L00133521 | L00135441 | SR 43110404: The auto-synchronize tags setting did not synchronize correctly when new tags were added, and objects with references to the new tags did not work. |
| L00133674 | L00134613 | SR 103134125; SR 49010033: Remote node deploy failed after Application Server was upgraded. |
| L00133708 | L00133709 L00133710 |
SR 43110414; SR 43110417; SR 49410052: A remote GR was occasionally unable to connect to the Application Server IDE, and platform status was listed as unavailable in Platform Manager. |
| L00134423 | When multiple objects that use I/O auto assignment were imported, warnings about unresolved I/O references for some of the imported objects were sometimes displayed in error. | |
| L00134427 | During installation of a product that embeds the 2014 R2 version of ASB, Application Server would, depending on its version, either lose configuration, or always show as configured. | |
| L00134499 | SR 44710488: Object Viewer displayed incorrect values with Bad data quality for some Input.Value attributes and timeouts would occur. | |
| L00134677 | SR 51510460: While upgrading, platform deployment to a remote node failed. | |
| L00134704 | L00134850 | SR 43110446: Redundant AppEngines stopped operating if the backup platform and AppEngine were not deployed. |
| L00134713 | SR 20611434: Access was denied, and repeated error messages were logged from component ObjSyncMgr. | |
| L00134716 | SR 38910496: When the QueryObjects method was executed, the CommandResult always returned TRUE-SUCCESS. | |
| L00134955 | SR 103133241: In the Chinese version of InTouch, a Situational Awareness Library symbol did not display in published applications. Instead of the symbol, the message "Graphic not available" was displayed. | |
| L00135002 | L00136015 L00136605 |
SR 103133094; SR 33913773; SR 23314780: InTouch managed applications were not activating all items from an OPC UA server.
Important: If you are using an OPC UA client with Wonderware System Platform (WSP) 2014 R2 P01, you must apply HotFix CR L00136605. WSP 2014 R2 P01 includes fixes to Application Server for this issue, but OPC UA client is a separate installation and is not included in the patch. |
| L00135073 | The descriptions and Eng Units settings of inherited attributes were deleted when a new attribute was added to the parent template or a different attribute was deleted from the parent. | |
| L00135076 | L00135326 | SR 43110442: After Galaxy validation, the Operations view did not sort objects correctly when the Status column was used for sorting. |
| L00135117 | SR 43611211: After a reboot, one node was not able to see alarms from other nodes. | |
| L00135136 | SR 19713757: Multiple concurrent terminal service users were sometimes unable to connect to the Application Server IDE, and an error message stating that the clients could not be synchronized would be displayed. | |
| L00135254 | SR 103133437: Redeploying an object did not clear the Galaxy status flag that indicated that there were pending changes. | |
| L00135424 | SR 51010321: Choosing the Repair option from Setup changed the watermark for the Application Server IDE from 2014 R2 to an older version. | |
| L00135466 | SR 54010002: When using a Redundant AppEngine with an undeployed and unassigned partner, the following error was generated on each scan: "EventHistorizationShim SetHistorianDetail: System.Exception: SetRedundantSFMode call failed, error: Server name length invalid" | |
| L00135553 | SR 52410087: Reassigning objects in the IDE took longer than expected. | |
| L00135651 | SR 54010003; SR 45110540: During failover, the Logger listed an access violation for some engines. This could lead to other error messages, including communication errors, failure to connect to the standby platform for store/forward, and failure to get store forward redundancy attributes from engine. | |
| L00135684 | SR 52410673: An analog field attribute reading a double word from a PLC, with the first bit modified as a signed bit, would display 0 in Object Viewer instead of the actual value in the PLC double word. | |
| L00135872 | SR 103134042: Attribute descriptions in derived templates were lost when a change was made to the parent template. | |
| L00135926 | Changing one object sent all application objects that referenced the changed object into a warning state. To remove the warning state, the objects required manual validation. | |
| L00136014 | SR 51010375: Float attributes that used scaled Integer inputs were rounded. | |
| L00136048 | SR 31712856: A new Galaxy based on a backup cab file could not be created if the Galaxy name was 12 characters or longer. | |
| L00136054 | SR 103134004: The data quality for field attributes configured as Boolean or float occasionally did not update correctly. | |
| L00136110 | SR 103133825: Data change events for analog and Boolean area attributes were not being recorded in Historian and were instead triggering a warning in the log. | |
| L00136169 | SR 10417772; SR 103134440: After migrating a Galaxy from a previous version to Wonderware Application Server 4.1 (2014 R2), some objects were not displayed in the Model and Deployment views of the IDE. | |
| L00136251 | SR 103134082: ArchestrA Graphics disappeared from WindowMaker or WindowViewer after working correctly for a period of time. | |
| L00136227 | SR 103134493: Entering an IP address instead of node name was accepted for the Time Master node, which would then cause the Galaxy to stop. | |
| L00136496 | SR 103134462: The object description was propagated to the Historian, instead of the field attribute description, when the object or field attribute description was changed and the change was deployed. |
Known Issues - Wonderware Application Server 2014R2 Patch 01
This section describes known issues that remain in Application Server 2014R2 Patch 01.
| OPC UA Client: |
Attributes that include I/O references using Wonderware's OPC UA client service intermittently remain in "initializing" state in Object Viewer when the OPC UA client service is undeployed and deployed, or when the network is disconnected and reconnected.
Workaround: Make sure HotFix CR L00136605 is installed. Determine which object (or objects) contain the attributes that are still in initializing state, then undeploy and redeploy the affected object(s). |
|
| L00112566: | SR 103121156: The engine.ExternalReferenceCntUnbound attribute may display a negative number. This can indicate that there was a configuration error, a communications error or an undeployed node. The negative count is the result of a synchronization issue. It has no impact on performance, and does not by itself indicate that there is an error at the present time. The attribute value can be safely ignored. | |
| L00135918: | SR 10417772: Migrating a Galaxy from a GR where MTD AutoSave was running to Wonderware Application Server 2014 R2 resulted in objects being placed under unassigned objects in the Deployment view.
Additional information is available in Tech Alert TA198 - Migration of a galaxy to Wonderware System Platform (WSP) 2014 R2 fails if that galaxy had AutoSave for System Platform (A4SP) version 2.03 or prior installed Note: The link to Tech Alert TA198 will not work unless you are logged into Schneider Electric Software Global Customer Support (Wonderware Developer Network). Use either of the following workarounds:
|
|
| L00137028: |
In some cases, while running the Field Attribute conversion workflow, the following message may appear in the SMC Logger:
Workaround: No workaround is needed. The objects are successfully converted. Ignore the message in the Logger. |
|
| L00137029: |
If a Galaxy contains one or more redundant platforms that are in a software update pending state (black on orange icon), performing a cascade deploy operation from the Galaxy level will result in the error message: "Aborting undeploy operation..." and the following message will appear in the SMC Logger:
Workaround: Redeploy from the platform level to clear the software update pending (SUP) icon on the redundant platform. Once the SUP icon has been cleared on all redundant platforms in the Galaxy, you can successfully cascade deploy from the Galaxy level, if necessary. |
|
Wonderware Application Server 2014R2 (version 4.1) Readme
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.
|
© 2015 Schneider Electric Software, LLC. All rights reserved.
