InTouch 9.0 P03

Материал из archestra.info
Перейти к: навигация, поиск



InTouch® 9.0 Patch 03 ReadMe

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 9.0 Patch 03 Build has primarily been tested on:

·        Windows Server 2003 Standard Edition with SP1

·        Windows XP Professional with SP2

·        Windows 2000 Server with SP4

·        Internet Explorer 6.0 SP1

To install the InTouch 9.0 Patch 03 from a CD, you must follow these instructions:

For regular InTouch:

·        The CD volume name must be Patch.

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

 

For Terminal Services InTouch:

·        The CD volume name must be PatchTS.

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

 

If the CD has a name different than the names listed above, 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.

Microsoft Windows XP SP2, and Windows Server 2003 SP1 introduce several security technologies including disabled NetDDE, enhanced Windows firewall, and a reduced RPC attack surface. These enhancements affect the use of NetDDE, LogViewer, and SuiteLink protocols in InTouch.

If InTouch must be operated on Windows XP SP2 or Windows Server 2003 SP1, the patch installation runs the OS Configuration Utility. This utility opens specific ports that enable NetDDE and adds Wonderware SuiteLink and Wonderware LogViewer to the firewall exception list.

InTouch does not work properly on a Windows XP SP2 or Windows Server 2003 SP1 computer if you do not run the OS Configuration Utility during installation.

During the InTouch patch installation, select the designated check box to determine whether the installation runs the utility or not.


Resolved Issues

The following issues are fixed for this patch release. Click on the issue  number for more information about the problem.

L00032114 IOSetRemoteReferences() take a long time to execute.

L00033450 If InTouch windows are imported and you select the 'Use Existing Tags (Conserve Placeholders)' option, the wrong tagnames are assigned to cells.

L00034151 ACK is not synchronized on a Hot backup pair if the client alarm object (AlarmViewer control) was re-queried or the client window with the alarm object was closed and reopened.

L00034559 GDI Object Halo memory leak causes error messages such as "Too low on memory resources for bitmap display" or "Not enough memory".

L00034610 Multiple QuickFunctions returning strings in a Value Display String.

L00034775 No access to the InBatch's ActiveX properties or to the Objects in the Wizard.

L00034805 You can configure the OnKeyUp script in the InTouch.ini file.

L00035155 The new methods added in the InTrack 7.11 Patch 06 do not appear in the InTrack buttons.

L00035179 The tag count for Remote Tagname Referencing is not decrementing when windows are closed, causing the limit of 65498 to be reached prematurely.

L00035297 Alarm DB Purge/Archive is not working correctly - NULL is written in event text file for Event Column. It should be ' ' (blank) or the actual comment from event.

L00035363 Memory Leak - The Handle count in the View.exe process in Windows Task Manager increases every time the historical trend display is updated.

L00035500 "Calling WWDHCON_FillBuffer . . . " dubug message is logged in the Log Viewer when updating the Historical Trend.

L00035683 View is leaking memory by poking to the UDA of an Industrial Application Server object.

L00035860 InTouch should detect whether the ActiveX object is fully loaded into memory before triggering an Event on that ActiveX object.

L00036260 Handle Count increases when using FileWriteFields() and FileWriteMessage() functions.

L00036439 Bitmap resource issue: Error message "Failed to convert DIB. Different color depth?" appears.

L00036941 InTouch WindowViewer uses 100% CPU and hangs

L00038722 With Min/Max display mode, trend chart displays are not consistent, depending on the start time and end time of the time span.

L00038759 WindowViewer crashes if .AlarmEnabled is set to 0 for a discrete tag using Expanded Summary Alarms.

L00038870 After stopping and starting InSQL, the tags do not update. InSQL shows Null until the tag changes value. Issue: InTouch does not send the correct OPC quality (= 0) .

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

L00040477 When running an InTouchView application from WindowViewer with a license file containing an InTouchView Feature Line, the following message appears: The License File '...\wwsuite.lic' was located, but the Feature Line 'InTouch' could not be found inside of it.

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

L00041561 After TSE clients fail-back and the engine fails back to the primary node, alarm queries in the AlarmViewer control do not connect to the local servers InTouch alarm provider.

