Building Automation Knowledge Base

Issue The customer requests End User License Agreement (EULA) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Requests for the End User License Agreement (EULA) Resolution The EULA can be found in the following locations:   "About" box for WorkStation under the "Help" menu. See the screenshots below. WorkStation Help menu EULA   WorkStation Log on Page It is also available in the installation folder (under Workstation\language). WebHelp LICENSING END USER LICENSE AGREEMENT

  Issue  A flaw was found in handling multiplexed streams in the HTTP/2 protocol. A client can repeatedly make a request for a new multiplex stream and immediately send an RST_STREAM frame to cancel it. This creates extra work for the server setting up and tearing down the streams while not hitting any server-side limit for the maximum number of active streams per connection, resulting in a denial of service due to server resource consumption(CVE-2023-44487 from Redhat). All versions 2.13 and higher with HTTP/2 enabled are affected: 2.13, 3.0, 4.0, and 5.0. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation SmartX AS-P Server SmartX AS-B Server Cause HTTP vulnerability raised security concerns for EBO Resolution EBO isn't affected by the impacted protocol since EBO doesn't utilize HTTP 2.0 and 3.0.

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 If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it.  The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016. A defect QS#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue Requirement for a number of users to be able to access Security Expert using Web Client at the same time. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Unsure how many Web Client users are licensed with the standard license or how to add additional user licenses. Resolution Included with the base SX-SRVR license is an allowance for having three (3) concurrent Web Client operators.  Additional operator licenses (SX-WEB-OPR) must be purchased to allow Web Client logins beyond the licensed amount of three, purchase as many of these as is required.

Issue With Microsoft's new licensing model there is uncertainty around which parts of a Security Expert system need to allow for addition device CAL's for SQL Server. Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause Unclear documentation. Resolution Security Expert Controllers do not talk to the SQL Server, are not a client on SQL and do not require a CAL. The Controllers talk to the Security Expert Software, not SQL or the Operating System. A card holding user who is NOT a Security Expert Operator will not require a CAL. The Controller and any attached equipment are NOT a user in SQL, they do not inject or operate queries against it, so a CAL is not required. A CAL would be required for a Windows user to log into their Windows user account, and the Security Expert client would connect to the Server using the CAL associated with the Windows user account.

Issue There is no indication that a card has been read when being presented at a Security Expert Smart Card Reader. Product Line EcoStruxure Security Expert Environment Security Expert Security Expert Smart Card Reader (SX-DRD-??, SX-DRK-??, SX-RD-??, SX-RK-??) Cause Reader is configured but there is no LED activity or beep when a card is presented at the reader. Resolution If the Security Expert Smart Card Reader does not blink or beep, then the reader cannot read the card for one of the following reasons. Wrong technology, e.g. trying to read a 125khz card on a 13.56mhz reader will not work and vice versa The card is encoded with a proprietary format/encryption The card is encrypted and the encryption keys are not programmed into the reader (note that this is different from the above case; there are many scenarios where cards are encrypted but not proprietary and therefore if the encryption keys are programmed into the reader it can be read) If you get a single beep/short flash of the reader ports reader LED but no event/data in Security Expert it means that the reader can read the card but the format at the reader port is not able to correctly interpret the data which is why no events are being logged. Another format should be selected from the Reader Format list to suit the card type, if no suitable format exists in the list a custom format must be created.

Issue Security Expert Evaluation License is no longer working. New Evaluation License is not working. Product Line EcoStruxure Security Expert Environment Security Expert Licensing Cause The policy for Security Expert Evaluation Licenses has changed since July 2020. Now, only one Evaluation License can be tied to a specific email address. If there were multiple Evaluation Licenses assigned to an email address, all but one of those licenses have been deleted and are no longer usable. Resolution Contact your local support channel with your known Evaluation License SSN's and email address to have the valid license identified. If the license period needs to be extended or transferred to a new machine this can also be accomplished, see Transferring Security Expert licenses from one PC to another Please note: Support cannot alter the registered email address.  A new Evaluation License Request will have to be made for each required license.   

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Issue Valid cards occasionally fail to read when being badged at Card Readers enabled for both 125KHz and 13.56MHz technology. Product Line EcoStruxure Security Expert Environment Security Expert Multi-Technology Card Readers (SX-DRD-SB, SX-DRK-SB, SX-DRK-SB-BT, SX-DRK-SW-BT, SX-DRD-XB, SX-DRK-XB, SX-DRK-XB-BT, SX-DRK-XW-BT ) Cause This issue arises when Dual Technology readers and Dual Technology cards are used together on the same site. When any card is presented to the reader, it activates both the 125KHz and 13.56MHz card technologies. While this is usually fine for single-technology cards, Dual Technology cards can result in missed reads at the controller as both technologies may respond simultaneously. Resolution Dual Technology readers are ideal for sites with both older 125KHz cards and newer 13.56MHz cards. Dual Technology cards are ideal for sites with both older 125KHz readers and newer 13.56MHz readers. To prevent issues, avoid using Dual Technology cards on Dual Technology readers. Disable one technology on the readers or revert to single-technology cards.

