Wonderware® InTouch® HMI 2012 (version 10.5) Patch 01 Readme

Last revision: 04/23/2012

About This Readme

This document includes information about Wonderware®InTouch®HMI 2012 (version 10.5) Patch 01. It updates the previous ReadMe files included with Wonderware InTouch HMI 2012 (v10.5).


Wonderware InTouch HMI 2012 (v10.5) Patch 01 Information

Applying Patch 01 to InTouch HMI 2012 (v10.5)

Resolved Issues - Wonderware InTouch HMI (v10.5) Patch 01

InTouch Documentation Issues

Applying Patch 01 to InTouch HMI 2012 (v10.5)

This section explains how to apply InTouch HMI 2012 (v10.5) Patch 01 to existing instances of InTouch 2012 (v10.5) installed at your site.

Important: InTouch HMI 2012 (v10.5) Patch 01 must be applied only to InTouch HMI 2012 (v10.5). No other version of InTouch can be upgraded with this patch.

The InTouch HMI 2012 (v10.5) Patch 01 Setup.msp patch file is available from the Wonderware Technical Support web site. You can copy the Setup.msp patch file directly to the computer where InTouch is installed, or burn it to a CD. If you decide to copy the patch file to a CD, you must use the following conventions to prepare the InTouch HMI 2012 (v10.5) Patch 01 CD:

You must install the Setup.msp patch file only when UAC is turned off or disabled.

Apply the Patch

  1. Close Application Manager, WindowMaker, or WindowViewer, or System Mangement Console (SMC/MMC) if they are running.
  2. Place the Setup.msp patch file in a folder on the computer where InTouch is installed, or place the Patch CD into the computer's CD-ROM drive.
  3. Open Windows Explorer, and then move to the location where you placed the InTouch patch Setup.msp file.
  4. Double-click on the Setup.msp file to start the patch installation procedure.
  5. Click Next. The Updating System dialog box shows the progress of the patch update.
  6. If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
  7. Click Finish.
  8. Click Yes to restart your computer.

< top of document >

Resolved Issues - Wonderware InTouch HMI (v10.5) Patch 01

InTouch HMI (v10.5) Patch 01 resolves the following issues listed by their Change Request number:

L00096629: HF CR L00116487 SR 103116551: The StartApp() function in InTouch 10.1 did not correctly open the Excel spreadsheet.
L00100439: HF CR L00118773 SR 15616845: Using Dynamic Resolution (DRC) replace-type windows behavee unexpectedly and closed windows already open.
L00110323: HF CR L00117084 SR 41610071 HF 2355: Zooming in and printing the application output wrong coordinate positions.
L00110611: HF CR L00117425 SR 19816998: On importing an InTouch window in a Managed Application, the System tags displayed as placeholders.
L00110695: HF CR L00117085 SR 41610081: InTouch keypad remains open even after the parent window that invoked the keypad is closed.
L00110791: HF CR L00116976 SR 33410812 HF 2294: Importing DBLoad from the IDE failed. Add a new Registry DWORD value DisableWriteToNewTag to the following Registry locations:
  • On 32-bit operating systems: HKEY_LOCAL_MACHINE:SOFTWARE\Wonderware\Intouch\Installation
  • On 64-bit operating systems: HKEY_LOCAL_MACHINE:SOFTWARE\Wow6432Node\Wonderware\Intouch\Installation
If you do NOT intend to do a delta import from the Historian (InSQL), set the DisableWriteToNewTag DWORD value to 1 to improve the performance of the DBLoad. Otherwise, set the value to 0.
L00115201: HF CRs L00114702, L00116121 SRs 33430926, 33410952]: An alarm or event record was not logged to the alarm database if one of the fields contained a single quotation mark (apostrophe).
L00115667: HF CR L00114593 SR 41610130: Window location information was unexpectedly changed and saved when using the mouse scroll wheel in WindowMaker.
L00115766: HF CR L00115350 SRs 33410954, 33410861: When an attribute in alarmed state had its value or alarm limit modified so that it remained in alarmed state and was then reported again due to an engine restart, the alarm was logged twice with the same timestamp but with different values.
L00116359: HF CR L00113474 SR 38231312: After switching languages, then printing a window without opening it, the window did not print in the new language.
L00116367: HF CR L00112069 SR 33410861 HF 2467: With the AlarmDBLogger running as a service, a local platform query to get alarms from the Galaxy flooded the Alarm database with hundreds of old alarms so that the database grew one GB in two days. Add a new Registry DWORD value ArchestrAAlarms to the following Registry locations:
  • On 32-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\AlarmLogger\ArchestrAAlarms
  • On 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wonderware\AlarmLogger\ArchestrAAlarms
The new DWORD value, ArchestrAAlarms, controls how the system looks up the ArchestrA alarms.
  1. In the absence of the ArchestrAAlarms DWORD value or if it is disabled by setting its value to zero or any value other than 0, 1, or 2, the system looks up ArchestrA Alarms using the GUID (current behavior).
  2. If the ArchestrAAlarms DWORD value is added and is set to 1, then the system looks up the alarms using the TagName+OriginationTime+ProviderId combination. If the same alarm is reported by multiple InTouch alarm providers, then the alarm is considered to be separate alarms, each coming from a different provider.
  3. If the ArchestrAAlarms DWORD value is added and is set to 2, then the system looks up the alarms using the TagName+OriginationTime.
