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

<html><head><title>Wonderware Application Server 2012 R2 Patch 02 Readme</title>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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:#FFFFFF;
	font-weight:bold;
	font-family:Verdana;
	font-size:18pt;
	background-color:#C3D603;
	margin-top:18pt
	margin-bottom:6pt
}

h2 {
	color:#000000;
	font-weight:bold;
	font-family:Verdana;
	font-size:16pt;
	margin-top:18pt
	margin-bottom:6pt
}

h3 {
	color:#000000;
	font-weight:bold;
	font-family:Verdana;
	font-size:12pt;
	margin-bottom:6pt
}

h4 {
	color:#000000;
	font-weight:bold;
	font-family:Verdana;
	font-size:10pt;
	margin-top:18pt
	margin-bottom:6pt
}

h5 {
	color:#000000;
	font-weight:bold;
	font-family:Verdana;
	font-size:9pt;
	margin-top:18pt
	margin-bottom:6pt
}

h6 {
	color:#FFFFFF;
	font-weight:bold;
	font-family:Verdana;
	font-size:8pt;
	background-color:#C3D603;
	margin-top:18pt
	margin-bottom:6pt
}

p {
	margin-left:2px;
	color:#000000;
	font-family:Verdana;
	font-size:12px;
	margin-top:6pt;
	margin-bottom:6pt;
}

p.right {
	text-align:right;
}

/*Created a note style to make all of the notes consistent.*/
p.note {
	border-top: 2pt solid #C3D603;
	border-bottom: 2pt solid #C3D603;
	padding-top: 2pt;
	padding-bottom: 2pt;
	margin-top:12pt;
	margin-bottom:12pt;
}

ul {
	margin-left:20px;
	font-family:Verdana;
	font-size:12px;
}

ol {
	margin-left:20px;
	font-family:Verdana;
	font-size:12px;
}

td {
	color:#000000;
	font-family:Verdana;
	font-size:12px;
}

hr {
	color:#FFFFFF;
	width:100%;
	height:1px;
	font-family:Verdana;
	font-size:12px;
	text-align:right;
}

title {
	color:#000000;
	text-align:center;
	font-family:Verdana;
	font-size:22px;
}

li {
	color:#000000;
	list-style:inherit;
	font-family:Verdana;
	font-size:12px;
	line-height:14pt;
	margin-bottom:4pt;
	margin-left:2px;
}

.center {
	text-align:center;
}

.bold {
	font-weight:bold;
}

.indent {
	margin-left:.1in;
	color:#000000;
	font-family:Verdana;
	font-size:12px;
	margin-bottom:4pt;
}

/*Created the several td styles below to make it easier to apply and globally
change table cell styles in the future.*/

td.cell {
	font-weight:normal;
	text-align:center;
	vertical-align:middle;
}

td.cellLeft {
	font-weight:normal;
	text-align:left;
	vertical-align:middle;
}

td.cellSmall {
	font-weight:normal;
	font-size:0.6em;
	text-align:center;
	vertical-align:middle;
}

td.supported {
	background-color:#FFFFFF;
	font-weight:normal;
	text-align:center;
	vertical-align:middle;
}

td.supportedRecommended {
	background-color:#FFFF99;
	font-weight:normal;
	text-align:center;
	vertical-align:middle;
}

td.smallsystemSmall {
	background-color:#eaaf0f;
	font-weight:normal;
	font-size:0.6em;
	text-align:center;
	vertical-align:middle;
}

td.supportednot {
	background-color:#FFC3AB;
	font-weight:normal;
	text-align:center;
	vertical-align:middle;
	color:#D81C3F;
}

td.supportedSmall {
	background-color:#FFFFFF;
	font-weight:normal;
	font-size:0.6em;
	text-align:center;
	vertical-align:middle;
}

td.supportedRecommendedSmall {
	background-color:#FFFF99;
	font-weight:normal;
	font-size:0.6em;
	text-align:center;
	vertical-align:middle;
}

td.supportednotSmall {
	background-color:#FFC3AB;
	font-weight:normal;
	font-size:0.6em;
	text-align:center;
	vertical-align:middle;
	color:#D81C3F;
}

td.colhead {
	background-color:#c3d603;
	font-weight:bold;
	text-align:center;
	vertical-align:bottom;
}

td.colheadSmall {
	background-color:#c3d603;
	font-weight:bold;
	font-size:0.6em;
	text-align:center;
	vertical-align:bottom;
}

td.rowhead {
	background-color:#eaaf0f;
	font-weight:bold;
	text-align:left;
	vertical-align:middle;
}

td.rowheadSmall {
	background-color:#eaaf0f;
	font-weight:bold;
	font-size:0.6em;
	text-align:left;
	vertical-align:middle;
}

td.gray {
	background-color:#adafaf;
	text-align:left;
}

td.graySmall {
	background-color:#adafaf;
	font-size:0.6em;
	text-align:left;
}


  </style>

<meta content="MSHTML 6.00.2900.3132" http-equiv="GENERATOR"><basefont size="12px" face="verdana, arial, tahoma, helvetica">
<div style="TEXT-ALIGN: center"></div>

<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 R2 (version 3.6) Patch 02 Readme</h1>
<p>Last revision: 05/27/2014 </p>