L00041709 Importing supertags do not work correctly.

L00043734 AlarmDbView Control's Query Filter or Filter Favorites is corrupted if any one of the query conditions (AlarmDbView control properties) is manually updated.

L00043736 GetAccountStatus does not return -1 if "Users must change password at next logon" is selected.

L00044016 If the sort order is set to a column other than 'Time', when an alarm is selected in the AlarmViewer control and another client acknowledges an alarm, the new Ack message is placed at the top of the list, moving the highlighted alarm down the control.

L00044198 New features are added to the SPCPro.

L00045201 Shutting down View.exe nullifies Ctrl+Alt+Del policy settings.

L00045715 Industrial Application Server alarm/event does not get logged to the alarm database if the AckMsg contains a single quotation mark (apostrophe).

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

L00046016 New diagnostic feature added when Alarm DB Logger loses connection with the database if the alarm buffer overflows. This feature allows the operators to assess the health of the utility.

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

L00046631 The TagAccess Application from the Factory Toolkit does not work with Intouch 9.0 Patch02.

Back to Top


Detailed Descriptions for Resolved Issues

L00033450 If InTouch windows are imported and you select the 'Use Existing Tags (Conserve Placeholders)', the wrong tagnames are assigned to cells.

Problem:
If InTouch windows are imported and you select the 'Use Existing Tags (Conserve Placeholders)', the wrong tagnames (and wrong type) are assigned to the cells. If you break apart the cell and take a look at the animation links, the tagnames assigned may also be the wrong type.

Back to Resolved Issues

L00034151 ACK is not synchronized on a Hot Backup pair if the client alarm object (AlarmViewer control) was re-queried or the client window with the alarm object was closed and reopened.

Problem:
- ACK synchronization does not occur if alarm object on the consumer node is closed and reopened after alarms are regenerated.
- ACK synchronization does not occur if the alarms are re-queried on the consumer node after alarms are regenerated.

Back to Resolved Issues

L00034559 GDI Object Halo memory leak causes error messages such as "Too low on memory resources for bitmap display" or "Not enough memory".

Problem:
An application has a background object that matches the size of the window. This object has an animation link and scripting to change the windows background color if the user prints the window. This saves black ink.

Because the object is the same size as the visible viewing area and there are animation links, the "Halo" appears off screen and is not seen.
An application can crash after an hour with the following error message "View - Too low on memory resources for bitmap display or not enough memory...". This is due to GDI objects leaking memory and reaching a critical limit.

Back to Resolved Issues

L00034805 You can configure the OnKeyUp script in the InTouch.ini file.

Problem:
Need a way to cancel the activation of the "OnKeyUp" script when a button is pressed.

Detail:
Left mouse button behavior can be configured in the [InTouch] section of the InTouch.ini as follows:
    [InTouch]
    MouseMustBeOnObjectForOnKeyUp=1  

1.      Default setting: no InTouch.ini setting or "MouseMustBeOnObjectForOnKeyUp=0"

Behavior for the "On Key Down" and "On Key Up" is as follows:

·         Releasing the left mouse button before or after moving the mouse pointer off the object activates the "On Key Up" script.


    For example:

 

In an InTouch application window, paste a button with an action script that sets a memory tag discrete to 1 for the "On Key Down" event and sets the memory tag discrete to 0 for the "On Key Up" event. Create an animation display link for the discrete tag.
Move the mouse over the button object and press the left mouse button. The discrete value changes to 1. Release the left mouse button. The discrete value changes to 0. Repeat this but before releasing the left mouse button, move the mouse pointer off the button, release the button and the value changes to 0.

 

2. Set "MouseMustBeOnObjectForOnKeyUp=1" or any non-zero value in InTouch.ini:
   

Behavior for the "On Key Down" and "On Key Up" is as follows:

·         Releasing the left mouse button after moving the mouse pointer off the button does NOT trigger the "On Key Up" event.


    For example:

 

In an InTouch application window, paste a button with an action script that sets a memory tag discrete to 1 for the "On Key Down" event and sets the memory tag discrete to 0 for the "On Key Up" event. Create an animation display link for the discrete tag.
Move the mouse over the button object and press the left mouse button. The discrete value changes to 1. Release the left mouse button. The discrete value changes to 0.
Repeat but this time before releasing the left mouse button, move the mouse pointer off the button, release the button, and the value remains at 1.

