honeywell tracetm · this patch software change notice contains important information that must be...

HONEYWELL TRACETM

R130

___________________________________

Patch-2 Software Change Notice

___________________________________

HTDOC-X587-en-620A

September 2019

HTDOC-X587-en-620A 2

DISCLAIMER

This document contains Honeywell proprietary information. Information contained herein

is to be used solely for the purpose submitted, and no part of this document or its contents

shall be reproduced, published, or disclosed to a third party without the express

permission of Honeywell International Sàrl.

While this information is presented in good faith and believed to be accurate, Honeywell

disclaims the implied warranties of merchantability and fitness for a purpose and makes

no express warranties except as may be stated in its written agreement with and for its

customer.

In no event is Honeywell liable to anyone for any direct, special, or consequential damages.

The information and specifications in this document are subject to change without notice.

Copyright 2019- Honeywell International Sàrl

ABOUT THIS DOCUMENT


Table of contents 1 ABOUT THIS DOCUMENT .............................................................................................................................. 4

2 WHAT’S NEW IN HONEYWELL TRACE R130 PATCH-2 ................................................................... 5

3 INSTALLING R130 PATCH-2 .................................................................................................................. 10

3.1 Supported Migration Scenarios ................................................................................................................... 10

3.2 Installer Package ................................................................................................................................................. 10

3.3 Install Instructions .............................................................................................................................................. 11

4 PATCH 2 – RESOLVED ISSUES ............................................................................................................... 18

5 PATCH 1 - RESOLVED ISSUES ................................................................................................................ 20

6 KNOWN ISSUES ............................................................................................................................................ 22

7 NOTICES.......................................................................................................................................................... 23

ABOUT THIS DOCUMENT


1 About this document

This Patch Software Change Notice contains important information that must

be read prior to installing and working with Honeywell Trace R130 Patch-2.

Trace R130 Patch-2 is a cumulative release that contains the following: Trace

R130 Patch-1, the hotfixes released after Patch1, enhancements, and fixes.

For more information about enhancements, see the section What’s New. For

information about fixes, see the section Resolved Issues

WHAT’S NEW IN HONEYWELL TRACE R130 PATCH-2


2 What’s New in Honeywell Trace R130 Patch-2

The following feature enhancements are available in R130 Patch-2:

Parameter related information are now included in the CL View also.

Previously, only point names were displayed under the Referenced

Tags. Now, parameters related details are also displayed.

Tags based grouping of the referenced tags is enabled for CL,

PointScript, CAB instance, and Display View. You can view

tag.parameter(s) details on expanding the required Tag.



Provision to view I/O modules and channels is enabled for the DHP

[EPLCG] node in the Hardware View of the TPS system.

New option is introduced in the TPS Data Collection page to

selectively collect DS [Display] files. The DS files will be collected only

if this option is selected.



New icon [R] is introduced to indicate the Reserved Channels in the

Hardware View to ease the identification of reserved vs free channels

and allocation appropriately.

Option to select any Display Object on the Reference Tags list will

highlight the selected object on the Display view for HMI display.



Group number and position number data appears for Experion Groups

and Trend references.

The tags referred in a display will list all display files instead of each

object in a display. Each object reference can be viewed on the

selected display file.

INSTALLING R130 PATCH-2


3 Installing R130 Patch-2

This section provides information about how to install Trace R130 Patch-2.

3.1 Supported Migration Scenarios You can install the Trace R130 Patch-2 in the following progression:

1. Migration

Trace R121 Trace R130.1 Trace R130 Patch-2

2. New Installation

Trace R130.1 Trace R130 Patch-2

3. Upgrade

Trace R130.1 Trace R130 Patch-1 + Hotfixes (which is not

mandatory) Trace R130 Patch-2

3.2 Installer Package The Trace_R130.1_Patch2.zip package contains individual installer for each

Trace nodes in the following folder:

L3Server

L4Server

Offline_DataCollector

RemoteNode



3.3 Install Instructions Install the patch Trace_R130.1_Patch2.zip on Honeywell Trace Server (L3

and L3.5), Trace Data Collector, and Remote nodes.

If installing on… Follow these steps

Trace Server at L3 / Offline

Trace Server

1. Make sure the Data Collection is not in progress. If

Data Collection is in progress, wait until the

collection is complete.

2. Close all the instance of Trace application and

Microsoft SQL.

3. Extract the Trace_R130.1_Patch2.zip file.

4. Copy the L3Server_update.exe from

Trace_R130.1_Patch2\L3Server and paste in your

Trace Server machine.

5. Right-click the L3Server_update.exe, select Run as

Administrator, and click Yes.

6. Honeywell Trace L3 Server Patch appears. Click

Update.

7. Select Automatically close and attempt to restart

applications and click OK.



ATTENTION:

You may encounter the following message occasionally.

Click OK to ignore and proceed with the installation.

8. Click Finish.

9. Restart the machine, click Yes.



Trace Server at L3.5 / L4 1. Make sure the Data Collection is not in progress. If



2. Close all the instance of Trace application and

