Wonderware® InTouch® HMI Version 10.1 Service Pack 3 (SP3) Patch 01 Readme

Last revision: 04/29/2011

About This Readme

This document includes information about Wonderware®InTouch®HMI 10.1 SP3 (Service Pack 3) Patch 01. It updates the previous ReadMe files included with Wonderware InTouch HMI 10.1, Wonderware InTouch HMI 10.1 SP2, Wonderware InTouch HMI 10.1 SP2 Patch 01, and Wonderware InTouch HMI 10.1 SP3.

Important!

< top of document >


Wonderware InTouch HMI Version 10.1 SP3 Patch 01 Information

System Requirements

Product Compatibility

Applying InTouch 10.1 SP3 Patch 01 to InTouch 10.1 SP3

Resolved Issues - Wonderware InTouch 10.1 SP3 Patch 01

Known Issues - Wonderware InTouch 10.1 SP3 Patch 01

Wonderware InTouch HMI Version 10.1 SP3 Information

Support for New Operating Systems

XML Graphics Importer

System Requirements

Using Wonderware InTouch with Windows 7 and Windows Server 2008 R2

Installing Microsoft .NET Framework on Wonderware InTouch 10.1 SP3

Upgrading from a Previous Version of Wonderware InTouch

Product Compatibility

Resolved Issues - Wonderware InTouch 10.1 SP3

Known Issues - Wonderware InTouch 10.1 SP3

Antivirus Software Exclusions

Wonderware InTouch® HMI Version 10.1 SP2 Patch 01 Information

Clarifications From Previous InTouch 10.1 Readme Notes

Applying Patch 01 to InTouch Version 10.1 SP2

Product Compatibility

Resolved Issues - InTouch Version 10.1 SP2 Patch 01

Known Issues - InTouch Version 10.1 SP2 Patch 01

Wonderware InTouch® HMI Version 10.1 SP2 Information

New Features of InTouch Version 10.1 SP2

System Requirements

Known Issues – InTouch HMI Version 10.1 SP2

InTouch HMI Documentation Issues

InTouch HMI Documentation

InTouch HMI Version 10.1 Information

About This Release

Antivirus Software Exclusions

System Requirements

Resolved Issues – InTouch 10.1

Known Issues – InTouch 10.1

InTouch Documentation Issues

InTouch Documentation

< top of document >


System Requirements

The hardware and software requirements for this patch are the same as for the previous release.

< top of document >


Product Compatibility

Wonderware InTouch HMI Version 10.1 SP3 Patch 01 is compatible and can co-exist with the following products:

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

< top of document >


Applying InTouch 10.1 SP3 Patch 01 to InTouch 10.1 SP3

This section explains how to apply InTouch 10.1 SP3 Patch 01 to existing instances of InTouch 10.1 SP3 installed at your site.

Important: InTouch 10.1 SP3 Patch 01 must be applied only to InTouch version 10.1 SP3. No other version of InTouch can be upgraded with this patch.

The InTouch 10.1 SP3 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 10.1 SP3 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 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.
  6. Accept the license.
  7. Click Next. The Updating System dialog box shows the progress of the patch update.
  8. If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
  9. Click Finish.
  10. Click Yes to restart your computer.

< top of document >


Resolved Issues - Wonderware InTouch 10.1 SP3 Patch 01

InTouch version 10.1 SP3 Patch 01 resolves the following issues listed by their Change Request number:

L00072507: SR 103112359: The GDI object leaks when an object is moved with the keyboard in WindowMaker and it does not reduce even when the window is closed.
L00078567: SR 23516152: The GDI object leaks when you activate the resizable keypad in WindowViewer.
L00091065: HF CR L00090007 (Hotfix 1307) SR 12610609: The subscribe API function, Sort Flag sfUseOriginatedTime(), does not work.
L00092150: SR 33810897: A data change script does not work, but a discrete pushbutton script works for an operator who has no permission to write an attribute to UDA.
L00092893: SR 38910040: If a null value is passed as an argument in any action script of an ArchestrA Symbol, a red cross is displayed for the symbol at run time in WindowViewer or the symbol is not displayed at all.
L00093755: SR 38910082: When you convert a graphic to a group, a red cross appears in the graphic.
L00094984: SR 24514159: WindowMaker stops responding while initializing ActiveX. If a new ActiveX control is created by duplicating an existing ActiveX control, the new control will have the same name as the old one. This causes the WindowMaker to stop responding.
L00100516: HF CR L00099272 (Hotfix 1724) SR 15616796: If the regional setting and language are not United States and English, the loading of the TrendClient control will have an exception error on date and time, and no trend configuration will load. Also, this can happen if there is a mismatch between the regional setting and language used to save the object configuration data and the settings used to load the configuration data at run time.

The latest TrendClient control configuration data is now stored in a culture-independent format. Therefore, the TrendClient control configuration data loads correctly, regardless of the regional settings and language selected. You will still observe an exception when the TrendClient loads until the modified TrendClient control configuration data has been saved to all object instances of the TrendClient controls. To save the configuration data, go to each instance of the TrendClient control in the application and validate the object. The validation action causes the existing configuration data to be processed and written in the new format. The next time the TrendClient control is used at run time, there will not be a problem if the regional setting and language are not the same as those that were used when the configuration data was saved.

L00101260: HF CR L00100478 (Hotfix 1777) SR 23518809: Inconsistent results are displayed while evaluating a real value.
L00101312: HF CR L00100134 (Hotfix 1789) SR 23518903: If an IDEA Toolkit application is running, InTouch 10.x WindowMaker or WindowViewer cannot be started.
L00101594: HF CR L00100948 (Hotfix 1803) SR 24410910: If a QuickFunction returns a value, then the AlarmComment of the alarmed tag that is changed in the QuickFunction is either blank or a wrong value is displayed in the Alarm Viewer.
L00101769: SR 15315447: You will not be able to configure Alarm DB Logger as a service on a computer that has Windows Server 2008.
L00102585: HF CR L00100780 (Hotfix 1790) SR 10415745: Windows and ArchestrA Symbols take a long time to display when you load them from the disk. As you load more and more InTouch windows, View stops responding.
L00103349: HF CR L00100168 (Hotfix 1771) SR 103117132: The TrendClient control query returns incorrect information when you apply Hotfix 1616 to browse old data.
L00103726: HF CR L00102677 (Hotfix 1888) SR 40210282: The following error message is displayed in WindowViewer: "Stack frame allocation error, cannot execute script function; Unknown opcode in GetSValue():65"
L00104894: HF CR L00104534 (Hotfix 1974) SRs 103117339 and 25313475: If an ArchestrA Symbol button uses script to write (poke) an I/O value when the button is pushed, the value is not sent to the PLC if it is the same as the previous value.

To resolve this issue, use .ini settings called "ForceWriteForAnalogIOTags" for integer and "ForceWriteForAnalogRealIOTags" for real values. The values should be set to 1 in the InTouch.ini file. This forces the I/O tags to be written (poked) even though the old value and new value are the same.

L00105388: HF CR L00103933 (Hotfix 1984) SR 40210405: When you cancel or close an open script inside a Project View folder in WindowMaker, some folders stay collapsed and cannot be expanded, some folders remain expanded and cannot be collapsed, and windows and scripts inside an expanded folder cannot be edited.
L00105420: After the InTouch timeout ($InactivityTimeout) expires, the current InTouch user is not logged off properly.
L00105601: SR 40210714: The ArchestrA AlarmClient Control does not expose the .FromPriority and .ToPriority properties that are available in the AlmDBViewCtrl ActiveX in InTouch.
L00105687: HF CR L00105022 (Hotfix 2014) SR 23518895: When you switch from development time to run time, the following issues are observed in run time:
  • The font style is different from that of development.
  • The graphic position of some objects is changed.
