Building Automation Knowledge Base

Issue Prevented from logging in to Security Expert due to client licenses being available. See message "Licensed number of connections exceeded" when attempting to login. Login Message Product Line EcoStruxure Security Expert Environment Security Expert Client Cause The Concurrent client connections are being used up by active Security Expert clients or clients that have not been properly logged out.   Available licenses can be confirmed by checking under About | License. The Concurrent client connections feature will show the number of used connections out of the total available for use.  Consumed Connection Licenses Resolution 1 - Log out unused Security Expert clients. Currently logged in Operators can be determined by checking the Windows application event logs Security Expert Data Service events for "New Operator Logon" and "Remove Operator by Disconnect". These contain the record id and name of the operator identifying who has logged in. Those Operators are still logged in if there is no reciprocal disconnect message seen. If it can't be determined from the Operator which machine is being logged into this can be identified by viewing currently open ports to the server using Wireshark.   2 - Correctly close the Security Expert client to release the client license Closing the Security Expert client by clicking the "x" on the windows taskbar can close the application without first logging out the current Operator. This can result in the concurrent client license not being released. To then release the consumed licenses the Security Expert server must be restarted. Taskbar Log out the Operator before closing the Security Expert client or close the Security Expert client by clicking the "x" at the top right of the client window. Close Client   3 - Operator timeout This setting is disabled by default. Set the "Enable operator timeout" setting on Operators for an appropriate time. After this amount of time with no activity the Operator will be automatically logged out releasing the client license. Operator timeout

Issue Define I/A Series AX/G3/N4 software compatible with a specific version of Windows Product Line TAC IA Series Environment I/A Series (Niagara) AX/G3/N4 software Windows 32-bit and 64-bit operating systems Cause Only specific releases of the I/A Series AX/G3/N4 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series G3/N4 software and various versions of the Microsoft Windows Operating System software.   Refer to Supported Operating Systems for Niagara 3.7 and earlier (June 2016) Refer to Supported Operating Systems for Niagara 3.8 (July 2020) Refer to Supported Operating Systems for Niagara 4.1, 4.2, and 4.3 (September 2019) Refer to  Supported Operating Systems for Niagara 4.4 and higher (March 2025)   For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Issue Security Expert Data Service fails to start with error 1067: The process terminated unexpectedly  Product Line Security Expert Environment Security Expert Server Cause Port used by the service is blocked or already in use Permission issues with the service logon account Prerequisite .NET Framework is incomplete or not installed correctly Resolution In Windows go to Windows Features and ensure that all .NET Framework items show a check mark to indicate that each sub item has been enabled. See Ensuring Windows features are installed for Security Expert SOAP service for details. In Windows Event Viewer, examine the Application log, it will typically have an entry with details about the reason for the error. In this case, we see an Address Already In Use Exception in the Socket Connection Listener. This is a clue the error is with the network port. The Security Expert data service has been configured to use the default port 8000. On the server, list the network ports using netstat. We can see PID 5660 is already using the port. Get the name of service associated with PID 5660. Once the service is identified, take corrective steps to ensure the two services don't use the same port. Make sure the Windows account the service is using to log on has the appropriate permissions. If port 8000 isn't being used, first Reboot the Security Expert PC and if the error still persists, uninstall Security Expert, reboot and reinstall.

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * CPs are available on: EBO Hotfix List Note: Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   Note: RP-C is only supported on EBO 3.0 and later SpaceLogic/EasyLogic versions compatibility SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: Previous to Version 1.0, SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 2.0 (Build 77) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well. Release Notes  Starting with Version 3.1 (Build 85), firmware 6.00.03.03007 CP2 and 7.x RC can be employed. The EasyLogic controllers are supported by the Niagara modules with these releases.  N4.10, 4.13 and 4.14 are the only versions with these modules. Product Annoucement      

Issue The VX logging functionality is not included in the 5.15 release. It is functioning in prior and later releases. Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause VX functionality was not included with the 5.15 release. Resolution Use a version other than 5.15 where the VX log is included.

Issue How do you integrate a time schedule in a Xenta programmable data manager, the occupancy command for a Xenta 121, and the override button on the associated STR-350 stat in an LNS system where everything is connected using SNVTs? Product Line TAC Vista Environment Xenta 121 Cause The desired outcome is to have all of the occupancies synchronized at all times. This will ensure the stat shows the current effective setpoint, the 121 runs the unit when appropriate, and the effective occupancy is available from the front end. Resolution Place the STR-350 in between the Xenta programmable occupancy output and the input command of the Xenta 121. Bind nvoOccupancy (user-defined name) output from Xenta programmable to nviEffectOccup of STR-350. Bind nvoOccManCmd output from STR-350 to nviOccManCmd of Xenta 121.

