Wonderware Application Server 3

Wonderware Application Server 3.1 SP3 ReadMe https://wdnresource.wonderware.com/support/patchfixes/1/AppSv31S...
Wonderware Application Server 3.1 SP3 Readme

Last revision: 11/15/2010
This document adds information about Wonderware® Application Server 3.1 Service Pack 3 (SP3) to the
previous Readme files included with Wonderware Application Server 3.1 SP2 (Patch 01), Wonderware
Application Server 3.1 SP1 and Wonderware Application Server 3.1.
Wonderware Application Server 3.1 SP3 Information
About Wonderware Application Server 3.1 Service Pack 3 (SP3)
Antivirus Software Exclusions
Minimum Hardware Requirements
Software Requirements and Compatibility
Installing Wonderware Application Server 3.1 SP3
Upgrading to Version 3.1 SP3 from an Earlier Version of Application Server
Resolved Issues 4 Wonderware Application Server 3.1 SP3
Known Issues 4 Wonderware Application Server 3.1 SP3
Wonderware Application Server Documentation Issues
Wonderware Application Server Documentation
Important!
1. Before installing Wonderware Application Server 3.1 SP3, ensure that you create known good
backups of all Galaxies.
2. Installing Wonderware Application Server 3.1 SP3 automatically undeploys any platform that is
currently deployed in the node that is being updated.
3. Once the GR node is upgraded from any prior version to version 3.1 SP3, all run'time nodes
hosting InTouch applications must be upgraded both to Wonderware Application Server 3.1 SP3
and to InTouch 10.1 SP3 (if you are running InTouch applications). You will not be able to deploy
or undeploy objects on non'upgraded nodes.
4. If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply
Wonderware Application Server 3.1 SP3 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.
5. All the restrictions applicable to Windows Vista and Windows Server 2008 are also applicable to
Windows 7 and Windows Server 2008 R2, respectively. For more information, see Using
Application Server with Windows Server 2008 and Using Application Server with Windows Vista.
6. If you are using SQL Server 2008 SP1, you must be sure to select the x86 option during the SQL
Server installation. This will install SQL Server in 32'bit mode, which is the only mode supported.
7. SQL Server 2008 SP1 does not deliver the BUILTIN\Administrators role by default. Application
Server has been modified such that it does not depend on this role. During the product installation,
you must provide the proper SQL authentication to allow the installer to configure SQL Server for
proper access by the Application Server interfaces. A "SQLAdmin" utility also has been provided
to allow the SQL Server configuration if necessary after the install.
8. If InTouch 10.x and Wonderware Application Server 3.x are installed on the same node, they both
must be upgraded to Wonderware Application Server 3.1 SP3 and InTouch 10.1 SP3.
9. Disable UAC before installing the Wonderware Application Server 3.1 SP3 and InTouch 10.1 SP3,
1 of 72 11/04/2011 08:56 AM
applicable for Windows Vista and above operating systems. For more information about UAC
support, see Support for Windows Operating System User Account Control (UAC)
10. If your version of Wonderware Application Server is 3.0 or earlier, you must upgrade it to
Wonderware Application Server 3.1 SP3 before upgrading to InTouch 10.1 SP3.
11. You cannot restore a Galaxy .cab file backed up in SQL Server 2008 to a node with SQL Server
2005. SQL Server 2008 database backups are not backward compatible with SQL Server 2005.
Attempting this restore initializes, then the progress dialog quickly displays 100% completion of
restoring the database, but the Galaxy .cab restore operation does not complete. If you then start
the IDE, the Galaxy will be blank.
12. The antivirus software exclusions list has been updated. Click this Antivirus Software Inclusions
link for details.
13. Windows Server 2008 R2 no longer supports the /console switch as a means of setting the remote
desktop client (RDC), also known as a console session. Click this Terminal Services Behavior link
for further information about terminal services behavior changes.
14. Using multiple NICs in Windows Server 2008 R2, as with Windows Vista, requires specific
configuration. Click this Using multiple NICs in Windows 2008 for further information about using
multiple NICs in Windows Server 2008 R2.
< top of document >
About Wonderware Application Server 3.1 SP3

Wonderware Application Server 3.1 SP3 adds support for the following Microsoft operating systems:
Windows 7 Professional, 32/644bit (emulation mode) versions

Windows Server 2008 R2 Standard, 644bit (emulation mode) version
< top of document >

The following list shows the minimum computer hardware requirements to host Wonderware Application Server
version 3.1 SP3 components on both 324bit and 644bit systems.
Galaxy Repository (GR) Node

Computer with 2 GigaHertz (GHz) or faster processor, 32/644bit. A multi4core processor is strongly
recommended. The Intel Itanium 2 processor is not supported.
Minimum of 2 GigaBytes (GB) RAM. 4 GB RAM is recommended.
At least 30 GB of available disk space for a 324bit operating system, 40 GB for a 644bit operating system.
Super VGA (1024 x 768) or higher resolution video adapter and monitor.
Network interface card.
CD4ROM or DVD drive for installation.
Keyboard.
Mouse or a compatible pointing device.
Development and Application Nodes

The following are hardware requirements for development and application nodes, with and without InTouch
applications:
Computer with 2 GigaHertz (GHz) or faster processor, 32/644bit. A multi4core processor is strongly
2 of 72 11/04/2011 08:56 AM
recommended. The Intel Itanium 2 processor is not supported.

Minimum 1 GigaByte (GB) RAM. 4 GB RAM is strongly recommended.
At least 30 GB of available disk space for a 324bit operating system, 40 GB for a 644bit operating system.
Keyboard.
Mouse or compatible pointing device.
< top of document >

This section describes the operating system, database, and other software requirements to install Application
Server version 3.1 SP3, along with product compatibility.
Operating Systems
Product Compatibility
SQL Server Database Requirements
Other Software Requirements
Operating Systems
For server components: Windows Server 2008 R2 is the recommended operating system for computers
running server components.
For client components: Windows 7, 324bit or 644bit, is the recommended operating system for
computers running client components.
The following table lists the supported operating systems that can be installed on computers running as
Application Server development, application, and GR nodes. Development and application nodes are
considered to be clients of the server GR node.
Wonderware Application Server Components

ArchestrA Run
ArchestrA IDE Galaxy
Time
(Development Repository
(Application
Node) (GR Node)
Operating Systems Node)
Windows Server 2008 R2, Standard • • •
Windows 7, Professional, 324bit • • •
Windows 7, Professional, 644bit • • •
Windows Server 2008 SP2, Standard, 324bit • • •
Windows Server 2008 SP2, Enterprise, 324bit • • •
Windows Server 2008 SP2, Standard, 644bit
• • •
(emulation)
Windows Server 2008 SP2, Enterprise, 644bit
• • •
(emulation)
Windows Vista SP2, Business, 324bit
• • •
(See Vista Restrictions)
Windows Vista SP2, Enterprise, 324bit
• • •
3 of 72 11/04/2011 08:56 AM
Windows Vista SP2, Business, 644bit (emulation)

• • •
(emulation) • • •
Windows Vista Business
• • •
Windows Vista Business SP1
• • •
Windows Vista Enterprise
• • •
Windows Vista Enterprise SP1
• • •
Windows Vista Ultimate
• • •
Windows Vista Ultimate SP1
• • •
Windows Server 2003 Standard Edition SP2 • • •
Windows Server 2003 Enterprise Edition SP2 • • •
Windows Server 2003 Standard Edition R2 SP2 • • •
Windows Server 2003 Enterprise Edition R2 SP2 • • •
Windows XP Professional SP3 • • See Note 2
Windows XP Tablet •
Operating System Notes:
1. The Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced
Server operating systems are not supported for Application Server version 3.1 SP1, SP2 or
SP3. An error occurs if you attempt to install or upgrade Application Server version 3.1 SP1,
SP2 or SP3 on a computer running any edition of the Windows 2000 operating system.
2. The Galaxy Repository node can run on a supported Windows client operating system (such
as Windows XP Professional SP3) in a single node configuration of Application Server. A
supported Windows Server operating system (such as Windows Server 2003 SP2) is
recommended for the Galaxy Repository node.
3. The Bootstrap, IDE, and Galaxy Repository are supported by the following language
versions of Microsoft operating systems: English, Japanese, Chinese, German, and French.
The Galaxy Repository is also supported by the English, Japanese, Chinese, German, and
French versions of Microsoft SQL Server 2005 SP3 and SQL Server 2008 SP1.
Support for Windows Operating System User Account Control (UAC)
Application Server versions 3.1, 3.1 SP1, 3.1 SP2, 3.1 SP2 Patch 01, and 3.1 SP3 support
UAC4enabled run4time operations without elevated privileges.
For all configuration and installation operations, including those called during run4time operations,
UAC must be disabled or privileges must be elevated to the required level.
DDE Support
In Windows Vista, Windows 2008 and later operating systems, DDE is supported only on a local
node. Windows Server 2008, as with Windows Vista, does not support NetDDE. ArchestrA
4 of 72 11/04/2011 08:56 AM
Symbols use the client layer when accessing InTouch tags and appear as a third4party client trying
to access WindowViewer as a data server, therefore the use of NetDDE for communication is not
supported and not recommended.
In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag

on a local node.
Wonderware Application Server 3.1 SP3 is compatible and can co4exist with the following products:
Wonderware® InTouch® HMI 10.1 SP3

Wonderware Historian Client 10.0 SP1
Wonderware InTouch CE 10.1
Wonderware Historian Server 10.0 SP1
Wonderware Manufacturing Execution System 4.0
Wonderware Information Server 4.0
Wonderware InControl™ 7.11 SP2 P01
Wonderware Manufacturing Execution Module 1.0
Wonderware InBatch™ 9.0
Wonderware QI Analyst™ 8.0 SP1 P01
Wonderware SCADAlarm™ 6.0 SP2 P01
In some cases, Wonderware Application Server 3.1 SP3 is supported in newer environments than a compatible
product. Wonderware Application Server 3.1 SP3 has been tested for compatibility with listed products only in
the environments that are supported by that particular product.
SQL Server Requirements

Microsoft SQL Server 2005 with SP3 and SQL Server 2008 SP1 are the databases supported by Wonderware
Application Server version 3.1 SP3. You must use the Standard or Enterprise editions of SQL Server 2005 SP3
or SQL Server 2008 SP1. Neither the Compact, Express, nor the Workgroup editions of SQL Servers can be
used as the Galaxy Repository. See the following section and SQL Server Rights Requirements, for more
information.
SQL Server 2005 SP2/SP3 or SQL Server 2008 SP1 must be installed on the computer designated as the
ArchestrA Galaxy Repository node prior to installing Application Server.
You also cannot install and use Application Server on a computer that has both Microsoft SQL Server
2000 and Microsoft SQL Server 2005 or 2008 installed.
The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the computer's physical
memory.
TCP/IP must be enabled on the computer hosting a SQL Server 2005 or 2008 database. The TCP/IP
protocol setting can be verified from the SQL Server Network Configuration under SQL Server
Configuration Manager.
SQL Server Rights Requirements
SQL Server 2008 does not automatically create the BUILTIN\Administrators role as delivered in SQL Server
2005. Because of this change to SQL Server, the Application Server 3.1 SP3 installation process will create the
necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This
automated process will provide the rights required to allow operations within the Galaxy Repository without the
need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If
you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of
two options to restore it:
5 of 72 11/04/2011 08:56 AM
Run the Change Network Utility from the Windows Start menu.
Run the aaConfig SQL Utility from the Windows Start menu.
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the
aaConfig SQL Utility to restore it. Refer to the Wonderware Application Server User's Guide, About ArchestrA
User Accounts, for further information and procedures about restoring the aaAdministrators group.

The following list describes other third4party software required for Application Server version 3.1 SP3.
Microsoft .NET Framework 3.5 SP1 must be installed prior to installation of SQL Server 2008 SP1 or
Wonderware Application Server 3.1 SP3 using the Microsoft role management tool on Windows 2008 R2
and Windows 7 (32/644bit) operating systems.
Microsoft .NET Framework 3.5 SP1 must be installed on every computer that hosts an Application Server
component. The GR node will require .NET Framework 3.5 SP1 if it is being installed with SQL Server
2008 SP1 as .NET Framework 3.5 SP1 is a SQL Server 2008 SP1 prerequisite. Application Server 3.1 SP3
has been validated with both .NET Framework 3.5 and 3.5 SP1.
Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008 is required only by the MXAccess and
GRAccess toolkits distributed with Application Server.
Using Wonderware Application Server with Windows 7 and Windows

Server 2008 R2
In ArchestrA, when the DDESuiteLinkClient is connected to the local DAServer using DDE, it does not
work with UAC (User Access Control) enabled. The same works when UAC is disabled.
For toolkits such as the ArchestrA Object Toolkit, GRAccess Toolkit, and MXAccess Toolkit to function
properly on Windows Vista and later operating systems, you may need to start the toolkit by right4clicking
on the file and then clicking Run As Administrator.
Wonderware Application Server may experience performance degradation when running on the Windows
7 or Windows 2008 R2 operating systems, depending on how certain operating system tuning parameters
are configured. For more information, see Tech Note #719.
Installing .NET Framework 3.5 SP1 on Windows 2008 R2 and Windows 7 64'bit Operating Systems
Starting with Windows 2008 R2, the method of installing .NET Framework 3.5 SP1 has changed. This change
affects the installation of Application Server 3.1 SP3 on Windows 2008 R2 and Windows 7 644bit operating
systems.
If .NET Framework 3.5 SP1 is not already installed on your system prior to installing Application Server 3.1
SP3, you must install it manually.
If you have already started the Application Server 3.1 SP3 installation, you will need to exit, manually install
.NET 3.5 SP1, then return to the Application Server 3.1 SP3 installation.
For Windows 2008 R2 Operating Systems: To install the .NET Framework 3.5 SP1, you can use the
Microsoft Server Manager interface or the Microsoft Power Shell.
To use the Server Manager
1. Click Start, then highlight Administrative Tools and select Server Manager.
2. In the Server Manager, select Add Features, then expand .NET Framework 3.5.1
Features.
3. In .NET Framework 3.5.1 Features, select the .NET Framework 3.5.1 check box. Click
Next.
4. Click Install to confirm the installation selection. The .NET Framework 3.5.1 installation will
6 of 72 11/04/2011 08:56 AM
proceed.
To use the Windows Power Shell
1. Click Start, highlight All Programs and select Accessories.

2. Expand Windows PowerShell and right click Windows PowerShell and select Run as
administrator. Click Yes on the User Account Control box.
3. At the Power Shell Command Prompt, enter the following two commands and press Enter
after each command:
a. Import'Module ServerManager
b. Add'WindowsFeature as'net'framework
4. Exit Windows Power Shell.
For Windows 7 Operating Systems: To install the .NET Framework 3.5 SP1, use the Programs and Features
interface.
1. Start Control Panel, then select Programs, then select Programs and Features.
2. Click Turn Windows Features On or Off.
3. Select the Microsoft .Net Framework 3.5.1 check box, then click OK.
4. Restart your computer.
< Top of document >
Installing Wonderware Application Server

The Wonderware Application Server Installation Help (Install4AppServer.chm) located in the root folder of the
installation CD includes detailed installation and upgrade instructions. Make sure the target computers that you
want to install Application Server version 3.1 SP3 components on meet third4party software requirements. You
must install Wonderware Historian 9.0 Patch 02 or higher to use time propagation and late data from the
Wonderware Application Server to the Historian.
< Top of document >
Upgrading to Version 3.1 SP3 from an Earlier

Version of Application Server
After the hardware and software requirements are met, including the proper operating system, SQL server and
other pre4requisites, you can upgrade to Application Server version 3.1 SP3 from the following versions of
Application Server:
Version 2.1 Patch 02

Version 3.0, including all patches and service packs
Wonderware Application Server 3.1 SP3 Upgrade Requirements

The following requirements apply when upgrading existing Application Server components to version 3.1 SP3:
1. Upgraded IDE/Client nodes cannot connect to a non4upgraded Galaxy Repository (GR) and vice4versa.
2. The GR Node will be undeployed before upgrading to Application Server 3.1 SP3.
Migrating Applications to Wonderware Application Server Version 3.1
7 of 72 11/04/2011 08:56 AM
SP3
You can migrate applications from the following earlier versions of Application Server to version 3.1 SP3:

GR Node Migration
For versions earlier than 3.1, as listed in the preceding topic, the existing database schema is migrated to the
new version 3.1 SP3 schema. Configured Wonderware Historian nodes are saved in the new schema. The GR
node migration fails if the GR node is used as a run4time node for another GR.
< Top of document >
Resolved Issues ' Wonderware Application Server