L00105852: HF CR L00104749 (Hotfix 2039) SR 103117979: If the Always load windows from disk option for WindowViewer is not selected, then the onShow script from an ArchestrA symbol does not execute properly.
L00105853: HF CR L00104993 / L00104896 (Hotfix 2008) SR 12610860: When the Alarm DB Purge-Archive utility executes the Purge function, SQL server goes up to 100% and the Alarm Comment table is not cleared when purging finishes.
L00106052: HF CR L00105482 (Hotfix 2038) SR 103118049: When you export language data for an ArchestrA Symbol that has a large number of custom properties, the following error message is displayed: Exception during WWConvertToXML: System.AccessViolationException: Attempted to read or write protected memory while exporting.
L00106220: HF CR L00105209 (Hotfix 2025) SR 38910297: WindowMaker stops responding when you open the aaSymbol dialog box to edit the custom properties for an ArchestrA Symbol on Windows XP SP3.
L00106274: HF CR L00094932 (Hotfix 2062) SR 103116169: WindowViewer flickers constantly when alarms are updated.
L00106359: HF CR L00103482 (Hotfix 1917) SR 103117094: You are unable to use ArchestrA AlarmClient Control in Historical mode due to SQL Server query timeouts.
L00106361: HF CR L00104147 (Hotfix 1953) SR 30712291: The ArchestrA AlarmClient control does not work with the default query if it is in historical mode. The following error message is displayed: "ExecuteQuery() in DCMCommand failed: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
L00106544: HF CR L00105319 (Hotfix 2065) SR 103117936: The InTouch WindowViewer program stops responding intermittently due to being out of handles.
L00106750: HF CR L00105534 (Hotfix 2072) SR 103118108: During the conversion to InTouch 10.1 from InTouch 9.5, action scripts are deleted if there is no itocx.cfg file in the InTouch application folder.
L00106773: HF CR L00106376 (Hotfix 2081) SR 40210744: The InTouch timeout ($InactivityTimeout) and warning ($InactivityWarning) periods are not reset by clicking the ArchestrA Symbol in a managed InTouch application. This causes the user to be automatically logged off, even though they are working with the application.
L00107013: HF CR L00105349 (Hotfix 2098) SR 40210555: In a standalone InTouch application, when you point the mouse at a rectangle, the halo of the rectangle appears for a short while and then disappears.
L00107148: HF CR L00106823 (Hotfix 2108) SR 41610006: WindowViewer gets locked when key scripts are executed while other applications such as a command prompt are open and running.
L00107183: HF CR L00106998 (Hotfix 2121) SR 38230992: The rendering optimization is consuming too much memory, causing the InTouch HMI to stop responding at 1.4 GB.
L00107212: HF CR L00092198 (Hotfix 2103) SR 12912063: None of the InTouch security scripts will run if the local security policy is not enabled for the user.

For the hotfix to work, you must add a registry entry. The registry entry can be used to specify the LogonType that should be used. The registry value does not exist by default.

To create the registry entry:

  1. Create the registry key.
    • For a 32-bit version of Windows, create the registry key: HKEY_LOCAL_MACHINE\Software\ArchestrA\Security
    • For a 64-bit version of Windows, create the registry key: HKEY_LOCAL_MACHINE\Software\Wow6432Node\ArchestrA\Security
  2. Create a DWORD value "LogonType".
  3. Set the LogonType to the desired value.

Examples:

for interactive logon (LOGON32_LOGON_INTERACTIVE)      2

for Batch logon (LOGON32_LOGON_BATCH)                        4

for Service logon (LOGON32_LOGON_SERVICE)                  5

L00107213: HF CR L00106977 (Hotfix 2119) SR 40210782: The Alarm DB Viewer does not correctly sort alarm records with millisecond resolution. There is a SQL server resolution limitation of 3 milliseconds, which the Alarm control does not address correctly.
L00107385: HF CR L00106966 (Hotfix 2122): While an application is printing, the memory usage and GDI object counters increase. Even after the printing is complete, these values are not reset. This results in an exception error, which causes WindowMaker to stop responding.
L00107388: HF CR L00102483 (Hotfix 1966) SRs 40210485 and 40210300: The Histdata application (histdata.exe) always starts on a full screen in Windows Server 2008 or an upgraded operating system, irrespective of how the application was closed earlier.
L00107527: HF CR L00103236 (Hotfix 2102): For the Japanese version of the InTouch 10.1 HMI, the Find function in a script editor highlights a wrong word if the script contains double-byte characters.
L00107630: HF CR L00106875 (Hotfix 2107) SR 28610994: During the Galaxy Repository (GR) operations, the InTouch runtime takes long to perform if the items to be resolved do not exist.

Manually add a filter string to the InTouch.Ini file. Any Galaxy item names whose initial characters match this filter string, independent of the character's case, will not be submitted to the I/O subsystem for registration and advisement.

L00107646, L00109694: HF CR L00107538 (Hotfix 2154) SR 41610043: You can open a second keypad in the InTouch HMI while one is already open. If you cancel or close both the keypads, the InTouch HMI stops responding.
L00107840: SR 41610014, 41610029: The coordinate positions of texts and wizards are not printed correctly.
L00107844: SR 41610016, 41610031: Text without an animation link and information on other objects are not printed correctly if they are grouped together as a symbol.
L00107848: SR 41610018, 41610033: Line and fill color of figures like rectangles, ovals, and polygons are not printed while the contents of an animation link are properly printed.
L00107850: SR 41610022, 41610037: The wizard name is not printed.
L00107851: SR 41610023, 41610038: In a wizard, the font name is printed, but the style and size of the font are not printed.
L00108062: HF CR L00107558 (Hotfix 2157) SR 33410738: The InTouch user interface does not refresh completely. The current screen displays remnants of previous objects.
L00108269: HF CR L00106362 (Hotfix 2076) SR 12610851: The functionality of DBLoad in InTouch 10.1 SP2 takes more time than 10.0 SP2.
L00108321: HF CR L00108002 (Hotfix 2187) SR 33112021: If the SQLConnect() function fails, the error message in the logger is incorrect.
L00108405: HF CR L00108333 (Hotfix 2201) SR 33410751: When you use DBLoad for the first time after installing Hotfix 2076, the following error message is displayed: "Fail to load."
L00108426: HF CR L00107998 (Hotfix 2193) SR 34132311: When the application is published, the default language of an ArchestrA Symbol changes to US English and the default text is translated to the same.
L00108542: HF CR L00108192 (Hotfix 2191) SR 103119374: With Hotfix 1931 (CR L00103416) installed, the ArchestrA AlarmClient Control sometimes fails to display alarms.
L00108549: HF CR L00096824 (Hotfix 2031): The alarm printer utility does not print alarms in different colors. You are unable to specify the colors for Alarm Type, Alarm State, Group Name and Priority.
L00108552: HF CR L00108488 (Hotfix 2210) SR 33410755: After installing Hotfix 2201, DBLoad does not function correctly from the command line if the application is empty. The following error message is displayed at this time: "Load failed. See Log Viewer for problems."
L00108578: "While showing" scripts in an ArchestrA Symbol keep on writing the same values to custom properties, causing high CPU usage of InTouch WindowViewer.
L00108687: SR 10416004: Select the /LARGEADDRESSAWARE flag on InTouch executable files so that you can access up to 3 GB of virtual memory on 32-bit systems and up to 4 GB of virtual memory on 64-bit systems.
L00108688: SR 10416004: For optimal large memory address space utilization, set the WWHeap memory range to the maximum allowed default value.
L00109053: HF CR L00108624 (Hotfix 2218) SR 103119429: When you upgrade from InTouch 7.0 to 10.1 SP2 Patch 01, the Save Script feature functions very slowly.
L00109410: HF CR L00109201 (Hotfix 2268) SR 41610066: When you select the Line or Shape tool, and then double-click the window, the WindowMaker software stops responding.
L00109545: HF CR L00109132 (Hotfix 2265) SR 103119330: When InTouch WindowMaker converts a legacy application to InTouch 10.1 SP2, it changes the font of the button names to Tahoma.
L00109981: SR 24515011: When you upgrade from InTouch 10.1 Patch 01, the following error message is displayed: "Failed to load Window Index 1. Stage=8 Linked=1."

However, this error message is not displayed in view.exe of InTouch 10.1 SP2 Patch 01.

L00110128: HF CR L00109699 (Hotfix 2327) SR 19816820: The following error message appears in the SMC when the window closes and reopens: "! PostMessage Failed in the case of ABCB_WNAPCB_REMOVED - Error from AlmCallbackList::CallCallback of almblist.cpp file."
L00110157: HF CR L00109879 (Hotfix 2330) SR 10415853: WindowViewer stops responding with an assertion error in line 945 of vumisc.cpp.
L00110272: HF CR L00110124 (Hotfix 2341) SR 17133229: InTouch WindowMaker stops responding when you try to import the Chinese dictionary from the disk. The EventViewer displays the following error message: ".NET runtime 2.0 Error Reporting; Event-ID: 1000."
L00110275: HF CR L00109144 (Hotfix 2267) SR 103119480: For an ArchestrA Symbol opened in a ShowSymbol dialog box, you will not be able to execute a Mouse Up action script for a Push Button, if the pointer is not directly over the graphic element at that time.
L00110411: SR 33932486: When the value or limit string contains more than 131 characters, the Alarm DB Logger fails to log alarms properly.
L00110500: HF CR L00110203 (Hotfix 2350) SR 103120395: Value deadband does not work for .HiHi and .LoLo alarms, but works for .Hi and .Lo alarms.
L00110763: HF CR L00110119 (Hotfix 2339) SR 41610072: In InTouch 10.1 SP3, Japanese characters are not printed correctly in the HTML output.
L00110948: HF CR L00110534 (Hotfix 2367) SR 33932492: Alarms are not restored because of the quotation marks present in the alarm short descriptions.
L00111008: HF CR L00109958 (Hotfix 2332) SR 34211148: InTouch stops responding for 30 seconds or more when the ArchestrA AlarmClient Control makes a query for alarms. However, this does not affect the AlarmViewControl ActiveX when it queries for alarms.