<p>This document contains three separate Readme files; the current release, and the two prior releases as shown in the following section: 
<ul> 
<li>Wonderware<sup>&reg;</sup> Application Server 2012 R2 Patch 02</li>
<li>Wonderware<sup>&reg;</sup> Application Server 2012 R2 Patch 01</li>  
<li>Wonderware<sup>&reg;</sup> Application Server 2012 R2</li>
</p> 


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

<ul>
<li><b>Installation</b> - Wonderware Application Server 2012 R2 (v3.6.000) or 2012 R2 P01 (v3.6.001) must be installed before you can install this patch.</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.</li>-->

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


<li><b>UAC</b> - Disable UAC before installing Wonderware Application Server 2012 R2 (v3.6) and InTouch HMI 2012 R2 (v10.6), applicable for Windows Vista and above operating systems.</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  R2 (v3.6) Patch 02 and InTouch HMI 2012 R2 (v10.6) Patch 02, 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>

<h3>Wonderware Application Server 2012 R2 (v3.6) Patch 02 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="#A - P02">Applying Patch 02 to Wonderware Application Server Version 2012 R2 (v3.6)</a>
<!--<p><a href="#Known Issues">Known Issues - Wonderware Application Server 2012 (v3.5) Patch 01</a>-->
<p><a href="#RI- WAS 3.1 SP3_Patch02">Resolved Issues -  Wonderware Application Server 2012 R2 (v3.6) Patch 02</a>
<p></p>
<br>


<h3>Wonderware Application Server 2012 R2 (v3.6) 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="#A - WAS 3.1 SP3">Applying Patch 01 to Wonderware Application Server Version 2012 R2 (v3.6)</a>
<!--<p><a href="#Known Issues">Known Issues - Wonderware Application Server 2012 (v3.5) Patch 01</a>-->
<p><a href="#RI- WAS 3.1 SP3_Patch01">Resolved Issues -  Wonderware Application Server 2012 R2 (v3.6) Patch 01</a>
<p></p>
<br>



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



<!--<A href="#About Wonderware Application Server 3.5">About Wonderware Application Server 2012 R2 (version 3.6)
</A> 
<P><A href="#Antivirus Software Exclusions">Antivirus Software Exclusions</A> 
<P><A href="#Minimum Hardware Requirements">Minimum Hardware Requirements</A> 
<P><A href="#Software Requirements and Compatibility">Software Requirements and Compatibility</A>
<P><A href="#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>-->
<!--<A 
href="#Installing Wonderware Application Server 3.5">Installing Wonderware Application Server 3.5
</A> -->
<p><A href="#AppServer 2012 R2 Readme">Wonderware Application Server 2012 R2 (v3.6) Readme</a></p>
<!--<P><A href="#Upgrading to Wonderware Application Server 3.5">Upgrading to Wonderware Application Server 2012 R2 (version 3.6)</A> 
<P><A href="#Migrating to Wonderware Application Server 3.5">Migrating to Wonderware Application Server 2012 R2 (version 3.6)</A>-->
<P><A href="#Known Issues">Known Issues - Wonderware Application Server 2012 R2 (version 3.6)</A>
<P><A href="#Resolved Issues">Resolved Issues - Wonderware Application Server 2012 R2 (version 3.6)</A>
<!--<P><a href="#Documentation Issues">Wonderware Application Server Documentation Issues</A> -->
<!--<P><A href="#Wonderware Application Server Documentation">Wonderware Application Server Documentation</A>
<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 - P02"></a>Applying Wonderware Application Server 2012 R2 (v3.6) Patch 02</h1>

<p>Close any anti-virus programs running on the computer before you update 
Wonderware Application Server with Patch 02. </p>
<p>Apply this patch <span class="bold">only</span> to Wonderware Application Server 2012 R2 (v3.6.000) or Wonderware Application Server 2012 R2 P01 (v3.6.001). You can check the version number in the Control Panel under <span class="bold">Add or Remove Programs</span> (aka <span class="bold">Programs and Features</span>).</p> You can confirm this patch has been installed on a node by verifying the version number is 3.6.002.

<p class="note"><b>Note:</b> You can install Wonderware Application Server 2012 R2 (v3.6) Patch 02 without installing the Wonderware Application Server 2012 R2 (v3.6) Patch 01.</p>

<p><span style="FONT-WEIGHT: bold; FONT-SIZE: 14px; 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 R2 (v3.6) Patch 02 and InTouch 2012 R2 (v10.6) Patch 02 in order for them to coexist.</b></p>
<p class="note"><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 02 to both nodes. A remote connection between the 
  ArchestrA IDE and the Galaxy Repository fails if the nodes are at different 
  versions of Wonderware Application Server. </li>
  <ul>
    <li>An ArchestrA IDE node still at version 3.6 cannot connect to a remote GR node updated with Patch 02. </li>
    <li>An ArchestrA IDE node updated with Patch 02 cannot connect to a remote GR node still at version 3.6. </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 02 on the GR node, ensure any active remote IDE 
  sessions are disconnected. Patch 02 requires ArchestrA-related processes be 
  shut down and may require a reboot.</li>
  </ul>


<!--<h1><a name="Known Issues"></a>Known Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 01</h1>
<p>This section describes known issues in Wonderware Application Server 2012 R2 (v3.6) Patch 01.</p>

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

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127324:</span></td>
    <td>Repeatedly opening and closing InTouch View windows containing ArchestrA symbols which reference Application Objects can result in significant memory usage increases in WindowViewer, which appears in Windows Task Manager as view.exe. As a workaround, close and restart WindowViewer. </td>
</tr>

</tbody></table>-->


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

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00107457:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 30712432/30711916:</b> The "Lost Alarm Communication" alarm priority was set to 1, which prevented use of that priority for other alarm conditions. This issue has been resolved. You can now manually create a registry entry to provide the alarm priority on all platforms as follows: <br>
<OL><li>Create new registry key "Alarms" under section "HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\" </li>
<li>Create new DWORD value "CommunicationErrorAlarmPriority", and set the value (priority) between 0-999 (Use the decimal option when setting the value.) </li>
<li>If the value for CommunicationErrorAlarmPriority is not set or is out of range, the default value "1" is used.</li></OL>
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122043:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 43110215:</b> Error "Failed to deploy <PcName>: Failed to get the bootstrap's version" occurred while deploying a platform to a Windows 7 client. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124709:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 41610463:</b> Platforms did not deploy correctly and IDE freezes occurred on Windows 7 client nodes. 
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124824:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 43610739:</b> When using FSGateway in a multi-galaxy configuration and adding a large number tags to FSGateway using an OPCClient tags got stuck in an initializing state. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125013:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 22318077:</b> Items created with syntax &lt;DIObjectName&gt;.&lt;TopicName&gt;.&lt;Attribute(ItemName)&gt; would go from bad to good quality repeatedly if the Buffered Data option was checked for a User Defined Attribute (UDA).  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125088:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><b>SR 48910069:</b> Field Attributes did not show the correct value unless configured for Buffered Data, and Integer Field Attribute values could not be set to zero if the initial value of the Field Attribute was other than zero. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125123:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 37112904:</b> Multiple issues occurred with the OPCClient Object, such as performance and reconnect, engine scan overruns even when the object was idle, block read and block write triggers were slow and disconnect behaviours were mishandled.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125295:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 14832266:</b> Adding dynamic primitives for some attributes failed due to a name conflict in the database. An error is now logged when adding a dynamic primitive conflicts with a graphic that has an identical name.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125485:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 44510170:</b> When more than one instance of the MxAccess ActiveX sample was registered in an InTouch application, unregistering one MxAccess sample ActiveX control caused WindowViewer to hang.  
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125741:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 31611867:</b> The System.String.Join function returned "System.String[]" instead of the actual value of the array string. 
 </td>
</tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00126318:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 14832305/15712683:</b> A re-registration issue in the alarm NotificationDistributorRuntime reactivated old alarms that could then not be acknowledged.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00126469:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 43110295:</b> Deploying a redundant engine that has areas and objects without selecting the <b>Cascade Deploy</b> option  resulted in the loss of all running objects.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00126489:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 27811031:</b> Alarms on a remote node, queried through a remote desktop session, intermittently could not be seen.   
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00126520:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 45510344:</b> An InTouch Window with ArchestrA graphics required more than normal time to save. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127372:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 14413640:</b> Reads and writes from a third-party OPCClient via FSGateway to a User Defined Attribute (UDA) could not be done when using Chinese characters.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127379:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 45110257:</b> Both primary and redundant engines went active at the same time. 

</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127643:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 43110295:</b> Areas and contained objects showed warning messages after validation.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127759:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 43110326:</b> The DiscreteDevice object showed incorrect values when the <b>Advanced Communication Mode</b> was enabled.  
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00128024:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 46810184:</b> With the regional settings set to German, switching to ArchestrA security added a suffix of .5 to all analog tags when shown as text strings.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00128094:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 49410008:</b> Instances with bad items that did not exist in the PLC caused a slow down of the AppEngine until it ceased responding.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00128535:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
ArchestrA Workflow Server 2012 R2 SP1 Gateway objects could not be configured on Wonderware Application Server 2012 R2 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00128546:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 15712744:</b> Pokes to Application Object attributes failed when OSGroup-based security was configured and integrated with FSGateway. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00128575:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 45110229:</b> Loading a Galaxy from a .csv file required a long time even though few parameters had changed. 
</td>
</tr>
<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129017:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103129747:</b> The "Enable state label" for a Discrete Field Attribute did not work for OPR events.  
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129089:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 37112888 and SR 103128979:</b> When a remote data source node time synced, a "timestamp out of sequence" warning was logged for every item being polled. This log warning is now set under a custom log flag, "Log OutofSyncTimestamps", which is disabled by default. The "timestamp out of sequence" warning will not appear in the logger unless the custom log flag is enabled.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129116:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103128979:</b> Two systems were successfully time synced after drifting out of sync, but an excessive number of messages were reported to the OPCClient. These messages were benign, but had the potential to fill the log. 
</td>
</tr>
<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129089:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 37112888 and SR 103128979:</b> When a remote data source node time synced, "timestamp out of sequence" warnings occurred for every item being polled.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129496:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103130007:</b> Object Viewer showed incorrect Boolean array values from a BACnet OPC Server, but the individual array elements showed correct values.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129575:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103129209:</b> Some graphics were lost while importing a new Galaxy version and then overriding the objects.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129833:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 41810243:</b> The RDI object was in disconnected state while both source DI objects were partially connected.  
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00129813:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103129988:</b> Attempting to access the system using smart card credentials resulted in the error message "User does not belong to any of the configured roles." With operating system security, InTouch uses the user name obtained from the "Common Name" attribute of a certificate to log on with a Smart Card. In this case, the user name specified by the "Common Name" attribute differed from the operating system user name. 
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00130333:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 33812522:</b> WindowMaker displayed a red X when selecting an alternate instance on an embedded ArchestrA Graphic where the instance of the object had containment with another object instance. 
 </td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00130716:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 19818424:</b> A corrupted symbol in an Object disabled the Symbol editor "embed graphic" functionality. The GraphicBrowserControl displayed an error and became unresponsive. 
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00131142:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 33411322:</b> Error occurs when using Write2() and advise the item using AdviseSupervisory ().
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00131224:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 42010087:</b> Incorrect mapping of the item resulted in an error in SMC.
 </td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00131389:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103130791:</b> Ondatachange event is generated continuously when the Field Attribute is configured with scaling.

 </td>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00131391:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 40215771:</b> On the HMI, graphic shows an alarm state when there are no active alarms because the quality of "InAlarm" gets stuck in the "Initializing" state. 

 </td>
