Building Automation Knowledge Base

Issue By design, the Continuum system cannot delete personnel objects until all the distributed copies can be first removed from the controller(s). In some cases the distributed copies cannot be removed from the controllers, such as when a controller is permanently offline or has been deleted. Product Line Andover Continuum Environment CyberStation Cause Communication failure between CyberStation and controllers. Resolution Starting in CyberStation version 1.94 a new feature has been added that allows the user to force a delete of personnel objects even if the distributed copies cannot be removed. In CyberStation 'Delay Distribution' dialog, a new button has been added; the button is only enabled when CyberStation is in offline edit mode. Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. Put CyberStation in Offline edit mode to enable the 'Clean up failed personnel delete distribution' button Click on the button, the system will provide the following warning Click OK to force all personnel deletions that are pending or have failed distribution to complete; any distributed copies in the controllers will be left orphaned. If offline controller returns online orphan distributed personnel records in controller can be removed by one of the following methods: Cool start the controller.  (For controllers that support access control and backup to flash such as the CX9680, ACX5720, ACX5740 . Note that personnel objects ARE NOT saved to flash memory, the controller requests a personnel distribution from CyberStation on cool start). See Restart modes of the second generation Infinity controllers for more information on cool start. Reload the controller from the CyberStation, this will perform a cold start and re-send all objects to the controller followed by a personnel distribution.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Cybersecurity vulnerability scans are flagging the Building Operation License Server because it is using HTTP rather than HTTPS Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation License Server Cause The Building Operation License Server contains a web portal for diagnostics and administration. By default, the Building Operation License Server Administration web portal is configured to use HTTP Resolution It is possible from the Administration area of the Building Operation License Server Administration web portal to configure HTTPS communications. Note: this does not change how Ecostruxure Building Operation connects to the license server.   The following process configures the Building Operation License Server Administration web portal to use HTTPS   From a web browser open the Building Operation License Server Administration web portal by typing http://localhost:8888 Once the web portal opens, select Administration at the top right. You will be prompted to log on, use "admin" as the user name. If you have logged in before, use the password you have defined. If not, enter "admin" as the password, and you will then be prompted to create a password. Once signed in Select the Server Configuration tab. Under the Secure Web Server Configuration section, select Enable HTTPS Change HTTPS Port to a unique number e.g. 8443 Select Redirect Non-Secure Web Access to Secure Web Access At the bottom of the page click the Save button and close the web browser tab. Restart the Building Operation X.X License Server from the Windows Services app (services.msc) If the license server is opened using http://localhost:8888 it will now redirect to HTTPS using the port specified in step 4 above

Issue How can I find out whether the EBO 2022 multi-version support applies to AS Classic module?  Does it apply to all the AS, AS-P, and AS-B modules? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EBO 2022 Release Note describes that the EBO 2022 Device Administrator software is not supported on the original AS classic (part number SXWAUTSVR10001) but there is no description of the software backward compatibility of the EBO on AS classic. Resolution An AS classic can continue to exist in a multi-version system; the maximum version an AS classic can operate at is 3.1.2. It is nowhere implied that it is not supported under a multi-version setup. The statement “EBO 2022 does not support AS classic” in the EBO 2022 Release Note is misunderstood. It simply means that one cannot install EBO 2022 on an AS Classic, the same as the previous EBO 3.2 version. Note that the AS Classic will not inherit any features introduced in later EBO releases when operating in a multi-version system.

Issue When performing a backup of all Servers and All Data on an Enterprise Server the backup fails and generates an error in Software Administrator indicating the backup is corrupt although the backup is not corrupt. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Enterprise Server Cause There is not enough free disk space on the Enterprise Server to save the backup file created.  The error generated in Software Administrator is a generic error. Resolution Check the Trace Log for Internal Server Error: Insufficient_Space_For_Backup If this is evident free up additional space on the Enterprise Server and re-try saving the backup.

Issue One or more inputs on the SP-ACX will randomly report as open for a brief moment (a second or less), This can result in unauthorized door access if for example the input is associated with a door Exit Request. Product Line EcoStruxure Security Expert Environment SP-ACX Cause Electrical noise in wiring Resolution Increase the Alarm input speed, issue has been seen with Alarm input speed set to 0, increasing the input speed to 1 second typically resolves the problem.