< top of document >


Known Issues - Wonderware InTouch 10.1 SP3 Patch 01

The following are known issues specific to InTouch 10.1 SP3 Patch 01. Known issues from InTouch 10.1 SP3 are still valid, unless listed as resolved in this patch.

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.

L00112188: Installing the 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.

< top of document >    


Wonderware® InTouch® HMI Version 10.1 Service Pack 3 Readme

Last revision: 11/4/2010

About This Readme

This document adds information about Wonderware® InTouch HMI 10.1 SP3 (Service Pack 3) to the previous ReadMe files included with Wonderware InTouch HMI 10.1, Wonderware InTouch HMI 10.1 SP2, Wonderware InTouch HMI 10.1 SP2 Patch 01.

About This Release

Version 10.1 SP3 of Wonderware® InTouch HMI includes support for new operating systems, an XML graphics importer, and resolved issues.

Wonderware InTouch HMI version 10.1 SP3 Information

Important!


  1. If you are using managed InTouch applications with ArchestrA® symbols from Application Server 3.0, before installing Wonderware Application Server 3.1 SP3, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
  2. If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 SP3 and InTouch 10.1 SP3.
  3. Disable UAC before installing the Wonderware Application Server 3.1 SP3 and InTouch 10.1 SP3, applicable for Windows Vista and above operating systems.
  4. If your version of Wonderware Application Server is 3.1 SP2 or earlier, then upgrade it to Application Server 3.1 SP3, before upgrading to InTouch 10.1 SP2 to 10.1 SP3.
  5. Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality must always be modified on the same language operating system and InTouch language version, on which it was initially developed. Attempts to modify these components in a different language operating system, or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system language different from the originally developed language are supported. Refer to Known Issues CRs L00088974, L00088993, and L00088998.
  6. Review the Antivirus Software Exclusions list.
  7. Windows Server 2008 R2 no longer supports the /console switch as a means of setting the Remote Desktop Client (RDC), also known as a console session. Click this Terminal Services Behavior link for further information about terminal services behavior changes.
  8. If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:\InTouch!$System to access the alarms, with a colon (:) after the node name. Click this Terminal Services Behavior link for further information about terminal services behavior.
  9. Launching the ArchestrA Licensing Utility from an existing License CD may not work on a 64-bit operating system. Launch the utility from the installed shortcut instead.
  10. If you notice an issue with command line printing, the command may have been copied from another application. To correct, please type quotes (“) instead of using copy and paste.
  11. All the restrictions applicable to Windows Vista and Windows Server 2008 are also applicable to Windows 7 and Windows Server 2008 R2, respectively.
  12. The InTouch HMI and Alarm DB Logger cannot be configured to run as services in Windows Vista or later operating systems. This includes Windows Server 2008, Windows Server 2008 R2, and Windows 7 operating systems. In these operating systems, services are no longer allowed to interact with the desktop. Services now run in Session 0, and interactive processes (such as the InTouch HMI and Alarm DB Logger) run in a Session ID greater than 0. You can no longer configure the InTouch HMI and Alarm DB Logger to run as services as a way to automatically start them. For instructions on an alternate technique for automatically starting these processes, see Tech Note 725, available from the Wonderware website.

< top of document >


Support for New Operating Systems

Wonderware InTouch 10.1 SP3 supports the following new releases of Microsoft operating systems:

< top of document >


XML Graphics Importer

Using the XML graphics feature, you can import window definitions into InTouch applications using XML formatted files. It uses a pre-configured XML file, a command file, and automatically creates windows containing objects, graphics, and SmartSymbols in both stand-alone an managed InTouch applications.

See the "XMLImportUserGuide.pdf" for more information.

< top of document >


System Requirements

This section describes the hardware and software requirements to install Wonderware® InTouch HMI Version 10.1 SP3.

Hardware Requirements

The following lists show the recommended specifications to install Wonderware® InTouch HMI Version 10.1 SP3. These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors.

Standalone InTouch Node

Non-GR Platform With or Without an InTouch Application

  • Computer with 2 GHz or faster processor (32/64 bit). Multi-core processor is strongly recommended. Intel Itanium 2 processor is not supported.
  • 1 GB of memory minimum, 4 GB or greater recommended
  • At least 30 GB of available disk space for 32-bit OS, 40 GB for 64-bit OS
  • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
  • Network interface card
  • CD-ROM or DVD drive for installation
  • Keyboard
  • Mouse or compatible pointing device

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 7 Professional 64-bit
Windows 7 Professional 32-bit
Windows Server 2008 R2 Standard
Windows 2008 Standard 32-bit
(See Vista Restrictions)
Windows 2008 Standard 64-bit
(See Vista Restrictions)
Windows Vista SP2 Business, Enterprise, or Ultimate
(See Vista Restrictions)
Windows Vista SP1 Business, Enterprise, or Ultimate
(See Vista Restrictions)
Windows Vista Business, Enterprise, or Ultimate
(See Vista Restrictions)
Windows 2003 Standard Server R2
Windows 2003 Standard Server SP2
Windows 2003 Enterprise Server R2
Windows 2003 Enterprise Server SP2
Windows XP Professional SP3  
Windows XP Tablet     

Note:

  • Wonderware InTouch HMI version 10.1 SP3 does not support any version of the Microsoft Windows 2000 operating system. If you attempt to install or upgrade the InTouch HMI on a computer running Microsoft Windows 2000, an error dialog box appears during the installation procedure.
  • Microsoft Windows 7 (32-bit or 64-bit) is the recommended operating system to run InTouch client components. 
  • Microsoft Windows 2008 R2 is the recommended operating system to run InTouch server components.

< top of document >


Using Wonderware InTouch with Windows 7 and Windows Server 2008 R2

  • Consuming alarms within an RDP session: On the Windows 7 and Windows Server 2008 R2 operating systems, there is a change in the behavior of interactive applications such as InTouch that can result in a difference in how remote alarm retrieval queries must be configured. The scenario manifests itself if InTouch WindowViewer is starting and is generating alarms from an interactive Windows 7, Windows 2008 R2 or Windows Vista desktop session. In this case, if an AlarmViewer control (running within InTouch) on a remote node is configured to query the alarms from the source InTouch, the source alarms will not appear unless the AlarmViewer's alarm query is configured using the steps outlined here.
    1. After launching InTouch WindowViewer (alarm provider) on the Windows 7, Windows Server 2008 R2 or Vista node, open the SMC Logger and look for the most recent string generated by AlarmMgr such as "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 and use it in the next step.
    2. In the Alarm Query tab of the AlarmViewer control on the remote machine, configure the alarm query as follows, substituting your actual nodename of the alarm providing InTouch for "nodeabc" below and substituting your IP address noted in the previous step: \\nodeabc:253.127.148.120\intouch!$system
    3. Test and verify that the alarms sourced from the alarm provider are properly displayed in the AlarmViewer control of InTouch.
  • The InTouch HMI and Alarm DB Logger cannot be configured to run as services in Windows Vista or later operating systems. This includes Windows Server 2008, Windows Server 2008 R2, and Windows 7 operating systems. In these operating systems, services are no longer allowed to interact with the desktop. Services now run in Session 0, and interactive processes (such as the InTouch HMI and Alarm DB Logger) run in a Session ID greater than 0. You can no longer configure the InTouch HMI and Alarm DB Logger to run as services as a way to automatically start them. For instructions on an alternate technique for automatically starting these processes, see Tech Note 725, available from the Wonderware website.
  • Wonderware InTouch 10.1 SP3 does not support the following functions: 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 Vista or later operating systems.
  • The InTouch Extensibility Toolkit may need to be started by right-clicking and selecting "Run As Administrator" on Windows Vista or later operating systems to function properly.
  • The onscreen keyboard options have changed for the Windows 7 and Windows Server 2008 R2 operating systems.
  • Hovering to select from the Windows keyboard does not work in the Windows 7 Professional and Windows Server 2008 R2 Standard operating systems.

< top of document >


Installing Microsoft .NET Framework on Wonderware InTouch 10.1 SP3

