Application Server 2012 R2 patch 02 (3.6 patch 02)

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

Wonderware Application Server 2012 R2 Patch 02 Readme

Wonderware Application Server 2012 R2 (version 3.6) Patch 02 Readme

Last revision: 05/27/2014

This document contains three separate Readme files; the current release, and the two prior releases as shown in the following section:

  • Wonderware® Application Server 2012 R2 Patch 02
  • Wonderware® Application Server 2012 R2 Patch 01
  • Wonderware® Application Server 2012 R2

Important!
  • Installation - Wonderware Application Server 2012 R2 (v3.6.000) or 2012 R2 P01 (v3.6.001) must be installed before you can install this patch.

    Installing Wonderware Application Server on a computer used as a domain controller is not supported.

  • UAC - Disable UAC before installing Wonderware Application Server 2012 R2 (v3.6) and InTouch HMI 2012 R2 (v10.6), applicable for Windows Vista and above operating systems.
  • Coexistence - If Wonderware Application Server and the InTouch HMI are installed on the same node, they both must be upgraded to Application Server 2012 R2 (v3.6) Patch 02 and InTouch HMI 2012 R2 (v10.6) Patch 02, respectively.

Wonderware Application Server 2012 R2 (v3.6) Patch 02 Information

Applying Patch 02 to Wonderware Application Server Version 2012 R2 (v3.6)

Resolved Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 02


Wonderware Application Server 2012 R2 (v3.6) Patch 01 Information

Applying Patch 01 to Wonderware Application Server Version 2012 R2 (v3.6)

Resolved Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 01


Wonderware Application Server 2012 R2 (v3.6) Information

Wonderware Application Server 2012 R2 (v3.6) Readme

Known Issues - Wonderware Application Server 2012 R2 (version 3.6)

Resolved Issues - Wonderware Application Server 2012 R2 (version 3.6)

Applying Wonderware Application Server 2012 R2 (v3.6) Patch 02

Close any anti-virus programs running on the computer before you update Wonderware Application Server with Patch 02.

Apply this patch only to Wonderware Application Server 2012 R2 (v3.6.000) or Wonderware Application Server 2012 R2 P01 (v3.6.001). You can check the version number in the Control Panel under Add or Remove Programs (aka Programs and Features).

You can confirm this patch has been installed on a node by verifying the version number is 3.6.002.

Note: You can install Wonderware Application Server 2012 R2 (v3.6) Patch 02 without installing the Wonderware Application Server 2012 R2 (v3.6) Patch 01.

Important!

This patch must be installed on all Wonderware Application Server nodes. On nodes where both Application Server and InTouch are installed, you must install Application Server 2012 R2 (v3.6) Patch 02 and InTouch 2012 R2 (v10.6) Patch 02 in order for them to coexist.

Note: For all configuration and installation operations, Windows User Account Control (UAC) must be disabled or privileges must be elevated to the required level.

  • 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 02 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 3.6 cannot connect to a remote GR node updated with Patch 02.
    • An ArchestrA IDE node updated with Patch 02 cannot connect to a remote GR node still at version 3.6.
  • 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.
  • Prior to applying Patch 02 on the GR node, ensure any active remote IDE sessions are disconnected. Patch 02 requires ArchestrA-related processes be shut down and may require a reboot.

Resolved Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 02

Wonderware Application Server 2012 R2 (v3.6) Patch 02 resolves the following issues listed by their Change Request number:

L00107457: SR 30712432/30711916: The "Lost Alarm Communication" alarm priority was set to 1, which prevented use of that priority for other alarm conditions. This issue has been resolved. You can now manually create a registry entry to provide the alarm priority on all platforms as follows:
  1. Create new registry key "Alarms" under section "HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\"
  2. Create new DWORD value "CommunicationErrorAlarmPriority", and set the value (priority) between 0-999 (Use the decimal option when setting the value.)
  3. If the value for CommunicationErrorAlarmPriority is not set or is out of range, the default value "1" is used.