If the same alarm is reported by multiple InTouch alarm providers, then only one instance of the alarm will be logged in the database.
L00116419: HF CR L00116319 SR 103121430 [CAR 050820]: A NAD client opening or compiling a window for the first time resulted in error and warning messages, "Bitmap pixels and planes mismatched 32:16 1:1" and "Failed to load Window Index 10804. Stage=9 Linked=1". The windows still loaded properly.
L00116551: HF CR L00116132 SR 103122267: When a condition script was configured to execute every minute, inserting data into SQL through SQL Access, WindowViewer ceased to function after less than an hour.
L00116690: HF CR L00116494 SR 103122402: The Alarm DB Logger hangs with the error message, "The statement has been terminated." The conversion of a CHAR data type to a DATETIME data type resulted in an out-of-range DATETIME value.
L00116865: HF CR L00116007 SR 15316210: A Smart Symbol replace operation modified many Tagnames in the Instance References column. The window was saved and closed, but when the window was reopened, the original default Tagnames appeared in the Instance References column.
L00116867: HF CR L00116489 SR 42010030: Language Switching for Application Server Alarm Comments did not work correctly for ACK Alarms.
L00116978: HF CR L00116826 SR 41610154: Key scripts linked to the CTRL key did not import.
L00117305: HF CR L00117089 SR 103118108: Action scripts were deleted during conversion from InTouch 9.5 to InTouch 10.1 if ActiveX was not installed.
L00117436: HF CR L00117030 SR 103122442: Opening an ArchestrA Symbol from another ArchestrA Symbol, showed with ShowSymbol function, then opening a keypad on a textbox, modeless, then calling another InTouch window caused the InTouch application to freeze.
L00117539, L00117540: The ShowGraphic function forced displays into the viewable window instead of the user-specified location.
L00117551: HF CR L00117352 SR 41610181: WindowMaker crashed with a Heap error message when zooming the window with the mouse scroll wheel after setting the zoom percentage.
L00117556: HF CR L00117373. SR 33932683: Attempting to change the size of very large symbols are created out of standard graphic elements resulted in a size in pixels that was off by two or more pixels.
L00117600: HF CR L00114637 SR 41610132: Linked tag information was lost when importing windows containing ActiveX controls.
L00117646: HF CR L00117484: InTouch application logon using Single Sign-On failed when a domain was not available.
L00117701: HF CR L00117518 SR 33811894: Using a resizeable keyboard in InTouch does not allow entry of a negative number.
L00117802: HF CR L00117530 SR 12611886: A SuperTag with exactly 64 members caused DBLoad to fail on the second import of the same CSV file.
L00117829: HF CR L00117585 SR 41610196: Zooming in and printing an application prints incorrect coordinates for thick line weight polylines and polygons.
L00117873: HF CR L00117994 SR 103123189: With an Archestra symbol with an embedded Alarm Client Control and alarms selected at run time, the selected alarms can become de-selected when a new alarm occurs.
L00117911: HF CR L00117647 SR 24515368: When running Recipe Manager on a dual monitor system, the Recipe Select dialog box split between screens instead of remaining on one screen.
L00118082: HF CRs L00117645, L00115745: Initial values in a DBdump for some tags are different when the Group By option is selected or de-selected.
L00118083: HF CR L00117455 SR 41610188: When multiple pens were added in run time, one or more pens failed to be added to the Trend Client. Error messages were written to the Logger: "Item has already been added. Key in dictionary: 'ffc35062758' Key being added: 'ffc35062758'" and "WW Internal Diagnostics - Message generated during .Net Garbage Collection: An instance of .Net class ArchestrA.Visualization.GraphicLibrary.aaExpressionClientScriptCompiler was not disposed."
L00118209: HF CR L00118019 SR 103123335: Under Windows 7 64-bit and Windows Server 2008 R2 operating systems, attempting to export alarm comments from an application where alarms are already present in other languages resulted in a dictionary file without the translated comments.
L00118272: HF CR L00118032 SR 33811917: The Alarm DBLogger didn't connect to WWALMDB on a remote server but on the same domain. Errors messages appeared in the Logger: "!Tables were not created in WWALMDB database. Please use 'Create' button in the Configuration page" and "Unable to reconnect!! - Wait for reconnect."
L00118341: HF CR L00118026 SR 103123043: When enlarging a Trend Client Control, the PenName label was pushed out of the graphic and disappeared from view.
L00118397: HF CR L00118311 SR 41610231: When Tag names were changed in the Tagname Dictionary, the selection list for Data Change scripts still showed the old names. However, the new names appear correctly in the application explorer.
L00118425: HF CR L00117996 SR 31611482: The Numeric Keypad went into the backgroup when called from a symbol rather than remaining in focus.
L00118594: HF CR L00118457 SR 25315228: An Intouch application implemented with custom ActiveX and ActiveX event scripts crashed when the ActiveX event scripts were executed.
L00118696: HF CR L00118946 SR 43110127: The Alarm DBLogger did not allow configuration of a query string longer than 1024 characters.
L00118911: HF CR L00118611 SR 12612031: AttemptInvisibleLogon did not work correctly if the logged on user is configured as "user must change password upon next login". AttemptInvisibleLogon did work correctly if the user account does not require a password change upon next log on.
L00118914: HF CR L00118587: Alarm Restore failed using the archived files and the InTouch Alarm Db Restore application when the folder used is 2GB in total size.
L00119004: HF CR L00118741 SR 103123775: With Windows Input Service for Touchscreens active and a Real tag configured, changing the tag value with the touchscreen caused WindowViewer to crash. The hardware was a B & R Panel PC.
L00119131: HF CR L00118992 SR 41610250: CPU went to 100% and the system froze when a rotated text was placed on top of an animation-linked object.
L00119145: HF CR L00119053 SR 103124050: On a Windows 7 SP1 32-bit operating system runing InTouch 10.1 SP3 Patch01, Simplified Chinese, the SelectQuery method of the AlarmDBView Control in Chinese InTouch didn't work and displayed a warning message that the filter name could not be found.
L00119337: HF CR L00118964 SR 20611183: While running InFusion View, a While True script stopped executing when the expression was still True. A While True script should continue executing as long as the expression is True, and should work evn when using remote terminal sessions (WYSE clients).
L00119357: HF CR L00118978 SR 103124001: An Action Script On Left Key Up did not work correctly with an ArchestrA Symbol opened by using the ShowSymbol command.
L00119676: HF CR L00119269 SR 31711973: When running an InTouch Managed application in InTouch version 10.1 SP3 P01, with DASABCIP 4.1 SP2 installed on the same node, using OS Group-based security, attempting a Secured Writes failed with the error message "The user ID is {00000000-0000-0000-0000-000000000000}, which is not acceptable for security verification."
L00119852: HF CR L00119269 SR 31711973: When running an InTouch Managed application in InTouch version 10.1 SP3 P01, with DASABCIP 4.1 SP2 installed on the same node, using OS Group-based security, attempting a Secured Writes failed with the error message "The user ID is {00000000-0000-0000-0000-000000000000}, which is not acceptable for security verification."

< top of document >

InTouch Documentation Issues

The following table lists all documentation corrections to InTouch HMI 2012 (v10.5) documentation.

Item Location of Change Existing Documentation Change
1 InTouch® HMI 2012 (v10.5) Readme
(Readme.HTML), "Remote Alarm Retrieval Queries" topic.

The source alarms will not appear unless the AlarmViewer control's alarm query is configured. This type of query only works for InTouch as an alarm provider running in a Terminal Services session, not for InTouch running in a console session. HF CR L00119852 SR 103124484

The source alarms will not appear unless the AlarmViewer control's alarm query is configured. This type of query only works when querying InTouch running in a Terminal Services session.

< top of document >

Wonderware InTouch HMI Version 10.5 Readme

Last revision: 10/07/2011

About This Readme

This Readme contains important information about Wonderware® InTouch® HMI version 10.5. It explains the new features and any known issues that remain unresolved.

About This Release