Microsoft .NET Framework 3.5 SP1 must be installed prior to installation of SQL Server 2008 SP1 or Wonderware Application Server 3.1 SP3 using Microsoft role management tool on Windows 2008 R2 and Windows 7, 32/64-bit operating systems.

Installing InTouch 10.1 SP3 on a Windows 2008 R2 or Windows 7 64-bit System

Starting with Windows 2008 R2, the method of installing .NET Framework 3.5 SP1 has changed. This change affects the installation of InTouch 10.1 SP3 on Windows 2008 R2 and Windows 7 64-bit operating systems.

If .NET Framework 3.5 SP1 is not already installed on your system prior to installing InTouch 10.1 SP3, you must install it manually.

If you have already started the InTouch 10.1 SP3 installation, you will need to exit, manually install .NET 3.5 SP1, then return to the InTouch 10.1 SP3 installation.

For Windows 2008 R2 Operating Systems: To install the .NET Framework 3.5 SP1, you can use the Microsoft Server Manager Interface or the Microsoft Power Shell.

To use the Server Manager

  1. Click Start, then highlight Administrative Tools and select Server Manager.
  2. In the Server Manager, select Add Features, then expand .NET Framework 3.5.1 Features.
  3. In .NET Framework 3.5.1 Features, click the check box for .NET Framework 3.5.1. Click Next.
  4. Click Install to confirm the installation selection. The .NET Framework 3.5.1 installation will proceed.

To use the Windows Power Shell

  1. Click Start, highlight All Programs and select Accessories.
  2. Expand Windows PowerShell and right click Windows PowerShell and select Run as administrator. Click Yes on the User Account Control box.
  3. At the Power Shell Command Prompt, enter the following two commands and press Enter after each command:
    1. Import-Module ServerManager
    2. Add-WindowsFeature as-net-framework
  4. Exit Windows Power Shell.

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

  1. Start Control Panel, then select Programs, then select Programs and Features.
  2. Click Turn Windows Features On or Off.
  3. Select the Microsoft .Net Framework 3.5.1 check box, then click OK.
  4. Restart your computer.

< top of document >


Upgrading from a Previous Version of Wonderware InTouch

After the hardware and software requirements are met, you can upgrade to InTouch version 10.1 SP3 from the following versions of InTouch:

  • Version 10.1
  • Version 10.0 SP2
  • Version 9.5 SP1
  • Version 9.0 P03
  • Version 8.0 SP2 P04

Migrating Applications to InTouch Version 10.1 SP3

An InTouch application, with the most recent patches applied, can be migrated from the following versions to InTouch 10.1 SP3:

  • Version 7.0 (For InTouch applications migrated from versions prior to version 7.0, first convert them to version 7.0 and then convert them to 10.1 SP3)
  • Version 7.1
  • Version 7.11
  • Version 8.0
  • Version 9.0
  • Version 9.5
  • Version 10.0
  • Version 10.1

< top of document >


Product Compatibility

Wonderware InTouch HMI Version 10.1 SP3 is compatible and can co-exist with the following products:

  • Wonderware Application Server 3.1 SP3
  • Historian Client 10.0 SP1
  • InTouch CE 10.1
  • Wonderware Historian Server 10.0 SP1
  • Manufacturing Execution Systems 4.0
  • Wonderware Information Server 4.0
  • InControl 7.11 SP2 P01
  • Manufacturing Execution Module 1.0
  • InBatch 9.0
  • QI Analyst 8.0 SP2 P01
  • SCADAlarm 6.0 SP2 P01

< top of document >


Resolved Issues - Wonderware InTouch 10.1 SP3

L00097880: HF CR L00103744 (Hotfix 1935) SR 12610874: Logging a STRING PV change/event causes an alarm db logger loop if the string value exceeds 131 chars.
L00099115: AlarmViewer on Windows 2003 fails to fetch the Alarms provided by InTouch application on Windows 7 (64-bit).
L00099731: InTouch 10.1 SP2 OSconfiguration utility is not compatible on Windows 7 & Windows 2008 R2.
L00101371: HF CR L00100155 (Hotfix 1773) SR 25333441: WindowMaker and WindowViewer stop responsing if the Edit Script window is left open.
L00101644: HF CR L00100619 (Hotfix 1787) SR 33811216: The resizable keyboard causes WindowViewer to stop responding.
L00101689: HF CR L00100957 (Hotfix 1762): Embedded alarms leaks memory when configured to retrieve historical alarms (for EAC and AFcommon).
L00101691: HF CR L00100763 (Hotfix 1788) SR 12610815: ERROR: 'ArchestrA.Visualization.GraphicLibrary.aaDataSubscriptionManager' failed for the following reason1: 'System.NullReferenceException: Object reference not set to an instance of an object. at ArchestrA.Visualization.GraphicLibrary.aaDataSubscriptionManager.ProcessData(Object sender, EventArgs eventArgs)'
L00101823: When the windows on-screen keyboard is invoked on Windows 7 (64 bit) operating system using InTouch, the following error message is displayed: "Could not start On-Screen Keyboard".
L00101824: When using the on-screen keyboard on Windows 2008 R2, the String Input link does not accept alphabetical characters and the error message "Could Not Create Input Dialog Box" is displayed.
L00102159: HF CR L00099148 (Hotfix 1772) SR 103116948: The ArchestrA graphic "On Mouse Leave" script fails to run on all machines.
L00102160: HF CR L00100123 (Hotfix 1758) SR 15315374: When you export the dictionary for run-time language switching, all text strings are not exported.
L00102408: HF CR L00101770 (Hotfix 1859): APUStartQuery() function fails to set the date and time limits for records to be processed from the alarm memory.
L00102830: HF CR L00101792 (Hotfix 1851) SR 40210166: Memory leak occurs in hd.exe when trending data from the InSQL provider.
L00103873: Embedded Alarm Control (EAC) still has memory leaks (private bytes) after applying Hotfix 1688 and Hotfix 1703.
L00104011: HF CR L00102943 (Hotfix 1887): The Historical Trend does not display data after an upgrade, causing errors in WWHCI and WWIHIST.
L00104137: HF CR L00103553 (Hotfix 1905): Alarm DB Logger truncates a description from AppServer to 131 characters and causes alarm logging to fail.
L00104300: HF CR L00103911 (Hotfix 1939): WindowViewer stops responding when transferring focus from one DateTime picker to another.
L00104422: HF CR L00103744 (Hotfix 1935): Alarm DB Logger truncates a UDA string value in AppServer and causes the alarm logging to fail.
L00104996: HF CR L00104266 (Hotfix 1934) SR 32010096: WindowViwer stops responding while calling a simple quick function as a result of a bug in rtexpr.lib.
L00105181: Alarm DB Logger truncates a description from AppServer to 131 characters.
L00105213: HF CR L00095406 (Hotfix 1338): WindowViewer stops responding when trying to close it.
L00105218: HF CR L00097080 (Hotfix 1631) SR 33811071: The View.exe process' memory grows when switching windows containing ArchestrA Graphics despite unchecking the "Always load from disk" option.
L00105221: HF CR L0097508 (Hotfix 1712): The value of the .Quality field becomes zero after a window with a "Replace" type is closed and re-opened.
L00105230: The application version does not change to a higher version for managed IT application after migration.
L00105525: HistTrend display does not display data in Windows 7 and Windows Server 2008 R2 operating systems.
L00105600: HF CR L00104841 (Hotfix 1996) SR 28610994: InTouch runtime performance is affected if the galaxy repository is present on the network and the galaxy repostory is busy with an intensive operation. This can cause a safety issue.
L00106525: InTouch Viewer crashes when window is made hide after keypad is launched.
L00106744: HF CR L00106366 (Hotfix 2078) SR 103117464, SR 31711401 and SR 38910267: An ArchestrA corruption occurs when editing in WindowMaker and then updating an object script from the IDE.
L00107181: HF CR L00107120 (Hotfix 2129) SR 15617162: WindowViewer consumes CPU and gets very slow.

< top of document >


Known Issues - Wonderware InTouch 10.1 SP3

L00103534: WindowViewer cannot run as a service for Windows 7 and Windows Server 2008 R2.
L00103813: The following functions are not supported on Windows 7 and Windows Server 2008 R2 platforms: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
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 UAC 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.
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 (4.0.1.1233)
  • VMware Tools = Old Version (add/remove programs) = 3.1.2.7193
  • VMware Tools = Old Version (Help/about) = 3.5.0, B123630
  • Video driver version = Old Version (Display properties) VMWare SVGA2 version 11.04.03.0002 (11.4.3.2) 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) 8.0.2.14744
  • VMware Tools = Upgraded Version (Help/about) = 4.0.0 B208167
  • Video driver version = New Version (Display properties) VMware SVGA 3D (Microsoft Corporation - WDDM) Version (7.14.1.31) 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.