L00122043: SR 43110215: Error "Failed to deploy : Failed to get the bootstrap's version" occurred while deploying a platform to a Windows 7 client.
L00124709: SR 41610463: Platforms did not deploy correctly and IDE freezes occurred on Windows 7 client nodes.
L00124824: SR 43610739: When using FSGateway in a multi-galaxy configuration and adding a large number tags to FSGateway using an OPCClient tags got stuck in an initializing state.
L00125013: SR 22318077: Items created with syntax <DIObjectName>.<TopicName>.<Attribute(ItemName)> would go from bad to good quality repeatedly if the Buffered Data option was checked for a User Defined Attribute (UDA).
L00125088: SR 48910069: Field Attributes did not show the correct value unless configured for Buffered Data, and Integer Field Attribute values could not be set to zero if the initial value of the Field Attribute was other than zero.
L00125123: SR 37112904: Multiple issues occurred with the OPCClient Object, such as performance and reconnect, engine scan overruns even when the object was idle, block read and block write triggers were slow and disconnect behaviours were mishandled.
L00125295: SR 14832266: Adding dynamic primitives for some attributes failed due to a name conflict in the database. An error is now logged when adding a dynamic primitive conflicts with a graphic that has an identical name.
L00125485: SR 44510170: When more than one instance of the MxAccess ActiveX sample was registered in an InTouch application, unregistering one MxAccess sample ActiveX control caused WindowViewer to hang.
L00125741: SR 31611867: The System.String.Join function returned "System.String[]" instead of the actual value of the array string.
L00126318: SR 14832305/15712683: A re-registration issue in the alarm NotificationDistributorRuntime reactivated old alarms that could then not be acknowledged.
L00126469: SR 43110295: Deploying a redundant engine that has areas and objects without selecting the Cascade Deploy option resulted in the loss of all running objects.
L00126489: SR 27811031: Alarms on a remote node, queried through a remote desktop session, intermittently could not be seen.
L00126520: SR 45510344: An InTouch Window with ArchestrA graphics required more than normal time to save.
L00127372: SR 14413640: Reads and writes from a third-party OPCClient via FSGateway to a User Defined Attribute (UDA) could not be done when using Chinese characters.
L00127379: SR 45110257: Both primary and redundant engines went active at the same time.
L00127643: SR 43110295: Areas and contained objects showed warning messages after validation.
L00127759: SR 43110326: The DiscreteDevice object showed incorrect values when the Advanced Communication Mode was enabled.
L00128024: SR 46810184: With the regional settings set to German, switching to ArchestrA security added a suffix of .5 to all analog tags when shown as text strings.
L00128094: SR 49410008: Instances with bad items that did not exist in the PLC caused a slow down of the AppEngine until it ceased responding.
L00128535: ArchestrA Workflow Server 2012 R2 SP1 Gateway objects could not be configured on Wonderware Application Server 2012 R2
L00128546: SR 15712744: Pokes to Application Object attributes failed when OSGroup-based security was configured and integrated with FSGateway.
L00128575: SR 45110229: Loading a Galaxy from a .csv file required a long time even though few parameters had changed.
L00129017: SR 103129747: The "Enable state label" for a Discrete Field Attribute did not work for OPR events.
L00129089: SR 37112888 and SR 103128979: When a remote data source node time synced, a "timestamp out of sequence" warning was logged for every item being polled. This log warning is now set under a custom log flag, "Log OutofSyncTimestamps", which is disabled by default. The "timestamp out of sequence" warning will not appear in the logger unless the custom log flag is enabled.
L00129116: SR 103128979: Two systems were successfully time synced after drifting out of sync, but an excessive number of messages were reported to the OPCClient. These messages were benign, but had the potential to fill the log.
L00129089: SR 37112888 and SR 103128979: When a remote data source node time synced, "timestamp out of sequence" warnings occurred for every item being polled.
L00129496: SR 103130007: Object Viewer showed incorrect Boolean array values from a BACnet OPC Server, but the individual array elements showed correct values.
L00129575: SR 103129209: Some graphics were lost while importing a new Galaxy version and then overriding the objects.
L00129833: SR 41810243: The RDI object was in disconnected state while both source DI objects were partially connected.
L00129813: SR 103129988: Attempting to access the system using smart card credentials resulted in the error message "User does not belong to any of the configured roles." With operating system security, InTouch uses the user name obtained from the "Common Name" attribute of a certificate to log on with a Smart Card. In this case, the user name specified by the "Common Name" attribute differed from the operating system user name.
L00130333: SR 33812522: WindowMaker displayed a red X when selecting an alternate instance on an embedded ArchestrA Graphic where the instance of the object had containment with another object instance.
L00130716: SR 19818424: A corrupted symbol in an Object disabled the Symbol editor "embed graphic" functionality. The GraphicBrowserControl displayed an error and became unresponsive.
L00131142: SR 33411322: Error occurs when using Write2() and advise the item using AdviseSupervisory ().
L00131224: SR 42010087: Incorrect mapping of the item resulted in an error in SMC.
L00131389: SR 103130791: Ondatachange event is generated continuously when the Field Attribute is configured with scaling.
L00131391: SR 40215771: On the HMI, graphic shows an alarm state when there are no active alarms because the quality of "InAlarm" gets stuck in the "Initializing" state.

< top of document >


Wonderware Application Server 2012 R2 (version 3.6) Patch 01 Readme

Last revision: 07/31/2013

This document includes information about Wonderware® Application Server 2012 R2 (version 3.6) Patch 01. It updates the previous Readme files included with Application Server 2012 R2 (version 3.6).


Important!
  • Installation - Application Server 2012 R2 (v3.6) must be installed before you can install this patch.

    Installing Application Server on a computer used as a domain controller is not supported.

  • UAC - Disable UAC before installing Wonderware Application Server 2012 R2 (v3.6) and InTouch HMI 2012 R2 (v10.6), applicable for Windows Vista and above operating systems.
  • Coexistence - If Wonderware Application Server and the InTouch HMI are installed on the same node, they both must be upgraded to Application Server 2012 R2 (v3.6) Patch 01 and InTouch HMI 2012 R2 (v10.6) Patch 01, respectively.

Wonderware Application Server 2012 R2 (v3.6) Patch 01 Information

Applying Patch 01 to Wonderware Application Server Version 2012 R2 (v3.6)

Resolved Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 01


Wonderware Application Server 2012 R2 (v3.6) Information

Wonderware Application Server 2012 R2 (v3.6) Readme

Known Issues - Wonderware Application Server 2012 R2 (version 3.6)

Resolved Issues - Wonderware Application Server 2012 R2 (version 3.6)

Applying Wonderware Application Server 2012 R2 (v3.6) 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 2012 R2 (v3.6). You can check the version number in the Control Panel. See the Add or Remove Programs section under Wonderware Application Server.

Important!

This patch must be installed on all Wonderware Application Server nodes. On nodes where both Application Server and InTouch are installed, you must install Application Server 2012 R2 (v3.6) Patch 01 and InTouch 2012 R2 (v10.6) Patch 01 in order for them to coexist.

Note: For all configuration and installation operations, Windows User Account Control (UAC) must be disabled or privileges must be elevated to the required level.

  • 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 3.6 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 3.6.
  • 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.
  • 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 2012 R2 (v3.6) Patch 01

Wonderware Application Server 2012 R2 (v3.6) Patch 01 resolves the following issues listed by their Change Request number:

L00082941: SR22315571: Custom help added to a derived template object appeared when help was invoked from instances but not from the derived template itself.
L00087517: Deleting an InTouchViewApp template that was locked by another process resulted in an unclear dialog box and error message.
L00093278: SR 103115883: Level alarms configured on a Field Attribute were set to true immediately on breaching the alarm threshold even though the configured time deadband had not been exceeded.
L00100718: SR 103117318: Item references for Topic-specific Attributes did not appear when DIObjects are opened in Read-Only mode, but did appear when DIObjects were opened for editing.
L00110869: Under certain conditions, a symbol configured with an OnShow script could result at run time in the null reference error "Object reference not set to an instance of an object."
L00116706: SR 103122399: The LogDataChangeEvent function did not correctly log time in the EventStamp column, and entered 0 in the EventTimeZoneOffset column. Time logged in the EventTime column was correct.
L00119452: SR 31712002: The SQL database location defaulted to c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data, not to the location set by the SQL server.
L00119620: SR 103123957: The ArchestrA Object Toolkit (AOT) DeleteAttribute() function resulted in the "Attempted to read or write protected memory..." error.
L00121185: HF CR L00120870: The script execution order was inaccessible and the Configure Execution Order listbox disabled when opening the object editor for a read-only user defined derived template or instance. Scroll bars are now enabled for read-only templates or instances.
L00122784: HF CR L00122616: The ScanGroupRuntime2 intermittently dropped writes resulting in unexplained Tag write time-outs and Batches being put on hold.
L00122845: HF CR L00122598 SR 45710085 and SR 103125662: Importing an InTouch 9.5 application to InTouch 2012 failed and displayed "Import operation aborted. Source file is in ReadOnly Mode."
L00122847: HF CR L00122678 SR 103125882: Using the SetAttributeVT function resulted in the error message, "Attempt to read or write protected memory."
L00123014: HF CR L00121864:Writing to an item from a scan group configured for a five (5) minute scan cycle did not return the value until after the next scan cycle. Implementing the Demand-Read After Write enhancement resolved the issue.
L00123287: HF CR L00123250: Changes to a template description were propagated to instances with and without LOCK.
L00123729: HF CR L00121815 SR 25315245: TSE sessions timed out, and the anonymous engine IDs were not recycled, resulting in the "CNmxAdapter :: GetAnonymousEngineID - FAILED" error message.
L00123778: HF CR L00123679: When a two-way selective trust was enabled for the ArchestrA network account and one-way outgoing trust was enabled for all users, the IDE failed to open an object on first attempt.
L00123813: HF CR# L00123574 SR 10512085: The redundant AppEngine failover displayed unknown errors and became quarantined because of a time constraint in the SetAttribute.
L00123944: HF CR L00123705 SR 12912660: Bootstrap failed to create an instance of Bootstrap on a remote machine, and displayed an "access denied" error message.
L00124013: HF CR L00124000: Engine CPU usage stuck at 100-percent when engines tried to resubscribe with the remote platform. Communication had been lost between the platforms while an ESX server snapshot was being taken.
L00124108: HF CR L00122772 SR 43610579: The Stats.Reset field was set to true, but did not set the elapsed times of the TimeSinceLastTransition to 00:00:00:000. The value for TimeSinceLastTransition kept increasing.
L00124300: HF CR L00123769 SR 103126710: A field attribute alarm value was "false" instead of "true" after redeploying objects.
L00124408: The GR Browser Service crashed when a Galaxy was created, but the IDE showed the service instance as deployed.
L00124529: When performing write operations on attributes running on a redundant engine which is failed over, the reason description for remote secured and verified write attributes showed the "retrieving reason description" message for a few seconds then went blank. The reason description was not retrieved.
L00125047: HF CR L00124940 SR 27810889: A User Defined Object Analog Field Attribute displayed incorrect values in an S7 PLC, using the SIDirect DAServer.
L00125309: HF CR L00125111 SR 14812231: A high number of missed MX heartbeats occurred (NetNMXHearbeatsMissedCnt) across all platforms in the Galaxy. Part of the resolution includes the following edits to the Windows Registry:

Create a DWORD registry value "HeartBeatTolerance" on the path

"HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\Nmx" for a 32-bit machine, and

"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\Nmx" for a 64-bit machine

Note: The value is in milliseconds. A value of 0 is disabled. The enabled range is from 1 to 250 milliseconds.

L00125529: HF CR L00125442 SR 34211435: The GlobalDataCache service stopped synchronizing with the Galaxy Repository.
L00125637: HF CR L00125468: When testing asynchronous subscription using a Matrikon OPC server, items became stuck initializing.
L00125639: HF CR L00125506 SR 14832275: When hosting an RDI object on a Redundant Engine, references went to BAD quality on failover, bypassing the "Maximum time to maintain good quality after failure" setting.
L00126320: HF CR L00126035 SR 15712676: Duplicate alarms appeared with the same timestamp in the WWALMDB when alarms were generated every second in the Alarm Viewer Control summary.

< top of document >


Wonderware Application Server 2012 R2 (version 3.6) Readme

Last revision: 10/24/2012

About This Readme

This Readme provides information about important resolved and known issues for Wonderware® Application Server 2012 R2 (version 3.6).

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

Known Issues

Resolved Issues

This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.