Use this setting to cancel the activation of the "On Key Up" script.

Back to Resolved Issues

L00035155 The new methods added in the InTrack 7.11 Patch 06 don’t show up in the InTrack buttons.

Problem:
The objects Lot, Sublot, Material and Location are provided with the RefreshCache method. This method refreshes the local cache. The Location object is provided with SetUDACheckLock method which checks the lockcount setting before SetUDA function is called. These methods were previously not available under InTrack buttons.

Back to Resolved Issues

L00035297 Alarm DB Purge/Archive is not working correctly - NULL is written in event text file for Event Column. It should be ' ' (blank) or the actual comment from the event.

Problem:
Alarm DB Purge/Archive is not working correctly - NULL is written in event text file for Event Column. Alarm DB Restore fails and rolls back.

Back to Resolved Issues

L00035363 Memory Leak - The Handle count in the View.exe process in Windows Task Manager increases every time the historical trend display is updated.

Problem:
The Handle count in the View.exe process in Windows Task Manager increases every time the historical trend display is updated either through the wizard buttons or from functions such as HTUpdateToCurrentTime(Trend_Template.Name);

Back to Resolved Issues

L00035683 View is leaking memory by poking to the UDA of an Industrial Application Server object.

Problem:
View constantly and steadily loses memory if View is keeping poking value to the UDA of an Industrial Application Server object. The rate of leaking is proportional with the rate of poking (poke interval) and numbers of UDAs poked. The CPU on the node where View is poking is steadily increasing until it finally reaches 100%.

Back to Resolved Issues

L00035860 InTouch should detect whether the ActiveX object is fully loaded into memory before triggering an Event on that ActiveX object.

Problem:
If an InTouch window containing the ActiveX object (therefore loading the ActiveX object into memory) is loaded or an event belonging to the ActiveX object is triggered before the ActiveX object is fully loaded into memory, error messages appears.  InTouch should detect whether the ActiveX object is fully loaded into memory before triggering an Event on that ActiveX object.

Back to Resolved Issues

L00036439 Bitmap resource issue: Error message "Failed to convert DIB. Different color depth?" appears.

Problem:
The bitmap does not appear. Instead a rectangle appears and WindowMaker performance deteriorates.
SMC Logger shows the message: "Info WM Failed to convert DIB. Different color depth?"

Back to Resolved Issues

L00036941 InTouch WindowViewer uses 100% CPU and hangs.

Problem:
InTouch WindowViewer uses 100% CPU and hangs after running for an undetermined amount of time. The application hangs while it is in the "Procution Active" mode which includes sending data to the QI Analyst database, refreshing QI Analyst ActiveX controls, and performing the FileWriteFields() function.

Back to Resolved Issues

L00038870 After stopping and starting InSQL, the tags do not update. InSQL shows Null until the tag changes value. Issue: InTouch does not send the correct OPC quality (= 0).

Problem:
After the server is disconnected, the OPC quality is changed to bad because WindowViewer is no longer connected. After connecting, it should show the OPC quality as before disconnecting. Thus the quality is not updated after disconnection.

Back to Resolved Issues

L00041561 After TSE clients fail-back and 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.

Problem:
After TSE clients fail-back and 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

L00041709 Importing supertags is not working correctly.

Problem:
Importing a supertags csv file results in an additional number of supertags being created in the tagname dictionary.

Back to Resolved Issues

L00043734 AlarmDbView control's Query Filter or Filter Favorites is corrupted if any one of the query conditions (AlarmDbView control properties) is manually updated.

Problem:
The Filter Favorites and Query Filter no longer work after any manual change of the query properties, such as ToPriority, FromPriority, Provider, and GroupName or the Refresh() action is executed.

Back to Resolved Issues

L00044016 If the sort order is set to a column other than 'Time', when an alarm is selected in the AlarmViewer control and another client acknowledges an alarm, the new Ack message is placed at the top of the list, moving the highlighted alarm down the control.

 

