Просмотр исходного текста страницы Application Server 2012 patch 01 (3.5 patch 01)

<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Wonderware Application Server 3.5 Patch 01 Readme</title>

<meta name="GENERATOR" content="MSHTML 8.00.6001.18812"></head>
<body alink="#0000ff" link="#0000ff" bgcolor="#ffffff" vlink="#800080">
<p></p>
<p></p>
<!--Wonderware Styles-->
<style type="text/css">
h1 {color: rgb(255, 255, 255); font-weight: bold; font-family: Verdana; font-size: 18pt; background-color: rgb(195,214,3); }
h2 {color: rgb(195,214,3); font-weight: bold; font-family: Verdana; font-size: 14pt}
h3 {color: rgb(195,214,3); font-weight: bold; font-family: Verdana; font-size: 13pt}
h6 {color: rgb(255, 255, 255); font-weight: bold; font-family: Verdana; font-size: 24pt; background-color: rgb(195,214,3); } 
p {margin-left: 2px; color: black; font-family: Verdana; font-size: 12px; margin-bottom:4pt}
p.right {text-align: right}
ul {margin-left: 20px; font-family: Verdana; font-size: 12px}
ol {margin-left: 20px; font-family: Verdana; font-size: 12px}
td {color: black; font-family: Verdana; font-size: 12px}
hr {color: rgb(195,214,3); width: 100%; height: 1px; font-family: Verdana; font-size: 12px; text-align: right}
title {color: rgb(0, 0, 0); text-align: center; font-family: Verdana; font-size: 22px}
li {color: rgb(0,0,0); list-style:inherit; font-family: Verdana; font-size: 12px; line-height: 14pt; margin-bottom:4pt; margin-left: 2px;}


.note {color: black; font-family: Verdana; font-size: 12px; font-weight: bold}
.center {text-align: center}
.bold {font-weight: bold}
.indent {margin-left: 12px; color: black; font-family: Verdana; font-size: 12px; margin-bottom:4pt}
</style>



<meta content="MSHTML 6.00.2900.3132" http-equiv="GENERATOR"><basefont size="12px" face="verdana, arial, tahoma, helvetica">
<div style="TEXT-ALIGN: center"><!--Start of the Visible ReadMe--></div>
<h1 class="center">Wonderware Application Server 2012 (version 3.5) Patch 01 Readme</h1>
<p>Last revision: 04/24/2012 </p>

<p>This document includes information about Wonderware<sup>®</sup> Application Server 2012 (version 3.5) Patch 01. It updates the previous Readme files included with Application Server 2012 (version 3.5).</p> 
<p></p>

<br>
<span style="FONT-FAMILY: Verdana; COLOR: red; FONT-SIZE: 24px; FONT-WEIGHT: bold">Important!</span><br>

<ul>
<li><b>Installation</b> - You need to install Application Server 2012 (v3.5) before installing this patch. Refer to the 
<a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#2012 Important">"Important"</a> section for Application Server 2012 (v3.5) to 
ensure that all the requirements are met for that version before upgrading to the patch, and for other Application Server information.<p></p>

<p>If you use SQL Server 2008 SP1, 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.</p></li>

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

</p><p>If you installed the Application Server 3.5 <b>wwcdi.dll</b> Hot Fix which was released after 02/29/2012, the Hot Fix must be reverted back to the original <b>wwcdi.dll</b> before installing Application Server 2012 (v3.5) Patch 01.
</p><p></p>

<li><b>UAC</b> - Disable UAC before installing Wonderware Application Server 2012 (v3.5) and InTouch HMI 2012 (v10.5), applicable for Windows Vista and above operating systems.</li>

<li><b>Coexistence</b> - If Wonderware Application Server and the InTouch HMI are installed on the same node, they both must be upgraded to Application Server 2012 (v3.5) Patch 01 and InTouch HMI 2012 (v10.5) Patch 01, respectively.</li>


<!--<li><b>Alarm DB Logger</b> - The Alarm DB Logger runs as a service in all operating systems. 
In prior releases that supported Vista, Windows 7, or Windows Server 2008, the Alarm DB Logger could not be enabled to run as a service. 
The issue has been corrected, and the restriction has been removed.</li>

<li><b>Language Switching</b> - Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching 
functionality must always be modified on the same language operating system and InTouch language version, on which it was initially developed. 
Attempts to modify these components in a different language operating system or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system 
language that is different from the originally developed language are supported. Refer to Known Issues CRs L00088974, L00088993, and L00088998.</li>

<li><b>Restoring a CAB</b> - 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 such a restore initializes, and the progress dialog box quickly displays 100% completion of restoring the database, 
but the Galaxy.cab restore operation does not complete, and no Galaxy is created. When you then start the IDE, the Galaxy will be blank.</li>

<li><b>Antivirus Exclusions</b> - The antivirus software exclusions list has been updated. 
Click this <a href="#Antivirus_Software_ExclusionsSP2">Antivirus Software Exclusions</a> link for details.</li>

<li><b>Remote Sessions</b> - 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 <a href="#Terminal Services Behavior">Terminal Services Behavior</a> link for further information 
about terminal services behavior changes.</li> 

<li><b>Multiple Network Cards</b> - Using multiple NICs in Windows Server 2008 R2, as with Windows Vista, requires specific configuration. 
Click <a href="#Win2008_NICs">Using Multiple NICs in Windows 2008 </a> for further information 
about using multiple NICs in Windows Server 2008 R2.</li>

<li><b>License Utility</b> - Starting the ArchestrA Licensing Utility from an existing License CD may not work on a 64-bit operating system. 
Start the utility from the installed shortcut instead.</li>

<li><b>Operating System Restrictions</b> - All the restrictions applicable to Windows Vista and Windows Server 2008 are also applicable to Windows 7 and Windows Server 2008 R2, respectively.</li>

</b>!-->
</ul>

<br><br><br>


<h3>Wonderware Application Server 2012 (v3.5) Patch 01 Information</h3>

<!--<p> <a href="#Min H/W reqmnts_Patch01">Hardware Requirements</a>
<p><a href="#S/W Reqmts & Compatibility_Patch01">Software Requirements and Compatibility</a>!-->
<p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#A - WAS 3.1 SP3">Applying Patch 01 to Wonderware Application Server Version 2012 (v3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#RI- WAS 3.1 SP3_Patch01">Resolved Issues -  Wonderware Application Server 2012 (v3.5) Patch 01</a>
<!--<p><a href="#KI-WAS 3.1 SP3_Patch01">Known Issues - Wonderware Application Server 2012 (v3.5) Patch 01</a>!-->
</p><p></p>
<br><br>



<h3>Wonderware Application Server 2012 (v3.5) Information</h3>

<a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#About Wonderware Application Server 3.5">About Wonderware Application Server 2012 (version 3.5)
</a> 
<p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Antivirus Software Exclusions">Antivirus Software Exclusions</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Minimum Hardware Requirements">Minimum Hardware Requirements</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Software Requirements and Compatibility">Software Requirements and Compatibility</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2">Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2</a> 
</p><p><!--<A 
href="#Installing Wonderware Application Server 3.5">Installing Wonderware Application Server 3.5
</A> -->
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Upgrading to Wonderware Application Server 3.5">Upgrading to Wonderware Application Server 2012 (version 3.5)</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Migrating to Wonderware Application Server 3.5">Migrating to Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Resolved Issues - Wonderware Application Server 3.5">Resolved Issues - Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Known Issues - Wonderware Application Server 3.5">Known Issues - Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Wonderware Application Server Documentation Issues">Wonderware Application Server Documentation Issues</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Wonderware Application Server Documentation">Wonderware Application Server Documentation</a>
</p><p></p>
<br><br>




<!--<h1><a name="Min H/W reqmnts_Patch01"></a>Hardware Requirements </h1>
<p>The hardware requirements for this patch are the same as for the previous release.</p>
<p></p>
<br><br>
<h1><a name="S/W Reqmts & Compatibility_Patch01"></a>Software Requirements and Compatibility</h1>
<p>The software requirements for this patch are the same as for the previous release.</p> 
<p></p>
<br><br>!-->


<h1><a name="A - WAS 3.1 SP3"></a>Applying Wonderware Application Server 2012 (v3.5) Patch 01</h1>

<p>Close any anti-virus programs running on the computer before you update 
Wonderware Application Server with Patch 01. </p>
<p>Apply this patch <span class="bold">only</span> to Application Server 2012 (v3.5). You can check the version number in the Control Panel. See the <span class="bold">Add or Remove Programs</span> 
section under Wonderware Application Server.</p>

<p><span style="FONT-WEIGHT: bold; FONT-SIZE: 18px; COLOR: red; FONT-FAMILY: Verdana">Important! 
</span></p>
<p><b>This patch must be installed on all Wonderware Application Server nodes. On nodes where both Application Server and InTouch are installed, 
you must install Application Server 2012 (v3.5) Patch 01 and InTouch 2012 (v10.5) Patch 01 in order for them to coexist.</b></p>
<p><b>Note:</b> For all configuration and installation operations, Windows User Account Control (UAC) must be disabled 
or privileges must be elevated to the required level.
</p><ul>
  <li><b><font color="red">Before installing the patch, ensure you have created known good backups of all installed Galaxies.</font>
  </b> 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 <span class="bold">Action</span> menu, click <span class="bold">Backup</span>. Follow the prompts to complete the backup operation 
  for each Galaxy.</li> 
  <li>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. </li>
  <ul>
    <li>An ArchestrA IDE node still at version 3.5 cannot connect to a remote GR node updated with Patch 01. </li>
    <li>An ArchestrA IDE node updated with Patch 01 cannot connect to a remote 
    GR node still at version 3.5. </li></ul>
  <li>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. </li>
  <li>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.</li>
  </ul>
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; Top of document &gt; </a>
</p><hr>




<h1><a name="RI- WAS 3.1 SP3_Patch01"></a>Resolved Issues - Wonderware Application Server 2012 (v3.5) Patch 01</h1>
<p> Wonderware Application Server 2012 (v3.5) Patch 01 resolves the following issues listed by their Change Request number:
</p><p>
<table style="TEXT-ALIGN: left" border="0" cellspacing="1" cellpadding="5" width="760">
<tbody>

