InTouch HMI 2014 R2 (v11.1) Service Pack 1

Posted on 3,911 views

Last revision: 1/28/2016

About This Readme

This Readme provides information about InTouch HMI 2014 R2 (v11.1) Service Pack 1. Readme files from previous releases of Wonderware InTouch HMI are posted on the Schneider Electric Software Global Customer Support (GCS) website.

Download the WSP2014R2 with SP1.iso password:zhenergy.com

This Readme includes the following sections:

New Features in InTouch HMI 2014 R2 (v11.1) Service Pack 1

System Requirements

Component Compatibility

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

Documentation Issues

InTouch Documentation

Important!

FactorySuite Gateway (FS Gateway) 3.0 SP1 is installed as a hidden feature of InTouch HMI 2014 R2 SP1 in a Wonderware System Platform (ASP) 2014 R2 SP1 installation.

  • If you previously installed FS Gateway 2.0 SP1 without any other InTouch products, then installing Wonderware System Platform 2014 R2 SP1 will upgrade FSGateway to version 3.0 SP1.
  • If you previously installed FS Gateway 2.0 SP1 as part of ArchestrA System Platform 2012 with InTouch 10.5, you must uninstall FS Gateway before upgrading to Wonderware System Platform 2014 or later.

For more information about FS Gateway installation, upgrade, and uninstall, see the Wonderware System Platform Installation Guide, “InTouch HMI Requirements and Prerequisites” section, “Installing FS Gateway and Modifying FS Gateway Installations” topic.

< top of document >

New Features in InTouch HMI 2014 R2 (v11.1) Service Pack 1

Service Pack 1 provides support for the latest versions of Microsoft products and several enhancements to features introduced in InTouch HMI 2014 R2 and InTouch HMI 2014 R2 Patch 01.

Support for the Latest Versions of Microsoft and Other Products

InTouch 2014 R2 SP1 supports and is compatible with the most current versions of Microsoft and other products:

  • Microsoft Windows 10
  • Microsoft SQL Server 2014 Service Pack 1 and SQL Server 2012 R2 Service Pack 3
  • Microsoft .NET Framework 4.6
  • vSphere/ESXi 6.0 in virtual environments

Support Regional Settings for Numeric Value Displays and Numeric Input

During run time, numeric data can be entered and displayed in ArchestrA graphics in a format that matches the format of the country set as the regional locale on the computer running WindowViewer. Numbers show a thousand separator and decimal point that match the selected country’s format.

The InTouch WindowViewer keypad now includes comma, period, and a thin space keys to enter numbers that match the format of the country set as the regional locale. In addition, if the WindowViewer Follow regional settings for ArchestrA Graphics configuration option is selected, the keypad displays numeric values using symbols based on the regional settings.

Export and Import Application Style Library Applied to ArchestrA Symbols in Modern Applications

Users can export a Modern application’s Application Style Library from WindowMaker to a designated folder location as an XML file. Users can also import the Application Style Library to a Modern application to reuse the Quality and Status display, the Element Styles, and numeric format styles that were defined in another Modern application.

Export ArchestrA Graphic Toolbox Symbols That Have Embedded Symbols from Automation Objects

When exporting ArchestrA symbols from the Graphic Toolbox that have embedded symbols from automation objects in them, users see a dialog box with an option to export the associated objects hosting the graphics in the same operation.

Export Localization Strings of Selected Symbols in Modern Applications

This feature allows you to export the strings of selected symbols. You can then edit the strings within the exported XML files, and re-import them later.

Export Selected Symbols from the ArchestrA Toolbox in Modern Applications

Exporting and importing ArchestrA symbols in Modern applications have been enhanced in Service Pack 1. Rather than exporting or importing the entire set of Archestra symbols, now one or more selected symbols can be exported or imported.

The selected ArchestrA symbols are exported to an .aaPKG file to a designated folder location.

Support for the Last History Statistic of the History Summary Data Type Custom Property

A History Summary custom property can be added to a symbol that references historical data collected over a specified period during run time. The Historian can transform this data to create a set of analog or state summary statistics that can be shown by ArchestrA graphic animation during run time.

In Service Pack 1, the analog Last historical statistic has been added to the History Summary custom property. The Last historical statistic shows the last data value that occurred in a historical summary period.

Include an Overridden Tag for Programmatic Symbol Exports

A new XML attribute has been added to each symbol within the XML file containing ArchestrA symbols that have been programmatically exported. The attribute identifies whether changes have been made to the properties of the embedded symbols in a base symbol or not. This new Overridden attribute added to the exported XML file is essentially a “change flag”.

In Service Pack 1, an exported symbol that does not contain any changes to embedded symbol custom properties includes an Overridden attribute set to False, which is the default value.

Overridden="False"

The Overridden attribute makes it easier to programmatically identify symbols that have not been changed.

Installation Option to not Install a Galaxy Repository on the InTouch Development Computer

In prior releases, the Wonderware System Platform installation program automatically installed SQL Server Express when an InTouch development environment was going to be installed on a computer without SQL Server. An instance of SQL Server Express was required as a Galaxy Repository to support InTouch Modern applications.

In Service Pack 1, the installation program includes an option to not install SQL Server on the InTouch development computer. This option is provided for customers who do not intend to create Modern applications and do not need SQL Server installed on their development computer.

Import InTouch Modern Applications Through the Command Line

A utility is available which enables importing InTouch Modern applications through the Windows Command Prompt interface. See the InTouch Modern Application guide for details.

Support of Non-Default SQL Port

InTouch components that use SQL Server can now run properly if SQL Server is configured to use a port other than the default of 1433. This allows compliance with more stringent IT security policies.

Eliminated SysAdmin Role Support

The ArchestrA user (of the aaAdministrators user group) can be removed from the SQL Server SysAdmin role. Note: This feature is not enabled by default. Please refer to the Application Server documentation for details.

< top of document >

System Requirements

Contents

Introduction

This section describes the hardware and software requirements to support Wonderware System Platform 2014 R2 SP1 products, including InTouch HMI 2014 R2 SP1.

Hardware Requirements

Contents

Hardware Guidelines

The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2014 R2 SP1 software based on the size of the installation. These guidelines are subject to the limitations of your Windows operating system.

  • The Intel Itanium 2 processor is not supported.
  • We recommend 1280 x 1024 as the minimum display resolution for engineering tools such as the Integrated Development Environment (IDE).
CPU Cores
(Minimum)1
RAM1 (GB) Storage (GB)2 Network
(MBPS)
Small Installation

(1 – 25K I/O per Node)

≥2 ≥4 ≥30 ≥100
Medium Installation

(25k – 50k I/O per Node)

≥4 ≥8 ≥500 ≥1000
Large Installation

(More than 50k I/O per Node)

≥8 ≥16 ≥1000 ≥1000
Notes:
1 In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.
2 Minimum amount of storage needed to provide sufficient capacity for 1 week @ max frequency.

Hardware Requirements Notes:

Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for InTouch HMI 2014 R2 SP1. Refer to the following Microsoft Web pages for Windows and SQL Server hardware requirements:

Auxiliary Hardware Requirements

This section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this Readme.

Alternative Authentication Using Smart Cards

  • Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
  • Smart Card Reader: OK 3021 USB Smart Card Readers

Operating System, .NET Framework, and Virtualization Requirements

Summary of Software Requirements for InTouch HMI 2014 R2 SP1