</tr>

</tbody></table>



<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>



<h1 class="center">Wonderware Application Server 2012 R2 (version 3.6) Patch 01 Readme</h1>
<p>Last revision: 07/31/2013 </p>

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

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

<ul>
<li><b>Installation</b> - Application Server 2012 R2 (v3.6) must be installed before you can install this patch. </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.</li>-->

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


<li><b>UAC</b> - Disable UAC before installing Wonderware Application Server 2012 R2 (v3.6) and InTouch HMI 2012 R2 (v10.6), applicable for Windows Vista and above operating systems.</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  R2 (v3.6) Patch 01 and InTouch HMI 2012 R2 (v10.6) 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>

<h3>Wonderware Application Server 2012 R2 (v3.6) 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="#A - WAS 3.1 SP3">Applying Patch 01 to Wonderware Application Server Version 2012 R2 (v3.6)</a>
<!--<p><a href="#Known Issues">Known Issues - Wonderware Application Server 2012 (v3.5) Patch 01</a>-->
<p><a href="#RI- WAS 3.1 SP3_Patch01">Resolved Issues -  Wonderware Application Server 2012 R2 (v3.6) Patch 01</a>
<p></p>
<br>



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



<!--<A href="#About Wonderware Application Server 3.5">About Wonderware Application Server 2012 R2 (version 3.6)
</A> 
<P><A href="#Antivirus Software Exclusions">Antivirus Software Exclusions</A> 
<P><A href="#Minimum Hardware Requirements">Minimum Hardware Requirements</A> 
<P><A href="#Software Requirements and Compatibility">Software Requirements and Compatibility</A>
<P><A href="#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>-->
<!--<A 
href="#Installing Wonderware Application Server 3.5">Installing Wonderware Application Server 3.5
</A> -->
<p><A href="#AppServer 2012 R2 Readme">Wonderware Application Server 2012 R2 (v3.6) Readme</a></p>
<!--<P><A href="#Upgrading to Wonderware Application Server 3.5">Upgrading to Wonderware Application Server 2012 R2 (version 3.6)</A> 
<P><A href="#Migrating to Wonderware Application Server 3.5">Migrating to Wonderware Application Server 2012 R2 (version 3.6)</A>-->
<P><A href="#Known Issues">Known Issues - Wonderware Application Server 2012 R2 (version 3.6)</A>
<P><A href="#Resolved Issues">Resolved Issues - Wonderware Application Server 2012 R2 (version 3.6)</A>
<!--<P><a href="#Documentation Issues">Wonderware Application Server Documentation Issues</A>-->
<!--<P><A href="#Wonderware Application Server Documentation">Wonderware Application Server Documentation</A>
<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 R2 (v3.6) 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 R2 (v3.6). 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: 14px; 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 R2 (v3.6) Patch 01 and InTouch 2012 R2 (v10.6) Patch 01 in order for them to coexist.</b></p>
<p class="note"><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.6 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.6. </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>


<!--<h1><a name="Known Issues"></a>Known Issues - Wonderware Application Server 2012 R2 (v3.6) Patch 01</h1>
<p>This section describes known issues in Wonderware Application Server 2012 R2 (v3.6) Patch 01.</p>

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

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00127324:</span></td>
    <td>Repeatedly opening and closing InTouch View windows containing ArchestrA symbols which reference Application Objects can result in significant memory usage increases in WindowViewer, which appears in Windows Task Manager as view.exe. As a workaround, close and restart WindowViewer. </td>
</tr>