<tr>
<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00108559:</span></td>
<td> <b> HF CR L00103059 SR 103119397 HF 1889:</b>  
A WinPlatform faceplate deployed in an InTouchViewApp on Windows Server 2008 did not display correctly when opened in WindowViewer. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112570:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00114258 SR 19417937:</b> After an alarm is acknowledged, the user-defined language identifier is prefixed to the Alarm Comment field. With this prefix in the alarm comment, the alarm comment language switching stopped working.    
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00114445:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00113225 SR 42410006:</b> The security audit (OPR) event description exceeds 271 characters in length. This caused the insert to database WWALMDB Events table to fail.    
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115668:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00114748 SR 12912503:</b> Performing a new deployment of an InTouch Application caused ArchestrA Graphics corruption.     
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115684:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00115247 SR 38231630:</b> Archestra Alarm Client Control columns ordered at design time did not appear in the same order at run time, but instead used standard Time ordering.     
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115740:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00115251 SR 19418048:</b> Deploying a Managed InTouch Application required a long time, from a few minutes to more than ten minutes.      
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116358:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00115954 SR 19418036:</b> Opening an ArchestrA Graphic in the IDE Graphic Editor required several minutes.       
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116434:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00116176 SR 19417966:</b> 
After importing SmartSymbols into ArchestrA Graphics, a number of SmartSymbol elements, including scripts, were missing in the ArchestrA Graphic.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116508:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L0011841:</b> Writing to a secured array attribute using the SignedWrite function resulted in a .NET error. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116979:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00116747 SR 40212165:</b> PostCheckIn event failed to fire when importing newer version base templates into the Galaxy, causing derived objects to fail to update. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116980:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00116751 SR: 34211277:</b> The TempDB Log file grew to maximum size and aaGR froze when importing an object to the Galaxy. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117300:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L0016863 SR 34211168:</b> Galaxy backup failed when the C:\ drive had insufficient space even though the backup directory was located on a different drive. Edit the Registry to specify a new String value of type REG_SZ for the temporary files location for the Galaxy Backup/Restore operation, <b>TempRepositoryPath</b>, at one of the following Registry locations:
<ul>
<li>32-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\GR\
</li><li>64-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\GR</li>
</ul>
Example: TempRepositoryPath = D:\Temp<br>
To reset to the default location, delete the <b>TempRepositoryPath</b> or set its value to blank.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117310:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> A Redundant Device Integration (RDI) item stayed in Initializing quality or became stuck in Bad quality, even though the DI source showed Good quality 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117320:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117071:</b> Importing an exported file on Application Server in ArchestrA System Platform exhibited problems with the stored procedure "internal_set_host_association". 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117366:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117307 SR 33811863:</b> Renaming a deployed or undeployed object containing ArchestrA Graphics required almost five minutes, caused the GR process to become unresponsive, and caused aaBootstrap and aaEngine to auto restart. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117422:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> When the SignedAlarmAck function is used, it resulted in lower case "Ack" in the Alarm Client AlarmComment field whereas Alarm Client acking an alarm results in upper case "ACK" text in the Alarm Client AlarmComment field.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117494:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> A popup dialog displayed when the SignedAlarm function was used to ACK an alarm with the parameters "ackCommentIsEditable" and "Signature_Reqd_for_Range" set to False. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117497:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00116948:</b> On a machine that had high number of Cores (8 - 16), bulk operations did not use all the available cores. To use the available CPU cores, add the DWORD <b>CheckinThreads</b> to the Registry in one of the following locations:
<ul>
<li>64-bit operating systems: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\GR] 
</li><li>32-bit operating systems: [HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\GR] </li>
</ul>
For example: "CheckinThreads"=dword:00000004  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117501:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> The Operator Node field or column in the Alarm Viewer Control did not show the expected node name when accessing an ArchestrA System Platform node via remote desktop (RDP) to Ack an alarm. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117541:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117189 SR 33811846:</b> Updates to a UDA reference did not show in Object Viewer in a redundant system after failover to backup then switching back to primary. Instead, the UDA reference took the redundant backup value - the original value before deploying changes.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117550:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> The SignedAlarmAck Alarm Acknowledgement dialog was inconsistent with the appearance and size of the AlarmClient AckAlarm dialog. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117558:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117428 SR 43110090:</b> After deploying an object from the derivation view, an asynchronous script, working correctly before the deploy, did not execute again even when its condition was evaluated to True (expression type was WhileTrue). 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117607:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00115843:</b> Creating an instance of a $U_HCCF_Txxx template containing 57 objects required excessive time, 50 minutes or more to create one instance. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117700:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00114964 SR 15316256:</b> Deployment of a platform on a Windows 7 64-bit operating system required 18 minutes.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117885:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117579 SR 20114109:</b>  Could not authenticate a user against the local active directory because Application Server tried to  authenticate against the primary domain controller which was blocked by a firewall. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117914:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117593 SR 103122826:</b> Filtering an object by contained name in the ArchestrA Graphic Editor when doing "select alternate instance" returns a blank window even if there is an object with the name that contains the filter.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117988:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117820:</b> Alarm data was not distributed to the InTouch Alarm Providers after the engine was shutdown and restarted by the Bootstrap as the engine was not responding.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118112:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00117292 SR 37112243:</b> RDI is connected to two DDESuitelinkClient objects. If the active DDESL object is set offscan, RDI connection status goes to OffScan. If DDESL object is put back onscan, RDI shows disconnected and never goes back to connected status until the RDI is redeployed.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118126:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00116889 SR 103121095:</b> OPC quality 224 through 255 are incorrectly represented as BAD state. This BAD state information is also logged to Historian. According to the OPC Specification, all quality values above 192 should be GOOD.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118241:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 38910352:</b> The Platform stopped communicating with partner; messageChannel library stuck sending messages. 
Antivirus drivers appeared to be blocking the messages. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118285:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> An InTouchViewApp deployment resulted in an OutOfMemory error.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118398:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118304 SR 38910349:</b> In the Object Editor clipboard, copying and pasting from one symbol to another, embedded symbols were pasted with the default name "EmbeddedSymbolN", instead of keeping the original name as in Application Server 3.1.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118441:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118411:</b> Galaxy Import and Galaxy Load failed with error message, "The Tagname Template does not exist in the Galaxy. Import the template and then do Galaxy Load." The Galaxy Load failed when the keyword "template" was in the exported object .csv file.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118561:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00109815 SR 40210818 HF 2314:</b> When one of the redundant AOS shut down, one out of ten times, some AppEngines did not fail over. From the SMC log, engines that did failover switched to Backup Standby status for no apparent reason. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118617:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118452. SR 29710009:</b> Object template(s) and instance(s) corruption occurred in software issues such as object quarantine and set attribute failures when a package exported from one Galaxy is imported into another Galaxy on-site. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118863:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118505, L00098459 SR 103123076:</b> Undeploying an RDI object whose backup DI source was wrongly configured with an invalid PLC IP address, and with a large number of subscriptions (4K+ items) resulted in an Access Denied error in the RDI and Scan Group.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119060:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118985:</b> Galaxy QueryObjects did not find objects that needed redeployment (EDeploymentStatus.deployedWithPendingChanges). 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119069:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118897 SR 103123709:</b> Closing a window with an ArchestrA graphic element with an orientation animation configured for that element with reference to an UDA, changing the UDA value to 0, then reopening the window resulted in the window showing the old position value. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119119:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> Alarm Ack status did not update in the Alarm Client Control when alarms were acknowledged through the Alarm Client Control. The alarm Ack status updated on re-query. Alarm ACK status correctly updated in the Alarm Viewer Control and if alarms were acknowledged through the SignedAlarmAck function.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119231:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> Sorting by user's Full Name in the IDE Security Editor, then attempting to add a user, resulted in an error message. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119235:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118636 SR 38910344:</b> The SignedWrite function using HotFix L00118412 did not write the value, requested creadentials only the first time, and stopped working after the first attempt. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119237:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00118923 SR 38910367:</b> IBMX (MxAccess client) randomly missed On Write Complete events. A client application, such as InBatch, would randomly fail to receive a callback from a write complete.  
</td>
</tr>


</tbody></table>



</p><p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>



<meta content="MSHTML 6.00.2900.3132" http-equiv="GENERATOR"><basefont size="12px" face="verdana, arial, tahoma, helvetica">
<div style="TEXT-ALIGN: center"></div>
<h1 class="center">Wonderware Application Server 2012 (version 3.5) Readme</h1>

<!--
<H3 class=center><FONT color = "red"><b>*** BETA DRAFT - NOT FOR PUBLIC RELEASE ***</FONT></b></H3>
!-->

<p>Last revision: 9/23/2011</p>
<h2>About This Readme</h2>
<p>This document provides information about Wonderware<sup>®</sup> 
Application Server 2012 (version 3.5) features.</p> 
<h2>Wonderware Application Server 3.5 Readme Information</h2><font size="2">
<p>Click the following links to go to the various sections of this Readme.</p> 
<p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#About Wonderware Application Server 3.5">About Wonderware Application Server 2012 (version 3.5)
</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Antivirus Software Exclusions">Antivirus Software Exclusions</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Minimum Hardware Requirements">Minimum Hardware Requirements</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Software Requirements and Compatibility">Software Requirements and Compatibility</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2">Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2</a> 
</p><p><!--<A 
href="#Installing Wonderware Application Server 3.5">Installing Wonderware Application Server 3.5
</A> -->
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Upgrading to Wonderware Application Server 3.5">Upgrading to Wonderware Application Server 2012 (version 3.5)</a> 
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Migrating to Wonderware Application Server 3.5">Migrating to Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Resolved Issues - Wonderware Application Server 3.5">Resolved Issues - Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Known Issues - Wonderware Application Server 3.5">Known Issues - Wonderware Application Server 2012 (version 3.5)</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Wonderware Application Server Documentation Issues">Wonderware Application Server Documentation Issues</a>
</p><p><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Wonderware Application Server Documentation">Wonderware Application Server Documentation</a>
</p><p></p>


  
  </font><br>
  <span style="FONT-FAMILY: Verdana; COLOR: red; FONT-SIZE: 24px;"><a name="2012 Important"><b>Important!</b></a></span><a name="2012 Important"><br>



</a><ul><a name="2012 Important">
<li><b>Installation</b> - Before installing Wonderware Application Server 2012 (version 3.5): <br>
<ul style="LIST-STYLE-TYPE: disc">
<li>Ensure that you create backups of all Galaxies. </li>

<li>If you are using a Wonderware InTouch HMI 10.0 application with ArchestrA<sup>©</sup> Symbols, run the ArchestrA Symbol Analysis and Repair Utility and ensure that all issues reported by the utility are addressed.</li>

<li>Installing Application Server on a computer used as a domain controller is not supported.</li>

  <li>Installing Wonderware Application Server 3.5 
  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. </li>

<li><b>SQL Server Installation:</b></li>

<ul style="LIST-STYLE-TYPE: disc">

<li>If you use SQL Server 2008 SP1, 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.</li>


<li><b>SQL Server User Account:</b> SQL Server 2008 SP1 does not deliver the BUILTIN\Administrators role by default. While installing ArchestrA System Platform, configuration changes to SQL Server are required. If the installer does not have SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install "SQLAdmin" utility allows you to verify if the SQL configuration has been performed.  </li>
  
  <li><b>SQL Server Memory Usage:</b> After installing SQL Server, Use SQL Server Management Studio to confirm that the "Maximum Server Memory" is configured to approximately 65% of the total available RAM. By default SQL Server does not clamp this setting. The ArchestrA System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.</li>
  
  <li><b>Installing SQL Server Express:</b> If you plan to use SQL Server 2008 Express Edition with Wonderware Information Server 2012 and Wonderware InTouch 2012 on the same node, the following limitations apply. (These limitations do not apply if you use a non-Express edition of SQL Server.)
<ul>
  <li>Installing Information Server 2012 first, using MS SQL Express default instance name set to "SQLEXPRESS", and then installing InTouch 2012 will work without issue. Notice that in this scenario, each component uses a dedicated instance of MS&nbsp;SQL Express.
</li><li>Installing InTouch 2012 first, which silently installs and configures MS SQL Express, and then installing Information Server 2012, will not allow Information Server to work. In this case, during the configuration of Information Server, an error message will show in the Configuration Utility stating: "SQL Server client components not found". <br>

To work around this issue, configure Information Server to use an instance of MS SQL Express (or a non-Express edition) on a remote node</li>
</ul></li>
  
  <li><b>Restoring a CAB:</b> 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 such a restore initializes, 
and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy .cab restore operation does not complete, and no Galaxy is created. When you start the IDE, the Galaxy is blank.</li>

  </ul>

   </ul>


</li></a><li><a name="2012 Important"><b>UAC</b> - Disable User Account Control (UAC) before installing Wonderware Application Server 3.5 and Wonderware InTouch HMI 10.5, applicable for Windows Vista and above operating systems. 
For more information about User Access Control support, see </a><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#UAC_Support">Support for Windows Operating System User Access Control</a>.</li> 

<li><b>Coexistence and Upgrade</b>:</li>



<ul style="LIST-STYLE-TYPE: disc">

<li>If Wonderware Application Server and the InTouch HMI are installed on the same node, they both must be upgraded to 
Application Server 3.5 and Wonderware InTouch HMI 10.5, respectively.</li>


  <li>You must install Wonderware Historian 9.0 Patch 
  02 or Historian 10.0 or later to take advantage of new Historian features including 
  time propagation and late data from the Wonderware Application Server to the 
  Historian. These versions are also required to leverage the new Historian 
  configuration options from the IDE.</li> 

  <li>If the ArchestrA IDE connects remotely to the 
  Galaxy Repository on another computer, apply Wonderware Application Server 3.5 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. </li>

  <li>It is strongly recommended that you undeploy the platform prior to upgrading the software in that node. Once the GR node is upgraded from any prior version to version 3.5, all run-time nodes hosting InTouch applications must be upgraded both to 
  Wonderware Application Server 3.5 and to Wonderware InTouch HMI 10.5 (if you are running InTouch applications). You will not be able to deploy or undeploy objects on non-upgraded nodes. Installing the software on a run-time node will remove the running platform and objects. The platform and objects can then be redeployed after the software upgrade is complete.</li>