Version 10.5 of the Wonderware InTouch HMI includes enhancements and new features.

New Features

System Requirements

Product Compatibility

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation


< top of document >

New Features in Wonderware InTouch HMI version 10.5

< top of document >

System Requirements

This section describes the hardware and software requirements to install Wonderware InTouch HMI Version 10.5.

Hardware Requirements

The following shows the recommended specifications to install and run Wonderware InTouch HMI Version 10.5.

InTouch Hardware Requirements

Hardware Requirements Small
(1 - 5,000 I/O)
(5,000 - 20,000 I/O)
(> 20,000 I/0)
Application Server
Galaxy Repository (GR)
CPU (GHz) 1.2 2.5 2.5
Minimum Cores 1 2 4
RAM (Min GB) 1 2 4
Hard Disk size
(Available in GB)
50 100 250
Monitor 1024 x 768 1280 x 1024 1280 x 1024
Network card (MBPS) 100 100 1000

Input Devices
DVD drive for installation      
Mouse or compatible pointing device      

Auxiliary Hardware Requirements

Windows 7 Embedded
Alternative Authentication Using Smart Cards

Software Requirements

The following table lists the supported operating systems that can be installed on computers that run InTouch server and client components.

Operating Systems Product Name Components
WindowMaker WindowViewer ArchestrA IDE ArchestrA Run Time Galaxy Repository
Windows XP SP3
Professional, 32-bit only
Windows Vista SP2
Business or Ultimate, 32-bit or 64-bit
Windows 7
Professional or Ultimate, 32-bit or 64-bit
Windows 7 SP1
Professional or Ultimate, 32-bit or 64-bit
Windows Server 2003 SP2
Standard or Enterprise, 32-bit only
Windows Server 2008 SP2
Standard or Enterprise, 32-bit or 64-bit
Windows Server 2008 R2
Standard or Enterprise, 64-bit only
Windows Server 2008 R2 SP1
Standard or Enterprise, 64-bit only
Windows XP Tablet  Y Y N Y N


Using Wonderware InTouch with Windows 7 Embedded

Windows 7 Embedded has been qualified and supported for InTouch run time (WindowViewer) and FS Gateway. It is not supported for use in a development environment (IDE), for local process and alarm storage, or for historical logging.

Windows 7 Embedded is identical to the desktop version of Windows 7 operating system, but has specific hardware requirements that are listed in the Hardware Requirements section. It also has the following licensing restrictions:

Using Wonderware InTouch with Windows Vista, Windows 7, and Windows Server 2008 R2

DDE Support

Windows Vista and Windows Server 2008 do not support NetDDE for InTouchView applications. By design, an InTouchView application does not serve data to any other source, including InTouch 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. Windows Server 2003 and Windows XP Pro still support NetDDE.
In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.

Support for Windows Operating System User Account Control

InTouch version 10.5 supports User Account Control-enabled run-time operations without elevated privileges. For all configuration and installation operations, including those called during run-time operations, User Account Control must be disabled or privileges must be elevated to the required level.

Remote Alarm Retrieval Queries

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch when running on operating systems such as Windows 7 and Windows Server 2008 R2. When InTouch WindowViewer is started and generates alarms from interactive Windows 7, Windows Server 2008 R2, or Windows Vista desktop session, an AlarmViewer control (running within InTouch) 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 as an alarm provider running in a Terminal Services session, not for InTouch running in a console session.

To configure the AlarmViewer's alarm query

  1. After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows Server 2008 R2, or Windows Vista node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr". The indicated IP address will be unique to your alarm-providing node. Note the IP address.
  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 for "nodeabc" below and substituting your IP address noted in the previous step: \\nodeabc:\intouch!$system.
  3. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.

Terminal Services Behavior

Modify terminal services behavior in Windows Server 2008 for proper operation of the software. Wonderware software detects when an application is running in the console. Windows Server 2008 treats all remote connections as a remote RDP session regardless of /console or /admin switches in the mstsc connection.

To disable the ability to switch users through the Group Policy interface

  1. Click Start. The Start menu appears.
  2. Select Run. The Run dialog box appears.
  3. In the Run dialog box, enter gpedit.msc
  4. Click OK. The Group Policy dialog box appears.
  5. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.
  6. 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.
  7. On the File menu, click Exit to close the Group Policy editor.

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

To disable the ability to switch users through the Registry Editor

  1. Click Start. The Start menu appears.
  2. Click Run. The Run dialog box appears.
  3. In the Run dialog box, enter regedit.exe.
  4. Click OK. The Registry Editor dialog box appears.
  5. Go to the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows > CurrentVersion > Policies > System.
  6. Right-click and select DWORD (32-bit) Value. Name it HideFastUserSwitching.
  7. Set the HideFastUserSwitching data value to 1.
  8. 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 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. 

Using Multiple Network Interface Cards

If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or else a remote node cannot connect to the Galaxy Repository node.

A connection is a term used to define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under certain circumstances, the connection on your computer can change if, for example, the IP address on your network card changes. Your computer's connection can be affected by external factors. During computer startup, and each time a connection changes, the operating system goes through an "Identifying" process to determine which profile should be assigned to the connection.

A profile is a collection of firewall settings that can be applied to a connection. There are three profiles currently defined in the operating system: Domain, Public, and Private.

This is important because the OS Configuration utility and the Firewall utility apply their firewall exceptions to the Domain and Private profiles only. 

As previously noted, you can specify which profile you want assigned to a connection as long as that connection is not a Domain connection. This is done through the "Network and Sharing Center". Click the Network icon located on the right side of the task bar and then click one of the networks that are shown. You can change a connection from a Public profile to a Private profile. The firewall calls these settings "Profiles" but the network calls them "Location types." 

On computers using dual NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. Windows typically assigns the second NIC the Public profile. 

The first issue is that your entire computer (all connections) is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the second connection to the Private profile for any of the  firewall exceptions to work. You want the active profile on the message exchange (MX) NIC to be the profile opened by OS Configuration.

The second issue is that it appears that a restart of your computer, or even a restart of a computer to which you are connected, can change your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have to change the connection back to the Private profile after each restart or a restart of the connected computer.

To avoid these NIC issues and prevent the “Identifying” process from taking place on a connection and changing the assigned profile, certain items must be present in the definition of the connection. Follow these rules and procedures:

  1. If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.
  2. If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup provided in the Wonderware Application Server User's Guide and the accompanying online help.
  1. Assign the NIC an IP address, subnet mask and gateway address. Typically, these addresses are internal, non-routable addresses. For example, 192.168.1.xx and 10.x.x.x are common addresses of this type.
  2. A NIC acting as Redundancy Message Channel (RMC) does not require a default gateway. Otherwise, the gateway can be the same as the IP address. Vista and Windows Server 2008 will identify this NIC and assign it a Private profile.

