Building Automation Knowledge Base

Issue How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  

Issue This condition will arise after successfully installing and running Project Configuration Tool for some time. PCT 1.x can no longer initialize the virtual host adapter as a result of the adapter being deleted or removed. The errors may be a result of but not limited to: Introducing a new VPN software package to your PC/Laptop. Manually removing or modifying the Virtual Box Host Only - Network Adapter. Malware or Antivirus platforms that have removed or disabled the adapter. Example: PCT Version - 1.1.2.57 Local mode was set up on a physical laptop and used to offline engineer a project. The job was completed and PCT was not used again for roughly a month. A new project was sold and required PCT for offline engineering. The laptop was booted up and PCT failed to open. The user was presented with the following errors: "Get System State Command: 'Could not connect' " "Get predefined properties command: 'Could not connect' " "GetDashboardErrors Command: 'Could not connect' " "Get System Memory info Command: 'Could not connect' " Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only) Project Configuration Tool 1.x Cause PCT 1.x can no longer initialize the virtual host adapter as a result of the Vbox adapter being deleted or removed. Resolution Reinstall PCT 1.x on top of your current installation. Your projects will not be modified in the process. Locate the installer. Run the installer, it will ask you to remove the previous version. Press ok. Progress will show as uninstalling. PCT will prompt for installation. Click Next. Select default installation paths. Click Next. Select desired PCT mode. Click next. Ready to Install selected mode. Click Next. PCT software installed. Click Finish. Now PCT will set up the Virtual Host Adapter. Press Ok. Status bar. Compted setup dialog. Click Ok. Run PCT. If successful you will see the template sets getting installed via the top right of the window. Open a project and test an AS/AS-P. If the above steps do not work, here are a few more to try:   Restart the machine after the PCT software finishes re-installing Right-click and select “Run as Administrator” Uninstall PCT software and Oracle VirtualBox and re-install once more   If PCT 1.x still will not work, please open a support case with your local Product Support Group.

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

Issue EBO server (ES/AS/Edge) Trace.log shows COV publisher errors. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server - Standard Cause A BACnet device is misconfigured and trying to perform COV subscription that produces an error. Resolution Review EBO server Trace.log EXAMPLE:  2023-12-28 13:54:05.124 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:54:07.354 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:55:05.173 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:55:07.420 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:02.921 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:56:05.213 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:56:07.673 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:09.862 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:57:02.932 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:57:05.247 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:57:07.719 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:57:09.874 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:58:02.945 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:58:05.288 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:58:07.767 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:58:09.889 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f​ Lookup the BACnet Error Code: Decoding BACnet Errors - Schneider Electric Community (se.com) EXAMPLE:  0x8001001f is unknown object, so a device is trying to subscribe to an object (Object Type + Object ID) that does not exist. NOTE: There could be other error codes not used in this example that are reported. Enable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Information to Trace. Wait for time to pass so Trace.log can collect more records. Review EBO server Trace.log to find the new line before the error, identifying the controller with the misconfiguration. Example: MSTP device (MAC 3) on local MSTP network is misconfigured for unconfirmed COV to BV 202  2023-12-28 14:11:08.439 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 3 process 1: <binary-value, 202>, lifetime 18000s, unconfirmed 2023-12-28 14:11:08.441 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f​ Example: IP Device (MAC 192.168.198.136:47808) is misconfigured for confirmed COV to AV 204  2023-12-28 14:07:03.073 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 192.168.198.136:47808 process 1: <analog-value, 204>, lifetime 18000s, confirmed 2023-12-28 14:07:03.075 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f​ Disable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Trace to Information. Inspect the listed BACnet devices and correct the misconfiguration.

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

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 configure the relative path permissions Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Relative path permissions help configure the path permission for multiple modules (i.e.100 AS-Ps) or many different folders Resolution Here's how to give 'read-only' analog value permissions for 2 separate folders: 1. Go to Relative path permissions. Select the type of permissions desired (Full permissions for Analog Value/ NO permissions for Digital Value) 2. Go to the Local Account Group and select the Permissions tab. Under Path Permissions, add (+) the created path permissions to the desired folders. 'Folder' and 'Folder 2' are selected to have the same path permissions. Save and apply configuration.   3. When viewing the system tree, both 'Folder' and 'Folder 2' have read permission for Analog Value

