InTouch^® 9.5 Patch 02 and Patch 03 ReadMe

This ReadMe file describes the defects fixed in these patches and known issues.

InTouch® 9.5 Patch 03  -  Fixed Defects and Known Issues

InTouch® 9.5 Patch 02  -  Fixed Defects and Known Issues

InTouch^® 9.5 Patch 03  -  Fixed Defects and Known Issues

We strongly recommended that you exit all Wonderware^® programs, including executable (.exe) files and services, before you install this patch.

This InTouch 9.5 Patch 03 build has primarily been tested on:

·          Windows Server 2003 Standard Edition R2

·          Windows XP Professional with SP2

·          Windows 2000 Server with SP4

·          MS SQL 2005 with SP1

·          Internet Explorer 6.0 SP1

*          If you want to install the InTouch 9.5 Patch 03 from a CD, you must follow these instructions:

      For InTouch:

·          The CD volume name must be Patch.

·          Copy the file Setup.msp to the root of the Patch CD.

 

      For InTouch for Terminal Services:

·          The CD volume name must be PatchTS.

·          Copy the file SetupTS.msp to the root of the PatchTS CD.

 

If the CD is named something other than Patch or PatchTS, the patch installation from the CD will not be successful.

 Note: NetDDE is not supported on Windows XP SP2 or Windows 2003 and later operating systems.

The Microsoft Windows XP SP2 and Windows Server 2003 R2 operating systems introduce several security technologies, including disabled NetDDE, enhanced Windows firewall, and a reduced RPC attack surface. These enhancements affect the uses of NetDDE, Log Viewer, and SuiteLink protocols in InTouch.

If InTouch must run on the Windows XP SP2 or Windows Server 2003 R2 operating systems, the patch installation runs an operating system (OS) configuration utility. This utility opens specific ports that enable NetDDE and adds Wonderware SuiteLink and Wonderware Log Viewer to the firewall exception list.

InTouch does not work properly on a Windows XP SP2 or Windows Server 2003 R2 computer if you do not run the OS configuration utility during installation.

During the InTouch patch installation, select the appropriate check box to allow the installation to run the utility.

Resolved Issues

The following defects were fixed for this patch release. Click on the defect number for a more detailed description of the problem.

L00049742 Visibility for the text fails and some of the text is left showing when a language different than 1033 is selected.

L00050070 The Alarm DB Purge/Archive Utility crashes at startup when it is configured to start as a service.

L00051263 Importing the language text file changes the content of the translated text.

L00051338 The Modify button does not work in the Configure SPC Database dialog box.

L00052195 ActiveX events do not run while WindowViewer is minimized.

L00052211 Provide configurable wwHeap in the memory range up to 1024 MB, with a default of 256 MB.

L00052786 When you switch languages, the translated text is not shown correctly.

L00052813 I/O type tagnames are activated if the tagnames are part of real-time trends, even if the window containing the real-time trend is not being shown, and the Only update when in memory check box for the trend is selected.

L00052980 Unable to create the alarm database on SQL Server 2005.

L00053143 InTouch for Terminal Services is not re-using the AnonymousEngineID when it is restarted: CNmxAdapter::Initialize - GetAnonymousEngineID FAILED.

L00053417 Unable to create Detail Mode of Tables on server with case sensitive database collation, such as Latin1_General_BIN.

 

Back to Top

Detailed Descriptions for Resolved Issues

L00049742 Visibility for the text fails and some of the text is left showing when a language different than 1033 is selected.

Problem:
Switching between languages leaves some text showing on the display.

Back to Resolved Issues

L00050070 The Alarm DB Purge/Archive Utility crashes at startup when it is configured to start as a service.

Problem:
The Alarm DB Purge/Archive Utility crashes at startup when it is configured to start as a service and the purge schedule is set to "weekly" or "monthly."

Back to Resolved Issues

L00051263 Importing the language text file changes the content of the translated text.

Problem:
Importing the language text file changes the content of the translated text without the file being opened with an editor.

Back to Resolved Issues

L00051338 The Modify button does not work in the Configure SPC Database dialog box.

Problem:
The Modify button does not work in the Configure SPC Database dialog box after the database is saved and verified. Clicking on the Modify button does not produce any results.

Back to Resolved Issues

L00052195 ActiveX Events do not run while WindowViewer is minimized.

Problem:

• ActiveX events stop during and after WindowViewer is minimized.
• Every event is logged as an info message by the ocxgot module, causing the Log Viewer to fill up. The following message is logged: "The ActiveX Object:EventTest1::(Is not initialized, event can not be triggered now)"

This behavior is different than that of InTouch 9.0 Patch 02 and prior releases.

Back to Resolved Issues

L00052211 Provide configurable wwHeap in the memory range up to 1024 MB, with a default of 256 MB.

Modifications to wwHeap capabilities:

1.      You can configure range of the Wonderware Memory Manager (wwHeap) in 1 MB increments up to 1024 MB. If you set the range to less than 32 MB, a warning is written to the Log Viewer. Any value greater than 1024 MB is set to 1024 MB. wwHeap has a memory range default of 256 MB. This range is configured by a registry entry. You cannot change the range until wwHeap is completely reset, which means that all programs using wwHeap have been stopped.

 