The following table lists the operating system, .NET Framework, and virtualization requirements for the suite of Wonderware System Platform products, including InTouch HMI 2014 R2 SP1.

Note: Only the software versions and service packs shown in the following tables are supported by the products included in Wonderware System Platform 2014 R2 SP1.

Windows Client OS1 (32/64-bit) Windows Server OS (64-bit) .NET Framework MS Browser Virtualization Host
Embedded2 Professional, Enterprise
Ultimate3
Embedded4 Standard, Enterprise5,
Data Center6
Windows
Server
VMWare
Win
7 SP1
Win
8
Win
7 SP1
Win
8
Win
8.1
Win
10
2008 R2 SP1 2012 2012 R2 2008 R2 SP1 2012 2012 R2 3.5 SP1 4.5.17 4.5.27 4.67 IE 108 IE 118 Edge Hyper-V9 vSphere 5.x-6.010 Workstation11
Wonderware Application Server 2014 R2 SP1 Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y Y
Wonderware InTouch 2014 R2 SP1 Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y Y
Wonderware Historian 2014 R2 SP1 Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y Y
Wonderware Historian Client 2014 R2 SP1 Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y Y
Wonderware Information Server 2014 R2 Portal N N Y Y N N Y Y Y Y Y Y C Y Y Y Y Y N Y Y Y
Wonderware Information Server 2014 R2 Client Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y N Y Y Y
FS Gateway 3.0 SP2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
System Size This section applies to GR Node only; remote nodes can use any supported OS
Small Installation (1-25,000 I/O per node) Y Y Y Y Y Y Y Y Y Y Y Y C Y Y Y Y Y Y
Medium Installation (25k-50k I/O per node) N N Y Y N Y Y Y Y Y Y Y C Y Y Y Y Y Y
Large Installation (50k-400k I/O per node) N N N N N N Y Y Y Y Y Y C Y Y Y Y Y Y
Notes   1 Up to five remote nodes are supported by a GR running on a Client OS.
2 Windows 7.1 SP 1 Embedded must use Application Compatibility Template. Windows 8 Embedded must use full image with all modules.
3 Ultimate applies to Windows 7 SP1 only. Ultimate versions not available for newer versions of Windows.
4 All Embedded Windows Server versions must use full image with all modules.
5 Enterprise applies to Windows Server 2008 R2 only.
6 Data Center applies to Windows Server 2012 and 2012 R2 only.
7 Custom Client Controls that leverage functionality not contained in .Net Framework 4 are not supported.
8 Enable Compatibility View mode when accessing Wonderware Information Server with Internet Explorer.
9 Support for Hyper-V is based on operating system version.
10 Support for VMWare vSphere includes High Availability/Disaster Recovery.
11 Supported versions of VMWare Workstation include 7.x through 11.x.

 

Supported Y
Not Supported N
Coexist C
Not Applicable

Software Requirement Notes:

Windows Operating System Notes

    • Windows versions 8, 8.1, and 10 support touch screen gestures. If the user swipes in from the right edge of a touch screen with a finger gesture, a set of Windows charms appears, which includes Search, Share, Start, Devices, and Settings. Moving the mouse cursor to the upper-right corner of a screen also shows the Windows charms for non-touch screens.

Showing the set of charms is a standard feature of Windows versions 8, 8.1, and 10 that cannot be disabled by software for a touch screen. As a result, operators can access these Windows charms and possibly unlock a dedicated touch screen view node.

  • Newer operating system Service Packs (SPs) than those listed do not block the installation of Wonderware products. A warning message may appear during the installation process.
  • The Galaxy Repository (GR Node) can run on a client Windows operating system in a configuration in which Wonderware System Platform products are installed on up to five nodes. For a system with more than five nodes, the Galaxy Repository must installed on a computer running a Windows Server operating system.
  • Development and application nodes are considered to be clients of the server GR node.
  • When an operating system is upgraded on a computer, existing Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are three exceptions. Wonderware System Platform products do not need to be uninstalled when upgrading from:
    • Windows 8 to 8.1
    • Windows 8.1 to 10
    • Windows 2012 to Windows 2012 R2

.Net Notes

  • Versions of .NET (other than 4.x versions) can coexist, but all .NET code, including QuickScript.net scripts, run under .NET 4.5.1.For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .
  • .NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.

Operating System Notes Common to Wonderware Products

ActiveX Controls Behavior on Windows 7, Windows 2008 R2, and Later Operating Systems

Due to the Data Execution Prevention (DEP) feature of Windows 7 and later operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behavior in InTouch 11.1 either in WindowMaker or WindowViewer running on Windows 7, Windows 2008 R2, and later operating systems. For more information, refer to Tech Note 922: “Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)” available from the Wonderware Technical Support web site.

Configuring Remote Alarm Retrieval Queries When Running Windows 7, Windows 8, or Windows Server 2008 R2

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows 7, Windows 8, and Windows Server 2008 R2.

When InTouch WindowViewer is started and generates alarms from an interactive Windows desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control’s alarm query is configured.

This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.

To configure the AlarmViewer’s alarm query

  1. After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows 8, or Windows Server 2008 R2 node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: “Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120”. The indicated IP address will be unique to your alarm-providing node. Note the IP address for Step 2.
  2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for “nodename” below and substituting your IP address noted in the previous step:

\\nodename:ip_address\intouch!$system

where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.

  1. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.

Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems

Starting with Microsoft Windows Vista, the operating system imposes “Session 0 Isolation” as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.

Prior to Windows Vista, Wonderware Application Server and InTouch WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as

\InTouch!$System \Galaxy!Area_001

is now serviced by two separate instances of AlarmMgr — one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.

This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, “AlarmMgr Support for InTouch and AppServer on Windows Vista and Later”. You can download this TechNote from the Schneider Electric Software Global Customer Support (GCS) website.

Terminal Services Behavior in Windows Server 2008 R2 and Later Operating Systems

Windows Server 2008 R2 and later Windows versions no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 and later, all remote connections are treated as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.

This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session.

In another aspect of Terminal Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value when running on Windows 2008 SP2 and Windows 2008 R2 operating systems with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the Terminal Server. You must install the “Terminal Server” role for Windows 2008 SP2 or the “Remote Desktop Host” role for Windows 2008 R2 in order for TSEGetClientId() and other related functions to work properly.

The impact to Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.

Wonderware Application Server and InTouch HMI detect when the application is running in the console. In Windows Server 2008 R2 and later, it implies that the application was started by a user physically at the machine. However, this behavior requires that you disable Fast User Switching in both Windows 7 and Windows Server 2008 operating systems.

When running Windows Server 2008 R2 or later versions of Windows, you must modify the terminal services behavior for the Wonderware software to operate properly.

Wonderware software detects when an application is running in the console. From Windows Server 2008 R2 and later versions of Windows, all remote connections are treated as a remote RDP session regardless of /console or /admin switches in the mstsc connection.

To disable fast user switching through the Group Policy interface

  1. Click Start and then Run. The Run dialog box appears.
  2. Enter gpedit.msc and click OK. The Group Policy dialog box appears.
  3. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.
  4. Set Hide Entry Points for Fast User Switching to Enabled.  Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the Task Manager.
  5. On the File menu, click Exit to close the Group Policy dialog box.

By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.

Certain editions of Windows Vista do not have the Group Policy editor. So, alternatively, you can configure the Switch User settings through the registry.

