Experion PKS

R431.1 Support Software Media Software Change

Notice

EPDOC-X175-en-4311A
February 2015

Release 431.1
 Document Release Issue Date
EPDOC-X175-en-4311A 431.1 0 February 2015

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 2015 - Honeywell International Sàrl

2 www.honeywell.com
Contents

1 Introduction ............................................................................................................................................ 5
1.1 About this document ........................................................................................................................................... 6
1.1.1 Revision history ................................................................................................................................... 6
1.2 Check for updates on Honeywell Process Solutions website ............................................................................. 7
2 Issues ...................................................................................................................................................... 9
2.1 .......................................................................................................................................................................... 10
2.2 .......................................................................................................................................................................... 16
2.3 .......................................................................................................................................................................... 50
2.4 .......................................................................................................................................................................... 51
3 Notices .................................................................................................................................................. 53
3.1 Documentation feedback .................................................................................................................................. 54
3.2 How to report a security vulnerability .............................................................................................................. 55
3.3 Support .............................................................................................................................................................. 56
3.4 Training classes ................................................................................................................................................. 57

3
CONTENTS

4 www.honeywell.com
1 Introduction

Note
Known Issues are covered in this SCN, for other information refer to the Experion R431 General Release SCN.

Related topics
“About this document” on page 6
“Check for updates on Honeywell Process Solutions website” on page 7

5
1 INTRODUCTION

1.1 About this document

This Software Change Notice contains information for all the users of Experion R431.1. The Support Software
SCN must be read prior to installing and managing the Experion system. The Support Software SCN contains
known issues.

1.1.1 Revision history

Version Date Description

A February 2015 Draft version

6 www.honeywell.com
 1 INTRODUCTION

1.2 Check for updates on Honeywell Process Solutions website

The Honeywell Process Solutions website, http://www.honeywellprocess.com contains software updates,
documentation, and recommended antivirus updates.
In our effort to provide the most up-to-date information, updates to this SCN are available on the Honeywell
Process Solutions website.

To access the Honeywell Process Solutions website

1 In a web browser, type the following URL.
https://www.honeywellprocess.com/support
The Product Support page appears.
2 If you are a new user, register at this website. Click Register, and follow the on-screen instructions.
3 If you are already registered, type your user name and password, and click Login to logon.
Your account logon name appears in the top-right of the page.

To download documents, security updates, or antivirus notifications

1 In the Search box, type the name of the required document, security update, or antivirus notification.
For example, to download the SCN, type Experion General Release Software Change Notice or Experion
Support Media Software Change Notice in the Search box.
2 Click Search.
The All Support Search Results page appears with the search results.
3 In the left pane, use the Search Result Filters to further filter the document, security update, or antivirus
notification. For example, if you are locating a Software Change Notice:
a In Document Type, click Software Change Notice.
b Inl Product Release, click the required Experion product release.

4 Click the document, security update, or antivirus notification link to open it.

7
1 INTRODUCTION

8 www.honeywell.com
2 Issues

This chapter provides the information about the Experion issues and workarounds.

Attention
Experion PKS R431.1 Support Software Media Software Change Notice reflects only Product Anomaly Reports
(PARs) with priority severity position 2.1 and above.
The PARs positioned at 2.2 and below are not included in this Software Change Notice.

Related topics
page 10
page 16
page 50
page 51

9
2 ISSUES

2.1

Experion Station-Native Window

PAR Description
1-DLHZ3R Error Indication: LCNP4 board not loading occasionally.
Description: Occasionally it is observed that after the pc restart/LCNP Reset,
emulators refuse to load the board.
Recovery: Perform the following steps.
1. From the Start menu select Settings/Control Panel/ Administrative Tools.
Select Services in the Services window, scroll down to TDC Emulators
Service. Right click TDC Emulators Service and select stop option. Once
the service is in stopped state Right click and select start option. Afte the
TDC Emulators Service Stop/Start, reset the LCNP board by selecting the
LCNP Reset option from the Start Menu->All Programs-> Honeywell
Experion PKS-> TPS Applications-> LCNP Status dialog.
2. Load the TPS\EPKS node which is stuck up in POWER_ON state from
another GUS/EST/US node in the same LCN.
Workaround: None.

OPC Gateway

PAR Description
1-2GZIVP6 Error Indication: Data values coming from the OPC Gateway may freeze based
on incorrect OPC Server function.
Description: Once the OPC Gateway subscribes to an OPC Server for a data
value, it is unable to detect if the OPC Server has stopped updating this point
correctly. This can be visible where the data is seen to be "frozen" coming from
the OPC Gateway but a new connection to the OPC Server by another client can
get correct "live" data.
Recovery: The OPC Gateway is unable to recover only a single data value. If an
OPC Server stops updating one of the points to the OPC Gateway one of two
actions can be taken. (1) (2)
1. Remove all requests for this point by clients of the OPC Gateway. This
requires unloading these points from Monitor.
2. Set the OPC Gateway to IDLE. This will result in the connection to the OPC
Server being closed and ALL DATA from the OPC Gateway will go to
Failsafe values. Commanding the OPC Gateway to RUN will restore all data
from all points coming from the OPC Gateway.
Workaround: None.

10 www.honeywell.com
 2 ISSUES

Secure Communication Manager

PAR Description
Error Indication: Experion nodes stop communicating and/or deployment of
secure communications policies fail after a re-synchronize command.
Description: This outcome is possible if the configuration information of a
restored Security Manager does not match or is incompatibly different than the
secure communication policies deployed and operating in the system.
Recovery: Modify secure communications configuration to restore system
communications. The changes to be made are dependent on which nodes have
lost communication and whether the nodes are currently secured or not.
Workaround: First, always backup the Security Manager after secure
communications configuration changes, so that subsequent restores of the
Security Manager will always match what has been deployed to the system.
Secondly, before using the Reysnchronize command, carefully evaluate the
configuration to be deployed vs the current system to decide if the command
should be executed. See the Secure Communications User Guide for additional
information on backup/restore considerations and use of the re-synchronize
1-1TRB5UD command.
Error Indication: Hardware replacement of the ESV node designated as
Security Manager with no backup or unusable backup results in a loss of Secure
Communications configuration data.
Description: If the Security Manager node is replaced and a backup of the
Secure Communications configuration (through EBR or other means) was not
taken or cannot be restored, the configuration data is effectively lost and Secured
nodes can no longer be managed through the Secure Communications tool.
Recovery: Recovering the Secured nodes requires clearing their individual
Secure Communications configuration and re-configuring the Secure
Communications system. Please refer to the "Secure Communications User's
Guide", Section "Node Maintenance" - Scenario "Restoring Security Manager
without a valid backup".
Workaround: Plan regular backups of the Security Manager node. Recommend
taking a backup of the Security Manager node and its Secure Communications
configuration whenever a new node has been Secured or an already Secured node
1-289JLQB has been Unassigned / removed.

11
2 ISSUES

Secure Communication Agent

PAR Description
1-3JXC9T1 Error Indication: Secured, redundant Experion Servers with ServerB as primary
and ServerA as backup, ServerA is rebooted and ends up taking over as primary.
Description: This can occur when ServerA is started after reboot. Server A may
timeout waiting for communications with Server B to be established before the
IPSec negotiation succeeds, which can be up to 2minutes. ServerA will assume a
primary role, resulting in dual primary Servers. Once the IPsec negotiation
succeeds the Servers will start communicating and Server B will step down to the
backup role knowing that ServerA is the preferred primary.
Recovery: None needed if ServerA in primary role and ServerB in backup role is
ok. If ServerB needs to be in the primary role, then command a Server swap.
Workaround: Take secured Experion Server pairs out of Secure
Communications before staring critical operations that will cause a reboot, such
as an Experion migration or Windows patch update. After the operation is
completed, the Experion Sever pair can then be re-secured. From the Secure
Communications user interface, nodes are taken out of Secure Communications
by Unassigning them from the Secured Nodes list, and nodes are added to Secure
Communications by Securing them from the Unassigned Nodes list.
Furthermore, when it is known in advance that the system is expecting to be
running Server B as primary and Server A is likely to have a period where it may
not be able to communicate with Server B, additional action is recommended to
ensure that when communications are re-established, ServerA will not elevate to
a primary role. Follow the instructions documented (associated with PAR
1-2TXBDD5) to stop and disable the Experion System service on Server A
before doing the critical operation, and subsequent restart and enable of the
service after the operation is completed.
1-288O73J Error Indication: C300 remain "updating" in Secure Communications UI;
policies are not applied
Description: After un-assigning a Security Manager proxy from the Secure
Communications UI, any nodes communicating with the Security Manager
through that proxy will no longer receive policy updates.
Recovery: Secure the removed proxy node
Workaround: To prevent this situation do not un-assign proxy nodes or ensure
all BOOTP servers point to one proxy node. See the Secure Communications
User Guide for further information.
1-1XVYCPZ Error Indication: C300 temporarily lose communication with console stations
during policy deployment.
Description: When securing a large number of Windows and C300 nodes at
once, C300 has been observed to temporarily lose communication with consoles
stations in the same security zone.
Recovery: Not required, communication restores automatically.
Workaround: Refer to the Secure Communications User Guide for the
recommended procedure to secure nodes. In addition, securing nodes in several
parts (for example 10-15 nodes at a time) vs all at once will further increase the
probability of avoiding interruptions in communication.

12 www.honeywell.com
 2 ISSUES

System Management

PAR Description
1-MZ6L8J Error Indication: FTE nodes disjoin and reconnect.
Description: FTE nodes gets disjoined and reconnected when time in NTP
source is slightly modified.
Recovery: None required system automatically recovers.
Workaround: None.
1-MNAFT7 Error Indication: Server data connection is lost
Description: Server lost data connection to System management by launching
the L2.5 switch display from the station. Issue is caused by slow response from
the switch.
Recovery: Switch to another display to continue working, and retry the switch
display later.
Workaround: None
1-28CKTBT Error Indication: The memory usage for the System Management Synchronized
Repository service (SyncRep.exe) rapidly increases on multiple nodes on a
network and network utilization increases significantly. There may be system
performance impact, and the synchronization of alarms between the nodes may
be delayed. If a syncrep memory leak occurs on only a single system, it is not
this issue, and this recovery procedure does not apply.
Description This behavior has been encountered on only one network to date,
and only under the specific scenario of unplugging the current primary server
from the network, and then later plugging it in again. Warning: until there is a fix
for this issue, all sites should avoid the above scenario. Even under this specific
scenario, the frequency of occurrence of the syncrep memory leak is low.
Recovery: Contact Honeywell TAC for more information about this issue.
Workaround. The best way to avoid this problem is to avoid the specific
scenario where this has been observed . If this issue occurs even once at a site,
the following procedure is recommended in order to prevent repeated occurrence.
1. Log on to one of the systems affected using a domain administrator account.
2. Open the system management display.
3. Ensure the correct set of computers displayed is correct for your current
configuration.
4. Right-click the scope item (domain or OU) in the left pane and select
properties.
5. In the properties dialog, as the Settings Source, select one of the nodes that is
properly configured for the Synchronized Repository settings (in particular,
the multicast address)
6. In the Synchronized Repository Configurations section at the bottom of the
properties page, for each of the three selectable values for Repository Name
(TPS_ComponentInfo, TPS_SysEvt, and TPS_SysEvtExt), set the value of
Maximum Response Time (ms) to 250.
7. Click OK or Apply, which causes the Save Common Configuration dialog to
appear. This dialog will list all the nodes the above settings will apply to.
Check the list, and if any nodes are red, determine the cause, and get them
back on-line if possible, as this timing change will not be applied to nodes
that are not running, only to the nodes that have the status Connection OK.
Click the OK button to apply the changes. For each node that displays
Connection OK, the status should change to
8. Configuration information was changed successfully.
9. Once this process has completed, click the Close button.2/28/2014 12:05:37
AM.

