Issue Do all StruxureWare I/O modules use the same base? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Cause Want to select the correct I/O module base Resolution Yes all Building Operation I/O modules use the same SXWTBIOW110001 terminal 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

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

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.    

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

Issue The "BACnet device proxy base" type is missing in the Search type after EBO 4.0 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Building Operation SmartX Living Space Sensor BACnet B3 IA SE8000 VT8000 Cause The "BACnet device proxy base" was removed from EBO 5.x and later. Resolution To search for a specific type, add individual type to "Include types" For example 'BACnet device' will return all 3rd party (generic) BACnet devices. 'SpaceLogic Series Device' will return all MP and RP devices. Sample Search all BACnet devices(excluding AS/ES) XML attached

Issue How to create a write to file notification that creates a comma separated value (CSV) file. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) Cause Write to file notification has options for Excel and text formats, but no option for CSV format. Resolution As the name suggests, Comma-separated values (CSV) is a text file format that uses commas to separate values, and newlines to separate records. A CSV file stores tabular data (numbers and text) in plain text, where each line of the file typically represents one data record. This means that the text format can be selected in in the notification to provide a CSV file.   Building Operation 1.7 and earlier Under file name, use the extension .csv. See screenshot below:   This will produce a .csv file located in your database folder under the Notification folder.   Building Operation 1.8 and later With the introduction of "Variable Triggered Notifications" and "Alarm Triggered Notifications," users can now find the Write to File option within the "Distribution method" in the Triggered Notification Object. Within the Configure Write to File window, users will have the option to save the file with the .csv extension.   Using write to file option to save Text file with .csv extension This will produce a .csv file located in your database folder under the Notification Files folder.  File location in the system tree   For additional information and guidance, refer to the Notifications topic in EBO WebHelp.

Issue The automation server was added successfully; however, it never appeared in the server list. It did, however, get added to the communications tab. The System Tree server list varies from the Communication tab list of servers. No servers shown under "Servers" List in System Tree but is seen in Communications tab Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause This is typically caused by the Group account not having permission to access the root path.  To verify this is the issue, log in with the "admin" user account and verify that the server lists match.    Looking at the screenshot below: If the Add (+ icon) option has been used to add the ES-1 Path Permissions, no server will be visible.  Additional Path Permissions need to be added for each server. If the Add System (Hierachial icon) option is used (the default for the local admin account group), this is the System's top-level path. Then, all servers will be seen.       See online WebHelp topic User Account Group – Software Permissions Tab Resolution Depending on which method is required by the end user. If using the Add (+icon) option  Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add (+) the Automation Server(s) to the path permissions as shown below: Repeat the above step for every server Each time a new Automation Server is added, repeat all steps.  If using the Add System (Hierachial icon) option Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add System (Hierachial icon) to the path permissions as shown below: Users must log off and log on to see any of the implemented changes.    

  Issue The IoT alarm is being displayed, and acknowledging the alarm removes it temporarily, but it returns. Product Line EcoStruxure Building Operation Environment Building Operation EnterpriseServer Building Operation Workstation Lead/Shadow enabled System Alarms  Cause In Building Operation version 3.0.1, Cloud Connectivity was enabled at the Automation Server.  The alarm indicates that the Automation Server cannot connect to the Cloud server, whether attached to an Enterprise Server or Standalone, typically because there is no internet access.   By default, the option for Cloud Connectivity is set to Auto. Once the Automation Server is attached to an Enterprise Server, this option is applied in all sub-server settings and controlled from the lead object in the Enterprise Server. Resolution To prevent the alarm from triggering, Navigate to the Enterprise Server Control Panel Under the "Security and Communication" section, select Cloud Connectivity Switch the function from Auto to Disable. This change will be passed down to all sub-servers. Should the alarm not clear, a power cycle may be necessary to clear this alarm. See the following online WebHelp topic, Cloud Connectivity Overview, for further information.