Enterprise Buildings Integrator (EBI) R610.

1
Command and Control Suite (CCS) R310.1

Known Issues Bulletin

Issue 1, August 19, 2021

This document lists and summarizes issues that you may encounter when configuring or using this release of
Enterprise Buildings Integrator or Command and Control Suite. Installation and upgrade issues are addressed in the
EBI R610.1/CCS R310.1 Software Release Bulletin.

This article discusses: It applies to:

Known issues EBI R610.1
CCS R310.1
Prerequisite reading:
EBI R610.1/CCS R310.1 Software Release Bulletin
Related documents: Support:
EBI R610.1 Compatibility Matrix For information about updates to
CCS R310.1 Compatibility Matrix this bulletin, contact your nearest
Honeywell office or Technical
Assistance Center.

Copyright 2021 Honeywell International Sàrl

HONEYWELL DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND MAKES NO EXPRESS WARRANTIES EXCEPT AS MAY BE
EXPRESSLY STATED IN ITS WRITTEN AGREEMENT WITH AND FOR ITS CUSTOMERS.
In no event will Honeywell be liable to anyone for any direct, indirect, special, or consequential damages. The information and
specification in this document are subject to change without notice.
1 www.honeywell.com
Table of Contents
Enterprise Buildings Integrator (EBI) R610.1 1
BNPS 4
Core 4
Displays 4
Installation 5
Localization 5
Quick Builder 5
Tools 6
Web Access 6
EBI 6
BACnet Point Server 6
BACnet Utilities 7
Cardholder Presentation - Card Printing 7
Core - SQL 7
Displays - General 7
Global Schedules 7
Notification Management 7
Notification Presentation 8
Quick Lists 8
Security Service 8
Service Framework 8
XLNET 8
FPS 8
Core 8
Database 9
Displays 9
Installation 10
MNS 10
Panel 10
Quick Builder 10
Tools 11
VOIP 11
HMIWeb Display Builder 11
Arrange Object 11
Custom Properties 11
HDB other 11
Point Browser Support 12
Rendering 12
Shapes 12
Stylesheets 12
Textbox 12
IdentIPoint 12
Access Firmware 12
Common Firmware 12
IPPS-G 13
Core 13
Displays 13
IPPS-V 14
3rdParty 14
Core 14
Database 15
Displays 15
Installation 15
Quick Builder 15
Station 15
Chromium View 15
Map Elements 16
Online Map Builder 16
Application Framework 16

2
 Automation Model 16
Chart/Trend 16
Indicator 16
Installation 17
Internationalisation Infrastructure 17
Navigation 17
Station other 17
Platform 17
Printing 17
Security 17
Toolbar/Menu 18
Window Manager 18
XLS80E 18
Core 18
Database 20
Displays 21
Hardware or Firmware 22
Installation 22
Management Pages 22
Tools 22

3
BNPS
Core
• The healthy status symbol (green check mark) does not appear in the System status pane for BNA. (ISR 112256)
Workaround: Double-click the BNA or see the Status pane.

• BNA Channel 1 failure alarm becomes RTN after the migration even though it is active in the field. (ISR 145131)
Workaround: Restart the BNA.

• When ESIG is enabled, if point attributes from IRC Direct Access and XL Classic Direct Access are changed,
only the Operator field in the Event summary contains a value. (ISR 145141)
Workaround: None.

• You can rename schedules successfully when Electronic Signature is enabled, but the Value and Previous Value
fields in the Event Summary for this event are empty. (ISR 145153)
Workaround: None.

• On a redundant server system, the FirmwareDeviceInfo XML file is not updated after an EBI manual failover is
performed. (ISR 145169)
Workaround: None.

• BNPS EXCEL Classic points can be commanded even if the Point is in Auto Mode. (ISR 159493)
Workaround: None.

• Point addresses do not update automatically in the point detail display page after the delete download and re-
download operation is performed for the same point in Quick Builder. (ISR 191894)
Workaround: Restart BNPS and check the point address again.

• For HPEP controllers, performing a data flash operation results in incorrect values being shown in the Value
column in the Events summary. (ISR 202220)
Workaround: None.

• The BNA firmware version is not updated on the BNA point detail display until the point server is restarted. (ISR
211718)
Workaround: Restart the point server after the BNA firmware version is changed.

Displays
• When restoring the application to an Excel Plus controller, the firmware download/upload options are enabled,
when they should be unavailable. (ISR 145086)
Workaround: None.

• In the R7044 Controller schedules page, any data entered into the time value fields is not saved unless you
press the Enter key before moving to the next field. (ISR 208511)
Workaround: To save the values, press the Enter key before moving to the next field.

• For analog input and digital input points, stopping the BNPS causes an error message to be displayed when
loading shape files. (ISR 209220)
Workaround: None.

• The Backup/Restore file name text boxes on the Controller Maintenance page has a text length limitation of 80
characters. (ISR 222766)
Workaround: Change the path so that it has a maximum length of 80 characters.

4
Installation
• While performing an upgrade, the BNPS service is unregistered if you terminate the installation. (ISR 145174)
Workaround: None.

• The message stating that files cannot be updated because they are in use appears only on a remote point server
machine. (ISR 145175)
Workaround: Close the other point server applications from the notification area and continue the installation.

• Sometimes the installation fails to enable the IIS settings automatically and a message appears informing the
user that this needs to be done manually. (ISR 207249)
Workaround: Enable the IIS features manually and restart the installation.

• Sometimes BNPS fails to uninstall successfully. (ISR 222500)

Workaround: Open Task Manager, right-click BNPSCnfg.exe, and then click End task.

Localization
• After localization, strings such as "Type mismatch", "Zone Manager Update Complete", "Start", and "Value
clamped at maximum" are not converted to the localized language. (ISR 145107)
Workaround: None.