Issue Is it possible for multiple Automation Servers to be placed on the same backplane and use one power supply? Some known issues in this unsupported configuration: Automation Server only partially discover the IO Modules Function Block Programs (FBP) remain in an unloaded state (see FBP Unloaded) EBO 2022 (v4.0) and higher, Alarm: IO Driver unexpectedly timed out Product Line EcoStruxure Building Operation Environment Automation Server Power Supply SmartStruxure IO Modules Cause The terminal bases provides a path for communication between all connected units on the same backplane, as such the connection of two or more Automation Servers will cause communication issues between all connected units on that same backplane. Resolution From EBO 2022 (v4.0.1) due to changes in the Central I/O (CIO), checks are now made in the Automation Server to verify that the server is physically in SLOT 2, if this is not the case, then all Tasks are disabled, and will not run.    You cannot connect more than one Automation Server to the backplane. Only one Automation Server is allowed per power supply, the architecture is always "PS-AS-....." and after that I/O modules with additional PS units as needed, but only one Automation Server can exist on the same backplane.   Note that an alarm will also generate if you have the following configuration is attempted (also not supported)  PS-AS-PS-AS  Alarms will only clear after a restart (warm) of the server 

  Issue Erratic communication problems encountered during system migration from legacy products to AS-P controllers due to mismatched duplex settings. Product Line EcoStruxure Building Operation. Environment SpaceLogic AS-P SpaceLogic AS-B Cause Legacy controllers or existing devices supporting only Half-Duplex are incompatible with AS-P/AS-B controllers, which support Full Duplex 10/100BASE-TX communications. Resolution To address this issue, follow these steps: Install a managed switch: Introduce a managed switch between the devices to enable effective communication. Configure port settings: Utilize the features of the managed switch to configure each port according to the required duplex mode, either Half-Duplex or Full-Duplex. By implementing a managed switch, you can ensure compatibility between Half Duplex and Full Duplex devices, resolving communication problems and facilitating a smooth migration process.

  Issue How are Modbus 64-bit registers calculated in the Modbus limitations on an RP-C? Can both RS485 ports be used for Modbus on an RP-C? Product Line EcoStruxure Building Operation Environment SpaceLogic RP Controller series RP-C Modbus Cause EBO version 2023 introduced 64-bit register support in RP controllers. EBO Webhelp states that an RP-C has a maximum limit of 250 Modbus registers. It is unclear if a 64-bit register is counted as four 16-bit registers or just one register on the Modbus maximum count. The RP-C controller has two RS-485 ports, and it is unclear if both ports can be utilized for Modbus simultaneously. Resolution A 64-bit Modbus register is counted as one register in the Modbus maximum register count. The RP-C controller has two configurable RS-485 ports that can be used for: Sensor bus Room bus Modbus network As per EBO webhelp, the controller can host two networks, but only one network of each network type.

  Issue How can the WorkStation "Remember me on this computer" option be enabled or disabled? Remember me option is available; user can turn on or turn off remember me: Remember me option is enabled      Remember me option is unavailable; user can't turn on remember me: Remember me option is not enabled   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The availability of the "Remember me on this computer" option is determined by the security setting "Instruct clients to allow autocomplete of credentials." If this setting is unchecked, the server will disable the autocomplete feature for username and password fields on the login page, which also affects the availability of the "Remember me" option in WorkStation. Resolution For EBO versions 3.0 and higher: Remember me for WorkStation logins can be disabled on the server by navigating to Control Panel->Security settings. For EBO version 4.0 (EBO 2022) and higher: The availability of the "Remember me" option is determined by the "Instruct clients to allow autocomplete of credentials." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option. In EBO version 6.0 (EBO 2024) and higher, this option is unchecked by default for new installations. For upgrades, the setting chosen before the upgrade will be retained. For EBO version 3.x:  The availability of the "Remember me" option is determined by the "Allow Remember me." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option.

Issue Search widget graphics can't find graphic pages created under child servers.    Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Currently, in EBO 2023, the dynamic search widget will only find graphic pages created on the server the user is logged into on WebStation. The dashboard search widget is not related to the native EBO search object and cannot search child servers. Resolution EBO 2024 (V6) or higher: From 6.0.1 it is possible to include TGML widgets from sub servers (all servers must have EBO version 6.0.1). Note that this functionality is only supported when you use HTTPS as the protocol between the servers, which is the default protocol in 6.0.1.   EBO 2023 (V5) or lower: If graphic pages are located under child servers, they need to be added to the dashboard manually.  Refer to: Adding a Graphic to a Dashboard

Issue The Insight Sensor and Multi Sensor Ambient Light Sensor require calibration before they can be effectively used. Product Line EcoStruxure Building Operation. Environment Insight Sensor. Multi Sensor Cause When setting up a new Insight Sensor or Multi Sensor device, the default settings for Gain and offset may result in inaccurate readings. Calibration is necessary to ensure accurate data collection based on the specific installation area. Resolution To perform the calibration, the following two tasks need to be carried out manually: Calibrate the Light Sensor: Conduct the calibration process in an environment without any daylight for optimal results. Set the light to 100%. Measure the lux level at the reference point using a lux meter. Adjust the gain settings on the sensor to match the measured lux level. Linearize the Feedback Signal: In some cases, lights may not provide a linear feedback (lux level) as the output increases. To compensate for this non-linearity, the signal from the controller is linearized before being sent to the output. During the optimization phase, the controller incrementally increases the output in 10% steps, measuring the adjacent lux levels for each step. The maximum lux supplement is calculated by subtracting the lux level at 100% output from the lux level at 0% output. After the optimization phase, breakpoints are determined and verified by re-running the test. If the results fall within the maximum difference limit compared to a linear signal, the calibration test is considered valid. Remember, performing the calibration process without any daylight present will yield the best results.  

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.

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