Microsoft SQL.


4. Copy the L4Server_Update.exe from

Trace_R130.1_Patch2\L4Server and paste in your

Trace Server machine.

5. Right-click the L4Server_Update.exe, select Run as

Administrator, and click Yes.

6. Honeywell Trace L4 Server Patch appears. Click

Update.



ATTENTION:



7. Click Finish.


Trace Server at L3

To establish sync between L3 and L3.5/L4:

1. Run the Trace Admin Console for Sync.



Trace remote node 1. Make sure the Data Collection is not in progress. If




3. Copy the RemoteNode_Update.exe from

Trace_R130.1_Patch2\RemoteNode and paste in

your Trace remote node machine.

4. Install the RemoteNode_Update.exe located in

Trace_R130.1_Patch2\RemoteNode. Click Update.

NOTE:

Only for PHD node, provide the host name of PHD

Database Server.

5. Click Finish.



Trace Data Collector 1. Make sure the Data Collection is not in progress. If



2. Close all the instance of Trace application.


4. Copy the Offline_DataCollector_Update.exe from Trace_R130.1_Patch2\Offline_DataCollector and paste in your machine where Trace Data Collector is installed.

5. Install the Offline_DataCollector_Update.exe. Click

Update.

6. Select Automatically close and attempt to restart

applications, and click OK.



ATTENTION:



7. Click Finish.


PATCH 2 – RESOLVED ISSUES


4 Patch 2 – Resolved Issues

The following is the list of resolved issues in Patch-2.

PAR # Issue - Description

1-BPY8N41 Trace login takes longer time to load the dashboard page.

1-BPY8N4B Unable to login Trace due to failed Trace License service.

1-BPY8N4J CDS parameters (including arrays) and references are missing for

the AM points in TPS system.

1-BPY8N5V Loading peer reference takes longer time.

1-BPY8N81 Fetching snapshot status message was displayed in all the page in

Trace application when data collection was in progress.

1-BPY8N8A Trace snapshot collection fails when large number of displays are

collected in Experion PKS system.

1-BPY8NB9 Sync between L3 and L3.5/L4 fails when ICMP ping is blocked by

the firewall.

1-BPY8NBH PVRAWHI and PVRAWLO parameters are missing in Trace property

for SM AI Points in TPS system.

1-BPY8NCW If multiple TPS systems were selected while adding PHD

application, Trace is unable to resolve all PHD references.

1-BPY8NHK PHD data collection fails when the collector node does not have

PHD config tool installed.

1-BPYHMG6 TPS points are not resolved in EPKS HMI displays for ESVT systems

with DSA/Safety Manager tags.

1-BPYKY0M Network View does not appear for all clusters in a single EMDB

wherein each cluster has top-level switch.

1-BPYKYCS Tag list in the Hardware View populates other controller points.

1-BPYKYD0 Global search was not performed on the latest snapshot by default.

PATCH 2 – RESOLVED ISSUES


PAR # Issue - Description

1-BPYKYD8 Invalid Display reference anomalies in Experion HMI displays.

1-BPYKYDG Hardware View does not show FIM2 in the C200 remote chassis.

1-BPYKYDY Experion displays are not collected occasionally.

1-BPYKYE6 Unable to navigate to Hardware View from global search result for

TPS channels.

1-BPYKYEY Unable to acknowledge changes in the Logical View.

1-BPYKYF6 Unable to login to Trace after migrating to R130 occasionally.

1-BPYR5OC Unable to generate Trace reports after migrating to R130

occasionally.

PATCH 1 - RESOLVED ISSUES


5 Patch 1 - Resolved Issues

The following is the list of resolved issues in Patch-1.

JIRA PAR Issue - Description/Recovery/Workaround

RTRACE – 1924 When connections are shown on TRS, the index parameters were also

shown on the respective ends of the connections.

RTRACE – 1847 The TRS connections were missing because references for

downstream system for connections were not resolved.

RTRACE - 1950 When a system is deleted, its displays and references deletions were

also shown as changes in Change Detection.

RTRACE – 1912 For TPS, in Change Detection Page, for CL changes, object name was

appearing as a hyperlink.

RTRACE – 1940 For TPS, in Display View, on the right-side of the window, search box

was retaining previous search string.

RTRACE -1936 From any modification tab, if user performs suppression, it wasn’t

getting reflected in UI.

RTRACE -1852 For TPS, in Display View, navigation for few Referenced tags was not

working for .DS files.

RTRACE -1944 For Allen-Bradley ControlLogix, in few scenarios, Trace failed to

retrieve the correct Sheet Count for the respective FBD Tag which

results in missing FBD Logic in Allen-Bradley ControlLogix System.

RTRACE – 1935 In case of Logic Point, if there is any tag (for example, Array, Logic, or

Digital Composite) is configured as Input/Output Connections, Trace

wasn’t capturing those references.

RTRACE – 1933 For TPS, the tags referred indirectly in CL file, the information is listed

in TRS Tabular view, but it was not appearing as a link.