2.      You can choose whether wwHeap should start its search for free memory maps at the zero index or the most recently used index. This allows programs with smaller memory requirements to 'conserve' memory addresses, while those with larger memory requirements can be optimized to find available memory more quickly. The default behavior is to start the search at the zero index each time, as this is the original wwHeap behavior. You configure the setting is using the registry. You cannot change the value until wwHeap is completely reset, which means that all programs using wwHeap have been stopped.

 

3.      When wwHeap is first started, it can read an optional .INI text file containing a list of reserved memory addresses into which it should never allocate memory. This helps to avoid heap share allocation errors with third-party modules that are not necessarily loaded at system startup. The .INI file's path is read from the registry.

 

The wwHeap configuration information is always written to the Log Viewer at least once when wwHeap is first accessed by any program. This provides a record of the wwHeap configuration for diagnostic purposes.

The default settings for wwHeap:

• Memory range: 256 MB

 

• Starting address: 0x21000000

 

• Memory Conservation: Enable - Search for free memory starting at the beginning of the memory range

 

• Memory reservation .ini file: DO NOT process .ini file

 

The settings for wwHeap:

• Memory range: Create a DWORD registry entry with the value 'MemoryRange' under the following key:
  HKEY_LOCAL_MACHINE\Software\Wonderware\wwHeap
  Set it to the number of megabytes (MB), from 1 to 1024

 

• Starting address: Create a DWORD registry entry with the value 'BaseOffset' under the following key:
  HKEY_LOCAL_MACHINE\Software\Wonderware\wwHeap
  Set it to the desired memory base offset. The start and end memory addresses are written to the Log Viewer.

 

• Memory Conservation: To enable the efficient free-memory search algorithm, create a DWORD registry entry with the value 'ConserveMemory' under the following key:
  HKEY_LOCAL_MACHINE\Software\Wonderware\wwHeap
  Set the value to:
• 0 - efficient free-memory search (to cycle through the list)
• 1 - conserve memory (always start search at beginning of list)

 

• Memory reservation .ini file: To enable the memory reservation, create a REG_SZ (string) registry entry with the value 'ReserveFilePath' under the following key:
  HKEY_LOCAL_MACHINE\Software\Wonderware\wwHeap
  Set the value to the full file path of the .ini file containing the desired memory reservation entries.
  
  Create an .ini file with any name with the following content:
  Any entries lower than the memory range or greater than the memory range are ignored.
  
  [ReserveMemory]
  ; reserve memory range from 0x25000000 to 0x33450000
  MEM00001=0x25000000-0x33450000
  ; reserve memory range starting at 0x45000000 for 8 - 64K blocks
  MEM00002=0x45000000;8
  ; reserve memory range starting at 0x50000000 for 16- 64K blocks
  MEM00003=0x50000000;16
  ; stop list processing
  MEM00004=DONE

 

Back to Resolved Issues

L00052786 When you switch languages, the translated text is not shown correctly.

Problem:
When you switch languages, the translated text is not shown correctly.

Back to Resolved Issues

L00052813 I/O type tagnames are activated if the tagnames are part of real-time trends, even if the window containing the real-time trend is not being shown, and the Only update when in memory check box for the trend is selected.

Problem:
An application with many real-time trends that was migrated from a previous version of InTouch shows much higher activity in the DDE I/O Server. The tagnames that are part of real-time trends are activated as soon as the application is started, even if the window even if the window containing the real-time trend is not being shown, and the Only update when in memory check box for the trend is selected.

Back to Resolved Issues

L00052980 Unable to create the alarm database on SQL Server 2005.

Problem:
Unable to create the alarm database because creation of the stored procedure 'WWAlmDBUserCreate' is failing.

Alarm Database Manager tries to create the 'WWAlmDBUserCreate' stored procedure to create the logins for the users wwAdmin, wwPower and wwUser in the Master database. However, if the stored procedure 'WWAlmDBUserCreate' already exists in the Master database, then the users cannot be created. Possible reasons for the stored procedure 'WWAlmDBUserCreate' already existing in the Master database are:

• the stored procedure 'WWAlmDBUserCreate' in Master database has been created for some external use
• the creation of the alarm database failed due to security reasons or any other reasons
• the creation of the alarm database failed while upgrading from an older version of InTouch

In all these scenarios, Alarm DB Logger does not delete the stored procedure that already exists in the Master database and the database creation fails.

Back to Resolved Issues

L00053143 InTouch for Terminal Services is not re-using the AnonymousEngineID when it is restarted: CNmxAdapter::Initialize - GetAnonymousEngineID FAILED

Problem:
Logging on to and logging off from the InTouch for Terminal Services console using a remote desktop or thin client connection without closing WindowViewer causes a decrease of the available AnonymousEngineID. When the number of AnonymousEngineID reaches a certain limit, the thin clients stop updating remote referenced tags from the Industrial Application Server.

Back to Resolved Issues

L00053417 Unable to create Detail Mode of Tables on server with case sensitive database collation, such as Latin1_General_BIN.

Problem:
Creating an alarm database with SQL Server 2000 SP3a configured with a collation that is case sensitive (such as Latin1_General_BIN) gives an error message "Unable to create Detail Mode of Tables" and creates only one view, which is v_AlarmHistory.