Version 3.1 SP3
L00108980: Propagation of the Security Classification from Template to its immediate child Instance now
requires the attribute to be locked for User Defined Attributes (UDAs) and Field Attributes
(FAs). This behavior is different from the prior Wonderware Application Server release 3.1
SP2 P01.
L00084123: HF CR L00084123 (Hotfix 1070) SR 23516503: During deployment of the batch inventory
object, exceptions are generated from the component "script runtime". The issue was fixed in
10.0 SP2 under CR L00084362.
L00093708: HF CR L00092445 (Hotfix 1417) SR 20113107: Unassigning the InputSource with "444"
does not remove the item and causes attribute count to go up.
L00099172: A Windows DEP error message is shown when the SMC logger is kept open during an
upgrade of Application Server.
L00099731: The OSConfiguration utility fails to install on the Windows 7 operating system.
L00100041: HF CR L00099486 (Hotfix 1727) SR 33931901: If special characters in non4English
languages are used for the attribute name, the following configuration error message is
shown: "Invalid Reference for Unknown Reasons".
L00100919: If the value written to the SelectedIndex property of an ArchestrA Symbol list box is greater
than the number of elements in the list box, then an error is logged to the Logger instead of a
warning.
L00101103: HF CR L00101103 (Hotfix 1768) SR 19417289: In the Sequencer object, when the quality
value is not 192, the trigger will not work, even if the quality of the attribute is good and the
condition is true for the trigger. The issue has been resolved by checking all possible good
quality values other than 192.
L00101513: HF CR L00099258 and L00100590 (Hotfixes 1785 and 1717) SR 22316396: If the OPC
client uses the DISCONNECT/RECONNECT/WRITE tag, FSGateway stops responding and
the Bootstrap becomes unstable.
L00101688: HF CR L00101389 (Hotfix 1762) SR 10415503: A memory leak is occurring in the
TrendClient control.
8 of 72 11/04/2011 08:56 AM
L00101700: Imported AutomationObject instances (aaPkg) that have modified attributes (for example, a
UDA) and security classification (for example, a secure\verified write) are reset to 'Operate'
(the default).
L00101828: HF CR L0092808 (Hotfix 1445) SR103115713: Objects fail to deploy\undeploy under the
engine. An engine communication error and time out error are shown.
L00101902: The Galaxy Repository Load (GRLoad) operation is slower on the Windows 2008 R2
operating system than on the Windows 2008 operating system because of how operating
system tuning parameters are configured. See Tech Note 719, which is available from the
Wonderware Technical Support website.
L00101905: Import performance is slower on the Windows 2008 R2 operating system than on the
Windows 2008 operating system. See Tech Note 719, which is available from the
Wonderware Technical Support website.
L00102403: HF CR L00103184 (Hotfix 1682) SRs 37111208, 23518566, and 22316340: When
redeploying a RedundantDIObject whose backup source contains an invalid PLC address
subscribing to 5,000 items, an "Access Denied" error message is shown.
L00102636: HF CR L00101906 (Hotfix 1856) SR 19417358: New domain users cannot log on to the
Galaxy from a managed InTouch application. To log on from the InTouch application, the
new users should log on first from the IDE.
L00102831: HF CR L00101243 (Hotfix 1832) SR 30712173: Security classifications do not propagate
as expected. Field attributes created on an instance and configured as "Free Access" are
reset to operate when a change in the template is propagated.
L00102945: HF CR L00101721 (Hotfix 1864) SR 31711358: When you try to restore the Galaxy .cab,
an error message from the GalaxyRepController occurs stating that the specified path, file
name, or both, are too long.
L00103456: HF CR L00103456 (Hotfix 1848) SR 33410661: Importing/exporting templates causes a
loss of certain extension settings.
L00103836: HF CR L00103836 (Hotfix 1889) SR 19417373: If the "WinPlatformGroup" ArchestrA
Symbol is fragmented, then most fragments disappear from the InTouch window if it is bound
to Windows XP Professional SP3.
L00103840: HF CR L00103388 (Hotfix 1898) SR 33430625: When two windows with client controls
are displayed and they overlap each other, navigating from the window in focus to the
footprint of the window below automatically brings the window below on top.
L00103901: HF CR L00102228 (Hotfix 1867) SR 10415777: KeyUp and KeyDown events of the
AlarmClient control do not get triggered on the run4time client.
L00103902: HF CR L00101284 (Hotfix 1823) SR 38910199: Using OS security users with special
characters in the operating system profile corrupts the Galaxy security database.
L00103903: HF CR L00101169 (Hotfix 1811) SR 19417288: When a local (admin) user logs on to the
operating system, the domain user is unable to change the password using the
ChangePassword() function in the InTouch software, even after successfully logging in to the
InTouch software.
L00103935: HF CR L00103386 (Hotfix 1897) SR 12610862: A false alarm is generated when the Field
Attribute in UserDefined object is set to 'False' in the Active Alarm State.
L00104139: If a new Galaxy is created based on a .cab backup that has object licensing information in it,
then the licensing information becomes part of the new Galaxy.
L00104870: During Galaxy database migration, the following error message, logged in the ArchestrA.
Visualization.GraphicLibrary, appears: "Visual element reference list incomplete or
corrupted".
9 of 72 11/04/2011 08:56 AM
L00104984: HF CR L00104306 (Hotfix 1959) SR 31711437 and SR 19816541: After objects are
grouped, the show symbol animation shows a "graphic not found" error at run time.
L00105112: HF CR L00094255 (Hotfix 1614) SR 15616501: Application engines have memory leaks of
private bytes.
L00105114: HF CR L00102035 (Hotfix 1838) SR 31711293: If a redundant engine with 300 objects is
cascade deployed, the task stops responding and the engine fails over. The backup engine
fails and tries to fall back to the primary engine. The multi4threading brought by the
asynchronous scripts leads to overwriting the previous state of static MxValues.
L00105190: HF CR L00101378 (Hotfix 1833) SR 20610952: A date change event occurs due to the
comparison of a field attribute's value with another field attribute input source.
L00105214: HF CR L00096582 (Hotfix 1612) SR 31711209 and 31711201: If an InTouch application is
deployed on remote Terminal Server computer that has several clients are connected to it,
and changes to the InTouch application are deployed, the Logger has a message that
application is deployed, but the synchronization never initiates and the files do not get copied
to the remote computer.
L00105216: HF CR L00096970 (Hotfix 1624) SR 20113235: Setting the InputSource to "444" does not
remove the item from subscription in the DIObject.
L00105219: HF CR L00097169 (Hotfix 1646) SR 20610941: A UDA value sometimes does not show in
the symbol animation.
L00105285: HF CR L00104843 (Hotfix 1997) SR 17132632: Differing number of alarms and missing
alarm comments come from the same Galaxy.
L00105340: HF CR L00084123 (Hotfix 1445) SR 103115713: Objects fail to deploy\undeploy under the
engine. Engine communication error and time out error appear.
L00105392: HF CR L00104611 (Hotfix 1985) SR 33932079: When the Always load from disk check
box is cleared, the settings in the ArchestrA TrendClient are lost.
L00105464: HF CR L00103998 (Hotfix 1945) SR 33410699: The ArchestrA Web Exporter 1.0 (from
Wonderware Information Server 4.0) fails to successfully export an InTouch Window that
contains elements with an x4coordinate of more than 2000 pixels.
L00106651: HF CR L00106229 (Hotfix 2070) SR 10415949: LMX crash occurs when the engine is
shutting down or failing over. LMX Unknown error, MxConnection warnings, COM Error . .
. SchedulerImpl.cpp.
L00107180: Deployment is unsuccessful and aaPIM errors are observed in the logger after upgrading a
DIObject.
< top of document >
Known Issues ' Wonderware Application Server

Version 3.1 SP3
This section describes all known issues identified in Wonderware Application Server Version 3.1 SP3.
L00104874: Certain IDE operations are much slower on the Windows 7 and Windows 2008 R2 operating
systems than on earlier releases of Microsoft Windows for the following configuration:
10 of 72 11/04/2011 08:56 AM
1. The GR4node is a member of DomainA.

2. The interactive (logged4in) user on the GR is a member of DomainA, but
3. The ArchestrA Network User is an account in DomainB, and
4. 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:
1. Editing objects.
2. Deploying objects.
3. Deleting objects.
Workaround:
1. Ensure the network connection between the GR node and/or the IDE node 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 the ArchestrA
Network user all be members of the same domain.
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: Right4click 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.
L00106046: On Windows 2008 R2 644bit and Windows 7 324bit operating systems, if you attempt to
uninstall 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,
Application Server will continue to uninstall as if you had selected the Ignore option.
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.
L00107322: The Windows Server 2008 R2 (644bit) 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. Note that 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) 742842008
11 of 72 11/04/2011 08:56 AM
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 4 WDDM) Version (7.14.1.31) 941742009
L00107919: When you log on to the ArchestrA System Management Console (SMC) Platform Manager
with a newly4created, Active Directory OS Group account for 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.
< top of document >

Issues
The following table lists all documentation corrections to Application Server 3.1 SP3 documentation.
Item Location of Existing Change

Change Documentation
1 OPCClient Object n/a In the "Overview" section, insert a new subsection
Help (help.htm), "OPC Client Reconnection" (following the existing
"Block Reads and Block Writes" subsection):
"Overview" section
Following is the OPC Client connect/reconnect
behavior:
1. When the OPC Client starts, it will

immediately attempt to connect.
2. If the OPC Client is connected and gets
disconnected it will immediately try to
reconnect, raising the restartCnt by 1. After
RestartPeriod it will again attempt to
reconnect, again raising restartCnt by 1.
When Restart Max is reached, after exactly
RestartMax * RestartPeriod seconds, it will
raise the RestartAlarm and no further restart
attempts will be made.
3. When the OPC Client connects, it will set
RestartCnt to 0 and lower the RestartAlarm.
4. When ResetRestart is set to true, it will set
RestartCnt to 0 and lower the RestartAlarm
and attempt to reconnect immediately. If it is
already connected, setting ResetRestart will
12 of 72 11/04/2011 08:56 AM
not cause a disconnect followed by a

connect.
When a connection fails, OPC Client will try to

connect after each "Restart Period" for "Restart
attempts" times. If the "Restart Period" is 20000
ms, it will try to reconnect after 20 sec instead of at
each scan period. Because this represents a change
from earlier restart connection functionality, you
may need to modify the "Restart Period" for
"Restart attempts" accordingly.
2 Application Server References to References should be changed to Application
Installation Help Application Server Server version 3.1 SP3.
(Install4 version 3.1 SP2 in
AppServer.chm) various locations
within the Help file.
< top of document >

The Application Server product library consists of a set of Portable Document Files (PDF) located in the
UserDocs\English folder of the Application Server installation CD. You need Adobe Reader installed on your
computer to view Application Server documentation. You can download the latest version of Adobe Reader
from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html
After installing Adobe Reader, double4click on a PDF file with your pointing device to view the book with
Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.
Application Server installation instructions are located in the root folder of the Application Server installation
CD as an online help file. You can view these instructions by clicking the Installation Guide button in the
Application Server installation program. Product documentation is also available with Application Server online
help.
Documentation Set
The Application Server documentation set includes the following guides:
Wonderware Application Server User's Guide. Explains configuring and deploying Application Server
applications.
Creating and Managing ArchestrA Graphics User's Guide. Explains how you create and manage graphical
symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
Application Server Scripting Guide. Reference for the scripting language in Application Server.
Object Viewer User's Guide. Explains how to acquire run4time data using the Object Viewer.
Guide to the ArchestrA Alarm Control. Explains how to configure the alarm control (client) to show
current and historical alarms and events in a grid.
Guide to the ArchestrA Trend Client. Explains how to configure a chart to trend real4time data values.
Platform Manager User's Guide. Explains how to start and stop system components.
Galaxy Database Manager User's Guide. Explains how to backup and restore the Galaxy database.
Log Viewer User's Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
13 of 72 11/04/2011 08:56 AM
Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.
Wonderware FactorySuite License Utility Guide. Explains how to use the License Utility to manage the
license required for the running application.
Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used
between components of Wonderware products.
Application Server Installation Guide. Explains information about installing the product.
InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated
Development Environment (IDE) to manage InTouch applications so that you can use symbols you create
in the ArchestrA Symbol Editor. This guide is available on the InTouch HMI installation CD.
Information included in these guides is provided in online Help, which can be opened using the Help menu
options in each utility. During product installation, you can choose to install the documentation PDF on your
local hard drive.
Searching Application Server Books with Adobe Reader

The Application Server books are delivered as an Adobe PDF package, which provides a master index of all
books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to
the Application Server product library.
To search for information across all Application Server books simultaneously
Open Adobe Reader.

Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
Type the word or phrase that you want to search for in the Application Server books.
In the Where would you like to search area, select the option to search all PDF books.
If necessary, locate the Application Server version PDF package located on your Wonderware CD or on a
network folder containing copies of the Application Server PDF book files. After product installation, these files
can be found at: <driveletter>:\Program Files\ArchestrA\Framework\Docs.
Click Search. Adobe Reader lists the Application Server books that contain a match for your search criteria.
Click on the links to open the Application Server book to the topic containing the information that meets your
search criteria.
< Top of document >
Wonderware Application Server 3.1 SP2 Patch 01,

ReadMe
About This Readme

This document adds information about Wonderware® Application Server 3.1 Service Pack 2 (SP2), Patch
01 to the previous Readme files included with Wonderware Application Server 3.1, Application Server
3.1 SP1, and Application Server 3.1 SP2. Review this document for installation instructions and a
description of the issues resolved by Patch 01.
Important!
1. If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be
upgraded to Application Server 3.1 SP2 and InTouch 10.1 SP2, or Application Server 3.1 SP2 Patch
01 and InTouch 10.1 SP2 Patch 01.
2. If your version of Wonderware Application Server is older than version 3.0, you must upgrade it to
14 of 72 11/04/2011 08:56 AM
Application Server 3.1 SP2 before upgrading to InTouch 10.1 SP2. Patches may be applied after the
upgrades.
3. You cannot restore a Galaxy .cab file backed up in SQL Server 2008 to a node with SQL Server
2005. SQL Server 2008 database backups are not backward compatible with SQL Server 2005.
Attempting this restore initializes, then the progress dialog quickly displays 100% completion of
restoring the database, but the Galaxy .cab restore operation does not complete. If you then launch
the IDE, the galaxy will be blank.
4. Prior to installing the patch, please refer to the steps detailed in Installation Instructions.
Clarifications from Previous Application Server 3.1x Readme Files

Support for Windows Operating System User Account Control (UAC)
Application Server versions 3.1, 3.1 SP1, 3.1 SP2 and Patch 01 support UAC'enabled run'time operations
without elevated privileges.
For all configuration and installation operations, including those called during run'time operations, UAC
must be disabled or privileges must be elevated to the required level.
DDE Support
In Windows Vista, Windows 2008 and later operating systems, DDE is supported only on a local node.
Windows Server 2008, as with Windows Vista, does not support NetDDE. ArchestrA Symbols use the
client layer when accessing InTouch tags and appear as a third'party client trying to access
WindowViewer as a data server, therefore the use of NetDDE for communication is not supported and
not recommended.
In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a

local node.
Application Server 3.1 SP2, Patch 01 Information

Before You Install Application Server 3.1 SP2 Patch 01
Installation Instructions ' Application Server 3.1 SP2 Patch 01
Resolved Issues ' Application Server 3.1 SP2 Patch 01
Known Issues ' Application Server 3.1 SP2 Patch 01
Application Server 3.1 SP2 Information
About Application Server 3.1 Service Pack 2 (SP2)
Using Application Server with Windows Server 2008
Using Application Server with Windows Vista
15 of 72 11/04/2011 08:56 AM
Installing Application Server
Migrating Applications to Application Server version 3.1 SP2
Resolved Issues ' Application Server 3.1 SP2
Known Issues ' Application Server 3.1 SP2
Application Server Documentation Issues
Application Server Documentation
< top of document >
Application Server version 3.1 SP1 Information
About Application Server 3.1 Service Pack 1 (SP1)
Software Requirements
Migrating Applications to Application Server version 3.1 SP1
Resolved Issues ' Application Server 3.1 SP1
Known Issues ' Application Server 3.1 SP1
< top of document >
Application Server version 3.1 Information
About This Release
Upgrading to Version 3.1 from an Earlier Version of Application Server
16 of 72 11/04/2011 08:56 AM
Migrating Applications to Application Server version 3.1
Resolved Issues ' Application Server 3.1
Known Issues ' Application Server 3.1
< top of document >
Wonderware Application Server 3.1 SP2, Patch 01, is compatible and can co'exist with the following
products:
Wonderware InTouch HMI 10.1 SP2 P01

ActiveFactory 9.2
InTouch CE 10.1
Wonderware Historian Server 10.0
Performance Software 3.5
InControl 7.11 SP2 PO1
Manufacturing Execution Module 1.0
InBatch 9.0
QI Analyst 8.0 SP1 PO1
SCADAlarm 6.0 SP2 PO1
In some cases, Application Server 3.1 SP2 and 3.1 SP2, Patch 01 are supported in newer environments
than a compatible product. Application Server 3.1 SP2 and 3.1 SP2, Patch 01 have been tested for
compatibility with a listed product only in the environments that are supported by that particular
product.
< top of document >
Before You Install Application Server 3.1 SP2, 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 version 3.1 SP2. You can check the version number in the
Control Panel. See the Add or Remove Programs section under Wonderware Application Server.
< top of document >
Installation Instructions ' Application Server 3.1 SP2, 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 3.1 SP2 Patch 01 and
InTouch 10.1 SP2 Patch 01 in order for them to coexist.
17 of 72 11/04/2011 08:56 AM
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.1 SP2 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.1 SP2.
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.
< top of document >
Resolved Issues ' Application Server 3.1 SP2, Patch 01