If you do not configure the second NIC, Vista and Windows Server 2008 will assign a profile of Public to this NIC and cause all of the Wonderware product firewall exceptions to be deactivated on all NICs.

  1. Set a security policy so that Windows Vista and Windows Server 2008 do not re-set the RMC NIC to a Public profile on rebooting the system or changing the IP address. To make the Private profile setting persistent, do the following:
  1. On the Windows Start menu, click Run.
  2. Enter and run this command: SECPOL.MSC. The Local Security Settings menu appears.
  3. Select Network List Manager Policies on the menu tree.
  4. Select Unidentified Network from the Network Names displayed.
  5. Right-click, then select Properties, and then change the Location type from Not configured to Private.
  6. Exit the menu and return to Windows.

  1. If you have more than two NICs, make sure all connected NICs are configured with an IP address.

< top of document >

Product Compatibility

Wonderware InTouch HMI version 10.5 can be used with the following Wonderware products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Product Version Compatibility Co-existence
Wonderware Application Server 3.5 Y Y
Wonderware Application Server 3.1, 3.1 SP1, 3.1 SP2 P01, 3.1 SP3, 3.2 Y N
Wonderware Historian Client 10.0 SP1 Y N
Wonderware Historian Client 10.0 SP2 Y Y
Wonderware InTouch CE 10.1 N N
Wonderware Historian Server 10.0 SP1 Y Y
Wonderware Manufacturing Execution System 4.0, 4.0 SP1 Y Y
Wonderware Information Server 4.0, 4.0 SP1 Y N
Wonderware Information Server 4.5 Y Y
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.0 SP1, 9.0 SP2, and 9.5 Y Y
Wonderware QI Analyst™ 8.0 SP2 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.1 Y Y
Wonderware Intelligence™ 1.5 Y Y

In some cases, the InTouch HMI is supported in newer environments than a compatible product. The 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 installation instructions in English, see the ArchestrA System Platform Installation Guide (ASP_Install_Guide.pdf) or ArchestrA System Platform Installation Help (ASP_Install_Guide.chm).
The information provided in this Readme file supersedes the InTouch Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
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.

Installing the Wonderware InTouch HMI

The simplified process makes installing InTouch easier than ever.
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:

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


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

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

You must have the following software installed and enabled on your computer before you install the software:

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.

Important: If you are using Windows Server 2008 R2 operating system, the .NET Framework feature must be enabled before you run the installation.

To enable the .NET Framework feature

  1. In Control Panel, open Administrative Tools.
  2. Open Server Manager, and then click Features.
  3. In .NET Framework 3.5.1 Features, select the .NET Framework 3.5.1 check box. Click Next.
  4. Click Add Features to start the wizard.
  5. In the features list, select the .NET Framework 3.5.1 Features check box.

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 ArchestrA 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 existing user account, it should meet the following requirements:

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 located in the 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 commence the installation and to 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 installing a single product—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
      • Application Server Bootstrap
      • InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory
    2. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • Application Server Bootstrap, IDE, Galaxy Repository, Application Server documentation
      • InTouch sample applications
  6. When the installation prompts you to verify your selection, you have the opportunity to customize your installation.
    1. If you choose InTouch Run Time Only, the following will be installed:
      • InTouch sample applications
      • Additional InTouch Supplemental Components: InTouch SPC Pro and InTouch 16 pen trend
    2. If you chose InTouch Development and Run Time, you can add the following components:
      • Additional InTouch Supplemental Components: InTouch SPC Pro and InTouch 16 pen trend
  7. 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.
  8. 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 prerequisites not yet met. The installation checks your system, lists the missing prerequisites, and installs them for you.
  9. The installation proceeds to completion. You must restart your system when the installation is complete.

Installing Your Wonderware Product License

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

You use the ArchestrA License Manager to install the contents of the ARCHESTRA.LIC file to the computer where you have installed the InTouch HMI. The ArchestrA License Manager is included as a common ArchestrA component when you install the InTouch HMI.

To install your Wonderware product license

  1. Start the ArchestrA License Manager by doing the following:
    1. Ensure that the installation DVD is in your DVD drive.
    2. Click Start, and then Programs to show the Wonderware folder.
    3. Click the Wonderware folder, and then click the Common folder to show the list of common utilities.
    4. Click ArchestrA License Manager.
  2. Click File, and then Install License File. The Choose a License File to Install dialog box appears.
  3. Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.
  4. The Destination Computer for Installation dialog box appears. Type the domain and computer names.
    The ArchestrA License Manager copies the ARCHESTRA.LIC file to the C:\Program Files\Common Files\ArchestrA\License folder on the selected computer.

Now you can start creating InTouch applications. The next section explains how to manage an application from the ArchestrA IDE.

Antivirus Software Exclusions

After installing Wonderware InTouch HMI Version 10.5, configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders for 32-bit operating systems:

C:\Program Files\ArchestrA\
C:\Program Files\Common files\ArchestrA\
C:\Program Files\FactorySuite\ (may not exist in newer installations)
C:\Program Files\Wonderware\
C:\Documents and Settings\All Users\Application Data\ArchestrA

For 64-bit operating systems, the exclusion must reflect the (x86) program files directory instead:
C:\Program Files (x86)\ArchestrA\
C:\Program Files (x86)\Common files\ArchestrA\
C:\Program Files (x86)\FactorySuite\ (may not exist in newer installations)
C:\Program Files (x86)\Wonderware\

From Application Server Platform objects:

From Application Server Engine objects:

<InTouch Application folder path> including: 
C:\Documents and Settings\All Users\Application Data\ArchestrA\

<SMCLoggerStoragefilepath>. The default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\

SQL Server database files of type:


Ensure that the subfolders of the listed directories are also excluded. Specify folder names accordingly if you are using a 64-bit operating system. For example, the program file's root directory in a 64-bit operating system is C:\Program Files (x86)\... and the application data root directory in a 32-bit operating system is C:\ProgramData\...

Modifying, Repairing, or Removing the InTouch HMI

To modify, repair, or remove an installation

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Click the Add or Remove Programs option in Windows Control Panel. (In Windows Server 2008 R2, this is called Uninstall or Change a Program.) 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 the installation.

Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

Upgrading to Version 10.5 from an Earlier Version of the InTouch HMI

After the hardware and software requirements are met, including the proper operating system, SQL server and other prerequisites, you can upgrade to Wonderware InTouch HMI version 10.5 from the following versions of the InTouch HMI:

You can only upgrade ArchestrA System Platform products that are already installed and you will not be able to install new products within the ArchestrA System Platform that have an upgrade process. The installed components that need to be upgraded are selected and disabled. You can neither clear these check boxes nor select more components during the upgrade.

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.

Migrating Applications to Wonderware InTouch HMI Version 10.5

You can migrate applications from the following earlier versions of InTouch HMI to version 10.5:

< top of document >

Resolved Issues - Wonderware InTouch 10.5

This section describes important resolved issues in Wonderware InTouch HMI Version 10.5. This list is not a comprehensive list of all resolved issues for this release. The issues are listed by their Change Request number.

L00096155: HF CR L00093765 (Hotfix 1484) SR 15315044: A memory leak of about 4 MB per minute most likely occurs due to hundreds of calls to SetCustomPropertyValue.
L00103265: WindowViewer stops responding while writing to an I/O tag of string type with an I/O restriction license.
L00103656: WindowMaker stops responding when an XML file is imported with a minimum reference for an analog user input animation that contains a numeric character such as 33TT:RT.
L00105871: While you are converting windows after migration, if the required ActiveX control (referenced in the window) is not installed, the following message is displayed:
"Invalid reference or unknown OCX method".
WindowMaker stops responding when you click OK. This happens if the special character "%" is logged in the System Management Console (SMC).
L00106211: WindowViewer stops responding if the window is hidden when input is provided on the keyboard.
L00106307: In certain scenarios, WindowMaker stops responding while printing a window if you have selected the Database Details and Link Details check boxes.
HF CR L00113000 (Hotfix 2508) SR 31711779: The TrendClient control causes a memory leak at run time when it is placed in ArchestrA Symbol and is embedded in an InTouch window.
L00111197: HF CR L00100763 (Hotfix 1788) SR 12610815: The SMC log shows the following error:
ERROR: ArchestrA.Visualization.GraphicLibrary.aaDataSubscriptionManager' failed
L00111579: HF CR L00100763 (Hotfix 1788) SR 12610815: Leading zeros are ignored in an ArchestrA Symbol that is published to the Wonderware Information Server.
HF CR L00111719 (Hotfix 2448) SR 40211327: The AlarmDB Restore utility fails to restore records from archived files.
L00112173: HF CR L00111945 (Hotfix 2458) SR 1531606: When you close a modeless ArchestrA Symbol that is opened using the ShowSymbol function, Windowviewer is minimized.
L00112447: HF CR L00111777 (Hotfix 2446) SR 17133361: The propagation of SmartSymbol edit changes for a large number of windows results in access violation failures of values on wwHeap. This problem occurs as the memory is allocated on wwHeap with the GMEM_MOVEABLE parameter.
L00112665: HF CR L00110519 (Hotfix 2380) SR 41810008: I/O data randomly stops updating for several seconds continuing on up to several minutes.
L00113070: HF CR L00105319 (Hotfix 2065) SR 103117936: InTouch WindowViewer stops responding intermittently.
L00113174: HF CR L00112534 (Hotfix 2485] SR 40211374: When the number of milliseconds of an alarm starts with a "0", the GetXmlCurrentAlarms2 method returns the timestamp without the "0". For example, if an alarm was generated at 01:27:51:051 PM, then the alarm consumer reports it as 01:27:51:510 PM.
L00113177: HF CR L00110515 (Hotfix 2365) SR 10415972: A memory leak occurs due to increased private bytes in a published application that includes ArchestrA Symbols.
L00113692: HF CR L00111854 (Hotfix 2453): The last known value shown at run time is not correct when advanced formatting is applied.
L00114271: HF CR L00114119 SR 103121884: The Minimum and Maximum text labels are swapped in the Keyboard Resizable dialog box in the Japanese version of the InTouch HMI.
L00114442: HF CR L00112069 (Hotfix 2467) SR 33410861: Duplicate alarms are logged into the alarm database when the Alarm DB Logger is configured to log ArchestrA alarms.
L00114611: HF CR L00113997 SR 41610118: When the cursor is placed in the common area of two or more hotlinks, the background window gets selected.
L00114749: HF CR L00114273 SR 103121431: The condition script WHILE TRUE stops executing when the expression is still TRUE.
L00115031: HF CR L00113890 SR 41610119: The DBDump utility sometimes stops responding if you have selected the Group output by types check box.
L00115098: HF CR L00114418 SR 103121936: While setting the value of #AlarmViewerCtrl1.FlashUnackAlarms, the following error message is logged:
!ERR Alarm record buffer too small [=139 bytes] in AlmBufGetAlarm
L00115200: HF CR L00112659 (Hotfix 2495) SR 103120818: When an event is triggered from an ArchestrA Symbol at run time, the Operator Node field in the AlarmViewer control does not show the name of source node. The Operator node shows only the component name. To resolve this issue, the name of the computer from which the event was generated is prefixed with the component name.

< top of document >

Known Issues - Wonderware InTouch 10.5

This section describes known issues in Wonderware InTouch HMI Version 10.5. The issues are listed by their Change Request number:

L00077445: Touch push button animations do not work on client controls.
L00078446: The Symbol Editor stops responding when you edit the "format string" property of the “checked list box” client control.
L00081354: Windows do not print if the window name contains special characters.

Rename the directory path and the filename to remove all special characters.
L00082814: WindowViewer does not start when configured to start as a service. An error message appears “Access denied.” The user win.ini and the MS Windows system win.ini are not in sync.

See http://support.microsoft.com/kb/832048 to pick up the correct system win.ini file.
L00083270: Spaces are not imported as part of the translation for the selected language.
L00083636: Terminal Server sessions crash when a ViewApp is changed and then redeployed while WindowViewer is running in a 100-terminal session configuration across 10 Terminal Servers.

For certain applications and systems, you need to adjust the restart delay time by adding "ViewManagedRestartWaitPeriod" to the "Intouch" section in the Win.ini file. The default delay time is 5-seconds.
L00083828: There are inconsistencies between the selected language and the strings that are shown. 
L00083847: After you click "NO" in the Network Application Development properties dialog box, WindowViewer does not ask you to "restart" and "load" changes.  
L00083909: InTouch applications receive quality status and locale information from the deployed Galaxy. InTouch applications cannot receive data from an undeployed Galaxy.
L00084010: Translations are not loading after embedding a primitive from a different Galaxy employing a different language. Only the default English strings are shown.  
L00084834: The Annotation window stops responding if you use standard Windows cut, copy, and paste shortcuts.

Microsoft provides a Microsoft.Ink.dll CLR2.0 Update. See the following link to download the update.
L00086229: Running the AlarmDBLogger Manager as a Windows service is not working.