To disable fast user switching through the Registry Editor

  1. Click Start and then Run. The Run dialog box appears.
  2. Enter regedit.exe and click OK. The Registry Editor dialog box appears.
  3. Go to the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows > CurrentVersion > Policies > System.
  4. Right-click and select DWORD (32-bit) Value. Name it HideFastUserSwitching.
  5. Set the HideFastUserSwitching data value to 1.
  6. On the File menu, click Exit to close the Registry Editor.

In a Terminal Server environment that has a managed application deployed to it, the following behavior applies to references in the InTouch HMI application to the InTouchViewApp object:

ArchestrA Symbols referencing InTouchViewApp_001.Tag1:

Running on the Console – Refers to the tag value of the application running on the console.

Running in a Session – Refers to the tag value of the application running on the console.

Restarting the Window Viewer application running on the console causes references from the terminal session to disconnect and then reconnect.

InTouch Graphic referencing Tag1:

Running on the Console – Refers to the tag value of the application running on the console.

Running in a Session – Refers to the tag value of the application running in the session.

ArchestrA Graphic referencing InTouch:Tag1:

Running on the Console – Refers to the tag value of the application running on the console.

Running in a Session – Refers to the tag value of the application running in the session.

InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1:

Running on the Console – Refers to the tag value of the application running on the console.

Running in a Session – Refers to the tag value of the application running on the console.

Wonderware InTouch HMI 2014 R2 SP1 Operating System Notes

The following table lists the operating systems supported by InTouch HMI server and client components.

Operating Systems Wonderware InTouch HMI Components
WindowMaker WindowViewer ArchestrA IDE ArchestrA Run Time Galaxy Repository
Windows 7 SP1 Embedded, 32-bit or 64-bit Y Y N N N
Windows 7 SP1
Professional, Enterprise, or Ultimate, 32-bit or 64-bit
Y Y Y Y N
Windows 8
Professional or Enterprise 32-bit or 64-bit
Y Y Y Y N
Windows 8.1
Professional or Enterprise 32-bit or 64-bit
Y Y Y Y N
Windows 8.1 Embedded,
32-bit or 64-bit
Y Y Y Y N
Windows 10
Professional or Enterprise 32-bit or 64-bit
Y Y Y Y N
Windows Server 2008 R2 SP1
Standard or Enterprise, 64-bit only
Y Y Y Y Y
Windows Server 2012
Standard or Enterprise, 64-bit
Y Y Y Y Y
Windows Server 2012 R2
Standard or Enterprise, 64-bit
Y Y R R R
Supported Y
Not Supported N

Wonderware InTouch HMI 2014 R2 SP1 with Windows 7 and Later Versions of Windows

  • Windows 7 and later operating systems do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
  • The EnableDisableKeys() function writes to the Windows registry to enable or disable some keys on the host computer running an application in WindowViewer. For security purposes, Windows 7 and later versions of Windows prevent Standard or Power users from writing to the registry. Windows Administrators can write to the registry if not disabled by local domain security policies.You can configure local Windows security policies that work in conjunction with the EnableDisablekeys() script function to regulate the user’s access to keys in a running InTouch application.
  • As of Wonderware System Platform 2014, a computer running Windows 7 or later operating systems can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems.
  • The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on Windows 7 or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows 7 or later operating systems to function properly.
  • The onscreen keyboard options have changed for the Windows 7, Windows Server 2008 R2, and later operating systems.
  • Hovering to select from the Windows keyboard does not work in the Windows 7 Professional and later operating systems.

Wonderware InTouch HMI 2014 R2 SP1 View Applications and DDE Support

NetDDE is not supported for InTouchView applications.

By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.

In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.

Wonderware InTouch HMI 2014 R2 SP1 Support for Windows User Account Control

Wonderware System Platform 2014 R2 SP1 with InTouch HMI supports User Account Control-enabled operations on run-time nodes.

.NET Framework Requirements and Compatibility

IMPORTANT: Wonderware System Platform 2014 R2 SP1 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2014 R2 SP1, we strongly recommended that you:

  • Back up your applications
  • Familiarize yourself with the changes introduced by Microsoft in the .NET Framework
  • Review your .NET scripts and .NET controls for any required changes

After upgrading to Wonderware System Platform 2014 R2 SP1, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Wonderware System Platform 2014 R2 SP1 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. Wonderware System Platform 2014 R2 SP1 will use .NET 4.5.1, 4.5.2, or later.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to Wonderware System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.

In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:

BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());

To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:

What’s New in the .NET Framework: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx
What’s obsolete in the .NET Framework Class Library: https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx
Migration Guide to the .NET Framework 4.6 and 4.5: https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29
.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29

Virtualization Host Support

Wonderware System Platform 2014 R2 SP1 supports the following virtualization environments:

  • Microsoft Hyper-V: based on the version of Windows
  • VMware 6.0 virtualization with High Availability and Disaster Recovery (HA/DR)
  • VMWare vSphere 6.0
  • VMware 5.0 Update 1 virtualization with High Availability and Disaster Recovery (HA/DR)
  • VMWare vSphere 5.0 Update 1

SQL Server Requirements

Contents

SQL Server Requirements for All Wonderware Components

The following table lists SQL Server requirements for Wonderware System Platform 2014 R2 SP1 components, including InTouch HMI 2014 R2 SP1.

SQL Server Express-SSMSE SQL Server Standard, Enterprise
2008
SP3
(32 bit)
2008 R2

(32 bit)

2008 R2
SP1
(32 bit)
2008 R2
SP2
(32 bit)
2012

(32 bit)

2012
SP1
(32/64 bit)
2012
SP2
(32/64 bit)
2014

(32/64 bit)

2014
SP1
(32/64 bit)
2008
SP3
(32-bit only)
2008 R2

(32/64 bit)

2008 R2
SP1
(32/64 bit)
2008 R2
SP2
(32/64 bit)
2008 R2
SP3
(32/64 bit)
2012

(32/64 bit)

2012
SP1
(32/64 bit)
2012
SP2
(32/64 bit)
2014

(32/64 bit)

2014
SP1
(32/64 bit)
Application Server 2014 R2 SP1 S S S S S S S S S Y Y Y Y Y Y Y Y Y Y
InTouch 2014 R2 SP1 S S S S S S S S S Y Y Y Y Y Y Y Y Y Y
Historian 2014 R2 SP1 S S S S S S S S S Y Y Y Y Y Y Y Y Y Y
Historian Client 2014 R2 SP1
System Size:
Small Installation (1-25,000 I/O per node) N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Medium Installation (25k-50k I/O per node) N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Large Installation (50k-400k I/O per node) N N N N N N N N N N Y Y Y Y Y Y Y Y Y

Note: Match SQL Server version (32- or 64-bit) to operating system version.

Supported Y
Not Supported N
Not Applicable

We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program, especially if you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.

The Wonderware System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.

Considerations for SQL Server

    • Alarm DB Logger To use the Alarm DB Logger, you must set the default SQL Server authentication mode from Windows-based to Mixed Mode.
    • SQL Server Configuration Rights: While installing Wonderware System Platform, configuration changes to SQL Server are required. If the installer does not have SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install aaConfig SQL utility enables you to verify if the SQL configuration has been performed.
    • Maximum Server Memory: After installing SQL Server, Use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the computer’s total available RAM. By default SQL Server does not clamp this setting. The Wonderware System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
    • Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. 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 actually complete, and no Galaxy Repository is created. When you start the IDE, the Galaxy is blank.
    • Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate version installation. For more information and helpful procedures, see the following Microsoft references:
    • SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:
      • Run the Change Network Utility from the Windows Start menu.
      • Run the aaConfig SQL Utility from the Windows Start menu.