Wonderware Application Server 3.1 SP2, Patch 01 resolves the following issues. HotFix (HF) numbers
and Service Request (SR) numbers are referenced where available.
L00094638: HF CR L00093843 (HF 1492) SR 103116033: Different client and server software versions caused issues
the IDE, accessing various client objects, and starting the Editor. This condition occurred, for example, wh
server was updated with a service pack but the client was not. The issue has been resolved by preventing a
server if the client software version is not equal to the server software version.
L00095483: HF CR L00092531 (HF 1409, 1431): Checking in a custom category derived template inconsistently resul
operation failure message when child objects were checked out. The message has been adjusted for consist
resolving the issue.
L00095448, HF CR L00092182, L00096960 (HF 1409): Connection to the Galaxy was lost and Thread error message
L00099664: displayed. A Galaxy access exception handling now prevents the IDE crash.
L00096896: HF CR L00096504 (HF'1610) SR 33811042: Deploying objects in normal groups of four resulted in a ser
followed by a redundancy failure due to a task memory allocation failure to check for a null value. NMX A
been modified to check for a null value and the issue has been resolved.
L00098009: HF CR L00090838 (HF 1439) SR 28610675: Engine terminated abnormally due to a run4time memory wr
Code revision now returns proper result values and the issue is resolved.
L00098397: HF CR L00093549 (HF 1643) SR 103115987: Adding a new UDA in a parent template with a Boolean D
this example, and a default Category value (User Writeable) resulted in changing a child template Field Att
Category from its original value (Calculated) to the parent template UDA default Category value (User Wri
Check in now compares deserialized values against default values, resolving the issue.
L00098884: HF CR L00097416 (HF 1649) SR 39910127: The IDE crashed when selecting a checkbox in in an Arches
which had been generated by ArchestrA Object Toolkit (AOT) version 3.1. The cause in the Application Se
has been located and the issue resolved.
L00099958: HF CR L00090176 (HF 1295, 1348) SR 31610661: Continually accessing the license file resulted in a me
in the POM service. Changing the LMX call to use cached data resolved the issue.
18 of 72 11/04/2011 08:56 AM
L00100257: This CR is a memory leak HotFix roll up, merging the memory leak HotFixes listed below into Application
For ActiveFactory, you must separately apply the relevant HotFixes.
HF CR L00072418 (HF 826) SR 23515477, SR 103113128: ActiveFactory v9.2 aaHistTrendContro

ActiveX Control caused a memory leak in InTouch version 10.
HF CR L00075808 (HF 893) SR 24513257: SQL connections leak in InTouch 10 Patch 01 using
aaHistClientTrend Control.
HF CR L00085816 (HF 826, 1167) SR 23516793: After printing multiple times, an error message "A
generic error occurred in GDI+" appeared and the clipboard would no longer copy.
HF CR L00090396, L00056659 (HF 1317) SR19713447: The time required to add a pen to a Trend
"Live" mode increased with the number of pens already in the trend.
HF CR L00093828 (HF 1490) SR 15616549; HF CR L00072418 (HF 826); HF CR L00075808 (H

893): aaHistClientTrend Ctrl caused memory/GDI Object leak in InTouch 10.x and aaHistClie
Ctrl caused SQL Connection Leaks memory.
HF CR L00095988 (HF 1600) SR 37610472: aaHistClientTrendControl imported as a .dll into a Ga

crashed while creating private groups.
HF CR L00096530 (HF 1616) SR 33931715: TrendClient pen disappeared if data did not change du
the trend period.
HF CR L00097877 (HF 1694) SR 14812088: Using aaHistClientQuery Control and aaHistClientTre

a simple InTouch window caused a GDI leak. The application crashed when it reached the 10.000 lim
HF CR L00097878 (HF 1658) SR 14812088: If you disabled the "Refresh Entire chart every..." opt
the next time you right clicked the property a .Net Runtime error appeared and the application froze
lot of pens were shown in the trend.
< top of document >
Known Issues ' Application Server 3.1 SP2, Patch 01

Wonderware Application Server 3.1 SP2, Patch 01 has the following known issues:
L00102947: On 644bit Windows Vista and 644bit Windows 2008 operating systems, installing Application Server 3.1 SP
continues to completion with the Logger and Object Viewer open. Errors appear in the SMC. However, tha
expected "files in use" Windows dialog does not appear and the installation continues is a Windows behavi
Different operating systems are known to behave differently, and the behavior on these operating systems i
Windows issue and causes no installation side effects.
< top of document>
Wonderware Application Server 3.1 SP2 Readme

About This Readme
19 of 72 11/04/2011 08:56 AM
This document adds information about Wonderware® Application Server 3.1 SP2 (Service Pack 2) to the
previous Readme files included with Wonderware Application Server 3.1 and Application Server 3.1 SP1.
New in Wonderware Application Server 3.1 SP2

The following are included in this release:
1. Application Server Alarm Comment Language Switching support

2. New operating system support
3. New SQL Server version support
4. Using Application Server with Windows Server 2008
5. OnShow symbol script behavior changes
6. Resolved Issues and merged Hot Fixes
Important!
1. Before installing Wonderware Application Server 3.1 SP2:
Ensure that you create good known backups of all Galaxies.
If you are using an InTouch 10.0 application with ArchestrA Symbols, run the ArchestrA
Symbol Analysis and Repair Utility and ensure all issues reported by the utility are
addressed.
2. Installing Wonderware Application Server 3.1 SP2 automatically undeploys any platform that is
currently deployed in the node that is being updated. Changes to the WinPlatform object and other
components require any deployed platforms to be redeployed.
3. If InTouch 10.x and Application Server 3.x are installed on the same node, they both must be
upgraded to Application Server 3.1 SP2 and InTouch 10.1 SP2.
4. Once the GR node is upgraded from any prior version to version 3.1 SP2, all run'time nodes
hosting InTouch applications must be upgraded both to Application Server 3.1 SP2 and to InTouch
10.1 SP2 (if you are running InTouch applications). You will not be able to deploy or undeploy
objects on non'upgraded nodes.
5. If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply
Wonderware Application Server 3.1 SP2 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.
6. If you are using SQL Server 2008, you must be sure to select the x86 option during the SQL Server
installation. This will install SQL Server in 32'bit mode, which is the only mode supported.
7. SQL Server 2008 does not deliver the BUILTIN\Administrators role by default. Application Server
has been modified such that it does not depend on this role. During the product installation, you
must provide the proper SQL authentication to allow the installer to configure SQL Server for
proper access by the Application Server interfaces. A "SQLAdmin" utility also has been provided
to allow the SQL Server configuration if necessary after the install.
8. You must install Wonderware Historian 9.0 Patch 02 or Historian 10.0 to take advantage of new
historian features including time propagation and late data from the Wonderware Application
Server to the Historian. These versions also are required to leverage the new Historian
configuration options from the IDE.
9. The antivirus software exclusions list has been updated. Click this Antivirus Software Exclusions
link for details.
10. Windows Server 2008 no longer supports the /console switch as a means of setting the remote
desktop client (RDC), also known as a console session. Click this Terminal Services link for further
information about terminal services behavior changes.
11. Using multiple NICs in Windows Server 2008, as with Windows Vista, requires specific
configuration. Click this Using multiple NICs in Windows 2008 for further information about using
multiple NICs in Windows Server 2008.
< top of document >
20 of 72 11/04/2011 08:56 AM
About Application Server 3.1 SP2

Wonderware Application Server 3.1 SP2 includes the following enhancements and new features:
Application Server Alarm Comment Language Switching support

The alarm comment language switching feature leverages the multi4language interface developed for
Application Server in version 3.1. You can export alarm messages contained in objects to a file, translate them,
and import them back into the Galaxy for convenient maintenance. Translated alarm comment files must also be
imported by InTouch in order to switch languages at run time.
ArchestrA Alarm Control Column Header Language Switching

support
The ArchestrA Alarm Client control has been enhanced to support localization of its column headers.
Procedures to localize ArchestrA Alarm Client control column headers are the same as those for localizing
ArchestrA symbols.
Support for New Operating Systems

Application Server supports new releases of Microsoft operating systems including:
Windows Vista SP2: Ultimate, Business, and Enterprise editions, 32/644bit (emulation mode) versions
Windows Server 2008 SP2: Business and Enterprise editions, 32/644bit (emulation mode) versions
Support for New Versions of SQL Server

Application Server supports new releases of Microsoft SQL Server including:
SQL Server 2005 SP2 and SP3: Standard and Enterprise 324bit versions
SQL Server 2008 SP1: Standard and Enterprise 324bit versions
Support for New Versions of .NET Framework

Application Server supports .NET Framework 3.5 SP1, which is required by SQL Server 2008.
Application Server Utilities and Toolkits

Two Application Server utilities, the Database Scrubber Utility and the Galaxy Graphics Analyzer, have been
modified to support the new Microsoft technologies. The Application Server Toolkits (GRAccess, MXAccess
and ArchestrA Object Toolkit) support the new Microsoft operating systems as well as Microsoft Visual
Studio 2008.
< top of document >

After installing Application Server, configure your antivirus software to prevent archive
21 of 72 11/04/2011 08:56 AM
files from being scanned. Also, antivirus software should not scan files in the following
ArchestrA folders:
C:\Program Files\ArchestrA\*.*
C:\Program Files\Common files\ArchestrA\*.*
C:\Program Files\FactorySuite\*.* (may not exist in newer installations)
C:\Program Files\Wonderware\*.*
C:\InSQL\Data\*.*
C:\Historian\Data\*.*
C:\Documents and Settings\All Users\Application Data\ArchestrA*.*
From Application Server Platform objects:
History Store Forward directory: (if not default)
From Application Server Engine objects:
Checkpoint directory location (if not default)
<InTouch Application folder path> including:
C:\Documents and Settings\All Users\Application Data\ArchestrA\
<SMCLoggerStoragefilepath>.
The default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\
SQL Server database files of type:
.mdf
.ldf
NOTE: Ensure subfolders of the listed directories are also excluded. Specify folder names
accordingly if you are using a 644bit operating system. For example, the program file's
root directory in a 644bit operating system is C:\Program Files (x86)\... and the
application data root directory in a 324bit operating system is C:\ProgramData\...
< top of document >

The following list shows the minimum computer hardware requirements to host
Application Server version 3.1 SP2 components on both 324bit and 644bit systems. The
Intel Itanium2 processor is not supported.
Galaxy Repository (GR) node

Computer with 2 gigahertz (GHz) or faster processor, 32/644bit. A multi4core
processor is strongly recommended. The Intel Itanium 2 processor is not supported.
Minimum of 2 gigabytes (GB) RAM. 4 GB RAM or is recommended.
At least 30 GB of available disk space for a 324bit operating system; 40 GB for a
22 of 72 11/04/2011 08:56 AM
644bit operating system.

Keyboard.
Development and Application nodes (with and

without InTouch application)
Computer with 2 gigahertz (GHz) or faster processor, 32/644bit. A multi4core
processor is strongly recommended. The Intel Itanium 2 processor is not supported.
Minimum 1 gigabyte (GB) RAM. 4 GB RAM is strongly recommended.
At least 30 GB of available disk space for a 324bit operating system; 40 GB for a
644bit operating system.
Keyboard.
The hardware requirements for using the Alarm Client and Trend Client at run time are the
same as for the InTouch HMI version 10.1 run time. The Windows Vista and Windows
2008 operating systems and SQL Server 2008 impose hardware requirements that may
exceed the minimum requirements for Application Server version 3.1 SP1 and 3.1 SP2. If
you intend to install Application Server 3.1 SP2 on a computer running Windows Vista,
Windows Server 2008, or SQL Server 2008, see the following Microsoft web sites for
hardware requirements:
www.microsoft.com/windows/products/windowsvista/editions
/systemrequirements.mspx
www.microsoft.com/windowsserver2008/en/us/system4requirements.aspx
msdn.microsoft.com/en4us/library/ms143506.aspx#EE32
< top of document >
Software Requirements and

Compatibility
This section describes the operating system, database, and other software requirements
to install Application Server version 3.1 SP2, along with product compatibility.
Operating Systems
23 of 72 11/04/2011 08:56 AM
Operating Systems
For server components: Windows Server 2008 SP2 644bit is the recommended
operating system for computers running server components.
For client components: Windows Vista SP2 324bit or 644bit is the recommended
operating system for computers running client components.
The following table lists the supported operating systems that can be installed on
computers running as Application Server development, application, and GR nodes.
Development and application nodes are considered to be clients of the server GR node.
Wonderware Application Server

Components
ArchestrA
Run Time
(Application
Node) (GR Node)
Windows Server 2008 SP2, Standard, 324bit • • •
Windows Server 2008 SP2, Enterprise, 324bit • • •
Windows Server 2008 SP2, Standard, 644bit
• • •
(emulation)
Windows Server 2008 SP2, Enterprise, 644bit
• • •
(emulation)
• • •
• • •
Windows Vista Business
• • •
Windows Vista Business SP1
• • •
Windows Vista Enterprise
• • •
Windows Vista Enterprise SP1
• • •
Windows Vista Ultimate
• • •
Windows Vista Ultimate SP1
• • •
Windows Server 2003 Standard Edition SP2 • • •
Windows Server 2003 Enterprise Edition SP2 • • •
Windows Server 2003 Standard Edition R2 SP2 • • •
24 of 72 11/04/2011 08:56 AM
Windows Server 2003 Enterprise Edition R2 SP2 • • •

Windows XP Professional SP3 • • See Note 2
Windows XP Tablet •
Notes:
1. The Windows 2000 Professional, Windows 2000 Server, and Windows 2000
Advanced Server operating systems are not supported for Application Server version
3.1 SP1 or SP2. An error occurs if you attempt to install or upgrade Application
Server version 3.1 SP1 or SP2 on a computer running any edition of the Windows
2000 operating system.
2. The computer designated as the Galaxy Repository node can run on Windows XP Pro
only as a single4node configuration of Application Server. Windows Server 2008 is
the recommended operating system for the GR node.
3. The Bootstrap, IDE, and Galaxy Repository are supported by the following language
versions of Microsoft operating systems: English, Japanese, Chinese, German, and
French. The Galaxy Repository is also supported by the English, Japanese, Chinese,
German, and French versions of Microsoft SQL Server 2005 and SQL Server 2008.
Wonderware Application Server 3.1 SP2 is compatible and can co4exist with the following
products:
Wonderware InTouch HMI 10.1 SP2

ActiveFactory 9.2
InTouch CE 10.1
Wonderware Historian Server 10.0
Performance Software 3.5
InControl 7.11 SP2 PO1
Manufacturing Execution Module 1.0
InBatch 9.0
QI Analyst 8.0 SP1 PO1
SCADAlarm 6.0 SP2 PO1
In some cases, Application Server 3.1 SP2 is supported in newer environments than a
compatible product. Application Server 3.1 SP2 has been tested for compatibility with a
listed product only in the environments that are supported by that particular product.
SQL Server Requirements

Microsoft SQL Server 2005 with SP2 or SP3 and SQL Server 2008 SP1 are the databases
supported by Application Server version 3.1 SP2. You must use the Standard or
Enterprise editions of SQL Server 2005 or SQL Server 2008 SP1. Neither the Compact,
Express, nor the Workgroup editions of SQL Server 2005 can be used as the Galaxy
Repository. Refer to the following section, SQL Server Rights Requirements, for further
information.
SQL Server 2005 SP2/SP3 or SQL Server 2008 SP1 must be installed on the
computer designated as the ArchestrA Galaxy Repository node prior to installing
Application Server.
25 of 72 11/04/2011 08:56 AM
You also cannot install and use Application Server on a computer that has both
Microsoft SQL Server 2000 and Microsoft SQL Server 2005 or 2008 installed.
The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the
computer's physical memory.
TCP/IP must be enabled on the computer hosting a SQL Server 2005 or 2008
database. The TCP/IP protocol setting can be verified from the SQL Server Network
Configuration under SQL Server Configuration Manager.
SQL Server Rights Requirements
SQL Server 2008 does not automatically create the BUILTIN\Administrators role as that
was delivered in SQL Server 2005. Because of this change to SQL Server, the Application
Server 3.1 SP2 installation process will create the necessary operating system user group
(aaAdministrators) as well as the necessary SQL Server role. This automated process will
provide the rights required to allow operations within the Galaxy Repository without the
need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be
present and enabled. If you accidentally delete the aaAdministrators group from the
Windows operating system, you can run either of two options to restore it:
Run the Change Network Utility from the Windows Start menu.
Run the aaConfig SQL Utility from the Windows Start menu.
If you accidentally delete the aaAdministrators group from the SQL Server security logins,
you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application
Server User's Guide, About ArchestrA User Accounts, for further information and
procedures about restoring the aaAdministrators group.

The following list describes other third4party software required for Application Server
version 3.1 SP2.
Microsoft .NET Framework 3.5 must be installed on every computer that hosts an
Application Server component. The GR node will require .NET Framework 3.5 SP1 if
it is being installed with SQL Server 2008 as .NET Framework 3.5 SP1 is a SQL
Server 2008 prerequisite. Application Server 3.1 SP2 has been validated with both
.NET Framework 3.5 and 3.5 SP1.
Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008 Microsoft Visual Studio
2005 or 2008 is required only by the MXAccess and GRAccess toolkits distributed
with Application Server.
Alarm Client and Trend Client Requirements

The software requirements for using the Alarm Client and Trend Client at run time are the
same as for the InTouch HMI version 10.1 run time. If you want to trend data from the
Wonderware Historian (formally known as IndustrialSQL Server), version 9.0 or later is
required.
The Trend Client is compatible with the following Wonderware products:
InTouch 10.1 and InTouch 10.1 SP2

Wonderware Application Server 3.1, Wonderware Application Server 3.1 SP1, and
Wonderware Application Server 3.1 SP2
Wonderware Historian 9.0 or 10.0
ActiveFactory 9.2
26 of 72 11/04/2011 08:56 AM
QI Analyst 8.1
< top of document >
Using Application Server with Windows

Server 2008
All behaviors and restrictions described under Using Application Server with Windows
Vista apply to Windows Server 2008. This section describes additional behaviors and
restrictions when using the Windows Server 2008 operating system with Application
Server.
Terminal Services Behavior in Windows Server 2008

In a change from Windows Server 2003, Windows Server 2008 no longer supports the
/console switch as a means of starting the remote desktop (RDP) client, also known as
Session 0 or Terminal Server Console session. In Windows Server 2008, Session 0 is no
longer an interactive session, and is reserved only for Windows services. Windows Server
2008 treats all remote connections as remote RDP sessions regardless of /console,
/admin, or any other switches used to make the connection.
This impacts InTouch functionality such as Alarm Manager that depends on the Terminal
Server Console session. Refer to the InTouch 10.1 SP2 Readme for further information
about InTouch applications running in the Terminal Server Console. The impact to
Application Server is minimal as most Application Server processes run as services. One
impact to Application Server is to carry forward the restriction introduced with the
Windows Vista operating system which permits only one alarm provider. While both
Application Server and InTouch can be configured as alarm providers, only one alarm
provider is supported.
Application Server and InTouch detect when the application is running in the console. In
Windows 2008 it implies that the application was started by a user physically at the
machine. However, this behavior requires that you disable Fast User Switching in both
Windows Vista and Windows Server 2008 operating systems.
To disable Fast User Switching in Windows Vista or Windows 2008, use the following
procedure:
1. Click Start, then Run, and enter gpedit.msc in the text box. Press Enter.
2. Go to the following location:
Local Computer Policy \Administrative Templates\System\Logon.
3. Set Hide entry points for Fast User Switching to Enabled.

4. Exit the Group Policy Editor.
By enabling the policy, Administrators hide the Switch User button in the Windows
logon, in the Start menu, and in the Task Manager. Note that the Group Policy Editor does
not exist in certain editions of Windows Vista. Alternately, you can configure the setting
by editing the Registry.
1. Click Start, then Run, and enter regedit.exe in the text box. Press Enter.
2. Navigate to the following branch:
27 of 72 11/04/2011 08:56 AM
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
\Policies\System.
3. Create a DWORD (324bit) Value named HideFastUserSwitching.

4. Set the Value data for HideFastUserSwitching to 1.
5. Exit the Registry Editor.
Other Windows Server 2008 Restrictions

Windows Server 2008, as with Windows Vista, does not support DDE or NetDDE.
ArchestrA Symbols use the client layer when accessing InTouch tags and appear as
a third4party client trying to access WindowViewer as a data server. As a result,
ArchestrA symbols cannot communicate with InTouch tags. The use of NetDDE for
communication is not recommended.
Windows Server 2008 security, as with Windows Vista, prevents started Windows
services from interacting with desktop objects. This is a User Interface Privilege
Isolation (UIPI) issue. From Windows Vista onwards, DDE cannot communicate
across the session. Scripts such as WWPoke(),WWExecute(),WWRequest() will not
run across the session. You still can run certain functions by using SuiteLink in place
of DDE or NetDDE.
Using Multiple Network Interface Cards with

Windows Server 2008
The behavior of Windows Vista with multiple NICs configured has carried forward to
Windows Server 2008. If you are using multiple network interface cards (NICs) with
Windows Server 2008 SP2, you must configure settings so that the firewall does not
block remote node access to the Galaxy Repository. See Using Multiple Network Interface
Cards with Windows Vista for further information and procedures applicable to Windows
Vista and also to Windows Server 2008.
Using Application Server with Windows

Vista
This section describes specific restrictions when using the Windows Vista operating
system with Application Server and how to configure multiple Network Information Cards
on a computer running Windows Vista.
Vista Restrictions
Application Server version 3.1 SP2 can run under Windows Vista Enterprise,
Business or Ultimate editions. The Windows Vista Home Basic and Home Premium
editions are not supported. The Windows Vista Business Edition is recommended for
use with Application Server.
You must log on as a Windows Vista administrator to run Application Server version
3.1 SP2. You cannot run Application Server as a Windows Vista standard user or
power user.
The Windows Vista User Account Control (UAC) must be disabled when running
Application Server. Refer to Microsoft Windows Vista documentation for instructions
to disable UAC.
When you disable Windows Vista UAC, you must restart the computer before
28 of 72 11/04/2011 08:56 AM
attempting to install the ArchestrA IDE or Wonderware Application Server. A Galaxy

connection error occurs if you attempt to install the ArchestrA IDE or Wonderware
Application Server and you did not restart the computer after you disabled the UAC.
Windows Vista does not support a traditional Application Server single4node
configuration that includes Wonderware Historian (formerly IndustrialSQL Server).
The Galaxy Repository is supported on Vista only for a single4node configuration of
Application Server. For multiple4node Galaxies, Windows Server 2008 SP2 644bit is
the recommended operating system for the Galaxy Repository node.
If the computer that hosts the Galaxy Repository runs on Windows Vista, SP2 must
be applied to SQL Server 2005 installed on the same computer.
A computer running on Vista cannot be configured to be an alarm provider and also
have InTouch WindowViewer on the same computer configured to generate alarms.
Only one of the two will function properly as an alarm provider.
Windows Vista does not support NetDDE. ArchestrA Symbols that use the client
layer when accessing InTouch tags, and appear as a third4party client trying to
access WindowViewer as a data server. As a result, ArchestrA symbols cannot
communicate with InTouch tags. The use of NetDDE for communication is not
recommended.
Windows Vista security prevents started Windows services from interacting with
desktop objects. When Application Server 3.1 SP2 is installed on a computer running
Vista, scripts do not run correctly if they include the InTouch ActivateApp() and
SendKeys() functions. Windows Vista prevents these functions from interacting with
desktop objects to start Windows programs or send keystrokes to these programs.
Using Multiple Network Interface Cards with

Windows Vista
If you are using multiple network interface cards (NICs), you must configure certain
settings for the firewall or else a remote Vista node cannot connect to the Galaxy
Repository node. A connection in Vista is a term used to define a network interface card
(NIC), its settings and the settings of whatever the NIC is connected to. Under certain
circumstances, the connection on your computer can change if, for example, the IP
address on the computer to which you are connected changes. Your computer's
connection can be affected by external factors. During computer startup, and each time a
connection changes, Vista goes through an "Identifying" process to determine which
profile should be assigned to the connection. A profile is a collection of firewall settings
that can be applied to a connection. There are three profiles currently defined in Vista:
Domain , Public ,and Private.
The Domain profile is active only when the computer can authenticate with a domain
controller on all active interfaces such as LAN, wireless, and VPN. The domain profile
may be more or less restrictive than the other two profiles depending on network
security policies.
The Private profile is active whenever the network type for all active network
connections on the computer are identified as private networks. The private profile
typically is used in a more trusted environment and is less restrictive than the public
profile to allow for network discovery.
The Public profile is active in all other circumstances. The public profile typically is
more restrictive than the private profile because the computer often is connected to
the Internet in an insecure location. Network discovery and remote access are
disabled rather than explicitly blocking specific traffic. Firewall exceptions and rules
can be created on any or all of these profiles.
This is important because the OS Configuration utility and the Vista Firewall utility apply
their firewall exceptions to the Domain and Private profiles only. As previously noted, you
29 of 72 11/04/2011 08:56 AM
can specify which profile you want assigned to a connection as long as that connection is
not a Domain connection. This is done through the "Network and Sharing Center". Click
the Network icon located on the right side of the task bar and then click on one of the
networks that is shown. You can change a connection from a Public profile to a Private
profile. The firewall calls these settings "Profiles" but the network calls them "Location
types."
On computers using dual NICs, the first NIC is normally connected to the domain and is
assigned the Domain profile automatically. Windows typically assigns the second NIC the
Public profile.
The first issue is that your entire computer (all connections) is restricted to the most
restrictive of the profiles assigned to any connection. So if the second connection was
assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or
Vista Firewall utilities will be allowed. The exceptions were set for Domain and Private
only, not Public. You must set the second connection to the Private profile for any of the
firewall exceptions to work. You want the active profile on the message exchange (MX)
NIC to be the profile opened by OS Configuration.
The second issue is that it appears that a restart of your computer, or even a restart of a
computer to which you are connected, can change your connection back to the Public
profile. Once again the firewall exceptions will not be effective. You'll have to change the
connection back to the Private profile after each restart or a restart of the connected
computer. To avoid these NIC issues and prevent the "Identifying" process from taking
place on a connection and changing the assigned profile, certain items must be present in
the definition of the connection. Follow these rules and procedures:
If you have only one NIC, no action is required. The profiles and firewall rules are
automatic.
To configure two NICs, do the following:
1. If the second NIC is not physically connected to anything (that means no wire in it), no action is required.
The profiles and firewall rules are automatic.
2. If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal
redundancy setup provided in the Wonderware Application Server User's Guide and the accompanying
online help.
a. Assign the NIC an IP address, subnet mask and gateway address. Typically, these addresses
are internal, non4routable addresses. For example, 192.168.1.xx and 10. x.x.x are common
addresses of this type.
b. A NIC acting as Redundancy Message Channel (RMC) does not require a default gateway.
Otherwise, the gateway can be the same as the IP address. Vista and Windows Server 2008
will identify this NIC and assign it a Private profile.
If you do not configure the second NIC, Vista and Windows Server 2008 will assign a profile of
Public to this NIC and cause all of the Wonderware product firewall exceptions to be deactivated
on all NICs.
3. Set a security policy so that Windows Vista and Windows Server 2008 do not re4set the RMC NIC to a
Public profile on rebooting the system or changing the IP address. To make the Private profile setting
persistent, do the following:
a. On the Windows Start menu, click Run.

b. Enter and run this command: SECPOL.MSC. The Local Security Settings menu appears.
c. Select Network List Manager Policies on the menu tree.
d. Select Unidentified Network from the Network Names displayed.
e. Right click, then select Properties, and then change the Location type from Not configured to
Private.
30 of 72 11/04/2011 08:56 AM
f. Exit the menu and return to Windows.
4. If you have more than two NICs, make sure all connected NICs are configured with an IP address.
< top of document >

The Application Server Installation Help (Install4AppServer.chm) located in the root folder of the installation
CD includes detailed installation and upgrade instructions. Make sure the target computers that you want to
install Application Server version 3.1 SP2 components on meet third4party software requirements. You must
install Wonderware Historian 9.0 Patch 02 or higher to use time propagation and late data from the Wonderware
Application Server to the Historian.
< top of document >

After the hardware and software requirements are met, including the proper operating system, SQL server and
other pre4requisites, you can upgrade to Application Server version 3.1 SP2 from the following versions of
Application Server:

Version 30, including all patches and service packs
Version 3.1
Version 3.1 SP1
Application Server 3.1 SP2 Upgrade Requirements

The following requirements apply when upgrading existing Application Server components to version 3.1 SP2:
1. Upgraded IDE/Client nodes cannot connect to a non4upgraded Galaxy Repository (GR) and vice4versa.
2. The GR Node will be undeployed before upgrading to Application Server 3.1 SP2.
3. Application Server 3.1 SP2 will import a new major version of the WinPlatform object. This will require
the running platforms to be undeployed during the upgrade process.
Winplatform and other related objects on a remote node will be marked as "software update
pending".
A new schema and extension will be added for the alarm comment language switching
feature.
You will not be able to deploy from an upgraded GR node to non4upgraded remote nodes.
< top of document >
Migrating Applications to Application Server

Version 3.1 SP2
31 of 72 11/04/2011 08:56 AM
There is no migration required from version 3.1 to version 3.1 SP2. You can migrate applications from the
following earlier versions of Application Server to version 3.1 SP2:

GR Node Migration
new version 3.1 SP1 schema. For versions earlier than 3.1, as listed in the preceding topic, data from the
existing schema is migrated to the new version 3.1 SP1 schema. Configured Wonderware Historian nodes are
saved in the new schema. The GR node migration fails if the GR node is used as a run4time node for another
GR. No migration is required from version 3.1 to 3.1 SP1.
< top of document >
Resolved Issues ' Application Server Version 3.1 SP2

Wonderware Application Server version 3.1 SP2 resolves the following issues. The issues are listed by their
Change Request number. Where Change Requests were the result of Service Requests and Hot Fixes, those
reference numbers also are included.
L00082045: HF CR L00078597 (Hotfix 1023); SR 24513402:The script from Application Server online
help, "Accessing an Excel Spreadsheet Using CreateObject", does not work with Application
Server 3.0 P02. The following error message displays:
242389 5/28/2008 4:19:51 PM 3300 2700 Error ScriptRuntime
UserDefined_002.vv: Script performed an illegal operation.
242390 5/28/2008 4:19:51 PM 3300 2700 Error ScriptRuntime
UserDefined_002.vv: mscorlib: Exception has been thrown by the
target of an invocation.
This issue has been resolved.

L00088665: HF CR L00087585 (HF 1198); SR28610617: When doing a cascade deploy, the CPU load
was 100%, while deploying the same number of objects in groups resulted in a CPU load of
roughly 30%. This issue has been resolved.
L00088666: HF CR L00075290 (Hotfix 1223); SR 30710884 & SR 31710995: A number of
xxDictionary errors result from a missing dictionary file or if the aaDCT file path contains
invalid characters. You will see a warning message in the SMC Logger that the .aaDCT file is
missing. To resolve this problem, you must replace the xxDictionary.dll file. Messages related
to invalid characters in the path are resolved by creating a new aaDCT path and continuing
the process.
L00088901: HF CR L00086611 (HF 1212); SR 19815629: Some valid domain users, after logging in,
were not visible in the user list in the ArchestrA IDE view security if the ArchestrA security
was set to OS Group. This occurred only when the domain user directly logged in through
InTouch or SMC without logging into ArchestrA IDE. This problem was caused by the length
of the user profile xml string exceeding 1024 characters in some cases.
If the user profile string length is more than 1024 characters, it now splits into segments of
1024 characters. The separate segments are sent to the ClusterFactory Object and there are
appended to form the original string. The original string is then sent for further processing.
32 of 72 11/04/2011 08:56 AM
L00088961: HF CR L00088598 (HF 1238); SR 12610577: Opening the Reference By tab in the
property of an ArchestrA Graphics template caused the IDE to terminate. The cause was a
SQL stored procedure time4out which occurred before the Reference By tab could complete
retrieving visual element data. Adjusting the SQL stored procedure time4out resolved the
issue.
L00089995: HF CR L00089179 (HF 1281); SR 23517430: Galaxy Dump/Load deleted graphics defined
at the instance level. This issue was caused by not exporting the symbol primitives
information as part of a galaxy dump. Exporting the graphic primitive information in the GR
dump operation solved the issue.
Note that a GR dump does not export the graphic content information, it only exports the
names of the graphic primitives.
Also note that creating new instances with GRLoad does not create the graphic content
inside the graphic primitive.
L00089998: HF CR L00088732 (Hotfix 1249); SR 15711415:Factelligence .Net Client Controls were
missing from symbols after importing to the IDE. The importing package contained
Factelligence Version 3.4 controls and the galaxy was using Version 3.5 controls. The issue
was resolved by modifying the way the event parameter's assembly is loaded. Instead of
reading the assembly name from serialized data, the assembly name is now read from the
ObjectEventParam object that initializes while loading the client control's event animations.
If the ObjectEventParam object is not initialized, the assembly name is read from the
serialized data.
L00090013: HF CR L00076399 (Hotfix 1025); SR: 19713174 & SR 31710971: During a reconnection
to the TIPS OPC server, the Application Server OPCClient object could not add an item and
displayed the following warning: Missing/Pending connection to OPC Server . can't
add items yet. The issue was resolved by implementing the following behavior:
1. When the OPC Client starts, it will immediately attempt to connect.

2. If the OPC Client is connected and gets disconnected it will immediately try to
reconnect, raising the restartCnt by 1. After RestartPeriod it will reconnect again,
raising restartCnt by 1 again. When Restart Max is reached, after exactly RestartMax
* RestartPeriod seconds, it will raise the RestartAlarm and no further restart attempts
will be made.
3. Whenever the OPC Client connects, it will set RestartCnt to 0 and lower the
RestartAlarm.
4. When ResetRestart is set to true, it will set RestartCnt to 0 and lower the RestartAlarm
and attempt to reconnect immediately. If it is already connected, setting ResetRestart
will not cause a disconnect followed by a connect.
L00090687: HotFix 1204; SR # 37510042: A GRAccess query for all objects with pending changes
returned the container instead of the object itself. The case "deployedwithpendingChanges"
added to the query resolved the issue.
L00090812: (Also see L00090013 in this section.) When you shut down OPCServer or it shuts down due
to any failure, the OPCClient proxy object will try to reconnect after "Restart Period" for
"Restart" attempt times. The earlier logic was that for each scan, OPCClient will try to
re4connect for "Restart attempts" times within "Restart Period". The modified logic is that
after the connection fails, OPCClient will try to connect after each "Restart Period" for
"Restart attempts" times. If the "Restart Period" is 20000 ms, it will try to reconnect after 20
sec instead of at each scan period. Due to this new connection logic, current functionality of
the restart connection is changed, so you need to modify the "Restart Period" for "Restart
attempts" accordingly.
33 of 72 11/04/2011 08:56 AM
L00090974: HF CR L00090176(HF 1295); SR 31610661 CR A500002074: A memory leak was

occurring in the POM service. SCC.LIB leaked handles if the license file was continually
accessed. The issue was resolved by using a cached version of the license file data.
L00091015: HF CR L00085452 (HF 1137); SR22315668: Private bytes of an AppEngine
(DINetworkA) were seen to leak memory with the warning message "Write Transaction was
completed by the ScanGroup not by the Server" logged from the Scan Group run4time
primitive. Aborting pending write requests then clearing the vector in
ScanGroupRuntime2.dll resolved the issue.
L00091167: HF CR L00089991 (Hotfix 1301); SR 17132448: A newly created user could not log on
from within InTouch. After logging on to the IDE once, the InTouch logon worked. The user
initially was not able to log on because the roles were not properly being configured for the
user. The issue was resolved by using active directory services to get the user's full name
when NetUserGetInfo() fails. The user object, obtained by using the ADsGetObject API is
used to get the user full name. The ADsGetObject uses an anonymous bind in case the user
authentication fails. If this API also fails then the user name itself is assigned as the user full
name. This ensures that the full user name is always set and roles are updated for the user to
log on.
L00091226: When the OnShow symbol script contains external references the data may not be available
at run time due to a timing issue. For example, this can occur with the ArchestrA symbol
method SetCustomPropertyValue. To resolve this issue, Application Server 3.1 SP2 has
enabled a configurable OnShow symbol script timeout to allow external references to resolve
in the following sequence of events:
1. The data is subscribed and the symbol will be drawn disabled.

2. A timer triggers for the OnShow script with a user4configurable maximum wait time.
3. The timer callback execute. It checks for initialization of all data references.
4. Data Callbacks occur for all subscribed data references.
5. The timer callback executes. It checks references and proceeds to execute the scripts.
6. The symbol is enabled, then the OnShow script executes followed by triggering the
timer for the While Showing script.
7. Named scripts become eligible for execution as soon as OnShow completes.
OnShow will not wait for Invalid references and custom "444" properties to resolve. If the
external data does not become available within the configured timeout, the OnShow script
will still execute but will place a message in the Logger that not all references have been
resolved. Because WhileShowing and named scripts will be blocked until OnShow executes,
some events may be missed. For example, the named script OnDataChange will not run
during the time OnShow is delayed even if the data point is changing.
When you select the OnShow predefined script, the Data Timeout text box displays in place
of the usual Trigger Period text box. Use the following parameters to configure the Data
Timeout:
The default for new graphics is 1000ms.

The default for migrated graphics is 0ms.
Maximum value permitted is 30000ms.
Minimum value permitted is 0ms.
Only integers are valid.
L00091315: Hotfix 1294; SR#19815788 and 103114852: The Engine CPU attribute was stuck in
initializing when the IP address was used for the platform in an IA series multi4NIC system.
With revisions in NTPlatformPrimitive3.dll, the performance counter name can be read
successfully and resolves the issue. (This was an issue primarily for the InFusion industrial
automation product in a multi4NIC system.)
34 of 72 11/04/2011 08:56 AM
L00091737: HF CR L00090963 (HF 1336); SR103115447: The Pv.Bad.InAlarm and Pv.Bad.Condition

displayed as true but quality displayed as good with C0:GOOD. Replacing
xxAnalogDeviceRuntime3.dll on the GR node resolved the issue.
L00091821: HF CR L00090748 (HF 1327); SR 19416904: AppEngine redundancy did not fully
function if one computer of the pair shut down normally rather than through an abrupt power
loss or network interruption. After the failover, Platform Manager showed the active engine
as running OffScan while Object Viewer ScanState showed the active engine running
OnScan, which is correct. Replacing NTPlatformPrimitive5.dll resolved the issue.
L00091902: HF CR L00091431 (HF 1356); SR 103115467: The Alarm ACK State of the Field Attribute
was not retained after failover. The Alarm was reported with a new time stamp. The solution
including checking Alarm condition only after the quality initialization is completed and
modifying logic so that no unwanted event is reported on failover resolved the issue.
L00091975: HF CR L00091534 (Hotfix 1363); SR 23517753: The Alarm attribute was writing back to
the word that generated it, causing it to change the state. This occurred during a Force Fail
Over between a redundant pair of services. To resolve this issue, a new interface has been
added to return the correct primitive (100 for Boolean PV).
L00092243: HF CR L00091788 (Hotfix 1375); SR 19815933: AlarmMrg.exe was not closing when
exiting View.exe if the application was using the AlarmClient .Net control. Reference counts
were not properly disposed while closing the view, and one extra call was made to initialize
alarm manager while subscribing to alarms from the Alarm Control client. The issue was
resolved by avoiding the extra call to initialize Alarm Manager while subscribing to alarms
from the Alarm Control client by providing the alarm consumer name and by calling
Unsubscribe Alarms while shutting down the view.
L00092440: HF CR L000091991 (HF 1387); SR: 28610697: An unknown error occurred when
attempting to restore the GR Backup cab file. Ensuring that the number of zip entries are
written correctly resolved the issue.
L00092488: HF CR L00092312 (Hotfix 1406); SR 32010081: Objects marked for software upgrade
were taking up to two minutes per object to deploy. The issue was resolved in the stored
procedures to improve the deployment process for an object with software upgrade required.
L00092942: HF CR L00091140 (Hotfix 1374); SR 37510140: If you set an object Execution Order =
"After" and the Relative Object="@MyContainer", a warning icon displays unless you don't
do a validate. The issue was resolved by a check for primitive ID, general and attribute,
execution order and set attribute resolution to MxReferenceAttributeNotPresent.
L00092967: HF CR L00089379 HF'1400; SR33931273: AppEngine and ViewEngine status displayed
as being off scan while really being on scan. The scan state in Object Viewer correctly
showed the engines as on scan. Modifications in NTPlatformPrimitive4.dll resolved the issue.
L00093073: HF'1410 CR L00092403; SR 31711104: After setting an input source to "444"via script the
item returned a GOOD quality and displayed the last known value in Application Server 3.0.
Clients displayed an incorrect value with a good quality when the PLC Value changed. The
issue was resolved with revisions to two input/output run4time DLLs.
L00093711: HF CR L00092793 (Hotfix 1437); SR 38910034: Upgrading from Application Server 3.0
SP2 to 3.1 SP1, creating one user defined object template which contains an embedded
symbol with the show symbol animation having a property of user defined window title, then
exporting this object and importing to the higher version displays SMC Logger errors and
displays a warning icon on the imported template. This issue was resolved as follows: If the
Localized Item count=0, and if the translation Item is not able to find the key for the window
title, then we do not assign the translation string to TitleText.
L00093791: HF CR L00093406 (Hotfix 1467); SR 103115946: The internal_add_folder store
procedure performs a transaction which starts after the duplicate name check. In a multi4
threaded scenario, this can create a duplicate folder with same name within the parent folder.
35 of 72 11/04/2011 08:56 AM
The issue was resolved by beginning the transaction by adding it in the start of the stored
procedure "Internal_add_folder".
L00093792: HF CR L00093412 (Hotfix 1467); SR 103115935: If an error occurred when checking in an
object, the message which was returned from the PreCheckIn event was different from
CommandResult.CustomMessage from GRAccess. When a CheckIn error occurred, aaGR
sent the default error message to the clients and did not consider the custom preCheckIn
Message. The issue was resolved by retrieving a custom message if one is configured in an
AOT object and using it to notify clients.
L00094159: HF CR L00093510 (Hotfix 1473); SR 33810942: When using the GRAccess to get an
enumeration of IgObjects with a specified template name the returned objects have a count
of 1. But accessing the item either by name or by index displays the error message
HRESULT: 0x80004002 (E_NOINTERFACE))."} System.Exception
{System.InvalidCastException}.
In Application Server 3.1 SP1, for version 1.3 type libraries, a separate "IgObject13" was
defined in IgObject.idl. However, in the connection maps a corresponding interface entry
point was not defined. The issue was resolved by defining a corresponding interface entry for
IgObject13 in the header files of both template and instance.
L00094202: HF CR L00092439 (Hotfix 1419); SR 38910033: Deleting a UDA removed other Input
Extensions in derived templates and instances. During shapechange, extensions were copied
to the derived objects. However when an dynamic attribute in the
ParseAndProcessXMLInfo() failed to add as it was deleted in the parent template, the
function returned failure immediately without processing other nodes in the XML passed by
SetExtensionInfo(). The issue was resolved by continuing the process until all
"ExtensionInfo/AttributeExtension/Attribute" nodes have been processed.
L00094323: HF CR L00093923 (Hotfix 1494); SR 103116000: LMX displays Invariant Failed errors
when migrating from IAS 2.5 to IAS 3.1.100 due to bad cache files in \ProgramFiles
\ArchestrA\Framework\bin\Cache. The issue was resolved by deleting the invalid
ObjectHandleCache file when an incorrect cache file is detected. An info message,
CObjectRefCache::InitializeCacheFromFile . deleting : <drive>:\< file path
and name > is logged in the SMC logger.
L00094923: HF CR L00094203 (Hotfix 1504); SR 103115892: When a SuiteLink connection was

established and the advanced communication setting was disabled, wwClintf was supposed
to behave the same way before Active On Demand was introduced. But the wwClintf code
did not consider this setting and always invoked the Active On Demand (SOD) interface
pointer, which prevented the items from being released from the DAServer active list. The
issue was resolved by looking for the value of the �GlobalAdviseOnlyActiveEnabled�
attribute in the GlobalRuntimeSettings.xml file. If the value is false, then the SOD pointer is
not invoked.
L00094929: HF CR L00093964 (Hotfix 1499); SR 38910056: Named Scripts inside an Archestra
graphics did not execute if binded to a bad quality InTouch Tag. If the status was bad or
initializing, the value change flag was set to false and the script did not execute. The issue
was resolved by executing the scripts even if the quality is bad but the category is okay,
meaning that data is successfully coming from InTouch to ArchestrA.
L00095041: HF CR L00094050 (Hotfix 1543); SR 23517971: Historian received late data from
Application Server when ACM was enabled. If the attribute being historized was viewed
with InTouch or Object Viewer, then the value in the earlier messages ceased updating. The
issue was resolved by modifying LMX modified to not use duplicate cacheindex values when
re4subscribing to an attribute.
L00095516: HF CR L00083688 (Hotfix 1097); SR 19217566: Unable to browse the Domain for users
and groups in the IDE when there was no local domain controller. While querying the active
directory for the group information, the procedure was fetching DNSHOSTNAME and
36 of 72 11/04/2011 08:56 AM
parsing that again before making the LDAP query. The issue resolved by using the domain
name directly (selecting the domain name in the text box) rather than reading
DNSHOSTNAME and parsing it before making the LDAP query.
L00095546: HF CR L00093790 (Hotfix 1488); SR 38910081: Using a UDA InputOutput extension, the
TimeStamp did not propagate between items. If the alarm extension was enabled for this
UDA in the alarm viewer, the DateTime was always the same. This problem occurred if the
alarm attribute was configured with the bit value of an InputOutputExtenstion attribute of
integer type. For example, if alarm1 was configured as Me.alarm_word.00 then the value of
alarm1 was changed, the change did not propagate the timestamp. If the alarm1
InputOutputExtension is set as Me.alarm_word then the timestamp propagated correctly. To
resolve this issue, in the NotifyAttributeChange3() method, the timestamp value of extended
attribute is now retrieved. This attribute holds the time at which the previous value has been
modified but not the time stamp of the new value.
L00095597: HF CR L00094408 (Hotfix 1524); SR 103116126: A Security4audit event message contains
the following information: Operator1, which is the full name of the primary operator
requesting a change. The full name is an attribute of the UserProfile. Operator2, which is the
full name of the secondary operator validating the change, if any. However, in the
WWALARMDB and AlarmClient, the name of the operator which produces the event was
not saved. In Attribute security type : Verified Write, all User1, User2, and Operator fields
were blank. To resolve this issue, code was modified to skip the condition to get the local
node of the operator, copied the Operator full name macro to get the proper name, and set an
event flag to get the operator related parameters instead of AckOperator parameters.
L00095697: With Advanced Communication Management (ScanOnDemand) enabled, if the PV value is
not subscribed, subscribing to other attributes resulted in no values. Code has been added to
the following attributes so that the PV attribute can be activated when any of these attributes
are subscribed:
PV.IsActive1
PV.IsActive2
PV.IsNULL
PV.IsInTransition
PV.IsPassive
L00095701: HF CR L00095308 (Hotfix 1521): LMX DLL leaked COM BSTR handles and memory.
This was especially noticeable when strings were involved in the MX Value data transfer.
Code has been modified to correct the leaks in the COM BSTR memory.
L00095758: HF CR L00094349 (Hotfix 1549); SR 33810984: A .Net error displays in the deployed
InTouch application which has a show symbol animation when displayed with a desktop
resolution width less than 460. The issue occurred due to client size of the symbol when the
ShowSymbolAnimationDialog initializes. When the client size was greater than the desktop
resolution width, it resulted in the .Net error. The issue was resolved by capturing errors in
InitializeComponent method and logging them to the SMC logger.
L00096540: HF CR L00095782 (Hotfix 1573); SR 23518325: The value returned by a Redundant DI
Object could become stuck and would not reinitialize on failover. As a result, acknowledged
alarms became unacknowledged. This issue has been resolved in the RedundantDIObject and
is updated during Galaxy patching.
L00096755: HF CR L00096204 (Hotfix 1592): Error messages Access Denied were being logged
during the BlockRead operation. Code has been modified to avoid the Access Denied error
messages in the logger during the BlockRead operation.
L00097073: HF CR L00094563 (Hotfix 1528); SR 19417068: A forced failover caused AppEngine
redundancy partner status to remain in Switching to Standby state. Synchronizing with
ObjectSynchMgr took one hour. The Bootstrap worker thread was busy processing large
37 of 72 11/04/2011 08:56 AM
failover status messages (~50 Kb) after a restart of the AOS2 node. This caused the newly
forced failover engine to wait for the redundancy status while restarting. To resolve this
issue, modifications have been made to avoid duplicate messages while the AOS2 node is
starting up. This reduces the number of failover messages which the worker thread has to
process.
< top of document>
Known Issues ' Application Server Version 3.1 SP2

This section describes all known issues identified in Application Server Version 3.1 SP2.
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.
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.
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 as4designed. 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 Application
Server, but was not required for InTouch.
L00092675: In the alarm comment run4time language switching feature, the PhraseId can go out of sync
in exported files for the same alarm message in different languages. This doesn�t 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 re4export all the languages of the conflicting file from the Galaxy, and re4import 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: On Vista and onwards, the DDE cannot communicate across sessions. This is a User
Interface Privilege Isolation (UIPI) issue. For example, with 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 Application Server version 2.5 to version 3.1 SP1, the following
error message appears: "ArchestrA.Configuration.PackageServerNet.PackageServerNet
38 of 72 11/04/2011 08:56 AM
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 DASevers are installed first and then ArchestrA
products are installed. This issue will be addressed in future DASevers 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 Application Server version 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 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 2008 644bit
SP2 Standard Edition operating system with SQL Server 2008 SP1 installed. These drivers
are 324bit drivers and are not visible in a 644bit system directly from Control Panel,
Administrative Tools, DataSources(ODBC). You can create ODBC connections by
running C:\Windows\SysWOW64\odbcad32.exe. This is a 324bit application, which will
display 324bit drivers. This issue does not occur on 324bit systems.
Microsoft does not provide a 644bit OLE DB Provider for Oracle. Oracle provides a separate
OLE DB Provider for use on 644bit 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 will not timeout.
3. Use the asynchronous script with an appropriate timeout limit.
L00097788: Existing license CDs have issues running aaLicView.exe in a 644bit operating system and will
not correctly install a license. You must use the license utility installed with the Application
Server or InTouch software.
L00098305: After upgrading the GR node, a Deploy/Un4deploy attempt on a non4upgraded remote
platform undeploys InTouchViewApp and ViewEngine assigned under the non4upgraded
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.
39 of 72 11/04/2011 08:56 AM
This behavior does not occur if SOD is disabled.

L00099445 With SQL Server 2008 installed, and Application Server 3.1 SP2 installed (IDE and Boostrap
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 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/644bit and Windows Vista 32/644bit operating systems, with
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 to populate the
custom property values.
<top of document >

Item Location of Change Existing Change

Documentation
1 Creating and Managing n/a Add the following text after the first paragraph:
ArchestrA Graphics
User's Guide If you perform a first4time string substitution on an
(aaGraphics.pdf), embedded symbol in the primary language, that
"String Substitutions and substitution is shown in the secondary languages.
Language Switching" You can then perform a substitution in the secondary
section, page 426 language to create a string substitution specific to the
secondary language.
Application Server Help
(IDE.chm), If you perform a first4time string substitution on an
"String Substitutions and embedded symbol in a secondary language, the
40 of 72 11/04/2011 08:56 AM
Language Switching" substitution is also applied to the primary language,

topic because the translated string that previously existed
for the primary language is no longer valid. Because
the primary language value is changed in the symbol,
this string applies to all secondary languages
configured. You can then perform a second
substitution in the primary language, which will
apply to all secondary languages except the ones that
have had a specific substitution set.
If you perform a string substitution in a secondary

language with an existing string substitution in the
primary language, the new substitution is applied to
the secondary language only.
2 Application Server n/a Add the following NOTE text after the first
User's Guide (IDE.pdf), paragraph:
p.134
NOTE: This dependence on the attribute being
ArchestrA IDE Help referenced by a running application is only the case
(IDE.chm), when the attribute subscription is not already active
"Configuring Advanced due to configuration for history, alarming, or
Communication scripting. For example, if an attribute is configured
Management" topic for history, the subscription to the field device will
always be active regardless of what window is active
Wonderware Application in InTouch, and regardless of whether InTouch is
Server 3.1 Readme, running at all.
"About this Release",
"Advanced
Communication
Management" section.
Saving the Date Timestamp as Historical Data
If slow updates for real4time data values are received from an I/O source and an intermittent network
disconnect occurs, the timestamp of the first data value of a historized attribute uses the AppEngine's timestamp
instead of the source's timestamp. In the following example, in row number 4, the value "30" is sent again to the
historian, but the timestamp is the AppEngine timestamp and not the actual timestamp of "2008411424
18:50:41.061" when the value of 30 was generated from the I/O source.
DateTime TagName Value Quality QualityDetail OPCQuality

2008411424 18:48:30.081 Realtime_Client.ival 20 133 44 192
2008411424 18:51:38.666 Realtime_Client.ival NULL 1 24 0
2008411424 18:52:06.670 Realtime_Client.ival 30 0 192 192 44> Row number 4
If slow updates for late data values are received from an I/O source and an intermittent network disconnect
occurs, the timestamp of the first data value of a historized attribute is modified to maintain the time sequence.
In the following example, in row number 4, the value "30" is sent again to the historian, but the timestamp is
modified by adding 5 milliseconds to previous timestamp of the NULL data value. Note that a QualityDetail of
704 is stored for the data value in row number 4.

2008411424 18:48:30.081 Latedata_Client.ival 20 133 44 192
41 of 72 11/04/2011 08:56 AM
2008411424 18:50:53.625 Latedata_Client.ival NULL 1 24 0

192 44> Row number
2008411424 18:50:53.630 Latedata_Client.ival 30 0 704
4.
< top of document >

from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html
After installing Adobe Reader, double4click on a PDF file with your pointing device to view the book with
Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.
Application Server installation instructions are located in the root folder of the Application Server installation
CD as an online help file. You can view these instructions by clicking the Installation Guide button in the
Application Server installation program. Product documentation is also available with Application Server online
help.
Documentation Set
applications.
local hard drive.
42 of 72 11/04/2011 08:56 AM

The Application Server version 3.1 books are delivered as an Adobe PDF package, which provides a master
index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that
belong to the Application Server product library.
Open Adobe Reader.

Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
Type the word or phrase that you want to search for in the Application Server books.
In the Where would you like to search area, select the option to search all PDF books.
If necessary, locate the Application Server version 3.1 PDF package located on your Wonderware CD or on a
network folder containing copiesoftheApplicationServerPDFbookfiles.
Afterproductinstallation,thesefilescanbefoundat:<driveletter>:\Program Files\ArchestrA\Framework\Docs.
Click Search. Adobe Reader lists the Application Server books that contain a match for your search criteria.
Click on the links to open the Application Server book to the topic containing the information that meets your
search criteria.
< top of document >
Wonderware Application Server 3.1 Service Pack 1

Readme
About This Readme

This document adds information from Wonderware Application Server 3.1 Service Pack 1 (SP1) to the previous
Readme file included with Wonderware Application Server 3.1.
About Application Server 3.1 SP1

Wonderware Application Server 3.1 SP1 includes the following enhancements and new features:
Enhanced Object Import

You can import an object even when it has a lower (earlier) configuration version than an existing object.
During the import, you can:
Overwrite objects with the same tagname and codebase as an existing object even if the imported object
is older than the existing object
Migrate base templates with newer or older codebase
Rename objects with the same tagname but a different codebase
Enhanced Service Pack Installation

The service pack installer has been modified so that it will not require a deployed platform to be automatically
removed or the software uninstalled during the upgrade process. Only major upgrades will require a deployed
platform to be removed and redeployed.
43 of 72 11/04/2011 08:56 AM
< top of document >

ArchestrA folders (ensure subfolders of the listed directories are also excluded):
C:\Program Files\ArchestrA\*.*
C:\Program Files\Common files\ArchestrA\*.*
C:\Program Files\FactorySuite\*.* (may not exist in newer installations)
C:\Program Files\Wonderware\*.*
C:\InSQL\Data\*.*
C:\Documents and Settings\All Users\Application Data\ArchestrA\*.* From Application
Server Platform objects:

C:\Documents and Settings\All Users\Application Data\ArchestrA\
<SMCLoggerStoragefilepath>. The default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\ SQL Server
database files of type:
.mdf
.ldf
< top of document >

The following list shows the minimum computer hardware requirements to host Application Server version 3.1
SP1 components.
2 gigahertz (GHz) or faster dual core processor, or a 3 GHz or faster single core processor. A dual core
processor is strongly recommended for optimal performance.
Minimum of 2 gigabytes (GB) RAM. For Galaxies with more than 500 objects, 4 GB RAM is
recommended in the GR node.
30 GB of available disk space.
CD4ROM or DVD drive.
Keyboard.
Development and Application nodes
2 GHz or faster processor.
44 of 72 11/04/2011 08:56 AM
Minimum 1 gigabyte (GB) RAM. For improved performance 4 GB RAM is strongly recommended.
Keyboard.
The hardware requirements for using the Alarm Client and Trend Client at run time are the same as for the
InTouch HMI version 10.1 run time. The Windows Vista operating system imposes hardware requirements that
may exceed the minimum requirements for Application Server version 3.1 SP1. If you intend to install
Application Server 3.1 SP1 on a computer running Windows Vista, see the following Microsoft web site for
hardware requirements: www.microsoft.com/windows/products/windowsvista/editions
/systemrequirements.mspx
< top of document >
Server version 3.1 SP1.
Operating Systems
Operating Systems
Windows Server 2003 Standard Edition SP2 is the recommended operating system for computers running
server components.
Windows XP SP3 is the supported XP version for this release.
Windows XP Professional SP3 is the recommended operating system for computers running client
components.
ArchestrA Run
Time
(Application
Node) (GR Node)
Windows Vista Business (See Vista Restrictions) x x x
Windows Vista Business SP1 (See Vista
x x x
Restrictions)
Windows Vista Enterprise (See Vista
x x
Restrictions)
Windows Vista Enterprise SP1 (See Vista
x x x
Restrictions)
Windows Vista Ultimate (See Vista Restrictions) x x x
Windows Vista Ultimate SP1 (See Vista
x x x
Restrictions)
45 of 72 11/04/2011 08:56 AM
Windows Server 2003 Standard Edition SP2 x x x

Windows Server 2003 Enterprise Edition SP2 x x x
Windows Server 2003 Standard Edition R2 SP2 x x x
Windows Server 2003 Enterprise Edition R2 SP2 x x x
Windows XP Professional SP3 x x See Note 2
Windows XP Tablet x
Notes:
1. The Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server operating
systems are not supported for Application Server version 3.1 SP1. An error occurs if you attempt to
install or upgrade Application Server version 3.1 SP1 on a computer running any edition of the Windows
2000 operating system.
2. The computer designated as the Galaxy Repository node can run on Windows XP Pro only as a
single4node configuration of Application Server. Windows Server 2003 is the recommended operating
system for the GR node.
3. You can run Application Server only on computers running a 324bit operating system. You cannot run
Application Server on a computer running a 644bit operating system.
4. The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of
Microsoft operating systems: English, Japanese, Chinese, German, and French. The Galaxy Repository is
also supported by the English, Japanese, Chinese, German, and French versions of Microsoft SQL Server
2005.

Microsoft SQL Server 2005 with SP2 is the only database supported by Application Server version 3.1 SP1. You
must use the Standard or Enterprise editions of SQL Server 2005. Neither the Compact, Express, nor the
Workgroup editions of SQL Server 2005 can be used as the Galaxy Repository.
SQL Server 2005 SP2 must be installed on the computer designated as the ArchestrA Galaxy Repository
node prior to installing Application Server.
2000 and Microsoft SQL Server 2005 installed.
memory.
TCP/IP must be enabled on the computer hosting a SQL Server 2005 database. The TCP/IP protocol
setting can be verified from the SQL Server 2005 Network Configuration under SQL Server
The Microsoft SQL Server 2005 login for BUILTIN\Administrators group must be present and enabled.

The following list describes other third4party software required for Application Server version 3.1 SP1.
Microsoft .NET Framework 3.5 Microsoft .NET Framework 3.5 must be installed on every computer that
hosts an Application Server version 3.1 SP1 component. The Application Server installation program halts
if .NET Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you
install .NET Framework 3.5. If you click Install Prerequisites, the installation program automatically
installs .NET Framework 3.5.
Microsoft Visual Studio 2005 Microsoft Visual Studio 2005 is required only by the MXAccess and
46 of 72 11/04/2011 08:56 AM
The software requirements for using the Alarm Client and Trend Client at run time are the same as for the
InTouch HMI version 10.1 run time. If you want to trend data from the Wonderware Historian (formally known
as Industrial SQL Server), version 9.0 or later is required.
InTouch 10.1
Wonderware Application Server 3.1 and Wonderware Application Server 3.1 SP1
Wonderware Historian 9.0
ActiveFactory 9.2
QI Analyst 8.1
< top of document >

This section describes specific restrictions when using the Windows Vista operating system with Application
Server and how to configure multiple Network Information Cards on a computer running Windows Vista.
Vista Restrictions
Application Server version 3.1 SP1 can run under Windows Vista SP1, Windows Vista Enterprise SP1,
Windows Vista Business SP1, or Windows Vista Ultimate SP1. The Windows Vista Home Basic and
Home Premium editions are not supported. The Windows Vista Business Edition is recommended for use
You must log on as a Windows Vista administrator to run Application Server version 3.1 SP1. You cannot
run Application Server as a Windows Vista standard user or power user.
The Windows Vista User Account Control (UAC) must be disabled when running Application Server.
Refer to Microsoft Windows Vista documentation for instructions to disable UAC.
When you disable Windows Vista UAC, you must restart the computer before attempting to install the
ArchestrA IDE or Wonderware Application Server. A Galaxy connection error occurs if you attempt to
install the ArchestrA IDE or Wonderware Application Server and you did not restart the computer after
you disabled the UAC.
Windows Vista does not support a traditional Application Server single4node configuration that includes
Wonderware Historian (formerly IndustrialSQL Server).
The Galaxy Repository is supported on Vista only for a single4node configuration of Application Server.
For multiple4node Galaxies, Windows Server 2003 is the recommended operating system for the Galaxy
Repository node.
If the computer that hosts the Galaxy Repository runs on Windows Vista, SP2 must be applied to SQL
Server 2005 installed on the same computer.
A computer running on Vista cannot be configured to be an alarm provider and also have InTouch
WindowViewer on the same computer configured to generate alarms. Only one of the two will function
properly as an alarm provider.
Windows Vista does not support NetDDE. ArchestrA Symbols that use the client layer when accessing
InTouch tags, and appear as a third4party client trying to access WindowViewer as a data server. As a
result, ArchestrA symbols cannot communicate with InTouch tags. Windows Server 2003 and Windows
XP Pro still support NetDDE.
Windows Vista security prevents started Windows services from interacting with desktop objects. When
Application Server 3.1 SP1 is installed on a computer running Vista, scripts do not run correctly if they
include the InTouch ActivateApp() and SendKeys() functions. Windows Vista prevents these functions
from interacting with desktop objects to start Windows programs or send keystrokes to these programs.
Using Multiple Network Interface Cards with Windows Vista
47 of 72 11/04/2011 08:56 AM
If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or
else a remote Vista node cannot connect to the Galaxy Repository node. A connection in Vista is a term used to
define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under
certain circumstances, the connection on your computer can change if, for example, the IP address on the
computer to which you are connected changes. Your computer's connection can be affected by external factors.
During computer startup, and each time a connection changes, Vista goes through an "Identifying" process to
determine which profile should be assigned to the connection. A profile is a collection of firewall settings that
can be applied to a connection. There are three profiles currently defined in Vista: "Domain", "Public" and
"Private".
The Domain profile is assigned automatically to a connection if a domain controller for the domain to
which the computer is a member is found on the connection.
The Public profile is designed to keep the computer from being visible to other computers on the network.
Network discovery is turned off for the Public profile.
The Private profile is used for a more trusted environment. Network discovery is turned on for a Private
profile. Firewall exceptions and rules can be created on any or all of these profiles.
This is important because the OS Configuration utility and the Vista Firewall utility apply their firewall
exceptions to the Domain and Private profiles only. As previously noted, you can specify which profile you
want assigned to a connection as long as that connection is not a Domain connection. This is done through the
"Network and Sharing Center". Click on the Network icon in the right side of the task bar and then click on one
of the networks that is shown. You can change a connection from a Public profile to a Private profile. The
firewall calls these settings "Profiles" but the network calls them "Location types." On computers using dual
NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. The
second NIC is typically assigned the Public profile. The first issue is that your entire computer (all connections)
is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was
assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Vista Firewall
utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the
second connection to the Private profile for any of the firewall exceptions to work. The second issue is that it
appears that a restart of your computer, or even a restart of a computer to which you are connected, can change
your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have
to change the connection back to the Private profile after each restart or a restart of the connected computer.
To avoid these NIC issues and prevent the "Identifying" process from taking place on a connection and
changing the assigned profile, certain items must be present in the definition of the connection. Follow the rules
below:
1. If you have only one NIC, no action is required. The profiles and firewall rules are
automatic.
2. If you have two NICs follow the actions below:
If the second NIC is not physically connected to anything (that means no wire
in it), no action is required. The profiles and firewall rules are automatic.
If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal
redundancy setup. Vista will identify this NIC and assign it a Private profile. If the NIC is not
configured, Vista will assign a profile of Public to this NIC and cause all of the Wonderware
product firewall exceptions to be deactivated on all NICs. For the NIC to be configured properly,
give it an IP address, sub net mask and gateway address. The gateway address can be the same as
the IP address. Usually these addresses will be the internal, non4routable addresses like 192.168.0.x
or the 10.x.x.x range.
If you have more than two NICs, make sure all connected NICs are configured with an IP address
and default gateway address and have been assigned a profile of private.
< top of document >
48 of 72 11/04/2011 08:56 AM
install Application Server version 3.1 SP1 components on meet third4party software requirements. You must
install Wonderware Historian 9.0 Patch 02 to use time propagation and late data from the Wonderware
Application Server to the Historian.
< top of document >

After the hardware and software requirements are met, you can upgrade to version 3.1 SP1 from the following
versions of Application Server:

Version 3.1
Because the hardware and software requirements of Application Server 2.0 are not compatible with those of
Application Server 3.1 SP1, you cannot directly upgrade from Application Server 2.0. But, you can migrate
applications developed with version 2.0 Patch 01 to version 3.1.
Upgrade Limitations
The following limitations apply when upgrading existing Application Server components to version 3.1 SP1:
Before upgrading the GR node, all deployed nodes must be at the same version and there should be no
connected clients.
Before upgrading a visualization node, the InTouchViewApp AutomationObject should be shut down.
Uploading application run4time changes from a non4upgraded node is not permitted.
InTouch HMI must be upgraded to version 10.1 if it is installed on the same computer that has upgraded
Application Server version 3.1 0r 3.1 SP1 components.
If Wonderware Historian is installed on the same computer with Wonderware Application Server, you
must install Wonderware Historian 9.0 Patch 02 before upgrading to Wonderware Application Server 3.1
or to Application Server 3.1 SP1.
Updating Wonderware Application Server 3.1 with SP1

Install the service pack on the Application Server nodes after installing the service pack on the Galaxy
Repository node.
Where possible, exit all applications that are running. To avoid potential platform and engine shutdown
issues during the patch installation, we recommend the engines and platform be set off4scan then
manually shutdown prior to running the installer.
To install Service Pack 1:
1. Open the ArchestrA System Management Console (SMC).

2. Expand Platform Manager.
3. Login to the Galaxy.
4. Select the Platform for which Service Pack 1 is to be installed.
5. From the Right pane, select one engine at a time. Engines hosting DI objects should be set
off4scan and shutdown last.
6. Right4click the engine and set it off4scan.
49 of 72 11/04/2011 08:56 AM
7. Right4click the engine and shut it down.

8. Shutdown the platform.
9. Exit the System Management Console prior to installing the patch.
10. After Service Pack 1 is applied, you will be prompted to restart the system.
Do not deploy objects marked with software upgrades until the Galaxy nodes have been updated.
Platforms containing redundant engines must be updated together.
If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded
to Application Server 3.1 or Application Server 3.1 SP1 and InTouch 10.1.
< top of document >

Version 3.1 and 3.1 SP1
There is no migration required from version 3.1 to 3.1 SP1. You can migrate applications from the following
earlier versions of Application Server to version 3.1 and 3.1 SP1:

GR Node Migration
new version 3.1 SP1 schema. For versions earlier than 3.1, as listed in the preceding topic, data from the
existing schema is migrated to the new version 3.1 SP1 schema. Configured Wonderware Historian nodes are
saved in the new schema. The GR node migration fails if the GR node is used as a run4time node for another
GR. No migration is required from version 3.1 to 3.1 SP1.
< top of document >
Resolved Issues ' Application Server Version 3.1 SP1

Wonderware Application Server version 3.1 SP1 resolves the following issues. The issues are listed by their
Change Request number:
L00079297: Cannot import objects if the configuration version is older.
< top of document >
Known Issues ' Application Server Version 3.1 SP1

This section describes all known issues identified in Application Server Version 3.1 SP1.
error message is shown: "ArchestrA.Configuration.PackageServerNet.PackageServerNet
instance not properly disposed." The error message is informational. No action is required.
50 of 72 11/04/2011 08:56 AM
L00089829: When upgrading from Application Server version 3.1 to SP1, if you install the Service Pack
without first manually shutting down all platforms and engines, you may encounter
NMXService shutdown issues and the following errors might appear in the log:
7901 2/26/2009 10:56:24 AM 4076 4832 Error NmxSvc Unknown error 0xC0000005
(c0000005) raised.
7902 2/26/2009 10:56:24 AM 4076 4832 Error NmxSvc Unknown error 0xC0000005
(c0000005) caught at line 2128 in NmxControler.cpp (in Y:\AAMXCoreDev\src\NmxSvc\).
If these errors appear, you may disregard them. No further action is required. We
recommend following the steps outlined earlier in this Readme under the heading "Updating
Wonderware Application Server 3.1 with SP1".
Upgrades from Application Server versions 2.5 and 3.0 to version 3.1 SP1 do not encounter
this issue.
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.
warning message appears in the log: "Failed to patch the galaxy." The logged message applies
only to Galaxies from Application Server versions earlier than 3.1. No action is required.
Galaxies earlier than version 3.1 will be patched upon connection.
< top of document >

Documentation
1 Guide to ArchestrA Alarm n/a The description and syntax of the
Control, ShowGroupByHeader property need to
aaAlarmClientControl.pdf, be added to the Alarm Control
p.113 Properties section after the ShowGrid
property. The following descriptive
ArchestrA Alarm Control content needs to be added:
Help,
aaAlarmClientControl.chm, The ShowGroupByHeader property is a
"Alarm Control Properties" read4write Boolean property to show or
hide the column grouping label at the
top of the run4time Alarm Control in the
historical mode. You can set the
ShowGroupByHeader property to true
to show the label "Drag a column header
here to group by that column".
2 Guide to ArchestrA Alarm For Alarm Controls For Alarm Controls hosted by
Control hosted by Automation Automation Object templates or
aaAlarmClientControl.pdf Object templates or instances, you can specify one of the
p.27 instances, you can following alarm queries:
specify one of the
ArchestrA Alarm Control following alarm queries: \galaxy!<myArea.Tagname> to
51 of 72 11/04/2011 08:56 AM
Help, retrieve alarms and events from

aaAlarmClientControl.chm, \galaxy!myArea to the Area object hosting the
"Showing Current Alarms or retrieve alarms Automation Object template or
Recent Alarms and Events" and events from instance.
the Area object \galaxy!<me.Area>!
hosting the <me.Tagname>.* to retrieve
Automation alarms and events from the
Object template or Automation Object template or
instance. instance.
\galaxy!me to
retrieve alarms
and events from For more information on alarm queries,
the Automation see Alarm Queries.
Object template or
instance.
For more information on

absolute alarm queries,
see Alarm Queries in the
InTouch HMI Alarms
and Events Guide.
3 Creating and Managing n/a Add the following text after the first
ArchestrA Graphics User's paragraph:
Guide (aaGraphics.pdf),
"String Substitutions and If you perform a first4time string
Language Switching" substitution on an embedded symbol in
section, page 426 the primary language, that substitution is
shown in the secondary languages. You
Application Server Help can then perform a substitution in the
(IDE.chm), secondary language to create a string
"String Substitutions and substitution specific to the secondary
Language Switching" topic language.
If you perform a first4time string

substitution on an embedded symbol in a
secondary language, the substitution is
also applied to the primary language,
because the translated string that
previously existed for the primary
language is no longer valid. Because the
primary language value is changed in the
symbol, this string applies to all
secondary languages configured. You
can then perform a second substitution
in the primary language, which will
apply to all secondary languages except
the ones that have had a specific
substitution set.
If you perform a string substitution in a

secondary language with an existing
string substitution in the primary
language, the new substitution is applied
to the secondary language only.
52 of 72 11/04/2011 08:56 AM
192 44> Row number
4.
< top of document >

from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html After installing
Adobe Reader, double4click on a PDF file with your pointing device to view the book with Adobe Reader. You
can also open a book with the Adobe Reader Open command from the File menu. Application Server
installation instructions are located in the root folder of the Application Server installation CD as an online help
file. You can view these instructions by clicking the Installation Guide button in the Application Server
installation program. Product documentation is also available with Application Server online help.
Documentation Set
applications.
53 of 72 11/04/2011 08:56 AM
local hard drive.

1. Open Adobe Reader.

2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
3. Type the word or phrase that you want to search for in the Application Server books.
4. In the Where would you like to search area, select the option to search all PDF books.
5. If necessary, locate the Application Server version 3.1 PDF package located on your Wonderware CD or
on a network folder containing copiesoftheApplicationServerPDFbookfiles.
Afterproductinstallation,thesefilescanbefoundat:<driveletter>:\Program Files\ArchestrA\Framework
\Docs.
6. Click Search. Adobe Reader lists the Application Server books that contain a match for your search
criteria.
7. Click on the links to open the Application Server book to the topic containing the information that meets
your search criteria.
< top of document >
Wonderware Application Server Version 3.1

Readme
This document contains information about Wonderware Application Server version 3.1, including the new
ArchestrA Alarm and Trend Clients. Review this document for descriptions of new features, installation
requirements, and any known issues.
About This Release
54 of 72 11/04/2011 08:56 AM
Wonderware Application Server 3.1 includes the following enhancements and new features:
Advanced Communication Management

Advanced Communication Management minimizes network traffic and CPU usage of a DIObject or DAServer.
While the client application is running, scanning for an attribute value is suspended when the owning object no
longer appears in the running application. For example, Advanced Communication Management suspends
scanning for an object's attribute value when the operator minimizes the application window containing the
object. When the operator shows the window containing the object again, Advanced Communication
Management resumes scanning and the object's attribute value is updated in the application.
Time Propagation
Time propagation preserves the timestamp of process data obtained from source field devices like a PLC or
DAServer. The timestamp can be shown from visualization client applications like InTouch. Also, timestamps
are associated with the value and quality of data saved to the Wonderware Historian.
Improved Alarm Usability

Individual alarms of an object can now be selectively enabled, silenced, or disabled by an operator or a script.
Object4wide disablement prevails over the alarm mode of any individual alarm. For each individual alarm,
the object's alarm mode follows the most restrictive setting of either the individual alarm or the entire
object.
Individually disabling one type of alarm has no effect on any other types of alarms in an object. For
example, disabling a HiHi Level alarm of an object does not disable the object's Rate of Change alarm.
Individually disabling an alarm does not propagate downward through the object hierarchy to any other
assigned or contained objects. For example, disabling a HiHi Level alarm on Object A does not disable a
HiHi Level alarm on contained Object B.
Script Improvements
Two new methods are available for Application Server scripts. The LogDataChangeEvent() method logs
application change events to the Galaxy Historian. The SetAttributeVT() method can be used to set the value
and timestamp of an object attribute.
New History Attributes

From the IDE, you can configure the historical attributes of data saved to the Wonderware Historian. The
following list shows the new historical attributes introduced in version 3.1:
Description
Interpolation type (linear, stairstep, system default)
Rollover value (counter4mode retrieval)
Sample count
Rate deadband
Swinging door
Support for Late Data to the Historian

Application Server now includes late data support to save historical data that arrives with a timestamp earlier
than the Wonderware Historian's current time.
55 of 72 11/04/2011 08:56 AM
Alarm and Trend Clients

The ArchestrA Alarm Client and Trend Client are available from within the ArchestrA Symbol Editor.
The Trend Client:
Plots the real time values of ArchestrA application object attributes and InTouch tags.
Supports historical data from a Wonderware Historian or from InTouch history files (LGH). However, the
Trend Client can operate without these data sources.
Supports full and cyclic retrieval while getting data from the Wonderware Historian.
Supports faceplate displays created within the ArchestrA IDE graphics of InTouch version 10.1 or later.
The Alarm Client shows current and historical alarms and events.
The Trend Client and Alarm Client work with multilingual versions of InTouch applications and Wonderware
Application Server. The Trend Client and Alarm Client support the following languages:
English
German
French
Japanese
Simplified Chinese
A localization toolkit is available to add support to other languages and it is distributed separately. It also
includes a Microsoft Word version of the documentation.
< top of document >
MXAccess Toolkit Enhancements

The MXAccess Toolkit includes new methods to support Advanced Communication Management and time
propagation. Also, the MXAccess Toolkit can be used to write applications that can establish a supervisory
connection.
< top of document >

ArchestrA folders: (ensure subfolders of the listed directories are also excluded)
C:\Program Files\ArchestrA\
C:\Program Files\Common files\ArchestrA\
C:\Program Files\FactorySuite\ (may not exist in newer installations)
C:\Program Files\Wonderware\
C:\InSQL\Data\
C:\Documents and Settings\All Users\Application Data\ArchestrA From Application Server
Platform objects:
56 of 72 11/04/2011 08:56 AM

C:\Documents and Settings\All Users\Application Data\ArchestrA\ <SMC Logger Storage
file path>. The default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\ SQL Server
database files of type:
.mdf
.ldf
< top of document >

The following list shows the minimum computer hardware requirements to host Application Server version 3.1
components.
2 gigahertz (GHz) or faster dual core processor, or a 3 GHz or faster single core processor. A dual core
processor is strongly recommended for optimal performance.
Minimum of 2 gigabytes (GB) RAM. For Galaxies with more than 500 objects, 4 GB RAM is
recommended in the GR node.
Keyboard.
Development and Application nodes
2 GHz or faster processor.

Minimum 1 gigabyte (GB) RAM. For improved performance 4 GB RAM is strongly recommended.
Keyboard.
The hardware requirements for using the Alarm Client and Trend Client at run time are the same as for the
InTouch HMI version 10.1 run time. The Windows Vista operating system imposes hardware requirements that
may exceed the minimum requirements for Application Server version 3.1. If you intend to install Application
Server 3.1 on a computer running Windows Vista, see the following Microsoft web site for hardware
requirements: www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.mspx
< top of document >
57 of 72 11/04/2011 08:56 AM
Server version 3.1.
Operating Systems
Operating Systems
Windows Server 2003 Standard Edition SP2 is the recommended operating system for computers running
server components.
Windows XP SP3 is the supported XP version for this release.
Windows XP Professional SP3 is the recommended operating system for computers running client
components.
ArchestrA Run
Time
(Application
Node) (GR Node)
Windows Vista Business (See Vista Restrictions) x x x
Windows Vista Business SP1 (See Vista
x x x
Restrictions)
Windows Vista Enterprise (See Vista
x x x
Restrictions)
Windows Vista Enterprise SP1 (See Vista
x x x
Restrictions)
Windows Vista Ultimate (See Vista Restrictions) x x x
Windows Vista Ultimate SP1 (See Vista
x x x
Restrictions)
Windows Server 2003 Standard Edition SP2 x x x
Windows Server 2003 Enterprise Edition SP2 x x x
Windows Server 2003 Standard Edition R2 SP2 x x x
Windows Server 2003 Enterprise Edition R2 SP2 x x x
Windows XP Professional SP3 x x See Note 2.
Windows XP Tablet x
Notes:
1. The Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server operating
systems are not supported for Application Server version 3.1. An error occurs if you attempt to install or
upgrade Application Server version 3.1 on a computer running any edition of the Windows 2000
operating system.
2. The computer designated as the Galaxy Repository node can run on Windows XP Pro only as a
single4node configuration of Application Server. Windows Server 2003 is the recommended operating
system for the GR node.
3. You can run Application Server only on computers running a 324bit operating system. You cannot run
Application Server on a computer running a 644bit operating system.
4. The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of
Microsoft operating systems: English, Japanese, Chinese, German, and French. The Galaxy Repository is
58 of 72 11/04/2011 08:56 AM
also supported by the English, Japanese, Chinese, German, and French versions of Microsoft SQL Server
2005.

Microsoft SQL Server 2005 with SP2 is the only database supported by Application Server version 3.1. You
must use the Standard or Enterprise editions of SQL Server 2005. Neither the Compact, Express, nor the
Workgroup editions of SQL Server 2005 can be used as the Galaxy Repository.
SQL Server 2005 SP2 must be installed on the computer designated as the ArchestrA Galaxy Repository
node prior to installing Application Server.
2000 and Microsoft SQL Server 2005 installed.
memory.
TCP/IP must be enabled on the computer hosting a SQL Server 2005 database. The TCP/IP protocol
setting can be verified from the SQL Server 2005 Network Configuration under SQL Server
The Microsoft SQL Server 2005 login for BUILTIN\Administrators group must be present and enabled.

The following list describes other third4party software required for Application Server version 3.1.
Microsoft .NET Framework 3.5 Microsoft .NET Framework 3.5 must be installed on every computer that
hosts an Application Server version 3.1 component. The Application Server installation program halts if
.NET Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you
install .NET Framework 3.5. If you click Install Prerequisites, the installation program automatically
installs .NET Framework 3.5.
Microsoft Visual Studio 2005 Microsoft Visual Studio 2005 is required only by the MXAccess and

The software requirements for using the Alarm Client and Trend Client at run time are the same as for the
InTouch HMI version 10.1 run time. If you want to trend data from the Wonderware Historian (formally known
as IndustrialSQL Server), version 9.0 or later is required.
* InTouch 10.1
* Wonderware Application Server 3.1
* IndustrialSQL Server 9.0 (Wonderware Historian)
* ActiveFactory 9.2
* QI Analyst 8.1
< top of document >

This section describes specific restrictions when using the Windows Vista operating system with Application
Server and how to configure multiple Network Information Cards on a computer running Windows Vista.
59 of 72 11/04/2011 08:56 AM
Vista Restrictions
Application Server version 3.1 can run under Windows Vista SP1, Windows Vista Enterprise SP1,
Windows Vista Business SP1, or Windows Vista Ultimate SP1. The Windows Vista Home Basic and
Home Premium editions are not supported. The Windows Vista Business Edition is recommended for use
You must log on as a Windows Vista administrator to run Application Server version 3.1. You cannot run
Application Server as a Windows Vista standard user or power user.
The Windows Vista User Account Control (UAC) must be disabled when running Application Server.
Refer to Microsoft Windows Vista documentation for instructions to disable UAC.
When you disable Windows Vista UAC, you must restart the computer before attempting to install the
ArchestrA IDE or Wonderware Application Server. A Galaxy connection error occurs if you attempt to
install the ArchestrA IDE or Wonderware Application Server and you did not restart the computer after
you disabled the UAC.
Windows Vista does not support a traditional Application Server single4node configuration that includes
Wonderware Historian (formerly IndustrialSQL Server).
The Galaxy Repository is supported on Vista only for a single4node configuration of Application Server.
For multiple4node Galaxies, Windows Server 2003 is the recommended operating system for the Galaxy
Repository node.
If the computer that hosts the Galaxy Repository runs on Windows Vista, SP2 must be applied to SQL
Server 2005 installed on the same computer.
A computer running on Vista cannot be configured to be an alarm provider and also have InTouch
WindowViewer on the same computer configured to generate alarms. Only one of the two will function
properly as an alarm provider.
Windows Vista does not support NetDDE. ArchestrA Symbols that use the client layer when accessing
InTouch tags, and appear as a third4party client trying to access WindowViewer as a data server. As a
result, ArchestrA symbols cannot communicate with InTouch tags. Windows Server 2003 and Windows
XP Pro still support NetDDE.
Windows Vista security prevents started Windows services from interacting with desktop objects. When
Application Server 3.1 is installed on a computer running Vista, scripts do not run correctly if they include
the InTouch ActivateApp() and SendKeys() functions. Windows Vista prevents these functions from
interacting with desktop objects to start Windows programs or send keystrokes to these programs.
Using Multiple Network Interface Cards with Windows Vista

If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or
else a remote Vista node cannot connect to the Galaxy Repository node. A connection in Vista is a term used to
define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under
certain circumstances, the connection on your computer can change if, for example, the IP address on the
computer to which you are connected changes. Your computer's connection can be affected by external factors.
During computer startup, and each time a connection changes, Vista goes through an "Identifying" process to
determine which profile should be assigned to the connection. A profile is a collection of firewall settings that
can be applied to a connection. There are three profiles currently defined in Vista: "Domain", "Public" and
"Private".
The Domain profile is assigned automatically to a connection if a domain controller for the domain to
which the computer is a member is found on the connection.
The Public profile is designed to keep the computer from being visible to other computers on the network.
Network discovery is turned off for the Public profile.
The Private profile is used for a more trusted environment. Network discovery is turned on for a Private
profile. Firewall exceptions and rules can be created on any or all of these profiles.
This is important because the OS Configuration utility and the Vista Firewall utility apply their firewall
exceptions to the Domain and Private profiles only. As previously noted, you can specify which profile you
want assigned to a connection as long as that connection is not a Domain connection. This is done through the
"Network and Sharing Center". Click on the Network icon in the right side of the task bar and then click on one
60 of 72 11/04/2011 08:56 AM
of the networks that is shown. You can change a connection from a Public profile to a Private profile. The
firewall calls these settings "Profiles" but the network calls them "Location types." On computers using dual
NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. The
second NIC is typically assigned the Public profile. The first issue is that your entire computer (all connections)
is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was
assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Vista Firewall
utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the
second connection to the Private profile for any of the firewall exceptions to work. The second issue is that it
appears that a restart of your computer, or even a restart of a computer to which you are connected, can change
your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have
to change the connection back to the Private profile after each restart or a restart of the connected computer.
To avoid these NIC issues and prevent the "Identifying" process from taking place on a connection and
changing the assigned profile, certain items must be present in the definition of the connection. Follow the rules
below:
1. If you have only one NIC, no action is required. The profiles and firewall rules are
automatic.
2. If you have two NICs follow the actions below:
If the second NIC is not physically connected to anything (that means no wire
in it), no action is required. The profiles and firewall rules are automatic.
If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal
redundancy setup. Vista will identify this NIC and assign it a Private profile. If the NIC is not
configured, Vista will assign a profile of Public to this NIC and cause all of the Wonderware
product firewall exceptions to be deactivated on all NICs. For the NIC to be configured properly,
give it an IP address, sub net mask and gateway address. The gateway address can be the same as
the IP address. Usually these addresses will be the internal, non4routable addresses like 192.168.0.x
or the 10.x.x.x range.
If you have more than two NICs, make sure all connected NICs are configured with an IP address
and default gateway address and have been assigned a profile of private.
< top of document >

install Application Server version 3.1 components on meet third4party software requirements. You must install
Wonderware Historian 9.0 Patch 02 to use time propagation and late data from the Wonderware Application
Server to the Historian.
< top of document >
Upgrading to Version 3.1 from an Earlier Version of

Application Server
After the hardware and software requirements are met, you can upgrade to version 3.1 from the following
versions of Application Server:

61 of 72 11/04/2011 08:56 AM
Because the hardware and software requirements of Application Server 2.0 are not compatible with those of
Application Server 3.1, you cannot directly upgrade from Application Server 2.0. But, you can migrate
applications developed with version 2.0 Patch 01 to version 3.1.
Upgrade Limitations
The following limitations apply when upgrading existing Application Server components to version 3.1:
Before upgrading the GR node, all deployed nodes must be at the same version and there should be no
connected clients.
Before upgrading a visualization node, the InTouchViewApp AutomationObject should be shut down.
Uploading application run4time changes from a non4upgraded node is not permitted.
InTouch HMI must be upgraded to version 10.1 if it is installed on the same computer that has upgraded
Application Server version 3.1 components.
If Wonderware Historian is installed on the same computer with Wonderware Application Server, you
must install Wonderware Historian 9.0 Patch 02 before upgrading to Wonderware Application Server 3.1.
< top of document >

Version 3.1
You can migrate applications from the following earlier versions of Application Server to version 3.1:

GR Node Migration
The existing database schema is migrated to the new version 3.1 schema. Data from the existing schema is
migrated to the new version 3.1 schema. Configured Wonderware Historian nodes are saved in the new schema.
The GR node migration fails if the GR node is used as a run4time node for another GR.
< top of document >
Resolved Issues ' Application Server Version 3.1

Wonderware Application Server version 3.1 resolves the following issues. The issues are listed by their Change
Request number:
L00046232: In a UserDefined object, the Time Deadband option of a State alarm for a discrete field
attribute is similar to the Time Deadband option for an analog attribute in a limit alarm.
L00049932: You receive a "Could not resolve reference" error message for a .desc attribute when saving
an instance of a UDO object locked at the template level.
L00051580: After importing a Galaxy Load in the IDE with a hierarchy of Platforms, RedundantEngine,
and Area objects, the backup engine is deleted in IDE and the primary engine icon is
replaced with a normal engine icon. A Galaxy Load is performed with the "Replace Entire
Instance" option. The "Replace Entire Instance" option only deletes the objects that have no
62 of 72 11/04/2011 08:56 AM
hosted child objects.

L00054247: IDE performance slows significantly after you add more than 100 field attributes to a UDO.
L00057894: The calculated WinPlatform.CPULoadAvg value is incorrect for a platform running on a
computer with a dual core processor.
L00059983: Generating an alarm does not populate the user name or full name into the Alarm Record
reported to the Distributed Alarm System if the Galaxy is configured for Galaxy Security and
a user is logged on.
L00061480: When individual bits are manipulated within a field attribute of type integer using a script
within the same UserDefined object, only the value associated with one bit gets manipulated
instead of all the bits that are changed in the script.
L00063314: The Application Server Alarm Priority range is 0 to 999. The InTouch Alarm Priority Range
is 1 to 999. When 0 is entered as alarm priority from Application Server, an alarm priority of
1 is actually logged in alarm database and shown in the InTouch AlarmView summary
control.
L00064528: An object with a reference to "MyContainer" that is renamed and moved between areas
loses the binding reference and shows the warning "Could not resolve reference
MyContainer.XXX in attribute 4XX.XXX".
L00064546: An InTouch client application running on a non4upgraded remote node cannot see an alarm
generated on another remote node that has been upgraded with Application Server.
L00066957: Cannot deploy any object if the computer's Windows DEP configuration is set to
/noexecute=AlwaysOn.
L00067495: Migrating an Application Server version 2.5 Galaxy with FMM objects fails with errors, and
the migration process hangs in an infinite loop.
L00067697: A large cascade deploy does not complete because a Redundant engine was stopped by the
Bootstrap while it was starting up on a remote node.
L00068078: A cascade deploy of over 1000 objects were deployed off scan, but marked as undeployed
without error messages.
L00068433: If you shut down the Wonderware Historian and then immediately restart the computer,
frequent disconnects/reconnects occur for MDAS clients, such as the Wonderware
Application Server. This fix requires Wonderware Application Server 3.1 and Wonderware
Historian 9.0 Patch 02.
L00069976: Application Server scripts calculate Quality incorrectly for expressions containing Boolean
AND or OR operators.
L00070352: A radio button graphic shows only one button with a title Unresolved Reference the first time
the IDE is started.
L00070995: Deploying or undeploying a GRPlatform of over 170 remote nodes takes several hours and
error messages are written to the log.
L00071061: Backing up a large Galaxy fails because of insufficient disk space without a warning message
written to the logger.
L00071079: When uploading run4time changes for an object with a symbol, the revision version does not
remain consistent with the configuration version.
L00071206: Users can acquire User Configuration permissions with any security mode.
L00071647: The OnShow script in an ArchestrA graphic appears to run, but the script does not set an
attribute. (See SR14811879)
63 of 72 11/04/2011 08:56 AM
L00071843: ObjectViewer does not handle a returned WriteStatus of "Pending" properly because it does
not wait for the final SetReponse() return message and the dialog box normally shown for
writes that fail does not appear.
L00072015: When an FSGateway is deactivated on an ApplicationObject server node, the SMC and
ObjectViewer become unresponsive, and platform communications are disrupted.
L00072074: Communication failures during a cascade deployment of a large number of objects cause the
deployment to fail.
L00072300: When a client control is deleted and a new version of the client control is imported from a
remote IDE, an ArchestrA Symbol referencing the client control will show Version 1 on the
remote IDE and Version 2 on the Galaxy Repository IDE. This is a mismatch of versions.
(See SR103112086
L00072450: An attribute value from the CheckedInPackage of an object using IGalaxyFX interface
cannot be obtained because the Check Out and then Check In operations fail when done for
an instance of custom ArchestrA object.
L00073495: A Galaxy backup does not work correctly if the ArchestrA IDE is not installed on the same
computer.
L00073550: The graphic element reference list is incomplete, or it is corrupted. The error message "Failed
to get Graphic element reference list" appears in the SMC Logger. (See SR23515471)
L00074841: An ApplicationObject fails to deploy when an InternationalizedString Array in the object is
modified using GRAccess.
L00075206: Customized graphic text is lost after group change.(See SR14811926)
L00075453: A WinPlatform object Remote Activation Failure error occurs when you attempt to deploy
the object to a node with a name greater than 15 characters.
L00075663: When Application Server and Factelligence are installed together, users can successfully log
on from the Configure Galaxy dialog box without a valid password or user ID.
L00075763: Custom property links for ArchestrA symbols do not accept the following special characters
that can be used in InTouch tag names: _ (underscore), 4 (hyphen), $ (dollar), % 4 (percent),
and &. 4 (ampersand).
L00075800: MX References do not start in scripting; .InputSource in ArchestrA Graphics does not start in
scripting. The MX References do work on display the link and in a Custom Property. (See
SR15010810)
L00075917: A Galaxy load operation that uses the Only Update Changed Attributes option forces all
modified objects to a checked out state.
L00076426: An exception occurs while checking in a derived template with ArchestrA graphic symbols
and more than 1000 instances.
L00076900: Warning "Could not find embedded graphics" appears after a template and its instances of a
Galaxy are exported as an aaPKG file, and are then re4imported into a new Galaxy. (See
SR33430263)
L00077680: Watch window does not always update with the current Float Array values after copying
values from another Float Array or changing values from the ObjectViewer
L00078407: Exporting the contents of the Galaxy Repository fails with warning messages written to the
logger.
L00079430: Removing a string from a symbol with Value Display Animation in a primary language also
removes the strings in secondary languages.
64 of 72 11/04/2011 08:56 AM
L00081739: The Graphic toolbox pop4up window and the Graphics tab preview window thumbnails show
"not found" when an application object instance containing symbols with date time picker is
imported in a new Galaxy.
L00087227: A Wonderware Application Server 3.0 Galaxy with an imported InTouchCompactApp
aaPKG file to Wonderware Application Server 3.1, errors are logged in the SMC Logger.
< top of document >
Known Issues ' Application Server Version 3.1

This section describes all known issues identified in Application Server Version 3.1. The known issues are
grouped by function.
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 re4deployed.

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. This issue is discussed in CR L00077833.
Before installing Wonderware Application Server, 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/en4us/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.
65 of 72 11/04/2011 08:56 AM
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 non4upgraded IDE node (earlier than
ApplicationServer 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."
L00082886: Area objects are not deployed after performing a cascade deploy of a Galaxy migrated from
version 3.0 to version 3.1 of Application Server with Vista as the operating system.
Perform the following as a workaround.
1. Click Start, then Run.

The Run dialog box appears.
2. In the Open field, type OptionFeatures.exe
3. Click OK.
The Windows Features dialog box appears.
4. Expand the following:
* Microsoft message Queue (MSMQ) Server
* Microsoft message Queue (MSMQ) Server Core
5. Place a check to the left of:
* Microsoft message Queue (MSMQ) Server
* Microsoft message Queue (MSMQ) Server Core
* MSMQ Active Directory Domain Service Integration
* MSMQ HTTP Support
*MSMQ Triggers
* Multicasting Support
* MSMQ DCOM proxy
6. Click OK.
The Windows Features dialog box closes.
7. Deploy the Automation Objects.
L00083270: Spaces are not imported as part of the translation for the selected language.
L00083828: There are inconsistencies between the selected language and the strings that are shown.
L00083909: InTouch applications receive Quality Status and Locale information from the deployed
Galaxy. InTouch applications cannot receive data from an undeployed Galaxy.
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 964dpi.
Wonderware does not support running the product in DPIs other than 96 DPI.
L00086625: When you upgrade nodes from Wonderware Application Server 3.0 Patch 03 to 3.0 SP2, the
following warning from msiexec appears: "GetArchestrAInstallPath(): Failed to Read the
Registry ArchestrA install path Key".
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 file4lock within the CheckOut
folder. You should not attempt to check4in the InTouchViewApp.
66 of 72 11/04/2011 08:56 AM
Fix the file4lock issue, and perform the "undo4checkout" 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.
ArchestrA Alarm Client

This section lists current issues that remain in the ArchestrA Alarm Client (Control).
L00080966: Unable to browse all supported methods and properties from the Alarm Control's Element
Browser. Also, many additional unwanted methods and properties appear in the Element
Browser. This is due to limitation from the ArchestrA framework. Workaround: Use the
Guide to the ArchestrA Alarm Control as reference. Chapter 4 "Scripting the Alarm Control"
contains all supported methods and properties including syntax and in most cases examples.
L00082738: Query filters added at run time are not saved if you switch back to WindowMaker.
Workaround: Export the query filters you create at run time to an XML file. After switching
back to WindowMaker, import the query filters from the XML file.
L00084764: If you change the Query String of the Default Query after adding filtering criteria using the
Query Filter editor, then the additional filtering details are removed.
L00085789: It is not possible to hide more than 300 single alarm records. If you need to hide a larger
number of alarms, consider hiding the group or priority instead. Hiding one group instead of
many individual alarm records in that group only creates one hidden item in the Hidden
Alarms dialog box.
L00086092: It is not possible to hide any alarm records if the alarm query is configured for a large number
of providers. If the alarm query is too long, when you attempt to hide alarms, a message is
shown in SMC Log Viewer and a message "The maximum limit of hidden alarms has been
reached" appears. To avoid this problem, consider using multiple Alarm Controls or switching
the alarm query between several sets of alarm providers.
L00086127: The scriptable properties and methods to hide alarms continue to operate when the alarm
control is in the historical mode, although the historical alarms are not hidden. Acting on
historical alarms with a hide request should be avoided. This can cause the control to use
excessive CPU.
67 of 72 11/04/2011 08:56 AM
In the script that hides alarms, set the client mode to "1" or "2" ("Current Alarms" or "Recent
Alarms and Events"), before performing a hide action.
L00088079: Portions of the Symbol Editor are shown in black when the Embedded Alarm Control 4 Edit
Animations 4 Colors Configuration dialog box opens. This is observed only on Windows XP
and Windows 2003 with Display Properties configured to use the 'Windows XP' Theme.
ArchestrA Trend Client

This section describes all known issues identified in the Trend Client.
L00082107: When you import the Trend Client package (.aaPKG) into the IDE, some unwanted warning
messages appear in the logger.
L00085245: When you configure the Pen Type (Pen.TrendType)as 'Auto' and the default value of
Historian is not available, the Trend Client generates Plot type as line during run time,
regardless of the data type (real or integer).
L00086210: If you use a relative reference for a custom property in the pen configuration, the Trend
Client does not resolve the pen configuration during run time. The Trend Client supports
custom properties for absolute references, but does not support custom properties for relative
references.
L00086285 The Trend Client does not copy any background image files to another node and, therefore,
: does not show a configured plot image on a client node. To view the plot image on a client
node:
Use the image file only in a single4node application

Copy the image file to the same file path on each client node
Place the image file on a UNC share and use this shared path while configuring the
Trend Client
L00087611: The Element Browser or Events page of the Trend Client shows a number of unwanted
events and properties. Also, the Element Browser or Events page does not allow you to
browse all the supported methods, properties, and events. This occurs because of a limitation
of the ArchestrA framework. For information about all the supported methods, properties,
and events, see the Trend Client documentation.
L00087617: The AddPen method does not work when you specify a relative reference or an absolute
reference as a history source name. You must specify the value for the history source name
in the script if you add a pen using a script.
L00087683: A data loss occurs when you initialize the trend with history data and refresh the trend chart.
top of document >

The following table lists all documentation corrections to Application Server 3.1 documentation.
Documentation
68 of 72 11/04/2011 08:56 AM
1 Application Server User's n/a Add the following paragraphs for

Guide, IDE.pdf, "Saving the Date Timestamp as
"Saving the Date Timestamp Historical Data" after the last paragraph:
as Historical Data," page
154.
Application Server Help,
IDE.chm,
"Saving the Date Timestamp
as Historical Data" topic
2 Guide to ArchestrA Alarm n/a The description and syntax of the
Control, ShowGroupByHeader property need to
aaAlarmClientControl.pdf, be added to the Alarm Control
p.113 Properties section after the ShowGrid
property. The following descriptive
ArchestrA Alarm Control content needs to be added:
Help,
aaAlarmClientControl.chm, The ShowGroupByHeader property is a
"Alarm Control Properties" read4write Boolean property to show or
hide the column grouping label at the
top of the run4time Alarm Control in the
historical mode. You can set the
ShowGroupByHeader property to true
to show the label "Drag a column header
here to group by that column".
3 Guide to ArchestrA Alarm For Alarm Controls For Alarm Controls hosted by
Control, hosted by Automation Automation Object templates or
aaAlarmClientControl.pdf Object templates or instances, you can specify one of the
p.27 instances, you can following alarm queries:
specify one of the
ArchestrA Alarm Control following alarm queries: \galaxy!<myArea.Tagname> to
Help, retrieve alarms and events from
aaAlarmClientControl.chm, \galaxy!myArea to the Area object hosting the
"Showing Current Alarms or retrieve alarms Automation Object template or
Recent Alarms and Events" and events from instance.
the Area object \galaxy!<me.Area>!
hosting the <me.Tagname>.* to retrieve
Automation alarms and events from the
Object template or Automation Object template or
instance. instance.
\galaxy!me to
retrieve alarms
and events from For more information on alarm queries,
the Automation see Alarm Queries.
Object template or
instance.
For more information on

absolute alarm queries,
see Alarm Queries in the
InTouch HMI Alarms
and Events Guide.
4 Creating and Managing n/a Add the following text after the first
ArchestrA Graphics User's paragraph:
Guide (aaGraphics.pdf),
"String Substitutions and If you perform a first4time string
69 of 72 11/04/2011 08:56 AM
Language Switching" substitution on an embedded symbol in

section, page 426 the primary language, that substitution is
shown in the secondary languages. You
Application Server Help can then perform a substitution in the
(IDE.chm), secondary language to create a string
"String Substitutions and substitution specific to the secondary
Language Switching" topic language.
If you perform a first4time string

substitution on an embedded symbol in a
secondary language, the substitution is
also applied to the primary language,
because the translated string that
previously existed for the primary
language is no longer valid. Because the
primary language value is changed in the
symbol, this string applies to all
secondary languages configured. You
can then perform a second substitution
in the primary language, which will
apply to all secondary languages except
the ones that have had a specific
substitution set.
If you perform a string substitution in a

secondary language with an existing
string substitution in the primary
language, the new substitution is applied
to the secondary language only.
192 44> Row number
4.
70 of 72 11/04/2011 08:56 AM
< top of document >

from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html After installing
Adobe Reader, double4click on a PDF file with your pointing device to view the book with Adobe Reader. You
can also open a book with the Adobe Reader Open command from the File menu. Application Server
installation instructions are located in the root folder of the Application Server installation CD as an online help
file. You can view these instructions by clicking the Installation Guide button in the Application Server
installation program. Product documentation is also available with Application Server online help.
Documentation Set
applications.
Creating and Managing ArchestrA Graphics User's Guide . Explains how you create and manage
graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment
(IDE).
local hard drive.

71 of 72 11/04/2011 08:56 AM
1. Open Adobe Reader.

2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
3. Type the word or phrase that you want to search for in the Application Server books.
4. In the Where would you like to search area, select the option to search all PDF books.
5. If necessary, locate the Application Server version 3.1 PDF package located on your Wonderware CD or
on a network folder containing copies of the Application Server PDF book files. After product
installation, these files can be found at: <drive letter>:\Program Files\ArchestrA\Framework\Docs.
6. Click Search. Adobe Reader lists the Application Server books that contain a match for your search
criteria.
7. Click on the links to open the Application Server book to the topic containing the information that meets
your search criteria.
< top of document >
© 2010 Invensys Systems, Inc. All Rights Reserved.
72 of 72 11/04/2011 08:56 AM

Wonderware Application Server 3

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Wonderware Application Server 3

Diunggah oleh

Hak Cipta:

Format Tersedia

Wonderware Application Server 3.1 SP3 ReadMe https://wdnresource.wonderware.com/support/patchfixes/1/AppSv31S...

Wonderware Application Server 3.1 SP3 Readme

Wonderware Application Server 3.1 SP3 Information

About Wonderware Application Server 3.1 Service Pack 3 (SP3)

Antivirus Software Exclusions

Minimum Hardware Requirements

Software Requirements and Compatibility

Installing Wonderware Application Server 3.1 SP3

Upgrading to Version 3.1 SP3 from an Earlier Version of Application Server

Resolved Issues 4 Wonderware Application Server 3.1 SP3

Known Issues 4 Wonderware Application Server 3.1 SP3

Wonderware Application Server Documentation Issues

Wonderware Application Server Documentation

< top of document >

About Wonderware Application Server 3.1 SP3

Windows 7 Professional, 32/644bit (emulation mode) versions

< top of document >

Minimum Hardware Requirements

Galaxy Repository (GR) Node

Development and Application Nodes

recommended. The Intel Itanium 2 processor is not supported.

< top of document >

Software Requirements and Compatibility

Wonderware Application Server Components

Windows Vista SP2, Business, 644bit (emulation)

Operating System Notes:

Support for Windows Operating System User Account Control (UAC)

In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag

Wonderware® InTouch® HMI 10.1 SP3

SQL Server Requirements

SQL Server Rights Requirements

Other Software Requirements

Using Wonderware Application Server with Windows 7 and Windows

To use the Server Manager

To use the Windows Power Shell

1. Click Start, highlight All Programs and select Accessories.

< Top of document >

Installing Wonderware Application Server

< Top of document >

Upgrading to Version 3.1 SP3 from an Earlier

Version 2.1 Patch 02

Wonderware Application Server 3.1 SP3 Upgrade Requirements

Migrating Applications to Wonderware Application Server Version 3.1

Version 2.0 Patch 01

< Top of document >

Resolved Issues ' Wonderware Application Server

< top of document >

Known Issues ' Wonderware Application Server

1. The GR4node is a member of DomainA.

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

L00104907: Tooltip animations are not working for WCC controls.

VMware, Inc. vCenter Lab Manager 4.0 (4.0.1.1233)

VMware Tools = Upgraded Version (add/remove programs) 8.0.2.14744

< top of document >

Wonderware Application Server Documentation

Item Location of Existing Change

1. When the OPC Client starts, it will

not cause a disconnect followed by a

When a connection fails, OPC Client will try to

< top of document >

Wonderware Application Server Documentation

Searching Application Server Books with Adobe Reader

To search for information across all Application Server books simultaneously