• Some BNPS web pages have alignment issues after being localized. (ISR 145108)
Workaround: None.

• Localized text is displayed as junk characters in the SPS and Global Schedules databases for a non-native
operating system. (ISR 175240)
Workaround: None.

• Localized text is displayed as junk characters in controller schedule pages (web pages) for EXCEL IRC and
EXCEL EMC controllers. (ISR 175270)
Workaround: Use Global Schedules pages to configure schedules.

• After localizing to Chinese the emcDirecAccess.asp and R7044DirecAccess.asp pages display garbled
characters. (ISR 178489)
Workaround: None.

• When installing the BNPS language pack, clicking the Cancel button on the Select Components dialog box does
not enable the Finish button, preventing you from exiting the installation. (ISR 209287)
Workaround: Open Task Manager, click the Processes tab, navigate to the setup.exe program, and end the
process.

Quick Builder
• Importing from Quick Builder fails for data points (.XMR) if done after clicking a facility name. (ISR 145130)
Workaround: Click the point and then start the import.

• During Quick Builder export, when multiple point servers like BNPS, FPS, and IPPS-V are selected, only IPPSV
points are exported in the xmr file. (ISR 160696)
Workaround: Select only one point server at a time.

• When downloading points in Quick Builder, any points that are not assigned to a controller are not downloaded,
but the system does not indicate the points are not assigned to a controller. (ISR 191897)
Workaround: Make sure each point is assigned to a controller before downloading the points.

5
• Quick Builder displays garbled characters in the device field when selecting different EXCEL IRC room points
from different controllers. (ISR 197927)
Workaround: None.

Tools
• For BNPS, the Alias name in Station accepts 16 characters, but the BNPS applet and BNPS installation accepts
only ten characters. (ISR 191710)
Workaround: Use a maximum of ten characters in the Alias name.

Web Access
• EXCEL EMC Analog Input points can be commanded through direct access pages in Auto mode. (ISR 145104)
Workaround: None.

• The message “Error while configure system” is displayed when a remote point server direct access link is
opened. (ISR 145132)
Workaround: None.

• In EXCEL lRC light schedule, two switch points show the same time for On and Off. (ISR 145136)
Workaround: None.

• For EXCEL IRC Digital Input points, changing the mode from Auto to Manual is not reflected on the direct access
page. (ISR 145162)
Workaround: None.

• BNPS Web access pages do not open in the HMIWeb Browser client. (ISR 145164)
Workaround: None.

• When using remote point server, navigating to Schedules and Direct access pages results in a security alert
regarding certificates. (ISR 159599)
Workaround: Ignore the warning. There is no functional impact.

EBI
BACnet Point Server
• The BACnet point server terminates when the system receives an alarm of type change-of-reliability with over
255 characters. (ISR 223870)
Workaround: Disable the type change-of-reliability in the controller if it is not required.

• Sometimes a remote BACnet point server fails to communicate with the EBI server after it is restarted. (ISR
225151)
Workaround: If possible, disable any unused NIC; or try the following:
1. On the point server computer, stop bacnet direct (or run net stop “bacnet point server”).
2. On the server computer, kill ms_linkd.exe (or run taskkill /f /im ms_linkd.exe).
3. On the point server computer, start bacnet direct (or run net start “bacnet point server”).

• No event is raised when a BACnet controller is restarted by using the Maintenance tab of the controller's Point
Detail Display. (ISR 226335)
Workaround: None.

• The system updates the host time on BACnet alarms after the Point Server is restarted. (ISR 226727)

6
 Workaround: Refer to the Field Time to see when an alarm occurred.

• On redundant servers with local BACnet Point Servers, under some timing conditions, Trend Log buffer collection
may not happen after the primary point server is restarted. (ISR 228190)
Workaround: None.

BACnet Utilities
• After restarting the “BACstac Protocol and BACnet PS service” manually, bacnetutilities sometimes fails to re-
establish communication with BACstac, resulting in the server being unable to access BACnet schedules. (ISR
226798)
Workaround: Use Task Manager to terminate the bacnetutilities.exe service.

Cardholder Presentation - Card Printing

• When upgrading from an EBI R500 system to an EBI R610 system, bitmap (.bmp) or Graphics Interchange
Format (.gif) images on card layouts do not display when printing the cards. (ISR 228378)
Workaround: 1. Open the .xaml file in a text editor.
2. Change any .png references for the cardholder in ..\Honeywell\Server\cms\PhotoID\NewCardLayouts back to
the original .bmp or .gif format.

Core - SQL
• On a system that uses orchestration, the SbManagementDB, SBMessageContainer, and SbGatewayDatabase
databases are all set to Full recovery mode, which results in huge log files. (ISR 222547)
Workaround: In SQL Server Management Studio (SSMS), manually change the database configuration to
Simple recovery mode to reduce the size of the log files.

Displays - General
• When an operator changes the location to which an access level is assigned, an event is raised with a blank
source field. (ISR 223337)
Workaround: None.

• On a KBOB-licensed system, the point name is not shown as per the convention "pointname.parameter followed
by value" when it is selected on the Alarm Summary or point detail page. (ISR 223411)
Workaround: None.

Global Schedules
• When creating a base schedule, no schedule event is created in the calendar for the following year when the
"Use Every Year" option is enabled in conjunction with the Usage list. (ISR 226660)
Workaround: Create the schedule manually.

Notification Management
• Frequent and continuous acknowledgement of alarms by using the Alarm banner can result in the system
displaying a script error. (ISR 223555)
Workaround: Click OK to remove the script error and continue to acknowledge the alarms.

• The comment added flag does not persist against point server point alarms after performing a manual failover.
(ISR 226438)
Workaround: None.