If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application Server User’s Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.

Considerations for SQL Server Express

  • SQL Server Express is supported for use on a Galaxy Repository node and recommended for use only with small systems.
  • If you plan to modify an InTouch HMI installation which has SQL Server Express installed, then add Wonderware Application Server with full SQL Server, you must install the full SQL Server prior to modifying the InTouch HMI installation or installing Wonderware Application Server.
  • If you plan to use SQL Server Express with Wonderware Information Server 2014 R2 SP1 and Wonderware InTouch HMI 2014 R2 SP1 on the same node, the following limitations apply:
    • Install Wonderware Information Server first with the SQL Server Express default instance name set to “SQLEXPRESS”. Then, install Wonderware InTouch HMI. This scenario will work without issues because each component uses a dedicated instance of SQL Server Express.
    • If you install InTouch HMI 2014 R2 SP1 first, the Wonderware System Platform installer silently installs and configures SQL Server 2012 SP1 Express. Installing Wonderware Information Server will fail during configuration with an error message stating: “SQL Server client components not found.”To work around this issue, configure Wonderware Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.
    • The computing capacity of SQL Server 2012 SP1 Express is limited to the lesser of one CPU socket or four processor cores.
  • For InTouch HMI installations, the Wonderware System Platform installer installs SQL Server 2012 SP1 Express with Tools (32-bit) if these conditions are met:
    • No other SQL Server elements are installed on the computer at the time of installation.
    • You select only the InTouch Development and Runtime Wonderware System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.
    • The installation program includes an option to not install SQL Server on an InTouch development computer. When the option is selected, it prevents SQL Server from being installed. Clear this option to automatically install SQL Server on a development computer.

InTouch Access Anywhere Requirements

The following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the Wonderware InTouch Access Anywhere documentation.

You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel.

Requirements

The InTouch Access Anywhere Server can be installed as a Wonderware System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed on a separate computer within a network DMZ.

The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.

Supported InTouch Access Anywhere Browsers

Wonderware InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers validated to support Wonderware InTouch Access Anywhere include the following:

Browsers Tested with InTouch WindowViewer

  • Apple Safari
  • Google Chrome
  • Microsoft Edge
  • Microsoft Internet Explorer
  • Mozilla Firefox
  • Opera

Functionally Compatible Browsers

Older versions of the listed browsers are functionally compatible with InTouch Access Anywhere. You may be able to use the following older versions of these browsers, but specific behaviors are unknown because no formal testing has been done with InTouch Access Anywhere.

  • Apple Safari versions 5 and 6
  • Google Chrome versions 11-27
  • Microsoft Internet Explorer versions 7, 8, and 9
  • Mozilla Firefox versions 4-21
  • Opera versions 11-14

You are strongly encouraged to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.

< top of document >

Wonderware InTouch HMI 2014 R2 SP1 Product Compatibility

Product Compatibility refers to the ability of a product to work with various versions of other products running on different network nodes. Product Compatibility also refers to the ability of a product to work with various versions of the same product running on different nodes.

Coexistence refers to same-node installation of a product with other Wonderware and Invensys products that support the same hardware, operating system, and SQL Server versions. Other products not listed will be covered by System Compatibility Testing unless specifically noted.

In a single-node environment, if you want to install multiple components on a single computer, all components must be at the versions delivered in Wonderware System Platform 2014 R2 SP1.

In a node-to-node environment, components are compatible between the current licensed version and one licensed version back.

The following table lists Wonderware and Schneider Electric products and their compatibility and coexistence with InTouch HMI 2014 R2 SP1.

Product Version Compatibility Co-existence
Wonderware System Platform 4.5 N N/A
2012 Y N/A
2012 R2 Y N/A
2012 R2 P01 Y N/A
2012 R2 P02 Y N/A
2012 R2 P03 Y N/A
2014 Y N/A
2014 P01 Y N/A
2014 R2 Y N/A
2014 R2 P01 Y N/A
Wonderware InTouch CE 10.1 N N
Wonderware Manufacturing Execution System 4.0 SP1 N N
4.0 SP2 N N
MES 2012 P01-4.5 Y Y
MES 2014-5.0 Y Y
MES 2014 SP1-5.0.1 Y Y
Wonderware InControl™ 7.11 SP2 P01 N N
Wonderware Manufacturing Execution Module 1 Y N
Wonderware InBatch™

* If you are using Wonderware Information Server with InBatch software, upgrading to Wonderware Information Server 5.6 requires an InBatch hotfix to maintain compatibility.

10.0 (2012 R2) N N
10.1 (2014) Y * Y *
10.2 (2014 R2) Y * Y *
11.0 (2014 R2 SP1) Y * Y *
Wonderware QI Analyst™ 8.0 SP1 P01 N N
8.0 SP2 Y Y
8.0 SP3 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 N N
Wonderware Intelligence 1.5 N N
1.5.100 (2012) Y Y
2.0 P01 (2014 R2 P01) Y Y
ArchestrA Workflow™ 1.5 (2012) N N
1.6 (2012 SP1) N N
1.7 (2012 R2) N N
1.8 N N
1.9 (2012 R2 SP1) N N
Wonderware Skelta BPM 2014 N N
2014 R2 Y Y
2014 R2 SP1 Y Y
InteleTrac 5.01 Y Y
2014 R2 Y Y
Wonderware PEM 2.1 SP1 N N
Wonderware Online (see components below) 1.0
  • Historian Client Trend
10.6 Y Y
  • Historian Client Trend
10.6?? Y Y
  • InTouch
11.x Y Y
  • MRC (Mobile Report Connector)
2014 R2 Y Y
  • MRC (Mobile Report Connector)
2015 Y Y
Recipe Manager Plus PEM 1.0 (2014) Y Y
1.5 (2014 SP1) Y Y
2.0 (2014 R2) Y Y
Schneider Electric Citect-VJC 7.2 SP3 Y Y
7.3 Latest SP N Y
7.4 SP1 Y Y
Schneider Electric ClearSCADA CS 2013 R1 N Y
CS 2013 R2 N Y
CS 2014 R1 N Y
CS 2015 R1 Y Y

 

Supported Y
Not Supported N
Not Applicable

In some cases, the Wonderware InTouch HMI is supported in newer environments than a compatible product. Wonderware InTouch HMI has been tested for compatibility with a listed product only in the environments that are supported by that particular product.

< top of document >

Wonderware InTouch HMI Installation