RTRACE – 1553 If the two AM Nodes are configured as Redundant, Trace failed to

identify that information when the Node numbers are not

consecutive.

RTRACE – 1415 Trace failed to consider those parameters while parsing the

Checkpoint file, which results in mismatch compared to Source

System.

PATCH 1 - RESOLVED ISSUES


JIRA PAR Issue - Description/Recovery/Workaround

RTRACE -1951 Migrated L3 (old machine to new machine) and fresh L3.5

synchronization was failing.

BW- 36350 Post-Experion data collection, there was an "i" icon that appears to

right of system name. Clicking or placing cursor over the icon wasn't

opening the screen tip containing details.

RTRACE -1931 In TPS, for few .htm files, the referred links/tags were not listed in the

Referred Links/tags pane.

RTRACE -1955 Experion parsing failed due to displays collection failure.

RTRACE -1953 TPS data collection was failing because user action was required

while reading the .PCT file.

RTRACE -1952 In the migration scenario, Change Detection was slow.

RTRACE -1946 IAA report generation was failing in few L3 migrated machines.

RTRACE-1932 When .htm files are searched from Global Search, a window opens

displaying the following message, "Currently, the view for this display

is not available."

RTRACE-1614 Stored Procedure fine tuning and caching performance has

improved after migrating from R121 to R130.

RTRACE-1947 ESVT system license consumes pure TPS and pure EPKS license.

KNOWN ISSUES


6 Known Issues

The following is the list of known issues.

PAR # Issue - Description/Recovery/Workaround

RSWORD-967 Flexera License Utility throws error when an expired or outdated

“Response.bin” file is uploaded to activate the license.

RSWORD-968 When an unused Activation key is used for returning license, Flexera

is creating .bin file, which it should not create (as it cannot be used).

RSWORD-969 When Flexera License Activation Utility screen is left idle for more

than 20 minutes, application throws an error for the first operation

done past this idle period.

Workaround: Refresh the screen post-idle time.

RSWORD-970 Flexera License Activation Utility accepts only GUID, whereas it is

accepting any number of characters.

RSWORD-980 In License Activation Utility, online license activation may fail

throwing “Generic communications error.”

RTRACE – 1949 For Trace Data Collector, in few scenarios, the status shown is

“Initiating” even though the overall Snapshot status has failed. This

occurs when Resume button is clicked during the snapshot failure.

RTRACE – 1960 External tag references with respect to communication between

Allen-Bradley ControlLogix and Experion PKS via EIM are not

appearing.

NOTICES


7 Notices

Trademarks

Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are

registered trademarks of Honeywell International, Inc.

OneWireless™ is a trademark of Honeywell International, Inc.

Other trademarks

Microsoft and SQL Server are either registered trademarks or trademarks of

Microsoft Corporation in the United States and/or other countries.

Trademarks that appear in this document are used only to the benefit of the

trademark owner, with no intention of trademark infringement.

Third-party licenses

This product may contain or be derived from materials, including software, of

third parties. The third party materials may be subject to licenses, notices,

restrictions and obligations imposed by the licensor.

The licenses, notices, restrictions and obligations, if any, may be found in the

materials accompanying the product, in the documents or files

accompanying such third party materials, in a file named third_party_ licenses

on the media containing the product, or at

http://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedback

You can find the most up-to-date documents on the Honeywell Process

Solutions support website at:

http://www.honeywellprocess.com/support

If you have comments about Honeywell Process Solutions documentation,

send your feedback to:

[email protected]

Use this e-mail address to provide feedback, or to report errors and omissions

in the documentation. For immediate help with a technical problem, contact

your local Honeywell Process Solutions Customer Contact Center (CCC) or

Honeywell Technical Assistance Center (TAC).

http://www.honeywell.com/ps/thirdpartylicenses

http://www.honeywellprocess.com/support

mailto:[email protected]

NOTICES


How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software

defect or weakness that can be exploited to reduce the operational or security

capabilities of the software.

Honeywell investigates all reports of security vulnerabilities affecting

Honeywell products and services.

To report a potential security vulnerability against any Honeywell product,

please follow the instructions at:

https://honeywell.com/pages/vulnerabilityreporting.aspx

Submit the requested information to Honeywell using one of the following

methods:

Send an e-mail to [email protected].

or

Contact your local Honeywell Process Solutions Customer Contact Center

(CCC) or Honeywell Technical Assistance Center (TAC) listed in the “Support”

section of this document.

Support

For support, contact your local Honeywell Process Solutions Customer

Contact Center (CCC). To find your local CCC visit the website,

https://www.honeywellprocess.com/en-US/contact-us/customer-support-

contacts/Pages/default.aspx.

Training classes

Honeywell holds technical training classes that are taught by process control

systems experts. For more information about these classes, contact your

Honeywell representative, or see http://www.automationcollege.com.

https://honeywell.com/pages/vulnerabilityreporting.aspx

mailto:[email protected]

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

http://www.automationcollege.com/

NOTICES


honeywell tracetm · this patch software change notice contains important information that must be...

Documents