L00092147: SR 103115692: If the Galaxy Browser was open in the second monitor in a dual-monitor system, then the dual monitor was changed to a single monitor, the Galaxy Browser position was out of bounds and could not be seen on the single monitor. A change in user preference settings to include the number of monitors resolved the issue.
L00094592: SR 103116159: An error pop-up dialog, "Attribute not writeable", appeared when saving a template derived from DDESuiteLinkClient. This issue has been resolved.
L00107457: SR 30712432/30711916: Lost alarm communication alarm priority was set to 1, which prevented use of that priority for other alarm conditions. The issue has been resolved. You can now manually create a registry entry to provide the alarm priority. Add the registry key CommunicationErrorAlarmPriority under the registry section HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\Alarms and set the value (priority) between 0-999 (Use the decimal option when setting the value.) If the value for CommunicationErrorAlarmPriority is not set or is out of range, the default value (1) is used.
L00108759: SR 10416087: Galaxy dump did not properly export or import scripts with names beginning with an underscore character (_). Importing the .csv file back to the Galaxy resulted in an empty script.
L00104182: SR 38910250: Intermittent LMX errors appeared while erasing References from the Unresolved References list. The issue is now resolved.
L00108975: SR 15315829: Exporting objects from a remote IDE created temporary folders that were not deleted upon completion of export, consuming large amounts of disk space.
L00109878: SR 20113801: Setting the same limits for Lo and LoLo alarms resulted in the error message "PV: The HiHi limit must be greater than the LoLo limit". The error message has been corrected and the issue resolved.
L00111121: SR 103120422: State change events were not logged into the Alarm Database, for example, when changing the DiscreteDevice_001 PV state. Instead, logging events errors appeared in the logger.
L00112065: SR 103121279: Incorrect script syntax caused the AppEngine to crash. It could not be redeployed or undeployed. The issue is resolved.
L00113024: SR 42410004: Validation was not automatically performed when an object was moved from one parent object to another when the object was checked out.
L00112980: SR 20611106: Checking in an InTouchViewApp template failed when the revision number exceeded 32767.
L00115425: SR 15712461: The value deadband for a Field Attribute was not working as expected. All values updated regardless of the size of the value change.
L00116208: SR 103122477:: Deleting the description field of a Field Attribute in an instance, followed by a Galaxy load operation, resulted in the content of the template Field Attribute description being rewritten to the instance.
L00116783: Installing Application Server as a product was blocked if a version of SQL Server 2008 newer than SP1 (SP2 or 64-bit SP1) was used.
L00116979: SR 40212165: Derived objects migrated to newer versions were not being properly stored when importing a new version of a base template into a Galaxy. The issue has been resolved.
L00117300: SR 34211168 Galaxy backup failed on a hard drive with insufficient disk space, even though the backup location was another drive with sufficient space. Temp backup files were still written to the local drive, causing the backup failure. The issue has been resolved.
L00117320: Problems were experienced with the stored procedure "internal_set_host_association" when importing an export file. The issue was related to a known SQL Server 2008 SP2 issue.
L00117497: Performing a bulk operation from the IDE, such as propagation of changes from a template to all derived templates and instances, did not take advantage of all available cores in the PC. At least 2-3 cores seemed blocked. The issue has been resolved.
L00117541: SR 33811846: Updates to a UDA reference were not reflected in Object Viewer in a redundant system after failover to the secondary then return to primary. The UDA reference took the original value before the deployment changes.
L00117558: SR 43110090: After redeploying an object following a cascade check in of the parent template, a script stopped executing even though the script trigger (WhileTrue) was evaluated as true.
L00117607: Creating an instance of a template containing less than 60 objects, but containing numerous visual elements, contained templates, and instances, required an unusually long time. Optimizing the change propagation, template instance creation, and renaming operations resolved the issue.
L00117700: SR 15316256: Deployment of a platform on a Windows 7 64-bit computer required 18 minutes, far longer than a normal deployment. This issue has been resolved.
L00117885: SR 20114109: User authentication against the local active directory failed. Wonderware Application Server was attempting to authenticate against the primary domain controller, which was blocked by a firewall. Logon optimization resolved the issue.
L00118112: SR 37112243: With an RDI connected to two DDESuitelinkClient objects, when the active DDESL object was set to OffScan, the RDI connection status went to OffScan. When the DDESL object was put back OnScan, the RDI remained disconnected until it was redeployed.
L00118126: SR 103121095: OPC quality was incorrectly represented as Bad. This state information also was logged into the Historian. Data quality interpretation in Wonderware Application Server did not match interpretation of data quality in OPC.
L00118198: SR 37611734/37611747: Under certain circumstances, a Redundant Device Integration (RDI) item stayed in Initializing quality or became stuck in Bad quality, even though the DI source shows Good quality.
L00118241: SR 38910352: The platform stopped communicating with its partner and the message channel library was stuck sending messages. Symantec antivirus was running on the platform nodes, and the Symantec drivers seemed to be blocking the messages. The issue has been resolved.
L00118498: SR 103123638: Advising an item continuously caused a memory leak, resulting in a steady increase in memory consumption.
L00118617: SR 29710009: Importing an aaPKG file caused galaxy corruption of some templates and objects. This occurred when importing the aaPKG with the overwrite option enabled.
L00118863: SR 103123076: When undeploying a RedundantDIObject (RDI) with an incorrectly configured backup DI source, then redeploying, an" access denied" error message appeared on the RDI and the ScanGroup.
L00118970: Opening a DI Object in "Read Only" mode did not display the ScanMode column in the Topic Tab.
L00119060: < GRAccess application function QueryObjects failed to find objects in deployment pending status.
L00119210: SR 40210818: When one redundant AOS shut down, the AppEngines intermittently did not fail over. In some instances, those AppEngines that did fail over started in standby.
L00119231: SR 45110020: ArchestrA security did not provide a username sort function. This was inconvenient, especially when large numbers of users had accounts in the system. A sort function has been added to the User tab of the IDE Security Configuration dialog.
L00119237: SR 38910367: Under certain circumstances, the write completion callbacks from a connected DAServer were not called in the DDESuiteLinkClient DIObject. Randomly, individual item writes initiated to individual attributes of the DDESuiteLinkClient DIObject failed to be acknowledged.
L00119425: SR 103124193: Using Top Server OPC Server 5, pulling the ethernet cable from the PLC caused the OPC Server to send Bad quality for polled items, but OPCProxy showed items as Initializing in Object Viewer.
L00119615: Associated files were deleted from the CheckedIn folder even though the PreCheckIn event failed.
L00119762: WindowViewer crashed during attempt to log in with ArchestrA security set to OS Group.
L00119774: Running QueryObjects from a GRAccess application failed to find FCS (non-ArchestrA) objects needing redeployment.
L00119891: SR 103124434: The Anonymous Engine ID intermittently did not recycle correctly when opening, closing, and reopening WindowViewer, and caused WindowViewer to crash.
L00120192: A Galaxy created from a .CAB file that was backed up in Application Server 3.2 failed to migrate on an Application Server 3.5 machine if the Galaxy name provided was not the same as the one backed up in Application Server 3.2.
L00120400: After making changes to the RDI object, all AppObjects referencing the RDI object went to a warning state. To remove the warning state, the AppObjects required manual validation.
L00120626: SR 20114325: The IDE connection froze when synchronizing security (OS Group-based) with the Active Directory.
L00120677: SR 38910393: OPC DI needed to implement a Time Sequence validation and a Read when subscribing Active references.
L00120678: SR 22317676: DDE/SuiteLink DI needed to implement a Time Sequence validation.
L00120709: SR 37112565: When the active DAServer was deactivated, the RDI failed over, but the item reported Bad quality on the RDI, even though the item reported Good quality on the active DDESuitelink DI source object.
L00120980: SR 38910394: Items became stuck in Initializing state after switching between ArchestrA graphics using ShowGraphic.
L00121007: SR 38910395: The script execution order was not accessible when opening a UserDefined derived template/instance read-only.
L00121023: SR 24910041: LMX writes failed in certian circumstances when the item had not yet been added to the DI object scan group item list.
L00121187: SR 31711844: The OPCClient kept disconnecting and reconnecting even though the OPC Server was local to the OPCClient, resulting in "Warning OPCClient Target Node is missing" messages.
L00121293: SR 12612158: The GR machine was deregistered from an old domain and registered in a new domain. Subsequently, the IDE was not able to browse for users in the new domain but was still able to browse the users in the old domain.
L00121453: SR 38910398: When events were logged, the Operator Node Name included an unexpected suffix.
L00121940: The ArchestrA IDE displayed an access warning dialog at startup, and opened in read-only mode.
L00122211: SR 31712114: Deploying only one platform of a redundant pair required 2-3 times longer to deploy than when also deploying the redundant platform. Continuous scan overruns then occurred on the engine until the engine was either taken off scan or the redundant platform was deployed.
L00122213: SR 10416742: When using the SignedWrite() function, events were not logging the full details of the verified write operation and an unhandled .NET error occurred.
L00122221: SR 103125569: When using the SetData method to insert a value to element 0, SetData did not check whether the array was 0 index or not, and called the SetAttribute function. SetAttribute did not treat the array with 0 index as an array, considered it to be a normal value, and destroyed the array attribute.
L00122253: SR 33933024: During run time, handles grew on aaGR.exe until the process crashed.