Issue A system with multiple WebRequest calls appears to become erratic after upgrading the AS-P to EBO 2022 and above. After a reboot, multiple scripts execution are hanging.   In previous EBO versions, the script would be stopped and return an Unknown Exception error message.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause The Architectural Guidelines always recommended a maximum of 5 concurrent WebRequest calls. In EBO 2022, this limitation is enforced to limit the impact on the system resources and prevent scripts stopping due to Unknown Exception errors.   Architectural Guidelines    Web requests exceeding this number will be queued, and the scripts doing these calls will hang on that function as the queue is emptied. This will directly impact the execution of other scripts.   Resolution 1. Enforce a good scripting practice to prevent more than 5 concurrent Web Request calls. 2. Cascade the execution of scripts to make sure that after a reboot, the scripts are executed in a sequence to prevent simultaneous calls filling the queue and causing scripts to be stopped.  

Issue At times it is necessary to programmatically disable a program from another program Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Server (ES/ASP/ASB) Cause A program will not just stop another program without some additional steps. In Continuum there was an ability to just name another program stop it. Resolution A program can stop itself,  however, here is a way for one program to stop another program. The user can declare an input variable in a program, check it and stop the program, based on the value of that variable. That input variable would be set from outside the program. Example: Prog1 stops Prog2 ======================== ‘Prog1 Numeric Output OutStopProg    ‘bound to the input variable InStopProg of prog2 ‘Stop program Prog2 OutStopProg = true        ‘this statement sets the input variable InStopProg  of Prog2 to true ======================== ‘Prog2 Numeric Input InStopProg     ‘bound to the OutStopProg variable of Prog1 If InStopProg = true then Stop   ‘this statement stops prog2 if InStopProg  is true  

Issue A site configured a schedule to have 2 different holiday durations during a spring break holiday week. The schedule is not working as expected. The Holiday week is set up as a range for Monday - Friday and assigned to a single Holiday group.   Two new schedule durations have been added with the respective days selected that they would like the durations to activate on. On the 2 new durations, they added the Holiday group in the "Always Active On" area.   Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Access Expert V3 Premise Cause Holiday and special date durations will activate on the holiday dates regardless of the day(s) of the week selected in the scheduled duration. The day(s) of week checkboxes in each duration is only used for setting a recurring weekly activation on those days and are not required for Holidays. For durations that will only be used during holidays, do not select any day(s) of the week. Resolution In this case, since you need two different durations during your holiday week, you will need two new durations but with different holiday groups for each duration. Set the M, W, and F duration as holiday group A and T, R for holiday group B. Now apply the Holiday Groups to the right dates via the Holidays Menu.      

Issue When configuring the in-built Visitor Management System (VMS) there is no report mechanism under the Visitor tab to show visitor access. Product Line EcoStruxure Security Expert Environment Security Expert Client Visitor Management System Cause Reports for visitors are part of the list of the Report types under the more general User reports Resolution Visitor reports for visitors using the in-built VMS can be generated with a User Report by selecting one of the following Report Type options: All current visitors All overdue visitors All visitors by date Visitor user report setup This can then be further configured to your requirements by editing the report filter. Launch the event report view in a new window by pressing the Edit in report view button. The report can be run and filters can then be configured as required and saved as the default report filter.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue What is the best order to update software and firmware from very outdated sites? Should we update the controller's firmware or Security Expert client/Server software first? Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause Controller, firmware, Client, Server, Software Resolution Update the controller's OS to 2.0.27 Then update the controller's firmware to the "interim-build" v2.08.1287 Then update to release build 2.08.1295. Firmware is located on the EcoExpert Extranet  There is no importance of installation order between controller firmware and Client/Server software