</ul>


<li><b>Alarm DB Logger</b>:</li> 


<ul style="LIST-STYLE-TYPE: disc">
<li>In order to use the Alarm DB Logger, you need to set the default SQL Server authentication mode from Windows-based to Mixed Mode. See L00116459 under <b>Installation Issues</b> for more information. </li>
<li>Results can be inconsistent if you attempt to log alarms from both InTouch and the Galaxy with Application Server and InTouch running in a console session on the same node under Windows Vista, Windows 7, or Windows Server 2008 operating systems. We do not recommend running both InTouch and Application Server in a console session on the same node.</li>
</ul>

<li><b>Language Switching</b> - Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality must always be modified on the same language operating system and InTouch language version, on which it was initially developed. Attempts to modify these components in a different language operating system or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system language that is different from the originally developed language are supported. </li>
<!--
Refer to Known Issues CRs L00088974, L00088993, and L00088998.</li>
!-->



<li><b>Antivirus Exclusions</b> - The antivirus software exclusions list has been updated. 
Click this <a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Antivirus Software Exclusions">Antivirus Software Exclusions</a> link for details.</li>


<li><b>Remote Sessions</b> - 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 <a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#TermServ">Terminal Services Behavior in Windows Server 2008</a> link for further information 
about terminal services behavior changes.</li> 


<li><b>Multiple Network Cards</b> - Using multiple network interface cards (NICs) in Windows Server 2008 R2, as with Windows Vista, requires specific configuration. 
</li>

<li><b>License Utility</b> - Starting the ArchestrA Licensing Utility from an existing License CD may not work on a 64-bit operating system. 
Start the utility from the installed shortcut instead.</li>

<li><b>Operating System Restrictions</b> - All the restrictions applicable to Windows Vista and Windows Server 2008 are also applicable to Windows 7 and Windows Server 2008 R2, respectively. </li>




</ul>

<hr>

<h2><a name="About Wonderware Application Server 3.5"></a>About Wonderware Application Server 2012 (version 3.5)</h2>
<p>The release of Wonderware Application Server 2012 (version 3.5) includes the following enhancements and new features:</p>
<ul>
<li><a name="DataBuffering"></a><b>Buffered Data Support: </b>
The Buffered Data Support feature enables data updates from field devices, which support Buffered Data Value Time Quality tag data, 
to be accumulated and propagated efficiently to data consumers such as objects, alarms, and Historian without losing the buffered data between engine scans.<br>
Buffered data is defined as data captured and stored locally on a remote device for later transfer to a supervisory system 
for processing, analysis, and long-term storage. 

</li><li><a name="ACLS"></a><b>Node-to-Node Version Protection: </b>
The Node-to-Node Version Protection feature provides a mechanism to identify and synchronize object components on a client that 
falls out of sync with the deploying Galaxy Repository node. Deployed object components of the client node are synchronized with 
the connected Galaxy Repository on the Server node.

</li><li><a name="ImportObjectTypeFilter"></a><b>Import Enhancements: </b>
A new Import Object Type Filter will restrict overwriting objects during an import operation, regardless of user preference options, 
based on the import overwrite restriction configuration. 

</li><li><a name="EnhancementsToolkits"></a><b>Enhancements to Toolkits: </b>
The Wonderware Application Server Toolkits (<b>GRAccess</b>, <b>MXAccess</b> 
and <b>ArchestrA Object Toolkit</b>) support the new Buffered Data Support feature. 

</li><li><a name="PlatformDeployment"></a><b>Platform Deployment Enhancements: </b>
You can now modify and test WinPlatform by deploying it without deploying its hosted objects. 
A configurable option permits a choice of whether or not to cascade deploy the platform object.

</li><li><a name="AssociateGraphics"></a><b>Associate All Galaxy Graphics with an InTouchViewApp Template:</b>
Associating all Galaxy graphics with an InTouchViewApp template enables deployed and published InTouch applications to execute "show graphic" requests made of any graphic in the Galaxy without having to embed them in the application.

<!--<li><b>Symbol Deployment Enhancements with Manifest Manager: </b>
You can create manifests of ArchestrA symbols using the new Manifest Manager and then associate the manifests with InTouchViewApp. When you deploy the InTouchViewApp, the ArchestrA Symbols associated to Manifests also get deployed. You can use this feature to deploy, publish and export ArchestrA symbols in manifest collections. For importing Manifests, you can use the existing ArchestrA import functionality.-->
</li></ul>

<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Antivirus Software Exclusions"></a>Antivirus Software Exclusions</h2><span style="FONT-FAMILY: Verdana">
<p>After installing Wonderware Application Server, configure your antivirus software to prevent archive files from being scanned. 
<table style="TEXT-ALIGN: left; WIDTH: 710px" border="0" cellspacing="1" cellpadding="5">
  <tbody>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">
	<font color="rgb(195,214,3)">NOTE</font></span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
      <ul>
        <li>Ensure that subfolders of the listed directories are also excluded. 
        </li><li>If you are using a 64-bit operating system, folder names must be 
        specified accordingly. For example, the program files root directory in a 
        64-bit operating system is C:\Program Files (x86)\... and the application data root directory in a 64-bit operating system is C:\ProgramData\...
  </li></ul></td></tr></tbody></table>
Antivirus software should not scan files in the following ArchestrA folders:
  </p><ul>
  <li>C:\Program Files\ArchestrA\*.*
  </li><li>C:\Program Files\Common files\ArchestrA\*.*
  </li><li>C:\Program Files\FactorySuite\*.* (may not exist in newer installations)
  </li><li>C:\Program Files\Wonderware\*.*
  </li><li>C:\InSQL\Data\*.*
  </li><li>C:\Historian\Data\*.*
  </li><li>C:\Documents and Settings\All Users\Application Data\ArchestrA*.*</li></ul></span><p></p>
  
  <p>From Wonderware Application Server Platform objects:</p>
<ol>
  <li>History Store Forward directory default location:
  <ul>
  <li>C:\Documents and Settings\All Users\Application Data\ArchestrA\
  </li><li>C:\Users\All Users\ArchestrA\ 
  </li></ul>
</li><li>Checkpoint directory location default location:
  <ul><li>C:\Program Files\ArchestrA\Framework\bin
  </li><li>C:\Program Files (x86)\ArchestrA\Framework\bin
  </li></ul>
</li><li>InTouch Application folder path:
  <ul><li>C:\Documents and Settings\All Users\Application Data\ArchestrA\</li></ul>
</li><li>SMC Logger Storage file path:
<ul><li>C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\</li></ul>
</li><li>SQL Server database files of type: 
<ul>
  <li>.mdf 
  </li><li>.ldf</li>
  </ul></li></ol>
  
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Minimum Hardware Requirements"></a>Minimum Hardware Requirements</h2>
<p>The following list shows the minimum computer hardware requirements to host 
Wonderware Application Server 3.5 on both 32-bit and 64-bit systems. The Intel Itanium 2 processor is not supported.
</p>
<h3>Application Server Galaxy Repository or ArchestrA System Platform 2012 Combination of Products</h3>

<ul>
<li>The recommended operating system for a Galaxy Repository is Windows 2008 R2 SP1.
</li><li>SQL Server 2008 SP1 Standard or Enterprise (32-bit) is the only supported version at this time.
</li></ul>

<table style="TEXT-ALIGN: left" cellspacing="2" cellpadding="2" width="700" border="1">
  <tbody>
  <tr>
    <td bgcolor="#EAAF0F" style="FONT-WEIGHT: bold; WIDTH: 190px; TEXT-ALIGN: center">Hardware Requirements</td>
    <td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 120px; TEXT-ALIGN: center">Small<br> (1 - 5,000 I/O)</td>
    <td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 150px; TEXT-ALIGN: center">Medium<br> (5,000 - 20,000 I/O)</td>
	<td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 120px; TEXT-ALIGN: center">Large<br> (&gt; 20,000  I/0)</td>
</tr>



<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">CPU (GHz)</td>
    <td style="WIDTH: 100px">2</td>
    <td style="WIDTH: 100px">2.5</td>
	<td style="WIDTH: 100px">2.5</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Minimum Cores</td>
    <td style="WIDTH: 100px">1</td>
    <td style="WIDTH: 100px">2</td>
	<td style="WIDTH: 100px">4</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">RAM (Min GB)</td>
    <td style="WIDTH: 100px">2</td>
    <td style="WIDTH: 100px">4</td>
	<td style="WIDTH: 100px">8</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Hard Disk size<br>(Available in GB)</td>
    <td style="WIDTH: 100px">100</td>
    <td style="WIDTH: 100px">250</td>
	<td style="WIDTH: 100px">500</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Monitor</td>
    <td style="WIDTH: 100px">1024 x 768</td>
    <td style="WIDTH: 100px">1280 x 1024</td>
	<td style="WIDTH: 100px">1280 x 1024</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Network card (MBPS)</td>
    <td style="WIDTH: 100px">100</td>
    <td style="WIDTH: 100px">100</td>
	<td style="WIDTH: 100px">1000</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="FONT-WEIGHT: bold; TEXT-ALIGN: center; WIDTH: 190px"><br>Input Devices<br></td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">DVD drive for installation</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Keyboard</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Mouse or compatible pointing device</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>
</tbody>
</table> 

<h3>Application Server Development or Run Time</h3>

<ul>
<li>The recommended operating system for development (IDE) or run-time nodes (Bootstrap) is Windows 7 SP1.
</li></ul>

<table style="TEXT-ALIGN: left" cellspacing="2" cellpadding="2" width="700" border="1">
  <tbody>
  <tr>
    <td bgcolor="#EAAF0F" style="FONT-WEIGHT: bold; WIDTH: 190px; TEXT-ALIGN: center">Hardware Requirements</td>
    <td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 120px; TEXT-ALIGN: center">Small<br> (1 - 5,000 I/O)</td>
    <td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 150px; TEXT-ALIGN: center">Medium<br> (5,000 - 20,000 I/O)</td>
	<td bgcolor="#C3D603" style="FONT-WEIGHT: bold; WIDTH: 120px; TEXT-ALIGN: center">Large<br> (&gt; 20,000  I/0)</td>
</tr>



<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">CPU (GHz)</td>
    <td style="WIDTH: 100px">2</td>
    <td style="WIDTH: 100px">2.5</td>
	<td style="WIDTH: 100px">2.5</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Minimum Cores</td>
    <td style="WIDTH: 100px">1</td>
    <td style="WIDTH: 100px">2</td>
	<td style="WIDTH: 100px">4</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">RAM (Min GB)</td>
    <td style="WIDTH: 100px">2</td>
    <td style="WIDTH: 100px">4</td>
	<td style="WIDTH: 100px">4</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Hard Disk size<br>(Available in GB)</td>
    <td style="WIDTH: 100px">100</td>
    <td style="WIDTH: 100px">100</td>
	<td style="WIDTH: 100px">100</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Monitor</td>
    <td style="WIDTH: 100px">1024 x 768</td>
    <td style="WIDTH: 100px">1280 x 1024</td>
	<td style="WIDTH: 100px">1280 x 1024</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Network card (MBPS)</td>
    <td style="WIDTH: 100px">100</td>
    <td style="WIDTH: 100px">100</td>
	<td style="WIDTH: 100px">1000</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="FONT-WEIGHT: bold; TEXT-ALIGN: center; WIDTH: 190px"><br>Input Devices<br></td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">DVD drive for installation</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Keyboard</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>

<tr>
    <td bgcolor="#EAAF0F" style="WIDTH: 155px">Mouse or compatible pointing device</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
    <td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
	<td bgcolor="#ADAFAF" style="WIDTH: 100px">&nbsp;</td>
</tr>
</tbody>
</table> 
  <p>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. Windows 7 and Windows Server 2008 R2 operating 