Problem:
If the sort order is set to a column other than 'Time', an alarm is selected in the AlarmViewer control and another client acknowledges an alarm, the new Ack message is placed at the top of the list. This makes the selected alarm move down the control. Eventually the selected alarm disappears off the screen.

Back to Resolved Issues

L00044198 New features are added to the SPCPro.

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" displays 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.      The user 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

L00045201 Shutting down View.exe nullifies Ctrl+Alt+Del policy settings.

Problem:
Run the Group Policy Editor (gpedit.msc) to set some of the Registry Keys (Group Policy) like DisableTaskMgr, DisableLockWorkstation, DisableChangePassword, NoClose, NoLogOff.

Go to User Configuration/Administrative Templates/System/CTRL+Alt+Del. You can pick the Task Manager, as an example, and select "Enable". When you press CTRL + Alt + Del, the Task Manager option is unavailable.

Start WindowViewer and stop it again. Press Ctrl + Alt + Del again. The Task Manager button is now enabled even if the EnableDisableKey() function is not used in the InTouch application.

Back to Resolved Issues

L00045715 Industrial ApplicationServer alarm/event does not get logged to the alarm database if the AckMsg contains a single quotation mark (apostrophe).

Problem:
The alarm/event record does not get logged to the alarm database. The following Info messages are posted to the SMC Logger for the WWAlmLogger component:

- Database connection available.
- Logging events failed.

Back to Resolved Issues

L00045822 Unable to connect to LogViewer by using the '[computer name]' in SMC.

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

Back to Resolved Issues

L00046016 New diagnostic feature added when Alarm DB Logger loses connection with the database if the alarm buffer overflows. This feature allows the operators to assess the health of the utility.

Solution:
Three functions GetAlarmLogCacheCount( ), GetAlarmLogConnStatus( ) and GetAlarmLogMaxCacheCount( ) allow you to see the status of Alarm DB Logger's status, connection and cache count.

These functions only work after creating the following registry keys and their values.
        -  Create a key with the name "AlarmDBLogStatus" in the registry folder "SOFTWARE\Wonderware".
        -  Create two DWORD value with the following names:

·     nbsp;    EnableAlarmDBLogStatus
1      enable the Alarm DB Logger diagnostics
0      disable the Alarm DB Logger diagnostics

·         SmartCacheStatusLoggingRate
the time interval (in minutes) in which Alarm DB Logger provides the diagnostics to view. The default is 1 minute. If this entry is blank, the default is used. Set this value to 1 minute or more. If you set it lower than 1 minute, the performance of Alarm DB Logger may decrease.

New Functions:

GetAlarmLogConnStatus()             
   Returns the database connection status.

-1     Alarm logger is closing with no connection
0      Connection status is not available
1      Connection is active
2      Connection is not available
4      Alarm logger is closing with valid database connection
 
GetAlarmLogCacheCount()           
   Returns the number of alarms in the Alarm DB Logger cache.
 
GetAlarmLogMaxCacheCount()     
   Returns the maximum number of alarms that can be cached into the Alarm DB Logger cache.

Back to Resolved Issues

L00046260 Using InSQL 7.1 as an InSQL Distributed History Provider in InTouch 9.0 Patch 02 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.0 Patch 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 "InSQLLowerVersion=1" into the InTouch.ini as follows:

[InTouch]

InSQLLowerVersion=1

Note: InTouch 9.0 not compatible with InSQL 7.1. See the compatibility matrix table at https://wdn.wonderware.com/sites/WDN/Pages/Tech_Support/TechSupport.aspx for details.
If you are using InSQL 7.1 as an Distributed History Provider for InTouch 9.0, the Historical trend might show a gap at right side of trend during Fall Back time change in October, and data for 12am-1am is not logged.

Back to Resolved Issues

L00046631 The TagAccess Application from the Factory Toolkit does not work with Intouch 9.0 Patch02.

Problem:
The TagAccess Application from the Factory Toolkit (using IntouchCOM.dll v 7.1.0.2) does not work with Intouch 9.0 Patch02 results in the runtime Error "Connection to Intouch Failed".

Back to Resolved Issues

Back to Top


© 2006 Invensys Systems, Inc. All Rights Reserved.