Issue Building Operation WorkStation freezes and crashes. The stack trace shows: System.ComponentModel.Win32Exception: Not enough quota is available to process this command Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause This is an error from Windows system: Not enough quota is available to process this command There are two potential causes for this error: Windows does not have enough virtual memory for all of the processes that are currently running on the machine or Windows is running out of other resources such as: disk space, handles, GDI resources, process message queue or something else. This error turns up on a lot of programs in Windows intermittently, such as Windows File Explorer. WorkStation freezes (usually because its waiting on the server) and the user tries to do a 'soft' shutdown (not a kill process) of WorkStation in the Task Manager. The Windows OS then sends instructions via the message queue (to simulate a user press on the "red cross" button on upper right in caption bar) which in turn leads to this quota error. Resolution If this error is seen, Microsoft recommends closing some applications and trying again. If you still get this message, increase the size of your paging file.   In the Taskbar Search, type “Advanced System“. You will see View Advanced System Settings. Click on it. Or you can navigate to it via Control Panel In System Properties, click the Advanced tab In the Performance section click the Settings button Performance Options will open. Click the Advanced tab Here, under Virtual memory, select Change Uncheck Automatically manage paging file size for all drives Highlight your Windows system drive Select Custom size Change the Initial size value and the Maximum size value to a higher value Click Set Finally, Click Apply/OK all the way  

Issue TAC Vista reports an error in the Alarm view that no more threads can be created and remote workstations cannot connect to the Vista server. Product Line TAC Vista Environment TAC Vista Workstation Cause This issue occurs when the TAC Vista remote computer that connects to the TAC Vista Server computer is left logged in and the Remote computer goes into hibernation. This causes the TCP/IP Thread between the TAC Vista remote computer and the TAC Vista server PC's to remain in use. Then once the TAC Vista remote computer is taken out of hibernation another TCP/IP Thread is created. Eventually this will use up the allocated thread count and generate an error. Resolution Restarting the TAC Vista Server PC will fix the issue until the TCP/IP Thread count increase to the limit again. The TAC Vista Remote Workstation computer can be setup so it doesn't go into hibernation and remains on, then the TAC Vista log off function works correctly and closes down the TCP/IP Thread. Alternatively change the TAC Vista Remote Workstations to TAC Vista Servers and configure them to look at the mastern TAC Vista server. This configuration uses a different communication setup for Server to Server communications. See the Creating TAC Vista multi-server network Knowledge Base article for further information on this configuration

Issue There are some differences between Bypassing/Clearing the Bypasses of Inputs and Trouble Inputs when Arming Security Expert Areas Product Line EcoStruxure Security Expert Environment Security Expert Controller Security Expert Keypad Arming Areas Cause Both Inputs and Trouble Inputs can be easily Bypassed when attempting to Arm an Area in Security Expert.  However, while Input Bypasses can also be cleared from the Keypad, Bypasses of Trouble Inputs cannot. Resolution The Bypassing and Clearing of Bypasses on Inputs can be carried out from the keypad.  However, whilst a Trouble Input can be Bypassed from the keypad the Bypass can only be cleared by restarting the controller from the web interface.   The following video will illustrate how to: Bypass and Clear the Bypass on an Input via the keypad Bypass a Trouble Input via the keypad Clear the Trouble Input Bypass via the Web Interface  

Issue Is there a way to bring an unresponsive/offline Security Expert module back online after a Firmware Upgrade has failed? Product Line EcoStruxure Security Expert Environment Security Expert Controller Security Expert Module Cause If there is an interruption/issue when upgrading firmware on a Security Expert module, the module itself can go offline and become unresponsive. Resolution There is a 'hidden menu' in the Security Expert controller's web interface on the Application Software tab that can be used to 'Force Upgrade' an unresponsive module to 'try' and bring it back online.   The following video will illustrate how to: Attempt to bring a Security Expert module back online after a failed firmware upgrade

Issue CSV file that has been edited with Excel does not import. There is no error given but the import has no effect. Product Line Andover Continuum Environment CyberStation Cause This problem can occur if the application used to edit the CSV file adds hidden characters. Resolution Make sure the file contains ONLY plain text. Use a simple text editor such as Notepad to avoid this issue