systems and SQL Server 2008 impose hardware requirements that may exceed the 
minimum requirements for Wonderware Application Server 3.5. If you 
intend to install Wonderware Application Server 3.5 on a computer running Windows 7, Windows Server 2008, or SQL Server 2008, see the following Microsoft Web sites for hardware requirements:</p><br>
<blockquote><p><a href="http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx">www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx</a><br><br> <a href="http://www.microsoft.com/windows/windows-7/get/system-requirements.aspx">www.microsoft.com/windows/windows-7/get/system-requirements.aspx</a><br><br>
<a href="http://msdn.microsoft.com/en-us/library/ms143506.aspx#EE32">msdn.microsoft.com/en-us/library/ms143506.aspx#EE32</a><br></p></blockquote> 

<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Software Requirements and Compatibility"></a>Software Requirements and Compatibility</h2><p>This section describes 
the operating system, database, and other software requirements to install 
Wonderware Application Server 3.5, along with product compatibility.</p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Operating_Systems">Operating Systems</a> 
  </li><li><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Compat">Product Compatibility</a>
  </li><li><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#SQLServer">SQL Server Requirements</a> 
  </li><li><a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Other_Software">Other Software Requirements</a> </li></ul>
<h3><a name="Operating_Systems"></a>Operating Systems </h3>
<ul>
  <li><b>For server components:</b> Windows Server 2008 R2 is the 
  recommended operating system for computers running server components. 
  </li><li><b>For client components:</b> Windows 7, 64-bit, is the 
  recommended operating system for computers running client components. 