13
2 ISSUES

PAR Description
1-1EYHNCP Error Indication: Missing Managed Component alarm in alarm summary.
Description: Sometimes the MANCOMP is not shown when a network failure
occurs (such as disconnecting one of the FTE cables).
Recovery: Restart System Event Provider.
Workaround: Same as the recovery.

System Repository

PAR Description
1-1RTR2H5 Error Indication: CDA disconnects seen when performing "Load with contents"
of a controller.
Description: CDA disconnects were seen when doing "Load with contents" of a
controller having a huge amount of heavy strategies ( 1000+ RCMs) is done on a
heavily loaded setup.
Recovery: Perform switchover of servers to recover from the CDA disconnect if
the recovery doesn't happen automatically.
Workaround: The workaround to avoid this issue is to download the strategies
under the controller in smaller chunks instead of doing a "Load with contents"
for the controller.
1-3ILK9CN Error Indication: Failed to get the parameter information from System
Repository for Parameter.
Description: Failed to get the parameter information from System Repository for
Parameter error for CEE SCADA points on reload after modifying the previous
CEE SCADA in Expressions.
Recovery: Close control builder, invoke again and load.
Workaround: None.

OPM-Upgrade Tool

PAR Description
1-3N3C5RD Error Indication: Readiness Check of C300 controllers having 500 or more
references blocks goes to Pending state2.
Description: One or more L1 or L2 node in Upgrade Tool goes to pending state
on a relatively larger system with controllers having 500 or more references
blocks . 3.
Recovery: Relaunch Upgrade Tool and follow the steps mentioned in
Workaround.
Workaround:
• After Readiness check enumeration, for the C300 which have more reference
blocks, unselect the readiness check. Are there any dangling control
connections and proceed.
• Run ECC to identify the dangling control connections.

14 www.honeywell.com
 2 ISSUES

ETN-Enhanced TNode Virtualization

PAR Description
1-3NGCUTW Error Indication: Native Window Access level shows OPR (Operator)
irrespective of Signon Manager access.
Description: In case of a FTE connection reset (both Yellow and Green cable
Disconnect/Connect), it is observed that sometimes Native Window access level
shows OPR irrespective of the Signon Manager access level.
Recovery: None.
Workaround:
• Close the Native Window and re-open to get the correct access level.
• or
• Log-off and log-on again to the system.

15
2 ISSUES

2.2

CDA-Embedded

PAR Description
1-15CPF6R Error Indication: You notice that connection to C200E is in RED state
and all the IOs in the C200e do not give any value and display data access
of these IOs shows reverse video.
Description: On removal of Enet module the C200e connection is lost.
Recovery: There is no specific recovery mechanism for this scenario, one
way to ensure any connection loss for C200e, Enet module must be verified
if it is connected properly or not.
Workaround: None.
1-1NJX441 Error Indication: Noticed un-command shutdown ACE nodes during
stable run.
Description: This error is observed on stable system run, when ace.exe
process shuts down you try to restore the check point and activate them to
make them work properly.
Recovery: Restore check point of ACE nodes and make the controller
active.
Workaround: None.
1-NI0RKX Error Indication: Momentary failure in exchange block communication
with C300/C200E & PLC 5/PLC5550.
Description: Momentary failure in exchange blocks communication with
C300/C200E & PLC 5/PLC5550 observed while C300 connected through
ENET, C200E to PLC5 while connected through Control net, C200E
connected to PLC5550 through remote chassis.
Recovery: This error is a temporary condition and recovery happens
automatically. This error does not have any major impact on the execution.
Workaround: None.
1-QL372H Error Indication: Parent phase block displays that child activity already
exists.
Description: The phase block is out of sync with the child activity
Recovery: The child RCM will need to be executed then aborted and reset.
After this the parent Activity will take control of the child RCM. This has a
greater chance of happening on an inter cluster peer to peer configuration.
Workaround: None.
1-VI032H Error Indication: Connection will be disconnected for 7 seconds to
exchange block during C300 switch over when exchange block configured
on different FTE community.
Description: Seven seconds connection loss is observed for exchange
blocks during C300 switch over when exchange block configures on
different FTE community.
Recovery: Automatic recovery after 7 seconds.
Workaround: None.

16 www.honeywell.com
 2 ISSUES

1-3OO0E8N Error Indication: LOV and LOC observed on C300 while doing
continuous switch over (Power switchover).
Description: C300 switchover by cutting down the primary controller
power, there was a LOV and LOC observed after it has switched over
about 200 times (Primary restarted 200 and Secondary restarted 200
times ). The C300 is configured with the max load as specified in the PCT
spec.
Recovery: Stop the switchover and restart the Controllers.
Workaround : None.

CDA-Server

PAR Description
1-1EE8TQT Error Indication: New devices added to the Experion network are not
detected in FDM, also any existing device removal do not dynamically get
updated in FDM.
Description: This error occurs in a scenario where dynamic loading/
unloading of device and dynamic removal/connection of devices happen.
Recovery: If its redundant software mux, you have to stop the software
mux service on primary which enables software mux to switch over to back
up . On non redundant system, you have to rebuild network after stopping
the software mux service to recover from this issue.
Workaround: None.
1-1JLODM1 Error Indication: You can notice that the connection to FIM4 fails on
Load while active operation.
Description: This error occurs in scenario where cable is disconnected
from yellow CF9 and you try to perform Load while active operation, the
load fails.
Recovery: No Recovery.
Workaround: Reconnect the Yellow UPlink cable from CF9. the
connection is restored.
1-1LSM0ZQ Error Indication: You may notice server lost data connection to CDA
after server failover from Server B to Server A.
Description: After server fail over from server B to server A, continuous
data disconnect is observed.
Recovery: Synchronize the server and do fail over to server A.
Workaround: None.
1-1U5Z8ST Error Indication: CDA Server stops responding during normal operation.
Description: pscdasrv.exe(CDA Server) terminated unexpectedly during a
stable load with ActivityCreate/Delete. This may result in loss of view
condition. The probability of this occurrence is very low.
Recovery: Manual Start of EPKS Control Data Access service.
Workaround : None.
1-SZJRS9 Error Indication: Peer to Peer between 2 SIM C300 nodes does not work.
Description: After rebooting the SIM node and checkpoint restore, it is
observed that Peer to Peer between 2 SIM C300 nodes does not work.
Recovery: Restart the Primary Server.
Workaround: None.

17
2 ISSUES

1-WCPMRX Error Indication: Console CDA crashed after deleting OPCG & ICG.
Description : CDA on console station crashed, after deleting OPCG and
ICG. This may result in loss of view condition. The probability of this
occurrence is very low.
Recovery : Manual Start of EPKS Control Data Access service.
Workaround : None.
1-Y3OQTM Error Indication: You may see reverse videos on Display and may view
loss of trend values.
Description: During normal operation, the servers may lose view to the L1
network in a situation where an unresponsive component exists around
CDA Server. This may be because of a faulty device, too high
communication load. This may result in a loss of view condition.
Recovery: Remove the device/node that causes unresponsiveness or
reduces the communication load to be within spec. Stop/Restart EPKS
Control Data Access service.
Workaround: None.

CDA-Control Data Access

PAR Description
1-MXX9XL Error Indication: CDAsp on a SIM node stops responding if there are 10
or more SIM nodes configured on a single SIM node and all of them have a
p2p reference to Safety Manager.
Description: During loading CM's to SIM nodes which have a p2p
configured to Safety Manager, cdasp on the SIM node might crash if there
are 10 or more SIM nodes are created on the same node.
Recovery: none
Workaround: Do not configure 10 or more SIM nodes on a single
machine and all initiating
1-N2IKQ7 Error Indication: You may see reverse videos on display and may observe
loss of trend values.
Description: During normal operation, the servers may lose view from the
controllers under very high communication load situation. This may result
in a loss of view condition.
Recovery: Manual. Stop/Restart of EPKS Control Data Access service.
Workaround: None.
1-NE4TG3 Error Indication: Loss of View observed or Server failover is observed.
Description: If for any reason, the primary CF9 loses power and switches
over to the partner CF9, you may notice Loss of View to the controllers in
the cluster. In case of redundant Servers, you may notice that Server has
failed over.
Recovery: For non-Redundant Servers, restart the Control Data Access
Server service manually if not already running. For Redundant Server
setup, if Server has failed over, go over to the old Primary and restart the
Control Data Access Server service manually if not already running.
Workaround: None.

18 www.honeywell.com
 2 ISSUES

1-P9OBD9 Error Indication: The Server may lose data connection to the Controller
and result in LOV.
Description: If there are multiple controllers switching over
simultaneously, this will cause a burst of alarms to be regenerated which
may affect the data connection to the controllers that are not switching
over.
Recovery: Automatically recovers after few seconds
Workaround: None.
1-UNZ125 Error Indication: None.
Description: Removal of cable from QCS node will not be detected in
Experion station.
Recovery: Since this feature is not supported there is no specific recovery
mechanism. When you detect that the values do not get updated in QCS,
one way to recover is manual verification of the cables, ensure that the
cables are connected and working.
Workaround: None.
1-VK9U47 Error Indication: LOV observed and controller status shows red in
control builder.
Description: You may see reverse video for display data access, and
controller status shows red in Control Builder.
Recovery: Switchover the Server A where this issue is observed or you
must start the CDA server manually in case of permanent LOV observed.
Workaround: None.

C300 Controller

PAR Description
1-OBTIOP Error Indication: In Control Builder, C300 block is red but CEE block is
green. platform block parameters are not available.
Description: A network loop, possibly between two CF9s, is creating
excessive traffic, resulting in high CPU load, CEE/control parameter access
is given higher priority.
Recovery: Remove loop. May have to switchover or power cycle the
affected module.
Workaround: When performing network maintenance, be careful to not
connect cables between switches, especially CF9s, that create a network
loop.
1-OF7R1R Error Indication: Different communications are observed after powering
up a C300 controller.
Discription: Experion embedded nodes when powered up may not
properly detect duplicate IP Addresses. They will attempt to join the
network, and this willo disrupt communications with the other already-
running node(s). However, the FTE Status Display will correctly report
duplicate device index.
Workaround: Keep a record of assigned addresses to avoid duplicates..
Verify through the FTE status display that the intended device index is free.
Recovery: change the device index on the newly powered node and reboot/
power cycle it.