Disable this option for Vista.
L00088095: If you are a Terminal Server user and you do not have "Administrator" privileges, you must be either a "Power User," or a "Remote Desktop User" to access the license. Otherwise, you receive a licensing error message. It is not obvious that you are missing rights and privileges necessary to successfully login.
L00088673: Non-English locale animation static "text" strings are not propagated to default (English) locale static "text" strings.  
L00088871: Exporting the language dictionary using Microsoft Vista may result in not being able to retrieve the dictionary file as a standard user.

When running WindowMaker as a standard user elevated to administrator rights as a different user than logged onto the Desktop, exporting  the Language dictionary opens a default path that is not accessible by the standard user.

It is recommend that you change the path to a public folder location.
L00088974: When an ArchestrA Symbol is exported from an application developed with an English version of InTouch and imported into an application developed in a different InTouch Language, like French, the strings of the ArchestrA Symbol cannot be substituted in WindowMaker.
L00088993: An ArchestrA Symbol with string substitutions is not showing the string substitutions in WindowMaker when the Galaxy Primary language is not English.
L00088998: InTouch Applications, which are configured to support runtime language switching and contain ArchestrA Symbols and native InTouch animations, initially show mixed language strings, if executed in an operating system language different from the one in which it was originally developed.
L00089000: The EnableDisableKeys function does not work in a Vista operating system, if the user is configured as a Standard User. Use the runtime environment configuration options in WindowMaker in addition to the operating system security policies to lock the application from access to the desktop.
L00092171: When starting AlarmDbLoggerManager, the Settings, Stop, and Start buttons remain disabled.
L00092204: SPCPro is not supported on the Windows Vista 64-bit operating system, resulting in inconsistent run-time behavior for SPC DDE items (e.g. autocollection, startcollection).
L00092635: IDE imports files in Galaxy_XXX_localeID_Alarm_Comments_Untranslated.txt. InTouch cannot import files in that format. InTouch HMI imports files in Galaxy_XXX_localeID_Alarm_Comments.txt format and the header information.
L00092766, L00093388:
On Windows Vista or later operating systems, the following help files cannot open:  ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, Hdmerge.hlp and testprot.hlp. Microsoft WinHlp32.exe is required to display 32-bit Help files that have the ".hlp" file name extension. To view .hlp files on Windows Vista, you need to install this application.
L00092774, L00096793: The alarm hot backup pair does not work on Windows Vista or Windows Server 2008 for the query \\Machinename:ipaddress\intouch!$system using mstsc/console since no IP address required for remote logins. In this case, InTouch is the only provider.
L00092964: WindowViewer reports low memory upon startup regardless if the system has enough memory available.
L00093253: If you open a symbol with ShowSymbol animation and the symbol contains one or more expressions involving datapoints that are repeated across thousands of expressions already displayed in InTouch windows, the viewer freezes while all the datapoints are evaluated/updated.
L00093559: The calendar control in the graphic editor is drawn with different size fonts on different operating systems. For example, the sizes shown are different on Windows Server 2003 and 2008 operating systems. The size of the calendar control does not change when you change the font on the Windows Vista operating system. If a symbol with calendar control is saved in a Windows Server 2003 system and then opened in a Windows Server 2008 system, the size changes after export and import. This affects the symbol layout as well. As a workaround, ensure that your operating system themes are consistent in screen resolution, DPI, icon size, and font size settings.
L00094181: In a Windows Server 2008 computer hosting an InTouch application that is an alarm provider, the alarm query for retrieving alarms from a remote computer does not work if the application is not running within the console. See Using Wonderware InTouch with Windows Vista, Windows 7, and Windows Server 2008 R2 for details.
L00096097: Changes on InTouch CE (Windows Server 2008 64-bit) are not recognized by the validation process and display "Validation is already done".
L00096310: Terminal Servers have at least 20% higher CPU usage on Windows Server 2008 (32-bit and 64-bit).
L00096790: Help for the Annotate Layout function in InTouch states that it is supported only on an XP Tablet PC. Windows Vista is also supported.
L00096840 On Windows Server 2008, the TseQueryRunningOnConsole() and TseQueryRunningOnClient() functions return incorrect values from a remote logon when using the same InTouch View opened from a console.
L00099595 If you install InTouch with the Application Server auto-install checkbox selected, the Application Server installation location cannot be on a mapped network drive. This limitation occurs only on Windows Server 2008 (32/64-bit) and Windows Vista (32/64-bit) operating systems.

You can use the following procedure as workaround: Cancel the AutoAppServerLaunch and manually navigate to the network install folder to launch the Application Server install, or install both InTouch and Application Server using the installation CDs.

L00102808: InTouch View application cannot run if an ArchestrA graphic name contains localized characters and if is deployed on an English operating system.
L00103242: If pre-existing InTouch application Window files (.WVW) are compiled and recreated when the Window is opened for the first time in WindowViewer in InTouch 10.5 with a resolution that is different from the one in which the files were originally compiled, the logger displays the following:
Warning message - "Loading Window <Window Index Number> WinChunkRead Failed".
Error message - "Failed to load Window Index <Window Index Number>. Stage=<Stage Number> Linked=<Linked Number>".
L00103392: When the minimum and maximum references are configured using I/O tags, the I/O tags which are InTouch local tags and have tag types, are considered as any other tag. When the I/O tag refers to a remote reference which has a string value, the I/O tag value, which is 0, is used for the Minimum and Maximum fields. When minimum and maximum references are configured using remote references (RTR), the RTR does not have type information and InTouch assigns default type TYPE_STRING for any RTR. The minimum and maximum references resolve the RTR as strings.
L00103534: WindowViewer cannot run as a service for Windows 7 and Windows Server 2008 R2.
L00103603: When the quality of minimum and maximum references are in a 'Bad' state, and the configured reference is a local InTouch tag, the minimum and maximum limits of the InTouch tag from the tag database are used for the minimum and maximum references. When minimum and maximum references are configured using remote tag references, the minimum and maximum limits of the data type of the remote tag reference are used for the minimum and maximum references. When the remote tag reference is a string, the decimal point (".") is used to find whether the remote tag reference has an integer or a real value.
L00103813: The following functions are not supported on Windows 7 and Windows Server 2008 R2 platforms: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
L00104006: If the window is opened Local Message Exchange (LMX) to activate the reference. The UDA sends the last known 'Good' value and propagates the activation to the DAtest server. When it receives a 'Bad' connection from the DAtest server, it sends the "Bad" quality value. InTouch receives only the "Bad" quality value from the UDA with subsequent closed and opened windows.
L00104093: The display of the minimum and maximum references based on quality holds 'Good' during the initialization of WindowViewer. Transition is ignored for all quality states except 'Good'. When transition happens from 'Initializing' to 'Good' or from 'Bad' to 'Good', the reference is poked and the 'Good' value is displayed.
L00105367: When the application migrates to a different operating system such as Windows Server 2008, Windows 7, or Vista, with SMC kept open, the logger displays the following warning message:
"Unable to connect the logger if running on Windows 2003 sp1 or Windows XP Operating systems".
L00105601: The new .FromPriority and .ToPriority properties for the ArchestrA AlarmClient Control have some limitations.