< top of document >    


Wonderware® InTouch® HMI Version 10.1 Service Pack 2 Patch 01 Readme

Last revision: 4/21/2010

About This Readme

This Readme contains important information about Wonderware® InTouch HMI version 10.1 SP2 and Patch 01. This Readme explains how to apply Patch 01 to InTouch version 10.1 SP2. This Readme lists all resolved issues in InTouch version 10.1 SP2 and Patch 01. It also includes any known issues that remain unresolved from version 10.1 SP2 and Patch 01.

This Readme also includes the original Readme distributed with InTouch HMI version 10.1 SP2. Use the following links to jump to the various sections of this Readme.


Important!

  1. If InTouch 10.1x and Application Server 3.1x are installed on the same node, they both must be upgraded to Application Server 3.1 SP2 and InTouch 10.1 SP2, or Application Server 3.1 SP2 Patch 01 and InTouch 10.1 SP2 Patch 01.
  2. If your version of Wonderware Application Server is older than version 3.0, you must upgrade it to Application Server 3.1 SP2 before upgrading to InTouch 10.1 SP2. Patches may be applied subsequently after.

Clarifications From Previous InTouch 10.1 Readme Notes

DDE Support

Windows 2008 does 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 (UAC)

InTouch versions 10.1, 10.1 SP2, and 10.1 SP2 Patch 01 support UAC-enabled run-time operations without elevated privileges. For all configuration and installation operations, including those called during run-time operations, UAC must be disabled or privileges must be elevated to the required level.


< top of document >


Applying Patch 01 to InTouch 10.1 SP2

This section explains how to apply Patch 01 to existing instances of InTouch 10.1 SP2 installed at your site.

Important: InTouch Patch 01 must be applied only to InTouch version 10.1 SP2. No other version of InTouch can be upgraded with this patch.

The 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 Patch 01 CD:

  • For standard InTouch, the CD volume name must be Patch.
  • The Setup.msp file must be placed at the root of the CD.

Apply the Patch

  1. Close Application Manager, WindowMaker, or WindowViewer 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.
  6. Accept the license.
  7. Click Next. The Updating System dialog box shows the progress of the patch update.
  8. If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
  9. Click Finish.
  10. Click Yes to restart your computer.

Verify InTouch Has Been Updated

  1. Start Application Manager.
  2. Click Help from the Application Manager menu bar.
  3. Select About Application Manager. The About InTouch Application Manager dialog box shows the InTouch version installed on the computer.
    You should see Version: 10.1.201 listed in the dialog box after Patch 01 is installed.

< top of document >


Product Compatibility

In some cases, Wonderware InTouch HMI Version 10.1 SP2 Patch 01 is supported in newer environments than a compatible product. Wonderware InTouch HMI Version 10.1 SP2 Patch 01 has been tested for compatibility with a listed product only in the environments that are supported by that particular product. Wonderware InTouch HMI Version 10.1 SP2 Patch 01 is compatible and can co-exist with the following products:

  • Wonderware Application Server 3.1 SP2 Patch 01
  • ActiveFactory 9.2
  • InTouch CE 10.1
  • Wonderware Historian Server 10.0
  • Performance Software 3.5
  • Wonderware Information Server 3.1
  • InControl 7.11 SP2 P01
  • Manufacturing Execution Module 1.0
  • InBatch 9.0
  • QI Analyst 8.0 SP1 P01
  • SCADAlarm 6.0 SP2 P01

Resolved Issues - InTouch version 10.1 SP2 Patch 01

InTouch version 10.1 SP2 Patch 01 resolves the following issues listed by their Change Request number:

L00076382: HF CR L00074712(HF 846) SR 23515677: A handle leak occurs within InTouch when making a repeated DDE connection to Historical Data Manager from a Microsoft Excel workbook.
L00092079: HF CR L00082168 (HF 1061) SR 15314499: The Anonymous Engine ID is not recycled when WindowMaker running on the Terminal Server Console and Session is shutdown from View.
L00095236: HF CR L00094283 (HF 1510) SR 33810982: Action Script with key equivalent "return" does not work if it is called from Show Symbol; however it works when using the key equivalent "F1".
L00095978: HF CR L00094509 (HF 1519) SR 38610018: WWHEAP runs out of free shared maps for memory allocation. InTouch crashes when the application has multiple windows (more than 170) and needs to load all of them into memory. Request to remove the heap limit.
L00096057: HF CR L00094785 (HF 1556) SR 23518177: The Application Expander fails after language import
L00096298: HF CR L00095309 (HF 1562) SR 23518143: Printwindow() does not print the Trend Ctrl. Otherwise, when it does print other graphics successfully, it only prints one page (not the full window if it is more than one page).
L00096451: HF CR L00096402 (HF 1601) SR 23518393: "Msg to User" text (from the input keypad) shifts position aligned to the right after a language switch (e.g. Romanian).
L00097004: HF CR L00096059 (HF 1588) SR 10415583: After the installation of Hotfix 1510 (return key fix), the edit text box in ArchestrA Graphics does not work. Key action does not work if aaGraphic includes an edit box.
L00097133: HF CR L00094088 (HF 1599) SR33931644: Failure to convert custom property <Window> string value of "NaN.0" to Float.
L00097412: HF CR L00096530 (HF 1616) SR33931715: TrendClient pen disappears if the data does not change during the trend period.
L00097823: HF CR L00096858 (HF 1639) SR 15315189: Show Symbol does not show the ArchestrA Symbol in its correct size. The width is stretched.
L00097825: HF CR L00097408 (HF 1644) SR30712027: LMX exception occurs when more than one thread is accessing LMX via wwClintf at the same time.
L00098089: HF CR L00096574 (HF 1617) SR103116065: View crashes on change to $Language if an ArchestrA Graphic with ComboBox is displayed
L00098093: HF CR L00095601 (HF 1662) SR20610939: Slow behavior occurs on showing graphics when switching screens and LMX errors occur in the SMC logger when deploying the AppEngine.
L00098632: HF CR L00097431 (HF 1640) SR15616742: WindowViewer leaks managed private bytes (leading to a crash) when switching windows with ArchestrA Graphics using the OwningObject property.
L00098724: HF CR L00098586 (HF 1688) SR15616746: Embedded Alarm Control (EAC) leaks memory (private bytes), leading to a crash
L00098870: HF CR L00098623 (HF 1690) SR33430420: In a Text Box linked to a UDA, the value passed with IoSetRemoteReference rewrites the original value.
L00099062: HF CR L00095531 (HF 1675) SR37610557, SR37830639: Error when converting AlarmRecord[] to an alarm list. Value was either too large or too small. Alarm in unack state for 1 month, after ack shows an inconsistent state and errormessage.
L00099185: HF CR L00098394 (HF 1679) SR103116849: Using a Show Symbol animation, the popup contains user input value. Clicking the user input closes the popup, removes the prompt for the value, and the user input animation ceases to work.
L00099217: HF CR L00097401 (HF 1683) SR33931780: Certain elements disappear after switching the language.
L00099228: HF CR L00099076 (HF 1701) SR 15616746: A memory leak occurs in ArchestrA graphics when an outbound write to an ArchestrA or InTouch data point does not return a write result.
L00099330: HF CR L00098157 (HF 1668) SR 23518508: Indirect tags will not set completely in a datachange script if the .referencecomplete and .quality are set to zero.
L00099572: HF CR L00099189 (HF 1703) SR 10415503: Embedded Alarm Client object leaks. View memory grows up to 25 MB/hour.
L00099574: HF CR L00094601(HF 1378, 1497, 1527) SR 23517638, SR 33810854, SR 103115626: Memory leak issues. View private bytes goes up when a window is repeatedly opened and closed. WindowViewer crashes when the application reaches the physical and virtual memory limit. ArchestrA graphics leak memory when they communicate with the MXValue class.
L00099755: HF CR L00098403 (HF 1677) SR 15616742: View leaks managed private bytes when switching windows with ArchestrA Graphics which are using the OwningObject property in Symbol OnShow scripts.
L00101197: HF CR L00101197 (HF 1822) SR 40210138: IOSetRemoteReference function fails in InTouch 10.1 SP2 if the target pop-up window has a dynamic value that is bound to a reference that is already active in another window currently displayed.
L00103882: HF CR L00102729 ( HF 1878 ) SR 12610801, L00103838 (HF-1937) SR 103117770: New ArchestrA.Visualization.GraphicLibrary.dll causes empty embedded symbol after reopening the ArchestrA Graphic Symbol the second time.

 