7
Notification Presentation
• On a system on which KBOB is licensed, filtering the Event Summary on the Source field does not include ACK
events. (ISR 228383)
Workaround: To show the ACK events, change to Today (snapshot) or any suitable Date/Time filter.

Quick Lists
• On a KBOB-licensed system, the Quick View page shows only the first 40 characters of the BACnet point names.
(ISR 223345)
Workaround: Double-click the point name to display the point details page, which shows the full point name.

Security Service
• A remote BNPS point server cannot authenticate its web pages with a redundant EBI server in an environment
that requires Fully Qualified Domain Names (FQDN). (ISR 222632)
Workaround: Enter the host name in the Subject Alternative name while generating/requesting an FQDN
certificate.

Service Framework
• Video recordings generated on Point Server alarms by an Automation Rule do not cause the alarm to be treated
as a unique alarm, even when the system is configured to do so. (ISR 226747)
Workaround: Access the video clip by using the corresponding event in the Event summary.

• On a large redundant system, sometimes during failover the new primary server can start up in a state where
Stations cannot display web pages (for example, CMS, Automation Rules, and Global Schedules). (ISR 228357)
Workaround: Open and close the EBI configuration Panel.

XLNET
• The XLNET Daemon Service does not stop salt.exe, translon,exe, and xpc5_d.exe when the Service is stopped.
(ISR 225058)
Workaround: Manually kill the tasks if required.

FPS
Core
• DS bus Amplifier status is not shown properly in the Audio tab of DSDB PDD. (ISR 149147)
Workaround: None.

• Under a heavy load, the FPS service restarts after 5 days of board runtime. (ISR 149153)
Workaround: It is recommended to keep FPS Watchdog always running as a recovery mechanism.

• Configuring more than 6 FPS points on EBI Groups does not display properly. (ISR 149154)
Workaround: None.

• The Remote FPS Service does not restart automatically after it is disconnected from the network and the system
is restarted. (ISR 149197)
Workaround: None.

• Duplicate alarms are sometimes seen when disconnecting the LAN cable from FNA. (ISR 149201)

8
 Workaround: None.

• RTN alarm operation for a Fire point downloaded from FPS to EBI behaves differently from a scan task point.
(ISR 149209)
Workaround: None.

• FPS does not send an invalid parameter if PointState param is referred as PointState.POINTNAME in EBI. (ISR
149258)
Workaround: Provide proper parameter name in EBI scripts and custom display bindings.

• Timestamps on the point server page are not updated when a reconnection is successful. (ISR 174893)
Workaround: Verify the time in Alarm Summary and Event Summary.

• Loop IR Status reflects inconsistencies between EBI and Panel. (ISR 181877)
Workaround: Enable / Disable from Panel using the following steps:
1. Go to Panel Programming Menu and give password
2. Go to Alter status menu
3. Click More
4. Click Enable/Disable IR
5. Enter Loop number and IR command as Enable or Disable.

• For fire alarms, alarm comments are not retained in Alarm Summary after a point server restart. The alarm
changes state; RTN followed by unacknowledged after restarting the point server. (ISR 192169)
Workaround: None.

• Sometimes the Mass Notification Console becomes unresponsive for a few seconds. (ISR 193632)
Workaround: Wait five seconds for the console to return to normal.

• When redownloaded after a facility change, speaker points, currently in alarm, incorrectly show as Normal in the
VOIP page until a new alarm is raised. (ISR 215244)
Workaround: Restart the FNA so that the system displays the correct status.

Database
• FPS Maintenance Backup DB functionality did not work when domain user installed EBI. (ISR 146213)
Workaround: Change the owner of the maintenance job to MNGR.

Displays
• GDA error is shown when terminating a walk test. (ISR 149203)
Workaround: None.

• The hierarchy of controllers in the system summary page is not displayed correctly. (ISR 149220)
Workaround: Download the controllers again from Quick Builder.

• If offline FPS points are added to Groups, the group display has errors when loaded. (ISR 161750)
Workaround: None.

• Alarm instruction display value is not loaded automatically after Quick Builder download. (ISR 199530)
Workaround: Reload the point in Station.

• LED in FPS displays are not consistent with EBI styles. (ISR 199531)
Workaround: None.

9
• The Control tab in the RPU display is larger than the other tabs. (ISR 212239)
Workaround: None.

• ToolTips do not work for the FPS Point Name in the point detail display if the point name is approximately 20
characters long. (ISR 215201)
Workaround: None.

Installation
• The FPS applet tray icon does not load after the system is restarted and User Account Control (UAC) is enabled.
(ISR 149152)
Workaround: Manually launch applet from the tools folder under FPS folder.

MNS
• Buttons in DVC may be unresponsive if the Close button is pressed before releasing buttons from DVC. (ISR
193636)
Workaround: Based on the priority setting in Mass Notification console, press MNSALLCALL or FIREALLCALL
button from Mass Notification console.

• Mass Notification Console is non-operational even with AllCall buttons in green color when console is used for
the first time after installation. (ISR 194399)
Workaround: Run the “MNSSTATUSRESET" utility which is available along with the installer package. The
password to unzip the package is "support" (without quotes).
To run the MNSSTATUSRESET utility:
1. Copy the utility to the FPS Server machine.
2. Double-click the utility and click the MNSSTATUSRESET button.
The Mass Notification Console will return to normal state.

• In rare circumstances, Mass Notification Console status is not displayed correctly after performing paging
operation. (ISR 194400)
Workaround: 1.Start a new AllCall from MNS console:
a. Click the Close button in the Live Paging window
b. Click the Reset button in MNS console.
2. For Station users: Run the MNSSTATUSRESET utility.

• When the EBI server is restarted, sometimes MNSConsole starts before the EBI server, causing the system to
display the "Unable to access MNS License" message. (ISR 216146)
Workaround: Wait until the EBI server has restarted, and then close and reopen the MNS Console.