Back to Resolved Issues

Back to Top

 

InTouch^® 9.5 Patch 02  -  Fixed Defects and Known Issues

Resolved Issues

The following defects were fixed for this patch release. Click on the defect number for a more detailed description of the problem.

L00033431 After converting the WWALMDB alarm database from InTouch7.11 P06 to a later version of InTouch, every time the Alarm DB Logger utility is started, it tries to convert the database again.

L00034213 After opening WindowMaker in full screen mode, switching from WindowMaker to the desktop and then switching back to WindowMaker, WindowMaker is in the Task Manager processes list, but not accessible.

L00040139 Unable to enter 31 characters for the Eng Units field in the WindowMaker Tagname Dictionary.

L00041058 Need a way to delete a “disable the right-click delete menu” for SPC Charts while maintaining the ability to perform modify and corrective action of existing samples.

L00041238 Historical Trend Pens are lost or mixed up on a NAD Client when clients are notified via the Notify Clients function, or when the client application is restarted.

L00041286 Unable to delete or modify an SPC sample on other charts after deleting or modifying a sample on a different chart in the same window.

L00041433 The Alarm DB View control attempts to validate database connection as soon as the .ServerName property is set. This results in error messages, if the .UserID field was not set beforehand.

L00041448 The halo that follows the object geometry does not show properly.

L00041564 After TSE clients failback and then the engine fails back to the primary node, alarm queries in the AlarmViewer control do not connect to the local server’s InTouch alarm provider.

L00041626 If a remote tag reference is used in the fail-over expression, WindowViewer displays assertion error in file dbconvrt.c Line 39. The assertion error dialog box is continuously displayed.