For detailed English installation instructions, see the Wonderware System Platform Installation Guide (ASP_Install_Guide.pdf) or Wonderware System Platform Installation Help (ASP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed Wonderware InTouch HMI Getting Started Guide booklet that is included in the installation package. This booklet is provided for all supported languages.

The information provided in this Readme file supersedes the InTouch Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.

Contents

Installing the Wonderware InTouch HMI

The major decision you must make when you install InTouch HMI is whether to install the InTouch development and run-time components, or the run-time components alone. The installation program guides you in selecting the features you want, verifying or modifying your selections, installing prerequisite software, and then installing InTouch HMI and the ArchestrA IDE if you chose to install development components.

What You Need to Install InTouch HMI

You must have the following materials ready to install InTouch HMI:

  • Installation DVD.
  • Computer that meets the hardware and software requirements listed in this Readme.

Important: Use the hardware and software requirements listed in the Wonderware Application Server Readme if you are going to install the ArchestrA IDE.

Prerequisites

The installation program analyzes the software installed on your computer and lists any required software that is not installed.

Note: At the start of the installation, the prerequisites check is system-specific rather than product-specific.

The following prerequisites, if not already present on your system, will be installed by the Wonderware System Platform installation program:

  • Windows Installer 4.5
  • Microsoft .NET Framework 4.5.2
  • SQL Server 2012 Express SP1SQL Server 2012 Express SP1 will be installed automatically if one of the following conditions are met:
    • No version of SQL Server is installed on the host computer.
    • You select only InTouch Development and Runtime during the Wonderware System Platform installation. You must not select any Application Server components. When you select InTouch Development and Runtime, a Galaxy Repository will be installed for you.

The installation program installs both system-specific and product-specific prerequisites. You do not have to exit from the installation program to install the prerequisite software. For more information about Wonderware System Platform installation prerequisites, see the Wonderware System Platform Installation Guide.

About the ArchestrA User Account

The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account on every node when you install the Wonderware System Platform components for the first time on computers that communicate with each other.

WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.

If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the InTouch HMI installation. You must specify a user name, password, and domain.

If you choose to use an existing user account, it should meet the following requirements:

  • User account with a permanent password that does not expire.
  • User account in which the password cannot be changed.
  • User account that is a member of the local Administrators group.

After you install the InTouch HMI, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from the Start menu in the Wonderware Common folder after you install InTouch. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility help.

Note: If you recreate the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.

Performing the InTouch HMI Installation

Before you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time, to run applications already created and deployed.

The following procedure will guide you through the installation, with information specific to the InTouch HMI.

To install the InTouch HMI

    1. Insert the installation DVD into the computer’s DVD drive.
    2. Using Windows Explorer, manually start the installation by double-clicking setup.exe on the DVD.
    3. Follow the prompts to start the installation and install system prerequisites, as necessary.
    4. The installation program prompts you to select an installation type: either product-based selection or installation by computer roles. As you are only installing InTouch HMI, click the product-based selection as your installation type.
    5. Choose the components you want to install.
      1. If you choose InTouch Run Time Only, the following will be installed:
        • InTouch Run Time
        • InTouch documentation
        • Alarm DB Logger
        • FS Gateway (as a silent installation)
        • Application Server Bootstrap
        • InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory

Note: The 16 Pen Trend supplementary component is not installed by default. You must select the Customize Installation option and select 16 Pen Trend from the product list to install it as part of the InTouch HMI installation procedure.

      • Invensys License Manager
    1. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • InTouch Development
      • Application Server Bootstrap, IDE, Galaxy Repository, SQL Server 2012 Express SP1 with SSMSE, and Application Server documentation
      • InTouch sample applications
  1. When the installation prompts you to verify your selection, select Customize Installation if you want to add or remove components of your InTouch installation.
  2. After you verify and customize your selection, you are prompted to select the language you want to install. English is selected by default, but you can choose another language.
  3. Follow the subsequent installation steps to:
    1. Accept the End User License Agreement.
    2. Create a new ArchestrA user account, or specify an existing account.
    3. Install any prerequisite software components not yet installed on the computer.
    4. The installation proceeds to completion. You must restart the computer after completing the installation.

Installing Your Invensys Product License

Wonderware enforces the use of its products with a software license. After you install a product, you must install a single license file, ARCHESTRA.LIC, which contains your customer information, product data, and software features. Until you apply your Invensys product license, you can only run the InTouch HMI in demonstration mode.

You use the Invensys License Manager to install the contents of the ARCHESTRA.LIC file on the computer where InTouch HMI has been installed. The Invensys License Manager is included as an Invensys component when you install the InTouch HMI.

To install your Wonderware product license

Start the Invensys License Manager by doing the following:

    1. Place the installation DVD in the computer’s DVD drive.
    2. Click Start from the Windows desktop, and then click All Programs to show the Invensys folder.
    3. Click the Invensys folder, and then click the Invensys License Manager folder.
    4. Click Invensys License Manager.
    5. Click File, and then Install License File. The Choose a License File to Install dialog box appears.
    6. Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.

The Destination Computer for Installation dialog box appears.

    1. Type the domain and computer names.

The Invensys License Manager copies the ARCHESTRA.LIC file to the C:\Program Files\Common Files\ArchestrA\License folder on the selected computer.

Antivirus Software Exclusions

After installing Wonderware InTouch HMI Version 2014 R2 SP1, configure your antivirus software to avoid scanning archive files.

Notes:

  • The folders listed in this section may be different based on your installation choices.
  • Exclude the files in the lowest level subfolder of the listed directories in this section. Antivirus exclusions should not be recursive and should only apply to the lowest listed subfolder in the specified folder path.
  • If you are using a 64-bit operating system, folder names must be specified accordingly. For example, the program files root folder in a 64-bit operating system is C:\Program Files (x86)\… and the application data root folder in a 64-bit operating system is C:\ProgramData\.

Add the following folders of 32-bit operating systems to your antivirus scan exclusion list:

  • C:\ProgramData\ArchestrA\
  • C:\Program Files\ArchestrA\
  • C:\Program Files\Common Files\ArchestrA\
  • C:\Program Files\FactorySuite\ (The FactorySuite folder may not exist in newer installations)
  • C:\Program Files\Wonderware\
  • C:\InSQL\Data\
  • C:\Users\All Users\Applications
  • C:\Historian\Data

Add the following folders of 64-bit operating systems to your antivirus scan exclusion list:

  • C:\ProgramData\ArchestrA\
  • C:\Program Files (x86)\ArchestrA\
  • C:\Program Files (x86)\Common Files\ArchestrA\
  • C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)
  • C:\Program Files (x86)\Wonderware\
  • C:\Users\Public\Wonderware\
  • C:\Historian\Data

Add the following folders to your antivirus scan exclusion list:

  • History Store Forward folder default location:
    • C:\Documents and Settings\All Users\Application Data\ArchestrA\
    • C:\Users\All Users\ArchestrA\
  • Checkpoint folder location default location:
    • C:\Program Files\ArchestrA\Framework\bin (32-bit Windows)
    • C:\Program Files (x86)\ArchestrA\Framework\bin (64-bit Windows)
  • InTouch HMI application folders:
    • C:\Users\Public\Wonderware\IntouchApplications (default folder path)
    • You can select an application folder path when an InTouch HMI application is created.
  • ArchestrA System Management Console (SMC) Logger storage file path:
    • C:\ProgramData\ArchestrA\LogFiles (default folder path)

Add the following file types to your antivirus exclusion list:

  • SQL Server database files of type:
    • .mdf
    • .ldf
  • Exclude *.aFDX files from the C:\Windows\Temp folder

Modifying, Repairing, or Removing the InTouch HMI

To modify, repair, or remove a product

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Access the Windows Control Panel and select the Programs and Features option.The list of software installed on your computer appears.
  3. Select the InTouch component, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
  4. Follow the prompts to modify, repair, or remove InTouch.The name of the Uninstall/Change button varies depending on the version of Windows installed on your computer.

Note: Modern applications can no longer be created, edited, or run after Wonderware Application Server is uninstalled from the same computer that also hosts InTouch run time and development components. Modern applications no longer work because the Galaxy Repository required for Modern applications is removed when Wonderware Application Server is uninstalled.

Upgrading to Version 11.1 Service Pack 1 from an Earlier Version of the InTouch HMI