19
2 ISSUES

CEE-Database

1-SMAA33 Error Indication: CHECKBOOL.IN[1] parameter does not take input

when written through OPC gateway.
Description: This error occurs when flag block's input in ACE is connected
to a source like flag in C300 controller using OPC gateway.
Recovery: None.
Workaround: None.
1-VPKU61 Error Indication: DP_NUMBER parameter is not visisble on monitoring
side of ISO_5167_DUAL block.
Description: DP_NUMBER parameter is not visisble on monitoring side of
ISO_5167_DUAL block. There is no harm to control. Internally
DP_NUMBER parameter takes intended vlaue.
Recovery: None.
Workaround: None.

Control Builder-Fieldbus

PAR Description
1-107BU07 Error Indication: EPKS is unable to differentiate the case-sensitive units
like mpa & Mpa, Mg & mg.
Description: Experion displays selected units as Mpa and value is process
with unit mpa. Same is the case with other units which differs with case-
sensitive.
Recovery: None.
Workaround: None.
1-1ZQHZDT Error Indication: "Unspecified FMS Initiate" error message is displayed
while loading CM.
Description: When you triy to make Azbil FF device as the Link Master
the error is displayed.
Recovery: Acknowledge the message and try the workaround.
Workaround: Try keeping the FIM or other devices as Link Master.
1-1ZQHZJN Error Indication: Method Manager application stops responding.
Description: Method Manager stops responding while executing "Test Key
2" method of Sensor TB block.
Recovery: Kill the process using windows task manager (or) wait until
error info is generated. Clean the database locks to continue executing other
methods.
Workaround: None.
1-MDH0OZ Error Indication: Cannot use a block from one FF link in a CM on a
different link (6L.101.10746)
Description: It was observed, CM with FF device function block assigned
to FF link is not able to re-assign to any other CEE (like C300 or ACE) of
other controllers. But other way i.e from C300 to FF link working fine. And
CM under FF link is not able to un-assign as well.
Recovery: Acknowledge the error message.
Workaround: Create a new CM in the C300 and re-assign the FF blocks.

20 www.honeywell.com
 2 ISSUES

1-MW3V5X Error Indication: FFBlock from 1 FFLink can be Used in CM assigned to

other FFLink in a specific scenario.
Description: Reassigning the CM(Which is having FF device function
blocks) from c300 to FIM FFLink is allowed.But it must not be allowed.
Recovery: None.
Workaround: None.
1-OYOV8F Error Indication : Replacing FF device with identical FF device fails with
the following error "Device offnet".
Description : The replacement wizard will throw error saying
"EXPKS_E_NonExistentDevice (2L .101.3311)3051_1402_P1_7: Device
does not exist"
Recovery: Acknowledge the error.
Workaround: Attempt the replacement of the same device once again from
FF device replacement menu, Replacement is succeeded.
1-OYUXXR Error Indication: Device replacement fails saying device not found error
(Device off net).
Description: Device replacement fails saying device not found error
(Device off net).
Recovery: Acknowledge the error and close the replacement wizard
Workaround: Manually change the device tag and address before device
replacement/Perform second attempt of the same device replacement.
1-PAAF0B Error Indication: Trying to simultaneously load the same FIM from
different Control Builders may result in Load Failures.
Description: Multiple, simultaneous loads to the same FIM from different
Control Builders impacts the devices on the FIM Links when you attempt
to load.
Recovery: Multiple, simultaneous loads to the same FIM from different
Control Builders can have several unexpected side effects, including
inability to load, "device does not exist" error, "parameter not found in
database error", and device not seen in Control Builder.
Workaround: The best course of action is to attempt an immediate reload
of the failed block from a single Control Builder. There are several
warnings in both the Experion Standard Operating Procedures Guide which
states, "Maximum number of clients that can perform controller-related
database operations on the same controller at the same time: 1". Mutliple,
simultaneous you must avoid loading to the same FIM at the same time.
1-Q322Y2 Error Indication: FF Device delete operation from monitor view fails with
DB query execution error.
Description: Deletion of FF devices from Control builder monitor view
fails in database query execution error and all the devices showed in RED
from monitor view with error 7005.
Recovery: Close and re-open the Control Builder and reload the devices
from project view or forcedelete the devices from monitor view and load
again. But, 1st recovery option seems more appropriate to avoid any DB
inconsistencies and load the SR to proper state.
Workaround: None.
1-T9A7RI Error Indication: Method execution failure.
Description: Method Execution failure for Function blocks.
Recovery: None.
Workaround: None.

21
2 ISSUES

1-T9CEKR Error Indication: Method Execution Aborts.

Description: Method Execution Aborts for method "Test V Item" of
transducer block.
Recovery: None.
1-TGJO3P Error Indication: Method Execution Fails.
Description: Method Execution fails with "Built-in error" for some of the
methods in TMT 162 Rev2 device
Recovery: None.
Workaround: None.
1-TP28YN Error Indication: "Macrocycle exceeded limit" while try to load the a CM
with signal characterizes block of the device.
Description: "Macrocycle exceeded limit"
Recovery: None.
Workaround: None.
1-TVXKWL Error Indication: Reloading of FF FB having connection with SCM
forcing schedule in monitoring to NO_OPT.
Description: Reload the CM having FF AI function block having
connection with SCM is forcing the optimized schedule to Non-optimized
in monitoring database.
Recovery: Reload both SCM and CM together, this will bring back the
schedule to OPT.
Workaround: Reload both SCM and CM together, this will bring back the
schedule to OPT3/11/2013 5:24:02 AM, NRAMAIAH:Reload both SCM
and CM together, this will bring back the schedule to OPT
1-3E9JFPF Error Indication: Diagnostic Parameter values are not displayed for their
E&H Levelflex FMP5x FF device in Experion Control builder.
Description: Diagnostic Parameter values are not displayed for their E&H
Level flex FMP5x FF device in Experion Control builder.
Recovery: None.
Workaround: None.

Control Builder-Bulk Build/Edit

1-11SICGP Error Indication: Control Builder stops responding.

Description: While performing bulk edit operation, Control Builder stops
responding with Run time error.
Recovery: Close and re-open the Control Builder.
Workaround: None.
1-12Y56T9 Error Indication: Improper warning or failed error messages are observed
during save to ERDB operation of various workflow of Bulk Configuration
Tools.
Description: The error messages like Entry does not Exist, configuration
related errors are displayed with Failed status even though the save to
ERDB is successful.
Recovery: Ignore the improper errors with status as failed.
Workaround: Same as recovery.

22 www.honeywell.com
 2 ISSUES

1-3ILPKOZ Error Indication: HART channels are not displayed in the Bulk Edit list.
Description : Hart channels are not displayed in the bulk edit list. You
cannot edit the HART channel parameters.
Recovery : None.
Workaround : Use Bulk Configuration Tools->Bulk Edit work flow.
1-3JZ83JT Error Indication: Display of error message "Runtime Error R6025 - Pure
Virtual Function Call" during Bulk Edit on update Monitor of CHANNUM.
Description: The error is displayed due to an internal error that is causing
the issue. This issue is not reproducible on demand.
Recovery: Retry Bulk Edit.
Workaround: None.
1-3NHR0K1 Error Indication: "Save to ERDB failed error is displayed.
Description: If you do not specify the new channel names for the Replica
IOM in the configuration sheet, the existing channels in Typical IOM is
moved to the replica IOM.
Recovery: Reassign the channels to Typcial IOM using Bulk Edit.
Workaround: Provide new channel names in the configuration sheet so
that the new channels are created and assigned to new IOM.

Control Builder-Configuration Form

1-12RNGG1 Error Indication: When you perform controller migration you will be able
to close the Configuration Studio.
Description: While performing Migration of Controllers, closing of
configuration must be restricted. Closing of Configuration studio while
performing migration of controller leads to incomplete migration of
Controllers.
Recovery: None.
Workaround: You must not close the Configuration studio during the
migration of Controller.
1-1A4KN3Z Error Indication: There are two Error indications:
1. Control Builder stops responding
2. Two different IO channels with same number
Description: Two different IO channels of same IO module are showing
same IO channel number during Series C IO channel assignment, after the
strategies exported from TP 5.4 and imported in TP 6.1. Also one of the
channel still hold the last assign channel block name even though it already
unassigned. Control builder also got crashed when we were trying to assign
any of these two channels.
Recovery: None.
Workaround: None.
1-1T9HS0S Error Indication: No Units are showing for Bearing PV in the Control
Builder.
Description: Wireless Vibration Transmitter has a vendor provided units
for Bearing PV which are not shown/supported in the Control Builder.
Recovery: None.
Workaround: For you to check the ZFS user interface understand the
configured unit for Bearing PV.

23
2 ISSUES

1-3IK19PU Error Indication: Redundant FTEB is not created and redundancy

functionality is not available for imported FTEB.
Description: When a non redundant FTEB is created and is attempted to
convert to redundant then secondary FTEN is not created. Also redundancy
functionality is not available for imported FTEB. Assigning C200E
redundant module to FTEB sometimes creates the secondary controller as
unassigned.
Recovery: Create a new FTEB module as redundant instead of creating it
as non redundant and then converting it to redundant.
Workaround: Create a new FTEB module as redundant.
1-RZZXUB Error Indication: Maintenance Mode change is not reflected back in
ST800 DTM in FDM, when the change is done while the DTM
configuration is open.
Description: From Control builder for ST800 device, if the channel's
parameter 'PVSOURCE' is changed from AUTO to MAN, the display
shows 'Available for Maintenance'. Again change from MAN to AUTO, the
display removes the 'Available for Maintenance'. This is not updated in
DTM configuration form when you do the operation while DTM screen is
in open state in FDM.
Recovery: None.
Workaround: Before performing the required PVSOURCE change in
Control Builder, close the corresponding ST800 DTM in FDM. Once the
desired change is done, then re-launch the DTM in FDM to view the
change in Maintenance Mode.
1-UPBZT1 Error Indication: When entering base IP address with lowest octet other
than multiple of 10, then the address is replaced with lowest octet as
multiple of 10 and throws error message 12613.
Description: While entering the base IP address 10.66.51.128, CB is
throwing error message 12613. and the address is directly replaced by
10.66.51.130.
Recovery: Change the base IP address with lowest octect of multiple of 10.
Workaround: Configure the base IP address with lowest octect as multiple
of 10.
1-W92HO6 Error Indication : Local UDP Listeners has only 4 entries for C300 and
other FTE nodes.
Description: For C300 and other FTE node types, on its form, navigate to
"UDP/TCP" tab. You will see that for "Local UDP Listeners", there are
ONLY 4 entries. In C300, there are more than 4 that may be used and it is
impossible to see all of them. Even trying to use bigblue will not help since
the array index in the def file is set to 4, so, one will get an error trying to
read this parameter for index > 3.
Recovery: None.
Workaround: None.

24 www.honeywell.com
 2 ISSUES

