This ReadMe file
describes the defects fixed in this patch and known issues.
Before installing this patch, it is strongly recommended that you
exit all FactorySuite® programs, including executable (.exe) files
and services.
This InTouch 7.11 Patch 07 Build has primarily been tested on:
1. Windows
XP Professional with SP2 and MDAC 2.81
2. Windows
2000 Professional with SP4 and MDAC 2.7 SP1
3. Windows
NT 4.0 SP6a and MDAC 2.60
4. Internet
Explorer 6.0 SP1
* NetDDE is not supported
on Windows XP SP2, Windows 2003 and later operating systems.
Microsoft Windows XP SP2 introduces several security technologies
including disabled NetDDE, enhanced Windows firewall, and a reduced RPC attack
surface. These enhancements affect the uses of NetDDE, WWLogger, and SuiteLink
protocols in InTouch.
If InTouch needs to be operated on Windows XP SP2, you should contact your
local Wonderware Distributor or download the OS Configuration Utility from the
Wonderware Technical Support web site (www.wonderware.com/support/mmi). This
utility opens specific ports that enable NetDDE and adds Wonderware SuiteLink
and Wonderware Logger to the firewall exception list.
InTouch will not work properly on a Windows XP SP2 computer if you do not run
the OS Configuration Utility after installation of InTouch.
The following defects were fixed for this patch release. Click on
the defect number for a more detailed description of the problem.
L00006191 Duplicate
shortcut keys in SQL Access Manager/Table Template Configuration dialog box in
the German version of InTouch 7.11.
L00009846 3Dtext
and text object in Japanese version of InTouch 7.11 P03 (double-byte code) is
displayed rotated or using incorrect font.
L00011536 In
the French version of InTouch 7.11, an item cannot be added to the Symbol
Factory object library.
L00012425 AlarmDBView
Control takes a long time to get populated with data if database contains a
large number of records.
L00014196 The
"Invalid floating pt value" error message box is not modal (is
hidden).
L00014738 SuperTags
are not shown in alphabetical order, but are in the order in which they were
created.
L00014778 Logger
shows Mutex errors after a few days of running InControl.
L00015140 Wizard
is not retaining animation links.
L00015163 "Not
enough space for string - new name too long?" error message is displayed
when you attempt to convert an InTouch application to another screen
resolution.
L00016049
There is a difference in the text display block between single and double byte
characters. Double byte character fields are much wider that the text included.
L00016475 Inconsistent
message dialog boxes are displayed when using illegal characters along with hex
numbers and/or tagnames in a script.
L00016753 Unexpected
results occur when setting width of pen in 16-pen trend during design time.
L00016921 Fast
switching from WindowMaker to WindowViewer causes the following error messages
in WWLogger:
AlarmBuf /!CBThrd_Dispatch_Timer1Sec PostThreadMessage failed - Error: (1444) -
Invalid thread identifier.
AlarmBuf /!PostThreadMessage(0) (thread-id=0x724) failed
(AlmMgr=0x710,0x648,0x724).
L00016991 Fonts
display is 'blotchy' in WindowMaker when using 'Smooth edges of screen fonts'
setting. Fonts in WindowViewer are displayed OK.
L00017565 Alarm
Purge/Archive shuts down when user clicks OK.
L00017621 Tag
assignment in 16-pen window results in "Tagname.x is in an out-of-date
format or corrupted" and the application cannot be opened again.
L00017790 The
Edit Custom Color dialog box, when opened from the 16-pen trend control dialog
box, causes WindowMaker to crash.
L00017809 X
or Y location of window changes when reducing the width or height of the window
manually and without saving and closing.
L00017828
Cannot change a double byte font in AlarmDBView control.
L00017865 Unselecting
all radio button settings in Discrete Value Pushbutton can crash WindowViewer.
L00017867 In
the French version of InTouch, the Set/Reset Display button has incorrect
translation for Open.
L00017877 When
a new application and a new window are created, printing the window disables
WindowMaker after the printout.
L00017904 It
is possible to clear all radio buttons (unchecked) in the animation links, such
as Object Height/Width and the Percent Fills, which causes WindowMaker to
crash.
L00017934 In
the 16 Pen Trend environment, switching between WindowMaker and WindowViewer
and then clicking on the scooter (or F2) will increase its size.
L00017936 When
creating a new WWALMDB, Alarm DB Logger does not set any permissions for WWUser
/ WWPower / WWAdmin users for the *Ex views; hence those accounts cannot be
used for alarm retrieval using Alarm DB View.
L00017944 In
the 16 Pen Trend environment, Pen Trend goes blank in the run-time if trend is
stopped (Stop button) while the Configuration dialog box is opened.
L00017975 In
the French version of InTouch, the All and Historical options on the Query tab
in Alarm DB Logger Manager are not translated.
L00017979 In
the Japanese version of InTouch, creating an application path with certain
Japanese characters and deleting the application from the list causes the
InTouch Application Manager to not find the application.
L00017982 In
the Japanese version of InTouch, the All and Historical options on the Query
tab in Alarm DB Logger Manager are not translated.
L00017994 Alarm
DB Logger Manager hangs if the Alarm database was not created and you click
Start.
L00017999 Not
able to log alarms as user wwPower in the Alarm DB Logger.
L00018231 In
Japanese version of InTouch, there are corrupted fonts in WindowMaker dialog
boxes using Japanese local settings.
L00018283 Alarm
DB Logger will not function if there are more than 16 lines of queries in its
Alarm Query configuration.
L00018284 The
sharing of the Wonderware license folder when InTouch is started is a security
concern. Provide the ability to halt the sharing of this folder.
L00018294 After
installation of InTouch 7.11 Patch 06, Alarm DB Logger no longer logged alarms
to the database.
L00018335 In
the French, German, and Japanese versions of InTouch, the word “None” in the
following error message is translated: "Change Password for Operator
None".
L00018519 Enhancement
to the 16-pen trend functionality to eliminate occasional double thick line.
L00018566 WindowViewer
crashes on initialization of a HistData wizard.
L00018756 The
Cross Reference utility’s Save As function does not write the tag link locations
to the CSV file as documented in the InTouch Users Guide.
L00018790 In
the Japanese version of InTouch, the color fill animation link is the opposite
of what is true.
L00018838 Use
of the DialogValueEntry or DialogStringEntry causes a crash when users’ IDEA
script function is only used in Application On Shutdown script.
L00018906 In
Historical trending mode, 16-pen trend, the start time of the trend is the
current time. This problem results in an empty future trend.
L00019008 In
the Japanese version of InTouch, the error "can not open tagname.x"
is displayed after importing windows containing the password wizard.
L00019096 Changing
the font properties does not always provide the same results.
L00019104 The
Log file *.ALG does not include the Alarm Comment when the ACK or .ACK was
used, or when the almAck comment was blank (empty string).
L00019196 Unreadable
characters displayed in the keypad (a dash "-" looks the same as
period ".").
L00019283 No
longer able to use the AlarmDBView ActiveX in Visual Basic after installation
of InTouch Patch 06.
L00019352 Using
local variables in GetNodeName() will get error message dialog "Must have
writeable message variable for this argument to GetNodeName".
L00019410 The
Hardware/Software flow control settings are not preserved in the Alarm Printer.
L00019431 WWRequest
does not function after a failed connection.
L00019440 Failed
to create view in wwAlmDB by using AlterWWALMDB.exe.
L00019460 Crash
related to special characters in the MSSQL DB; no crash if unused tags are
deleted from the InTouch application.
L00019569 After
disabling and enabling InSQL, the analog tag does not update. InSQL shows Null
until the tag changes value.
L00019699 During
UNACK_RTN events, when ACKed on a client of a Hot Backup pair, the ACK is not
sent to the backup computer.
L00020058 DAO
querying a Hot Backup pair does not detect that WindowViewer is shutdown on the
primary provider when the Alarm DB Logger is also running on the primary
provider.
L00020170 AlterWWALMDB.EXE
in InTouch Patch 06 fails when used with Microsoft SQL Server 7.0 SP3. Error
message is the following: “Failed to Create v_AlarmEventHistoryEx1 view”. This
function works OK on SQL Server 2000 and MSDE.
L00020214 Tagname
Dictionary allows "Ctrl+Enter" to be typed in the Alarm Comment field
of Discrete tags, which results in an embedded CRLF that causes problems for
DBDump/DBLoad.
L00020312 Alarm
DB Restore stops restoring when it encounters comments in the comment file that
contain a comma.
L00020460 WWDlg_ScriptEdit
returns a modified script when the user clicks Cancel. There is no way to know
whether the user clicks OK or Cancel to close the Script Editor.
L00020552 Unable
to write to the ROCpct dot field from an IDEA application.
L00020559 Windows
Textbox only displays 130 characters of a 131-character-long tag.
L00020610 A
gap is displayed on the right side of a historical trend during the fall back
time change in October for Greenwich time zone when it is set to auto adjust
for time change.
L00020697 Enhancement
request: New feature to be able to bypass the creation of placeholders (based
on the existence of tags in the tagname dictionary) when windows and scripts
are imported from one application to another.
L00020741 The
following error message is displayed on alarm consumer’s node after a provider
stop/start: "/UNKNOWN /!SmartHeap Error Code 14, MEM_BAD_POINTER 00140188,
in pool 0 /UNKNOWN /!memory corruption(4013002B) val=0x40 -> AlarmConsumer
must restart".
L00020742 Screen
display flickers when halo is bigger than screen resolution and the mouse is
moved over push buttons.
L00020788 If
the password of the SPCPro database user is more than 4 characters long, an
SPCPro application or HeapShareFree error message is displayed when WindowMaker
is started.
L00020819 When
browsing tags during historical trend pen assignment, the entire remote tagname
dictionary is displayed instead of only the history tags.
L00021400 If
an application is developed with a later version of InTouch, the Application
Manager states the version as 'Old'.
L00021729 The
alarm system registers Rate of Change alarm based on a previous setpoint at
startup when Retentive Parameters is selected for a tag.
L00022064 Cross
Reference utility crashes WindowMaker if specific Recipe.csv file is in the
application directory.
L00022250 Not
enough disk space error is displayed when trying to install InTouch Patch 5a.
L00022365 In
the French version of InTouch, the Set/Reset Display button has incorrect
translation for "Open".
L00022618 Incorrect
info on the SPCPro About box.
L00022760 Alarm
entries are corrupted when acknowledged if the AlarmUserDefStr is set in the application
on a start script.
L00022771 An
Alarm Tree ActiveX object displays the following error message when calling
scripts. "Error processing AlarmTree1.UpdateView on method call (execute).
Exception 0x800A005B: Object variable or With block variable not set".
L00022981 Tags
Alarm 'Disabled' properties (for example, AlarmLoEnabled and .AlarmHiEnabled)
are not being retained if 'Update Use Counts' is used with WindowMaker.
L00023092 60k
license is not allowing over 61,405 RTR (and local tags, total).
L00024256 In
the Tagname Dictionary (SuperTags), the member list does not work after
clicking Select then Cancel.
L00024292 A
/View Unknown Opcode in GetSValue popup message is displayed from
QuickFunction.
L00024336 Text
Object's Font size does not save correctly when modifications are done with the
mouse.
L00024601 The
AlterWWALMDB.exe utility does not use the "top max records" setting
in the dialog for the first run, but rather uses the default 1000 records.
L00025147 The
InTouch Keyboard is shown even when the check box is cleared.
L00025585 Unable
to connect InSQL 8.0 or InSQL 7.1 to InTouch 7.11 when InTouch is running on a
Windows XP SP2 computer.
L00025933 If
there are a large number of alarms in the database, InTouch will only display
the oldest alarms in the AlmDbViewCtrl and display $NewAlarm for the rest.
L00026422 The
AlterWWALMDB.exe utility crashes after it fails to "Test Connection".
L00026453 Uninstall
does not remove the /Programs/Wonderware FactorySuite/InTouch/Alarm DB Alter
shortcut.
L00026454 Unable
to use the AlmDbViewCtrl for event history.
L00026587 In
the Japanese version of InTouch, the AlmDbViewCtrl property dialog box’s
"Refresh", "sort", and "sort" check boxes should
be “Refresh", "Sort", and "Reset”.
L00026588 In
the Japanese version of InTouch, Display Modes of the AlmDbViewCtrl property
dialog box are user editable.
L00026879 The
status bar on AlmDbViewCtrl displays incorrect information: "Displaying 1
thru 2000 of 1000 records".
L00027371 In
a workgroup environment, WindowViewer crashes after switching users on a
Windows XP computer.
L00027697 In
the Simplified Chinese version of InTouch, there are untranslated strings in
Alarm DB View and Alarm DB logger.
L00027800 Read-only
I/O tags are writeable using Indirect Tags.
L00028153 When
you open an application created in an English version of InTouch in a Japanese
WindowMaker, some characters' font size changes.
L00028170 In
AlmDbViewCtrl of the Simplified Chinese version of InTouch, the default font
does not show.
L00028309 Attempting
to display historical data in a trend when the selected range spans a Daylight
Savings Time transition loses data.
L00028900 Terminal
Services client connects to a server and runs WindowViewer in a different screen
resolution than that of the server application, and the font size is not
adjusted to the client environment when set to Japanese as its default language
or when using a Japanese OS.
L00028982 When
InSQL data is set for Greenwich Mean Time and the trend is set to plot for one
hour, two hours of data is shown during the Daylight Savings Time change.
L00029247 SPC
Limits Wizard does not create tags and errors are logged to the Wonderware Logger
after clicking on suggest and OK button.
L00006191 Duplicate shortcut keys in SQL Access Manager/Table
Template Configuration dialog box in the German version of InTouch 7.11.
Problem:
In the German version of InTouch, the "Element löschen" and
"Länge" controls had the same keyboard shortcut (L). Keyboard
shortcut “S” is now assigned to löschen.
L00009846 3Dtext and text object in Japanese version of
InTouch 7.11 P03 (double-byte code) is displayed rotated or using incorrect
font.
Problem:
Times New Roman font is rotated 90 degrees, and Terminal font is incorrect.
L00011536 In the French version of InTouch 7.11, an item
cannot be added to the Symbol Factory object library.
Problem:
In previous versions of the Symbol Factory when used with a localized version
of InTouch (e.g. French, German InTouch...), users could not add their own
InTouch objects to the library. The user would receive the error message
"You must first select an InTouch object" when trying to add an
object, even though the object was, in fact, selected. This has been fixed.
Also, if a new library was created and
then an item added, it succeeds but the object is blank in the library.
All INI file operations were modified to
use the Registry instead. This allows the Symbol Factory to operate properly
under Windows XP if a restricted-access user is logged on. Three new Registry
entries and a help file for Symbol Factory were introduced in this patch.
Symbol Factory help file was changed from WinHelp() to HtmlHelp(), so now the
Symbol Factory uses SymFac.chm instead of SymFac.hlp. SymFac.chm is in the same
folder as SymFac.dll.
L00012425 AlarmDBView Control takes a long time to get
populated with data if database contains a large number of records.
Problem:
If the WWALMDB has 200,000+ records in it, and you open the AlarmDBView Control
to query the alarms from the last 5 minutes, it takes 110 to 180 seconds (2-3
minutes) to populate even if no records are returned. Running the same query
from Query Analyzer also has the same delay. Delay is greatest when SQL Server
is on another node.
L00014196 The "Invalid floating pt value"
error message box is not modal (is hidden).
Problem:
When entering an invalid floating point value (for example, entering a comma
instead of decimal point in an input animation link), the error message window
that is displayed may be hidden. If there is a popup type window covering the
message, it remains hidden, waiting for the user to click OK. If the ALT TAB
key combination is disabled, there is no way to access the error message.
L00014738 SuperTags are not shown in alphabetical order,
but are in the order in which they were created.
Problem:
When selecting tags for pens of Trend object, the SuperTags are not shown in
alphabetical order, but are in the order in which they were created.
L00014778 Logger shows Mutex errors after a few days of
running InControl.
Problem:
Run InTouch application, InControl application, and IO Server in the same node.
After 2 to 3 days, the following errors appear in the logger:
2003/05/01 09:47:44.450/-0240:0264/UNKNOWN /Unable to access stats memory (two
timeouts on mutex)
2003/05/01 09:47:44.450/-0458:0454/UNKNOWN /Unable to access stats memory (two
timeouts on mutex)
2003/05/01 09:47:45.452/-03BC:03EC/UNKNOWN /Unable to access stats memory (two
timeouts on mutex)
The process value in the logger indicates that RTEngine, mbenet, and view all
get the mutex errors. After the initial group of errors, RTengine reports Mutex
errors continuously every couple of minutes. Restarting RTEngine causes the
errors to stop.
L00015140 Wizard is not retaining animation links
Problem:
A new object is placed by using the Place Wizard command. The Wizard Generator
(for creating wizards) has a Visibility check box that links to a tag. The
check box is cleared after breaking the wizard cell, double-clicking on
Visibility, and then clicking on the Cancel button.
L00015163 "Not enough space for string - new name
too long?" error message is displayed when you attempt to convert an
InTouch application to another screen resolution.
Problem:
"Not enough space for string - new name too long?" error message is
displayed when you attempt to convert an InTouch application that has a script
longer than 32,000 characters to another screen resolution. The new maximum
limit is 32,700 characters. For any script that has more than 32,700
characters, including spaces and line breaks (each line break = 2 characters),
the script will be truncated after importing or conversion.
L00016049 There is a difference in the text display
block between single and double byte characters. Double byte character fields
are much wider that the text included.
Problem:
A font display problem exists in Japanese version of InTouch. There is a
difference in the text display block between single and double byte characters.
Double byte character fields are much wider that the text included. Some
Japanese fonts could not display all characters on window.
L00016475 Inconsistent message dialog boxes are
displayed when using illegal characters along with hex numbers and/or tagnames
in a script.
Problem:
Inconsistent message dialog boxes are displayed when using illegal characters
along with hex numbers and/or tagnames in a script.
L00016753 Unexpected results occur when setting width of
pen in 16-pen trend during design time.
Problem:
There were two different methods for setting the width of a pen on the 16-pen
trend during design time. One method was in the upper gray area of the
configuration window in the frame titled Current Pen. The second method was
using a column along the right side of the grid with the pens, tags and other
settings. When using the first method, you must select the Pen number in the
Current Pen area, then its width, and then click Done to set the width of all
the pens. Then, you must select the next pen in the configuration window. This
methodology has changed to the following: at run-time, all pens will display at
the width of their design time specifications and the widths can be changed
using the dialog box and through any supported scripts functions.
L00016921 Fast switching from WindowMaker to
WindowViewer causes the following error messages in WWLogger:
AlarmBuf /!CBThrd_Dispatch_Timer1Sec PostThreadMessage failed - Error: (1444) -
Invalid thread identifier.
AlarmBuf /!PostThreadMessage(0) (thread-id=0x724) failed
(AlmMgr=0x710,0x648,0x724).
Problem:
When WindowViewer is starting up and the timer message is in place but the
callback thread is still not fully initialized, this problem occurs. The timer
message implemented by AlarmManager tries to post the message to the callback
thread, which is not yet initialized.
L00016991 Fonts display is 'blotchy' in WindowMaker when
using 'Smooth edges of screen fonts' setting. Fonts in WindowViewer are
displayed OK.
Problem:
Fonts display is “blotchy” in WindowMaker when using 'Smooth edges of screen
fonts' setting. Right-click on the desktop, select property, select Effects
tab, and then select the 'Smooth edges of screen fonts" check box. Text in
WindowMaker has holes or white space around the font edges. This “blotchy”
appearance is not displayed in WindowViewer.
L00017565 Alarm Purge/Archive shuts down when user
clicks OK.
Problem:
Alarm Purge/Archive shuts down when user clicks OK. The label OK is misleading
and has been changed to Close.
L00017621 Tag assignment in 16-pen window results in
"Tagname.x is in an out-of-date format or corrupted" and the
application cannot be opened again.
Problem:
Assign tag to a couple of 16-pen charts by selecting it from the tag dictionary
dialog box. Close the window, log off the application, and shut down using the
Action script in a pushbutton. When you restart WindowViewer the following
error message is displayed: "Tagname.x is in an out-of-date format or
corrupted". Also the application cannot be opened again.
L00017790 The Edit Custom Color dialog box, when opened from
the 16-pen trend control dialog box, causes WindowMaker to crash.
Problem:
The Edit Custom Color dialog box, when opened from the 16-pen trend control
dialog box, causes WindowMaker to crash.
L00017809 X or Y location of window changes when
reducing the width or height of the window manually and without saving and
closing.
Problem:
X or Y location of window changes when reducing the width or height of the
window manually and without saving and closing. The entire window moves left
instead of being resized. The top-left of the window is no longer at (4,4), but
rather is relocated to the left out of the visible pane (the white area).
L00017828 Cannot
change a double byte font in AlarmDBView control.
Problem:
Cannot change a double byte font in AlarmDBView control. It resets to default
font.
L00017865 Unselecting all radio button settings in
Discrete Value Pushbutton can crash WindowViewer.
Problem:
If none of the radio buttons (Direct, Reverse, Toggle, Reset, and Set) are
selected for Discrete Value Pushbutton when assigning a discrete tag to a
rectangle, clicking on the object in run-time can crash WindowViewer.
L00017867 In the French version of InTouch, the Set/Reset
Display button has incorrect translation for Open.
Problem:
In the French version of InTouch, the Set/Reset Display button has incorrect
translation for Open.
L00017877 When a new application and a new window are
created, printing the window disables WindowMaker after the printout.
Problem:
When a new application and a new window are created, printing the window
disables WindowMaker after the printout. Note: If you close the window first,
then open it again before printing, WindowMaker is not disabled.
L00017904 It is possible to clear all radio buttons
(unchecked) in the animation links, such as Object Height/Width and the Percent
Fills, which causes WindowMaker to crash.
Problem:
It is possible to clear all radio buttons (unchecked) in the animation links,
such as Object Height/Width and the Percent Fills. WindowMaker crashes when you
double-click on one of the Alarm Type radio buttons for Line Color/Analog Alarm
or Fill Color/Analog Alarm animation link.
L00017934 In the 16 Pen Trend environment, switching
between WindowMaker and WindowViewer and then clicking on the scooter (or F2)
will increase its size.
Problem:
In the 16 Pen Trend environment, switching between WindowMaker and WindowViewer
and then clicking on the scooter (or F2) will increase its size.
L00017936 When creating a new WWALMDB, Alarm DB Logger
does not set any permissions for WWUser / WWPower / WWAdmin users for the *Ex
views; hence those accounts cannot be used for alarm retrieval using Alarm DB
View.
Problem:
When creating a new WWALMDB, Alarm DB Logger does not set any permissions for
WWUser / WWPower / WWAdmin users for the *Ex views; hence those accounts cannot
be used for alarm retrieval using Alarm DB View.
L00017944 In the 16 Pen Trend environment, Pen Trend
goes blank in the run-time if trend is stopped (Stop button) while the
Configuration dialog box is opened.
Problem:
The contents of the Pen Trend will disappear even after the Configuration
dialog box is closed. Only clicking the Play button will make data appear
again.
L00017975 In the French version of InTouch, the All and
Historical options on the Query tab in Alarm DB Logger Manager are not
translated.
Problem:
In the French version of InTouch, the All and Historical options on the Query
tab in Alarm DB Logger Manager are not translated.
L00017979 In the Japanese version of InTouch, creating
an application path with certain Japanese characters and deleting the application
from the list causes the InTouch Application Manager to not find the
application.
Problem:
In the Japanese version of InTouch, creating an application path with certain
Japanese characters and deleting the application from the list causes the InTouch
Application Manager to not find the application.
L00017982 In the Japanese version of InTouch, the All
and Historical options on the Query tab in Alarm DB Logger Manager are not
translated.
Problem:
In the Japanese version of InTouch, the All and Historical options on the Query
tab in Alarm DB Logger Manager are not translated.
L00017994 Alarm DB Logger Manager hangs if the Alarm
database was not created and you click Start.
Problem:
Alarm DB Logger Manager hangs if the Alarm database was not created and you
click Start. Both the Start and Settings buttons are disabled.
L00017999 Not able to log alarms as user wwPower in the
Alarm DB Logger.
Problem:
Not able to log alarms as user wwPower in the Alarm DB Logger. InTouch modified
to give permissions to user wwPower. Existing customers must click either
Update Permissions or Alter Database button to resolve this issue.
L00018231 In Japanese version of InTouch, there are
corrupted fonts in WindowMaker dialog boxes using Japanese local settings.
Problem:
In Japanese version of InTouch, there are corrupted fonts in WindowMaker dialog
boxes using Japanese local settings.
L00018283 Alarm DB Logger will not function if there are
more than 16 lines of queries in its Alarm Query configuration.
Problem:
Alarm DB Logger will not function if there are more than 16 lines of queries in
its Alarm Query configuration. The new limit for the query text field is 1024
characters. If there is more than one line in the query window, two hidden
characters must be added to the total characters for each line. For example, if
each line in the query is 32 characters long, the total number of lines in the
query can be calculated by this equation: 1024 / (32 + 2) = 30 lines.
L00018284 The sharing of the Wonderware license folder
when InTouch is started is a security concern. Provide the ability to halt the
sharing of this folder.
Problem:
User needs to follow these steps:
1. Create
a new "License.ini" file in the \\Program Files\FactorySuite\Common
folder.
2. Type
both of the following lines into the "License.ini" file:
[License]
CreateLicenseShare=0
3. Remove
share from the "\\Program Files\FactorySuite\Common\License" folder
by selecting "Do not share this folder" in the sharing properties
tab.
4. Click
Apply and OK buttons.
L00018294 After installation of InTouch 7.11 Patch 06,
Alarm DB Logger no longer logged alarms to the database.
Problem:
After installation of InTouch 7.11 Patch 06, Alarm DB Logger no longer logged alarms
to the database. Some computers are OK while others demonstrate the problem.
The alarms are buffered into the queue. If the user tries to stop the logging,
the message "Flushing alarms in buffer.." is displayed and the logger
hangs at 100% CPU usage.
L00018335 In the French, German, and Japanese versions
of InTouch, the word “None” in the following error message is translated:
"Change Password for Operator None".
Problem:
In the French, German, and Japanese versions of InTouch, the word “None” in the
following error message is translated: "Change Password for Operator
None".
L00018519 Enhancement to the 16-pen trend functionality
to eliminate occasional double thick line.
Problem:
Drawing mode from the maximum value of one-data-collection time frame to the
minimum value of the next is requested, instead of from average to average.
Resolution: The modification contains two drawing modes.
To enable the Min-Max drawing algorithm, you must type the following entry in
the InTouch.ini file:
[InTouch] 16PenTrendDrawMode=1
If this algorithm is enabled
(16PenTrendDrawMode=1), the Log Viewer will display "16-Pen Trend Drawing
Mode= Min - Max". Otherwise it will display "16-Pen Trend Drawing
Mode = Averaging."
If the Min-Max INI entry is missing or the following entry is found in the InTouch.ini
file, the software will use the existing drawing algorithm:
[InTouch] 16PenTrendDrawMode=0
L00018566 WindowViewer crashes on initialization of a
HistData wizard.
Problem:
WindowViewer crashes on initialization of a HistData wizard.
L00018756 The Cross Reference utility’s Save As function
does not write the tag link locations to the CSV file as documented in the
InTouch Users Guide.
Problem:
The Cross Reference utility’s Save As function does not write the tag link
locations to the CSV file as documented in the InTouch Users Guide.
L00018790 In the Japanese version of InTouch, the color
fill animation link is the opposite of what is true.
Problem:
In the Japanese version of InTouch, the color fill animation link is the
opposite of what is true.
L00018838 Use of the DialogValueEntry or
DialogStringEntry causes a crash when users’ IDEA script function is only used
in Application On Shutdown script.
Problem:
The sequence of the function call causes memory corruption in MFC42.DLL. This
resulted in the crash after the WindowViewer exited.
L00018906 In Historical trending mode, 16-pen trend, the
start time of the trend is the current time. This problem results in an empty
future trend.
Problem:
In Historical trending mode, 16-pen trend, the start time of the trend is the
current time. This problem results in an empty future trend.
L00019008 In the Japanese version of InTouch, the error
"can not open tagname.x" is displayed after importing windows
containing the password wizard.
Problem:
When importing a window that contains a password wizard, which is not
configured, WindowMaker crashes with the error "can not open
tagname.x".
L00019096 Changing the font properties does not always
provide the same results.
Problem:
Changing the font properties does not always provide the same results,
depending on the order and tools used to change the font. Text objects that
have an appearance show the same font attributes when checking the font
properties.
L00019104 The Log file *.ALG does not include the Alarm
Comment when the ACK or .ACK was used, or when the almAck comment was blank
(empty string).
Problem:
The Log file *.ALG does not include the Alarm Comment when the ACK or .ACK was
used, or when the almAck comment was blank (empty string).
L00019196 Unreadable characters displayed in the keypad
(a dash "-" looks the same as period ".").
Problem:
When the keypad is called using DialogValueEntry, a dash "-" appears
as a period ".".
L00019283 No longer able to use the AlarmDBView ActiveX
in Visual Basic after installation of InTouch Patch 06.
Problem:
Prior to installation of InTouch Patch 06, users were able to create a VB
application on a computer with InTouch installed, drop the AlarmDBView ActiveX
onto a form, and right-click to get to the properties.
L00019352 Using local variables in GetNodeName() will
display the following error message: "Must have writeable message variable
for this argument to GetNodeName".
Problem:
Using local variables in GetNodeName() will display the following error
message: "Must have writeable message variable for this argument to
GetNodeName". For instance:
DIM LocalMsg AS MESSAGE;
GetNodeName(LocalMsg, 15);
LogMessage("LocalMsg: " + LocalMsg);
On the attempt to validate or save the script,
the error message is displayed.
L00019410 The Hardware/Software flow control settings
are not preserved in the Alarm Printer.
Problem:
Under Port Configuration on the Printer Tab, change the selection for Flow
Control from None to Hardware, click Apply and then OK. Reopen Port
Configuration and note that Flow Control has been set back to the default value
(None).
L00019431 WWRequest does not function after a failed
connection.
Problem:
WWRequest does not function after a failed connection.
L00019440 Failed to create view in wwAlmDB by using
AlterWWALMDB.exe.
Problem:
Failed to create view in wwAlmDB by using AlterWWALMDB.exe.
L00019460 Crash related to special characters in the
MSSQL DB; no crash if unused tags are deleted from the InTouch application.
Problem:
Crash related to special characters in the MSSQL DB; no crash if unused tags
are deleted from the InTouch application. WWLogger message is the following:
"/PTACC /Attempt to set string value having more than 131 characters.
String truncated."
L00019569 After disabling and enabling InSQL, the analog
tag does not update. InSQL shows Null until the tag changes value.
Problem:
After disabling and enabling InSQL, the analog tag does not update. InSQL shows
Null until the tag changes value.
L00019699 During UNACK_RTN events, when ACKed on a
client of a Hot Backup pair, the ACK is not sent to the backup computer.
Problem:
During UNACK_RTN events, when ACKed on a client of a Hot Backup pair, the ACK
is not sent to the backup computer.
L00020058 DAO querying a Hot Backup pair does not detect
that WindowViewer is shutdown on the primary provider when the Alarm DB Logger
is also running on the primary provider.
Problem:
DAO querying a Hot Backup pair does not detect that WindowViewer is shutdown on
the primary provider when the Alarm DB Logger is also running on the primary
provider.
L00020170 AlterWWALMDB.EXE in InTouch Patch 06 fails
when used with Microsoft SQL Server 7.0 SP3. Error message is the following:
“Failed to Create v_AlarmEventHistoryEx1 view”. This function works OK on SQL
Server 2000 and MSDE.
Problem:
AlterWWALMDB.EXE in InTouch Patch 06 used syntax that is not supported in SQL
Server 7.0.
L00020214 Tagname Dictionary allows
"Ctrl+Enter" to be typed in the Alarm Comment field of Discrete tags,
which results in an embedded CRLF that causes problems for DBDump/DBLoad.
Problem:
Tagname Dictionary allows "Ctrl+Enter" to be typed in the Alarm
Comment field of Discrete tags, which results in an embedded CRLF that causes
problems for DBDump/DBLoad. Disable the Ctrl+Enter key sequence in the Alarm
Comment field so a new line cannot be inserted.
L00020312 Alarm DB Restore stops restoring when it
encounters comments in the comment file that contain a comma.
Problem:
Alarm DB Restore stops restoring when it encounters comments in the comment
file that contain a comma.
L00020460 WWDlg_ScriptEdit returns a modified script
when the user clicks Cancel. There is no way to know whether the user clicks OK
or Cancel to close the Script Editor.
Problem:
WWDlg_ScriptEdit returns a modified script when the user clicks Cancel. There
is no way to know whether the user clicks OK or Cancel to close the Script
Editor.
L00020552 Unable to write to the ROCpct dot field from
an IDEA application.
Problem:
Unable to write to the ROCpct dot field from an IDEA application.
L00020559 Windows Textbox only displays 130 characters
of a 131-character-long tag.
Problem:
Windows Textbox only displays 130 characters of a 131-character-long tag.
L00020610 A gap is displayed on the right side of a
historical trend during the fall back time change in October for Greenwich time
zone when it is set to auto adjust for time change.
Problem:
Issues in historical logging and retrieving: InTouch has been modified so that
no data is lost during transitions between standard time and daylight savings
time.
L00020697 Enhancement request: New feature to be able to
bypass the creation of placeholders (based on the existence of tags in the
tagname dictionary) when windows and scripts are imported from one application
to another.
Problem:
When windows and scripts are imported from one InTouch application to another,
placeholders are used preceding each tag. This causes a problem when there are
many tags used in windows/scripts due to the limitation in the number of
placeholders (approx 4095). The user cannot import big applications, but rather
must import chunks of windows at a time to ensure that the number of
placeholders is not exceeded.
A new feature was introduced to the InTouch 7.11 Patch 07 that allows users to
import windows directly from one InTouch application into another through the
File - Import menu in WindowMaker. There are several options and limitations in
the new feature: