Building Automation Knowledge Base

Issue When trying to run an EBO virtual server in PCT2 the following error message is received: Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information. Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The maximum number of running servers in PCT 2 has been exceeded. Resolution PCT 2 supports a maximum of 250 running servers. If this limit is reached with 250 servers already operational, no additional servers can be started.

Issue What can be used to get the Device Log (aka Error Log) from a b3 or Infinet connected to an Automation Server (AS)? Product Line EcoStruxure Building Operation Environment Building Operation Server Bacnet Infinet Cause Need to get the Device Log (aka Error Log) from a b3 and/or Infinet connected to an AS. Resolution A tool called Building Operation Device Log Viewer (SE.SBO.Device.Log.Viewer.exe), starting with v1.9 now contains a dropdown used to choose BACnet (b3) or Infinet.  Prior to v1.9, it was limited to only obtaining b3 error logs.   64-bit Windows OS Default Location: "C:\Program Files (x86)\Schneider Electric [EcoStruxure|Struxureware]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   32-bit Windows OS Default Location: "C:\Program Files\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   Note: Based on the EBO system version you are connecting, use either [EcoStruxure|StruxureWare] and version [n.n] that matches. Note: Before v1.6 it was called Building Operation b3 Device Log Viewer and had a similarly named EXE file.   The Log Viewer tries to connect to the AS-P via UDP port 33487 when BACnet is selected and UDP port 33488 when Infinet is selected.

Issue How to configure PCT memory in Hyper-V. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Hyper-V Cause There is more memory available but PCT 2.0 can't start more servers. Example: Users with over 8 GB of memory can't start more than 36 servers.  Resolution This is because the default memory is set to 8GB, approximately 36 servers. (8GB - 2GB)/.170 GB = 36 server. Open the Hyper-V Manager In the left panel, right-click on "pct" and select Settings. The Setting dialog box opens. In the left pane, under Hardware, select the Memory item. The memory settings open in the right panel. The RAM shows 8192 MB(8 GB * 1024 = 8192 MB), the "Enable Dynamic Memory box" is checked, the Minimum RAM is 8192 MB and the Maximum RAM is 262144 MB(256GB *1024 = 262144 MB).    Enter the amount of memory assigned to PCT, 10240 MB(10 GB) in the example. If the "Enable Dynamic Memory" box is unchecked, the memory assigned to PCT will be 10240 MB. If the "Enable Dynamic Memory" box is checked, the memory assigned to PCT will be between 8 GB and 10 GB(not 256 GB or other amount because the limitation is set at 10 GB from the RAM setting above). R&D recommends not using "Enable Dynamic Memory".   Helpful Link: PCT 2.0 memory usage calculation

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue SmartX SpaceLogic/EasyLogic device is offline, inspection of the device's status LED reveals a solid red pattern instead of the normal solid green.   Product Line EcoStruxure Building Operation Environment SmartX SpaceLogic Controller SmartX EasyLogic Controller Cause A solid red status LED indicates the application can't be launched, typically there could be two reasons as the root cause of this situation: The application has become corrupted, this happens very rarely. Application keeps crashing on startup. To prevent an infinite startup->crash->startup loop, the firmware in the SmartX SpaceLogic/EasyLogic devices implement a feature known as the application startup retry counter, if the application has crashed multiple times, never running for longer than an internally defined time (typically 10 minutes), the boot applet will stop all attempts to launch the application. Resolution We can attempt to recover the device by performing the following steps: Cycle power to the device. Cold start the device by holding down the reset button for more than 5 seconds but less than 9 If the controller starts up and shows a normal status LED (solid green), immediately start  a device upgrade firmware operation, the goal is to get the uprev operation going before the application crashes again.

Issue Using a VPN, the Building Commissioning Tool is unable to recognize the network adapter Product Line EcoStruxure Building Operation Environment Building Operation Building Commissioning Tool Cause VPNs have not been specifically tested and therefore are not supported Resolution Though VPNs have not been tested and are not supported, some sites have found that this is possible. If the VPN adapter IP is available then it may work, if you have a VPN adapter that does not show up, please enter an enhancement request If the above isn't available, run the tool after turning off the VPN application or Global Protect.

Issue When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The error may arise due to either the server's name not being unique or one of its child servers' names not being unique. Resolution To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.