1-Z3FUD5 Error Indication: Assigning CMs with particular CDB blocks to ACE/
C300 failing.
Description: After importing attached CM files, when trying to assign the
CM to C300/ACE it fails to assign and shows CDB not compatible with
execution environment.
Recovery: Since this happens only for particular CDB blocks, the below
compatible platforms must be added in CDB def xml file and then it can be
imported.
<CompatiblePlatform>C200</
CompatiblePlatform><CompatiblePlatform>C300</
CompatiblePlatform><CompatiblePlatform>SCE</
CompatiblePlatform><CompatiblePlatform>C200E</CompatiblePlatform>
Workaround:Add the below lines in exported CDB Block's def xml file
and then import it. Then it will allow CM to be assigned to C300.
<CompatiblePlatform>C200</
CompatiblePlatform><CompatiblePlatform>C300</
CompatiblePlatform><CompatiblePlatform>SCE</
CompatiblePlatform><CompatiblePlatform>C200E</CompatiblePlatform>

Control Builder-Batch

1-13BFFO7 Error Indication: Proxy CBR is not listed after the validation of Proxy
CBR. You cannot configure it manually.
Description: If you create and validate new Proxy CBR in local cluster (for
Newly created CBR in remote cluster), the Proxy CBR does not list in Unit
function reference point picker and it is not validated manually as well.
Recovery: Delete the proxy CBR from Control Builder and re create the
proxy CBR.
Workaround: Same as recovery.
1-WJV6I5 Error Indication: An orphan activity will be created in the orphan activity
summary display.
Description: After Terminal Stop command given to PROC layer Activity
and it finishes, UPROC layer Child activity is listed under orphan activity
summary. CEE and UPROC MR show activity associated with them too.
Recovery: Remove the orphan activity from the orphan activity summary
display. This will resolve the issue.
Workaround: None.
1-XFDMT9 Error Indication: No error displayed, The default value of new parameter
added in the phase block is not displayed in datablock.
Description: In Datablock default value is not populated for the newly
added parameter for a phase block.
Recovery: Open the PDE of phase block and deselect the Use Value
reference option and save the Phase block. then open the Datablock of
receipe. Observe that default value is displayed for newly added
parameter.then open the phase block in PDE and select the "Use value
reference" option and save the PDE
Workaround: None.

25
2 ISSUES

1-ZESYD7 Error Indication: Reverse video observed in Child RCM and Child SCM
detail display during ICPP runtime.
Description: It is observed that Parent navigation option does not exist
after navigating to Child detail display
Recovery: Go back to parent detail display through back button in Station
tool bar.
Workaround: None.

Control Builder-Load/Upload/Update

1-13TQQLP Error Indication : "Out Of memory pop up or Last minute catch of

unexpected exception in error logs is generated.
Description: Last minute catch of unexpected exception is displayed due to
excessive memory usage when lot of bulk database operations have been
done without closing Control Builder.
Recovery: Manually close Control Builder.exe via the Task Manager.
Workaround: Close and open Control Builder, then try to load the
strategies.
1-1RT7EKD Error Indication: SQLServer.exe consumes lot of CPU time on
performing Load With contents.
Description: If the number of strategies loaded exceeds the DFS spec, the
load dialog could become unresponsive for a prolonged time.
Recovery: Cancel the load and perform the load operation by selecting the
strategies in small numbers.
Workaround: Perform the load operation by selecting the strategies in
small numbers.
1-3EG37WV Error Indication : Error "Comm Path is not set up for secondary C300
Controller " displayed during load.
Description :This error occurs during the load of redundant C300
controller, but occurs ocassionally.
Recovery :None.
Workaround: Uncheck and check the "Module is redundant" option in
C300 main configuration form and try reloading.
1-3J99M63 Error Indication: Mismatch between QVCS version number and mismatch
in configurations on the IOModule between the project and monitoring
side .
Description: Revert to version & load of IOM is updating the version
only.But content remains same on monitoring.
Recovery: This can be recovered either by making the configuration
changes of the IOM in project side to match with monitoring side and then
reload the IOM . Or Delete the configuration changes which are different
from project side IOM I,e( by deleting the channel blocks from monitoring
side) and then reload the IOM.
Workaround: Do Not revert QVCS version of IOM when there is
configuration mismatch between project and monitoring .

26 www.honeywell.com
 2 ISSUES

1-3M63XJF Error Indication: Checkpoint restore operations failed entries in the

Control builder error log for specific IOM.
Description: Dataflow stops if checkpoint restore for specific IOM fails.
The checkpoint restore for specific IOM fails ocassionally.
Recovery: This can be recovered by Reloading the corresponding Output
channels or Reload the CM's Containing or referring channels.
Workaround: None.
1-3MCY1VN Error Indication: An error is prompted while loading the CEE " Too many
activities.Registration has been rejected".
Description: Load while active in CEE does not work after modifying the
no of activities on a loaded CEE and will require a re-load.
Recovery : Reload the CEE to get the correct statistics information updated
in CEE which will inactivate and activate the Control Strategies running
under that CEE.
Workaround: None.
1-SJ4W66 Error Indication: C300 synchronization fails.
Description: After loading a CM containing DO channels connected to
DEVCTL blocks, synchronization breaks between C300s when the IOM
containing the loaded DO channels does not exist.
Recovery: The C300 Synchronization will restart automatically and
complete successfully.
Workaround: To prevent this situation, do not load a CM containing DO
channels connected to DEVCTL blocks unless the IOM is present.
1-TNX8CL Error Indication: Control Builder crashes when trying to re-load a strategy
with dangling connection.
Description: Control Builder crashes when trying to re-load a strategy with
dangling connection.
Recovery: None.
Workaround: Remove the dangling connection and reload the CM.
1-3E4HHLP Error Indication: Controller will inactivate and re-activate CMs.
Description: During load of controllers having same device index across
clusters are loaded , it leads to the loaded controller inactivating and
reactivating the CMs in the other cluster.
Recovery: The Controller recovers automatically.
Workaround: Ensure same device index is not used across clusters for the
controllers.

Control Builder-Profibus