</tbody></table>-->


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


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00082941:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR22315571:</b> Custom help added to a derived template object appeared when help was invoked from instances but not from the derived template itself.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00087517:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> Deleting an InTouchViewApp template that was locked by another process resulted in an unclear dialog box and error message. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00093278:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103115883:</b> Level alarms configured on a Field Attribute were set to true immediately on breaching the alarm threshold even though the configured time deadband had not been exceeded.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00100718:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103117318:</b> Item references for Topic-specific Attributes did not appear when DIObjects are opened in Read-Only mode, but did appear when DIObjects were opened for editing. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00110869:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b> Under certain conditions, a symbol configured with an OnShow script could result at run time in the null reference error "Object reference not set to an instance of an object." 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116706:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103122399:</b> The LogDataChangeEvent function did not correctly log time in the EventStamp column, and entered 0 in the EventTimeZoneOffset column. Time logged in the EventTime column was correct.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119452:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 31712002:</b> The SQL database location defaulted to c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data, not to the location set by the SQL server.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119620:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>SR 103123957:</b> The ArchestrA Object Toolkit (AOT) DeleteAttribute() function resulted in the "Attempted to read or write protected memory..." error.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121185:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00120870: </b>The script execution order was inaccessible and the Configure Execution Order listbox disabled when opening the object editor for a read-only user defined derived template or instance. Scroll bars are now enabled for read-only templates or instances.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122784:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00122616:</b> The ScanGroupRuntime2 intermittently dropped writes resulting in unexplained Tag write time-outs and Batches being put on hold.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122845:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00122598 SR 45710085 and SR 103125662:</b> Importing an InTouch 9.5 application to InTouch 2012 failed and displayed "Import operation aborted. Source file is in ReadOnly Mode."
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122847:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00122678 SR 103125882:</b>  Using the SetAttributeVT function resulted in the error message, "Attempt to read or write protected memory."
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123014:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00121864:</b>Writing to an item from a scan group configured for a five (5) minute scan cycle did not return the value until after the next scan cycle. Implementing the Demand-Read After Write enhancement resolved the issue.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123287:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00123250:</b> Changes to a template description were propagated to instances with and without LOCK.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123729:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00121815 SR 25315245:</b> TSE sessions timed out, and the anonymous engine IDs were not recycled, resulting in the "CNmxAdapter :: GetAnonymousEngineID - FAILED" error message. 
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123778:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00123679:</b> When a two-way selective trust was enabled for the ArchestrA network account and one-way outgoing trust was enabled for all users, the IDE failed to open an object on first attempt. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123813:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR# L00123574 SR 10512085:</b> The redundant AppEngine failover displayed unknown errors and became quarantined because of a time constraint in the SetAttribute.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00123944:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00123705 SR 12912660:</b> Bootstrap failed to create an instance of Bootstrap on a remote machine, and displayed an "access denied" error message. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124013:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00124000:</b> Engine CPU usage stuck at 100-percent when engines tried to resubscribe with the remote platform. Communication had been lost between the platforms while an ESX server snapshot was being taken.  
</td>
</tr>
 
<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124108:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00122772 SR 43610579:</b> The Stats.Reset field was set to true, but did not set the elapsed times of the TimeSinceLastTransition to 00:00:00:000. The value for TimeSinceLastTransition kept increasing. 

</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124300:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00123769 SR 103126710:</b> A field attribute alarm value was "false" instead of "true" after redeploying objects.
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124408:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b>The GR Browser Service crashed when a Galaxy was created, but the IDE showed the service instance as deployed.
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00124529:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b></b>When performing write operations on attributes running on a redundant engine which is failed over, the reason description for remote secured and verified write attributes showed the "retrieving reason description" message for a few seconds then went blank. The reason description was not retrieved.
</td>
</tr>



<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125047:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00124940 SR 27810889:</b> A User Defined Object Analog Field Attribute displayed incorrect values in an S7 PLC, using the SIDirect DAServer.
</td>
</tr>



<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125309:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00125111 SR 14812231:</b> A high number of missed MX heartbeats occurred (NetNMXHearbeatsMissedCnt) across all platforms in the Galaxy. Part of the resolution includes the following edits to the Windows Registry:
<p></p>
<blockquote><p>Create a DWORD registry value "HeartBeatTolerance" on the path </p>
<blockquote>
	<p>"HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\Nmx" for a 32-bit machine, and</p>
	<p>"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\Nmx" for a 64-bit machine</p>
	</blockquote>
	</blockquote>
<p class="note"><b>Note:</b> The value is in milliseconds. A value of 0 is disabled. The enabled range is from 1 to 250 milliseconds.</p>
</td>
</tr>


<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125529:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00125442 SR 34211435:</b> The GlobalDataCache service stopped synchronizing with the Galaxy Repository.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125637:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00125468:</b> When testing asynchronous subscription using a Matrikon OPC server, items became stuck initializing.  
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00125639:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00125506 SR 14832275:</b> When hosting an RDI object on a Redundant Engine, references went to BAD quality on failover, bypassing the  "Maximum time to maintain good quality after failure" setting. 
</td>
</tr>

<tr>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00126320:</span></td>
<td style="TEXT-ALIGN: left; VERTICAL-ALIGN: top">
<b>HF CR L00126035 SR 15712676:</b> Duplicate alarms appeared with the same timestamp in the WWALMDB when alarms were generated every second in the Alarm Viewer Control summary. 
</td>
</tr>




</tbody></table>



<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>


<A name="AppServer 2012 R2 Readme"><h1 class="center">Wonderware Application Server 2012 R2 (version 3.6) Readme</h1>


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


<p>Last revision: 10/24/2012</p>

<h2>About This Readme</h2>
<p>This Readme provides information about important resolved and known issues for Wonderware<sup>&reg;</sup> 
Application Server 2012 R2 (version 3.6).</p> 

<p>For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the Wonderware<sup>&reg;</sup> System Platform Readme, which is located in the root folder of the Wonderware System Platform installation media.</p>


<p>Readme files from previous releases of Wonderware Application Server are posted to the Wonderware Developer Network at <a href="http://wdn.wonderware.com/Downloads">http://wdn.wonderware.com/Downloads</a>.</p> 


<P><A 
href="#Resolved Issues">Resolved Issues</A></P>