Panel
• After disabling and then re-enabling FPS points in alarm, the Alarm summary for an XLS2000 panel does not
display the correct status. (ISR 212975)
Workaround: Restart the FPS.

Quick Builder
• DAX supports only two speakers, but in Quick Builder four speakers can be created. (ISR 149222)
Workaround: When configuring the speakers under DAX from Quick Builder, do not configure and download
speakers with number 3 and 4.

• During Quick Builder export, when we select BNPS, FPS and IPPSV points in the export formats, only IPPSV

10
 points are exported in the XMR file. (ISR 161330)
Workaround: None.

• In a redundant topology, when using a separate Client machine to perform a Quick Builder upload\download,
using the base name of the server causes Quick Builder operations to fail. (ISR 220999)
Workaround: In Quick Builder, type the current EBI primary server name in the Server name field.

• In Quick Builder, upload/download fails for FNA when the time master (496) parameter is added. (ISR 223754)
Workaround: None.

• Quick Builder allows you to enter a value greater than 500 in the DVC General Zone box even though the
maximum supported is only 500. (ISR 225127)
Workaround: Only enter a value of 0 to 500.

Tools
• Non-admin users can start or stop the FPS service using the FPS applet. (ISR 149174)
Workaround: None.

VOIP
• No message is shown to user while paging when any other PAM point acquires the audio channel. (ISR 149235)
Workaround: None.

• The VoIP progress bar may not progress beyond 0% when DVC-based paging is performed continuously (more
than 10 times). (ISR 212540)
Workaround: None.

• During speaker-based paging, if more than 180 speakers are selected, the progress bar may not progress
beyond 0% in FPSUI. (ISR 212609)
Workaround: Use DVC-based paging instead of speaker-based paging.

• If the VOIP live notification page is kept open in idle state for more than 20 minutes, the speaker selection is not
retained. (ISR 212843)
Workaround: Select the speakers again and click Live Notification.

HMIWeb Display Builder

Arrange Object
• Pasted objects cannot be moved together as a group until re-selected. (ISR 209115)
Workaround: Re-select the objects before attempting to move them.

Custom Properties
• Pages that have null-bound alphanumeric objects result in "Errors occurred on this page" errors. (ISR 204114)
Workaround: Remove the Null-bound alpha.

HDB other
• Adding a custom shortcut menu to a dynamic shape results in shortcut menus being removed for all other
elements in the display. (ISR 205280)
Workaround: Close the display and reopen it.

11
Point Browser Support
• In HMIWeb Display Builder, dragging and dropping points from the Point Browser only works when you click the
Points icon. (ISR 203214)
Workaround: Drag and drop points from the graphic icon to the left of the text.

• On the Data tab of the Properties dialog box, the Point list box does not display the points built on the server.
(ISR 203632)
Workaround: Click the Magnifier button to display the Point Browser. Then either select the point from the list,
or narrow your search by typing characters in the Search box at the top of the list.

Rendering
• Clicking and dragging the Alarm icon on a Station Status Bar then dropping it on the Alarm Line in locked down
mode calls up a white display. (ISR 208207)
Workaround: Navigate to another display via the Station toolbar.

Shapes
• Displays that contain embedded shapes with special characters (for example, a German umlaut) in its name
cannot be unarchived after using the Archive Displays and Shapes assistant. (ISR 212358)
Workaround: Archive the display folder manually instead of using the HMIWeb Display Builder Assistant.

• When using Custom Properties on text objects within a shape, any changes made to the text object directly do
not persist. (ISR 226852)
Workaround: Do not edit the text object directly; instead, edit the text by using the Custom Properties tab.

Stylesheets
• In HMIWeb Display Builder the scrollbar does not work if objects are drawn outside the bounds of the visible
window. (ISR 204066)
Workaround: Use the mouse scroll button instead.

Textbox
• In HMI Web Display Builder, if you select a text box and then select a second text box by using Shift+click, the
first text box goes into Edit mode. (ISR 202262)
Workaround: None.

IdentIPoint
Access Firmware
• A corrupt card certificate might trigger incorrect threat level changes. (ISR 228204)
Workaround: None.

Common Firmware
• You cannot log on to the IdentIPoint reader web page by using a password that has more than eight characters.
(ISR 221946)
Workaround: Use a password that has fewer than eight characters.

12
IPPS-G
Core
• RTN events are only displayed in the Event Summary after a successful reconnection with IPPS point server.
(ISR 209420)
Workaround: None.

• When IPPS is restarted, in Classic and G3 panels, active acknowledged alarms sometimes become active
unacknowledged alarms. (ISR 211576)
Workaround: None.

• Missing Status for RIO point is not updated when the panel is in engineering mode due to panel limitation. (ISR
213337)
Workaround: None.

• If the data bus between the Ethernet board and the Galaxy controller is disconnected, the panel point status
remains as online in the point detail display. (ISR 222817)
Workaround: None.

• The GROUP-SET Alarm is not reporting to EBI if a digit for IP of the panel has a prefix of zero. (ISR 222925)
Workaround: Do not append a zero to a digit when configuring the IP address for a Galaxy controller in the
Quick Builder settings. This is an example of a correct IP address entry: 10.64.235.5. This is an example of an
incorrect IP address entry: 10.64.235.05.
If an IP address has been configured incorrectly, complete the following steps:
1. Stop the IPPS service .
2. Enter the IP address without a preceding zero.
3. Click Save to download the controller configuration.
4. Navigate to <install folder>\Honeywell\EBI\PointServers\IPPS\Data, where <install folder> is the location where
EBI is installed.
5. Delete the incorrect bus message log file.
6. Start the IPPS service.

