InTouch 9.5 SP1
Last revision: 02/14/2007
This document contains important information about WonderwareÒ InTouch 9.5 with SP1. Review this document for known issues in this version and changes to the InTouch documentation included on this CD.
Upgrading from a
Previous Version
Resolved Issues –
InTouch 9.5 with SP1
Known Issues – InTouch
9.5 with SP1
Known Restrictions for Limited Users – InTouch 9.5 with SP1
Known Issues – InTouch Documentation
The language switching features in InTouch have been changed in InTouch 9.5 SP1. For more information, see the Localizing Alarm and Tag Comments document (LanguageSwitching.pdf) in the C:\Program Files\Wonderware\InTouch folder.
- Do not install InTouch on your Domain Controller. This is unsupported and can cause problems.
- InTouch 9.5 with SP1 will not install on a computer with Microsoft .NET Framework 2.0 Beta 2.
- When you start the install process, if you don’t have Microsoft .NET Framework 1.1 installed, the InTouch installation process installs it for you.
To run InTouch, we recommend at least the following software and hardware configurations:
Software
Requirements
Microsoft® Windows® Server 2003 with Service Pack 1 or
Microsoft® Windows® Server 2003 R2 or
Microsoft® Windows® 2000 Server with Service Pack 4 or
Microsoft® Windows® 2000 Advanced Server with Service Pack 4 or
Microsoft® Windows XP Professional with Service Pack 2 or
Microsoft® Windows® XP
Tablet PC Edition
Hardware
Requirements
PC with 1.2 gigahertz (GHz) or faster processor
512 MB memory minimum, 1 gigabyte recommended
At least 4 gigabytes (GB) of available hard disk space
Super VGA (1024 × 768) or higher resolution video adapter and monitor
CD-ROM or DVD drive for installation
Keyboard and mouse or compatible pointing device
Microsoft Windows Server
2003 Support and Requirements:
- InTouch 9.5 with SP1 Terminal Services Edition is supported on Microsoft Windows Server 2003 with Terminal Server enabled. The default setting for enabling Terminal Server on Windows Server 2003 is Application Server mode.
- Windows Server 2003 Terminal Server client User Name(s) must be a member of the Windows “Remote Desktop Users” and “Power Users” groups to connect to the server and to run applications on the server.
- TSAC (Terminal Services Advanced Client) functionality has been updated by Microsoft. For more information, see the Microsoft website http://www.microsoft.com/ and the Windows Server 2003 Administration Tools Pack Overview.
Note: Windows Server 2003 Terminal Server does not allow two clients to login with the same user ID. Each Terminal Services session has to have a unique user ID to connect to the Windows Server 2003 Terminal Server.
InTouch 9.5 with SP1 can be installed on a system without an existing installed version of InTouch or it can be installed as an upgrade to a system that already has InTouch 8.0 or later.
When upgrading from InTouch 8.0, the installation procedure detects which components are already installed on your system and updates your system accordingly. Adding components or removing any existing installed components during the upgrade is not recommended.
Upgrading to InTouch 9.5 with SP1 may require a reboot if the Microsoft MDAC version currently installed on the system is not up to the prerequisite version level required. InTouch 9.5 with SP1 requires, as a minimum, MDAC 2.7 SP1 for Windows 2000 and Windows XP Professional, and MDAC 2.8 for Windows Server 2003. The MDAC version is automatically checked during the installation procedure.
If you are upgrading from InTouch 7.11 or prior to InTouch 9.5 with SP1, uninstall InTouch before you install the new version.
If InTouch 7.11 is installed on your system and you have Alarm DB Logger set to run as a service, change the service mode to manual before you uninstall InTouch and reboot your system. You must also ensure that this service is not running before you install InTouch 9.5 with SP1. Otherwise, the installation cannot update the files properly. If you uninstall InTouch 7.11 with Alarm DB Logger in automatic mode, the InTouch 9.5 with SP1 installation will not complete properly.
Install InTouch Terminal Services on a dedicated server. We strongly recommend that you do not install InTouch Terminal Services on any computer that also acts as a database server (such as IndustrialSQL Server), RAS server or PPTP server.
InTouch and InTouch Terminal Services are not supported and should not be installed on a system that is configured to be a domain controller. InTouch Terminal Services is designed to perform like Windows 2000 Professional at the end-user level: it does not assign top priority to critical domain-level processes. Installing InTouch Terminal Services on any of these servers can significantly degrade performance.
Important Note: If you must copy the whole InTouch CD to a folder on your hard drive first and then run the installation from this folder, the full path name of this folder should not have a blank space in it. This does not affect users installing InTouch directly from the CD.
The quality dot field of a Remote Reference IO Tag from a
Tag Server is not updated correctly and is stuck at 192.
L00054233: Opening windows and displaying remote reference
tag values degrades over time.
Remote references to Galaxy IO tags, using
IOSetRemoteReferences() to display .#VString and .#QString values degrade over a
period of time.
L00054252: Font size in
internal windows, the SQL Access Manager Bind list, and the Table template is
too small to read.
The font size of internal windows for the
RecipeSelectRecipe() function in runtime and for the SQL Access Manager Bind
list and the Table template in development is too small to be read.
L00054614: Duplicate PhraseID for text objects in exported
language XML file
Duplicating an existing InTouch window containg text
objects resulting duplicated PhaseID in the exported language XML file.
L00054763: New setting in InTouch.ini setting to allow
.Quality to be set for Clamped Low or Clamped High state.
New setting
"SetQualityClamp=1" in the InTouch.ini file (in the Application directory) to
allow .Quality to be set for Clamped Low(85) or Clamped High(86) state. If
"SetQualityClamp=0" or if it is not present in InTouch.ini file then the
.Quality will not be clamped when the tag value is beyond its limits.
L00055088: In AlarmDBViewCtrl, ACK_RTN value is not correct
for Expanded Summary ACK Model alarm
If a tag is configured as an Expanded Summary ACK Model
alarm, the value field is not updated properly when the Alarm State changes to
ACK_RTN.
Note: The fix only applies to alarms newly
generated by InTouch 9.5 SP1.
L00055732: Unable to download or
update application on NAD client if source application includes SmartSymbol
templates and the client is logged on to windows as a Power User.
If an InTouch application has
SmartSymbol templates (i.e. there are subfolders/files in the Symbol folder),
downloading the application to a Terminal Services session generates
an error dialog "NAD unable to download new application" and the info
message "NAD could not copy directory . . ." is logged.
L00056377: On dual-core PCs, AlarmMgr.exe
tries forever to connect to providers, even when InTouch View.exe is shut
down.
On multi-core or multi-processor PCs, during window
compilation of View.exe startup, AlarmMgr.exe attempts to make connections to
any alarm providers specified in AlarmViewerControl queries. If
a connection was successful, it remains open subscribing to
alarms. If the connection was not successful, AlarmMgr.exe keeps trying and
repeatedly writes "Attempting to Connect to Provider" messages to the
logger. AlarmMgr.exe does this even though there is no client (such as
View.exe's AlarmViewerControl) interested in the alarms.
L00056756: Translation
associated with text phrase is erased when the text in the original text object
is changed and exported again.
Translation field of the text phrase is erased when the
text in the original text object is changed and exported again.
L00056879: Tooltips are not translated properly during the
Language switching process.
Duplicating an object that has the static text tooltip
configured results in the duplication of the phraseID, and the translation of
the tooltip is not working properly.
L00057173:
InTouch application with Access Names configured for Failover leaks
handles.
InTouch
application crashes after running for around 15 hours. This application contains
Access Names configured for Failover.
L00059184:
Tag count in an InTouch application is not matched with the tag license.
Tag count is not matched with
the tag license and an error message pops up when activating a remote tag
"Attempt to activate remote tags failed. Exceeded Maximum Number of Remote
Tags."
L00059228: AddPermission does not
work with both a Parent Domain and a Child Domain.
When there is a Parent Domain
and a Child Domain then AddPermission only works for the domain that the
computer is a member of (as seen in Control Panel/System).
L00060620: Switching between windows in an InTouch
application a few times, shut down WindowViewer, then View.exe crashed.
In an InTouch application
which connects to a galaxy, switching between InTouch windows a few times
then shutting down WindowViewer caused View.exe to crash.
L00060622: Using "%" in the
LogMessage() function can crash WindowViewer.
WindowViewer crashes when using "%" in the LogMessage()
script function, e.g. LogMessage( "%Z" );
L00060624:
AlarmMgr.exe Process Affinity can not be configured through registry keys.
In a PC with more than one CPU
(Dual-core, Quad-core ...), the AlarmMgr.exe Process Affinity can be configured
as follows. (If there is no registry setting, AlarmMgr.exe uses all available
CPUs by default.)
HKEY_LOCAL_MACHINE:Software\Wonderware\AlarmManager
DWORD value CPUAffinityMask
is a bit value
of the CPU you want alarm manager to use.
Example for Dual-core:
1 = CPU0, Value 2 = CPU1, value 3 = CPU0 AND CPU1.
DWORD value CPUAffinityState
0 = default =
apply specified affinity mask, or else ALL CPUs if "CPUAffinityMask" is missing.
1 = apply
affinity to all available processors, regardless of the "CPUAffinityMask"
setting
2 =
don't do anything at all, let the OS decide what to do with the process (limited
testing is, it has affinity for all available processors).
L00060771: Implement Tag Comment and Alarm Comment Language
Switching in InTouch 9.5 SP1
Tag comment and Alarm comment can be localized
through language switching feature in InTouch 9.5 SP1.
L00061213: Remote Tags do not update when View is started
in InTouch TSE.
In an
InTouch TSE application, if there are I/O tags (ITag1, DTag1) and an access
name ("MyAccessName") that refers to the local machine, using View.exe as an
application name and Tagname as a topic name, the value display for the remote
reference MyAccessName:DTag1 or MyAccessName:ITag1 does not display properly
when View.exe starts.
L00061247: aaLogger.exe uses 100%
CPU.
Corrupted log file can
cause aaLogger.exe to run at 100% CPU.
L00061465: View.exe crashes if set as service and using
logoncurrentuser() script function with OS security.
View.exe crashes if it is set as a service and you
are using the logoncurrentuser() script function with OS security.
L00061995: The input field of a user input animation link
should be resizeable in size and font to fit high resolution screen
settings.
The input field for the Analog and/or String user input links can be resized with the mouse pointer when there is a setting in the InTouch.ini file for Resizable InputLink in the [InTouch] section. The Resizable InputLink setting must use a non-zero value for the resizable input field. After the Input field is resized the first time, WindowViewer adds two more settings in the InTouch.ini file, Resizable InputLink Width and Resizable InputLink Height, for the width and height (in pixels) of the Input field dialog. You can change these settings manually.
Example:
[InTouch]
Resizable InputLink = 1
Resizable
InputLink Width=300
Resizable InputLink
Height=50
L00062215: Query Filter for Alarm comment does not retrieve any records during language switching
If the alarm database contains old data records that are
not configured for language switching (which do not have the two-character
application ID) and new records configured for language switching (which are
prefixed with the two-character application ID), you can not use alarm comment
queries that use the operators <, <=, >, and >=.
Installation
L00040464: During installation on any supported Windows platform, the online help doesn’t open properly if you are installing from a remote location
During the Installation Wizard, a button becomes available to open the Installation Guide online help. The online help opens and then reports that the page cannot be found. Security patch 896358 from Microsoft prevents .chm files from opening from a remote location. For more information, see Microsoft’s website.
SuiteVoyager Compatibility
L00041139: WinXML Exporter in SuiteVoyager 2.5 cannot handle InTouch 9.5 applications
The WinXML Exporter in SuiteVoyager 2.5 is not compatible with application files created with InTouch 9.5. These are therefore not supported with SuiteVoyager 2.5 or earlier. Existing SuiteVoyager applications are not affected. Please refer to the Wonderware Technical Support website for an updated version of WinXML Exporter.
SmartSymbols
L00038541: SmartSymbol instances that referenced local tagnames are not updated with the new name when a tag is renamed
You may edit a SmartSymbol that includes placeholder tagnames or local tagnames using the Replace function. If an edit is made to an undefined tag, the replacement is not made.
L00038868: Importing SmartSymbols with names that use foreign characters
If you create a SmartSymbol using foreign characters in the name, when you import that SmartSymbol into InTouch using English, the characters in the name are random ANSI characters.
L00039587: Action scripts and Smart symbols during import and export
Animation scripts in SmartSymbols get lost if there is a reference to a Quick Function and the function is not defined in the target application.
L00039994: Undoing string substitutions not supported when editing SmartSymbols
You cannot undo a string substitution of a text object embedded within a SmartSymbol if the string substitution is performed during a SmartSymbol Edit operation. To work around this limitation, cancel the SmartSymbol Edit operation and start over.
L00040177: Captions in SmartSymbols not reflecting translation changes
When you are using Language Switching, the caption on a SmartSymbol button is not translated if the SmartSymbol was edited and the changes committed. The workaround is to re-export and import the dictionaries.
L00040232: Substitute Strings work differently than using the native SmartSymbol properties.
To avoid resizing issues when replacing text, we recommend using substitute strings rather than the SmartSymbol properties.
L00040291: Importing SmartSymbols from 9.0 to 9.5
After migrating applications developed in 9.0, you may see problems. These problems appear when you:
- Edit the properties of SmartSymbols using the replace function or if you are binding a new SmartSymbol instance to an ArchestrA object. In these cases, the replace may not work correctly.
- Change the SmartSymbol instance reference with the Dot field doesn't change until you break the cell and manually substitute it.
Additionally, you can see:
- Substitute Tags for SmartSymbols does not show the modified references if the expression has references with new line characters.
If any of these happens, do the following:
- Put the SmartSymbol in Edit mode. You don’t have to make any changes.
- Commit the edit.
L00040591: Error: “Disk write error. Out of disk space”
If a SmartSymbol size increases to more than 32 KB, you see this error.
L00040763: Exporting language files to the same folder
If you export a language dictionary, do not export it to a folder that has another exported language dictionary. Always export your language dictionary to a folder by itself.
Import/Export/Migration
L00036952: Migrating an AlarmSuite database several times
If you migrate the same AlarmSuite database two or more times, AlarmSuite History Migration duplicates the data and does not overwrite all the data. To avoid this, don’t migrate the same AlarmSuite database two or more times.
L00040234: Trying to assign to a read-only name error when converting an InTouch 8.0 application to 9.5
“Trying to assign to a read-only name" error message appears when converting an 8.0 application to 9.5. This error occurs because of the read-only tag ($False) introduced for the replacement of the read-write $AlarmLogging and other four obsolete system tags in InTouch 9.5. The $False tag is a discrete read-only tag so as to restrict the usage of this dummy tag.
Also, if the Window script uses $AlarmLogging expressions and tries to update the read-only $False tag, the entire script is removed from the Window script and the entire script code is logged in the SMC logger. This helps you modify the Window script with the correct code accordingly.
History and Logging
L00018588: AlarmDBLogger skips the alarm records if the master record is not present in the database
AlarmDBLogger skips the alarm records if the master record is not present in the database. AlarmDBLogger skips the sub state change alarm records if the master record (equivalent ALM record) is not present in the database.
This situation can occur if an Alarm Database Purge is performed while there are tags in an alarm state. Changes to the alarm state of these tags are not logged.
Terminal Services
L00026212: Using NAD in Terminal Services
When NAD is used in a Terminal Server implementation, it is common for the NAD Master and the client copies of the InTouch application to reside on the same node. In this situation, it is unlikely that you are sharing the NAD Master folder.
If you are using Windows 2003, the NAD Master folder must be shared even if all files are on the same machine. Failure to do so results in a NAD failure to copy error when the client launches View.
L00041123: Using a query configured in Distributed Name Manager, you may not see some alarms
In an InTouch TSE Console session, a Distributed Alarm Object or Alarm Viewer using a query configured in the Distributed Name Manager does not display alarms if a platform starts before WindowViewer. Standard queries like \\<NodeName>\InTouch!$System work in this scenario. Starting WindowViewer before the Platform also works.
Adding the following entry to the InTouch section of the Win.ini in the Windows folder before starting WindowViewer, makes the alarm query configured in Distributed Name manager work properly.
ApplicationDirectory=<Full Path to the current application>
This is a problem only in the Console session, not Terminal Server client sessions.
WindowMaker
L00017860: Retentive and History errors when starting WindowMaker while View is running
Errors may be encountered when using the FastSwitch to open WindowMaker from View running an application that is logging historical data and is using some retentive tags, and is currently getting live updates.
L00037481: Setting the color for a button is not applying the color to the button
If you change the color of text on a button object using the Text Color tool in WindowMaker, the default settings for button text in the WindowMaker configuration are not updated with the new color. For text-only objects, the default color is updated.
WindowViewer
L00057767: Condition script goes into an endless loop if an IO Discrete tag resets its value in the script (100% CPU)
1. In an InTouch application, the following conditions lead to 100% CPU and the condition script will go to an infinite loop:
- An I/O discrete tag
(DTag1) refers to itself as an item name in an access name, e.g. MyAccess.
- A condition script resets
the discrete tag value to FALSE.
- A User Input link sets the discrete tag value to TRUE.
- A value display link
displays the discrete tag as a remote reference, e.g. MyAccess:DTag1
To work around this issue, the value
display link should be changed to DTag1.
2. A condition script will execute multiple times in the
following conditions:
- An I/O
discrete tag (DTag1) refers to another I/O discrete tag or memory discrete tag
as an item name in an access name, e.g. MyAccess.
- A condition script resets
the discrete tag value to FALSE.
- A User Input link sets the discrete tag value to TRUE.
Networks
L00021841: Hot Backup Pair - Client does not detect loss of network connection to Primary for 90+ seconds
It can take up to 3 minutes for a client to detect the loss of network connection and switch to backup.
This is a TCP/IP timing issue in Windows.
Alarm Tree Viewer
L00041015: Alarm Tree Viewer ActiveX Control has a limit on the number of alarm groups
The Alarm Tree Viewer ActiveX Control is successfully
tested with an approximate maximum of 500 Alarm Groups. The maximum number of
Alarm Groups that can be displayed depends on various factors, including the
Alarm Providers used and the total length of the Alarm Group names returned.
When the maximum number of Alarm Groups in the Alarm Tree Viewer ActiveX Control
is exceeded, no Alarm Groups are shown, and the following statement is found in
the Log Viewer (in the System Management Console): “Failed to retrieve the alarm
groups from the alarm subsystem provider All Providers.”
Miscellaneous
L00021260: Recipe Manager cannot verify the remote tag reference type at load time
Remote tag references are not supported in Recipe Manager.
L00023091: Searching using the cross reference utility crashes
If you are using the cross reference utility and you are
searching SQL, SPC, and Recipe at the same time, an error may occur if the
recipe file (recipe.csv) has more than 2048 characters in any one line.
L00025890: Some dialog boxes are not
modal
The following dialog boxes can lose focus and slip behind other windows:
- Windows to Close dialog box
- Change Password dialog box
- Configure user dialog box
- Open Window dialog box
- Close Window dialog box
- ODBC Data Source Administrator dialog box
Do not click on other applications or windows before closing these dialog boxes. If you do, you may need to restart View to correct the problem.
L00026993: For a non-admin user, with EnableDisableKeys(1,1,1) enabled, all the buttons in the shutdown dialog are active
In the Shutdown dialog box, all the buttons are active for non-admin users if the script EnableDisableKeys(1,1,1) is executed. Click on EnableDisableKeys(0,0,0) button to reset the settings.
The other shortcut keys like Ctrl+Esc, Alt+Esc, WinKey+E and so on are disabled.
L00037028: Cannot create new tables with Restore Utility if DB name includes double-byte characters
If the alarm database name contains double-byte characters, you cannot recreate tables using the Restore utility.
L00038542: Using I/O tagnames and DDE communication
Do not reference an I/O tagname linked to an access name with DDE type communication from an Asynchronous Quick Function.
L00039255: Status bar only accepts up to 9999 as values for X, Y, Width and Height
You can resize the object up to 9999 using the status bar.
You can resize the object further using the mouse.
L00039904: Windows are not placed correctly when using the Windows XP theme
If you are using the Windows XP theme, in InTouch when you open and close windows whose placement is based on calculations using $ObjVer and $ObjHor, you may experience positioning errors.
L00040561: Long path names
You cannot open an application in WindowMaker if the base path directory contains 114 or more characters. The default directory and the application directory together must be fewer than 114 characters.
L00040649: Double byte fonts on Windows 2000
On Windows 2000 only certain TrueType fonts work correctly. A simple work around is to use the fonts that work for those specific phrases in the Dictionary.
Japanese
|
Lucida Sans
Unicode |
Microsoft Sans
Serif |
MS Gothic |
MS Mincho |
|
MS PGothic |
MS PMincho |
MS UI Gothic |
NSimSun |
|
SimHei |
SimSun |
Tahoma |
|
Simplified Chinese
|
Microsoft Sans Serif |
NSimSun |
MS UI Gothic |
SimSun |
Tahoma |
L00062097: After a failover, not all the topics transfer to the secondary node from the primary node
When an AccessName is configured for the secondary node, the secondary configuration information is stored internally as another AccessName with the string _SEC appended to the AccessName's name. For example, if AB_HFPP is the AccessName for which the secondary node is configured, then two access names are created internally named AB_HFPP and AB_HFPP_SEC. If a new AccessName is also created with the name AB_HFPP_SEC, this AccessName will conflict with the already existing AB_HFPP_SEC file. The workaround for this is to modify either of the AccessNames so that their names should be different, such as AB_HFPP and AB_HFPP2.
Although InTouch 9.5 with SP1 can be run by Limited Users, certain features and operations will not be supported for Limited Users. We recommend that users who configure InTouch applications have Power User privileges. The following operations are not supported for Limited Users:
- Installing or uninstalling Wizards and ActiveX controls.
- Configuring node properties (Limited Users will not be permitted to access Node Properties in the Application Manager).
- Converting 16 bit applications created in InTouch 5.6.
- Opening applications created by other users.
- Using the license utility.
- Using SPCPro features.
- Using the Alarm Purge-Archive utility.
- Using the Alarm DB Restore utility.
- Using the AlarmSuite History Migration utility.
- Changing the Alarm DB Logger settings.
The following table describes changes to the documentation.
Item |
Location of Change |
Existing Documentation |
Change |
|
1 |
None at this time |
None at this time |
None at this time |
The InTouch documentation set is provided in PDF format (except the Installation Guide) and can be printed. Viewing these user's guides requires installation of Adobe's Acrobat Reader. This utility is not included on this CD, but you can download it for free from Adobe's website at the following web address:
www.adobe.com/products/acrobat/readstep2.html
After downloading the file from Adobe, you must run the executable to install it on your PC. Follow the typical installation routine. After installation, you can either start the Acrobat Reader and open a user's guide from the File menu or double-click a user's guide on the CD in Windows Explorer. The PDF files are located in the UserDocs folder in the CD root. The Installation Guide is located on the CD root.
Information included in these guides is provided in online Help, which can be opened using the Help menu options in each utility.