L00041661 Alarm Restore rolls back when an apostrophe (') is used in a comment field.

L00041710 Importing supertags is not working correctly.

L00043718 Value display animation link behaves differently in languages other than English during run-time language switching.

L00043798 "Out of Disk Space" error appears when saving a window containing an instance of a large SmartSymbol.

L00043972 Task Manager not available if the Task Manager is disabled by using the EnableDisableKeys(1,1,1) function, then re-enabled with the same function.

L00044014 Error message ''Super tag has exceeded max limit. Cannot add all member tags.'' appears.

L00044100 Double-clicking a SmartSymbol in WindowMaker leaks memory, even if nothing is done in the SmartSymbol Properties page. The Task Manager VM Size column continues to increase every time the SmartSymbol is double-clicked.

L00044199 New features are added to the SPCPro.

L00044226 The Commit Edit function of SmartSymbol leaks 90 MB of memory in the wm.exe process.

L00044275 Calling Recipeload periodically causes WWHeap errors and immediate shutdown of WindowViewer.

L00044312 Language switching: The font size of text is changed even if the size in the dictionary file matches the current font size.

L00044409 MSSQL 2005: Unable to create either Detailed or Consolidated tables using Alarm DB Logger.

L00044425 Alarm DB Purge / Archive utility only purges one time if configured to run as a Service.

L00044765 Unable to dump an InTouch Database with DBDump.exe if Secondary source for Access Name is enabled.

L00044795 Changing the window status of WindowViewer from Minimize to Maximize causes loss of encryption.

L00044870 Memory leaks when the "Retry Initiates" parameter under WindowViewer Configuration Utility/General Tab/IO is set to a value larger than zero, references to the galaxy are active in the application and the platform has not been deployed.

L00044877 Attempt to create a new Supertag from a Supertag that was created by a deleted Supertag causes the error message “INTSPT - Error Reading Entry” and corrupts the Tagname dictionary.

L00045386 Remote tags using redundant server do not re-initialize if the window containing the link is closed.

L00045673 Need a way to determine if a sample was deleted to avoid a rejected poke and update problems after setting the Selection to a deleted Sample Number.

L00045678 [Internationalization] WindowMaker crashes and application is destroyed after several particular operations on SQL access Bind List Configuration.

L00045705 "Advise all items" check box selection for the secondary source access name becomes unselected after WindowMaker restarts.

L00045766 After editing ActiveX properties, changes are not saved if the dialog box is opened with Shift-Double-click and the "Save All Windows" button is used before switching to run time.

L00045823 Unable to connect to Log Viewer by using the '[computer name]' in SMC.

L00045867 If a window contains an SPC Histogram or an SPC Control chart and it is created in InTouch 9.5 Patch 01, WindowMaker cannot open it in InTouch 9.5 Patch02.

L00045877 The "OnMouseOver" feature only works once on an overlay or popup window, which was invoked by another window.

L00045896 SQL Server error caused by an overflow at run time due to difference of two Datetime columns.

L00046142 Shift and click to select multiple objects does not always select objects.

L00046152 #VString2 displays "Good" in WindowViewer intermittently after toggling between windows.

L00046164 The TagAccess Application (using IntouchCOM.dll v 7.1.0.2) does not work with InTouch 9.5.

L00046200 Using InSQL 7.1 as an InSQL Distributed History Provider in InTouch 9.5 results in the following error: "InSQL history provider: error message from SQL-server: invalid object name 'timezone'".

L00046242 Using comma (,) in ValueString and LimitString causes alarm restore rollback.

L00046380 If a window is opened by the "On Mouse Over" event, the Window script doesn't work for the second window if the cursor is moved.

L00046385 When converting an application, a reference in a SmartSymbol instance is changed to a placeholder with a converted application. Also you cannot use tagname dot field as an instance reference.

L00046492 Failover to secondary source (access name "enabled secondary source") causes all items to be advised.

L00046876 Quick Functions do not show up all the time in the Cross Reference Utility.

L00046881 Popup window activating the halo of the window behind it causes the application to crash.

L00046921 Opening a window with a large number of objects is slow and WindowViewer consumes 100% CPU.

L00047214 ProviderID (Nodename) not inserted in the ProviderSession table, which causes the Alarm DB Logger utility to not log any alarm and events. Also the Alarm DB Logger utility is stuck with showing the number of alarms and events in the cache.

L00047450 GetAccountStatus script function returns -5 for expiring accounts.

L00047588 SmartSymbol instance is resized (larger) if the replaced text extends past the boundaries of the selection "handles". SmartSymbol instances (not necessarily from the same template) with text that exceeds handle boundaries is also resized.

L00047846 ActiveX events stop working after WindowViewer is minimized or maximized

L00048301 A Quick Function that is called from an indirect message type tag (including indirect supertag message members) does not return a value. The same scenario with a regular message tag returns the proper value to the message tag.

L00048336 A single click on slider handle of the "Vertical Slider Mouse Release" wizard after the data changes causes the value to jump back to the previous value.

L00048377 Alarm DB Purge/Archive utility does not start in activated mode and the "Activate" button is enabled and the "Deactivate" is disabled, even when the win.ini file contains the entry "AlarmDbPurgeArchiveActivated=1".

L00048383 There is no default selection for the "Run as" option in Alarm DB Purge/Archive utility.

L00048780 WindowMaker closes unexpectedly when the width of a combo box is equal or less than the width defined for the scrollbar item on Microsoft Windows.

L00049217 Action scripts for Center or Right mouse buttons did not convert in an imported window.

L00049761 When a tag is configured to log events, a priority field allows to change the priority value and can be used to filter data in the Alarm DB View control. However, if the "Event History" mode is selected, the priority field is not available.

L00049766 The .Reference dot field does not work after being assigned to an invalid access name.

L00049917 Functions GetAlarmLogConnStatus( ) and GetAlarmLogMaxCacheCount( ) are not working.

L00050671 There is a memory leak when the Real Time Trend option "Only update when in memory" is selected.

L00050680 If an acknowledged alarm goes from HI to HIHI, both states are acknowledged with the time stamp of the last acknowledgement. This occurs only for Hot Backup pairs.

L00050713 Set the value for Disable TaskMgr, DisableLockWorkstation, DisableChangePassword, NoClose, NoLogOff to 1 in the registry. When WindowViewer is shutting down, the registry keys for the NoClose button in the TaskManager is reset to 0.

L00050905 File/Print of all scripts crashes WindowMaker with an application that is converted from InTouch 7.11.

L00050926 Changing the window status of WindowViewer (switching between WindowMaker and WindowViewer) causes loss of encryption when the input link uses the keyboard.

L00050929 Changes made to the Quick Function are not updated after using the cross reference for that Quick Function.

L00051078 Error message “WWHeap (0003) HShareInternal: Could not map @5d080000. Error 487” appears when Recipe Load and IDEA applications are both running.

L00051122 Under certain circumstances, an object can display a halo even if it is disabled.

L00051178 Remote tags are using a secondary server even though the Disable Failover option is checked and the primary server is down.

Back to Top

Detailed Descriptions for Resolved Issues

L00033431 After converting the WWALMDB alarm database from InTouch7.11 P06 to a later version of InTouch, every time the Alarm DB Logger utility is started, it attempts to convert the database again.

Problem:
After converting the WWALMDB alarm database from InTouch 7.11 P06 to a later version of InTouch, every time the Alarm DB Logger utility is started, it attempts to convert the database again. It also stays in the "Initializing" process for a long time, for example longer than 15 minutes.
The first time the database is converted the message in the SMC logger is: Database schema is updated from InTouch version 7.11 to 9.0 forma. Subsequent starts of the Alarm DB Logger utility cause the following entries in the Log Viewer: Database schema is updated from InTouch 8.0 to 9.0 format.

Back to Resolved Issues

L00040139 Unable to enter 31 characters for the Eng Units field in the WindowMaker Tagname Dictionary.

Problem:
InTouch 9.5 only allows entry of 27 characters.

Back to Resolved Issues

L00041058 Need a way to delete a “disable the right-click delete menu” for SPC Charts while maintaining the ability to perform modify and corrective action of existing samples.

Problem:
Need a way to delete a “disable the right-click delete menu” for SPC Charts while maintaining the ability to perform modify and corrective action of existing samples.

Solution:
Implemented the functionality by introducing a new check box thus allowing you to disable the right-click delete menu for SPC Charts while maintaining the ability to perform modify and corrective action of existing samples.

The new behavior is as follows:

• If you select Allow Sample Del/Modify in the previous versions then after the patch is applied, the check boxes Allow Sample Modify and Allow Sample Delete are automatically selected.
• If you do NOT select Allow Sample Del/Modify in the previous versions then after the patch is applied the check boxes Allow Sample Modify and Allow Sample Delete are NOT automatically checked.
  You can configure the Modify and Delete check boxes for the individual charts.

 

Back to Resolved Issues

L00041238 Historical Trend Pens are lost or mixed up on a NAD Client when clients are notified via the Notify Clients function, or when the client application is restarted.

Problem:
Historical Trend Pens are lost or mixed up on a NAD Client when clients are notified, or when the NAD client application is restarted. This applies only if the retentiv.h file exists in the NAD Master application and the exclusion line in the win.ini in the user profile directory does not include the retentiv.h file.

Back to Resolved Issues

L00041286 Unable to delete or modify an SPC sample on other charts after deleting or modifying a sample on a different chart in the same window.

Problem:
Unable to modify or delete an SPC sample on a different chart, after modifying or deleting a sample on another chart that is on the same window.

Workaround:
Close and then reopen the window to modify or delete samples on charts other than the original chart where a sample was modified or deleted.

Back to Resolved Issues

L00041433 Alarm DB View control attempts to validate database connection as soon as the .ServerName property is set. This results in error messages if the .UserID field hasn't been set beforehand.

Problem:
If a script is called where .ServerName is set before .UserID, two error messages appear: "UserID cannot be empty". If a script is called where .ServerName is set after .UserID, but .Password property contains a wrong password, you get a connection failure message. Setting or changing the .ServerName property field causes the Alarm DB View control to attempt to connect to the database and refresh its display.

Back to Resolved Issues

L00041448 The halo that follows the object geometry does not show properly.

Problem:
The halo that follows the object geometry does not show properly if the window coordinates are changed in WindowMaker after the object has been originally created. The new coordinates should overlap the original position of the object.

Back to Resolved Issues

L00041564 After TSE clients failback and then the engine fails back to the primary node, alarm queries in the AlarmViewer control do not connect to the local server’s InTouch alarm provider.

Problem:
After TSE clients failback and then the engine is failed back to the primary node, alarm queries in the AlarmViewer control do not connect to the local server’s InTouch alarm provider and 0% completed appears on the control.

Back to Resolved Issues

L00041626 If a remote tag reference is used in the fail-over expression, WindowViewer displays an assertion error in file dbconvrt.c Line 39. The assertion dialog box is continuously displayed.

Problem:
If you include a remote tag reference in the fail-over expression, WindowViewer displays an assertion error in file dbconvrt.c Line 39.  The assertion dialog box is continuously displayed. You must end the View process with the Task Manager.

Back to Resolved Issues

L00041710 Importing supertags is not working correctly.

Problem:
Importing the supertags csv file results in an additional number of supertags being created in the Tagname Dictionary.

Back to Resolved Issues

L00043718 Value display animation link behaves differently in languages other than English during run-time language switching.

Problem:
When switched to another language, the display turns from "59.0 Minutes" to "# 0.0 Minuten59".

Back to Resolved Issues

L00043972 Task Manager not available if the Task Manager is disabled by using the EnableDisableKeys(1,1,1) function, then re-enabled with the same function.

Problem:
Task Manager not available if the Task Manager is disabled by using the EnableDisableKeys(1,1,1) function, then re-enabled with the same function EnableDisableKeys(0,0,0).

Back to Resolved Issues

L00044014 Error message ''Super tag has exceeded max limit. Cannot add all member tags.'' appears.

Problem:
When one of the tags is opened, it generates the error ''Super tag has exceeded max limit. Cannot add all member tags.'' but it still shows all the member tags.

Back to Resolved Issues

L00044199 New features are added to the SPCPro.

Problem:
Detail:
New features are added to the SPCPro:

1.      New read/write DDE "CurrentNote" item for inserting a sample note text using DDE tag.

2.      New read only DDE item called "HistogramMean" shows the "Mean".

3.      Cp and Cpk values are calculated immediately and do not wait until the next sample before recalculating.

4.      The "Measurement per Sample" setting is moved to the product level.  Each product can have its own Measurement per Sample value.

5.      You can delete or create a "Product" during runtime.

6.      Provided the new functions SPCSetProductControlLimits(), SPCSetProductRangeLimits(), SPCSetProductSpecLimits().

7.      "Product" names length in SPC dataset is increased to 64 characters.

User Interface Changes:
    -   "MeasPerSample" edit field removed from the "Datasets" dialog box. This field is added to the "Products" dialog box.

Database Changes:
    -    Removed the column 'MeasPerSample" from the SPCDatasets table.
    -    Added this column to the SPCProducts table.
    -    Upgraded the database version for the new schema.

New DDE Items:

CalculateCpAndCpk
   Setting this item calculates the Cp and Cpk values immediately for the current sample. After the Cp and Cpk calculation, this item is reset.

CurrentNote
   Similar to existing DDE tag "CurrentComment". "CurrentNote" is string type and has Read/Write access. Setting this DDE item sets the note text for current sample on the control chart.

HistogramMean
   A read only DDE item shows the "Mean" on the Histogram.


New functions:

SPCCreateNewProduct():
   Use this function to create the new products.

Syntax:	SPCCreateNewProduct( Dataset, Product, MeasPerSample);
	Dataset	The actual Dataset name. It can be the actual string or a message tag.
	Product	The name of the product whose control limits are to be set. It can be the actual string or a message tag.
	MeasPerSample	The value to be set for the Measurements Per Sample of the product.  It can be any number or an integer tag.

SPCDeleteProduct(): This function deletes all product information from the SPC database, including the product's measurements and samples during runtime.

Syntax:	SPCDeleteProduct(Dataset, Product);
	Dataset	The actual Dataset name. It can be the actual string or a message tag.
	Product	The name of the product whose control limits are to be set. It can be the actual string or a message tag.

If the product is currently collected or displayed, it cannot be deleted and a message is logged to the Log Viewer.

SPCSetProductControlLimits():
This function sets the control limit values of a control chart for an empty product.

Syntax:	SPCSetProductControlLimits( Dataset, Product, UCL, LCL );
	Dataset	The actual Dataset name. It can be the actual string or a message tag
	Product	The name of the product whose control limits are to be set. It can be the actual string or a message tag.
	UCL	The value to be set for the UCL of the product. It can be any number or a real tag.
	LCL	The value to be set for the LCL of the product. It can be any number or real a tag.

SPCSetProductRangeLimits():
   This functions sets the limit values of a range chart for an empty product.

Syntax:	SPCSetProductRangeLimits( Dataset, Product, URL, LRL );
	Dataset	The actual Dataset name. It can be the actual string or a message tag.
	Product	The name of the product whose limits are to be set. It can be the actual string or a message tag.
	URL	The value to be set for the URL of the product. It can be any number or a real tag.
	LRL	The value to be set for the LRL of the product. It can be any number or a real tag.

SPCSetProductSpecLimits():
  This function sets the specification limit values of a control chart for an empty product

Syntax:	SPCSetProductSpecLimits( Dataset, Product, USL, LSL );
	Dataset	The actual Dataset name. It can be the actual string or a message tag.
	Product	The name of the product whose control limits are to be set. It can be the actual string or a message tag.
	USL	The value to be set for the USL of the product. It can be any number or a real tag.
	LSL	The value to be set for the LSL of the product. It can be any number or a real tag.

 

Back to Resolved Issues

L00044275 Calling Recipeload periodically causes WWHeap errors and immediate shutdown of WindowViewer.

Problem:
Calling Recipeload every 2000 ms results in errors "Info WWHEAP (0004) Out of free shared maps for memory allocation", and immediate shutdown of WindowViewer.

Back to Resolved Issues

L00044312 Language switching: The font size of text is changed even if the size in the dictionary file matches the current font size.

Problem:
If the language is changed but the font size specified in the dictionary file is still at Arial 14, the font size changes. This issue also exists for other font sizes of Arial, such as 8 and 20.

Back to Resolved Issues

L00044409 MSSQL 2005: Unable to create either Detailed or Consolidated tables using Alarm DB Logger.

Problem:
Unable to create either Detailed or Consolidated tables using the Alarm DB Logger utility. The error message "Cannot create the database" appears.
The alarm database is created, but some tables are not created within the database.
When you try to connect to this database using the Alarm DB View control, the following message appears in the Log Viewer: "The statement has been terminated. The INSERT statement conflicted with the FOREIGN KEY constraint "F_Events_ProviderSession". The conflict occurred in database "qqqq", table "dbo.ProviderSession", column 'ProviderId'. ".

Back to Resolved Issues

L00044425 Alarm DB Purge / Archive utility only purges once if configured to run as a Service.

Problem:
If configured to run as a Service, the Alarm DB Purge / Archive utility only purges the database the first day. If it is running as an application, it purges according to the schedule. However, if it is configured to run as an application after it was set as a service, it still only purges at the first schedule.

Back to Resolved Issues

L00044765 Unable to dump an InTouch Database with DBDump.exe if Secondary source for Access Name is enabled.

Problem:
Unable to dump an InTouch database with DBDump.exe if Secondary source for Access Name is enabled. The DBDump fails and the following error is shown: "Dump Failed. See Log Viewer for problems".

Back to Resolved Issues

L00044870 Memory leaks when the "Retry Initiates" parameter under WindowViewer Configuration Utility/General Tab/IO is set to a value larger than zero, references to the galaxy are active in the application and the platform has not been deployed.

Problem:
Under WindowViewer Configuration - General Tab - IO is set the "Retry Initiates" value greater than zero.
References to the galaxy are active in the application and the platform has not been deployed.

·  The virtual bytes, handlers, private bytes for the View.exe process increase every time that the application tries to reinitiate I/O conversation with the Galaxy.

·  In Log Viewer the following message is logged every time the application tries to reconnect:
"Warning WWCLINTF Unable to connect to Platform, but there is no platform deployed to this computer".

 

Back to Resolved Issues

L00045673 Need a way to determine if a sample was deleted to avoid a rejected poke and update problems after setting the Selection to a deleted Sample Number.

Problem:

SPCSampleDeleted()
   Returns the status of a sample from a SPCPro dataset.

Syntax:	Result= SPCSampleDeleted( Dataset, Product, SampleNum );
	Dataset	The actual Dataset name. It can be the actual string or a message tag.
	Product	The name of the product whose control limits are to be set. It can be the actual string or a message tag.
	SampleNum	Represents any valid sample number.  Any number or integer tagname.

 

Result	The following results may be returned:
	-1	Invalid Dataset Name, Product Name, or Sample Number.
	0	Sample is not deleted.
	1	Sample is deleted.

Example:     Result= SPCSampleDeleted( "Dataset1", "Product1", 12345 );

Back to Resolved Issues

L00045678 [Internationalization] WindowMaker crashes and application is destroyed after several particular operations on SQL access Bind List Configuration.

Problem:
Some important steps:
1) Create some memory tags.
2) In the Bind List Configuration->tagname.fieldname, double-click to call the tag picker, and select "None" and click OK.
3) Then click the "Tagname" button to select the tags created in step 1.

The Tag Picker causes WindowMaker to crash.

Back to Resolved Issues

L00045705 "Advise all items" checkbox selection for the secondary source access name becomes unselected after WindowMaker restarts.

Problem:
After WindowMaker restarts, the "Advise all items" selection changes to "Advise only active items".

Back to Resolved Issues

L00045823 Unable to connect to Log Viewer by using the '[computer name]' in SMC.

Problem:
For the Hardware-enforced DEP (Data Execution Prevention), SMC cannot connect to the Log Viewer by using the '[computer name]'.

Back to Resolved Issues

L00045867 If a window contains an SPC Histogram or an SPC Control chart and it is created in InTouch 9.5 Patch 01, WindowMaker cannot open it in InTouch 9.5 Patch 02.

Problem:
If a window contains an SPC Histogram or an SPC Control chart and it is created in InTouch 9.5 Patch 01, WindowMaker cannot open it in InTouch 9.5 Patch 02.

Back to Resolved Issues

L00045877 The "OnMouseOver" feature only works one time on an overlay or popup window, which was invoked by another window.

Problem:
1. In WindowMaker open a window called "Win1"and switch to WindowViewer.
2. Right-click the button named "Show Win2".
3. Hover over the only object in Win2, which has the script associated with the "OnMouseOver" event.