<P><A 
href="#Known Issues">Known Issues</A></P>


<!--<P><A 
href="#Documentation Issues">Known Documentation Issues</A></P>-->


<h1><a name="#Resolved Issues"></a>Resolved Issues</h1>

<p>This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.</p>
<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">L00092147: </span></td>
    <td><b>SR 103115692</b>: If the Galaxy Browser was open in the second monitor in a dual-monitor system, then the dual monitor was changed to a single monitor, the Galaxy Browser position was out of bounds and could not be seen on the single monitor.  A change in user preference settings to include the number of monitors resolved the issue.   
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00094592: </span></td>
    <td><b>SR 103116159</b>: An error pop-up dialog, "Attribute not writeable", appeared when saving a template derived from DDESuiteLinkClient. This issue has been resolved.
  </td></tr>


<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00107457: </span></td>
    <td><b>SR 30712432/30711916</b>: Lost alarm communication alarm priority was set to 1, which prevented use of that priority for other alarm conditions. The issue has been resolved. You can now manually create a registry entry to provide the alarm priority. Add the registry key <b>CommunicationErrorAlarmPriority</b> under the registry section <b>HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Framework\Alarms</b> and set the value (priority) between 0-999 (Use the decimal option when setting the value.) If the value for <b>CommunicationErrorAlarmPriority</b> is not set or is out of range, the default value (1) is used.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00108759: </span></td>
    <td><b>SR 10416087</b>:  Galaxy dump did not properly export or import scripts with names beginning with an underscore character (_). Importing the .csv file back to the Galaxy resulted in an empty script. 
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00104182: </span></td>
    <td><b>SR 38910250</b>:  Intermittent LMX errors appeared while erasing References from the Unresolved References list. The issue is now resolved. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00108975: </span></td>
    <td><b>SR 15315829</b>:  Exporting objects from a remote IDE created temporary folders that were not deleted upon completion of export, consuming large amounts of disk space. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00109878: </span></td>
    <td><b>SR 20113801</b>:  Setting the same limits for Lo and LoLo alarms resulted in the error message "PV: The HiHi limit must be greater than the LoLo limit". The error message has been corrected and the issue resolved.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00111121: </span></td>
    <td><b>SR 103120422</b>:  State change events were not logged into the Alarm Database, for example, when changing the DiscreteDevice_001 PV state. Instead, logging events errors appeared in the logger.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112065: </span></td>
    <td><b>SR 103121279</b>:  Incorrect script syntax caused the AppEngine to crash. It could not be redeployed or undeployed. The issue is resolved. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00113024: </span></td>
    <td><b>SR 42410004</b>: Validation was not automatically performed when an object was moved from one parent object to another when the object was checked out. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00112980: </span></td>
    <td><b>SR 20611106</b>: Checking in an InTouchViewApp template failed when the revision number exceeded 32767. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00115425: </span></td>
    <td><b>SR 15712461</b>: The value deadband for a Field Attribute was not working as expected. All values updated regardless of the size of the value change.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116208: </span></td>
    <td><b>SR 103122477:</b>: Deleting the description field of a Field Attribute in an instance, followed by a Galaxy load operation, resulted in the content of the template Field Attribute description being rewritten to the instance. 
  </td></tr>

  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116783: </span></td>
    <td>Installing Application Server as a product was blocked if a version of SQL Server 2008 newer than SP1 (SP2 or 64-bit SP1) was used. 
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00116979: </span></td>
    <td><b>SR 40212165</b>:  Derived objects migrated to newer versions were not being properly stored when importing a new version of a base template into a Galaxy. The issue has been resolved. 
  </td></tr>

  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117300: </span></td>
    <td><b>SR 34211168</b> Galaxy backup failed on a hard drive with  insufficient disk space, even though the backup location was another drive with sufficient space. Temp backup files were still written to the local drive, causing the backup failure. The issue has been resolved. 
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117320: </span></td>
    <td>Problems were experienced with the stored procedure "internal_set_host_association" when importing an export file. The issue was related to a known SQL Server 2008 SP2 issue.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117497: </span></td>
    <td>Performing a bulk operation from the IDE, such as propagation of changes from a template to all derived templates and instances, did not take advantage of all available cores in the PC.  At least 2-3 cores seemed blocked. The issue has been resolved.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117541: </span></td>
    <td><b>SR 33811846</b>: Updates to a UDA reference were not reflected in Object Viewer in a redundant system after failover to the secondary then return to primary. The UDA reference took the original value before the deployment changes. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117558: </span></td>
    <td><b>SR 43110090</b>: After redeploying an object following a cascade check in of the parent template, a script stopped executing even though the script trigger (WhileTrue) was evaluated as true. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117607: </span></td>
    <td>Creating an instance of a template containing less than 60 objects, but containing numerous visual elements, contained templates, and instances, required an unusually long time. Optimizing the change propagation, template instance creation, and renaming operations resolved the issue. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117700: </span></td>
    <td><b>SR 15316256</b>: Deployment of a platform on a Windows 7 64-bit computer required 18 minutes, far longer than a normal deployment. This issue has been resolved. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00117885: </span></td>
    <td><b>SR 20114109</b>: User authentication against the local active directory failed. Wonderware Application Server was attempting to authenticate against the primary domain controller, which was blocked by a firewall.  Logon optimization resolved the issue.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118112: </span></td>
    <td><b>SR 37112243</b>: With an RDI connected to two DDESuitelinkClient objects, when the active DDESL object was set to OffScan, the RDI connection status went to OffScan. When the DDESL object was put back OnScan, the RDI remained disconnected until it was redeployed. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118126: </span></td>
    <td><b>SR 103121095</b>: OPC quality was incorrectly represented as Bad. This state information also was logged into the Historian. Data quality interpretation in Wonderware Application Server did not match interpretation of data quality in OPC. 
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118198: </span></td>
    <td><b>SR 37611734/37611747</b>: Under certain circumstances, a Redundant Device Integration (RDI) item stayed in Initializing quality or became stuck in Bad quality, even though the DI source shows Good quality. 
  </td></tr>

  
  <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118241: </span></td>
    <td><b>SR 38910352</b>: The platform stopped communicating with its partner and the message channel library was stuck sending messages. Symantec antivirus was running on the platform nodes, and the Symantec drivers seemed to be blocking the messages. The issue has been resolved.  
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118498: </span></td>
    <td><b>SR 103123638</b>: Advising an item continuously caused a memory leak, resulting in a steady increase in memory consumption. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118617: </span></td>
    <td><b>SR 29710009</b>: Importing an aaPKG file caused galaxy corruption of some templates and objects. This occurred when importing the aaPKG with the overwrite option enabled. 
  </td></tr>  

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118863: </span></td>
    <td><b>SR 103123076</b>: When undeploying a RedundantDIObject (RDI) with an incorrectly configured backup DI source, then redeploying, an" access denied" error message appeared on the RDI and the ScanGroup.
  </td></tr>  
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00118970: </span></td>
    <td><b></b>Opening a DI Object in "Read Only" mode did not display the ScanMode column in the Topic Tab. 
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119060: </span></td>
    <td>< GRAccess application function <b>QueryObjects</b> failed to find objects in deployment pending status. 
  </td></tr>
  
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119210: </span></td>
    <td><b>SR 40210818</b>: When one redundant AOS shut down, the AppEngines intermittently did not fail over. In some instances, those AppEngines that did fail over started in standby. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119231: </span></td>
    <td><b>SR 45110020</b>: ArchestrA security did not provide a username sort function. This was inconvenient, especially when large numbers of users had accounts in the system. A sort function has been added to the <b>User</b> tab of the IDE <b>Security Configuration</b> dialog. 
  </td></tr>  

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119237: </span></td>
    <td><b>SR 38910367</b>: Under certain circumstances, the write completion callbacks from a connected DAServer were not  called in the DDESuiteLinkClient DIObject. Randomly, individual item writes initiated to individual attributes of the DDESuiteLinkClient DIObject failed to be acknowledged.
  </td></tr>  
  
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119425: </span></td>
    <td><b>SR 103124193</b>: Using Top Server OPC Server 5, pulling the ethernet cable from the PLC caused the OPC Server to send Bad quality for polled items, but OPCProxy showed items as Initializing in Object Viewer.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119615: </span></td>
    <td>Associated files were deleted from the CheckedIn folder even though the PreCheckIn event failed. 
  </td></tr>

 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119762: </span></td>
    <td>WindowViewer crashed during attempt to log in with ArchestrA security set to OS Group. 
  </td></tr>

 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119774: </span></td>
    <td>Running QueryObjects from a GRAccess application failed to find FCS (non-ArchestrA) objects needing redeployment.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00119891: </span></td>
    <td><b>SR 103124434</b>: The Anonymous Engine ID intermittently did not recycle correctly when opening, closing, and reopening WindowViewer, and caused WindowViewer to crash.  
  </td></tr>

  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120192: </span></td>
    <td>A Galaxy created from a .CAB file that was backed up in Application Server 3.2 failed to migrate on an Application Server 3.5 machine if the Galaxy name provided was not the same as the one backed up in Application Server 3.2.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120400: </span></td>
    <td>After making changes to the RDI object, all AppObjects referencing the RDI object went to a warning state. To remove the warning state, the AppObjects required manual validation.  
  </td></tr>

  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120626: </span></td>
    <td><b>SR 20114325</b>: The IDE connection froze when synchronizing  security (OS Group-based) with the Active Directory.  
  </td></tr>
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120677: </span></td>
    <td><b>SR 38910393</b>: OPC DI needed to implement a Time Sequence validation and  a Read when subscribing Active references.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120678: </span></td>
    <td><b>SR 22317676</b>: DDE/SuiteLink DI needed to implement a Time Sequence validation.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120709: </span></td>
    <td><b>SR 37112565</b>: When the active DAServer was deactivated, the RDI failed over, but the item reported Bad quality on the RDI, even though the item reported Good quality on the active DDESuitelink DI source object. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00120980: </span></td>
    <td><b>SR 38910394</b>: Items became stuck in Initializing state after switching between ArchestrA graphics using ShowGraphic.  
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121007: </span></td>
    <td><b>SR 38910395</b>: The script execution order was not accessible when opening a UserDefined derived template/instance read-only. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121023: </span></td>
    <td><b>SR 24910041</b>: LMX writes failed in certian circumstances when the item had not yet been added to the DI object scan group item list.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121187: </span></td>
    <td><b>SR 31711844</b>: The OPCClient kept disconnecting and reconnecting even though the OPC Server was local to the OPCClient, resulting in "Warning OPCClient Target Node is missing" messages. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121293: </span></td>
    <td><b>SR 12612158</b>: The GR machine was deregistered from an old domain and registered in a new domain. Subsequently, the IDE was not able to browse for users in the new domain but was still able to browse the users in the old domain.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121453: </span></td>
    <td><b>SR 38910398</b>: When events were logged, the Operator Node Name included an unexpected suffix.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00121940: </span></td>
    <td> The ArchestrA IDE displayed an access warning dialog at startup, and opened in read-only mode.
  </td></tr>
  
  