• Sometimes, rather than show as return to normal, a YCRS485 alarm persists in the EBI alarm summary if the
RS485 cable is disconnected for more than 15 seconds. (ISR 223161)
Workaround: Use the separate stuck alarm removal graphics files to remove the YCRS485 alarms.

• Data Reconnection occurs if unsupported Galaxy point parameters are embedded in custom graphics. (ISR
223863)
Workaround: In custom graphics, do not use FaultState, MaskState, and/or ResistanceState parameters for
Classic panel points (and/or FaultState parameters for G3 panel points).

Displays
• Sometimes the zone map detail in the group point detail display is not updated to show the current state of the
zone. (ISR 211575)
Workaround: Refresh the page to update the value.

• The system displays a script error when opening the Galaxy Group General point detail display. (ISR 223559)
Workaround: In Server wide settings, in the "Point value error indication" section, click the "Display using
inverse video" option.

13
IPPS-V
3rdParty
• Auto discovery shows eight partitions even if only one partition is configured in the panel. (ISR 186894)
Workaround: None.

• "Battery Test Fail" event gets stuck in EBI alarm summary page. (ISR 201814)
Workaround: Force delete the alarm using steps detailed in PB-573 "Few events get stuck in EBI after disabling
Alarm Recovery using IPPS_R4.7_Update01_Temporary_Alarm_Recovery_Update".

Core
• Alarm recovery fails for BPE250 panels when downloaded for the first time if the BPE panel event log buffer has
more than 100 events. (ISR 148149)
Workaround: You can trigger alarm recovery again by downloading the controller points again or
disabling\enabling controller COMMS communication.

• Some Partition events (for example, the Walk test) are reported on zone points during alarm recovery. (ISR
167337)
Workaround: None.

• When communication fails, the system should display an active event in the EBI alarm summary and the panel
status should show in Yellow. (ISR 174767)
Workaround: None.

• Time synchronization fails for panels that use a 24-hour time format. (ISR 176604)
Workaround: Use the default 12-hour format in the Vista controller panel.

• Controller communication fails if the IP octet is configured using zero at the beginning of any of the three digits
(for example, 199.063.238.069). (ISR 177146)
Workaround: Configure the IP without using zero and then download from Quick Builder.

• Alarm reporting to EBI is delayed by 5 to 60 seconds when the system is loaded with approximately 1000 to 1800
alarms per minute with 1000 points in subscription. (ISR 181847)
Workaround: None.

• An output point's configuration (partition mapping, start partition, stop partition, and so on) should be supported
via the HAP protocol so it can be fetched during autodiscovery. (ISR 187577)
Workaround: None.

• In rare occasions, when enable/disable operation is done simultaneously on multiple panels in a loaded system
(>600 IPPS Vista points in subscription), data reconnection is seen. (ISR 200184)
Workaround: Restart the point server.

• Multiple active alarms for the same zone point are not reported by the point server to EBI when the alarm is
triggered multiple times from the panel. (ISR 212372)
Workaround: None.

• Extra alarms are reported to EBI when an Alarm-RTN-Alarm sequence happens in under one second. (ISR
212608)
Workaround: None.

14
Database
• The system will re-establish communication if a panel is disconnected and then immediately reconnected from
panel point detail display. (ISR 177025)
Workaround: Disable panel from PDD. Wait for at least 20 seconds to confirm panel is disabled completely,
then enable the Panel Communication.

• The IPPS database backup job history does not appear in the SQL database. (ISR 192042)
Workaround: None.

Displays
• In Internet Explorer 11, the Column headers for filtering and sorting the current day's events are inconsistent with
the subsystem's. (ISR 181449)
Workaround: None.

• In a custom display, the point status is shown as a red dotted line. Navigating to the point detail display and
returning to the custom display shows the status correctly. (ISR 181811)
Workaround: Navigate to the point detail display and then return to the custom display.

Installation
• When upgrading IPPS Vista from R4.7 to R4.9 the system displays a message stating a file is in use for
commserver module. (ISR 175424)
Workaround: Click Retry in the message.

• BNPS and FPS services do not start automatically after uninstalling the IPPS Vista point server. (ISR 176764)
Workaround: Manually start the respective point server services.

• After uninstalling the IPPS Vista point server, the system does not display a prompt to restart the system . (ISR
177069)
Workaround: After uninstalling the IPPSV, manually restart the system.

• On rare occasions, when installing the point server, the sqlcmd.exe terminates abruptly and the system displays
a “T-SQL execution command line utility has stopped working” error message. (ISR 201926)
Workaround: Uninstall and then reinstall the point server.

Quick Builder
• Downloading or updating many points in Quick Builder takes too long. (ISR 173723)
Workaround: To reduce the Quick Builder download time, download points from one controller at a time.

• For BPT128 panel points, the zone numbers change to 1 after migration using Quick Builder. (ISR 176598)
Workaround: Follow the migration procedure as documented in SRB [Export the QB in XMR before Migration
and Import the same XMR file after completing Migration Steps]. Or, manually change the zone numbers for the
zone points and then perform the update download.

Station
Chromium View
• The system does not automatically clear the Chromium browser cache. (ISR 223183)
Workaround: To clear the cache, manually delete the contents of
"C:\ProgramData\Honeywell\EBI\Client\BrowserControl\ChromiumCache"

15
Map Elements
• If a camera Smart Object is hiding another, clicking the video control on the background Smart Object does not
bring it to the foreground. (ISR 209729)
Workaround: To bring the background camera Smart Object to the foreground, click somewhere else on it.

• Sometimes when filtering map content, Smart Objects for a selected filter are still displayed on the map. (ISR
213128)
Workaround: Apply the map filter again.

• Smart Objects that are configured outside the map extent of a third-party map are not visible. (ISR 213743)
Workaround: Make sure all Smart Objects are placed within the map extent, or extend the map extent.