The "OnMouseOver" script is only activated the first time the mouse hovers over the object.

Back to Resolved Issues

L00045896 SQL Server error caused by an overflow at run time due to difference of two Datetime columns.

Problem:
SQL Server error caused by an overflow at run time due to difference of two Datetime columns. This error occurs when an alarm that has been in an alarm state for more than 24 days returns to normal.

Solution:
Notes: Known issue with this fix: If the database is created with the registry setting "DateDiffInSec = 1", the Alarm duration is calculated in seconds, but is shown in milliseconds in the Duration column in the Alarm DB View control. This issue will be resolved in the future release.

To use the fix in this CR, follow these following steps:

1. Apply the InTouch 9.5 Patch 02.
2. Create a DWORD value "DateDiffInSec" in the registry section HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\\AlarmLogger.
3. Set the value for DateDiffInSec to 1. This setting MUST be done before creating a new database.
4. Create a new alarm database with Alarm DB Logger Manager.

The new view v_AlarmEvenHistoryInternal2 is generated, which uses the second for Duration calculation.

To undo this, remove the "DateDiffInSec" or set the value to 0, and then create a new alarm database.

Back to Resolved Issues

L00046142 Shift and click to select multiple objects does not always select objects.

Problem:
When you hold down the shift key and click one time to select multiple objects, the objects are not always selected.

Back to Resolved Issues

L00046152 #VString2 displays "Good" in WindowViewer intermittently after toggling between windows.

Problem:
In an InTouch application with that uses an ArchestrA Galaxy and I/O, toggle between windows multiple times in WindowViewer. Various #Vstring2 links display incorrectly the value of "Good". These value display links are updated correctly after a few more toggles of the window.

Back to Resolved Issues

L00046164 The TagAccess Application (using IntouchCOM.dll v 7.1.0.2) does not work with InTouch 9.5.

Problem:
The TagAccess Application (using IntouchCOM.dll v 7.1.0.2) does not work with InTouch 9.5. Result in - Runtime Error: "Connection to Intouch Failed".

Back to Resolved Issues

L00046200 Using InSQL 7.1 as an InSQL Distributed History Provider in InTouch 9.5 results in the following error: "InSQL history provider: error message from SQL-server: invalid object name 'timezone'".

Problem:

Using InSQL 7.1 as an InSQL Distributed History Provider in InTouch 9.5 results in the following error: "InSQL history provider: error message from SQL-server: invalid object name 'timezone'"

If InSQL 7.1 is used as an InSQL Distributed History Provider, add the following entry to the [InTouch] section of the InTouch.ini file:

InSQLLowerVersion=1

Note: InTouch 9.5 is not compatible with InSQL 7.1.
If you are using InSQL 7.1 as a Distributed History Provider for InTouch 9.5, the historical trend may show a gap at right side of trend during Fall Back time change in October, and the data for the time period 12 AM to 1 AM is not logged.

Back to Resolved Issues

L00046242 Using comma (,) in ValueString and LimitString causes alarm restore rollback.

Problem:
The rollback happens when the event file is restored at the row with the comma (,) in the ValueString and StringLimit fields. If the comma is removed or replaced with other characters, the restore procedure succeeds or rolls back on other entry point where there is a comma.

Back to Resolved Issues

L00046385 When converting an application, a reference in a SmartSymbol instance is changed to a placeholder with a converted application. Also you cannot use a tagname dot field as an instance reference.