< top of document >

Known Issues

This section describes important known issues.



L00069519: In a redundant load sharing environment, the cascade deployment of a backup platform does not deploy InTouch ViewApp instances, if the redundant AppEngine has InTouch Proxy objects configured. Backup redundant object errors are logged. After the InTouch ViewApp deploy fails, it can be manually re-deployed.
L00076557: Opening and closing a view window when "Advanced Communication Management" is enabled for the Galaxy may cause a different timestamp to be returned for the attribute from the DAServer, even though nothing has changed on the device.
L00077487: During tag registration, Wonderware Historian discards the value for SampleCount (isSamples) provided by Application Server.

Before installing Wonderware Application Server 3.1, apply Wonderware Historian 9.0 Patch 02 to resolve this issue.
L00077490: Importing a client control from a Galaxy imports another version of the same client control if the other version resides in a different Galaxy on the same node.
L00078221: After you migrate an Application Server 2.1 application to Application Server 3.0 or later, the wrong value is returned for the .NET ToLocalTime() function.

Application Server 2.1 supports .NET 1.1, while Application Server 3.0 supports .NET 2.0. The DateTime structure in .NET 2.0 includes a new Kind property that indicates whether the time represents a local time, a Coordinated Universal Time (UTC), or whether UTC or local time is not specified. For more information, see the following Microsoft documentation: http://msdn.microsoft.com/en-us/library/system.datetime.aspx

To migrate an Application Server 2.1 application to version 3.0 or higher, you must modify scripts that use the ToLocalTime() function. Use the new Kind property (DateTime.KindProperty) and specify the time before you run the ToLocalTime() function. For example:

dim aTime as System.datetime;
dim aTime2 as System.DateTime;
aTime = me.lastpolltime;
aTime = system.datetime.SpecifyKind(aTime, system.dateTimekind.utc); me.locallastpolltime = aTime.tolocaltime();
L00078446: The ArchestrA Symbol Editor stops responding when you edit the "format string" property of the "checked list box" client control.
L00078465: Dates earlier to 1970 are not valid for purposes of the LogDataChangeEvent() script function. Using a date earlier than 1970 sends a warning message to the logger.

Use a date on or after 1/1/1970 when using the "LogDataChangeEvent()" script.
L00079595: Attempting to import a client control with the ArchestrA IDE fails if the file is located at a remote network location. Copy the client control file to the local computer where the ArchestrA IDE is installed to import operation.
L00081837: The following error message appears when a non-upgraded IDE node (earlier than Wonderware Application Server 3.0 SP2) tries to connect to an upgraded Galaxy Repository node. Error message: "IDE cannot connect to remote GR node <name> because it is an older version <number> than this IDE version supports."
L00083270: Spaces are not imported as part of the translation for the selected language.
L00083909: InTouch applications receive Quality Status and Locale information from the deployed Galaxy. InTouch applications cannot receive data from an undeployed Galaxy.
L00084306: StringFromTime() results are different in InTouch and Application Server. InTouch converts a timestamp given in UTC time to local time and returns the result as a string. This function takes Daylight Saving Time into account. The ArchestrA StringFromTime function still returns the time as GMT. Also, if you change the time zone while WindowViewer is running, the new time zone is not taken into consideration for script functions. On restart of the WindowViewer, the new time zone is taken into account for the script functions. This behavior occurs because time zone information is set during the view initialization.
L00085806: The font used for graphics in ArchestrA symbols does not render properly in the Symbol Editor and on print outs, if the DPI of the screen or printer is less than or greater than 96-dpi.

Wonderware does not support running the product in DPIs other than 96 DPI.
L00086242: Unable to connect to test server nodes when using the SuiteLinkDDEClient object and trying to connect to a local server on Windows Vista. Connection is successful to the Windows XP and Windows Server 2003 nodes. The issue does not occur if you put "localhost" in the node name of the DDESuiteLink DI object.
L00087046: An embedded symbol is lost after swapping symbol names. VERL (Visual Element Reference List) corruption is artificially causing a circular reference.
L00087247: InTouchViewApp fails to undo a checkout when there is a file-lock within the CheckOut folder. You should not attempt to check-in the InTouchViewApp.

Fix the file-lock issue, and perform the "undo-checkout" again.
L00087305: When you rename a referenced symbol while an object editor is open, the reference to the renamed symbol may be lost.
L00087471: The background reference binding thread may stop processing because of a database connection failure. The following message is logged in the System Management Console: "Warning WWCdi CRefString(TagName Validation). Database connection is no longer valid."

You must restart the aaGR.exe process to reestablish the connection to the database server.
L00087752: You must restart the aaGR.exe after you import an object with a minor version increment, if the object is written in .NET.

The issue may occur for ApplicationObjects written in .NET with the ApplicationObject Toolkit 3.1, versus ApplicationObjects written with an older version of the ApplicationObject Toolkit.