1-16JFE8J Error Indication: You are able to delete the first item from any grouped
modules when there is a DSB associated with that NETTAG.
Description: It must give an error popup message (for example, "You have
made a change to I/O definitions that has PDC references in the Control
Application.") when you try to remove an item from the grouped modules
when there are PDC references. Currently it allows to remove the first item
from the group where as it works as intended when deleting other modules
than the first one.
Recovery: Re-configure the modules
Workaround: Re-configure the modules

27
2 ISSUES

Control Builder-Delete

1-1A27Z5V Error Indication: Cannot force delete the offline device from monitoring
tree
Description: Unable to delete OW Adapter device from CB tree
monitoring when the device is in offline state. 'Force Delete' option does
not appear for OW Adapter device which is in offline state.
Recovery: Check if device is powered off or run out of battery.
Workaround: None.

Control Builder-Chart

1-1A58B5B Error Indication: IOP details are missing for PMIO channels.
Description: After assigning unassigned channels multiple times in CM
Loaded C200 with IOLIM and PMIO shows IOP details are missing on the
assigned channels.
Recovery: None.
Workaround: None.
1-1P915L9 Error Indication: After adding a phase block with function reference into a
Master Recipe chart, saving the Master Recipe, closing and opening the
Master Recipe again sometimes crashes Control Builder.
Description: After adding a phase block with function reference into a
Master Recipe chart, saving the Master Recipe, closing and opening the
Master Recipe again sometimes crashes Control Builder. Opening Control
Builder again and opening the same Master Recipe chart will work.
Recovery: Open Control Builder again and open the Master Recipe chart
again.
Workaround: None.
1-Q2XSJX Error Indication: Chart Visualization displays in Point detail displays
sometimes take 10-20 seconds come up.
Description: Chart Visualization displays in Point detail displays
sometimes take 10-20 seconds come up.
Recovery: None.
Workaround: Open the monitoring side charts from Control Builder for
the same point to view the details.
1-3L4KQ9D Error Indication: In certain scenarios REF parameter defaults to UDT
template name.
Description: Manual configuration of REF parameter.
Recovery: Re-enter correct REF value.
Workaround: Use Point Picker to enter REF value rather then typing
manually.

28 www.honeywell.com
 2 ISSUES

Control Builder-Change Parent/User Defined Template

1-1PQWSTZ Error Indication: Duplicate phase block created due to change parent in
specific scenario.
Description: Change Parent operation for phase block creates duplicate
copy in the chart.
Recovery: Delete the duplicate phase block.
Workaround: Delete the duplicate phase block.
1-3Q0K7WY Error Indication: On performing Change Parent(CP) of UDTCM1 to be
the child of UDTCM2 both configured with old style channels AIChannel-
>PID->AOchannel blocks, CP fails with unexpected error in case there is an
instance for the UDTCM1 and if there is no instance, then shows error
"Existing background connection exists...".
Description: Doing a change parent operation between two UDTs
containing Channel blocks throws an error.
Recovery: None.
Workaround: None.

Control Functions - Continuous

1-1VV0U7L Error Indication: OVRDSEL block does not propagate override

initialization correctly in some configurations when cascaded with another
OVRDSEL block.
Description: The issue is manifested when the strategy has cascaded
OVRDSEL blocks (to support more than four inputs in override selection
strategy). When an upstream OVRDSEL is not selected by a downstream
OVRDSEL block, all of the non-selected block's inputs must be subject to
override feedback initialization. The issue is that all inputs of the non-
selected OVRDSEL block except the locally selected input experiences
override initialization.
Recovery: None.
Workaround: None.

Checkpoint

1-286ELKP Error Indication: Checkpoint Service stops responding.

Description: While performing stability run with auto checkpoint tasks
scheduled, checkpoint service crashed after long run.
Recovery: Automatically checkpoint service gets restarted after the crash.
Workaround: None.
1-2BCAB6J Error Indication: Checkpoint service stops responding.
Description: Checkpoint services.exe crashed during stabilty run of HTS-
PC -SYS1 (R430 TP8.1 Tools patch-3c.
Recovery: Automatically checkpoint service gets restarted after the crash.
Workaround: None.

29
2 ISSUES

1-TK8YFP Error Indication: Checkpoint file is in "Incomplete state".

Description: After loading a contoller with CMs configured, restore
window is showing checkpoint file is in incomplete state
Recovery: Perform a manual checkpoint Save and try again the checkpoint
restore operation.
Workaround: Perform a manual checkpoint Save and try again the
checkpoint restore operation.
1-3OYICAZ Error Indication: Increase of private bytes of checkpoint service observed
in perfmon tool.
Description : This issue will be encountered in large system set up running
over a prolonged period.
Recovery : Restarting the checkpoint service will free the private bytes.
Workaround : None.

Control Builder-HART

1-3ILPL1F Error Indication: An issue is observed in listing Smart Channels in

Synchronize Maintenance Mode dialog.
Description: When you log in through local Engineer account, Synchronize
Maintenance Mode dialog does not list Smart Channels and clicking on the
dialog throws exception.
Recovery: Close the Control Builder and open Synchronize Maintenance
Mode dialog from Administrator account.
Workaround: Open Synchronize Maintenance Mode dialog from
Administrator account.
1-3IW5W4I Error Indication: Synchronize operation in Synchronize Maintenance
Mode dialog fails.
Description: When IOM switchover is in progress, Synchronize operation
of Maintenance Mode dialog is failing.
Recovery: Close the Maintenance Mode dialog, wait for IOM switchover to
complete, then Open Maintenance Mode dailog and do Synchronize.
Workaround: Perform Synchronize operation in Maintenance mode dialog
once IOM switchover completes.
1-3LZALJS Error Indication: Enabling of "Enable Auto Detection" feature throws
"Configuration mismatch" error.
Description: After loading HART IO channels, Enabling of "Enable Auto
Detection" checkbox from HART Status tab of IOM Properties from
monitoring side throws Enabling of "Enable Auto Detection" error message.
Recovery: Close the error message and proceed.
Workaround: None.
1-SHYPIT Error Indication: FF and Hart DD import function is not working with
Engineer login.
Description: It was observed FF and Hart DD import is not working with
Engineer login. If I click on DD import icon it throws an error Failed to read
FF attributes SQL database from server .
Recovery: None.
Workaround: None.

30 www.honeywell.com
 2 ISSUES

Control Builder

1-G3WCZ1 Error Indication: When attempting to enable/disable FF maintenance

alarms from chart tabs in Station:- checkbox values may not change unless
you change the tabs and return. Some bit checkboxes may fail to get
enabled.
Description: See error indication.
Recovery: See workaround.
Workaround: Open the equaivalent tab in Control Builder monitoring side
and enable/disable maintenance alarms there.
1-I3GBVR Error Indication: When system was idle for hours after opening CM in
Console, stops Responding Control Builder.
Description: Chart View of control builder is opened for 10 CM's in
console with 3 GB RAM. Keeping system idle for three hours crashes
control builder automatically. System was in base load with cycles scripts
running.
Recovery : None.
Workaround : None.
1-LH4MXJ Error Indication: While importing the database (corrupted) having phase
block without library name, it throws error while importing.
Description: While importing the database (corrupted) having phase block
without library name, it throws error while importing, a phase block with
empty library name is created in database.
Recovery: Contact TAC team to get the script to fix this issue for the
particular build.
Workaround: Run ECC before migration, if any phase block without
library name is present in the database is listed out. - contact TAC team to
get the script to fix this issue for the particular build.
1-O3WK4X Error Indication: The Remote Shed option "Normal Shed, No Return"
option does not work in Cerabar_S 05 Rev.
Description: The Remote Shed Option "Normal Shed, No Return" of PID
Block of E&H Cerabar_S Rev 05 sheds to Actual Mode "AUTO" and
Target Mode "AUTO" when the intended behavior is Actual Mode "CAS"
and Target Mode "CAS". The normal Mode "CAS" is selected. Actually
when this option is selected, in case of a failure of remote input (RCAS_In
or ROUT_In) the next lower priority Non-remote mode must be selected as
target than the actual mode.
Recovery: None.
Workaround: None.
1-PJDOPP Error Indication: In CB/RB while generating report(Paginated Text) for
SCM/RCM with a same name(an existing report name) an eror is generated
"Crystal Reporting Export: File I/O error".
Description: In B/RCM while generating a report(paginated Text format)
for RCM/SCM/MR with a same name(already on report with a file name
exist in same path). It generates a error "Crystal Reporting Export: File I/O
error"
Recovery: NONE
Workaround: You can provide a different file name for the report
generated while saving or you can change a directory path for the given file
name. This issue can be avoided by giving a new file name or changing the
directory path of the report.

31
2 ISSUES

1-PM89OX Error Indication: PVSOURCE option is not grayed out in PA channel

instances even though all options including PVSOURCE parameter is
defined in PA channel template.
Description: PVSOURCE option is not grayed out in PA channel instances
even though all options including PVSOURCE parameter is defined in PA
channel template.
Recovery: None.
Workaround: None.
1-QLJ7FD Error Indication: Few methods are not working in Magnetrol TA2 Rev1 in
R400.2 TB
Description: Following Methods are not working for Transducer Block(a)
Zero Power Test.(b) Low Cal Validation.(c) High Cal Validation. The
method will keep on running endlessly in the Experion host with no results.
Recovery: None.
Workaround: None.
1-RDTD13 Error Indication: Method manager fails to execute the methods.
Description: Method manager fails to execute the methods.
Recovery: None.
Workaround: None.

Control Builder-Load

1-KKLCSZ Error Indication: Reload of a loaded C200E causes "unexpected error" to

be shown.
Description: During the load of C200E this error is shown occasionally.
Recovery: Close the error dialog and reload.
Workaround: None.

Control Builder-System Repository

1-PV3SMT Error Indication: Peer-to-peer communication between CEE controller and

Experion Server points (SCADA, DSA, TPS, OPC, OPC Advanced point)
fails with NaN values.
Description: If a server with incomplete information in System Repository
(System Repository sync state can be observed from Server Redundancy
page) takes over the Primary role then, there is a high likelihood to lose
Experion Server points information in System Repository resulting in peer-
to-peer communication failures between CEE controller and Experion
Server points.
Recovery: None.
Workaround: None.
1-Y390VS Error Indication: When QCS subsystem tries to validate points in Server
through SR at a high rate, failures are seen.
Description: When QCS subsystem tries to validate points in Server
through SR at a high rate, failures are seen.
Recovery: Do a Stop and Start of Experion Server from "Start-Stop
Experion PKS Server" tool to recover.
Workaround: None. Lowering the number of non CEE point handle
requests to SR per second would avoid this.

32 www.honeywell.com
 2 ISSUES

Control Builder-Assign

1-TETYQT Error Indication: The Print Preview is crashing the Control Builder.
Description: In Experion R410.1 , The Print Preview is Crashing the
Control Builder. This is happening only when Macrocycle chart view
(double click on the segment) is opened and Print Preview is clicked.
Control builder crashes both from Monitoring and Project side. also the
Print option does not print any details or chart regarding Macrocycle (both
monitoring and project side).
Recovery: None.
Workaround: None.

Control Builder-Search

1-UXS811 Error Indication: Display of error message "Search will be aborted due to
server connection timeout error" during simultaneous execution of Where
Used Search and Online Data Search from Configuration Studio on the
Primary server.
Description : The error is displayed since the services "Experion PKS
Browser Orchestration" and "Experion PKS Browser Support Service" are
stopped in the Primary server on which the search is executed.
Recovery : Restart the services "Experion PKS Browser Orchestration" and
"Experion PKS Browser Support Service" on the Primary server.
Workaround : None.

Control Kernal

1-XGHDCZ Error Indication: An alarm generated from CAB function block may
appear active in Station, though it is in normal condition. This can be cross
verified by monitoring faceplate of the CAB function block.
Description: If an active alarm generated by CAB function block is returned
to normal condition while C300 switchover is in progress; there is
possibility that this particular alarm still appears as active in station.
Recovery: Toggle ALMENBSTATE parameter of CM containing CAB
function block. This will trigger a re-notification of alarm state to station.
Workaround: None.

Control Builder-Point Picker

1-ZA0E2F Error Indication: HMIWeb Display Builder stops responding.

Description: HMIWeb Display Builder stops responding when ActiveX
Control-Textbox is placed on Display.
Recovery: None.
Workaround: None.

33
2 ISSUES

EIP-COMMUNICATION

1-11RAB1P Error Indication: 3 to 5 seconds delay in establishing connection to the

EIP IO's on reloading the EIP IO's from monitoring side.
Description: This delay is not easily visible, and happens only if there is
some EIP IO on the monitoring side which is not powered up or not present
on the network.
Recovery: Automatically recovers.
Workaround: None.

Embedded Controller/Gateway Platform

1-1LSBQ9M Error Indication: After switchover or power cycle, a C300, FIM4, FIM8 or
PGM2 pair stops communicating.
Description: An unknown condition has caused a duplicate IP Address
situation that shuts down network communications. The node display of one
or both may show "DUP". CTools may show one or both nodes at the same
IP Address.
Recovery: Warning: You may lose your configuration and have to reload
from Control Builder. Power cycle the backup of the pair and wait to see if
the condition clears. If it does not, then power cycle the primary. If this does
not clear the problem, power cycle both together. Contact the Technical
Assistance Center and report the problem.
Workaround: None.
1-2ED9BQB Error Indication: Loss of communication with Ethernet/IP device.
Description: Any break in the communication path to a singly-attached
device may take up to a minute for FTE to resolve, if there is an alternative
path.
Recovery: An alternative path is resolved and the connection is restored
after a minute.
Workaround: None.

Enterprise Model Builder

1-BBESLV Error Indication: Assets can be downloaded to Server by you without

having engineer access.
Description: Same user name has been used to create user accounts on two
different servers. The privileges provided to you is different in both servers.
In one Server ( Server1) you have Engineer privilege whereas in the other
server (Server2) you do not have Engineer privilege. Adding both Servers to
the system of Server1, the system model or assets model can be downloaded
to both the servers.
Recovery: Ensure that the user accounts having the same user names in
different servers have the same privileges.
Workaround: None.

34 www.honeywell.com
 2 ISSUES

1-J3B3SH Error Indication: In a dual primary scenario while migrating form R400.1
to R410.1 release, the Assets or Alarm Groups configuration builder
launched from ServerA indicated that the connection is made to the primary
server. The OPM status is indicated in the status bar. However instead of
indicating secondary server the status bar shows that the connection has
been made to the primary server.
Description: In a dual primary scenario while launching the Assets or
Alarm Groups Builder, it is expected that the status bar on the right bottom
corner must indicate OPM and Secondary Server connection status. In this
scenario you see a primary server connection indicated on the status bar. In
this scenario, the configuration change is not allowed at this time as the
OPM status is enabled. This is a cosmetic anomaly and you can ignore the
indication on the status bar.
Recovery: None.
Workaround: None.

EBM-Controller

1-NDXIBN Error Indication: Loss of inter-community peer-peer communications.

Description: Powering down the top-level yellow switch disrupts
communications through the level 2.5 router.
Recovery: Correct network condition.
Workaround: None.
1-3KNG8RZ Error Indication: EXECSTS of transition block does not reflect the current
status of transition block.
Description: EXECSTS of transition block is stuck on previous bad status
and does not return the current status of transition block even if the bad
condition is return to OK.
Recovery: None for activity or class based recipe. For instance based recipe
running without activity, inactive the recipe block and reactive the recipe
block.
Workaround: Use either SO of transition block (for example,
scm_name.transtion_name.so) or EXECSTS of the specific condition
(scm_name.transition_name.c[1].execsts) in required evaluation.
1-NW1WPL Error Indication: No error is displayed to the user. An RCM starts running
like it has acquired equipment properly when in fact it hasn't.
Description: An RCM is configured to acquire a UCM. The RCM is started
and acquires the UCM. The UCM is inactivated and deleted. The RCM is
aborted, inactivated, activated, and started. The RCM does not try to acquire
the UCM again before it starts. In this case it cannot acquire it because the
UCM was deleted.
Recovery: None.
Workaround: Once the RCM is inactivated, reload it before you activate it
again.

35
2 ISSUES

1-PK1QJ5 Error Indication: After performing freeze and switchover , when a new
activity is created and started, it is struck in Acquiring Resource in Pre-Exec
State.
Description: When an OPM is performed on a controller having an MR
with multiple CR's running, the old CR's get removed as expected but after
OPM newly created Activities are not executing, they are struck in Pre-Exec
state with Acquiring Resource as Info.
Recovery: None.
Workaround: Remove the CR. Inactviate and Actviate the MR then Create
a new CR.
1-3QM82LT Error Indication: A step block displays an error of 2447 when trying to set
a unit.
Description: You are unable to select a unit.
Recovery: Abort the strategy.
Workaround: None.
1-LU37LJ Error Indication: You may observe that some activities you thought you
created do not show up in the activity summary display. The same activity
detail display may update from multiple activities which may cause
incorrect to be presented.
Description: Scenario:-
RCM_1 is running and it is acquired (either by another recipe or an
activity).
RCM_2 is trying to acquire RCM_1 (RCM_2 is in RCM_1s arbitration
queue, or listed as an un managed conflict). Idle->Cold start the controller.
Command RCM_1 to start. RCM_1 will reuse its Activity ID.
Recovery: There are no user steps for recovery. Once RCM_1 is run a
second time after the cold start, the problem will correct itself.
Workaround: Do not idle the controller when RCMs/SCMs are not in a
terminal state.I.E. Do not idle the controller when RCMs are in the running
state.

EBM-Tools

1-NS6M1L Error Indication: Load operation fails to load or does not give any error for
the updated range values of formula parameters in Data block/phase block.
Description: Loading of an RCM configured with the phase block having
invalid range values for its parameters does not give any errors and the
updated values are not reflected on monitoring side.
Recovery: None.
Workaround: None.
1-O0GF6A Error Indication: Key parameters in Table view display.
Description: When batch is executing across clusters such as parent and
child are in different clusters, the key parameter in table view of the parent
recipe that display child recipe key information could display.
Recovery: N/A.
Workaround: You must click the blank area which is right above key
parameters. This allows you to navigate to the child recipe detail Display
which displays all the information of the child recipe including the key
information.

36 www.honeywell.com
 2 ISSUES

1-PADH2J Error Indication: Running SCM after CP Save/ Restore after LWA of Alias
may result in harmful effect.
Description : When LWA is performed for SCM/RCM in active state and it
has changes to selected instances in alias table, then selected instances are
not loaded but the values in checkpoint are updated. CP save and restore
after that may point to the new values.
Recovery: For such scenario, when LWA is performed for SCM/RCM in
active state and it has changes to selected instances in alias table, perform
Checkpoint Rebuild after LWA
Workaround: After CP rebuild, CP save and restore works properly.
1-UMLIDH Error Indication: Proxy blocks are not listed from different release servers.
Description: ICP2P is not supported on two different releases during
configuration time due to GCL connection limitation.
Recovery: None.
Workaround: None.
1-VIAD8V Error Indication: The number of activities shown in CEE statics Tab is
different from the number of activities shown in Batch tab of CEE.
Description: The NUMACT value as seen in the Batch Tab of the CEE
shows a mismatch with the CEE-Activity Staistics -TOTALACTCAP.
Recovery: Reload the ACE node in server.
Workaround:Same as Recovery.
1-ZX2IMV Error Indication: C300 controller and FTEB CPUFREE goes down by
7%-8% when UT is running
Description: C300 controller and FTEB CPUFREE goes down by 7%-8%
when UT is running. This issue is observed for all C300 controller and
FTEBs when executing Readiness Check of the controllers/chassis.
Recovery: None.
Workaround: None.

Fieldbus Library Manager

1-OMCM9H Error Indication: "Store Echo curve of the Setup" method fails to execute
for Vegapuls FF device.
Description: "Store Echo curve of the Setup" method fails to execute for
the following Vegapuls Rev 6 Devices and crashes Methods manager.1)
Vegapuls 612) Vegapuls 623) Vegapuls 634) Vegapuls 655) Vegapuls 666)
Vegapuls 677) Vegapuls 688) Vegapuls SR 689) Vegapuls WL 68
Recovery: Clear the ERDB lock and Invoke the Methods manager again
and do not execute "Store Echo curve of the Setup" method.
Workaround: None.
1-Q407YH Error Indication: Scroll bar is not available & Get string value built-in
method is not supported.
Description: In Method manager, for drop down menu if menu more of
option then user has to use scroll bar to scroll down or up, but scroll bar is
not available and Get string value built-in method, Experion in unable to
read the parameter.
Recovery: None.
Workaround: None.