< top of document >


Known Issues in Wonderware® InTouch HMI Version 10.1 SP2 Patch 01

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

L00102808: InTouch View application cannot run if an ArchestrA graphic name contains localized characters and if is deployed on an English operating system.
L00103242: An InTouch application compiled using version 10.1 SP2 with HF 1821 results in the following error in the logger when WindowViewer opens the window for the first time:
"Warning view Loading Window 1 WinChunkRead Failed.
  Error view Failed to load Window Index 1. Stage=8 Linked=1"

Print Issue

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

< top of document >



 

Wonderware® InTouch® HMI Version 10.1 Service Pack 2 Readme

Last revision: 12/20/2009

About This Readme

This Readme combines information from Wonderware® InTouch HMI Version 10.1 Service Pack 2 (SP2) with the previous Readme file included with Wonderware® InTouch HMI Version 10.1:
  • InTouch version 10.1.200 (SP2)
  • InTouch version 10.1 (No Patch) 
The information from these Readme files is in order based on when the InTouch versions were released. 

About This Release

Version 10.1 SP2 of Wonderware® InTouch HMI includes the following enhancements and new features:


Important!

  1. If you are using managed InTouch applications with ArchestrA® symbols from Application Server 3.0, before installing Wonderware Application Server 3.1, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
  2. If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 and InTouch 10.1, or Application Server 3.1 SP2 and InTouch 10.1 SP2.
  3. If your version of Wonderware Application Server is older than version 3.0, you must upgrade it to Application Server 3.1 or Application Server 3.1 SP2 before upgrading to InTouch 10.1 or InTouch 10.1 SP2, respectively. 
  4. Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality, must always be modified on the same language operating system and InTouch language version on which it was initially developed. Attempts to modify these components in a different language operating system, or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system language different from the originally developed language are supported. Refer to Known Issues CRs L00088974, L00088993, and L00088998.
  5. Review the  Antivirus Software Exclusions list.
  6. Review the Known Issues - OnShow Symbol Script Issue section.
  7. Windows 2008 Considerations – Windows 2008 does not support the /console switch. As such, applications such as InTouch that may depend to run in the console session may not behave as expected if launched from a remote session. This may also impact alarm provider and query behavior. Click this Windows 2008 Restrictions link for further information about Windows Server 2008 and terminal services behavior changes.
  8. Launching the ArchestrA Licensing Utility from an existing License CD may not work on a 64-bit operating system. Launch the utility from the installed shortcut instead.

Alarm Comment Language Switching

You can format and export alarm comments from attributes in a Galaxy to external files for language translation. Exporting alarm comments to external files produces InTouch-compatible localized files to support alarm comment language switching in the InTouch the run-time environment.