Restart of the aaGR.exe is required if all of the following apply:
  • DotNetAppObject version 1.0 is loaded in the Galaxy
  • An object vendor creates a new minor version of DotNetAppObject version 1.1
  • An IDE user imports the new .aaPKG file with DotNetAppObject version 1.1 into the Galaxy that has DotNetAppObject 1.0 loaded.

    You must restart aaGR.exe for the new object to be recognized and deployed to the IDE nodes.
  • L00089937: Importing a major version of an object instance that is on a platform which is currently deployed will result in aaPIM logged messages. To resolve the issue, the platform hosting the object must be undeployed to clear the errors.
    L00092635: Application Server 3.1 SP2 will import an alarm comment file for language switching of format Galaxy_ACLSGalaxy1_2058_Alarm_Comments_Untranslated.txt but InTouch WindowMaker doesn't recognize the file. This behavior is as-designed. InTouch will only recognize file format %_AlarmComment.txt. The option to export untranslated comments was provided in Application Server in order to diagnose and verify quickly whether all translations for a specific locale have been done, and to manage or find untranslated alarm messages in large galaxies. This functionality was provided as value added for Wonderware Application Server, but was not required for InTouch.
    L00092675: In the alarm comment run-time language switching feature, the PhraseId can go out of sync in exported files for the same alarm message in different languages. This does not cause problems in exporting or importing alarm messages into the Galaxy, but it can lead to a failure in InTouch to switch the alarm comment language in run time. Alarms for which the PhraseId does not match between the different languages will not switch. Instead of showing the translated message, the default alarm message, in English if the Galaxy was created in English, will be displayed.

    The Lang.dll in InTouch has been modified to log a warning in the SMC that the current alarm message does not match across translated languages. The message recommends that you re-export all the languages of the conflicting file from the Galaxy, and re-import them to the InTouch application. The conflicting file name will be part of the message. We recommend that you keep all the translated exported language files in sync.

    L00093428: In Windows Vista and higher operating systems, the DDE cannot communicate across sessions. This is a User Interface Privilege Isolation (UIPI) issue. For example, with Wonderware Application Server running in Session 0 as a service, Excel would run in a session other than 0, a User interactive session. In this scenario, DDE is not able to communicate across the session. SuiteLink can work in place of DDE under certain conditions.
    L00093558: When you upgrade from Wonderware Application Server version 2.5 to version 3.1 SP1, the following error message appears: "ArchestrA.Configuration.PackageServerNet.PackageServerNet instance not properly disposed." The error message is informational. No action is required.
    L00093559: The calendar control in the graphic editor is drawn with different size fonts on different operating systems. For example, the sizes shown are different on Windows Server 2003 and 2008 operating systems. The size of the calendar control does not change when you change the font on the Windows Vista operating system. If a symbol with calendar control is saved in a Windows Server 2003 system and then opened in a Windows Server 2008 system, the size changes after export and import. This affects the symbol layout as well. As a workaround, ensure that your operating system themes are consistent in screen resolution, DPI, icon size, and font size settings.
    L00095432: After Installing ArchestrA products such as InTouch, InTouch CE, Application Server, InSQL, and ActiveFactory 9.2, some DAServers cannot be installed. During the DAServer installation, a Prerequisite Setup Error appears, "Rainbow Sentinel setup failed to complete successfully." The issue does not occur if the DAServers are installed first and then ArchestrA products are installed. This issue will be addressed in future DAServers releases.
    L00095452: The Reactor_Demo_Application_Server displays name conflict errors while attempting to enable history for several $ReactorSet.Reactor field attributes such as ConcPump and ConcValve. The issue appeared in Wonderware Application Server 3.1 which added the capability in the Extensions section to add a description in the history extension. This modification has created a conflict with field attributes and object graphics.
    L00095695: When using Microsoft SQL Server 2008 Development Edition, the GR service fails to connect and freezes. This issue occurs because the Development Edition of SQL Server, which is not supported by Wonderware Application Server, does not enable TCP/IP service by default.
    L00095744: The Microsoft OLE DB provider for Oracle and neither Driver do Microsoft Access[*.mdb] nor Driver do Microsoft Excel[*.xls] are visible in a Windows Server 2008 64-bit SP2 Standard Edition operating system with SQL Server 2008 SP1 installed. These drivers are 32-bit drivers and are not visible in a 64-bit system directly from Control Panel, Administrative Tools, DataSources(ODBC). You can create ODBC connections by running C:\Windows\SysWOW64\odbcad32.exe. This is a 32-bit application, which will display 32-bit drivers. This issue does not occur on 32-bit systems.

    Microsoft does not provide a 64-bit OLE DB Provider for Oracle. Oracle provides a separate OLE DB Provider for use on 64-bit systems.

    L00097202: Memory use rapidly grows when running an application that has InputSource changes every 5 seconds (200 UDAs) and BindTo changes every 10 seconds. Due to a synchronous script timeout, the code does not clean up the local indirect created at the time of script execution, which increases the size of the reference table in the LMX and leads to the memory leak.

    There are three possible workarounds to stop the memory leak:

    1. Declare the array of indirect into the Declarations section rather than inside the script.
    2. Reduce the sleep time inside the script or increase the Maximum time for script to execute in the engine configuration, so that script does not timeout.
    3. Use the asynchronous script with an appropriate timeout limit.
    L00097788: Existing license CDs have issues running aaLicView.exe in a 64-bit operating system and will not correctly install a license. You must use the license utility installed with the Wonderware Application Server or InTouch software.
    L00098305: After upgrading the GR node, a Deploy/Un-deploy attempt on a non-upgraded remote platform undeploys InTouchViewApp and ViewEngine assigned under the non-upgraded Remote platform.
    L00098946: With Scan on Demand (SOD) enabled, if an item is activated, deactivated, then reactivated it will return the last value available before it was suspended rather than the current live value. This behavior does not occur if SOD is disabled.
    L00099445: With SQL Server 2008 installed, and Wonderware Application Server 3.1 SP2 installed (IDE and Bootstrap only), attempting to add a Galaxy Repository using Modify, add GR (Add/Remove Programs, Change option) fails as the Add GR option does not automatically run the aaConfigSQL utility. WWCdi and WWPackageServer errors appear in the logger. This occurs only with SQL Server 2008 installed, and only when the initial Wonderware Application Server installation was performed using a local account.

    As a workaround, you can run the aaConfigSQL utility manually prior to running the Modify, Add GR option.

    L00099447: An object attribute with an input extension referring to another object attribute remains suspended after deployment when used in a script. This behavior only happens if the object attribute has no other references and is deployed to the backup engine with the primary engine undeployed. The workaround is to add a reference to the object attribute, such as adding it to a watch window, to trigger the activation so that its value, timestamp and quality can be posted appropriately.
    L00099472: On Windows Server 2008 32/64-bit and Windows Vista 32/64-bit operating systems, with Wonderware Application Server installed from CD media rather than from a network location or local install folder, adding a Galaxy Repository using the Modify, add GR option (Add/Remove Programs) fails to add a GR. Modify fails to find the path to setup.msi. This issue does not occur with Windows Server 2003 SP2.

    As a workaround, you can run the Modify option from the CD image with elevated privileges.

    L00099557: If you create a symbol with two or more custom properties, then modify the values of one custom property in the properties grid, then select the value field of the other custom property to modify it, the second property's value field shows as blank. Any already existing value disappears from the second custom property value field. The value itself is not erased, but is not shown.

    As a workaround, reopen the symbol and use the Custom Properties dialog box to populate the custom property values.

    L00104907: Tooltip animations are not working for WCC controls.
    L00105138: On the Windows Server 2008 and 2008 R2 operating systems, the UI controls for the $WinPlatform derived template do not align correctly.

    Workaround: Right-click Computer and then click Properties. Click Advanced system settings, and then click the Advanced tab. In the Performance area, click Settings. Click to clear the Smooth edges of screen fonts check box.

    L00106038: Errors are logged while deploying PEM objects. Factelligence 3.5 (PEM, FMM, MEM) objects are not supported in the current version of Wonderware Application Server. Upgrade to MES version 4.0 or higher is required.
    L00106046: On Windows Server 2008 R2 64-bit and Windows 7 32-bit operating systems, if you attempt to uninstall Wonderware Application Server while the IDE is open or while connected to a Galaxy, you will see a warning message. If you click Retry, without closing the IDE or Galaxy connection, Wonderware Application Server will continue to uninstall as if you had selected the Ignore option.
    L00106124: Importing objects built in AOT 3.1 or higher, minor version upgrade, can take a long time even if the object is changed only for editor assembly. Use the following steps to create an AOT object with minor version changes which should contain only editor changes and no changes in package logic:
    1. Open the base version AOT 3.1 or higher object in Visual Studio and do the required changes to the editor.
    2. To bump up the <Object name>Editor1.dll file version by modifying the file version information in the AssemblyInfo.cs file in the following example "<Object name>Editor" project:
      assembly: AssemblyFileVersion("1.2.0.0")
    3. To bump up the object's minor version modify the <Object name>.cs file in the following example "<Object name>.cs" project:
      ObjectAttributes.MinorVersion(2)
    4. Rebuild the object to get an object with a minor version change containing changes in the editor only.
    L00106403: If extensions (InputOutput, Input, Output, Alarm, or History) are added to a Field Attribute via the Extensions tab and the Field Attribute is later renamed, the Field Attribute's configuration structure can become corrupted.

    Workaround: Configure Field Attributes using only the options available on the Field Attributes tab in the editor of the $UserDefined object; do not configure a Field Attribute using options from the Extensions tab of the editor.

    L00106782: Certain IDE operations performed under the following configuration are much slower on Windows Server 2008 R2 and Windows7 operating systems than on earlier releases of Microsoft Windows:
    • The GR-node is a member of DomainA.
    • The interactive (logged-in) user on the GR is a member of DomainA.
    • The ArchestrA Network User is an account in DomainB.
    • The network connection to the DomainB Domain Controller is slow (little bandwidth, high latency).

    The following operations may slow down by a factor of 2 or 3:

    • Editing objects.
    • Deploying objects.
    • Deleting objects.

    Workaround:

    1. Ensure the network connection between the GRnode/IDEnode and the domain controller (that the ArchestrA network user is a member of) is fast and has low latency.
    2. Have the Galaxy nodes, the interactive user (logged in user) and ArchestrA Network user all are members of the same domain.

    For more information, see Tech Note #719.

    L00107322: The Windows Server 2008 R2 (64-bit) operating system running on VMware occasionally "locks up" or "hangs," and the user interface is no longer responsive (although tasks may still run in the background). This problem is not related to any software application installed on the computer and can be corrected by upgrading the VMware video driver. To upgrade VMware video drivers, you must upgrade the VMware tools, which includes all the drivers for the system.

    This problem was experienced during testing of this release using the following VMware Software:

    • VMware, Inc. vCenter Lab Manager 4.0 (4.0.1.1233)
    • VMware Tools = Old Version (add/remove programs) = 3.1.2.7193
    • VMware Tools = Old Version (Help/about) = 3.5.0, B123630
    • Video driver version = Old Version (Display properties) VMWare SVGA2 version 11.04.03.0002 (11.4.3.2) 7-28-2008

    The problem can be corrected by upgrading VMware tools and the video driver with the following versions. Note that additional information can be found at the following VMware link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011709.

    • VMware Tools = Upgraded Version (add/remove programs) 8.0.2.14744
    • VMware Tools = Upgraded Version (Help/about) = 4.0.0 B208167
    • Video driver version = New Version (Display properties) VMware SVGA 3D (Microsoft Corporation - WDDM) Version (7.14.1.31) 9-17-2009

    L00107919: When you log on to the ArchestrA System Management Console (SMC) Platform Manager with a newly-created, Active Directory OS Group account for Wonderware Application Server, and that OS Group account does not contain a "Full Name" description, the following error is generated: "User does not belong to any of the configured Roles". This also occurs when you log on to an InTouch application or Object Viewer.

    To work around this issue, log on to the ArchestrA IDE first using the new OS Group account and then log on to the SMC, InTouch application, or Object Viewer.

    L00108399: When saving an object ("myudax0" in this example) that has a User Defined Attribute (UDA) with input extension created using GRAccess with the buffered data property enabled, the follow error message is displayed: Buffered enabled UDA 'myudax0' does not have an input source.

    As a workaround, add the extension in GRAccess with type "inputextension" instead of "InputExtension".

    L00108539: The following message is displayed when AOT tries to connect to a Galaxy from an out-of-sync IDE node even though there are no other clients connected to the same Galaxy:
    Test Galaxy
    Connection to Galaxy 'Test' failed.
    Text: Unknown error.
    CustomMessage: Cannot Synchronize client as other clients are active.
    OK
    As a workaround, synchronize the Galaxy through the IDE first and then start the AOT.
    L00109396: The following warning is logged in IDE and Bootstrap nodes during upgrade of an undeployed galaxy:
    Warning msiexec GetArchestrAInstallPath(): Failed to Read the Registry ArchestrA install path Key."
    There is no workaround required. The error message does not impact the node upgrades.
    L00110185: Remote Platforms are unable to be deployed if the Galaxy Repository and remote nodes have same domain user, but one is specified by the fully-qualified domain name (mydomain.xxx.mycompany.com) and the other by just the domain name (mydomain). The following error message is shown: "Error: Failed to deploy WinPlatform_002 : Remote Node's UserId/Password don't match GR Node's."

    To work around this issue, make sure that the user\domain\password match identically for the nodes. Either both nodes need to use the fully-qualified domain name or both nodes do not.

    L00112178: Objects built using ArchestrA Object Licensing Toolkit (AOLT) version 1.0 are not compatible with Wonderware Application Server version 3.5 (2012) and higher versions. You must rebuild the objects with AOLT version 1.1 licensing.
    L00112189: Installing Wonderware Application Server on a computer used as a domain controller is not supported.
    L00113652: If you import objects that have dependencies in scripting to custom DLLs and if these custom DLLs are not present in the Galaxy, these objects being imported are placed in an error condition.

    As a workaround, you can import the custom DLLs used by scripts and validate the objects being imported to resolve this issue.
    L00113709: Objects created in Wonderware Intelligence 1.1 are not compatible with Wonderware Application Server 3.5.
    L00115036: If the identity of a ShowGraphic script is already in use, the graphic opened with that same identity will be replaced. During the replacement process, the OnHide script of that graphic will not be executed.

    As a workaround, use a HideGraphic script or a HideSelf script first to hide the open graphic. Then use a ShowGraphic script to open a new graphic.
    L00115135: In the OPCClient object, the installed DAServers are not listed under the Server Name. For the OPCClient object, the following error message is shown in the SMC log:

    .Net Editor Info - 17:35:14.3125809
    Failed to create instance of OPCEnum on server node COMPST01: 0x80040153

    As a workaround, if you invert the installation sequence by installing the OPC Server first and then the Bootstrap, the OPCEnum is installed without anonymous logon and a remote connection to the OPC Server is possible. You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission.
    L00115589, L00115710, L00116055: Any deployed InTouchViewApp instance that is configured to include all Galaxy graphics is incorrectly marked as pending a change if you:

    • Undeploy an object instance with an inherited graphic.
    • Perform an IDE operation after deploying of an object instance with an inherited graphic. Examples of IDE operations are renaming an instance, editing an instance and then closing without saving, adding a user-defined attribute, and so on. This can done on any object with or without graphics.
    • Import a new client control into the Galaxy.
    • Delete an unused client control (not referenced by any graphic) from the Galaxy.

    L00115681: If you configure an InTouchViewApp object and select the Include all galaxy graphics with this application check box, when you export the object to another Galaxy, the new InTouchViewApp object will not have this option selected. You must manually select the option again.
    L00115869: If a field attribute is configured as buffered and has an input extension to a non-buffered user-defined attribute, the field attribute returns bad quality even though the value updates. In order to get good quality, configure the input extension to a buffered user-defined attribute.
    L00116266: The database transaction log can significantly increase in size after migration of .cab files. As a workaround, use the Galaxy Database Scrubber utility to improve the operating performance of your Galaxy database. Also, you can increase the hard drive size. Follow the guidelines provided under Minimum Hardware Requirements in this Readme.
    L00116279: If there are bad visual element references in an object, warnings occur in the Logger when the object is deployed. To get the name of the object using the visual element ID from the log message, run the following SQL query against the Galaxy Repository database:

    select pri.tag_name ObjectName, pri.primitive_name SymbolName, pri.visual_element_id
    from visual_element_reference ver
    inner join internal_visual_element_description_view pri
    on pri.gobject_id = ver.gobject_id and
    pri.package_id = ver.package_id and
    pri.mx_primitive_id = ver.mx_primitive_id
    where ver.checked_in_unbound_visual_element_name is null
    and ver.visual_element_bind_status = 0
    and pri.visual_element_id = <visual element id>
    L00116317: SR 20114029: If you rename an ActiveFactory control that is used in an ArchestrA symbol before you export the object containing the symbol, and you then import the object into a Galaxy that contains a newer version of the same control, the import of the older control is skipped. By design, if a newer version of a client control already exists in the Galaxy, then the import of an older version of the client control is skipped. However, the control reference in the symbol retains the name change. Because the target Galaxy does not contain a control by this name, the object goes into warning and the "symbol not found" text is shown.

    To avoid this, do either of the following:

    • Make sure that the name of the control matches the version in the target Galaxy before you perform the export.
    • Rename the control in the target Galaxy to match the one in the export file. Make sure that the reference in the symbol is updated after you rename the control.
    L00116381: After opening a ShowGraphic() modal symbol from a container script that takes an expression as input, such as a data change script, all data subscriptions are blocked in the base symbol. As a workaround, open the ShowGraphic() symbol from an action script.
    L00116422: Opening a pop-up symbol from a ShowGraphic() script is different from opening the same symbol from Show Symbol animation, and Window Viewer occasionally hangs on script execution. Although you can use the ShowGraphic() script functions inside container scripts, you cannot use ShowGraphic() in WhileTrue or periodic scripts such as WhileShowing.
    L00116459: A remote node fails to connect to an WWALMDB database that is created using SQL Express Edition.

    Workaround: Change the SQL Server Express authentication from Windows mode to Mixed mode.

    To change SQL Server Express Authentication mode
    1. Download and install the x86 version of SQL Server 2008 Management Studio Express from http://www.microsoft.com/download/en/details.aspx?id=7593.
    2. After installation, right-click SqlExpress Connection, click Properties, and then click Security.
    3. Change the SQL Server Express authentication from Windows mode to Mixed mode and click OK.
    4. Restart the database instance or computer.
    L00116508: Writing to a secured array attribute using the SignedWrite() function can result in a .NET error in WindowViewer. Writing to an array is not supported. Instead, you can write to an array element.
    L00116555: If two pop-up windows open in InTouch WindowViewer, one from a ShowGraphic script and another from a ShowSymbol animation, then you cannot close the pop-up windows.

    Workaround: In the modeless ShowSymbol dialog box, click the Push button with the ShowSymbol animation. This Push button that is already selected changes, and you can interact with ShowSymbol dialog box.
    L00116641: If you attempt to acknowledge an alarm from an Alarm Control list with a Smart Card reader installed, but open the certificate list in the Ack Alarms dialog and remove the smart card, then click the empty certificate list, the system will display an error and fail to acknowledge the alarm.
    L00116828: If you attempt to modify the value of a UDA configured with Secured Write or Verified Write security classification using the MxAccess sample ActiveX control in InTouch, the value will not change as expected. As a workaround, the write to a Secured Write UDA value will succeed after you log on to InTouch with operator credentials. However, this workaround does not affect the issue of being unable to modify the Verified Write UDA value.
    L00122304: In an intermittent issue, if you repeat the UndoCheckout operation several times in a row, you can observe performance degradation. Performance degradation has been seen only after the third or fourth repeated UndoCheckout operation.
    L00122313: Importing an aaPKG file using the "Skip: Do not import" option can exhibit inconsisent behavior. In one scenario, importing an aaPKG file that contains instances created from a system template to a Galaxy containing an earlier version of the system template with no instances, using the option "Objects with same Tagname and Codebase - Skip: Do not import" did not import the newer system template instances. In another scenario, importing the aaPKG file to a Galaxy that contains a newer version of the system template than that being imported, with no instances, using the option "Objects with same Tagname and Codebase - Skip: Do not import", imported the aaPKG system template instances.
    L00122358: Because unregistered attributes are not cleared from the Application Server StoreForward cache, an unregistered attribute on the AppEngine can be registered again to the Historian after the Historian run-time database is rebuilt.

    < top of document >

    © 2012-2014 Invensys Systems, Inc. All Rights Reserved.