37
2 ISSUES

1-R3X0ZN Error Indication: Flow Units and User Units of the Transducer block
displays unit as "Kbytes".
Description: Which is "Kbytes" for "1599".
Recovery: None.
Workaround: None.

Fieldbus Interface Module

1-PAPV2D Error Indication: Changing the address or TAG for Un commissioned

device is resulting in inconsistent behavior.
Description : Changing the TAG name and address for two
uncommissioned devices with same TAG name and temp address is
showing inconsistent behavior as devices end up with same TAG name and
address.
Recovery: Following steps were followed to recover the state:
1. Remove one of the problematic device.
2. Configure and reload the other device.
3. Then connect the first device and reload it.
Workaround: This issue is observed following issues with other operation.
After following steps to recovery, it is not observed.

Fieldbus Interface Module-Series C

1-Y3T5WR Error Indication: Some ST800 Resource block parameters not updating in
FDM.
Description: Some Resource block parameters on the ST800, including
Simulation Active and Write Lock, will not reflect updates in FDM if the
value changes on the device. If the DTM on FDM is connected to the
Device then these parameters will also not appear to update in the Control
Builder block configuration pages.
Recovery: Values update correctly in Control Builder if the DTM is not
connected to the Fieldbus device. Close the DTM on the FDM and monitor
static parameters through Control Builder configuration forms only.
Workaround: When enabling Simulation or changing Write Lock of the
ST800, close the DTM on the FDM and verify the changes to these
parameters through the Control Builder block properties page.

IEC61850_Embedded

PAR Description
1-3KPXXJX Error Indication: After the first read request error 6520-6530 is displayed.
Description: The provided SCL file does not match the IED.
Recovery: The Physical device must be unloaded and the correct CID file
must be loaded.
Workaround: None.

38 www.honeywell.com
 2 ISSUES

PAR Description
1-3OZ2O8L Error Indication: Data takes longer than 6 seconds to refresh
Description: Data takes longer than 6 seconds to refresh, due to some
network issue.
Recovery: 850M recovers on its own.
Workaround: None.
1-3OGBUW7 Error Indication: Secondary 850M fails with error 0x00d2 while reloading
multiple IEDs (more than 13 IEDs at once).
Description: While reloading multiple IEDs from project view after
making changes, sometimes, 850M secondary fails with error 0x00d2. This
failure is observed only when you reload multiple devices in a single load
operation and is not observed during single device reload. Reloading
multiple IEDs at once results in improper stack fragmenting which may be
a major contributing factor to this failure.
Recovery: Reboot the failed 850M module.
Workaround: Reduce the number of IED devices getting loaded in a single
load operation or maintain more than 4.0 mb driver reserved free memory
of 850M.

Profibus Interface Modules

1-1275R3B Error Indication: On removal and re-insertion of Profibus cable from both
primary and the secondary PGM, output channels become bad in TURCK
and SiemensET200M DSB.
Description: When Profibus cable is removed from primary PGM,
switchover is initiated and when the Profibus cable is again removed from
the new primary also all the outputs will go bad and is expected. But when
the cable is reconnected on both the PGM's, output channels remain bad
and does not recover.
Recovery: It does not recover automatically.
Workaround: Perform PGM Switchover, all the output channels become
good.
1-1WK0AHV Error Indication: During PGM Switchover if a channel goes BAD then all
the channels in the grouped PDC will go BAD.
Description: Upon PGM switchover, just after the secondary takes over the
role of Primary and the new secondary is still coming up, at that time if a
channel goes bad, then all the channels in that PDC become BAD.
Recovery: Perform PGM Switchover.
Workaround: None.
1-3HBNUST Error Indication: After loading link1 master shows as offline with number
of configured slaves as zero. Connecting to PGM master in SYCON, error
message in link1 shows Timeout while resetting Profibus.
Description: This is observed in testbed with 125 slaves configured on
each link with lots of simulated slaves. Happens only during load so not
very critical.
Recovery: Reboot PGM2,. Switchover PGM in case of redundant PGM. In
non redundant case reboot PGM and load.
Workaround: None.

39
2 ISSUES

1-3NEJNEZ Error Indication: Negative enumeration values larger than ENUM64

supported by IEC61850 are not read by Control Builder.
Description: TYPECONVERT, PUSH and other blocks only support
enumerations from 0 - 63.
Recovery: None.
Workaround: You must use SCM steps and transitions to read these values
or cab blocks.

IXP-Import Export

1-1L2XTPG Error Indication: Error appears as "An unexpected error was encountered"
in QVCS window.
Description: This issue appears in ERDBs migrated from releases before
R310.2, with strategies having duplicate FF IO channel names, which are
checked in QVCS. When you do a revert operation for the channel or CM
from a newer QVCS version to older version, then error appears as 'An
unexpected error was encountered" in QVCS window.
Recovery: Acknowledge the error. Keep the strategy or IO Channel in the
source QVCS version itself.
Workaround: Delete the strategy from monitoring side, re-configure to
older QVCS version.
1-28C3M4F Error Indication: After DD import(FF\wireless) QVCS checked in
strategies are editable.
Description : Checked in Control modules (having referece to FF blocks)
become editable after performing dd import of the same FF device.
Recovery : Close and reopen Control Builder.
Workaround : Close and reopen Control Builder.
1-3IWH9K7 Error Indication: Problem is observed after import of CM using
IXPTOOL.exe, block connections are missing.
Description: Export a CM using IXPTOOL.exe.Export is successful. After
the Export delete the CM in Control Builder. Import the exported CM using
IXPTOOL. Import is successful but when the chart is opened the pin
connections in the CM is lost.
Recovery: Import using Control Builder.
Workaround: Import using Control Builder.
1-VM137H Error Indication: Error appears as "Entry does not exist
[EXPKS_E_CL_ENTNOTEXIST (4L .101.10020)].
Description: When we have a tagged basic block which is an embedded
child in a CM (for eg: HART AO BLOCK with Hart enabled, embedded
and assigned in a CM), importing another CM with an assigned HART AO
with the same name fails and connection to the HART AO Block is lost in
imported strategy. Error appears as the import failed and there is a name
conflict for child blocks.
Recovery: Acknowledge the error. Re-configure the imported strategy with
non-conflicting IO channel name and assignment.
Workaround: Ensure that there are no name conflicts within child blocks.
Need to check the IO Channel names in CMs, correct it before import if
possible.

40 www.honeywell.com
 2 ISSUES

1-WQUL43 Error Indication: Error appears with error code