• Refreshing a client while in Edit mode sometimes fails to display configured zoom regions. (ISR 213924)
Workaround: Exit from and then restart Edit mode.

Online Map Builder

• Sometimes on a touch client, a map element that has been deleted re-appears. (ISR 215036)
Workaround: Exit and then re-enter Edit mode, and then delete the object by using a mouse.

• In the EBI Station client, zoom regions cannot be configured by using touch interactions, but this method works in
the Command Wall and Command Console clients. (ISR 216158)
Workaround: In EBI Station, use a mouse to create zoom regions, or use the Command Wall or Command
Console client.

• Smart Objects on the Command Wall client cannot be moved using touch interaction. (ISR 216203)
Workaround: Move the Smart Objects by using the mouse.

• In Edit mode, if Smart Objects are moved on the map, the objects stay on top and block Smart Objects that you
open. (ISR 218938)
Workaround: Refresh the map in the browser.

Application Framework
• When an operator without appropriate privilege attempts to edit Station Connection Properties, the user interface
may not reflect the Station file settings. (ISR 199825)
Workaround: Restart the Station.

Automation Model
• When using scripts the PageLoadTime property can be sampled correctly only after the window has focus. (ISR
202439)
Workaround: Use window.external.Application.pageloadtime after the window has focus.

Chart/Trend
• Trend configuration on the 32nd pen does not work properly. (ISR 202583)
Workaround: Configure the trend using the Trend Configuration page.

Indicator
• The informational message audible alert does not activate when configured. (ISR 214982)
Workaround: None.

16
Installation
• Sometimes the Station toolbar Forward/Back (F8) list of previously visited displays is not accurate. (ISR 205201)
Workaround: None.

• Removing the GSresourcestatuscontrolimages folder from the Client\Abstract folder prevents Station from
starting. (ISR 211458)
Workaround: Restore a copy of the "GSresourcestatuscontrolimages" folder under the Abstract folder.

Internationalisation Infrastructure
• The Station menu tooltip and some strings in the Station Script Editor dialog box and the Station Connection
(View tab) dialog box are not translated. (ISR 212234)
Workaround: None.

Navigation
• The separator line on the Station menu does not appear in the new Station theme. (ISR 203156)
Workaround: None.

Station other
• Station briefly shows an MNGR privilege operator as "View Only" during logon. (ISR 200832)
Workaround: None.

• On Japanese localised systems, when an alarm is shelved, the Station message zone displays an error
message. (ISR 204664)
Workaround: None.

• n Command Console on a Chinese language system, the point detail display does not show underscore (_)
characters in point names. (ISR 212373)
Workaround: The underline (_) characters are not displayed; this does not affect functionality.

Platform
• If you configure an EBI Station client to use maps, Station will not open if a trust certificate has not been installed
on the Station client. (ISR 216238)
Workaround: If Station with Maps fails to launch, install the trust certificate on the Station client computer.

• A Station or Operator timeout occurs if Maps in Station is used for longer than the Station or Operator timeout
configured in the system. (ISR 217364)
Workaround: Configure a suitable timeout for the operator use of maps.

Printing
• Basic trend shapes are always printed at the top-left hand corner of the display instead of at the specified
coordinate. (ISR 203032)
Workaround: None.

Security
• The LDAP Operator name only supports 20 characters. (ISR 195611)
Workaround: None.

17
• Rotary Stations do not disconnect automatically when the timeout period specified in the Communications
timeout box is exceeded. (ISR 211752)
Workaround: Use an individual Operator timeout value or the Windows auto-logout feature.

Toolbar/Menu
• If the latency between the EBI server and EBI Station is over 100ms, Station cannot connect to EBI and a
timeout occurs. (ISR 218715)
Workaround: Use a local STB file for the remote Station.

Window Manager
• The Command Client Configuration tool does not handle redundant machines that are configured with a fully
qualified domain name (FQDN). (ISR 213216)
Workaround: Manually edit the incorrect paths and hostnames in the STN files.

• Switching between multiple instances of Windows users who are logged on to a single client computer at the
same time is not supported. (ISR 213678)
Workaround: On Command Wall, the user must log out of Windows to switch users.
On Command Console, users can switch by using the Status Bar without switching Windows accounts.

• On server failover, Command Wall shows a black screen. (ISR 221994)

Workaround: To resolve the issue, press CTRL+R.

• After a failure/recovery of Product Service/W3WP, a Station using maps shows an error page instead of the map
it was showing previously. (ISR 228343)
Workaround: Click the Map button on the toolbar to show the map again.

XLS80E
Core
• The status of "Last Known" parameters is incorrect for network panels that are not directly connected to the point
server. (ISR 148707)
Workaround: None.

• The "Restart" button on the XLS80e Point Server Task bar applet does not work. (ISR 148743)
Workaround: Stop the XLS80e Point Server service and restart it.

• When uploading loops from a panel, if you navigate to a different panel the system may display the incorrect
upload data for the original panel. (ISR 148756)
Workaround: Do not navigate away from the panel on which you are performing the upload.

• If the communication cable is disconnected during an upload, the Upload date message in the display will be
incorrect. (ISR 148757)
Workaround: If the Panel and Point Server are disconnected during upload, you must stop and restart the
upload.

• The "EBI to XLSNet Link Fault" alarm cannot be removed from the alarm summary. (ISR 148792)
Workaround: To avoid this ensure no "EBI to XLSNet Link Fault" alarm (or any event/alarm) is active in the EBI
alarm summary page when configuring an EBI connected Panel.

• Some XLS80e points have the wrong access rights on OPC. (ISR 148822)
Workaround: None.