These properties determine the range of alarms that are returned to the control. For example, if you set the .FromPriority property to 50 and the .ToPriority to 75, only those alarms that have a priority value between 50 and 75 (and inclusive of 50 and 75) are returned. By default, the .FromPriority is set to 1, and the .ToPriority is set to 999. You can set an alarm priority in one of two ways: by setting it in the filter of the SQL query or through scripting. However, the query filter always takes precedence. The script-accessible alarm priority properties TO and FROM only do not work if either priority is specified in the query filter. To use the script-accessible alarm priority properties, do not set the priority in the query filter. Finally, the script-accessible alarm priority properties TO and FROM only apply to the "historical" alarms mode. They do not work with the "current" or "recent" alarms modes.

L00106173: The utility 'Change Network Account' fails to run on a computer with InTouch installation only. Workaround: Install a compatible version of Wonderware Application Server (WAS) on the InTouch node. You may install just bootstrap, bootstrap+IDE, or full GR. Installing Wonderware Application Server allows the Change Network Account Utility to run.
L00106668: If you open a managed application in InTouch WindowViewer as non-admin user on a node that has the Windows 7 operating system installed with User Account Control enabled, while at the same time that the application’s WinPlatform object, located on a remote Galaxy Repository node, is undeploying, WindowViewer hangs for several minutes and the following message appears in the Logger: "! PostMessage failed - Error from the method ActivateChildWindow() of vumain.cpp file." However, the application will eventually open. Note that this issue is intermittent and only happens occasionally.
L00106914: SPCPro Control Chart, Pareto, and Histogram Wizard control cannot be embedded in a WindowMaker window in Windows Server 2008 and Windows 7 operating systems.
L00107109: After installing InTouch HMI, NetDDE Helper does not start and the following error message appears:
"Windows could not start the Wonderware NetDDE Helper service on target computer".
For security reasons, Microsoft no longer supports NetDDE on the Windows Vista and Windows Server 2008 operating systems. NetDDE is disabled by default on Windows XP Service Pack 2 and Windows Server 2003. However, Microsoft still supports the regular DDE.
L00107322: 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. Note that to upgrade VMware video drivers, you must upgrade the VMware tools, which includes all the drivers for the system.