"EXPKS_E_IXP_EXPORTBLOCKTYPEFAILED (4L .101.14231)" on
Exporting HART template.
Description :HART IO templates failed to export with an error code on
Exporting HART template.
Recovery: Acknowledge the error by clicking OK.
Workaround : Close the control builder and reopen once the import
operation is completed.

I/O-Serial Interface

1-1PRRY9P Error Indication: Value in device is overwritten by value on Serial Array

Channel block.
Description: The Series A Serial Interface IOM does not support writes
made directly to the device and not through the Serial Array Channel block.
If a Serial Array Channel is configured with WRITEOPT as "Write on
change" and the value in the device is directly changed, the SI IOM will
detect the difference and attempt to update the value in the device with the
value on the Serial Array Channel input.
Recovery: No recovery is required. The value in the device will match the
value on the Serial Array Channel.
Workaround: If the value in a device must be different than the last value
written through the SI Array Channel block then either:
Inactivate the Serial Array Channel and update the value directly in the
device.
or
Change the value on the Serial Arrary Channel and allow the SI IOM to
update the value in the device.

41
2 ISSUES

Series A IO Modules

1-2IAI1H5 Error Indication: PID connected to Series-A AI or AO sheds Mode on

switchover.
Description: If the following actions occur while using the topology of a
C300 controlling Series-A I/O through an FTE Bridge module in the I/O
chassis and if a Serial Interface Module resides in the same chassis as other
Series-A I/O Modules:1) Multiple Serial Interface I/O module blocks are
configured to map to the same physical Serial Interface Module in the I/O
chassis by using the same FTE Bridge Name and IOM Slot Number.2) Both
Serial Interface I/O module blocks are loaded to the C3003) A switchover is
performedThen on switchover there may be a momentarily loss of
communication between the C300 and other Series-A I/O modules which
reside in the same chassis as the FTE Bridge and Serial Interface Module. If
a PID block is providing a process value to the Series-A I/O channel this
loss of communication may be observed by the Mode of the PID block
shedding to Manual.No warning or error is raised during the configuration
or load operation of the Serial Interface Module blocks.
Recovery: Perform all of the following steps:
1. Delete all Control Modules containing Serial Array Channels assigned
to both of the Serial Interface Module blocks.
2. Delete both the Serial Interface module blocks.
3. Note: Only one Series A IO Module block may be configured to map to
any one physical Series-A IO Modules.
a. Identify the correctly configured Serial Interface Module block.
b. Load the correctly configured Serial Interface Module block.
c. Load all Control Modules containing Serial Array Channels
assigned to the correctly configured Serial Interface Module block.
4. Switch off power to the I/O chassis containing the FTE Bridge and
Serial Interface Module5).
5. Perform a Checkpoint Restore to the C3006).
6. Switch on power to the I/O chassis containing the FTE Bridge and
Serial Interface ModuleFor verification of the recovery perform a
switchover of the C300 and verify the connection is not lost to the other
Series-A IO modules in the chassis.
Workaround: To avoid a momentarily loss of connection to Series-A
Chassis I/O and possibility of a Mode shed while using the C300 to Series-
A Serial Interface Module through FTE Bridge topology take the following
precautions:
1. Before loading Serial Interface Module blocks to a C300 verify the path
configuration details are not identical to any currently loaded Serial
Interface Module blocks.
2. If all the actions have occurred except a switchover has not yet been
performed follow the steps identified in the Recovery.

42 www.honeywell.com
 2 ISSUES

Profit Loop Assistant

1-3KWWNT3 Error Indication: Exp R430, Profit Loop, Step Testing Bug in Level Loops
Description: When step testing level loops (i.e. integrators) there is a
problem if you change parameters which effect the future signal generation
(PRBS signal). In this case the SP of the loop gets set to match the OP of
the process for a single interval and then resumes its step. This can cause a
large spike in the SP to the loop if there is a large mismatch between the SP
and OP of the loop. This is a problem if any of these parameters are
modified during a test: upper/lower bounds of step, estimated response
time, move filter.
Recovery: None.
Workaround: Do not modify any of the following parameters during a test:
upper/lower bounds of step, estimated response time, move filter.

Table View

1-F8BHKD Error Indication: Trendparameter for SCM is not displayed in mini trend
display in the station.
Description: Trendparameter for SCM is not displayed in mini trend
display in the station.
Recovery : None.
Workaround : None.
1-HI1PMN Error Indication: When Report and Formula parameter is printed for
RCM, the report does not show the correct value.
Description: When Report and Formula parameter is printed for RCM, the
report does not show the correct value.Printing the report and formula
parameters, does not prints the current value.
Recovery: None.
Workaround: None.

PGM

1-I1C2F3 Error Indication: CPULoLo Resource and CPU Lo Resorce Alarm is

popping while loading DSB's.
Description: CPU Low resource and Low Low resource alarm is popping in
station while loading 5 or more DSB's together as well as during the PGM
switch over.
Recovery: None.
Workaround: Load DSB blocks in small groups or one by one.

43
2 ISSUES

1-MUCYTT Error Indication: Wrong channel status is observed in PDC on PROFIBUS

network cable disconnect & reconnect with DP/Asi link offline.
Description: Basically what is happening here is that DP/Asi link is made
offline and then PROFIBUS network cable is disconnected from the device.
When the DP/Asi link is made offline all the channel status shows Bad.
Now when the PROFIBUS network cable is disconnected and reconnected
few channels statuses are showing good which were actually Bad earlier.
Recovery:
If the DP/Asi Link is made online the channel statuses show up correctly.
or
Perform PGM Switchover.
Workaround:
Perform PGM Switchover.
or
Make the DP/Asi link online.
1-WDNURN Error Indication: When there is FTE cable disconnect and reconnect, and
when the "HoldOnFailure" is not selected for the outputs, the outputs are not
initialized with the CHINIT values for the output channels.
Description: When the FTE cable is disconnected and reconnected and if
the Hold On Faliure option for the outputs is not enabled, then the Init
values provided in the CHINIT parameter will not be written to the outputs
upon FTE cable reconnect.
Recovery: None.
Workaround: Hold On Failure option must be used to hold the outputs, the
feature of back initializing the outputs with the CHINIT values can not be
used for Drives.

Rockwell Network

1-11H1RD1 Error Indication: RsLinx does not show the Series A IO/SIM Card with
Module Icon.
Description: RsLinx application does not show the Series A IO/SIM Card
with Module Icon.
Recovery: None.
Workaround: None.
1-13QB7PX Error Indication: RsLinx automation tool fails when executed.
Description: RsLinx Automation doesn't stop the required services and
throws error
Recovery: None.
Workaround: Manually stop the Experion Server logger service from
Services.msc application and then re-run this tool. After stopping this
service RsLinx Automation works fine.

44 www.honeywell.com
 2 ISSUES

Standard Series C IO Modules

1-11VNY3X Error Indication: A "Device PV Range Mismatch" alarm is reported.

Description: When any PV Range extent has a non-whole number value, a
"PV Range Mismatch" alarm is reported when one does not exist.
Recovery: None.
Workaround: Avoid using decimal values for PV Range extents.

FF-Configuration

1-123KRXP Error Indication: "VCR Limit exceed" error is displayed while loading
Fieldbus device
Description: VCR limit exceed error while loading.
Recovery: Acknowledge the error.
Workaround: Cross check if the connections are done within the limitation.
if not, try to delete the block and recreate the required connections.
1-14E2RC8 Error Indication: None.
Description: Control Builder allows to un-assign even if the device is
loaded.
Recovery: None.
Workaround: Ensure the device is not loaded before making any changes in
the Project side.
1-3PF1Q5L Error Indication: When user executes Read Echo Curve method for
Honeywell GWR level transmitter SLG700, graph does not get plotted.
Description: The data is not fetched from the Auxillary transducer block for
this device while executing the method in Experion.
Recovery: None.
Workaround: None.

ModBus TCP Blocks

1-3KTUVO9 Error Indication: C300 PCDI CM array Error flag does not turn "ON"
when a single Modbus device communication (TCP) is lost.
Description: C300 PCDI Device disconnect is not updating in a timely
manner - can take up to five minutes.
Recovery: Once the device is flagged as failed - ERROR FLG = "ON" then
no recovery is necessary.
Workaround: None.

45
2 ISSUES

Third Party Components

1-2BPGTNP Error Indication: E3 plus relay is in "Blocked Start" state.