Issue The maximum number of backups in Vista is 20. Is it possible to change this limit? Product Line TAC Vista Environment Vista Server Cause When backups in Vista are set up, you can specify the maximum number of backups that should be created before the oldest is overwritten. The default is two, and the maximum is twenty. Resolution It is not possible to change this limit as it is a hard-coded number in Vista.

Issue How to connect a SpaceLogic IP Controller via MSTP Product Line EcoStruxure Building Operation Environment Workstation Automation Server (ASP/ASB) Space Logic IP Controller RS-485 Adapter Cause Only certain SpaceLogic IP Controller models and versions support the new BACnet MSTP Adaptor and details are required on how to configure these controllers for BACnet MSTP. Resolution The following video will illustrate how to: Configure ASP/ASB for BACnet MSTP Communication. Configure a SpaceLogic IP Controller as a BACnet MSTP device. Discover the SpaceLogic IP Controller on the BACnet MSTP network. Things you need: Software EcoStruxure Building Operation Workstation 2022 Building Commission Application (available from Google Play, Apple Store, or Microsoft Store) Hardware ASP/ASB version 4.0 or higher RP controller (hardware version 10 ) RS-485 Adaptor (Isolating or Non-Isolating) RJ45 UTP Straight Through Cable (12"/300mm or less) Note: - if the RP controller does not show MSTP settings check the Space Logic IP controller firmware release notes and install firmware corresponding to the EBO version.  For example firmware versions 3 and below do not have settings for MSTP configuration. Before attempting to install a SpaceLogic controller on MSTP consult the following: Isolated RS-485 Adapter and Non-isolated RS-485 Adapter for SpaceLogic IP controller types supporting the RS-485 MSTP adapter RP-C BACnet MS/TP Support for RP models supporting BACnet MS/TP Installing an RS-485 Adapter for information on installing the BACnet MSTP adapter Connecting an Isolated RS-485 Adapter and Connecting a Non-isolated RS-485 Adapter for port usage and CAT 5 UTP connection cable Allocating Flexible Ports for additional considerations on port usage Enabling the BACnet/IP Controller to Communicate on an MS/TP Network Please see the video below:

Issue What is its part number of the power fuse of an i2/b3 controller? Product Line Andover Continuum Environment Power fuse replacement i2 and b3 controllers 24VAC supply Cause Most controller fuses are not supplied through the factory. Resolution Faulty controllers can be repaired through the regular repairs process, but power fuses can be purchased through local suppliers. The power fuse for the following 24VAC controllers is: Type: Surface Mount Fuse NANO2® Very Fast-Acting, 448 Series Datasheet Ratings: 2A Rating: i2/b3867, i2/b3850 series. 3A Rating: bCX1, i2/b3810 series, i2/b3800 series, i2/b3600 series. 5A Rating: ACX5740, ACX5720 Note: Fuses are fitted to protect the controllers from damage, when replacing one always replace it with an equivalent rating. Also determine the reason why a fuse has blown before replacing, under normal operation a fuse should never blow.  Additional Information CX9702 (115 VA) Main Power Fuse: 250 VAC 1.5Amp Outputs: 125 VAC 3.5Amp replaceable Inputs/Outputs: Surface mount non-replaceable i2/b3814 outputs: see What is the part number of the i2814's output fuse? Note: The part numbers that used to be listed in iPortal have been removed from this article since they are no longer available from Schneider Electric. The fuses may be obtained from third-party vendors such as Littelfuse or Digikey.

  Issue Identifying a potential power supply/source failure to the Flex Server for a specific time period.  Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server went offline for some time and then came back online again. There is a need to identify if this happened due to a power source failure to Gateway.  Resolution Login to the Partner Portal and select the customer from the settings icon in the top right corner. Navigate to the Controller section in the left pane and select the particular Gateway from the dropdown. Navigate to 'Plots' tab and select 'PowerSource' Gateway stream under 'MSP430'. The 'PowerSource' stream value should always be equal to '1' as shown above. If this indicates '0' at any time, this suggests a potential loss of power supply to the Gateway.

  Issue There are issues for Flex Server to synchronize time with the Real Time Clock (RTC). Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The RTC parameter fails the synchronization test.  Resolution Check the voltage of the coin cell using a multimeter. If the voltage is less than 3.3V, replace the coin cell. If the voltage is equal to or greater than 3.3V and the test still fails, report the issue to technical support.

Issue Alarms with an invalid Source path cannot be removed from ES or AS Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation 3.0 and higher Cause The invalid path prevents alarms from being deleted. In earlier releases of EBO, there was an issue whereby an error could occur in the source path of an alarm if the Automation Server was renamed. Most invalid alarms observed originate from this type of error. Resolution Use Alarms Integrity Check in the following steps.  Automation Servers first, then Enterprise Server, and finally, if installed, Enterprise Central last. See Alarm Cannot be Acknowledged Due to Invalid Paths for additional details.   Expand System, Right-click the Alarm Control Panel,  Choose Advanced - Alarms Integrity Check.   The command runs quickly. There is no confirmation that the check has run, but a review of the alarms will show that the invalid alarms have been removed.

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 Bog File Encryption Changes in 4.15 Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 9000  Cause In Niagara 4.15, to continue to provide the best security practices, the user password hashes are now included in the encryption by the system passphrase. Resolution The system passphrase was introduced in Niagara 4 to provide additional protection to sensitive data from the Niagara system. Prior to Niagara 4.15, this included all reservable passwords (such as Niagara Network, database connection passwords, etc.), excluding the user's passwords as those are protected by being hashed. If you do not have the system passphrase for a station and need to unlock it through Workbench, both the user and encrypted data such as passwords will be removed where prior to Niagara 4.15 the user were left untouched as they are hashed. If you are copying a station from a remote host which you do not have the system passphrase for, you will need to reset the passphrase to successfully copy the station onto a new remote host. You will be required to enter the passphrase to edit or modify users or encrypted properties such as password fields for email, Niagara Network, etc. Prior to Niagara 4.15, you could edit and modify users without the passphrase, in Niagara 4.15 this will require the passphrase to decrypt the users.   Operation Niagara 4.14 Niagara 4.15 Modifying users in offline station bog file Users can be modified without entering the station bog file passphrase Station bog file passphrase is required to modify users Reset station bog file passphrase Removes reversable client passwords such as email, Niagara Network, etc. Hashed user passwords are not impacted Removes both reversable client passwords and hashed user passwords Understanding the System Passphrase in 4.15 Workbench or Supervisor When Niagara is installed on the engineering or supervisor device for the first time, the user will set the passphrase for that device. NOTE: When setting system passphrases, make sure that you take note of what they are. These should be shared with the owner of the building/site as the passphrase is owned by the device. You can change the system passphrase in the Platform Administration screen. You will be required to enter the current passphrase in order to successfully change it to a new passphrase, highlighting the importance of providing it to the owner of the building/site. JACEs & Remote Niagara Devices The passphrase is set during the commissioning process of the remote device. The remote device's passphrase can also be changed through the Platform Administration view with the same requirements as changing the Supervisor/device's passphrase.   Station Bog File Passphrases In 4.15, you will have the option to encrypt the new station with either the local system passphrase or a custom passphrase in the New Station Wizard. This passphrase is required to unlock the bog file in the user home when configuring encrypted properties as well as when copying this station onto a remote host. New Station Wizard: Note: When selecting the "Use the system passphrase" option, this is the passphrase for the local host (Workbench) Unlocking the station in the User Home: Copying the Station to a remote host with a different passphrase: Understanding how the station passphrase changes when using the Station Copier When a station from a remote host to your local host, the passphrase which is encrypting the data will be the system passphrase of the remote host. Copying a station from your local host to a remote host: For a station that originated on your local host with a passphrase encrypting its sensitive data, once you enter the current station bog file passphrase and successfully copy the station onto the remote device, it will utilize the system passphrase of the remote device when copying from the remote device back to your local host. Copying a station from a remote host to your local host: When a station is copied from the remote host, it will automatically be encrypted with the system passphrase of that remote host.   What do I do if I do not know the system passphrase of the remote host I copied the station from? In the user home,  you are able to reset the passphrase of the station, however, you will lose the encrypted sensitive data including system and user passwords. In this workflow, you have the option to remove all users except for one new super user which you provide the new username and password in the Bog File Passphrase dialog:  

Issue Enabling Scattered read for Modbus device that doesn't support it can lead to poll fail, with Point Modbus Error: Illegal function code. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (1.5 and above) Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Enterprise Server Cause Requirement to optimize communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at  Modbus Batch Read Function:   'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read.   Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the client, not as a server. You can enable the scattered read function in the properties of all Modbus devices. If a device does not support scattered read: In V6 or higher: the polls will fail with an Illegal function code, so scattered read needs to be disabled if not supported by the Modbus device. In V5 or below: the device is polled by the master device in the same way as if you had not enabled scattered read.'   The image below shows the properties dialogue window for a Modbus device and the corresponding setting.  The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'.  Refer to the Modbus TCP Device  section on Web Help for more information.     

Issue Why do the Architectural Guidelines specify a maximum of 1500 Extended Trend Logs in Automation Servers, whereas such a limitation did not exist with the Continuum Net Controllers, like the NetController II.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause EcoStruxure Building Operation's architectural guidelines specify a limit of 1500 Extended Trend Logs for the Automation Servers (AS-P/AS-B). Sites transitioning from Andover Continuum to EcoStruxure Building Operation need to understand the architectural differences that necessitate this limit. Resolution The architectural differences between Continuum and EcoStruxure Building Operation means that it is crucial that Extended Trend Logs are managed effectively to ensure ensuring optimal system performance.   In Continuum: Controller Role: Controllers do not participate in Extended Trend Log functionality beyond sending data from intrinsic logs upon request from Cyberstations. Log Management: Extended Trend Logs reside at and are managed by Cyberstations. Load Distribution: Multiple Cyberstations, configured to collaborate, maintain the Extended Trend Logs, minimizing the load on controllers.     This design puts very little load on the controllers when it comes to Extended Trend Log functionality.   In EcoStruxure Building Operation: Distributed Database Architecture: Extended Trend Logs are managed by the AS-P/AS-B servers. Server Load: The server performs tasks typically handled by multiple Cyberstations in Continuum, which often run on more powerful PC hardware. Performance Management: To prevent Extended Trend Log servicing from overwhelming the Automation Server's resources (CPU, memory), a limit of 1500 logs is enforced. Exceeding this limit can degrade server performance and potentially cause reboots due to critical memory usage.  This can be seen in the following example trace log entry: Nov 30 15:39:58 PSS-AS02 memcritsv[1011]: Memory usage critical!    

Issue PCT2 is unreachable using IP 192.168.10.2, with messages similar to: 504 Gateway Timeout Server error - server 192.168.10.2 is unreachable at this moment. Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) 2 Cause The Hyper-V Virtual Ethernet Adapter in Windows, labeled vEthernet (SwitchPctInternal), is not configured with the proper static IP address. It may be incorrectly configured as DHCP or with an incorrect static IP address Resolution Open Properties for vEthernet (SwitchPctInternal) Go to the Networking tab. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Configure the IP Address: Select Use the following IP Address. Ensure the IP address is set to 192.168.10.1. Set the subnet mask to 255.255.255.0. Leave the gateway field blank. Additional Notes Ensure that no other network adapters are conflicting with the vEthernet (SwitchPctInternal) settings. Verify that the PCT2 device is properly connected to the network.