Issue The SUM Alarm does not generate an alarm when an Automation Server goes offline Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The online status of the Automation Servers needs to be monitored so that an alarm can be generated if any of them go offline. Using the following configuration does not work. 1. Create a sum alarm 2. Add Source and set to AS path (e.g /SWXnetwork/servers/AS1). Replacing AS1 with a * makes no difference 3. Add System alarm ID and set to "Server Offline" 4. Add Alarm State and set to "Selection as required" Resolution Options that do work Option 1 System Alarm ID = Server offline Alarm Text = */Servers/* Alarm State = Alarm and Alarm Acknowledge - (Select as required). Option 2 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source Name = AS1 or AS*   Option 3 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source = /SWXnetwork/System/Server Communication/To/AS* - (As the alarm is in the ES, the path comes from the ES).

Issue How to calculate memory needed for PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause Unclear memory usage in PCT. Resolution The specifications show that the PCT default memory is 8 GB in Hyper-V. Each running PCT server takes 2 GB and 170 MB per running server. A 4-core CPU can run up to approximately 100 servers and an 8-core CPU can run up to approximately 200 servers. Memory Usage calculation example: For 23 servers, i.e. 23*0.170 GB + 2 GB = 6 GB For 36 servers, i.e. 36*0.170 GB+ 2 GB = 8 GB (default) For 47 servers, i.e. 47*0.170 GB+ 2 GB = 10 GB To start 100 servers, 100*0.170 GB+ 2 GB = 19GB   Helpful Link: PCT 2.0 memory configuration in Hyper-V

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 Services for assistance. Issue Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue When using the SBO xbk Analyzer, a warning with the following details is observed:  *** possible configuration issue *** (QC#49504)  Issue: 'Communication failed' alarms between servers, even if no bindings are made Action: Make sure servers can communicate with each other so they can synchronize. Product Line EcoStruxure Building Operation Environment Building Operation Server backups version 3.x and above.  Cause The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal. This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed. A possible scenario for this issue is: Two servers can see each other. Bindings are established between the two servers. The connection between the two servers is then disrupted (i.e., offline). Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization. Resolution  The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers. This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.   In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.   If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above.  As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.        

Issue During an Enterprise Central or Enterprise Server upgrade, the upgrade is halted with a message that the "server has not stopped". "Error: server state 'ServerShuttin'"   Upgrade Fails on Server not stopped state = starting Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause If the last shutdown of the ES/EC process was due to a crash or if it was stopped through the task manager, the current ES/EC server state is not updated, causing the upgrade to fail. Resolution Check that the server process is stopped: SE.SBO.EnterpriseServer.exe or SE.SBO.EnterpriseCentral.exe in the Task Manager. Open the database folder for the server in question, e.g., %programdata%\Schneider Electric EcoStruxure\Building Operation 3.2\db Edit the file: nsp_servers.serverstate Change the text "ServerShuttin" or "ServerRunning" to "ServerStopped". Save the file and try again (retry)

  Issue Fail to login to the selected server when the User name and Password are correct. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause In the example, the Server is in EBO 3.2.1.630 and the Workstation is 3.2.3.59. The Workstation is at a higher version than the Server but it's not the latest version. PCT loads the incorrect IP(192.168.10.2) in the WS due to the version.     Resolution PCT requires to use of the latest version of WorkStation for all releases (3.2, 4.0, 5.0, 6.0).  For example: EBO 3.2.1.630, 3.2.2.61, 3.2.3.59 and 3.2.4.1009 use WorkStation 3.2.4.4007(CP2) or above. EBO 4.0.1.86, 4.0.2.559, 4.0.3.176, 4.0.4.45 and 4.0.5.7 use WorkStation 4.0.5.3004(CP2) or above.    

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 A full backup immediately fails on the Automation Server.  Performing a configuration-only backup completes successfully. Product Line EcoStruxure Building Operation Environment Building Operation 3.x - first detected Building Operation Automation Server  Building Operation Automation Server Premium (AS-P) Building Automation Server AS-B Cause A directory under the DB folder, called tc [TypeCache], within the database of the Automation Server, had grown close to 1 GB in size.  The combination of this with the large TrendDb caused the backup failure with the following message seen in the trace log:    nsp.csc.bar.BarBackupOperation BarBackupOperation Execute failed with: Internal Server Error: Insufficient_Space_For_Backup (0x80008) in module Bar_Manager(51). "/<servername>": Insufficient space for backup, XXXXXXXXX bytes estimated for new backup but only XXXXX available   This tc directory contains types fetched from other servers that are used in runtime. These are loaded either from the local database or the tc directory. If a type for another server is not found in the tc directory when accessed, it will first be fetched from that server.   There may be other reasons for the backup failure, presenting this Insufficient_Space_For_Backup message in the trace.log. Clearing this Type Cache does not adversely affect the controller and can be cleared as the first step to see if this will allow the full backup to occur.    The issue has only been seen in Building Operation 3.x, if the issue is presented in a later revision or you continue to have failures, then contact your local support and reference this article.     Resolution To clear the Type Cache contents, follow these steps: Navigate to the RuntimeDBManager object under /System/Modules/RuntimeDBManager/ Right-click on the TypeCache object. Select Type Cache Clear All Attempt a full backup of the server again.  If failures continue to concur, then contact your local support

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   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 Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

Issue When upgrading Building Operation do new licenses need to be purchased? Product Line EcoStruxure Building Operation Environment Building Operation (All Versions) Cause Is there a requirement to upgrade (purchase new) licenses when performing software upgrades to Building Operation to make use of the new features available. Resolution Building Operation software version numbering consists of 3 fields the first of these denotes the major release version. For example: 1.9.4 - Release 1 2.0.1 - Release 2 3.0.1 - Release 3 3.2.4 - Release 3 4.0.4 - Release 4 (EBO 2022) 5.0.3 - Release 5 (EBO 2023) 6.0.2 - Release 6 (EBO 2024) An upgraded license will be required when moving between major versions of Building Operation. For example: An upgrade license needs to be purchased when a 1.9.4 system is upgraded to 2.04. An upgrade license is not required to upgrade a 3.0.1 system to 3.2.4 There is currently one exception to this rule, licenses previously purchased for EBO 2022(4.0) can also run a EBO 2023(5.0) system.   From EBO 2.0 onward a scalable licensing model has been adopted and the cost of upgrades are determined based on the declared size and capability needs of the system. For more information please refer to the Pricing Policy - EcoStruxure Building Operation and the Part Number and Hardware and Software Matrix - EcoStruxure Building Operation 2023

Issue Does EcoStruxure Building Operation support virtualization?  Can the Enterprise and Reports server be on a virtual machine? Can EcoStruxure Building Operation be installed in cloud environments? Product Line EcoStruxure Building Operation Environment VMWare Hyper-V Microsoft Azure Amazon Web Services EcoStruxure Building Operation 2.0 through current release. Cause Desire for virtualization or cloud environment. Resolution Emulating environments Virtualization has several interpretations. In this article, we'll specifically address running EcoStruxure Building Management software in emulating environments like VMware or Hyper-V. These emulating environment software packages replicate a physical PC environment, allowing multiple computers to operate on a single machine, hence the term "virtualization". Several software vendors offer emulating systems, with VMware and Hyper-V being the most prominent. The advantages of running an emulating environment include reduced physical machines, minimized space requirements, and lower maintenance costs.   It's important to note that other potential meanings of "virtualization" such as remote desktop, remote control software, terminal server environment, or cluster environment are not covered in this article.   EcoStruxure Building Management in emulating environments Currently, numerous installations are running EcoStruxure Building Management on VMware and Hyper-V without significant issues. Some challenges have been observed related to Veeam setup, which doesn't seem to integrate seamlessly with ES (and possibly EC).   VMware is utilized internally in R&D and Product Support teams with positive feedback on its performance. Users should have familiarity with the emulating product to configure settings correctly, ensuring network functionality. It's important to highlight that no specific efforts have been made to develop EcoStruxure Building Management to comply with emulating environments. Additionally, there are no specific tests to verify its functionality in emulating environments. Certain issues have been seen with the License system used by EcoStruxure Building Operation when running on specific emulating environments due to limitations in the license system's support for these environments.   Support for EcoStruxure Building Management installations running in emulating environments Product Support provides support for EcoStruxure Building Management software, irrespective of whether it runs on PC hardware or in an emulating environment. Support is provided for problems related to the EcoStruxure Building Management Software itself, but not for issues related to the environment it runs on. Except for approved operating systems and minimum memory requirements, Product Support does not offer guidance on configuring specific PC hardware or emulating environments. Cloud environments Cloud computing environments such as Microsoft Azure and Amazon Web Services provide on-demand availability of computer system resources without direct active management by the user. Cloud computing relies on sharing of resources and typically uses a pay-as-you-go model, which can help in reducing capital expenses.   One of the challenges of cloud computing is reduced visibility and control. Cloud users may not have full insight into how their cloud resources are managed, configured, or optimized by their providers. They may also have limited ability to customize or modify their cloud services according to their specific needs or preferences.   Support for EcoStruxure Building Management installations in Cloud environments EcoStruxure Building Operation has not been developed or tested with Cloud environments in mind and it is therefore not currently a supported environment.  

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue When logging into Workstation one of the following error codes is given.  Invalid returned data from license server system. (Error code: -12) Cannot connect to license server system. (Error code: -15) License server system does not support this feature (Error code: -18) The desired vendor daemon is down. (Error code: -97) Product Line EcoStruxure Building Operation Environment Workstation License Server Cause These type of issues are contributed to the License Server, Vender Daemon being down or not having a valid license for the application which is used. Here is a complete list of error codes Resolution If Workstation is installed on a different PC than the license server, refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96). If you get license error -18 refer to Error "Requested license is not available on the license Server" even though the license for the StruxureWare Building Operation is valid. Start by working through the troubleshooting steps below. In some cases the Building Operation License Server was unable to start due to antivirus programs on the computer.    Cannot connect to FlexNet License Admin Using your internet browser and go to localhost:8888. If you are unable to connect to this address then the License Server is not running.  Ensure that the Building Operation X.X License Server is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services.  Scroll through the list and select Building Operation X.X License Server. Click start in the top left corner of the window. Some times the following Windows Error 1067 is given when trying to start the License Server. Note: In the past this error has been caused by antivirus software on the computer. In this situation the antivirus program had to be uninstalled in order to allow the License Server to start.    If the Building Operation License Server will not start then it may be due to another program using TCP port 8888. Use TCPView to search for programs running on local port 8888 and stop the other program.      Vendor Daemon is Down Note: If working with a 32 bit PC, replace "Program Files (x86)" with "Program Files" in the file paths below. Using your internet browser go to the address localhost:8888. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password.  Click on the Vendor Daemon Configuration tab and then select the taclic daemon.  Verify that the path in the License File or Directory field matches the location of the taclic.lic file. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start.    Vendor Daemon is Down issue caused by ipv6 Cases have been seen where having ipv6 enabled on the same computer where the license server is running causes the Daemon is down error.  Often there will be entries in the license server logs that are similar to: 17:46:44 (demo) Lost connection to lmgrd, heartbeat timeout expired, exiting. 17:46:44 (demo) EXITING DUE TO SIGNAL 37 Exit reason 5 17:46:44 (demo) IN: "f1" user1@host1 (SHUTDOWN) 17:46:44 (lmgrd) demo exited with status 37 (Communications error) To confirm whether this is the issue ask the site if it is OK to disable ipv6 on the machine temporarily. In Windows control panel disable ipv6 Reboot the computer. In some cases, it might be needed to disable IPv6 completely in the registry: https://tweaks.com/windows/40099/how-to-properly-disable-ipv6/ If the issue is resolved then inquire with the site if it is OK to leave ipv6 disabled. If SIGNAL 37 errors are seen in the license server logs, these can be caused by having the localhost name associated with the IPv6 loopback address in the hosts file. This can cause communication problems between the license server daemon (lmgrd) and the vendor daemon, resulting in shutdown of the latter. If you have a line like the following in the /etc/hosts file: ::1 localhost ip6-localhost ip6-loopback please change it to ::1 localhost6 ip6-localhost ip6-loopback so that the localhost name is associated only with the IPv4 127.0.0.1 address. Please note that modifying this file requires Windows administrative privileges.  

Issue Files required to install EcoStruxure Building Operation Web Reports Server Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Tutorial for configuring Web Reports Resolution EcoStruxure Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and WebReports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for EcoStruxure has a tutorial which will walk you through configuring the report Server, and running reports: WebReports Overview  If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing WebReports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user".

Issue What is a Software Bill of Materials (SBOM) and how do I obtain one for EBO? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause A Software Bill of Materials (SBOM) is a comprehensive list of all software components used in a particular application or system. It provides details such as the names and versions of libraries, modules, frameworks, and other software elements integrated into the final product. SBOMs are used for several purposes:   Security: They help in identifying and addressing vulnerabilities in the software by providing transparency into the components used, making it easier to track and remediate security issues. Compliance: SBOMs assist in ensuring compliance with licensing requirements and open source software usage, helping organizations manage legal and regulatory obligations related to software distribution. Supply Chain Management: They enable organizations to understand and manage the dependencies and origins of software components, facilitating supply chain risk management and resilience. Support and Maintenance: SBOMs aid in effective support and maintenance of software by offering insights into the various components and versions used, allowing for better troubleshooting and updates. In essence, SBOMs enhance transparency, security, and governance in software development and deployment processes, thereby contributing to overall software quality and risk management. Resolution Since libraries and components contained within software may change between releases a SBOM is a dynamic document that needs to be compiled upon request. Please contact your local Product or Account management team, specifying the exact EBO version you require an SBOM for.