Upgrading InTouch HMI installs Version 11.1 Service Pack 1 on a computer that has a previous version currently installed. An upgrade removes the previous version of InTouch HMI and installs Version 11.1 Service Pack 1.

After the hardware and software requirements are met, you can upgrade to Wonderware InTouch HMI Version 2014 R2 SP1 (v11.1) from the following versions of the InTouch HMI:

  • Version 10.1 SP3
  • Version 10.1 SP3 P01
  • Version 10.2
  • Version 10.5
  • Version 10.6
  • Version 10.6 P01
  • Version 10.6 P02
  • Version 10.6 P03
  • Version 11.0
  • Version 11.0 P01
  • Version 11.1
  • Version 11.1 P01

You can only upgrade Wonderware System Platform products that are already installed. You cannot install any new Wonderware System Platform products by an upgrade process.

To upgrade from a previous version of the InTouch HMI

  1. Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program.
    The upgrade feature dialog box appears.
  2. Follow the prompts to complete the upgrade.

Upgrade Notes

  • Important Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.
  • InTouch Development (WindowMaker) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to ArchestrA 2014 R2 SP1. You must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server 4.1 to ensure that all issues reported by the utility are addressed.

Migrating Applications to Wonderware InTouch HMI 2014 R2 SP1 (v11.1)

Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to InTouch HMI 2014 R2 SP1 that were developed with the following earlier versions of InTouch HMI:

Product From Upgrade Node-by-Node Upgrade Migrate
Wonderware InTouch 7.0 N N/A N
7.1 N N/A N
7.11 P07 N N/A Y
8.0 SP2 P04 N N/A Y
9.0 P03 N N/A Y
9.5 SP1 N N/A Y
10.0 SP2 N N/A Y
10.1 (no SP) N N/A Y
10.1 SP2 N N/A Y
10.1 SP2 P01 N N/A Y
10.1 SP3 Y N/A Y
10.1 SP3 P01 Y N/A Y
10.2 Y N/A Y
10.5 Y N/A Y
10.6 Y N/A Y
10.6 P01 Y N/A Y
10.6 P02 Y N/A Y
10.6 P03 Y N/A Y
11.0 Y N/A Y
11.0 P01 Y N/A Y
11.1 Y N/A Y
11.1 P01 Y N/A Y

SPCPro was a Statistical Process Control (SPC) utility available with InTouch HMI prior to Version 11.0. SPCPro is no longer supported by InTouch HMI 2014 R2 SP1. We recommend that that you migrate your SPCPro databases to the latest version of QI Analyst if you still use SPCPro with InTouch. QI Analyst provides support for the latest versions of operating systems and databases.

QI Analyst also includes a utility to migrate your SPCPro database to a QI Analyst database, leaving the existing SPCPro database intact. Please contact your local Wonderware sales representative for further information.

Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing Wonderware System Platform 2014 R2 SP1 with InTouch HMI. InTouch 2014 R2 SP1 no longer includes SPCPro and will not open or migrate applications containing SPCPro components.

< top of document >

Resolved Issues

InTouch HMI 2014 R2 SP1 (v11.1) resolves the issues listed in the following table. These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column shows other subsequent change requests that are related to the original change request.

Original Change Request Related Change Requests Description
L00121730 L00122558, L00122803, L00137146 SR 45710056: A circular reference error message appeared after migrating an InTouch managed application from Version 3.0 of Application Manager. Custom properties were linked together in a set of linked attribute expressions that were not cleared while checking the datasource path for circular references.
L00124873 L00133267, L00133790, L00137161 SR 43910669, SR 48910456: Alarm comments were overwritten and not visible when using the Alarm Client control’s .Ack.Selected” method to acknowledge alarms.
L00132932 L00133998, L00134158, L00137176 SR 103132494: Alarms could not be acknowledged from the Alarm Client Control after a hot backup failover of the primary alarm provider server.
L00133430 L00133619, L00136983 SR 51010175, SR 103135262 : A pop up window containing ArchestrA graphics was opened by script containing the ShowSymbol method. The pop up window did not close when the parent window was closed by a DataChange script. A pop up window should always close when the parent window containing the ShowSymbol script is closed.
L00134836 L00137344, L00137548 SR 103135527: The ArchestrA Alarm Client control did not show translated alarm comments from the Historian database.
L00135010 L00137416, L00137761 SR 103133028: An automation symbol can now be embedded in an ArchestrA Graphic Toolbox symbol from the ArchestrA Symbol Editor. The symbol containing the embedded symbol can be copied and pasted to another location. The symbol supports Undo and Redo editing actions as well as display and string animations.
L00135759 L00136414 SR 52410655: The behavior of a push button symbol differed based on whether a left mouse click or the keyboard Enter key was used to set the active condition when a button was in the engaged “down” position. The push button returned to the correct “up” position when the left mouse key was released. When the Enter key was released, the push button remained in the incorrect engaged “down” position.
L00135845 L00135999, L00136050, L00137030 SR 103134079: ArchestrA graphics did not show the expected fill color when the animation was set for 100 percent horizontal fill.
L00135876 L00136285 SR 103133579: The Alarm Client control’s GetItem method did not show the millisecond portion of alarm time stamps.
L00135888 L00136719 SR 39911153: WindowViewer became non-operational several times a day with a detected access violation.
L00135909 L00136266 SR 19818733: Windows Tab key and Show Symbol functionality was not working.
L00136131 L00136341, L00136580 At run time, keyboard shortcuts did not work correctly with an input text box in a modal Showgraphic pop up window. The input text box showed the letter of the typed shortcut instead of performing the requested shortcut action.
L00136340 L00136582 SR 103134223: The GetPenValAtX2() method was not available in the .NET version of the ArchestrA Trend Client control in Windows System Platform 2014 R2 Patch 01 and earlier. The GetPenValAtX2() method is available in Windows System Platform 2014 R2 Service Pack 1. The GetPenValAtX2() method is also described in the ArchestrA Trend Client Control User’s Guide.
L00136366 L00136950, L00136977 SR 103134529 : The font size of text was different in WindowViewer after switching the language from French to English during run time.
L00136384 L00136931, L00136978 SR 45510935: A ViewEngine object failed to re-deploy when restarting a redundant computer with the Galaxy Repository node offline.
L00136491 L00137045 SR 19818750: Show window animation changed the perspective of the target window if the Fit to window option was selected on the published window in the ArchestrA Web Exporter.
L00136497 L00137085, L00137595 SR 103134318, SR 52310446: Text elements shown within ArchestrA graphics appeared blurred during run time even with the Smoothing property set to True.Alternative Solution:

  1. Open the Registry Editor by typing regedit from the Windows command line.
  2. Locate and then right-click the following registry subkey:
    • (for 32-bit machines) HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\InTouch
    • (for 64-bit machines) HKEY_LOCAL_MACHINE\Wow6432Node\SOFTWARE\Wonderware\InTouch
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type “TextRenderingOption” as the name of the DWORD, and then press Enter.
  5. Right-click on TextRenderingOption, and then click Modify.
  6. In the Edit DWORD Value dialog box, type “1” in the Value field, and then click OK.
  7. Run the application in WindowViewer to verify that the symbol text is not blurred.