The following alarm comment language switching capabilities are supported:
  • Localized languages of InTouch alarm control comments
  • Configurable list of languages for localization
  • Formatting of alarm fields/unique IDs for language switching
  • Exporting of alarm fields to individual locale files for translation 
  • Formatting of exported language files for editing and translation

    < top of document >


    Operating Systems Support 

    Wonderware InTouch HMI 10.1 SP2 has added support for the following Microsoft Windows operating systems:
  • Windows Vista Service Pack 2 Business, Enterprise, and Ultimate editions (32-bit and 64-bit operating systems)
  • Windows 2008 Service Pack 2 Business and Enterprise editions  (32-bit and 64-bit operating systems)

    < top of document >


    SQL Server Support

    Wonderware® InTouch HMI 10.1 SP2 has added support for the following databases:
  • Microsoft SQL Server 2005 SP3 (32-bit)
  • Microsoft SQL Server 2008 SP1 (32-bit)

    < top of document >


    .NET Support

    Support for Microsoft .Net Framework 3.5 SP1 has been added (required for SQL Server 2008).

    < top of document >




    Antivirus Software Exclusions

    After installing the Wonderware® InTouch HMI, configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders:

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

      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: NOTE: Ensure 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\...

      < top of document >


      System Requirements

      This section describes the hardware and software requirements to install Wonderware® InTouch HMI Version 10.1 SP2.


      Hardware Requirements

      The following lists show the recommended specifications to install Wonderware® InTouch HMI Version 10.1 SP2. These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors.

      Standalone InTouch Node

      Non-GR Platform With or Without an InTouch Application

      • Computer with 2 GHz or faster processor (32/64 bit). Multi-core processor is strongly recommended. Intel Itanium 2 processor is not supported.
      • 1 GB of memory minimum, 4 GB or greater recommended
      • At least 30 GB of available disk space for 32-bit OS, 40 GB for 64-bit OS
      • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
      • Network interface card
      • CD-ROM or DVD drive for installation
      • Keyboard
      • Mouse or compatible pointing device

      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 2008 Standard 32/64 bit
      (See Vista Restrictions)
      Windows Vista SP2 Business, Enterprise, or Ultimate
      (See Vista Restrictions)
      Windows Vista SP1 Business, Enterprise, or Ultimate
      (See Vista Restrictions)
      Windows Vista Business, Enterprise, or Ultimate
      (See Vista Restrictions)
      Windows 2003 Standard Server R2
      Windows 2003 Standard Server SP2
      Windows 2003 Enterprise Server R2
      Windows 2003 Enterprise Server SP2
      Windows XP Professional SP3  
      Windows XP Tablet     

      Note:

      • InTouch HMI version 10.1 SP2 does not support any version of the Microsoft Windows 2000 operating system. If you attempt to install or upgrade the InTouch HMI on a computer running Microsoft Windows 2000, an error dialog box appears during the installation procedure.
      • Microsoft Vista (32-bit or 64-bit) is the recommended operating system to run InTouch client components. 
      • Microsoft Windows 2008 (64-bit) is the recommended operating system to run InTouch server components.

      Windows Vista Restrictions

      • InTouch HMI version 10 or later can run under 32-bit or 64-bit operating system versions of Windows Vista Enterprise, Windows Vista Business, or Windows Vista Ultimate. The Windows Vista Home Basic and Home Premium editions are not supported. 
      • Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system. 
      • If a computer runs Windows Vista as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously. 
      • Windows Vista does 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. Windows Server 2003 and Windows XP Professional still support NetDDE.  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.  
      • InTouch HMI cannot be configured to run as a Windows Vista service. Windows Vista security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
      • Terminal server functionality is not available on Windows Vista.

      Using Multiple Network Interface Cards with Windows Vista

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

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

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

      • The Domain profile is active only when the computer can authenticate with a domain controller on all active interfaces such as LAN, wireless, and VPN. The domain profile may be more or less restrictive than the other two profiles depending on network security policies.  
      • The Private profile is active whenever the network type for all active network connections on the computer are identified as private networks. The private profile typically is used in a more trusted environment and is less restrictive than the public profile to allow for network discovery.
      • The Public profile is active in all other circumstances. The public profile typically is more restrictive than the private profile because the computer often is connected to the Internet in an insecure location. Network discovery and remote access are disabled rather than explicitly blocking specific traffic. Firewall exceptions and rules can be created on any or all of these profiles.

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

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

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

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

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

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

      • If you have only one NIC, no action is required. The profiles and firewall rules are automatic.
      • To configure two NICs, do the following:
      1. If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.
      2. If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup provided in the Wonderware Application Server User's Guide and the accompanying online help.
      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.

        Windows 2008 Restrictions

        1. If a computer runs Windows 2008 as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously. 
        2. Windows 2008 does 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.
        3. InTouch HMI cannot be configured to run as a Windows 2008 service. Windows 2008 security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
        4. Windows 2008 configured as a terminal server has limitations that may impact applications running in that environment. The terminal session /console switch has been deprecated. Users connecting remotely to the terminal server can no longer connect remotely as the console. Any remote connection to the server, even as an /admin, is treated as a remote connection. InTouch applications traditionally running as a console application may be affected by this change. Users connected remotely to the terminal server will not be able to launch /console applications. You must login at the physical machine to be considered a console session and for the application to run within the console.

        Terminal Services Behavior

        Modify terminal services behavior in Windows 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 and enter gpedit.msc. Click OK. The Group Policy dialog box appears.
        2. Go to the following location: Local Computer Policy -> Administrative Templates -> System -> Logon.
        3. 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.
        4. 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 users settings through the registry.

        To disable the ability to switch users through the Registry Editor

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

          Terminal Server Restrictions for Windows 2008

          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 with Windows Server 2008

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

          Other Software Requirements

          The following list describes other third-party software required for InTouch HMI version 10.1 SP2.
          • Microsoft .NET Framework 3.5 must be installed on every computer that hosts an InTouch version 10.1 component. The InTouch installation program stops if .NET Framework 3.5 is not installed on the target computer. A dialog box appears, requesting the installation of .NET Framework 3.5. If you click Install Prerequisites , the installation program automatically installs .NET Framework 3.5. 
          • Microsoft SQL Server 2005 Microsoft SQL Server 2005 SP1 or SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.  

          < top of document >


          Product Compatibility

          In some cases, Wonderware InTouch HMI Version 10.1 SP2 is supported in newer environments than a compatible product. Wonderware InTouch HMI Version 10.1 SP2 has been tested for compatibility with a listed product only in the environments that are supported by that particular product. Wonderware InTouch HMI Version 10.1 SP2 is compatible and can co-exist with the following products:

          • Wonderware Application Server 3.1 SP2
          • ActiveFactory 9.2
          • InTouch CE 10.1
          • Wonderware Historian Server 10.0
          • Performance Software 3.5
          • Wonderware Information Server 3.1
          • InControl 7.11 SP2 P01
          • Manufacturing Execution Module 1.0
          • InBatch 9.0
          • QI Analyst 8.0 SP1 P01
          • SCADAlarm 6.0 SP2 P01

          < top of document >


          Resolved Issues in Wonderware® InTouch HMI Version 10.1 Service Pack 2 

          Wonderware® InTouch HMI Version 10.1 SP2 resolves the following issues. The issues are listed by their Change Request number:

          L00074936, L00092104 Right-clicking on a button with a Show Symbol animation locks the button and disables the ability to left-click. (See SR 15010803 and SR 38610014)
          L00079422, L00089689 If there exists any ArchestrA graphics on a window at run-time and an object includes an OnKeyDown script that hides the current window and shows another window, its behavior reverts back to the default for Wonderware® InTouch HMI Version 10.0. As a result, the UseLegacyOnKeyUp setting in the InTouch.ini file will not trigger OnKeyUp. (See SR 19815365 and SR 15314624)
          L00085383 If RTR items that are binded to a symbol's public custom properties are requested by ArchestrA Symbols, they are not deactivated in DASserver.(See SR 23516834)
          L00085745 A translated tooltip does not show in run-time unless WindowViewer is maximized or moved to the left side of the screen. (See SR 24410903)
          L00086169 An ArchestrA graphic window with analog input displays to the foreground each time an input is changed. The last opened graphic with a Show Symbol animation does not have the focus. (See SR 10415127)
          L00086708 An ArchestrA graphic window with analog input displays to the foreground each time an input is changed. The last opened graphic with ShowSymbol animation does not have the focus. (See SR 10415127)
          L00087233 The item list in DASserver's DDE/SuiteLink PlugIn continues to grow when the same items are requested from ArchestrA graphic properties. (See SR 19416681)
          L00087461 $ApplicationVersion does not get updated on the NAD Client after the NAD Master performs the Notify Clients operation. (See SR 15314757)
          L00088127 The order of the Data Change script execution is different when triggered from a button or from a condition script. (See SR 24513829)
          L00088110 An ArchestrA graphic's analog animation does not update from an ArchestrA object's UDA and shows "#####". (See SR 103114586)
          L00088683 Replacing tags with the IOSetRemoteReference function call results in duplicate handles, eventually exhausting available handles. (See SR 15314822)
          L00088786 In a Galaxy with OS Group security and an InTouch application with ArchestrA-based security,  AttemptInvisibleLogon() fails if the username has an expired password or requires a change in password upon initial login. (See SR 23517329)
          L00088859 ArchestrA Symbol expressions do not properly evaluate input sources set to "---". (See SR 15616286)
          L00089072 When AlarmDbLogger is configured to run as a service, a warning appears stating "The Wonderware Alarm Logger Service service has reported an invalid current state 0". (See SR 37510057)
          L00089288

          The screen shows graphics problems when a window with a combination box is overlapped over another window. (See SR 23517321)

          L00089357

          Dividing by zero results in storing messages to the ArchestrA Logger, but a DMP file is not generated. (See SR 16310081)

          L00090015, L00090390 The previously-entered value is shown when you use the keypad to enter a value.(See SR 10415307)
          L00090252 WindowViewer does not always generate a dump file from View.exe for an access violation exception. (See SR 15314624)
          L00090590

          The Access Name button shows the wrong access name. The tag is pointing to the wrong data source. (See SR 20113078)

          L00090595

          When the WindowViewer memory option is not "Always load windows from disk", the popup symbols opened from a window do not close when the window closes.  (See SR 15616174)

          L00091110 Memory leak occurs if you switch windows that have ArchestrA graphics even when "Always load from disk" is unchecked. (See SR 33810854)
          L00091736 If you log in with an incorrect password immediately after logging in with the correct password, the AttemptInvisibleLogon() function will accept the wrong password. (See SR 37510162)
          L00092149 The InTouch HMI freezes when showing an ArchestrA popup symbol using the Show Symbol animation or Show function from a window with thousands of other ArchestrA Symbols. (See SR 103115490, HF 1368)
          L00092594 Refreshing WindowMaker SmartSymbols on a wide screen monitor or a resolution greater than 1280 pixels by 1024 pixels causes repainting and "ghosting" of moved objects. (See SR 38910016)
          L00092938 When you upgrade from Application Server 3.0 Patch 02 to Application Server 3.1, the application freezes because there is not enough memory to display a bitmap image. You must log off to recover from the error. (See SR 12912080)
          L00093086 WindowViewer crashes after you upgrade from InTouch HMI version 10.0 Patch 03 to InTouch HMI version 10.0 Service Pack 2 and make repeated asynchronous QuickFunction calls. The errors shown are "VarAPI_GetValue : An entry in Script Frame is missing" and "VarAPI_SetArgRealValue : type -1 not handled". (See SR 103115821)
          L00094203 The "Active on Demand" feature was disabled for InTouch HMI version 10.1 but some points are not de-activated and causing critical issues. (See SR 103115892)
          L00094229 In a single node system platform license with a keyless license, the Error Key does not enable WindowViewer despite checking InTouchViewApp under the Special option. (See SR 24514142 and SR 23517958)
          L00094569 Crashes occur when you use View.exe version 1412.466.0.0. This version is not in the InTouch HMI 10.1 Service Pack 2. (See SR 24514168, SR 24514150, and SR 20113127)
          L00094994 PrintScreen and PrintWindow functions do not work when WindowViewer is running as a service. (See SR 19417084 and SR 1950336)
          L00095489 An access violation error occurs when a query exceeds 1 kilobyte in length. (See SR 12610609 and SR 103114053)
          L00096961 After installing HotFix HF 1440, WindowViewer crashes after a few hours when using a blink animation link because the GDI continues to increase to the defined limit specified in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Windows. (See SR 33811098)

          < top of document >


          Known Issues in Wonderware® InTouch HMI Version 10.1 Service Pack 2

          This section describes all known issues in Wonderware® InTouch HMI Version 10.1 SP2. The issues are listed by their Change Request number: 
          L00092171 When starting AlarmDbLoggerManager, the Settings, Stop, and Start buttons remain disabled.
          L00092204 SPCPro is not supported on all versions of the Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, and later operating systems, 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. The InTouch HMI imports files in Galaxy_XXX_localeID_Alarm_Comments.txt format and the header information.
          L00092766
          On Windows Vista, the following help files cannot launch:  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 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. (Reference CRs L00092235 and L00092236. See SR 103115490; HotFix 1404.)
          L00093388 On Windows Vista, the following help files cannot launch:  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.
          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 2008 Server computer hosting an InTouch application that is an alarm provider, the alarm query for retrieving alarms from a remote machine does not work if the application is not running within the console. See Windows 2008 Restrictions for details.
          L00096097 Changes on InTouch CE (Windows 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 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 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 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.

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

          < top of document >


          InTouch Documentation Issues

          The following table lists all documentation corrections to InTouch 10.1 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

          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.

          2

          Application Server Help (IDE.chm),
          "String Substitutions and Language Switching" topic

          n/a 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.

          < top of document >    


          Wonderware® InTouch® HMI Version 10.1 Readme


          Last revision: 01/30/2009

          About This Release

          Version 10.1 of Wonderware® InTouch HMI includes the following enhancements and new features:

          Language Switching for ArchestrA Symbols

          You can switch to localized strings for ArchestrA Symbols. This includes any configuration-time changes to support the extracting and importing of text strings. You can localize the following strings: 
          • Text constant custom properties
          • Text graphics
          • Text overrides of custom properties in WindowMaker 
          You can also add, edit, and remove the locale data from the Symbol Editor.

          Licensing

          InTouch licensing now accounts for Terminal Service sessions. The licensing system now enforces per session licensing to prevent running unlicensed copies of InTouch within Terminal Server Sessions. 

          Non-Administrator Interactive User

          At a high level, this feature allows InTouch run-time functionality to be run by users who do not have administrative rights on the computer. It does not provide this support for configuration operations. Functionality is available for the following operating systems:
          • Windows XP SP3 (Power user)
          • Windows 2003 SP2, R2 + SP2 (Power user)
          • Windows Vista SP1 (Standard user with the UAC enabled)

          Well-known Client Control Support

          The Symbol Editor has been extended to allow new Graphic Objects to appear in the Symbol Editor tool palette.

          Printing Enhancements   

          Several printing features are added to the InTouch HMI:  
          • Saving and Printing a Tag Cross-Reference List
          • Printing Scripts
          • Printing Information about WindowMaker Objects
          • Printing Information about InTouch Windows
          • Printing Window Information from a Command Prompt

          Deployed File Management

          You can add additional files in a managed InTouch application so they are deployed and available at run time.

          < top of document >


          Antivirus Software Exclusions

          Configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders (ensure subfolders of the listed directories are also excluded): C:\Program Files\ArchestrA\
          C:\Program Files\Common files\ArchestrA\
          C:\Program Files\FactorySuite\ (may not exist in newer installations)
          C:\Program Files\Wonderware\
          C:\InSQL\Data\
          C:\Documents and Settings\All Users\Application Data\ArchestrA
          From Application Server Platform objects:
          • History Store Forward directory: (if not default)
          From Application Server Engine objects:
          • Checkpoint directory location (if not default)
          <InTouch Application folder path> including: 
          C:\Documents and Settings\All Users\Application Data\ArchestrA\
          <SMCLoggerStoragefilepath>. The default is:
          C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\
          SQL Server database files of type:
          • .mdf
          • .ldf 

          < top of document >


          System Requirements

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


          Hardware Requirements

          The following lists show the recommended specifications to install Wonderware® InTouch HMI Version 10.1. These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors.

          • Computer with 1.2 gigahertz (GHz) or faster processor
          • 512 MB of memory minimum, 1 gigabyte (GB) or greater recommended
          • At least 4 GB of available disk space
          • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
          • CD-ROM or DVD drive for installation
          • Keyboard
          • Mouse or compatible pointing device

          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 Vista Business
          (See Vista Restrictions)
          Windows Vista Business SP1
          (See Vista Restrictions)
          Windows Vista Enterprise
          (See Vista Restrictions)
          Windows Vista Enterprise SP1
          (See Vista Restrictions)
          Windows Vista Ultimate
          (See Vista Restrictions)
          Windows Vista Ultimate SP1
          (See Vista Restrictions)
          Windows 2003 Standard Server R2
          Windows 2003 Standard Server SP2
          Windows 2003 Enterprise Server R2
          Windows 2003 Enterprise Server SP2
          Windows XP Professional SP3  
          Windows XP Tablet     

          Note:

          • InTouch HMI version 10.1 does not support any version of the Microsoft Windows 2000 operating system. If you attempt to install or upgrade the InTouch HMI on a computer running Microsoft Windows 2000, an error dialog box appears during the installation procedure.
          • Microsoft Windows 2003 Standard Server R2 is the recommended operating system to run InTouch server components. 
          • Microsoft Windows XP Professional SP3 is the recommended operating system to run InTouch client components.

          Vista Restrictions

          • InTouch HMI version 10 or later can run under Windows Vista Enterprise, Windows Vista Business, or Windows Vista Ultimate. The Windows Vista Home Basic and Home Premium editions are not supported. 
          • You can run InTouch only on computers running a 32-bit operating system. You cannot run InTouch on a computer running a 64-bit operating system.  
          • Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system. 
          • If a computer runs Windows Vista as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously. 
          • Windows Vista does 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 graphics 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. 
          • InTouch HMI cannot be configured to run as a Windows Vista service. Windows Vista security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.

           Other Software Requirements

          The following list describes other third-party software required for Application Server version 3.1.
          • Microsoft .NET Framework 3.5 Microsoft .NET Framework 3.5 must be installed on every computer that hosts an InTouch version 10.1 component. The InTouch installation program stops if .NET Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you install .NET Framework 3.5. If you click Install Prerequisites, the installation program automatically installs .NET Framework 3.5. 
          • Microsoft SQL Server 2005 Microsoft SQL Server 2005 SP1 or SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.  

          < top of document >


          Resolved Issues in Wonderware® InTouch HMI Version 10.1

          Wonderware® InTouch HMI Version 10.1 resolves the following issues. The issues are listed by their Change Request number:
          L00034858: For an action script, double-clicking text within the double quotes selects additional text beyond the double-quotes, when a colon (:) follows the text. (See SR 1036163)
          L00037488: You can instantiate a SmartSymbol that references a tag that does not exist. (See SR#2351687)
          L00039308: The InfoAppTitle function does work with non-administrator user rights. (See SR 1036792)
          L00041099: Printscreen and Printwindow functions do not work if WindowViewer is running as service.  
          L00048778 Placing an apostrophe (single quote) in the comment text box of a discrete alarm tag (OnMsg) causes the Alarm DB Logger to fail to log an alarm.
          L00067243: Control label text is scrambled when created using the Wizard Graphics and saved as a SmartSymbol. (See SR 23514920)
          L00071647: The OnShow script in an ArchestrA Symbol appears to run, but the script does not set an attribute. (See SR 14811879)
          L00072300: When a client control is deleted and a new version of the client control is imported from a remote IDE, an ArchestrA Symbol referencing the client control will show Version 1 on the remote IDE and Version 2 on the Galaxy Repository IDE. This is a mismatch of versions. (See SR 103112086) 
          L00073550: The graphic element reference list is incomplete, or it is corrupted. The error message "Failed to get Graphic element reference list" appears in the SMC logger. (See SR 23515471)
          L00075206: Customized graphic text is lost after group change. (See SR14811926)
          L00075269: The RegisterEngine number decreases when a new connection is made using remote desktop (TSE) to the Application Server. (See SR 16310052)
          L00075763: Custom property links for ArchestrA symbols do not accept the following special characters that can be used in InTouch tag names:  _(underscore), -(hyphen), $(dollar), %(percent), and &(ampersand).
          L00075800: MX References do not start in scripting; .InputSource in ArchestrA Symbols does not start in scripting. The MX References do work on display the link and in a custom property. (See SR 15010810)
          L00076011: Graphic symbol custom property overrides are lost after group change. (See SR 14811926)
          L00076900: Warning "Could not find embedded graphics" appears after a template and its instances of a Galaxy are exported as an aaPKG file, and are then re-imported into a new Galaxy. (See SR 33430263)
          L00081430: License enforcement of Terminal Service Edition does not work. Too many WindowViewer sessions are permitted to open.
          L00081739: The Graphic toolbox pop-up window and the Graphics tab preview window thumbnails show "not found" when an application object instance containing symbols with date time picker is imported in a new Galaxy.
          L00083495: SPC Pro does not work when WindowViewer is started up directly on a computer with a  standard user login.
          L00085207: If you are using the SPC Control Chart on the Windows Vista operating system, you need to specify a System Data Source Name (DSN) and make sure that all application users can write to the folder in which the database file resides.

          1) The ODBC data source needs to be created as a System DSN and not as a User DSN. As application creator must be admin/power-user and application user can be standard user, it is likely these will be different users. A User DSN won't work for standard user and gives errors in the SMC.

          2) If you are using a database file (such as a Microsoft Access MDB file), then application creator must ensure that the application user can write to the folder in which the database file resides. Writing is required for database access (for example, adding sample points in the database). By default, most folders are not write-enabled.

          < top of document >


          Known Issues in Wonderware® InTouch HMI Version 10.1

          This section describes all known issues in Wonderware® InTouch HMI Version 10.1. 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.
          http://www.microsoft.com/downloads/details.aspx?FamilyID=84bbefa4-7047-41df-8583-e3bdbf9d805f&DisplayLang=en
          L00086229: Running the Alarm DB Logger 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.

          < top of document >


          InTouch Documentation Issues

          The following table lists all documentation corrections to InTouch 10.1 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
          (ITAddendum.pdf),
          ".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"

          < top of document >


          InTouch Documentation

          The InTouch product library consists of a set of Portable Document Files ( PDF) located in the UserDocs folder of the InTouch installation CD. 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 on a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. InTouch installation instructions are located in the root folder of the InTouch installation CD as an online help file. You can view these instructions by clicking Help as you complete the InTouch installation procedure. 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 >


          © 2011 Invensys Systems, Inc. All Rights Reserved.