Wonderware Application Server Readme. Wonderware Application Server 2. Patch 0. 1 Readme. Last revision: 3/1. About This Readme. This document includes information about Wonderware® Application Server 2.
Wonderware Application Server 2012 (version 3.5). It updates the previous Readme files included with. SuiteLink can work in place of DDE under certain.
Patch 0. 1. It updates the previous Readme file included with Application Server 2. The Patch 0. 1 Readme updates the previous Read.
024948 - Suspended Suitelink Updates. 021768 - Installed ABTCP on new node and it does not communicate. 023442 - Information on ZumBach drivers from Wonderware. Wonderware Software Solutions for Real-Time Success. Wonderware is the global leader in Human Machine Interface (HMI), SCADA and real-time operations management software. Wonderware Application Server 2012 R2 (version 3.6). Wonderware Application Server 2012 R2. DDE/SuiteLink DI needed to implement a Time Sequence validation. [Text] Upgraded to InTouch 2012 R2 SLOOOOOW LIVE PLC Questions And Answers.
Me file included with Wonderware System Platform 2. The entire Wonderware Application Server 2. Readme is included in this document, following the Patch 0. About this Patch Release. The Wonderware System Platform 2. Patch 0. 1 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 2. Patch 0. 1 Readme", available for download with the Patch Manager. Important! Installation - Application Server 2.
Wonderware Application Server 3.1. It updates the previous Readme files included with. You still can run certain functions by using SuiteLink in place of DDE.
Installing Application Server on a computer used as a domain controller is not supported. Coexistence - If Wonderware Application Server and the In. Touch HMI are installed on the same node, they both must be upgraded to Application Server 2. Patch 0. 1 and In. Touch HMI 2. 01. 4 Patch 0. Wonderware Application Server 2.
Patch 0. 1 Information. Applying Patch 0. Wonderware Application Server Version 2. Resolved Issues - Wonderware Application Server 2.
Patch 0. 1Wonderware Application Server 2. Information. Wonderware Application Server 2. Readme. Known Issues - Wonderware Application Server 2.
Resolved Issues - Wonderware Application Server 2. Applying Wonderware Application Server 2.
Patch 0. 1Close any anti- virus programs running on the computer before you update Wonderware Application Server with Patch 0. Apply this patch only to Application Server 2. 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 Application Server and In. Touch are installed, you must install Application Server 2.
Patch 0. 1 and In. Touch 2. 01. 4 Patch 0.
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 Archestr.
A 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 Archestr. A IDE connects remotely to the Galaxy Repository on another computer, apply Patch 0. A remote connection between the Archestr. A IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server.
An Archestr. A IDE node still at version 4. GR node updated with Patch 0. An Archestr. A IDE node updated with Patch 0.
GR node still at version 4. 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 Archestr.
A IDE, In. Touch Window. Maker, and In. Touch Window. Viewer, if installed and running. IMPORTANT: When you reboot a platform, you must set each engine On. Scan. Failing to set engines On.
Scan can result in reference resolution issues. Prior to applying Patch 0. GR node, ensure any active remote IDE sessions are disconnected. Patch 0. 1 requires Archestr. A- related processes be shut down and may require a reboot.< top of document > Resolved Issues - Wonderware Application Server 2.
Patch 0. 1 Wonderware Application Server 2. Patch 0. 1 resolves the following issues listed by their Change Request number. L0. 01. 19. 58. 7: SR 1.
The ROC alarm did not properly evaluate if the evaluation interval ("Evaluate Every n ms") was set to 5 minutes or more. L0. 01. 23. 70. 6: RDI group alarm counts (Item.
Error. Cnt. Alarm and Item. Error. Cnt) included initializing state attributes, thereby erroneously raising a high number of alarms.
L0. 01. 24. 30. 8: SR 2. After deploying a number of DI Objects, a host process accumulated memory and did not release, resulting in system errors and a system hang. L0. 01. 24. 92. 2: SR 4.
The "Click", "Double. Click", "Mouse. Click", and "Mouse. Double. Click" events were not working in the SQLData. Grid user control. L0. 01. 25. 46. 5: SR 1. When the RDI was connected to the backup source and the Backup DI source was changed to " " (empty), the RDI object would correctly fail over and reconnect, but it would not update I/O attributes through the backup source.
L0. 01. 26. 27. 6: SR 3. Descriptions for scan group item error count alarms could not be defined for multiple scan groups. The scangroup. Item. Error. Cnt. Alarm.
Desc. Attr. Name attribute could not be extended to a local string attribute. L0. 01. 27. 37. 2: SR 1. Reads and writes from a third- party OPC client via FSGateway to a User Defined Attribute (UDA) could not be done when using Chinese characters. L0. 01. 27. 63. 9: SR 4. The Checkpoint file could not synchronize after the backup engine was restarted.
L0. 01. 27. 85. 2: SR 3. Using the Write. 2() method to poke values and timestamps returned errors even with the Supervisory option enabled using Write. Supervisory(). L0. When Scan. Mode was set to Active. All in OPCClient objects, if instances had bad items that did not exist in the PLC, the RDI appeared to take the engine down. The CPU increased for the engine, the time idle average decreased to zero, and the engine stopped responding.
If the RDI was redeployed, the engine returned to normal, then degraded again over time. L0. 01. 28. 54. 6: SR 1. Pokes to Application Object attributes failed when OSGroup- based security was configured and integrated with FSGateway.
L0. 01. 28. 57. 5: SR 4. Loading a galaxy from a . L0. 01. 28. 61. 6: SR 4.
I/O attributes used in scripts were not properly subscribed if only the backup App. Engine was deployed. When the attribute was used for calculation only by scripts, with only the backup App. Engine deployed and Advanced Communication Management enabled, the I/O extended attribute data was not refreshed. L0. 01. 28. 79. 9: SR 1. Operator events were being logged as successful (Write success) before the write was actually verified. This allowed writes with bad quality or other errors to be logged as successful even if they were not.
L0. 01. 29. 01. 7: HF CR L0. SR 1. 03. 12. 97. The "Enable state label" for a Discrete Field Attribute did not work for OPR events. L0. 01. 29. 06. 8: After a platform restart, old alarms reappeared in the alarm database, but with a different status. L0. 01. 29. 08. 9: HF CR L0.
SR 3. 71. 12. 88. SR 1. 03. 12. 89. When a remote data source node time synched, 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 Outof. Sync. Timestamps", which is disabled by default.
The "timestamp out of sequence" warning will not appear in the logger unless the custom log flag is enabled. L0. 01. 29. 11. 6: SR 1.
Two systems were successfully time synched after drifting out of synch, but an excessive number of messages were reported to the OPC client. These messages were benign, but had the potential to fill the log. L0. 01. 29. 46. 7: HF CR L0.
SR 4. 47. 10. 18. FS Gateway did not propagate the correct timestamp data from the OPC server. There was a 1 or 2 millisecond difference between the alarm time displayed by the OPC server and client, and the timestamp in the history in the alarm database. L0. 01. 29. 49. 6: HF CR L0. SR 1. 03. 13. 00.
Object Viewer showed incorrect Boolean array values from a BACnet OPC server, but the individual array elements showed correct values. L0. 01. 29. 69. 2: HF CR L0. SR 1. 03. 13. 00. The SQLData object retrieved SQL data very slowly when two UDAs (assigned to the database item) retrieved data from the SQL database. L0. 01. 29. 83. 3: SR 4. The RDI object was in disconnected state while both source DI objects were partially connected.
L0. 01. 29. 92. 2: SR 4. An In. Touch 1. 0.
SP3 Patch 0. 1 script timeout resulted in a run- time error when the system attempted to log a debug call. L0. 01. 30. 44. 8: SR 1. After installing Wonderware System Platform 2. R2 Patch 0. 1, creating a new Galaxy of "Base_In. Touch" created a Galaxy with unnecessary objects. App. Engine. The Galaxy Patcher also added unnecessary objects to the "Base_In. Touch" galaxy. < top of document > Wonderware Application Server 2.
Readme. Last revision: 1. About This Readme. This Readme provides information about important resolved and known issues for Wonderware®. Application Server 2. 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. Downloads. Resolved Issues. Known Issues. Known Documentation Issues. Resolved Issues. This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues. L0. 00. 76. 55. 7: Opening and closing a view window when "Advanced Communication Management" is. Galaxy may change the timestamp on an attribute, even though nothing has changed on the.
L0. 00. 88. 22. 7: Hot Fix CR L0. SR 3. 75. 10. 09.
The SQLData. Grid. User. Ctrl On. Click event was not functioning. L0. 00. 92. 39. 7: SR 3. Hot Fix 1. 41. 3.
Redundant engines with many objects caused numerous "Objectsynchmgr Access denied" messages. L0. 00. 94. 26. 7: SR 3. Set. Value could not resolve primitive attributes that contained a dot "." in the External Name. L0. 00. 99. 64. 1: SR 1. Changing the unit of measurement for a UDA did not propagate to the Historian Server.