Issue How to Discover devices on the LonWorks network. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When adding LonWorks devices to the network, it is possible to let the SmartX server scan the LonWorks network. Resolution Open Workstation and locate your SmartX server. Left-click on the SmartX server to select it. Select the "Discovery Devices" tab. In the "Select device Type" drop-down list, click to expand the options and choose "Lonworks". Right-click on the "Devices" folder. From the context menu, select "Scan network for devices". Drag from the discovered devices and drop them into your Lonworks network under the SmartX server. Commission the devices. Following these steps should initiate the device scanning process and help you discover Lonworks devices on the network.   This video will show how to discover lonworks devices on a lonworks network.   At the end of this session you will be able to: Discover devices on the LonWorks network Add the discovered devices to your system  

Issue Which Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell Sigma Environment Sigma controllers Ethernet New Hardware. ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) Old Hardware V53  (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause The newer ARM-7 controller hardware supports more Ethernet connection speeds than the older V53 controller hardware. Resolution Most Ethernet hubs or switches autoscan to find the best connection speed.  For Sigma device hardware types, the supported Ethernet speeds are as follows: ARM-7 (New hardware): 100Base-T (and supports port auto-scanning on connection) 100M Half Duplex 10M full/half duplex V53 (Old hardware): 10Base-T (does not support port auto-scanning) 10M half Duplex Additionally, for direct connections to a Sigma controller: ARM-7 Ethernet connection supports both straight and cross-over Ethernet cables. V53 hardware only supports cross-over cables.

Issue What is the benefit in having separate MPM monitor and coordinator? Product Line EcoStruxure Building Expert Environment MPM Cause In smaller networks, it is acceptable to have the monitor function as the coordinator. However, in larger networks, the monitor becomes occupied with managing the traffic of all the remote MPMs, resulting in significant CPU usage. This applies to zigbee, UDP, and CANbus networks. Making the monitor a coordinator does not provide any advantages; it only introduces disadvantages. Resolution In smaller networks, it is acceptable to have the monitor act as the coordinator. However, in larger networks, the monitor's workload increases as it manages the traffic of multiple remote MPMs, consuming a significant amount of CPU resources.

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps from WebHelp topic Repairing an EcoStruxure Building Operation Software License. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all files:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue Which SpaceLogic Sensors could be used with the TAC Xenta 100 series controllers? Product Line TAC Vista Environment ZBuilder Xenta 122 Cause The STR100-series sensors will be withdrawn, and SpaceLogic Sensors have been identified as suitable replacements. Resolution Only TAC Xenta 122 controllers can be configured to use 10K Type 3 Thermistor.   To integrate SpaceLogic Sensors with the TAC Xenta 122 controllers, follow these steps in ZBuilder: Access the Configuration tab. Navigate to the Room unit settings. Locate the checkbox labeled "Use STR-5xx series" and select it.   Please note that only the SLASXXX, SLABXXX, and SLAWXXX models are compatible with the TAC Xenta 122 controllers. These sensors, however, do not feature buttons for setpoint adjustment or fan control.  

Issue What is the minimum pulse duration for the digital inputs (X1 - X3) on the TAC Xenta 121-FC? Product Line TAC Vista Environment Vista Server Xenta 121 Cause The device requires a certain pulse duration to be able to register the feedback signal from another device, such as a fan running signal. Resolution The minimum pulse input duration is 250ms. Click here to open the datasheet for Xenta 121-FC

Issue TAC Vista Error Codes in Plain Text Product Line TAC Vista Environment Vista Server Vista Workstation Cause Vista will sometimes give an error code. This list decodes the TAC Vista Family Error Codes. Resolution For a list of TAC Vista Error Codes in plain text click here.

Issue nvoSpaceTemp from TAC Xenta 100 series used with the room unit STR150 does not read temperatures greater than 33.4 °C (92.3 °F). Product Line TAC Vista Environment ZBuilder Xenta 121 Xenta 122 STR Sensor Cause The STR150 and the Xenta 100 line of controllers are capable of displaying temperatures greater than 33.4 °C (92.3 °F) or less than 8 °C (46.4 °F). However, the communication protocol between the STR150 and the Xenta 100 series is limited and thus restricts the temperature that the TAC Xenta 100 can read from the STR150 device. Resolution The STR150 data sheet states that temperature range transferred to a TAC Xenta 100 device is limited to 8 °C through 33.4 °C (46.4 °F to 92.3 °F). If temperatures outside of that range are needed an STR100 (simple 1.8k thermistor) or an STR-350 (communicating Lon stat with display) could be substituted. The ranges of those devices connected to a TAC Xenta 100 device are as follows: STR100: –10 °C to +50 °C (14 °F to 122 °F) STR350: 5 °C to 45 °C (41 °F to 113 °F)

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 (August 2023)   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 Error message in Platform Application Director; SEVERE [00:25:32 08-Feb-21 EST][sys] Cannot boot Product Line TAC IA Series Environment I/A Series N4.9 and later I/A Series N4 Enterprise Server I/A Series N4 WorkBench Cause In 4.9.1.30 and later, the JDK distributed with Niagara was upgraded to 8u271. Starting in JDK 8u261, the target Visual C++ version was changed. While the updated libraries are available in the jre/bin folder, this folder is not on the PATH for NRE binaries. This can cause Niagara to fail to launch on Windows if another copy of the Visual C++ Redistributables is not present. Resolution Install the Visual C++ 2017 Redistributables. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads At the time of this article, Microsoft packages the 2015, 2017, & 2019 redistributables together. Select and install the x64 version.      https://aka.ms/vs/17/release/vc_redist.x64.exe