This problem was experienced during testing of this release using the following VMware Software:

  • VMware, Inc. vCenter Lab Manager 4.0 (
  • VMware Tools = Old Version (add/remove programs) =
  • VMware Tools = Old Version (Help/about) = 3.5.0, B123630
  • Video driver version = Old Version (Display properties) VMWare SVGA2 version ( 7-28-2008

The problem can be corrected by upgrading VMware tools and the video driver with the following versions. Note that additional information can be found at the following VMware link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011709.

  • VMware Tools = Upgraded Version (add/remove programs)
  • VMware Tools = Upgraded Version (Help/about) = 4.0.0 B208167
  • Video driver version = New Version (Display properties) VMware SVGA 3D (Microsoft Corporation - WDDM) Version ( 9-17-2009

L00107379: The InTouch alarm group definition file (group.def) does not get copied to the execution directory of a deployed InTouchViewApp. A workaround is provided in Tech Note 256, "Using Network Application Development (NAD) with InTouch."
L00107919: When you log on to the ArchestrA System Management Console (SMC) Platform Manager with a newly-created, Active Directory OS Group account for Application Server, and that OS Group account does not contain a "Full Name" description, the following error is generated: "User does not belong to any of the configured Roles". This also occurs when you log on to an InTouch application or Object Viewer.

To work around this issue, log on to the ArchestrA IDE first using the new OS Group account and then log on to the SMC, InTouch application, or Object Viewer.

L00110652: Running a Quick Function with an OnShow or While Showing condition and with an Active X control, such as AlarmView control, can crash WindowViewer due to the Show Window and Active X call sequence. As a work around, it is not recommended to use Active X controls in an OnShow or OnHide script. If you do use an Active X control, you must call the Active X control first. For example, to show Window2 with an AlarmViewer control:

Do not use this sequence:

Show "Window2";
#AlarmViewerCtrl1.SuppressVisible ();

Use this sequence:

#AlarmViewerCtrl1.SuppressVisible ();
Show "Window2";

L00111062: When logging on to an InTouch application configured for SmartCard authentication, if you remove the card from the reader while the logon is in-progress, the logon fails but no error or information message appears.
L00111272: (Hotfix 2421) SR 33932385: An ArchestrA Graphics symbol can remain selected when the mouse pointer is quickly moved over the symbol. This issue occurs only on Windows Server 2008 or Windows Vista 64 bit computers only.

As a workaround, you can right click the symbol, then select Send to back on the context menu.

L00112188: Installing InTouch HMI on a computer used as a domain controller is not supported.
L00112470: InTouch 10.1 SP3 on the Windows Server 2008 SP2 32-bit operating system, without any previous InTouch versions already installed, may "fail to respond" and cause a dialog box to appear asking if the application should be stopped, debugged, or get help request. This can happen with InTouch.exe (InTouch Application Manager), WM.exe (WindowMaker) or View.exe (WindowViewer). This issue has been associated with computers that are in a workgroup and are not part of a domain.

To work around this issue:

  1. Close the application.
  2. Create an empty text file and call it "Win.ini".
  3. Open the "Computer" icon.
  4. Click on the "Organize" menu item and select "Folder and search options".
  5. Click on the "View" tab and enable "Show hidden files, folders, and drives".
  6. Double-click on the system drive to open its display (or whichever drive is hosting the user profiles).
  7. Click on the "Users" folder.
  8. Now for EACH user who will be using InTouch:
    1. Click on the user's folder and go to the "AppData\Local\Wonderware" folder.
    2. If you do NOT see an existing Win.ini file there, copy the empty file you made earlier.
  9. Close the "Computer" display dialog box.

This completes the workaround. When you next run InTouch.exe (InTouch Application Manager), an application fault should not occur.

L00113454: When you create an analog tag in an InTouch window and add two Value Display Analog animation links or UserInput Analog animation links, one to display the analog tag in Decimal format and the other one to display the tag in the Hex format, then at run time both the values are displayed correctly.

When you convert the InTouch window into XML format using ArchestrA Web Exporter so that it can be published and viewed in Information Server, then the value in the Hex format is displayed as a decimal number in the Value Display Analog animation link or in the UserInput Analog animation link. The same error occurs if you add a Value Display Analog animation link or a UserInput analog animation link to display the analog tag in Binary format.

L00114352: SR: 33811759: When you start InTouch WindowViewer and open a window that has an ArchestrA symbol with an embedded Alarm Control, the following warning message can appear multiple times in succession in the logger: Failed to reconnect to data source.
The warning message is incorrect, the embedded Alarm Control does connect to the InTouch WindowViewer and the warning messages can be ignored.
L00115036: 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.
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.
L00116459: The remote node fails to connect to a WWALMDB database that is created using SQL Express Edition.

Workaround: Set the SQL Server Express authentication from Windows mode to Mixed mode.

To change SQL Server Express Authentication mode

  1. Download and install the x86 version of SQL Server 2008 Management Studio Express from http://www.microsoft.com/download/en/details.aspx?id=7593.
  2. After installation, right-click SqlExpress Connection, click Properties, and then click Security.
  3. Change the SQL Server Express authentication from Windows mode to Mixed mode and click OK.
  4. Restart the database instance or computer.
L00116828: 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.
L00116883: Due to a Windows operating system issue, InTouch HMI and related applications, such as Alarm DB Logger, can crash on startup if installed to a drive other than C:\. As a workaround, create an empty file named win.ini in folder C:\Users\<username>\AppData\Local\Wonderware where "username" is the name of the user attempting to start the application.
L00117077: WindowViewer can become unresponsive when a blocking script is executed from a "Button Down" event. As a workaround: (1) Use a "Button Up" event to script blocking function calls such as ShowGraphic-modal and SignedWrite. (2) If using a push-button animation, click the "ReleaseButtonUp" option.

Print Issue

PrintWindow() cannot print the following controls in ArchestrA Symbols: ListBox, DateTimePicker, CalenderControl, EditBox, CheckBox, RadioButtonGroup, ComboBox, AlarmClient or TrendClient.

OnShow Symbol Script Issue

When the OnShow Symbol Script contains external references, the data may not be available at run time due to a timing issue. Application Server 3.1 SP2 enabled a configurable OnShow Symbol Script timeout to allow external references to resolve. The symbol will be drawn disabled and all scripts will be delayed. Once the data is available, the symbol will be enabled and the OnShow Symbol Script will execute first, followed by the rest of the scripts. If the external data does not become available within the configured timeout, the OnShow script will still execute but will place a message in the Logger that not all references have been resolved. Because named scripts will be blocked until OnShow executes, some events may be missed. For example, the named script OnDataChange will not run during the time OnShow is delayed even if the data point is changing.

InTouch Documentation Issues

The following table lists all documentation corrections to InTouch 10.5 documentation.

Item Location of Change Existing Documentation Change
1 Creating and Managing ArchestrA Graphics User’s Guide (aaGraphics.pdf), "String Substitutions and Language Switching" section, page 426

Application Server Help (IDE.chm),
"String Substitutions and Language Switching" topic
n/a Add the following text after the first paragraph:

If you perform a first-time string substitution on an embedded symbol in the primary language, that substitution is shown in the secondary languages. You can then perform a substitution in the secondary language to create a string substitution specific to the secondary language.

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

If you perform a string substitution in a secondary language with an existing string substitution in the primary language, the new substitution is applied to the secondary language only.
2 InTouch® HMI Documentation Addendum
".CVS Format for Printing Windows" topic, page 25

The current screen capture shows "Conveyor, Main, Reactor display, Menu" The screen capture should show "Conveyor,Main,Reactor display,Menu"
3 InTouch® HMI Documentation Addendum
"InTouch User's Guide" section, pages 24-26.

InTouch User's Guide (entire section). Delete entire InTouch User's Guide section.
4 InTouch® HMI Help
When you try to open the help file page for the GetWindowName function, the help page for the IOSetRemoteReferences function appears. The help file page for the GetWindowName function should appear.
5 InTouch® HMI Alarms and Events Guide
(ITAlarmsandEvents.pdf), "SQL Server Accounts for Alarm DB Logger Manager" section, page 274

InTouch® HMI Help (WM.chm), "SQL Server Accounts for Alarm DB Logger Manager" topic

The passwords listed are: wwAdmin, wwPower, and wwUser. The passwords listed should be: wwadmin, wwpower, and wwuser.
6 InTouch® HMI Documentation Addendum
(ITAddendum.pdf), "Performing a Secured Write" section, page 32, and "Performing a Verified Write" section, page 35

InTouch® HMI Help (WM.chm), "Performing a Secured Write" topic and "Performing a Verified Write" topic

domain_name/user_name domain_name\user_name
7 InTouch® HMI Documentation Addendum
(ITAddendum.pdf), "Configuring the Memory Health Check Interval" section, page 43

InTouch® HMI Help (WM.chm), "Configuring the Memory Health Check Interval" topic

If the memory or GDI count limit is exceeded, the system starts removing windows. If the memory or GDI count limit is exceeded, the system starts removing windows from cache memory.
8 InTouch® HMI Documentation Addendum
(ITAddendum.pdf), "Associating All Galaxy Graphics with an InTouchViewApp" section, page 80

InTouch® HMI Help (WM.chm), "Associating All Galaxy Graphics with an InTouchViewApp" topic

Right-click the InTouchViewApp template you wish to configure.

If the $InTouchViewApp template is not yet initialized or checked out, the Include all Galaxy graphics with this application check box is not available.

Right-click the derived InTouchViewApp template you wish to configure.

If the $InTouchViewApp template is not yet initialized or checked out, a warning message appears.

9 InTouch® HMI Documentation Addendum
(ITAddendum.pdf), "Security" section, page 96

InTouch® HMI Help (WM.chm), "Security" topic

If you are opening an InTouch application, you must log on again to re-authenticate yourself to run Tag Viewer. If you are opening an InTouch application, you can run Tag Viewer if your user access level is >= the minimum access level.

< top of document >

InTouch Documentation

The InTouch product library consists of a set of Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:
\Archestra System Platform\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.

Searching InTouch Books with Adobe Reader

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

To search for information across all InTouch books simultaneously

  1. Open Adobe Reader.
  2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
  3. Type the word or phrase that you want to search for in the InTouch books.
  4. In the Where would you like to search area, select the option to search all PDF books.
  5. If necessary, locate the InTouch version 10 PDF package located on your Wonderware CD or on a network folder containing copies of the InTouch PDF book files.
  6. Click Search. Adobe Reader lists the InTouch books containing information that matches your search criteria.
  7. Click on the links to open the InTouch book to the topic containing the information that meets your search criteria.

< top of document >

© 2012 Invensys Systems, Inc. All Rights Reserved.