Problem:
Unable to use a tagname dot field as an instance reference in a SmartSymbol.

Back to Resolved Issues

L00047450 GetAccountStatus script function returns -5 for expiring accounts.

Problem:
The Quick Function GetAccountStatus returns -5 (i.e. Account info failed) for accounts that have expiring passwords. However, it correctly returns -2 for accounts that don't expire.

Back to Resolved Issues

L00048383 There is no default selection for the "Run as" option in Alarm DB Purge/Archive utility.

Problem:
There is no default selection for the "Run as" option in Alarm DB Purge/Archive utility.

Solution:
The default value for "Run As" is "Application" when the registry key is not found or if the key is stored initially with invalid values.

Back to Resolved Issues

L00049761 When a tag is configured to log events, a priority field allows to change the priority value and can be used to filter data in the Alarm DB View control. However, if the "Event History" mode is selected, the priority field is not available.

Problem:
When a tag is configured to log events, a priority field allows to change the priority value. This field can be used to filter data in the Alarm DB View control. However, if the "Event History" mode is selected, the priority field is not available.

Solution:

• For alarm databases created after applying InTouch 9.5 Patch 02, the "Priority" column is created in the "v_Event History" view.
• For existing alarm databases, run the AlterWWALMDB.exe utility once. This adds the "Priority" column to the v_EventHistory view.

Back to Resolved Issues

L00049766 The .Reference dot field does not work after being assigned to an invalid access name.

Problem:
The .Reference dot field does not work after assigned to an invalid access name.
For example:
1. Set .Reference to TestProt.i00 - It works fine.
2. Set .Reference to Test.i00 - It does not work because test is an invalid access name.
3. Set .Reference to TestProt.i00 again - It no longer works.

Notes: If Tagname.Reference="" is used, user must re-enter the access name and the item name.

Back to Resolved Issues

L00049917 Functions GetAlarmLogConnStatus( ) and GetAlarmLogMaxCacheCount( ) are not working.

Problem:
The functions GetAlarmLogConnStatus( ) and GetAlarmLogMaxCacheCount( ) are not working in InTouch 9.5 Patch 01. If you use these functions in an action script, an error message "Cannot use Keyword" appears when you create the script.

Back to Resolved Issues

L00050671 There is a memory leak when the Real Time Trend has the option "Only update when in memory" selected.

Problem:
There is a memory leak when the Real Time Trend has the option "Only update when in memory" selected.

Back to Resolved Issues

L00050680 If an acknowledged alarm goes from HI to HIHI, both states are acknowledged with the time stamp of the last acknowledgement. This occurs only for Hot Backup pairs.

Problem:
If an acknowledged alarm goes from HI to HIHI, both states are acknowledged with the time stamp of the last acknowledgement. This occurs only for Hot Backup pairs.

Back to Resolved Issues

L00050905 File/Print of all scripts crashes WindowMaker with an application that is converted from InTouch 7.11.

Problem:
File/Print of all scripts crashes WindowMaker with an application that is converted from InTouch 7.11.

Back to Resolved Issues

L00050926 Changing the window status of WindowViewer (switching between WindowMaker and WindowViewer) causes loss of encryption when the input link uses the keyboard.

Problem:
Changing the window status of WindowViewer (switching between WindowMaker and WindowViewer) causes loss of encryption when the input link uses the keyboard.

Back to Resolved Issues

L00050929 Changes made to the Quick Function are not updated after using the cross reference for that Quick Function.

Problem:
Changes made to the Quick Function are not updated after using the cross reference for that Quick Function.

Back to Resolved Issues

L00051078 Error message “WWHeap (0003) HShareInternal: Could not map @5d080000. Error 487” appears when Recipe Load and IDEA applications are both running.

Problem:
WWHeap error messages appear in the Log Viewer when WindowViewer, Recipe Load, and IDEA applications are running at the same time.
WWHeap (0003) HShareInternal: Could not map @5d080000. Error 487
Assertion Error: File U:\AlarmMgrDev\src\systools\wwheap\wheap.c Code {B61E38E9-4E70-11d2-8070-00A0C90055CE}

Back to Resolved Issues

Back to Top

Known Issues

L00044912 Data Transformation Services - DTS export on the MS SQL Server generates errors.

Problem:
This issue exists in Microsoft SQL 2000 and 2005 Server Editions. The Data Transformation Services failed because of the view definition v_AlarmSuiteAlarmLog.

To work around this issue, do the following:

1) Open SQL Server Enterprise Manager and drill down to the database that needs to be transformed.
2) Click Views.
3) Right-click the view "v_AlarmSuiteAlarmLog" and select Design View.
4) From the SQL statement remove in two places the following characters from SELECT statements:,'' AS Units
5) Save the view.
6) Right-click on Data Transformation Services and select Export.

NOTE: Data Transformation Services do not export all the views and stored procedures. This is common for the entire database. The Alarm DB Logger utility cannot log the data to newly migrated database and produces error in Log Viewer. This is expected because the stored procedure is not available.

The best way to migrate is to back up the existing database by using SQL Server Enterprise Manager and then to restore it in SQL Server 2005.

Back to Top

© 2006 Invensys Systems, Inc. All Rights Reserved.