Issue Building Commission (EBC) self closes at Login screen in Windows. It seems to be after application is unused for an extended period of time. Product Line EcoStruxure Building Operation Environment Building Commission Tool Cause There is a fault in Microsoft.ui.xaml.dll as observed in the Windows Event Viewer. Resolution Uninstall the application via Windows Add or Remove Programs Reinstall the application via the Microsoft Store Open this link in a browser Building Commission - Free download and install on Windows | Microsoft Store Click Open in Store App button in upper right by sign-in

Issue EcoStruxure Building Operation allows using a period embedded in the name of an object (i.e My.AnalogValue) and  the name of a binding variable in the Script program cannot contain a period.     In the Script program all the periods in the binding variable names have to be changed to a different character such as the underscore (_).   This in turn causes a problem for a programmer that has created many objects using the period in the names as it is now NOT possible to use the default name matching binding template. Product Line EcoStruxure Building Operation Environment Script Programs Enterprise Server Automation Server Cause Script programs do not allow a period '.' in binding variable names because the period has special functionality in the Script compiler. Resolution Create a new path matching binding template or edit an existing one to map the underscore to the period.     Here is a second example:   Name of point/value contains embedded '.' as well as spaces      This is what the binding variable would look like in the Script program   and here is the Path Matching Template

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue How do you define the number of decimal places displayed for a point? Is it possible to change the number of decimals displayed in WorkStation / WebStation? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation  Cause The operating system's regional settings determine the default resolution for decimal places displayed. This value cannot be modified within WorkStation; however, the regional settings in WebStation can be adjusted to show the desired number of decimal places. Resolution This setting applies to all displayed values except graphics, where the graphic editor can define the number of digits displayed.   WorkStation Open Control Panel Select under Clock and Region - Change date, time, or number formats As shown in the screenshot below, select Additional Settings [1]  Then adjust the Customize Format "No. of digits after decimal to your requirements" [2]. Restart WorkStation if already opened. WebStation  From the User Account drop down Select Settings Select Regional Change the Decimals from Auto to the desired number (0-6) required in WebStation.  Click Save Log off/on to WebStation to see these changes.