<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122211: </span></td>
    <td><b>SR 31712114</b>: Deploying only one platform of a redundant pair required 2-3 times longer to deploy than when also deploying the redundant platform. Continuous scan overruns then occurred on the engine until the engine was either taken off scan or the redundant platform was deployed.
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122213: </span></td>
    <td><b>SR 10416742</b>: When using the SignedWrite() function, events were not logging the full details of the verified write operation and an unhandled .NET error occurred. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122221: </span></td>
    <td><b>SR 103125569</b>: When using the SetData method to insert a value to element 0, SetData did not check whether the array was 0 index or not, and called the SetAttribute function. SetAttribute  did not treat the array with 0 index as an array, considered it to be a normal value, and destroyed the array attribute. 
  </td></tr>

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122253: </span></td>
    <td><b>SR 33933024</b>: During run time, handles grew on aaGR.exe until the process crashed.  
  </td></tr>


  
</tbody></table>

<p>
</p>
<p class="right"><a title="Click this link to go to the top of the document." href="#Top">&lt; top of document &gt; </a><br>

<br>
<h1><a name="Known Issues"></a>Known Issues</h1>
<p>This section describes important known issues.</p>

<table style="TEXT-ALIGN: left" border="0" cellspacing="1" cellpadding="5" ><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. 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: 'Calibri','sans-serif'; 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> because it is an older version &lt;number> 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>An object vendor creates a new minor version of DotNetAppObject 
      version 1.1<br>
      <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>
 

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