Issue Have the VZ22, VZ32, VZ42 valves been replaced by the VZ219, VZ319, VZ419 series? Product Line Field Devices Environment Vista Satchwell Continuum Micronet Sigma Cause VZ*19* zone valves now available with equal or better specification than the older VZ*2 valves Resolution As per PA-00911 the VZ22, VZ32, VZ42 series valves are no longer available for sale.  The alternative is the standard catalogue zone offer, either the VZ*08* with MZ140 for thermal (low cost, silent) solutions, or the VZ*19* with MZ20 for a Motoric actuator solution. The alternative range VZ*08E or VZ*19*, is lower in cost and would be a suitable replacement in most applications. For high pressure applications, the VP228E PIBCV would be a suitable alternative. There should be no technical concern with changing over a PIBCV from a zone valve if the system pressure is above 25 kPa. There will be slight dimensional differences in the zone valve body length but for most installations the existing pipework should be able to accommodate the difference. A cross reference from the discontinued offer to the new offer is detailed PA-00911.   Datasheets for all valves and actuators can be found here or here for MZ18A, MZ18B, MZ20A, MZ20B, VZ*19*

Issue What is Life Reporting? Product Line EcoStruxure Security Expert Environment Security Expert Schindler Elevator HLI Integration Cause What function does the Life Reporting feature in a Schindler Elevator HLI Integration perform Resolution Life Reporting is a feature in the Security Expert Schindler Elevator HLI Integration. The life reporting interface is how Access Events from the Schindler system are reported back to Security Expert via TCP port. When enabled, you can receive "floor unlocked" events. Multiple loggers can be configured for the life reporting interface using the same IP address. Up to 32 loggers can be configured for the life reporting interface. You can also use Schneider Electric card readers for elevator access control alongside the Schindler system. For more details including prerequisites and configuration, please read AN - 196 - Security Expert Schindler HLI Integration    NOTE: Security Expert Software v 4.1.180 or higher is required. SX Controller Firmware v 2.08.919 or higher is required. One Security Expert Schindler Elevator High Level Interface License (SX-ELV-HLI-SC) per controller is required.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Note: To enable Windows Authentication login in Security Expert, the following are required:   SX-AD-USR: Active Directory User Integration License. During Security Expert installation, "Enable Windows Authentication on Data Service / Client Communications" must be enabled. In Security Expert Client: enable "Use Windows Authentication" Found in Global | Operators| Configuration section. A site has the domain abc.xyz.com (Where ABC is the domain and XYZ is the sub-domain) When Windows Authentication is enabled, users on the sub-domain (i.e: XYZ\username) are not visible in AD Search (found in  Security ExpertX Client: Global | Operators| Username field| ellipsis [...]). Because of this, It is not possible to directly connect operators with AD sub-domain users. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause This is an Active Directory design. The Search feature for Active Directory users will have the same visibility as the machine it's installed on. (In this case, the machine was joined to the ABC domain and this is the domain Security Expert is able to pull information from). XYZ Sub-domain users might have permission to access the ABC domain but they are not on the domain. Therefore, Security Expert can't search for them. Resolution Security Expert, the machines and the users must be on the same domain: Solution 1: Manually adjust the domain on the login page ex: "XYZ\username" The XYZ sub-domain users must have ABC privileges.   Solution 2: Create duplicate users on the ABC domain This is a temporary solution because you will be left with duplicate users   Solution 3:  Change the domain structure in Active Directory to match the users, workstations and Security Expert client/server on the same domain  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue I/NET transitioned User ID Credentials that have non-numerical characters (like a dash "-") cannot be modified in the Security Expert Client Product Line EcoStruxure Security Expert,TAC INET Environment Security Expert Controller Cause Security Expert Client does not allow User ID Credentials with non-numerical characters with a dash (-) to be modified Resolution Method 1: Delete the dash from the User ID Credential the first time you need to make any other edit to that user in SX. Click Save.   Method 2: Make a backup of the existing SX database in case you want to restore what you had. Use the latest version of the INET Database Transition Tool to re-transition ONLY Users. Note: Any adjustments you've made to the User's Access Levels in SX since the original transition from INET will be lost. You will need to make those adjustments again.