18
• The panel shows as being online in EBI Station even when the panel IDs in EBI and the XLS80e fire panel do not
match. (ISR 148845)
Workaround: You can reconfigure the panel point using the correct ID from the management pages. The
correct panel ID must be entered or misleading information will be presented.

• Calling up a custom graphic which contain invalid references can lead to a "Server Blocked" condition on the
XLS80E point server page. (ISR 148874)
Workaround: Configure the custom graphics with proper references to XLS80e points. If this issue occurs,
restart the respective XLS80e Point server.

• Sometimes if the Zone Walk test or Zone Disablement is initiated from the XLS80e panel, the events are reported
to Installation Point in EBI. (ISR 148881)
Workaround: You should keep the system fully configured by uploading newly configured devices into XLS80e
point server and building the points to EBI using Point build utility.

• After upgrading the XLS80e point server, the point values within the custom display graphics show “unknown”
and then slowly update to a normal condition. (ISR 148897)
Workaround: This issue will appear immediately after upgrading, until the XLS80e PS has completed
background polling to update each point status in the HE_DB database.
The time required for polling will vary depending on the number of panels. The estimated time taken for the
system to complete background polling for 1000 panels is 2hrs 15mins.
For 15000 panels the estimated time is 33hrs 45mins. Based on the size of the system, these figures can be
extrapolated to identify the approximate time required for background polling.
Please allow time for this between commission and handover.
Note: The system must be run continuously (without a restart) to complete polling. Do not restart the point server
or the PC, or the polling will start again from the beginning.
Note: For the above time estimates, the average time taken between two subsequent status polling is considered
as 8 seconds. This is arrived by analyzing the HE_Logs of various sites.
Note: We also recommend that you call up graphics that may be used more frequently by the EBI operator. This
will put these points into subscription and bring them from an unknown state quicker, by interrupting the normal
poll and taking priority.

• Point detail displays and custom graphics are slow to update if more than 30 points are viewed in EBI. (ISR
148900)
Workaround: Do not have more than 30 XLS80e points on a single custom graphic page; this reduces the
overall subscription load while opening the custom graphics page in EBI.
You can use the formula below to calculate the approximate time taken to update the status of the devices in
custom graphics when opened in Station.
The time taken for status update = ( Number of points in custom graphics x Time taken to poll status of one
device )
The time taken to poll the status of one device is between 3 to 4 seconds.
This value depends on the network speed and the number of panels in XLSNet. For a site system, this value can
be accurately calculated by analyzing the HE Logs of the system and calculating the time difference between the
status polling.

• When configuring XLS80e point server points as grouped displays, the parameter selection list does not show
the XLS80e point server parameters. (ISR 181155)
Workaround: Before configuring the XLS80e points as grouped displays, open the respective point detail
display pages once and then configure the displays.

• In XLS80e point server, alarms reported on the virtual inputs and virtual outputs are reported as installation
alarms. The alarm description shows the respective Virtual Inputs/Virtual Outputs. (ISR 181257)
Workaround: None.

19
• Random reconnection of data may be observed if the system is left idle. (ISR 197512)
Workaround: Configure a trend for one point from the XLS80e point server.

• Sometimes you cannot stop the XLS80e point server service in a timely fashion. (ISR 197649)
Workaround: None.

• After deleting all XLS80e point server points from EBI and the XLS80e point server database, alarms for the
deleted points are retained in the XLS80e point server database. (ISR 199036)
Workaround: Manually delete the alarms of the deleted points from the XLS80e database and restart the point
server.

• In rare circumstances, when multiple XLSNets are removed from the network, the XLS80e point server up to
95% CPU for a few minutes after the disconnection. This results in system slowness for few minutes and
sometimes the PS reconnects with EBI. (ISR 200562)
Workaround: CPU utilization drops after a few minutes. Alternatively, reconnect the panels and
ensure successful communication.

• When an XLS80e PS event code is configured as an RTN alarm (end alarm) with non-journal priority, the event
gets reported as a new Auto RTN alarm in alarm summary page. (ISR 201105)
Workaround: It is recommended to keep the RTN alarms (end alarms) as Journal priority in XLS80e point
server alarm codes configuration. When you face this problem, change the end alarm priority to Journal in the
XLS80e management pages - Alarm codes configuration section.

• If the XLS80 point server is stopped and then restarted within three seconds, the point server data and
notification sometimes fails. (ISR 215935)
Workaround: After stopping a service, wait at least five seconds before restarting the point server.

Database
• Alarm Group and Alarm Event Types are not consistent across the disablement/enablement events. (ISR
148747)
Workaround: You must manually configure the Alarm Groups and Alarm Event types of the events so that
active disablements are returned to normal by their respective enablement events.

• When a system reset is issued in the system when Aux Modules are in a SET state, the previous Aux Module
SET alarm in EBI is cleared and the new AUX module SET alarm is not reported in EBI. (ISR 181082)
Workaround: Aux Module events are reported immediately after the System Reset event. To resolve this
increase the time delay for Aux module events by configuring the “Hold time before network transmission”
setting. Configure a time delay of 2 seconds. (This should be as low as possible or the Aux module Set events
will report with a considerable delay to EBI).

• No Reply/Missing Fault is returned to normal automatically upon restoring the fault in the field without issuing a
System Reset. (ISR 181316)
Workaround: In the Alarm Codes configuration, for the Alarm code: 21 – “Restored After Missing”, modify the
Alarm type from “End Alarm” to “Auto Acknowledge” alarm and save it.
For details on how to modify the Alarm code, refer the section – Configuring Alarm Codes in XLS80e point server
Installation and Configuration guide.

• XLS80e point server Notification link continuously reconnects when EBI triggers alarm recovery when the system
has more than 600 active or unacknowledged XLS80e point server auto-RTN alarms. (ISR 181426)
Workaround: It is highly recommended NOT to keep more than 600 active alarms or unacknowledged auto-
RTN alarms in the Alarm summary page.