L00136500 L00137051, L00137084 SR 103134719: Graphics shifted by a couple of pixels on screen when a script was continuously running to set or reset a UDA’s attribute value.
L00136581 L00136810, L00136832 SR 103134803: The GetCPQuality() and GetCPTimeStamp() methods failed when in a symbol script.
L00136595 L00137189, L00137285 SR 52310372: InTouch text that used the MS Sans Serif font changed size when switching to another language during run time.
L00136644 L00137080 SR 103134441: WindowViewer could not be launched with a remote desktop connection using a MSTSC shortcut containing the path to an InTouch application.
L00136646 L00136984, L00137106 SR 42010116: Graphic buttons shown by scripts containing ShowSymbol or ShowGraphics methods became stuck in the set position when the Enter key was pressed and the mouse cursor was placed over the buttons.
L00136667 L00136819: SR 103134751: An InTouch application could not be run by passing the application name as a command line parameter in a RDP session on a Terminal Server.
L00136769 L00136878 SR 54410013: The time zone setting on the Alarm Client control was not retained between development sessions if set to Client Time Zone. The time zone reverted to the time zone of the development computer.
L00136857 L00136903 SR 52310372: Text in InTouch using the “MS Sans Serif” font changed size when region settings for non-unicode programs was set to Chinese.
L00136896 L00137098 SR 43611569: An ArchestrA graphic with an embedded Trend Client was opened by using a button with show symbol animation. All Trend graph labels appeared normal when the window was first opened. After closing and re-opening the graphic, the top scooter labels of the graph disappeared. Additionally, if the trend client was configured with references for Pen Details: Min and Pen Details or Max configuration fields, the Trend Client’s Y-axis labels also disappeared.
L00136918 SR 48910573: Memory usage by WindowViewer gradually increased because of unresolved references.
L00136932 L00137002, L00137044 SR 103135007: The Localized French caption of the Archestra Alarm Client control did not fit within the boundaries of the Requery button and could not be read.
L00137075 L00137343 SR 51010480: Fill Color animation of ArchestrA graphics failed when the graphics were associated with InTouch I/O Discrete tags whose values set truth table conditions. Graphic animation succeeded when WindowViewer was launched from WindowMaker. Graphic animation failed when WindowViewer was already running prior to a fast switch from WindowMaker, or the application window was closed and re-opened.
L00137101 L00137196, L00137287, L00137523 SR 103135224 SR 103135371: In an environment consisting of multiple Galaxies with different versions of InTouch deployed, different versions of ArchestrA symbols appeared when an InTouch application’s objects were redeployed.
L00137115 SR 410417820: When windows caching was enabled, an ArchestrA combo box was initialized and showed previous tag values instead of the current values.
L00137292 L00137383, L00137549 SR 103135489: After opening and closing several windows from WindowViewer, subsequent windows opened much more slowly because the cache was full.
L00137296 SR 103135604: Alarms in InTouch were displayed with an incorrect time-stamp when a burst of 100 alarms was generated with a time difference of 100msecs.
L00137335 L00137753 SR 40217411: When text within an ArchestrA symbol had its font changed, the text reverted to the original font when the symbol was copied using an XML file export import operation and the text of the symbol copy was modified.
L00137351 L00138130, L00138183 SR 103135589: The ArchestrA Alarm Client control became nonoperational during updates of the alarm table in the background.
L00137361 L00138574, L00138644 SR 103134274: Running InTouch applications containing an embedded Alarm Client control within a pop-up window became gradually slower until WindowViewer had to be restarted to restore normal application performance.
L00137411 L00137554 SR 37510838: WindowViewer became non-operational while using a Web browser component to navigate within a PDF file and rapidly typing a sequence of keyboard characters including a backspace and a space.
L00137469 L00138102, L00138191 SR 103135801: After upgrading from Wonderware System Platform v3.1 Service Pack 3, the SetcustompropertyValue method created Invalid Reference warning entries in the log when caching was enabled and an InTouch window was closed and reopened during run time.
L00137591 L00138112, L00138143 SR 12613372: Stand alone and managed InTouch applications exited from WindowMaker much more slowly after a tag update when an application was accessed through a Universal Naming Convention (UNC) folder path rather than a direct folder path.
L00137825 L00138236, L00138332 SR 55110092: An AlarmDBView control localized to Chinese could not return an alarm database query using the SelectQuery() method in a script.
L00137836 L00138087, L00138144 SR 51310846: Exporting an InTouch Modern application did not include the aaDCM.dll file. An error message appeared during a subsequent import operation indicating the file was missing.
L00137880 SR#103136129: While navigating among different InTouch WindowViewer windows containing ArchestrA Graphics, the “halos” indicating active, selected, or focused objects disappeared. This behavior occurred with the memory cache enabled.
L00137920 L00138259 SR 52310889: On computers set to Germany as its regional locale, scripts containing the FileWriteMessage() method converted an integer to text and added ,500000 to the end of the string.
L00138001 L00138141, L00138177 SR 103136196: WindowMaker became non-operational attempting to use the Substitute Strings utility to simultaneously change the names of more than 30 tags in a window.
L00138030 L00138149, L00138192 SR 43611579: WindowViewer eventually became non-operational because of excessive memory usage when scripts were used to rapidly switch the display of several windows containing an embedded Alarm Client control in a managed application.
L00138042 L00138184 SR 24516666: Exporting an alarm query added default query filter characters to the XML export file. The alarm query could not be imported using an action script associated with a graphic button. The query could be manually imported using the green button of the Alarm Client.
L00138094 L00138329, L00138485 SR 54310027: After embedding an ArchestrA symbol in an InTouch window and changing an InTouch tag to an ArchestrA object attribute reference, the symbol did not initially show the correct value of the attribute reference during run time. Selecting the field containing the attribute reference in WindowMaker again corrected the issue.
L00138161 L00138400 SR 103136567: If an assigned dotfield of an InTouch tag was assigned as a reference of a custom property of an ArchestrA symbol embedded in an InTouch window, the tag was not recognized and could not be deleted.
L00138230 L00138295 SR 103136606, SR 103124050: An AlarmDBView control localized to Chinese could not return an alarm database query using the SelectQuery() method in a script.
L00138354 L00138667 SR 24413063: In an InTouch Modern application, action scripts associated with ArchestrA graphics were not completely or properly validated for unresolved references. Only references within the first line of a script were validated and no references were validated in the remaining lines of a script.
L00138413 L00138721 SR 22210251: Current alarm records were not filtered by ArchestrA Alarm Client control using the .FromPriority and .ToPriority properties.
L00138483 L00138722 SR 103136612: An error message “Configuration error: Invalid reference – ‘UserObject’ does not exist.” appeared in the SMC log when the Alarm Client control showed Boolean alarms associated with attributes containing “Lo” or “Hi” in their names.
L00138488 L00138720 SR 51710035: Graphics configured with alarm border animation showed a portion of the alarm border when scripts containing the ShowSymbol or ShowGraphic methods hid the graphic from view during run time.
L00138904 L00138949 SR 103136548: With Data Source set to HistoryBlocks, scripting could not change the default filter in A2AlarmClient Control for Historical Alarms.
L00138706 L00138963 SR 43611719: Time zone change was not reflected in Alarm Client.
L00138986 L00139041 SR 55110117: With Galaxy set to Galaxy Security, and InTouch with ArchestrA security, a valid user logged into InTouchViewer entering a value in a graphic received “Write attempt fails…” error.
L00138742 L00138564 SR 103137000: Alarm Limits were not triggering correctly when the value of the difference is a number with a decimal (for example, 2.7).
L00138231 L00138818 SR 54810088: WindowMaker’s zoom feature was behaving erratically. Especially when resizing an object, a “ghost” image of the object at its former size was displayed.
L00138900 L00138934 SR 45510984: When using LCT time setting, EAC Alarm Client Control was displaying an incorrect time stamp for alarms that returned to normal unacknowledged..
L00138120 L00138624 SR 103136463: ArchestrA graphics embedded into an InTouch application using the hierarchical view lost the ability to select an alternate instance.