<td> <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. 
</td></tr> 
 
 <p><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>
	
<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>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>
		 
<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>Rebuild the object to get an object with a minor version change containing changes in the editor only.</li>
</ol>
</blockquote>
</tr>
</td>
<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.

</td></tr><br>	
	
<p><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>The interactive (logged-in) user on the GR is a member of DomainA. 
	<li>The ArchestrA Network User is an account in DomainB. 
	<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:
	<ul style="LIST-STYLE-TYPE: disc">
	<li> Editing objects.
	<li> Deploying objects. 
	<li> Deleting objects.</ul></li>
	 
	 <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>Have the Galaxy nodes, the interactive user (logged in user) and ArchestrA Network user all are members of the same domain.</ol></li>
	 <p>For more information, see Tech Note #719.

<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><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>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&cmd=displayKC&externalId=1011709</a>.</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>

</tr>
</td>


<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>
</tr>

	 </td></tr>
<tr>
<td style="text-align: left; vertical-align:top; FONT-WEIGHT: bold">L00108399: </span></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</span>:</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: </span></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: </span></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>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: 'Calibri','sans-serif'; 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 version 3.5 (2012) and higher versions. 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: </span></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: 'Calibri','sans-serif'; 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>
<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>
 
  </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. 

<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. 

	

<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 = &#60;visual element id&#62;<br>
</code>


 
<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>

<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. 


<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.

 
<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>After installation, right-click <b>SqlExpress Connection</b>, click <b>Properties</b>, and then click <b>Security</b>.
<li>Change the SQL Server Express authentication from Windows mode to Mixed mode and click <b>OK</b>.
<li>Restart the database instance or computer.</li></ol>

<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. 


<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.
<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. 
	

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

 <!-- 
<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>  
 !-->

<tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122304: </span></td>
    <td>In an intermittent issue, if you repeat the UndoCheckout operation several times in a row, you can observe performance degradation. Performance degradation has been seen only after the third or fourth repeated UndoCheckout operation.</td></tr>
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122313: </span></td>
    <td>Importing an aaPKG file using the "Skip: Do not import" option can exhibit inconsisent behavior. In one scenario, importing an aaPKG file that contains instances created from a system template to a Galaxy containing an earlier version of the system template with no instances, using the option "Objects with same Tagname and Codebase - Skip: Do not import" did not import the newer system template instances. In another scenario, importing the aaPKG file to a Galaxy that contains a newer version of the system template than that being imported, with no instances, using the option "Objects with same Tagname and Codebase - Skip: Do not import", imported the aaPKG system template instances.  </td></tr>
 <tr>
    <td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00122358: </span></td>
    <td>Because unregistered attributes are not cleared from the Application Server StoreForward cache, an unregistered attribute on the AppEngine can be registered again to the Historian after the Historian run-time database is rebuilt. </td></tr>
 


 
</tbody></table>
 
<p class="right"><a title="Click this link to go to the top of the document." href="#Top">&lt; top of document &gt; </a><br>


<!--<h1><a name="Documentation Issues"></a>Documentation Issues </h1>
<p>The following table lists important documentation corrections.</p> 
<p></p>
<table style="TEXT-ALIGN: left; WIDTH: 900px" 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></tr>
</tbody></table><p></p>
-->

<!--<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>
-->

<P>&copy; 2012-2014 Invensys Systems, Inc. All Rights Reserved.</P>
</HTML>