• No reply/missing fault is reported to EBI even if the facility is in Disabled mode. (ISR 184221)
Workaround: In the Alarm Codes configuration, locate Alarm code number 5 – No Reply / Missing, and then

20
 reconfigure the Alarm Category from GDA_COMMS to GDA_FIRE.

• When existing XLS80e points are moved from local to remote topology by running the point build utility, XLS80e
points do not come online. (ISR 215205)
Workaround: Do the following:
1. Open the management page and delete the XLS80e install.
2. Run the point build utility using the Delete orphan points option.
3. Reconfigure the XLS80e points for remote topology.

Displays
• Quick List does not display meaningful information for XLS80e point server points. (ISR 148831)
Workaround: None.

• An error message is displayed if you click Stop Upload twice for an XLS80e controller point. (ISR 148865)
Workaround: None.

• Control Level functionality does not work for XLS80e point server points. (ISR 148870)
Workaround: You must log on using the MNGR security level to access the XLS80e point server points even
though control levels are defined for those points.

• For XLS80e point server point detail displays, if the panel name is too long, the Location path does not display
properly in the General tab. (ISR 180985)
Workaround: Instead, use the full location name of the point above the General tab of XLS80e point server
point detail displays.

• XLS80e PS Point Detail Displays do not load properly on EBI client Station when XLS80e PS was installed on an
EBI client system that was installed using the "Typical Install" option. (ISR 198192)
Workaround: The EBI Client - Typical Install option does not install the common EBI displays, shapes and
images. Hence, when the XLS80e PS Point Detail Displays are referred locally on the EBI Client Station, they will
not load properly on the Station due to missing dependent files. This will not occur if XLS80e PS is installed on
an EBI Client installed using the "Custom Install" option and enabled to deliver the EBI displays.
As a workaround, modify the connection settings on the EBI Station to refer to the displays from the EBI server
system.

• When viewed with display resolution less than 1280x1024 pixels, some of the features on the device
configuration page in XLS80e point server management pages are not aligned. (ISR 198423)
Workaround: None.

• On the Maintenance tab of the XLS80e Panel Detail page after a device upload is performed, Uploaded Panel is
displayed as a black box. In addition, Upload in Progress displays as “Yes” and clicking Stop Upload results in an
error. (ISR 198718)
Workaround: None -- the black box disappears after approximately three minutes.

• In rare circumstances, while opening XLS80e point server point detail display in EBI station, the LEDs on the
face plate shows default color for a fraction of a second and then gets updated with the current status. (ISR
199912)
Workaround: No functional impact due to this issue.

• In the XLS80e point server management pages, if you select any text and press CTRL+X the selected text is
deleted. (ISR 200259)
Workaround: Do not select text and press CTRL+X. If you delete text, refresh the page to restore the text. This
issue is not restricted to XLS80e, it also impacts the Automation Rules displays.

• When we remove the non-EBI connected panel from XLSNet, the Last Known state LEDs of that panel, devices

21
 and zones show UNKNOWN state. (ISR 200714)
Workaround: Reconnect and perform system reset to get the LED status back to normal.

• When updating the facility for multiple points in the XLS80e Management page, you can navigate to other pages
while the update operation continues in the background. (ISR 199023)
Workaround: Refresh the management page and check if the facility has been updated for points.

Hardware or Firmware
• All the sounders and controls module get enabled when we issue an "All zone inputs enable" command from the
point detail display of a local zone which does not have any inputs associated with it. (ISR 200717)
Workaround: This is a limitation in the XLS80e Panel. It is recommended not to perform zone inputs
disablement / enablement for local zones panel which does not have inputs associated with it.

Installation
• On rare occasions, when installing the point server, the sqlcmd.exe terminates abruptly and the system displays
a “T-SQL execution command line utility has stopped working” error message. (ISR 201922)
Workaround: To resolve this issue, you must uninstall and then reinstall the point server.

Management Pages
• The XLS80e point server Management pages display script and navigation errors if the point name contains plus
("+") or equals ("=") characters. (ISR 198657)
Workaround: Avoid using these characters in XLS80e point server point names.

• Performing a search in the summary page using the ampersand ("&") character does not work. (ISR 199702)
Workaround: None.

Tools
• History assignment gating point parameter is not restored when upgrading from an earlier version of the XLS80e
Point Server and EBI. (ISR 148786)
Workaround: None.

• The system allows you to start a second instance of the point utility, even though the second instance will not
work. (ISR 148788)
Workaround: Do not run more than one instance of the point utility.

• Trying to close the point utility by closing the instance does not stop the utility, which can lead to unexpected
behavior. (ISR 148789)
Workaround: Use Task Manager to terminate child processes such as pntbld.exe and bckbld.exe.

• When restarting the XLS80e point server, the Date and Time stamp of existing XLS80e alarms are changed in
the Alarm summary. (ISR 178183)
Workaround: To address this issue you can modify the Notification type of XLS80e alarms in the Alarm codes
configuration in XLS80e management pages. Change the Alarm Type as “GDA Fire Alarm” in the Alarm codes
configuration.

Note: If you change default alarm and event settings, ensure anything coming into the alarm page is updated to
be “GDA Fire Alarm”. Please contact Technical Assistance Centre for more information at HBS-
TACSupportENA@honeywell.com.

• Dragging the mouse cursor over check boxes on the Point Build Utility causes two or three tooltips to open
simultaneously. (ISR 180654)

22
 Workaround: None.

• The XLS80e point server Stop/Start command does not work from the task bar applet. (ISR 198453)
Workaround: Right-click the applet and relaunch it using the "Run as administrator” option from the tools folder
inside the XLS80e point server installed directory. You can also perform the start and stop operation from the
Windows service control manager.

23