Description: E3 plus relay may trip with `Blocked Start indication during
operation even when the motor or starter is not connected to the relay.
Recovery: The trip condition can be recovered from the Control Builder by
giving the "E3[0]: Fault Reset"command through the E3 plus output channel.
Workaround: Configure the Starts/Hour parameter and the Starts Interval
parameters as follows:-Configure the Starts/Hour to allow more starts per
hour-Shorten the interval between the starts in the Starts Interval
parameterFor more information about troubleshooting related to E3 plus
relay trip with aBlocked Start indication, see the E3 & E3 Plus Solid-State
Overload Relay User manual from the Rockwell Literature Library.
1-G04A9M Error Indication: BADPV Alarms are reported against CM's using Siemens
ET200 IO Module (AI 331-1KF01-0AB0) after PGM Switchover.
Description: Intermittent BADPV Alarms are logged against Control
Modules using Siemens ET200 331-1KF01-0AB0 AI module after a PGM
Switchover. No loss of Communication to the device itself occurs or no such
event is logged. Problem recovers within a few seconds. However if Control
is configured to Shed on a Single BADPV, it will shed.
Recovery: Recovers automatically within few seconds.
Workaround: The workaround is not to use module type AI
331-1KF01-0AB0 in redundant systems. According to Siemens data sheet
the basic execution time of this module is 488 ms. In case of fail over this
time is too long.
1-NMO0DJ Error Indication: Input process data of TURCK IO modules go bad on
PGM switchover if one of the Turck gateway modules is removed
physically. It is also noticed that outputs are lost on PGM switchover, if the
Turck excom gateway module firmware version is less than 2.2.x.
Description: Input process data of TURCK IO modules go bad on PGM
switchover if one of the Turck gateway modules is removed physically. It is
also noticed that outputs are lost on PGM switchover, if the Turck excom
gateway module firmware version is less than 2.2.x.
Recovery: None.
Workaround: It is recommended to have both Turck gateway modules
connected physically in Turck excom rack. The Turck excom gateway
(GDP-IS) firmware version must be at least 2.2.x. With firmware version
less than 2.2.x, the outputs are not lost on PGM switchover if DPV1 is
enabled in PROFIBUS device configuration.
1-11KCT39 Error Indication: Profibus IO module appears RED on Monitoring with the
PFB Communication Status shown as ""PfbOffline and DEVSTATUS
parameter of these blocks shows 'PfbNotInRun'.
Description: PBI_DEVICE blocks go offline and appear in red in
monitoring side after load of many remote-chassis I/O including SST block
at the same time. This was also seen when chassis IO modules are loaded in
a particular order like Pulse input module, then Analog Output Modules and
then SST module along with its I/O modules.
Recovery: Delete all the modules and load the Profibus modules first and
then load the other chassis I/O modules.
Workaround: None.

46 www.honeywell.com
 2 ISSUES

1-17FPCH Error Indication: Internal error occurs when you try to open the documents
related to SST_PFB_CLX in SST Profibus installation CD part nr.705-0004,
Rev. 03-02.
Description: Internal error occurs when you try to open the documents
related to SST_PFB_CLX in SST Profibus installation CD part nr.705-0004,
Rev. 03-02. Because of this the user documentation cannot be used which
will assist in installation or up-gradation of firmware.
Recovery: None.
Workaround: Use next version of SST_PFB_CLX in SST Profibus
installation CD part nr.705-0004, Rev. 07.10.0.0 where issue is resolved.
1-PPG7GR Error Indication: C200 5ms controller is losing Connection with Server
Intermittently resulting in loss of View at Control Builder (everything turns
RED at Monitoring side) and Loss of View at Station for C200 Detail
Display.
Description: Loss of View / Server Connection fail on Control Builder &
Station for C200 5ms (Non-Redundant), when there is Peer-to-peer (P2P)
Connection between C200 5ms & ACE on CNET and cable is disconnected
as per below: Remove Control Net Cable A of Non-Redundant C200 5ms &
Remove Control Net Cable B of ACE. Remove Control Net Cable B of Non-
Redundant C200 5ms & Remove Control Net Cable A of ACE. In the above
two Scenarios, Loss of Peer-to-peer data communication between C200 &
ACE is observed which is expected. But in this scenario, the C200 5ms is
losing Connection with Server Intermittently (disconnects and connects
back) and hence resulting in Loss of View at Control Builder (everything
turns RED at Monitoring side) and Loss of View at Station for C200 Detail
Display.
Recovery: Reconnect the cables back.
Workaround: None.

CF-Control Function

1-RTYWYZ Error Indication: Incorrect Event flags are set momentarily in

RAMPSOAK block during profile transition.
Description: During transition from one profile to another, some Event flag
of upcoming profile is set to ON for a moment.
Recovery: The incorrect Event flags state set remain in that state
momentarily and recover automatically. The correct profile Event flag is set
after the recovery.
Workaround: None.
1-US3KDR Error Indication: Output of Offdelay block becomes ON after a delay when
input is read from sfatey manger.
Description: A boolean read from the safety manager through ECI gives a
wrong behavior on the offdelay function block. When the input is energized
the output must energize immediately but in this case the output is only
energized after the delay time.
Recovery: None.
Workaround: None.

47
2 ISSUES

SE-System Engeneering

1-SKJSF4 Error Indication: The user may see reverse videos on display, may see loss
of trend values.
Description: During normal operation, the servers may lose view from the
controllers under a situation where an unresponsive node may exist in the
network. This may be because of a faulty device below the unresponsive
node. This may result in a loss of view condition.
Recovery: Manual. Remove the device/node that is causing
unresponsiveness and Stop/Restart EPKS Control Data Access service.
Workaround: None.

Network-CNI

1-WCZEO9 Error Indication: Remote IO communication failed with a CNI Line error
3416.
Description: Remote IO communication failed with a CNI Line error 3416.
Recovery: None.
Workaround: None.
1-XG5K9X Error Indication: CNET cable removal system alarm RTN even though
cable fault is live
Description: CNET cable removal system alarm RTN even though cable
fault exists
Recovery: None.
Workaround: None.

Network-FTE

1-3G2TAP4 Description:
Recovery:
Workaround:

I/O-Series C

1-3GAHYYS Error Indication: Outputs that were POWERED when field power was lost
will return POWERED momentarily before initializing when power is again
restored.
Description: Unexpected output behavior upon return of lost field power.
For more details of anamoly see PN2014-30.
Recovery: None.
Workaround: For any output that was POWERED when field power was
lost ensure that the output cannot return immediately to the POWERED state
when the field power is restored. For more detail on how this can be
accomplished see PN2014-30.
1-3I90BL7 Error Indication: HART communication errors continuously accumulate.
Description: AI-HART Analog Input module cannot communicate properly
with a WIKA T32 transmitter.
Recovery: None.
Workaround: None.

48 www.honeywell.com
 2 ISSUES

1-3NDHL6P Error Indication:

Description:
Recovery:
Workaround:

ERDB, EMDB, DBAdmin

1-3NDHL6P Description: When we try to connect the Control Builder from Server A
which is in R430.1 release, it fails to connect with the following errors:1.
ERR_DB_SWITCHTOREPLICA "Failed to connect to primary ER,
connected to secondary@@DB_SWITCHTOREPLICA"2.
ERR_ERCLI_REQID "Invalid Request Id@@ERCLI_REQID"3.
ERR_CBCANNOTLOGON "Cannot connect to database. View Error Log
for details.@@CBCANNOTLOGON"4. ERR_PROV_COMINTERFACE
"Failed on COM interface.@@PROV_COMINTERFACE"
Recovery: Same as Workaround
Workaround: Connect Control Builder from Console/Flex station.
Error Indication: This error occurs when we are trying to Open the Control
Builder from ServerA which is in R430.1 release while ServerB has been
migrated to R431.1 release.
Description: When we try to connect the Control Builder from Server A
which is in R430.1 release, it fails to connect with the following errors:1.
ERR_DB_SWITCHTOREPLICA "Failed to connect to primary ER,
connected to secondary@@DB_SWITCHTOREPLICA"2.
ERR_ERCLI_REQID "Invalid Request Id@@ERCLI_REQID"3.
ERR_CBCANNOTLOGON "Cannot connect to database. View Error Log
for details.@@CBCANNOTLOGON"4. ERR_PROV_COMINTERFACE
"Failed on COM interface.@@PROV_COMINTERFACE".
Recovery: Same as Workaround.
1-3OD3HT0 Workaround: Connect Control Builder from Console/Flex station.

Redundancy-RM

1-3OHOIJB Error Indication: RM E054 Fault or EG02 Fault.

Description: When the RM cannot communicate on a chassis resident
module connection and back-plane ping indicates module is present, the RM
faults with E054 for this is an illogical condition; an EG02 fault with Data1
set to 0x45303534 indicates multiple faults detected with E054 being the
first fault. Both E054 and EG02 are major RM faults that disable the RM
from participating in redundancy coordination for the chassis resident
modules. When this happens on the Secondary, a loss-of-redundancy occurs.
When this happens on the synchronized primary, the synchronized secondary
chassis detects primary chassis RM fault and switches to the primary role.
However, the successful switchover depends on the original primary chassis
resident modules performing self-switchover in the absence of the RM. If
any of the original primary chassis modules detect loss-of-synchronization
prior to detecting RM removal, the module remains in the primary role
resulting in dual-primary.
Recovery: Power-cycle the chassis with the faulted RM.
Workaround: None.

49
2 ISSUES

2.3

OPM-Upgrade Tool

PAR Description
1-3N3C5RD Error Indication: Readiness Check of C300 controllers having 500 or more reference blocks go to pending
state.
Description: One or more nodes go to pending state on a relatively larger system with controllers having
500 or more references blocks . This issue can be observed only on R431.1 system.
Recovery: Close and re launch the Upgrade Tool4.
Workaround: Perform the following steps :
1. After Readiness check enumeration, for the C300 controller which has more reference blocks, clear the
readiness check box, clear any dangling control connections and proceed.
2. Run ECC tool to identify the dangling control connections.

50 www.honeywell.com
 2 ISSUES

2.4

Server - TPS Integration

PAR Description
1-3O9NPMP Error Indication: You get Data entry error on attempting to change mode of emulated
points from Cut Over Display before performing Cut over .
Description: You observe the error on performing the following steps.
1. HASE (Emulated) points are loaded to C300 controller but CUT OVER from HIWAY
to FTE is not performed.
2. Invoke Cut Over Display from Experion Station by entering SYSHSECTMGTB in
command prompt.
3. Enter Hiway Number and Box Number in COD Display to invoke faceplates for above
emulated points.
4. Attempt to store mode parameter of any of the above points from bottom (CDA) face
plates.
5. Mode store is unsuccessful and you get " Data entry error" while attempt to change
Mode of emulated points from Cut Over Display before performing Cut over .
Recovery: None.
Workaround: Perform the following steps if Application Engineer wants to change Mode
of HASE (Hiway Algorithm Slot Emulation) Slot CMs (Emulated Combo points) before
cut over.
1. Open Control Builder and Open the appropriate CM (Named as TPN point name).
2. Click on HRB block and click on MODEEM parameter.
3. Change to required Mode (AUTO/MAN/BCAS)
Perform the following steps if Application Engineer wants to change Mode of HASE Slot
CMs after cut over.
1. If AE wants to change mode of HASE slot CMs from COD then use the top faceplates
(TPN) faceplate.
or
Open Native Window and call Detail Display of the desired point and change the
mode.

Server

PAR Description
1-3PUQQQ5 Error Indication: Perfmon logs show increased memory usage for the process
hscodbcn.exe. Experion logs show constant authentication of ODBC client connections.
Description: ODBC driver resource usage can increase if an ODBC client does continuous
connect/disconnect. In this case the ODBC driver may eventually terminate and
automatically restart.
Recovery: None.
Workaround: Decrease the rate at which an ODBC client re-connects to and disconnects
from the Experion server. For AEA set the event collection period to 10 minutes.

51
2 ISSUES

IEC61850 Client Interface

PAR Description
1-3S5PF5Z Error Indication: IEC61850 SCADA HCI interface terminates abruptly when logging
level is set to 'FLOW'.
Description: IEC61850 SCADA HCI interface terminates abruptly when logging level is
set to 'FLOW'. In this case the interface terminates and restarts automatically.
Recovery: Same as workaround.
Workaround: Perform the following steps.
1. Open the corresponding OPC Config.XML that is terminating.
2. Change the Driver log level from FLOW to ERROR as per the following entry.
<DrvrLogLvl btype="Enum" type="LogLvl">ERROR</DrvrLogLvl>
3. Restart the corresponding driver.

FF Interface Modules

PAR Description
1-3QIZ2V1 Error Indication: During FIM4 failover test of15 FIM4s, 5 FIM4s stops responding with
the following error 0x03B3. Some FIM4s fail after 30 failovers and 2 fail after 100
failovers.
Description: A crash is observed in Fieldbus stack: FB_FS 0x0002-C 0x00-T 0xCF-M
166-L 0x0000-C 0x00D1-D with some kind of time out on fieldbus operation. This may
lead to control shed.
Recovery: Restart the affected module.
Workaround: None.

52 www.honeywell.com
3 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.

53
3 NOTICES

3.1 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 email 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) listed in the “Support and other contacts”
section of this document.

54 www.honeywell.com
 3 NOTICES

3.2 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 email to [email protected].
or
• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical
Assistance Center (TAC) listed in the “Support and other contacts” section of this document.

55
3 NOTICES

3.3 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.

56 www.honeywell.com
 3 NOTICES

3.4 Training classes

Honeywell holds technical training classes on Experion PKS. These classes are taught by experts in the field of
process control systems. For more information about these classes, contact your Honeywell representative, or
see http://www.automationcollege.com.

57
3 NOTICES

58 www.honeywell.com