< top of document >

Known Issues

This section describes known issues that remain in the release of InTouch HMI 2014 R2 SP1. The issues are listed by their Change Request number.

L00137472: Angled connector lines do not maintain horizontal and vertical orientation with 90 degree angles to each other when placed in a symbol whose dimensions exceed 1280 by 1280 pixels. Instead, a connector will revert to a straight line between connection points beyond the 1280 by 1280 pixel boundary.
L00138785,
L00136780 :
When Regional Settings are other than United States, InTouch WindowViewer crashes when EAC attempts to read Alarms and Events from History Blocks.

Workaround: Store Alarms and Events in the A2ALMDB, and configure the ArchestrA Alarm Control (EAC) to retrieve from this database instead of using History Blocks. Once this issue is resolved, the data in A2ALMDB can be migrated to History Blocks.

L00139557: When using a non-default SQL port: In Runtime with multiple EACs configured, database connections may fail with a “Timeout expired” warning (see full text below) appearing in the SMC.

Error Message: Open() in DCMConnection failed: ‘Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.’

Workaround: Perform a manual refresh on the ArchestrA Alarm Control (EAC) to re-establish the connection.

L00139560: When using a non-default SQL port: If the primary Historian server is down during a restart of WindowViewer, trend updates are delayed by approximately 25 seconds. This is a one-time delay after WindowViewer restarts.
L00139681: After changing the SQL port of the Historian node and restarting Historian, the ArchestrA Trend Client (RT Trend) does not reconnect to Historian.

Workaround: Restart the instance of WindowViewer hosting the Trend client.

L00139786: After switching between default and custom SQL ports for Dual Historian, on a machine where the ArchestrA Trend Client (RT Trend) is used and is configured by scripting, only the real time trend displays, not the Historian trend.

Workaround: Delete the servers.xml file typically found at the following location: C:\Users\<user-name>\AppData\Local\Wonderware\ActiveFactory\servers.xml.

L00139789: Connecting to a SQL database in Microsoft Windows 8 or Windows 10 operating systems, when a non-default port is configured for SQL, results in an error message that a connection to the server is not available.

Workaround: Disable (shut down) the firewall on Windows 8 and Windows 10 operating system machines.

L00139813: Deploying an InTouchViewApp with a fully qualified file name exceeding 260 characters results in errors logged in the Logger and client controls not copied to the destination location. A fully qualified file name is one that prefixes the file name with the drive letter and directory path. The fully qualified file name must not exceed 260 characters, and the directory name must not exceed 248 characters. These are Windows operating system limitations.
L00139833: Migrating a Galaxy which has an InTouchViewApp with embedded Historian Client controls from Wonderware System Platform versions 2012R2 or 2014R2 to version 2014R2 Service Pack 1, results in errors logged in the Logger.

Workaround: Before migrating the InTouch application, delete the previous version Historian Client controls that exist in the Galaxy. Import the newer version controls.

< top of document >

InTouch Documentation Issues

The following table lists corrections to InTouch 2014 R2 SP1 documentation.

Item Location of Change Existing Documentation Change
1 InTouch HMI Application Management and Extensions Guide (ITAppManagement.pdf), “Configuring an InTouch Application for NAD” section, page 46WindowMaker Help (WM.chm), “Configuring an InTouch Application for NAD” topic. French, German, Japanese, and Chinese versions of the InTouch HMI Application Management and Extensions Guide
You cannot use NAD update features if you are running WindowViewer as a service. For more infomation, see “Running WindowViewer as a Service” on page 66.
Remove the paragraph from the book.
2 InTouch HMI Application Management and Extensions Guide, “I/O in a Terminal Services Environment” section, page 60WindowMaker Help (WM.chm), “I/O in a Terminal Services Environment” topic. French, German, Japanese, and Chinese versions of the InTouch HMI Application Management and Extensions Guide
Note: Running WindowViewer as a Windows Service is not a supported configuration because of the Terminal Services architecture.
Remove the note from the book.
3 InTouch HMI Application Management and Extensions Guide (ITAppManagement.pdf), “Managing InTouch Services” Chapter 3, pages 65-72WindowMaker Help (WM.chm), “Managing InTouch Services” topic
WindowMaker Help (WM.chm), “Running WindowViewer as a Service” topic
WindowMaker Help (WM.chm), “Configuring WindowViewer to Start as a Service” topic
WindowMaker Help (WM.chm), “Manually Starting a Service” topic
WindowMaker Help (WM.chm), “Stopping a Service” topic
WindowMaker Help (WM.chm), “Configuring the User Account for InTouch Services” topic
WindowMaker Help (WM.chm), “Troubleshooting InTouch Services” topic
WindowMaker Help (WM.chm), “Viewing Error Messages for Services” topic
WindowMaker Help (WM.chm), “Troubleshooting Problems with the Services User Acccount” topic
WindowMaker Help (WM.chm), “Deactivating Advised I/O Items” topic
WindowMaker Help (WM.chm), “Registry Keys for the InTouch Services” topic
French, German, Japanese, and Chinese versions of the InTouch HMI Application Management and Extensions Guide
Chapter 3 “Managing InTouch Services”, entire chapter
Remove the chapter from the book.
4 Creating and Managing ArchestrA Graphics User’s Guide (AAGraphics.pdf), “Double-byte Character Languages” section, page 242ArchestrA Help (IDE.chm), “Double-byte Character Languages” topic. Addition to the French, German, Japanese, and Chinese versions of the Creating and Managing ArchestrA Graphics User’s Guide Add the following title and paragraph at the end of the section titled “Restrictions of Numeric Formatting by Regional Locale” section.
Double-byte Character LanguagesDouble-byte character languages like Chinese or Japanese provide narrow or wide character sets. The Windows default setting is to show narrow characters in Chinese or Japanese languages. The decimal point and digital grouping characters can be shown with a narrow double-byte character set. However, the comma or period characters cannot be shown with a wide double-byte character set.
5 InTouch Modern Application Guide (ITModernAppGuide.pdf), “Importing an InTouch Modern Application” section, page 16 French, German, Japanese, and Chinese versions of the InTouch Modern Application Guide Replace the command-line utility syntax provided under the heading “To import a Modern application using the Command Prompt” with the following:

InTouchConsole.exe /import:”c:\test\m1.aaPKG” /param:”c:\test\app1″,”m2″,”My modern app”

< top of document >

InTouch Documentation

The InTouch product library consists of a set of Portable Document Files (PDF) available in the following location of the Wonderware System Platform DVD:

\Wonderware System Platform\InstallFiles\CD-Intouch\UserDocs\English

You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

http://www.adobe.com/products/acrobat/readstep2.html

After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer.

< top of document >


© 2015 Schneider Electric Software, LLC. All Rights Reserved.

 

4 thoughts on “InTouch HMI 2014 R2 (v11.1) Service Pack 1

    1. Unknown Unknown Unknown Unknown

      the password is “zhenergy.com”,no quote, I’ve just update the web, sorry for the inconvenience

Leave a Reply

Your email address will not be published. Required fields are marked *

2 × 3 =