</li></ul>
<p>The following table lists the supported operating systems that can be 
installed on computers running as Wonderware Application Server development, application, 
and GR nodes. Development and application nodes are considered to be clients of 
the server GR node.</p><p></p>
<table style="TEXT-ALIGN: left; WIDTH: 675px" border="1" cellspacing="2" cellpadding="2">
  <tbody>
  <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: center; VERTICAL-ALIGN: center; FONT-WEIGHT: bold" rowspan="2">Operating Systems</td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; FONT-WEIGHT: bold" colspan="3">Wonderware Application Server Components</td></tr>
  <tr>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; WIDTH: 146px; FONT-WEIGHT: bold">ArchestrA 
      IDE <br>(Development Node) </td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; WIDTH: 146px; FONT-WEIGHT: bold">ArchestrA 
      Run time <br>(Application Node) </td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; WIDTH: 146px; FONT-WEIGHT: bold">Galaxy 
      Repository <br>(GR Node) </td></tr>
  <tr>
    <td bgcolor="#EAAF0F">Windows XP SP3 <br>Professional <br>(32-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td bgcolor="#ADAFAF" style="TEXT-ALIGN: center">N</td></tr>
  <tr>
    <td bgcolor="#EAAF0F">Windows Vista SP2 <br>Business or Ultimate <br>(32/64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td bgcolor="#ADAFAF" style="TEXT-ALIGN: center">N</td></tr>
  <tr>
    <td bgcolor="#EAAF0F">Windows 7 <br>Professional or Ultimate <br>(32/64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td bgcolor="#ADAFAF" style="TEXT-ALIGN: center">N</td></tr>
  <tr>
    <td bgcolor="#EAAF0F">Windows 7 SP1 <br>Professional or Ultimate <br>(32/64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td bgcolor="#ADAFAF" style="TEXT-ALIGN: center">N</td></tr>
 <tr>
    <td bgcolor="#EAAF0F">Windows Server 2003 SP2 <br>Standard or Enterprise <br>(32-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td></tr>
	<tr>
    <td bgcolor="#EAAF0F">Windows Server 2008 SP2 <br>Standard or Enterprise <br>(32/64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td></tr>
	<tr>
    <td bgcolor="#EAAF0F">Windows Server 2008 R2 <br>Standard or Enterprise <br>(64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td></tr>
	<tr>
    <td bgcolor="#EAAF0F">Windows Server 2008 R2 SP1 (Standard, Enterprise) <br>(64-bit)</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td>
    <td style="TEXT-ALIGN: center">Y</td></tr>
  </tbody></table>
<h4>Operating System Notes</h4>
<ol>
  <li>The computer designated as the Galaxy Repository node can run on Windows 
  XP Pro only as a single-node configuration of Wonderware Application Server. Windows 
  Server 2008 R2 is the recommended operating system for the GR node. 
  </li><li>The Bootstrap, IDE, and Galaxy Repository are supported by the following 
  language versions of Microsoft operating systems: English, Japanese, Simplified Chinese, 
  German, and French. The Galaxy Repository is also supported by the English, 
  Japanese, Simplified Chinese, German, and French versions of Microsoft SQL Server 2005 
  and SQL Server 2008 SP1.</li></ol>
  

  <h5><a name="UAC_Support"></a>Support for Windows Operating System User Access Control</h5>
<p>Application Server versions 3.1, 3.1 SP1, 3.1 SP2, 3.1 SP2 Patch 01, 3.1 SP3, 3.2, and 3.5 support User Access Control-enabled run-time operations without elevated privileges.</p>
<p>For all configuration and installation operations, including those called during run-time operations, User Access Control must be disabled or privileges must be elevated to the required level.</p>
<h5>DDE Support</h5>
<p>In Windows Vista, Windows Server 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. </p>
<p>In ArchestrA Symbols, <b>InTouch:&lt;tagname&gt;</b> is still a valid method of referring to an InTouch tag on a local node.</p>
 
  
<h3><a name="Compat"></a>Product Compatibility</h3>
<p>Wonderware Application Server 3.5 is compatible and can co-exist with the following products:</p>
<table style="TEXT-ALIGN: left; WIDTH: 695px" border="1" cellspacing="2" cellpadding="2">
  <tbody>
  <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: center; VERTICAL-ALIGN: center; FONT-WEIGHT: bold">Product</td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; VERTICAL-ALIGN: center; FONT-WEIGHT: bold">Version</td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; VERTICAL-ALIGN: center; FONT-WEIGHT: bold; WIDTH: 100px">Compatibility</td>
    <td bgcolor="#C3D603" style="TEXT-ALIGN: center; VERTICAL-ALIGN: center; FONT-WEIGHT: bold; WIDTH: 100px">Co-existence</td></tr>
  <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware InTouch HMI</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.5</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td></tr>
  <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware InTouch HMI</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.1, 10.1 SP2 P01, 10.1&nbsp;SP3, 10.2</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">N</td></tr>
   <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Historian Client</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.0 SP1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">N</td></tr>
   <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Historian Client</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.0 SP2</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td></tr>  
	<tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware InTouch CE</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">N</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">N</td></tr>
  <tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Historian Server</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">10.0 SP1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr><tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Manufacturing Execution System</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">4.0, 4.0 SP1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr><tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Information Server</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">4.0, 4.0 SP1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">N
	</td></tr><tr>
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Information Server</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">4.5</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y  

   </td></tr><tr>   
   <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware InControl™</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">7.11 SP2 P01</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr><tr>   
   <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Manufacturing Execution Module</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">1.0</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr><tr>   
   <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware InBatch™</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">9.0 SP1, 9.0 SP2, and 9.5</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr><tr>   
   <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware QI Analyst™</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">8.0 SP2</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
  </td></tr><tr>   
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware SCADAlarm™</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">6.0 SP2 P01</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr>
   <tr><td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">ArchestrA Workflow™</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">1.1</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
  </td></tr><tr>   
    <td bgcolor="#EAAF0F" style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">Wonderware Intelligence</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">1.5</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">Y
	</td></tr></tbody></table><p></p>
<blockquote><ul style="LIST-STYLE-TYPE: disc">

</ul></blockquote>
<p>In some cases, Wonderware Application Server 3.5 is supported in newer environments than a compatible product. Wonderware Application Server 3.5 has been tested for compatibility with a listed product only in the environments that are supported by that particular product. </p>
  <h3><a name="SQLServer"></a>SQL Server Requirements </h3>
<h5>SQL Server Database Requirements</h5>
<p>Microsoft SQL Server 2008 SP1 is supported by Wonderware Application Server 3.5. You must use the Standard SQL Server 2008 SP1. </p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li>SQL Server 2008 SP1 must be installed on the computer designated as the ArchestrA Galaxy Repository node prior to 
  installing Wonderware Application Server Galaxy Repository feature. 
  </li><li>If multiple versions of SQL Server are installed, the one utilized as the Galaxy Repository must be the default instance. 
  </li><li>The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the computer's physical memory. 
  </li><li>TCP/IP must be enabled on the computer hosting a SQL Server 2008 database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL Server Configuration Manager. 
  </li><li>In order to use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.</li></ul>
  
  
<h5><a name="SQLRights">Upgrading SQL Server on the Galaxy Repository Node</a></h5>
<p>When upgrading SQL Server on the Galaxy Repository node, back up the Galaxy before starting the upgrade. Upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see <a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Upgrading to Wonderware Application Server 3.5">Upgrading to Wonderware Application Server 3.5</a> and <a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#GRUpgrade">Galaxy Repository Node Upgrade.</a> Also see the Application Server Installation online Help.</p>

  <h5><a name="SQLRights">SQL Server Rights Requirements</a></h5>
<p>SQL Server 2008 does not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 3.5 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:</p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li>Run the Change Network Utility from the Windows Start menu. 
  </li><li>Run the aaConfig SQL Utility from the Windows Start menu. 
</li></ul><p>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 <i>Wonderware Application Server User's Guide</i>, About ArchestrA 
User Accounts, for further information and procedures about restoring the 
aaAdministrators group.</p> 
<h3><a name="Other_Software"></a>Other Software Requirements </h3><p>The other third-party software required for Wonderware Application Server 
version 3.5 is Microsoft .NET Framework 3.5 SP1. This must be installed on every computer that 
  hosts a Wonderware 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. Wonderware Application Server 3.5 has been 
  validated with .NET Framework 3.5 SP1.</p> 

<h3>Alarm Client and Trend Client Requirements</h3><p>If you want to trend data from the Wonderware 
Historian (formally known as IndustrialSQL Server), version 9.0 or Wonderware Historian 10.0 is 
required. <br><br>The Trend Client is compatible with the following Wonderware 
products:</p><p></p>
<ul style="LIST-STYLE-TYPE: disc">
  <li>Wonderware InTouch HMI 10.1, 10.1 SP2, 10.2 and 10.5
  </li><li>Wonderware Application Server 3.1, 3.1 SP1, 3.2, and 3.5 
  </li><li>Wonderware Historian 9.0 and 10.0 
  </li><li>ActiveFactory 9.2 and Wonderware Historian Client 10.0 SP1 and SP2
  </li><li>QI Analyst 8.1 </li></ul>
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2"></a>Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2</h2><p>This section describes specific behaviors and restrictions when using the Windows 7 and Windows 
Server 2008 R2 operating systems with Wonderware Application Server.</p>
<ul style="LIST-STYLE-TYPE: disc">
<li>In ArchestrA, when the DDESuiteLinkClient is connected to the local DAServer using DDE, it does not work with 
User Access Control enabled. The same works when User Access Control is disabled.
</li>
<li>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 right-clicking on the file and then clicking <b>Run As Administrator</b>.
</li>
<li>Wonderware Application Server may experience performance degradation when running on the Windows 7 or Windows Server 2008 R2 operating systems, depending on how certain operating system tuning parameters are configured. For more information, see Tech Note #719.
</li>  
<li>Using multiple NICs in Windows 7 and Windows Server 2008 R2 operating systems requires specific configuration. For more information, see "Configuring Multiple NICs for the Vista and Windows Server 2008 Operating Systems" in the <i>Wonderware Application Server User's Guide</i>.</li></ul>
<!--<table style="TEXT-ALIGN: left; WIDTH: 710px" border="0" cellspacing="1" cellpadding="5">
  <tbody>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold"><font color="rgb(195,214,3)">NOTE</font></span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
      A known issue regarding .NET 3.5 SP1 while installing Application Server 3.2 on a Windows Server 2008 R2 or Windows 7 64-bit operating system is documented in <a href="#Installation312"> Installing Wonderware Application Server 3.2. </a></td></tr></tbody></table>-->
<h3><a name="TermServ"></a>Terminal Services Behavior in Windows Server 2008</h3>
<p>
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. 
</p>
<p>
This impacts InTouch functionality such as Alarm Manager that 
depends on the Terminal Server Console session. Refer to the Wonderware InTouch HMI 10.2 
Readme for further information about InTouch applications running in the 
Terminal Server Console. The impact to Wonderware Application Server is minimal as most 
Wonderware Application Server processes run as services. One impact to Wonderware Application Server 
is to carry forward the restriction introduced with the Windows Vista operating 
system which permits only one alarm provider. While both Wonderware Application Server and 
InTouch can be configured as alarm providers, only one alarm provider can be configured at any one time.</p> 
<p>
Wonderware Application Server and InTouch detect when the application is running in the console. In Windows Server 2008 R2 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 7 and Windows Server 2008 operating systems. 
</p>
<p>
To disable Fast User Switching in Windows 7 or Windows Server 2008 R2, use the following procedure: 
</p>
<ol>
<li>Click <b>Start</b>, then <b>Run</b>, and enter <code>gpedit.msc</code> in the text box. Press <b>Enter</b>.</li>
<li>Go to the following location: 
Local Computer Policy\Administrative Templates\System\Logon.</li>
<li>Set Hide entry points for <b>Fast User Switching</b> to <b>Enabled</b>.</li>
<li>Exit the <b>Group Policy Editor</b>.</li>
</ol>
<p>
By enabling the policy, Administrators hide the <b>Switch User</b> button in Windows logon, in the <b>Start</b> menu, and in the <b>Task Manager</b>. Note that the <b>Group Policy Editor</b> does not exist in certain editions of Windows 7. Alternately, you can configure the setting by editing the <b>Registry</b>.
</p>
<ol>
<li>Click <b>Start</b>, then <b>Run</b>, and enter <code>regedit.exe</code> in the text box. Press <b>Enter</b>.</li>
<li>Navigate to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.</li>
<li>Create a DWORD (32-bit) Value named <code>HideFastUserSwitching</code>. </li>
<li>Set the Value data for <code>HideFastUserSwitching</code> to 1.</li>
<li>Exit the <b>Registry Editor</b>.</li>
</ol>
<span style="FONT-FAMILY: Verdana"></span> 
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>
<!--<h2><a name="Installing Wonderware Application Server 3.5"></a>Installing Wonderware Application Server 3.5</h2><p>Refer to the <i>ArchestrA System Platform Installation Guide</i> for details on Installation of Wonderware Application Server 3.5.</p>
<h3><a name="InstallAppServer"></a>Installing Application Server on a Windows Server 2008 R2 or Windows 7 64-bit System</h3><p><p>Starting with Windows Server 2008 R2, the method of installing .NET Framework 3.5 SP1 has changed. This change affects the installation of Application Server 3.5 on Windows Server 2008 R2 and Windows 7 64-bit operating systems.
<p>If .NET Framework 3.5 SP1 is not already installed on your system prior to installing Wonderware Application Server 3.5, you must install it manually. 
<p>If you have already started the Wonderware Application Server 3.5 installation, you will need to exit, manually install .NET 3.5 SP1, then return to the Application Server 3.2 installation. 
<p><b>For Windows Server 2008 R2 Operating Systems:</b> To install the .NET Framework 3.5 SP1, you can use the Microsoft Server Manager interface or the Microsoft Power Shell.</p>
<p class="bold">To use the Server Manager</p>
<ol type="1"> 
<li>Click <b>Start</b>, then highlight <b>Administrative Tools</b> and select <b>Server Manager</b>.
<li>In the <b>Server Manager</b>, select <b>Add Features</b>, then expand <b>.NET Framework 3.5.1 Features</b>.
<li>In <b>.NET Framework 3.5.1 Features</b>, select the <b>.NET Framework 3.5.1</b> check box. Click <b>Next</b>.
<li>Click <b>Install</b> to confirm the installation selection. The .NET Framework 3.5.1 installation will proceed.</li></ol>
<p class="bold">To use the Windows Power Shell</p>
<ol type="1">
<li>Click <b>Start</b>, highlight <b>All Programs</b> and select <b>Accessories</b>.
<li>Expand <b>Windows PowerShell</b> and right click <b>Windows PowerShell</b> and select <b>Run as administrator</b>. Click <b>Yes</b> on the <b>User Account Control</b> box.
<li>At the Power Shell Command Prompt, enter the following two commands and press <b>Enter</b> after each command:</li>
<ol type="a">
<li><b>Import-Module ServerManager</b>
<li><b>Add-WindowsFeature as-net-framework</b></li></ol>

<li>Exit Windows Power Shell.</li></ol>

<p><b>For Windows 7 Operating Systems:</b> To install the .NET Framework 3.5 SP1, use the Programs and Features interface. </p>

<ol type="1">
<li>Start <b>Control Panel</b>, then select <b>Programs</b>, then select <b>Programs and Features</b>.
<li>Click <b>Turn Windows Features On or Off</b>.
<li>Select the <b>Microsoft .Net Framework 3.5.1</b> check box and then click <b>OK</b>.
<li>Restart your computer.</li></ol>


<span style="FONT-FAMILY: Verdana"></span> 
<p class="right"><a title="Click this link to go to the top of the document." href="#Top">&lt; top of document &gt; </a>
<hr>-->

<h2><a name="#Upgrading to Wonderware Application Server 3.5"></a>Upgrading to Wonderware Application Server 2012 (version 3.5) </h2>
<p>After the hardware and software requirements are met, including the proper operating system, SQL server and other 
pre-requisites, you can upgrade to Wonderware Application Server 3.5 from the following versions of Wonderware Application Server:</p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li>Version 3.0 SP2 
  </li><li>Version 3.1 (All service packs and patches)</li>
  <ul style="LIST-STYLE-TYPE: disc">
    <li>3.1 
	</li><li>3.1 SP1
	</li><li>3.1 SP2
	</li><li>3.1 SP2 PO1
	</li><li>3.1 SP3
	</li><li>3.1 SP3 PO1
	</li></ul>
</ul>
<table style="TEXT-ALIGN: left; WIDTH: 710px" border="0" cellspacing="1" cellpadding="5">
  <tbody>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold"><font color="rgb(195,214,3)">NOTE</font></span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
Upgrading to Application Server 3.5 will affect run-time nodes. Node-by-Node upgrade is supported with limitations. Changing the security or history model in a node-by-node upgrade of the run-time nodes is not supported. Nodes that are currently deployed will not receive any history or security changes from the upgraded GR node.</td></tr></tbody></table>

<h3><a name="Upgrade_SP2_Requirements"></a>Wonderware Application Server 2012 (version 3.5) Upgrade 
Requirements</h3>

<p>The following requirements apply when upgrading existing Wonderware Application Server components to version 3.5:</p> 
<ol type="1">
  <li>Upgraded IDE/Client nodes cannot connect to a non-upgraded Galaxy 
  Repository (GR) and vice-versa. 
  </li><li>The GR Node will be undeployed before upgrading to Wonderware Application Server 3.5. 
  </li><li>Running platforms must be undeployed during the upgrade process. </li></ol>
  <ul style="LIST-STYLE-TYPE: disc">
    <li>WinPlatform and other related objects on a remote node will be marked as 
    "software update pending". 
	</li><li>You will not be able to deploy from an upgraded GR node to non-upgraded remote nodes.</li></ul>
<p></p>	

<h3><a name="GRUpgrade">Galaxy Repository Node Upgrade</a></h3>
<p><b>Important:</b> Back up the Galaxy before starting the upgrade. Also, upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Application Server Installation online Help.</p>
<p>The basic upgrade sequence is: 
</p><ol type="1">
<li>Upgrade your software prerequisites to the required versions.</li><br>
<b>Important:</b> If you are upgrading the SQL Server on the Galaxy Repository node, you must undeploy the Galaxy 
Repository node before starting the SQL Server upgrade.
<li>Upgrade the Application Server software in the Galaxy Repository node to the current version.
</li><li>Upgrade at least one IDE installation. If the Galaxy Repository node has the IDE as a feature, then the IDE is also updated. However, if you have any IDE-only nodes, you need to upgrade them separately. 
</li><li>Use the upgraded IDE to connect to the upgraded Galaxy Repository node and migrate the Galaxy database. For more information, see <a href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#grnode"> GR Node Migration</a>. 
</li><li>Deploy the Galaxy Repository Platform.
</li><li>Upgrade run-time nodes.</li>
<li>Upgrade non-redundant run-time nodes one at a time and redeploy them.</li><br>
<b>Important:</b> Redundant nodes must be upgraded together. You cannot leave one node running, while the other one is being upgraded.
<li>Upgrade redundant pairs as a set.</li> </ol>
<p>If you upgrade a remote Platform node before you migrate the Galaxy database, the remote Platform and hosted objects show the software upgrade pending icon after you migrate and deploy the Galaxy. To resolve this, undeploy and redeploy the remote Platform. The preferred sequence of upgrade is to upgrade the Galaxy Repository node, migrate the Galaxy database, and then upgrade the remote Platforms.</p>


<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Migrating to Wonderware Application Server 3.5"></a>Migrating to Wonderware Application Server 2012 (version 3.5) </h2><p>
You can migrate applications from the following earlier versions of Wonderware Application Server to version 3.5:</p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li>Version 2.1 PO2 
  </li><li>Version 3.0 SP2 
  </li><li>Version 3.1 (All service packs and patches)</li>
  <ul style="LIST-STYLE-TYPE: circle">
    <li>3.1 
	</li><li>3.1 SP1
	</li><li>3.1 SP2
	</li><li>3.1 SP2 PO1
	</li><li>3.1 SP3
	</li><li>3.1 SP3 PO1
	</li></ul>	
  <li>Version 3.2</li>
</ul>
<h3><a name="grnode"></a>GR Node Migration </h3>
<p>While migrating the GR Node, the existing database schema is migrated to the new version 3.5 schema. The GR node migration fails if the GR node is used as a run-time node for another GR.</p> 
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="#Resolved Issues - Wonderware Application Server 3.5"></a>Resolved Issues - Wonderware Application Server 2012 (version 3.5)</h2>

<p>This section describes important resolved issues in Wonderware Application Server 3.5. The following list is not a comprehensive list of all resolved issues.</p>

<table style="TEXT-ALIGN: left" border="0" cellspacing="1" cellpadding="5" width="700"><tbody>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111263</span>:</td>
    <td><b>HF CR L00110348 (Hotfix 2357) SR 15315947</b>: During the creation of a test Galaxy, when you open the template and run it on 
	ArchestrA IDE, the correct symbol is displayed. However, when you deploy the instance and run it on WindowViewer, 
	then an incorrect symbol is displayed.  
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111626</span>:</td>
    <td><b>HF CR L00109139 (Hotfix 2254) SR 22316915</b>: During RDI (Redundant DI object) failover, the total number of items in the 
	SMC\Client Groups and Device Groups do not match  with the number of RDI items. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111631</span>:</td>
    <td><b>HF CR L00111464 (Hotfix 2416) SR 33811636</b>: Galaxy Dump crashes ArchestrA IDE, and the following error message appears 
	in the SMC Logger:<br>
Error when trying to refresh proxies -No connection could be made because the target machine actively refused it 127.0.0.1:8090 

  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111640</span>:</td>
    <td><b>HF CR L00111068 (Hotfix HF2403) SR 103120006</b>: When you click a symbol button that is configured with the 
	ShowSymbol animation script and a pop-up dialog box, the symbol appears. After entering text in the dialog box, 
	when you close the symbol, the symbol button still remains selected.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111722</span>:</td>
    <td><b>HF CR L00111418 (Hotfix 2425)</b>: After deployment or failover of DDESL (DDESuitelink) object, 
	some items are displayed as good and some as bad. Items whose values should be displayed as good are stuck at initializing. 
	After the value of the item is updated in the field device, it is displayed as good in the DDESuitelinkClient object. 
	Some items whose values should be displayed as bad are also stuck at initializing.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111969</span>:</td>
    <td><b>HF CR L00111725 (Hotfix 2425) SR 22316791/37111660</b>: Double polling occurs in RDI even after ACM 
	(Advanced Communication Management) is disabled by following Hotfix 2033.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112580</span>:</td>
    <td><b>HF CR L00110749 (Hotfix 2383) SR 103119448</b>: On engine failover, RDI cannot connect to DI sources 
	and the platform communication errors appear. After the failover of an engine hosting OPC client objects and 
	another hosting the RDI object, RDI shows one OPC client object to be connected and the other to be disconnected.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112581</span>:</td>
    <td><b>HF CR L00102633 (Hotfix 1900) SR 22316050</b>: The engines restart automatically and the same process ID is associated 
	to the engine name. Hence it seems that their private byte memory leaks after installing Hotfix 1676C.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112613</span>:</td>
    <td><b>HF CR L00110688 (Hotfix 2379) SR 103120710</b>: When you request a tag through View, the tag opens but does not close. 
	For every tag that is left open, ScanGroupRuntime reports the following message:<br>
  &lt;tagname&gt; was already deleted due to reentrancy from data provider

	</td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112617</span>:</td>
    <td><b>HF CR L00109819 (Hotfix 2325)</b>: When a block is edited and checked in within the ArchestrA IDE, 
	then the objects remain in the memory and they are released only when the operation completes.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112619</span>:</td>
    <td><b>HF CR L00108335 (Hotfix 2200) SR 103119265</b>: After the switchover of a redundant AppEngine, 
	the redundant DIObject does not set some items to active state.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112622</span>:</td>
    <td><b>HF CR L00111832 (Hotfix 2463) SR 38231298</b>: The changes made in a parent template do not transmit to its 
	derived/child objects.   

  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113007</span>:</td>
    <td><b>HF CR L00110198 (Hotfix 2352) SR 23333459</b>: The ArchestrA graphic symbol changes its position or becomes bigger, 
	and then becomes small after a few hours or days on its own.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113077</span>:</td>
    <td><b>HF CR L00112646 (Hotfix 2493) SR 103121180</b>: When you point to an RDI object, double advisement is required.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113406</span>:</td>
    <td><b>HF CR L00112999 (Hotfix 2507) SR 15315956</b>: When a template object is imported into a customer’s test Galaxy 
	from SI’s (System Integrator) test Galaxy, then the deleted objects also get imported. However if the template object is imported into another Galaxy, 
	the deleted objects are removed. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113415</span>:</td>
    <td><b>HF CR L00098344 (Hotfix 2480) SR 19417204</b>: The Config Set Handler code stops working on an instance that is derived 
	from a template that is derived from the base template built by the ArchestrA Object Toolkit.
  </td></tr>  
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00114446</span>:</td>
    <td><b>HF CR L00113943 SR 103121317</b>: If a graphical object has an embedded object with text substituted at the host level, 
	then the XML file creates a code similar to the following: <br>
	<p>&lt;Context&gt;MySymbol:txt_test1;StringSubstitution;NovaString:-&amp;gt;Translation&lt;/Context&gt;

</p><p>If any of the text strings (NovaString or Translation) contains a colon or a semicolon, the code is broken, 
the object translation import fails, and an error appears.

  </p></td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00114500</span>:</td>
    <td><b>SR 19417537</b> If the network address of the platform uses an alias in the hosts file that is different from the NetBIOS name of the target computer, the deployment status in the IDE is not updated and the Platform Manager does not get an update for the run-time status. 
<p>This issue has been fixed. The platform's alias name must be included in the hosts file on both on the GR node and target node in the following format.</p>
<p>&lt;IPAddress&gt;  &lt;AliasName&gt;</p>  

  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115103</span>:</td>
    <td><b>HF CR L00114486 SR 33932491</b>: The deployment of an InTouchViewApp takes more than 40 minutes and when the 
	deployment is complete, many graphics are missing.  
	

  </td></tr>



</tbody></table>

<p>
</p>
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a><br>
</p><hr>
<br>
<h2><a name="Known Issues - Wonderware Application Server 3.5"></a>Known Issues - Wonderware Application Server 2012 (version 3.5) </h2>
<p>This section describes important known issues identified in Wonderware Application Server 3.5.

<br><p></p><br><p></p><table style="TEXT-ALIGN: left" border="0" cellspacing="1" cellpadding="5" width="700"><tbody>

 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00069519</span>:</td>
    <td>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. <br><br>After the InTouch ViewApp deploy fails, 
      it can be manually re-deployed. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00076557</span>:</td>
    <td><span style="FONT-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"></span>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.</td></tr>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00077487</span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">During tag registration, 
      Wonderware Historian discards the value for SampleCount (isSamples) 
      provided by Application Server. <br><br>Before installing Wonderware Application Server 3.1, apply 
      Wonderware Historian 9.0 Patch 02 to resolve this issue.</td></tr>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00077490</span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">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. 
</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00078221</span>:</td>
    <td>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. <br><br>Application Server 2.1 supports .NET 1.1, 
      while Application Server 3.0 supports .NET 2.0. The DateTime structure in 
      .NET 2.0 includes a new Kind property that indicates whether the time 
      represents a local time, a Coordinated Universal Time (UTC), or whether 
      UTC or local time is not specified. For more information, see the 
      following Microsoft documentation: 
      http://msdn.microsoft.com/en-us/library/system.datetime.aspx <br><br>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:<br><br>dim aTime as 
      System.datetime;<br>dim aTime2 as System.DateTime;<br>aTime = 
      me.lastpolltime;<br>aTime = system.datetime.SpecifyKind(aTime, 
      system.dateTimekind.utc); me.locallastpolltime = 
aTime.tolocaltime();</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00078446</span>:</td>
    <td>The ArchestrA Symbol Editor stops responding when you edit the "format 
      string" property of the "checked list box" client control.</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00078465</span>:</td>
    <td>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.<br><br>Use a date on or after 1/1/1970 
      when using the "LogDataChangeEvent()" script. </td></tr>
  <tr>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00079595</span>:</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">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. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00081837</span>:</td>
    <td>The following error message appears when a non-upgraded IDE node 
      (earlier than Wonderware Application Server 3.0 SP2) tries to connect to an upgraded 
      Galaxy Repository node. Error message: "IDE cannot connect to remote GR 
      node &lt;name&gt; because it is an older version &lt;number&gt; than this 
      IDE version supports."</td></tr>
  <tr>
    <td><span style="FONT-WEIGHT: bold">L00083270</span>:</td>
    <td>Spaces are not imported as part of the translation for the selected 
      language. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00083909</span>:</td>
    <td>InTouch applications receive Quality Status and Locale information 
      from the deployed Galaxy. InTouch applications cannot receive data from an 
      undeployed Galaxy.</td></tr>	  
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00084306:</span></td>
	<td>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.	
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00085806:</span></td>
    <td>The font used for graphics in ArchestrA symbols does not render 
      properly in the Symbol Editor and on print outs, if the DPI of the screen 
      or printer is less than or greater than 96-dpi. <br><br>Wonderware does 
      not support running the product in DPIs other than 96 DPI.</td></tr>	
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00086242:</span></td>
	<td>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. 
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087046</span>:</td>
    <td>An embedded symbol is lost after swapping symbol names. VERL (Visual 
      Element Reference List) corruption is artificially causing a circular 
      reference. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087247</span>:</td>
    <td>InTouchViewApp fails to undo a checkout when there is a file-lock 
      within the CheckOut folder. You should not attempt to check-in the 
      InTouchViewApp. <br><br>Fix the file-lock issue, and perform the 
      "undo-checkout" again. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087305</span>:</td>
    <td>When you rename a referenced symbol while an object editor is open, 
      the reference to the renamed symbol may be lost.</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087471:</span></td>
    <td>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." <br><br>You must restart the 
      aaGR.exe process to reestablish the connection to the database 
  server.</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087752:</span></td>
    <td>You must restart the aaGR.exe after you import an object with a minor 
      version increment, if the object is written in .NET.<br><br>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. <br><br>Restart of the aaGR.exe is required 
      if all of the following apply:<br>
      <li>DotNetAppObject version 1.0 is loaded in the Galaxy<br>
      </li><li>An object vendor creates a new minor version of DotNetAppObject 
      version 1.1<br>
      </li><li>An IDE user imports the new .aaPKG file with DotNetAppObject version 
      1.1 into the Galaxy that has DotNetAppObject 1.0 loaded.<br><br>You must 
      restart aaGR.exe for the new object to be recognized and deployed to the 
      IDE nodes.</li></td></tr>	

  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00089937:</span></td>
    <td>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. </td></tr>

	<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00092635:</span></td>
	<td>Application Server 3.1 SP2 will import an alarm comment file for language switching of format <code>Galaxy_ACLSGalaxy1_2058_Alarm_Comments_Untranslated.txt</code> but InTouch WindowMaker doesn't recognize the file. This behavior is as-designed. InTouch will only recognize file format <code>%_AlarmComment.txt</code>. The option to export untranslated comments was provided in Application Server in order to diagnose and verify quickly whether all translations for a specific locale have been done, and to manage or find untranslated alarm messages in large galaxies. This functionality was provided as value added for Wonderware Application Server, but was not required for InTouch.
	</td></tr>
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00092675:</span></td>
	<td>In the alarm comment run-time language switching feature, the PhraseId can go out of sync in exported files for the same alarm message in different languages. This does not cause problems in exporting or importing alarm messages into the Galaxy, but it can lead to a failure in InTouch to switch the alarm comment language in run time. Alarms for which the PhraseId does not match between the different languages will not switch. Instead of showing the translated message, the default alarm message, in English if the Galaxy was created in English, will be displayed.
	<p>
	The Lang.dll in InTouch has been modified to log a warning in the SMC that the current alarm message does not match across translated languages. The message recommends that you re-export all the languages of the conflicting file from the Galaxy, and re-import them to the InTouch application. The conflicting file name will be part of the message. We recommend that you keep all the translated exported language files in sync.  
</p>
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00093428:</span></td>
    <td>In Windows Vista and higher operating systems, the DDE cannot communicate across sessions. This 
      is a User Interface Privilege Isolation (UIPI) issue. For example, with 
      Wonderware Application Server running in Session 0 as a service, Excel would run in a 
      session other than 0, a User interactive session. In this scenario, DDE is 
      not able to communicate across the session. SuiteLink can work in place of 
      DDE under certain conditions.</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00093558:</span></td>
    <td>When you upgrade from Wonderware Application Server version 2.5 to version 3.1 SP1, the following error message appears: "ArchestrA.Configuration.PackageServerNet.PackageServerNet instance 
      not properly disposed." The error message is informational. No action is required. </td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00093559:</span></td>
	<td>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. 
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00095432:</span></td>
	<td>After Installing ArchestrA products such as InTouch, InTouch CE, Application Server, InSQL, and ActiveFactory 9.2, some DAServers cannot be installed. During the DAServer installation, a Prerequisite Setup Error appears, "Rainbow Sentinel setup failed to complete successfully." The issue does not occur if the DAServers are installed first and then ArchestrA products are installed. This issue will be addressed in future DAServers releases.
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00095452:</span></td>
	<td>The Reactor_Demo_Application_Server displays name conflict errors while attempting to enable history for several $ReactorSet.Reactor field attributes such as ConcPump and ConcValve. The issue appeared in Wonderware Application Server 3.1 which added the capability in the Extensions section to add a description in the history extension. This modification has created a conflict   with field attributes and object graphics.
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00095695:</span></td>
	<td>When using Microsoft SQL Server 2008 Development Edition, the GR service fails to connect and freezes. This issue occurs because the Development Edition of SQL Server, which is not supported by Wonderware Application Server, does not enable TCP/IP service by default.
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00095744:</span></td>
	<td>The Microsoft OLE DB provider for Oracle and neither <b>Driver do Microsoft Access[*.mdb]</b> nor <b> Driver do Microsoft Excel[*.xls]</b> are visible in a Windows Server 2008 64-bit SP2 Standard Edition operating system with SQL Server 2008 SP1 installed. These drivers are 32-bit drivers and are not visible in a 64-bit system directly from <b>Control Panel, Administrative Tools, DataSources(ODBC)</b>. You can create ODBC connections by running <code>C:\Windows\SysWOW64\odbcad32.exe</code>. This is a 32-bit application, which will display 32-bit drivers. This issue does not occur on 32-bit systems.
<p>
Microsoft does not provide a 64-bit OLE DB Provider for Oracle. Oracle provides a separate OLE DB Provider for use on 64-bit systems. </p>
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00097202:</span></td>
	<td>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. 
<p>
There are three possible workarounds to stop the memory leak: </p>
<ol>
<li>Declare the array of indirect into the Declarations section rather than inside the script.</li>
<li>Reduce the sleep time inside the script or increase the <b>Maximum time for script to execute</b> in the engine configuration, so that script does not timeout.</li>
<li>Use the asynchronous script with an appropriate timeout limit.</li>
</ol>
	</td></tr>
	  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00097788:</span></td>
	<td>Existing license CDs have issues running aaLicView.exe in a 64-bit operating system and will not correctly install a license. You must use the license utility installed with the Wonderware Application Server or InTouch software. 
	</td></tr>
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00098305:</span></td>
	<td>After upgrading the GR node, a Deploy/Un-deploy attempt on a non-upgraded remote platform undeploys InTouchViewApp and ViewEngine assigned under the non-upgraded Remote platform. 
	</td></tr>
<tr>
	<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00098946</span></td>
	<td>With Scan on Demand (SOD) enabled, if an item is activated, deactivated, then reactivated it will return the last value available before it was suspended rather than the current live value. This behavior does not occur if SOD is disabled.
	</td></tr>
<tr>
	<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00099445</span></td>
	<td>With SQL Server 2008 installed, and Wonderware Application Server 3.1 SP2 installed (IDE and Bootstrap only), attempting to add a Galaxy Repository using <b> Modify, add GR </b> (<b>Add/Remove Programs, Change</b> option) fails as the Add GR option does not automatically run the aaConfigSQL utility. WWCdi and WWPackageServer errors appear in the logger. This occurs only with SQL Server 2008 installed, and only when the initial Wonderware Application Server installation was performed using a local account. 
<p>As a workaround, you can run the aaConfigSQL utility manually prior to running the <b>Modify, Add GR</b> option. </p>
	</td></tr>
<tr>
	<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00099447</span></td>
	<td>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.
	</td></tr>
<tr>
	<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00099472</span></td>
	<td>On Windows Server 2008 32/64-bit and Windows Vista 32/64-bit operating systems, with Wonderware Application Server installed from CD media rather than from a network location or local install folder, adding a Galaxy Repository using the <b>Modify, add GR</b> option (<b>Add/Remove Programs</b>) fails to add a GR. Modify fails to find the path to setup.msi. This issue does not occur with Windows Server 2003 SP2. 
<p>As a workaround, you can run the Modify option from the CD image with elevated privileges. </p>
	</td></tr>
<tr>
	<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00099557</span></td>
	<td>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.  
<p>As a workaround, reopen the symbol and use the <b>Custom Properties</b> dialog box to populate the custom property values.</p>
	</td></tr>
 

 <tr><td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00104907:</span></td>
	<td>Tooltip animations are not working for WCC controls.
</td></tr>


<tr><td> </td></tr><tr>
<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00105138:</span></td>
	<td>On the Windows Server 2008 and 2008 R2 operating systems, the UI controls for the $WinPlatform derived template do not align correctly.
	<p>Workaround: Right-click <b>Computer</b> and then click <b>Properties</b>. Click <b>Advanced system settings</b>, and then click the <b>Advanced</b> tab. In the <b>Performance</b> area, click <b>Settings</b>. Click to clear the <b>Smooth edges of screen fonts</b> check box. 
</p></td></tr> 
 
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00106038:</span></td>
	<td>Errors are logged while deploying PEM objects. Factelligence 3.5 (PEM, FMM, MEM) objects are not supported in the current version of Wonderware Application Server. Upgrade to MES version 4.0 or higher is required.	
	</td></tr>
	
<tr><td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00106046:</span></td>
<td>On Windows Server 2008 R2 64-bit and Windows 7 32-bit operating systems, if you attempt to uninstall Wonderware Application Server while the IDE is open or while connected to a Galaxy, you will see a warning message. If you click <b>Retry</b>, without closing the IDE or Galaxy connection, Wonderware Application Server will continue to uninstall as if you had selected the <b>Ignore</b> option. 
</td></tr>

<tr>
<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00106124</span>:</td>
<td>Importing objects built in AOT 3.1 or higher, minor version upgrade, can take a long time even if the object is changed only for editor assembly. Use the following steps to create an AOT object with minor version changes which should contain only editor changes and no changes in package logic:
<blockquote>
<ol>
<li>Open the base version AOT 3.1 or higher object in Visual Studio and do the required changes to the editor.
</li><li>To bump up the <code>&lt;Object name&gt;Editor1.dll</code> file version by modifying the file version information in the <b>AssemblyInfo.cs</b> file in the following example "&lt;Object name&gt;Editor" project: <br>
		<code>assembly: AssemblyFileVersion("1.2.0.0")</code>
		&nbsp;
</li><li>To bump up the object's minor version modify the <b>&lt;Object name&gt;.cs</b> file in the following example "&lt;Object name&gt;.cs" project:<br>
		<code>ObjectAttributes.MinorVersion(2)</code>
</li><li>Rebuild the object to get an object with a minor version change containing changes in the editor only.</li>
</ol>
</blockquote>
</td></tr>

<tr>
<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00106403:</span></td>
	<td>If extensions (InputOutput, Input, Output, Alarm, or History) are added to a Field Attribute via the <b>Extensions</b> tab and the Field Attribute is later renamed, the Field Attribute's configuration structure can become corrupted.
<p>Workaround: Configure Field Attributes using only the options available on the <b>Field Attributes</b> tab in the editor of the $UserDefined object; do not configure a Field Attribute using options from the <b>Extensions</b> tab of the editor.

</p></td></tr>	
	
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00106782:</span></td>
	<td>Certain IDE operations performed under the following configuration are much slower on Windows Server 2008 R2 and Windows7 operating systems than on earlier releases of Microsoft Windows:
	<ul style="LIST-STYLE-TYPE: disc">
	<li>The GR-node is a member of DomainA. 
	</li><li>The interactive (logged-in) user on the GR is a member of DomainA. 
	</li><li>The ArchestrA Network User is an account in DomainB. 
	</li><li>The network connection to the DomainB Domain Controller is slow (little bandwidth, high latency).</li></ul>
	<p>The following operations may slow down by a factor of 2 or 3:
	</p><ul style="LIST-STYLE-TYPE: disc">
	<li> Editing objects.
	</li><li> Deploying objects. 
	</li><li> Deleting objects.</li></ul>
	 
	 <p><b>Workaround:</b></p> <ol><li>Ensure the network connection between the GRnode/IDEnode and the domain controller (that the ArchestrA network user is a member of) is fast and has low latency. 
	 </li><li>Have the Galaxy nodes, the interactive user (logged in user) and ArchestrA Network user all are members of the same domain.</li></ol>
	 <p>For more information, see Tech Note #719.

</p></td></tr><tr>
<td style="text-align: left; vertical-align:top; font-weight: bold;">L00107322:</td>
      <td style="text-align: left; vertical-align: top;">The Windows Server 2008 R2 (64-bit) operating system running on VMware occasionally "locks up" or "hangs," and the user interface is no longer responsive (although tasks may still run in the background). This problem is not related to any software application installed on the computer and can be corrected by upgrading the VMware video driver. To upgrade VMware video drivers, you must upgrade the VMware tools, which includes all the drivers for the system.

<p>This problem was experienced during testing of this release using the following VMware Software:</p>

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

<p>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: <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011709">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1011709</a>.</p>

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

</td></tr>



<tr>
<td style="text-align: left; vertical-align:top; font-weight: bold;">L00107919: </td>
      <td style="text-align: left; vertical-align: top;">When you log on to the ArchestrA System Management Console (SMC) Platform Manager with a newly-created, Active Directory OS Group account for Wonderware Application Server, and that OS Group account does not contain a "Full Name" description, the following error is generated: "User does not belong to any of the configured Roles". This also occurs when you log on to an InTouch application or Object Viewer.

<p>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.</p>
</td></tr>

	 
<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00108399:</td>
<td>When saving an object ("myudax0" in this example) that has a User Defined Attribute (UDA) with input extension created using GRAccess with the buffered data property enabled, the follow error message is displayed: <b>Buffered enabled UDA 'myudax0' does not have an input source.</b> <p>As a workaround, add the extension in GRAccess with type "inputextension" instead of "InputExtension". </p>
</td>
</tr>

<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00108539:</td>
<td>The following message is displayed when AOT tries to connect to a Galaxy from an out-of-sync IDE node even though there are no other clients connected to the same Galaxy:<br>
<blockquote>Test Galaxy<br>

Connection to Galaxy 'Test' failed.<br>
Text: Unknown error.<br>
CustomMessage: Cannot Synchronize client as other clients are active.<br>
OK 
</blockquote>
As a workaround, synchronize the Galaxy through the IDE first and then start the AOT.
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00109396:</td>
<td>The following warning is logged in IDE and Bootstrap nodes during upgrade of an undeployed galaxy:<br>
<blockquote>Warning msiexec GetArchestrAInstallPath(): Failed to Read the Registry ArchestrA install path Key."
</blockquote>
There is no workaround required. The error message does not impact the node upgrades. 
</td>
</tr>


<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00110185:</td>
<td> Remote Platforms are unable to be deployed if the Galaxy Repository and remote nodes have same domain user, but one is specified by the fully-qualified domain name (mydomain.xxx.mycompany.com) and the other by just the domain name (mydomain). The following error message is shown: "Error: Failed to deploy WinPlatform_002 : Remote Node's UserId/Password don't match GR Node's."<p></p>

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


</td>
</tr>
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112178</span>:</td>
    <td><span style="FONT-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"></span>Objects built using ArchestrA Object Licensing Toolkit (AOLT) version 1.0 are not compatible with Wonderware Application Server 3.5 (2012). You must rebuild the objects with AOLT version 1.1 licensing.</td></tr>
	
<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00112189:</td>
<td> Installing Wonderware Application Server on a computer used as a domain controller is not supported.
</td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113652</span>:</td>
    <td> If you import objects that have dependencies in scripting to custom DLLs and if these custom DLLs are not present in the Galaxy, these objects being imported are placed in an error condition. <br><br>As a workaround, you can import the custom DLLs used by scripts and validate the objects being imported to resolve this issue.
  </td></tr>
 
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113709</span>:</td>
    <td><span style="FONT-FAMILY: &#39;Calibri&#39;,&#39;sans-serif&#39;; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"></span>Objects created in Wonderware Intelligence 1.1 are not compatible with Wonderware Application Server 3.5.</td></tr>
 <tr>

    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115036</span>:</td>
    <td>If the identity of a ShowGraphic script is already in use, the graphic opened with that same identity will be replaced. During the replacement process, the OnHide script of that graphic will not be executed. <br><br>As a workaround, use a HideGraphic script or a HideSelf script first to hide the open graphic. Then use a ShowGraphic script to open a new graphic.
  </td></tr>
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115135</span>:</td>
    <td>In the OPCClient object, the installed DAServers are not listed under the Server Name. For the OPCClient object, the following error message is shown in the SMC log:<br><br>
.Net Editor Info - 17:35:14.3125809<br>  
Failed to create instance of OPCEnum on server node COMPST01: 0x80040153<br><br> 
As a workaround, if you invert the installation sequence by installing the OPC Server first and then the Bootstrap, the OPCEnum is installed without anonymous logon and  a remote connection to the OPC Server is possible. 
You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission. 
  </td></tr>


  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115589, L00115710, L00116055</span>:</td>
    <td>Any deployed InTouchViewApp instance that is configured to include all Galaxy graphics is incorrectly marked as pending a change if you:
<p>
</p><ul>

<li>Undeploy an object instance with an inherited graphic.</li>

<li>Perform an IDE operation after deploying of an object instance with an inherited graphic. Examples of IDE operations are renaming an instance, editing an instance and then closing without saving, adding a user-defined attribute, and so on. This can done on any object with or without graphics.  </li>

<li>Import a new client control into the Galaxy.</li>

<li>Delete an unused client control (not referenced by any graphic) from the Galaxy.</li>
</ul>
<p></p>
 
  </td></tr>


  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115681</span>:</td>
    <td>If you configure an <b>InTouchViewApp </b> object and select the <b>Include all galaxy graphics with this application</b> check box, when you export the object to another Galaxy, the new <b>InTouchViewApp</b> object will not have this option selected. You must manually select the option again. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115869</span>:</td>
    <td> If a field attribute is configured as buffered and has an input extension to a non-buffered user-defined attribute, the field attribute returns bad quality even though the value updates. In order to get good quality, configure the input extension to a buffered user-defined attribute. 

</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116266</span>:</td>
    <td>The database transaction log can significantly increase in size after migration of .cab files. As a workaround, use the Galaxy Database Scrubber utility to improve the operating performance of your Galaxy database. Also, you can increase the hard drive size. Follow the guidelines provided under <b>Minimum Hardware Requirements</b> in this Readme. 

	

</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116279</span>:</td>
    <td> If there are bad visual element references in an object, warnings occur in the Logger when the object is deployed. To get the name of the object using the visual element ID from the log message, run the following SQL query against the Galaxy Repository database:

<p></p>
<code>
select pri.tag_name ObjectName, pri.primitive_name SymbolName, pri.visual_element_id<br>
from visual_element_reference ver<br>
inner join internal_visual_element_description_view pri<br>
on pri.gobject_id = ver.gobject_id and<br>
pri.package_id = ver.package_id and<br>
pri.mx_primitive_id = ver.mx_primitive_id<br>
where  ver.checked_in_unbound_visual_element_name is null<br>
and ver.visual_element_bind_status = 0<br>
and pri.visual_element_id = &lt;visual element id&gt;<br>
</code>


 
</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116317</span>:</td>
    <td><b> SR 20114029:</b> If you rename an ActiveFactory control that is used in an ArchestrA symbol before you export the object containing the symbol, and you then import the object into a Galaxy that contains a newer version of the same control, the import of the older control is skipped. By design, if a newer version of a client control already exists in the Galaxy, then the import of an older version of the client control is skipped. However, the control reference in the symbol retains the name change. Because the target Galaxy does not contain a control by this name, the object goes into warning and the "symbol not found" text is shown.  

<p>To avoid this, do either of the following:</p>
<ul>
<li>Make sure that the name of the control matches the version in the target Galaxy before you perform the export.</li>
<li>Rename the control in the target Galaxy to match the one in the export file. Make sure that the reference in the symbol is updated after you rename the control.</li>
</ul>

</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116381</span>:</td>
    <td>After opening a ShowGraphic() modal symbol from a container script that takes an expression as input, such as a data change script, all data subscriptions are blocked in the base symbol. As a workaround, open the ShowGraphic() symbol from an action script. 


</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116422</span>:</td>
    <td>Opening a pop-up symbol from a ShowGraphic() script is different from opening the same symbol from Show Symbol animation, and Window Viewer occasionally hangs on script execution. Although you can use the ShowGraphic() script
functions inside container scripts, you cannot use ShowGraphic() in WhileTrue or periodic scripts such as WhileShowing.

 
</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116459</span>:</td>
    <td>A remote node fails to connect to an WWALMDB database that is created using SQL Express Edition.<br><br>
	<b>Workaround:</b> Change the SQL Server Express authentication from Windows mode to Mixed mode.<br><br>
	<b>To change SQL Server Express Authentication mode</b>
	<ol type="1">
<li>Download and install the x86 version of SQL Server 2008 Management Studio Express from <a href="http://www.microsoft.com/download/en/details.aspx?id=7593"> http://www.microsoft.com/download/en/details.aspx?id=7593</a>.
</li><li>After installation, right-click <b>SqlExpress Connection</b>, click <b>Properties</b>, and then click <b>Security</b>.
</li><li>Change the SQL Server Express authentication from Windows mode to Mixed mode and click <b>OK</b>.
</li><li>Restart the database instance or computer.</li></ol>

</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116508</span>:</td>
    <td>Writing to a secured array attribute using the SignedWrite() function can result in a .NET error in WindowViewer. Writing to an array is not supported. Instead, you can write to an array element. 


</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116555</span>:</td>
    <td>If two pop-up windows open in InTouch WindowViewer, one from a ShowGraphic script and another from a ShowSymbol animation, then you cannot close the pop-up windows.<br><br>
	<b>Workaround:</b> In the modeless <b>ShowSymbol</b> dialog box, click the <b>Push</b> button with the ShowSymbol animation.
	This <b>Push</b> button that is already selected changes, and you can interact with <b>ShowSymbol</b> dialog box.
</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116641</span>:</td>
    <td>If you attempt to acknowledge an alarm from an Alarm Control list with a Smart Card reader installed, but open the certificate list in the <b>Ack Alarms</b> dialog and remove the smart card, then click the empty certificate list, the system will display an error and fail to acknowledge the alarm. 
	

	
</td></tr><tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116828</span>:</td>
    <td>If you attempt to modify the value of a UDA configured with Secured Write or Verified Write security classification  using the MxAccess sample ActiveX control in InTouch, the value will not change as expected. As a workaround, the write to a Secured Write UDA value will succeed after you log on to InTouch with operator credentials. However, this workaround does not affect the issue of being unable to modify the Verified Write UDA value. 
 

 <!-- 
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115712</span>:</td>
    <td>If the identity in the ShowGraphic script function is already in use while you open a graphic, 
	then the graphic that was opened earlier with the same identity will be closed. 
	However, the OnHide script function is not executed on the closing graphic.<br> 
<p>As a workaround, you need to use the HideGraphic or HideSelf script function to hide the already opened graphic first, 
and then use the ShowGraphic script function to open the new graphic.</p>
  </td></tr>  
 !-->

</td></tr></tbody></table>
 
</p><p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a><br>
</p><hr>

<h2><a name="Known_Issues312"></a><a name="Wonderware Application Server Documentation Issues"></a>Wonderware Application Server Documentation Issues 
</h2><p>The following table lists all documentation corrections to Wonderware Application 
Server 2012 (version 3.5) documentation.</p> 
<table style="TEXT-ALIGN: left; WIDTH: 675px" border="1" cellspacing="2" cellpadding="2">
  <tbody>
  <tr>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top; FONT-WEIGHT: bold">Item</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top; FONT-WEIGHT: bold">Location 
      of Change</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top; FONT-WEIGHT: bold">Existing 
      Documentation</td>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top; FONT-WEIGHT: bold">Change</td></tr>

   <tr>
    <td style="TEXT-ALIGN: center; VERTICAL-ALIGN: top">2</td>
    <td style="VERTICAL-ALIGN: top">OPCClient Object Help (help.htm), <br><br>"Overview" section</td>
    <td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">n/a</td>
    <td style="VERTICAL-ALIGN: top">In the "Overview" section, insert a new subsection "OPC Client Reconnection" (following the existing "Block Reads and Block Writes" subsection):<br><br>
	Following is the OPC Client connect/reconnect behavior: 
<ol>
<li>When the OPC Client starts, it will immediately attempt to connect.</li>
<li>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.</li>
<li>When the OPC Client connects, it will set RestartCnt to 0 and lower the RestartAlarm.</li>
<li>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.</li>
</ol>
<p>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.</p>
	</td></tr>
</tbody></table><p></p>

<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>

<h2><a name="Wonderware Application Server Documentation"></a>Wonderware Application Server Documentation</h2><p>The Wonderware Application Server product library consists of a set of Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:<br>
\Archestra System Platform\CD-ApplicationServer\UserDocs\English
<br><br>You need Adobe Reader installed on your computer to view 
Wonderware Application Server documentation. You can download the latest version of Adobe 
Reader from the Adobe Corporation web site:</p>
<p><a href="http://www.adobe.com/products/acrobat/readstep2.html">http://www.adobe.com/products/acrobat/readstep2.html</a></p> 
<p>After installing Adobe Reader, double-click 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 <span style="FONT-WEIGHT: bold">Open</span> command from the <span style="FONT-WEIGHT: bold">File</span> menu. 
Product documentation is also available with Wonderware Application Server online help.</p> 
<h3>Documentation Set </h3><p>The Wonderware Application Server documentation set includes the 
following guides:</p> 
<ul style="LIST-STYLE-TYPE: disc">
  <li><span style="FONT-STYLE: italic">Wonderware Application Server User's 
  Guide</span>. Explains configuring and deploying Wonderware Application Server 
  applications. 
  </li><li><span style="FONT-STYLE: italic">Creating and Managing ArchestrA Graphics 
  User's Guide</span>. Explains how you create and manage graphical symbols 
  using the ArchestrA Symbol Editor within the Integrated Development 
  Environment (IDE). 
  </li><li><span style="FONT-STYLE: italic">Application Server Scripting 
  Guide</span>. Reference for the scripting language in Application Server. 
  </li><li><span style="FONT-STYLE: italic">Object Viewer User's Guide</span>. 
  Explains how to acquire run-time data using the Object Viewer. 
  </li><li><i>Guide to the ArchestrA Alarm Control</i>. Explains 
  how to configure the alarm control (client) to show current and historical 
  alarms and events in a grid. 
  </li><li><i>Guide to the ArchestrA Trend Client</i>. Explains 
  how to configure a chart to trend real-time data values. 
  </li><li><span style="FONT-STYLE: italic">Platform Manager User's Guide</span>. 
  Explains how to start and stop system components. 
  </li><li><span style="FONT-STYLE: italic">Galaxy Database Manager User's 
  Guide</span>. Explains how to backup and restore the Galaxy database. 
  </li><li><span style="FONT-STYLE: italic">Log Viewer User's Guide</span>. Explains 
  how to use the Log Viewer utility to determine system diagnostics. 
  </li><li><span style="FONT-STYLE: italic">Log Flag Editor Utility Guide</span>. 
  Explains how to turn on and off certain diagnostics logging messages. 
  </li><li><span style="FONT-STYLE: italic">Wonderware FactorySuite License Utility 
  Guide</span>. Explains how to use the License Utility to manage the license 
  required for the running application. 
  </li><li><span style="FONT-STYLE: italic">Wonderware ArchestrA Protocol 
  Guide</span>. Explains background information on the main protocols used 
  between components of Wonderware products. 
  <!--
  <li><span style="FONT-STYLE: italic">Application Server Installation 
  Guide</span>. Explains information about installing the product. 
  !-->
  </li><li><span style="FONT-STYLE: italic">InTouch HMI and ArchestrA Integration Guide</span>. 
  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. available in the following location in the ArchestrA System Platform DVD: <br>
\Archestra System Platform\CD-Intouch\UserDocs\English
 <br></li></ul>
  <p>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.</p> 
<h3>Searching Wonderware Application Server Books with Adobe Reader </h3><p>The Wonderware 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 Wonderware Application Server product 
library.</p> 
<p class="bold">To search for information across all Wonderware Application Server books 
simultaneously</p>
<ol type="1"> 
<li>Open Adobe Reader. 
</li><li>Press <span style="FONT-WEIGHT: bold">CTRL+SHIFT+F</span> or select <span style="FONT-WEIGHT: bold">Search</span> from the <span style="FONT-WEIGHT: bold">Edit</span> menu. The <span style="FONT-WEIGHT: bold">Search</span> dialog box appears. 
</li><li>Type the word or phrase that you want to search for in the Application 
Server books. 
</li><li>In the <span style="FONT-WEIGHT: bold">Where would you like to search</span> 
area, select the option to search all PDF books. 
</li><li>If necessary, locate the Wonderware Application Server 3.2 PDF package located 
on your Wonderware CD or on a network folder containing 
copies of the Wonderware Application Server PDF book files. 
After product installation, these files can be found at:&lt;driveletter&gt;:\Program 
Files\ArchestrA\Framework\Docs. 
</li><li>Click <span style="FONT-WEIGHT: bold">Search</span>. Adobe Reader lists the 
Wonderware Application Server books that contain a match for your search criteria. 
</li><li>Click the links to open the Wonderware Application Server book to the topic 
containing the information that meets your search criteria. </li></ol>
<p class="right"><a title="Click this link to go to the top of the document." href="https://wdnresource.wonderware.com/support/patchfixes/1/ReadMe_WAS35P01.html#Top">&lt; top of document &gt; </a>
</p><hr>
<p>© 2011 Invensys Systems, Inc. All Rights Reserved.</p>
</body></html>