Issue Need to perform a diagnostic verification as a preventative measure during routine maintenance or reactively in response to cabling that is causing RSTP issues. Product Line EcoStruxure Building Operation Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller (RPC) IP-IO Cause Cabling or cabling terminations between controllers in the RSTP loop can cause issues. Resolution Reference RSTP Troubleshooting for BACnet/IP Controllers - Schneider Electric Community to ensure that: the managed switch is appropriately configured for RSTP all SpaceLogic controllers, on the RSTP loop, report RSTP Status = Operational Leave one side connected to the managed switch, plug the free end into the laptop running Wireshark, and take a capture. Ensure both ends are unplugged Plug the other side into the managed switch, plug the free end into the laptop running Wireshark, and take a capture.  Evaluate based on the information below If either evaluation fails, check the cables based on Message Age using a cable tester. It is optional but highly recommended to use a cable tester that displays cable length, as it tends to be more accurate and can point out failures that other testers may report as passing. If it passes the evaluation on both ends, then one can plug both ends into the managed switch Evaluation This capture shows a topology change (TC + Root) in RSTP, then settles out to a consistent Root Bridge Priority and Message Age. Your capture should only show a topology change when Wireshark is capturing on one end and the other end is connecting/disconnecting from the managed switch. Review the following fields: Root Bridge Priority - should be consistent and show the Priority of the Root Bridge. The root bridge can be the switch to which the RSTP loop is connected or a managed switch upstream. If it shows 32768, then another SpaceLogic controller assumed the root because it is not communicating properly back to the root bridge. (See Message Age Note) Message Age - should be consistent and show the expected number of controllers away from the root bridge. When Root Bridge Priority is 32768, you can use Message Age to determine how many controllers away the issue is occurring, and check the cabling connected to or near that controller.

Issue Understanding how to decode BACnet error values found in EBO Trace/System Logs, Controllers, and Continuum devices when documentation for the error message is not readily available. 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 BACnet error messages in logs use a combined 32‑bit value that includes: BACnetErrorClass (BEC) in the high 16 bits BACnetErrorCode (BE) in the low 16 bits Values often appear with 0x800 prefix indicating hexadecimal formatting. Without decoding, the error meaning is unclear. Example: 0x8001001F 0x10000 → Error Class = Object 0x001F → Error Code = Unknown Object Resolution Understanding the Error Structure A BACnet error value is formed as: 0x8 0 0 [ErrorClassHex] [ErrorCodeHex] High 16 bits Low 16 bits Remove the 0x800 prefix, if present. Convert high 16 bits to identify Error Class. Convert low 16 bits to identify Error Code. Common Interpretation Example Error: 0x8001001F Error Class: 1 → Object Error Code: 1F (31 decimal) → Unknown Object Meaning: Device does not recognize the object. Possible reasons include: Expected program/database not loaded Object deleted or missing b3 device memory wiped after power failure Error Classes (High 16 Bits) (From BACnet Specification 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 Codes (Low 16 Bits) A subset of codes from BACnet 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   Frequently Encountered Errors Hex Value Decoded Meaning Notes 0x8000001E Device + timeout Device offline or non‑responsive 0x8001001F Object + unknown object b3/AS memory wipe, missing database 0x80020020 Property + unknown property Invalid property reference 0x80020025** Property + value out of range Writing 0 to multi‑state object 0x80020028 Property + write access denied Permission issue 0x8002002C Property + not COV property Subscription attempted on non‑COV property 0x8002002E Property + invalid configuration data Often caused by invalid COV alarm config 0x80030000 Resources + out of memory Device resource exhaustion 0x80050007 Services + inconsistent parameters Parameter mismatch 0x80050019 Services + operational problem General service failure 0x8005001D Services + service request denied Device rejected request 0x8005002B / 0x5002B Services + COV subscription failed May appear without 0x800 prefix   **Note: This error is not limited to writing an out-of-range value to a BACnet object. It may also occur when a configuration object is incomplete or incorrectly bound. For example, a Floating Limit Alarm with no Setpoint Reference bound may repeatedly generate BACnet error 0x80020025 ("Property + value out of range"). If this error is recurring, review alarm configurations, bindings, and referenced objects in addition to checking for illegal BACnet writes. Wireshark Tip Use the filter: bacapp.type == 5 This displays APDU error packets with decoded Class and Error fields in decimal. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue Clarification is required regarding whether Cross Controller Groups can be used in Security Expert systems that use the standard Download Server, or only in systems that use the Enterprise Download Server (EDS). Additional questions were raised regarding cross-controller functionality for alarm transmission, fire door control, and communication between controllers. Product Line EcoStruxure Security Expert Environment Security Expert Security Expert standard Download Server Security Expert Enterprise Download Server (EDS) Security Expert version 4.3.393.3 and later Cause Changes introduced in Security Expert version 4.3.393.18 modified how controller relationships are managed, resulting in different Cross Controller Group requirements for EDS and non-EDS deployments. Resolution Cross Controller Groups can be used without EDS. Beginning with Security Expert version 4.3.393.18, Cross Controller Groups are mandatory when using EDS and optional when not using EDS. For Security Expert versions 4.3.393.3 through versions earlier than 4.3.393.18, Cross Controller Groups needed to be created for both EDS and non-EDS sites. Cross Controller Group functionality can be used to reduce communication and .dat file size in non-EDS systems by grouping controllers, for example creating one Cross Controller Group per building. This limits .dat files to include only controllers within the same group. However, communication between controllers in different groups is blocked. The commands described in AN 180 Security Expert - Cross Controller Operations - Integration Guide (LocalIP = *,#) are only required in specific network configurations where NAT or port forwarding is used and controllers must communicate directly with each other. When controllers and the Security Expert server can reach each other through normal IP routing, the commands outlined in AN 180 Security Expert - Cross Controller Operations - Integration Guide are not required. For fire door control, a controller-level design using dedicated relay outputs connected directly to inputs on each SP-C controller is recommended to avoid dependence on network communication between controllers. Where a cross-controller solution is required, maintaining separate local door groups per controller is preferred over creating large door groups spanning multiple controllers.

Issue The Calendar Actions page can become slow to load and manage when a large number of historical Calendar Actions exist. Customers may also want clarification how Calendar Actions are retained in the controller and Security Expert database. Product Line EcoStruxure Security Expert Environment Security Expert Cause Historical Calendar Actions are not automatically deleted from the database and must be removed manually. A large number of accumulated Calendar Actions may negatively affect Calendar Actions page performance. Resolution 1. Hide old calendar actions setting Enabling this option will not remove old calendar actions, it will "hide" them from the operator when viewing the calendar actions page. If the option is then disabled, the old calendar actions will be seen again. The point of enabling the option is to hide actions that have already passed, so Security Expert will not load them when the Calendar actions page is opened. This reduces the amount of information the Calendar action needs to load when be viewed and will help it load faster.   The description in the documentation and the online help is wrong. Hide old calendar actions: Select this option to automatically clear calendar actions from the system once they become invalid (Sites | Calendar actions). This should read: Hide old calendar actions: Select this option to automatically hide calendar actions from the list once they have passed their activation time.   2. Calendar action retention in the controller Old actions are not retained in the controller. When a controller downloads the day after a Calendar Acton has expired, it will remove this Calendar action from the controller.   3. Calendar action retention in the Security Expert database Calendar Actions are not removed from the database and will need to be removed manually, as there is currently no supported mass-deletion method available. An internal tool, Calendar Cleaner utility, can help assist cleaning up old Calendar actions in the database. This can be supplied on an as needed basis by raising a case with Product Support. A product enhancement addressing Calendar Action cleanup behavior has been identified by Engineering. A permanent implementation is planned for Security Expert, although no release timeframe is currently available.

Issue Can the Power Supply (PS), Automation Server (AS/AS-P), and I/O module backplane assembly be installed vertically instead of horizontally when cabinet space is limited? Product Line EcoStruxure Building Operation Environment Power Supply (PS-24V) Automation Server (AS-B, AS-P, AS-P-3) Central I/O Modules Hardware installation in control cabinets Cause Customers may prefer a vertical installation due to cabinet layout constraints or conduit routing. Questions may also arise regarding whether more than one Automation Server can be connected to a single Power Supply. Resolution The system is designed, tested, and supported for horizontal mounting only. Vertical installation is not a supported mounting method because it reduces the effectiveness of the modules' natural convective air cooling. Reduced ventilation can increase the internal operating temperature of the modules, which negatively impacts component lifetime. Key considerations: The system is specified to operate at temperatures up to 50°C (122°F) when mounted horizontally. Increased internal temperature can significantly reduce the lifetime of electrical components. The Automation Server (AS) is considered particularly sensitive because: The CPU generates heat. Critical power-retention components used during shutdown and restart are affected by elevated temperatures. During normal operation, no immediate symptoms may be visible. Long-term exposure to elevated temperatures can result in hardware reliability issues, including failure to restart after a power cycle. Vertical Installation Considerations Ambient temperature should not exceed 35°C (95°F). Power supply loading should be reduced from 30 W to 25 W. Convective air cooling relies on warm air rising through the module enclosure and being replaced by cooler air from below. Horizontal installation supports this airflow pattern and is therefore preferred. Risk Mitigation To minimize risk when cabinet constraints exist: Always mount the Power Supply (PS) and Automation Server (AS) horizontally whenever possible. I/O modules may be mounted separately and connected using an S-Cable. If operating temperatures are near the maximum rated temperature, provide cabinet ventilation or external cooling in addition to mounting the PS and AS horizontally. I/O Bus Backplane Requirements More than one Automation Server cannot be connected to the same backplane because the backplane provides a communication path between connected units and Automation Servers cannot communicate on the backplane. The I/O Bus supports 32 slots, including the Power Supply and Automation Server. Empty backplane positions still consume a slot. Additional Information Refer to the SpaceLogic and EasyLogic Hardware Installation System Guide for complete installation, power budget, cooling, I/O bus, and wiring requirements. Important installation requirements include: Install the Power Supply, Automation Server, and Central I/O modules horizontally with the device label upright and reading left to right. Install devices on a horizontal DIN rail to ensure proper airflow and cooling. Vertical installation may exceed thermal specifications and reduce product lifespan. The I/O bus supports a maximum of one Automation Server per I/O bus. I/O bus device order must be maintained: Position 1: Power Supply Position 2: Automation Server Position 3-32: Central I/O modules and additional power supplies as required The I/O bus supports a maximum of 32 positions. S-cables may be used to connect multiple DIN rail sections while maintaining I/O bus continuity. Conclusion: Horizontal mounting is the only supported installation method. If vertical mounting is used, it is not a supported installation method and is performed at the installer's risk. Maintaining operating temperatures well below the maximum rated value is critical to reducing the risk of reduced product life and long-term reliability issues.

Issue Customer requires CMOS battery replacement information for an AD v3. Official replacement kit unavailable. Need an approved or compatible alternative. Product Line EcoStruxure Building Operation Environment Advanced Display v3 (ADv3) Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. 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. Cause The issue is caused by depletion or failure of the CMOS/BIOS battery in Advanced Display (AD v3) units. When the battery can no longer maintain BIOS settings and system clock information, the display generates CMOS battery errors, becomes unavailable and fails to operate as expected.   Resolution Replace the failed CMOS/BIOS battery. The official replacement component is SXWADBATKIT10001 SpaceLogic Advanced Display V3 CMOS Battery Replacement Kit.  If the kit is unavailable, a compatible CR2032 3V battery with a 2-wire Molex micro-connector may be used. Follow the WebHelp replacement procedure Replacing the CMOS Battery in AD v3.  Validate that the display resumes normal operation and CMOS errors are no longer present.

Issue After enabling HTTPS on Security Expert controllers and rebooting, HTTPS access does not work and the expected Public Key/Certificate is not generated. The HTTPS option may appear enabled, but the controller cannot be accessed using HTTPS. Product Line EcoStruxure Security Expert Environment Security Expert SP-C controllers Single Record Download Service (SRDS) Warning Potential for Data Loss: Ensure all important data is backed up before proceeding. Cause The controller HTTPS configuration may not be retained when certificates do not match, when no certificate is loaded on the controller, or when the controller does not have a factory default certificate. A known issue may also prevent generation of a new certificate when SRDS has previously been connected to the controller using HTTPS. Resolution Reinstall the HTTPS certificate on the controller by following the HTTPS certificate configuration procedure described in the AN 314 Security Expert - HTTPS Connection to the Security Expert Controller - Integration Guide application note. Factory default the controller to remove existing custom certificates and reload the factory certificate. Re-enable HTTPS and encrypt the controller again with HTTPS active. If the controller has previously been connected to Single Record Download Service (SRDS) using HTTPS, review the known certificate regeneration workaround documented in the AN-309 Single Record Downloads in Security Expert application note.

Issue A replacement b3 controller cannot be commissioned or downloaded in EcoStruxure Building Operation.   The following error is reported: Property inconsistent selection criterion BACnet The trace log shows: Commission Canceled Model Number in DB does not match B3 on MS/TP Network. Product Line EcoStruxure Building Operation Environment EBO version 7.1 AS-P - Automation Server Premium HW Ver 062 b3 on MS/TP Legacy conversion / transition project Cause The b3 controller hardware model does not match the controller model configured in EcoStruxure Building Operation. In this case, the physical controller was a b3865-V, while the device was configured in EcoStruxure Building Operation as a b3866-V. The trace log indicated that the model number in the database did not match the b3 controller detected on the MS/TP network. Resolution   In this case, the configured controller model was updated to match the actual controller hardware. The device was exported to an XML file, removed from EcoStruxure Building Operation, modified in the XML file by changing the model from 866 to 865, and then recreated by importing the updated XML file. After the configured model matched the physical controller hardware, the issue was resolved.   Note: The difference between the b3865 and b3866 controller models is that the b3866 supports damper feedback. If the differences between the configured controller and the installed hardware are more significant, the hardware may need to be replaced to match the configuration.   Validation: After updating the configured model to match the physical controller hardware and re-importing the device, the controller commissioned successfully and the download completed without the "Property inconsistent selection criterion BACnet" error.

Issue When selecting a building in the Clients view, the message "Building no longer available for selection" is displayed, even though the building was available when the Clients view was initially opened. Product Line EcoStruxure Building Advisor Environment Building Advisor Portal Cause The building was available when the Clients view was opened, but an administrator has since either restricted access to the building or deleted the building. Resolution Refresh the browser to update the organization tree. Validate that the building is visible and accessible after the organization tree has been refreshed.

Issue A user cannot access the Building Advisor Portal or view the organizations, clients, buildings, or resources they are expected to access. The user may be unable to log in or may have insufficient permissions to perform required actions. Product Line EcoStruxure Building Advisor Environment Building Advisor Portal Cause The user account does not have the required access privileges assigned for the target organization, client, building, or portal. Note: Admin privileges are required to add users and assign access privileges. Resolution To add a user and configure access in Building Advisor Portal: Open the Menu and select Users. In the Users view, select Add User. Enter the user's email address in the Email Login field. If the user should only access Customer Portal, select User is a customer. This disables access to Building Advisor Portal. To grant Customer Portal access, expand the appropriate resource in the Portfolio column and select the checkbox in the Customer Portal column. To grant Building Advisor Portal access, expand the appropriate organization, client, or building in the Portfolio column and select the required access type in the Access column. Click Save. Admin users can assign access privileges that are equal to or less than their own privileges. Validate the configuration by confirming that the user can log in and access the assigned resources.

Issue A user is unable to create or delete other users within the system. Product Line EcoStruxure Building Advisor Environment User Roles and Organization Permissions Cause The assigned role does not provide the required administrative permissions. Users with View or Edit privileges only have access to clients and buildings where Effective Access is not set to None. Administrative functions such as creating or deleting users require Admin privileges at the organization level. Resolution Verify the user's role assignment within the organization. View and Edit privileges apply only to clients and buildings that the user already has access to (Effective Access not equal to None). Admin privileges apply to all clients and buildings in the organization, future clients and buildings added to the organization, and the organization itself. None provides no access to the organization, clients, or buildings. If the user needs to create, modify, or delete other users, assign the user an Admin role for the organization. After updating the role, validate that the user can perform the required user management actions.

Issue After upgrading EcoStruxure Building Operation, Modbus communication performance may change, older devices may generate offline alarms, and Modbus bindings between Enterprise Server and attached servers may no longer function correctly. Systems using Modbus bitmask objects may require binding updates after upgrade. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 5.0 and earlier EcoStruxure Building Operation 6.0 and later EcoStruxure Building Operation 7.0 and later Modbus TCP devices Modbus Serial Client Enterprise Server Attached field servers Cause Changes to Modbus communication architecture introduced in version 6.0 and the Modbus bitmask structure introduced in version 7.0 can affect communication behavior and existing Modbus bindings. External bindings between Enterprise Server and attached servers are not automatically converted during upgrade. Resolution After upgrading from version 5.0 or earlier to version 6.0 or later, run Modbus diagnostics after several days of operation to evaluate device performance and connectivity. Based on the diagnostic results, adjust settings or configurations on Modbus devices if required. Be aware of the following Modbus Serial Client changes in version 6.0 and later: Silent character is fixed at 3.5 and cannot be changed. Poll delay defaults to 10 ms and cannot be changed. Existing customized values from earlier versions are retained but hidden. Poll delay (%) is obsolete because compatible Modbus devices communicate in parallel. When upgrading to version 7.0 or later, valid Modbus objects configured with bitmasks are converted to the new bitmask structure. Internal server bindings are updated automatically. External bindings between Enterprise Server and attached field servers must be updated manually on the server that owns the binding. To update Modbus bindings between EcoStruxure Building Operation servers: In WorkStation, expand the System folder and select Upgrade history. Open Moved objects properties and save the content as a text file. Open the objects that contain external Modbus bindings. Right-click the object and select Edit bindings. Copy the existing binding path. Open the Moved objects file from the target server. Search for the copied binding path. The old and new paths are separated by "->". Copy the new binding path from the target server entry. Paste the updated binding path into the Edit bindings view on the source server. After the binding path is updated, the binding is corrected.   Validation Verify previously affected Modbus devices remain online and no recurring offline alarms are generated

Issue IEEE 802.1X Operational Certificate on a Linux-based Edge Server using Device Administrator. Product Line EcoStruxure Building Operation. Environment Linux-based Edge Server Device Administrator BACnet/SC certificate management Cause IEEE 802.1X is not supported on Edge Servers. IEEE 802.1X operates at Layer 2 of the OSI model and is intended for authentication between physical network devices and network infrastructure. Resolution Edge Server is a software-only component and does not function as a Layer 2 network device.

Issue A license violation warning is displayed in WorkStation after configuring both the local License Server and a secondary License Server address. When only the local License Server is configured, the license violation warning does not occur. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 6.0.x - 7.1.x Enterprise Server License Administrator License Server Cause When the secondary License Server address is getting added, License Administrator displays a warning indicating that WorkStation, Enterprise Server, or Enterprise Central was still running on the computer. The license server address change may not be applied successfully when EBO components are running. A full license reset and reconfiguration resolves the issue.     Resolution Perform the following steps to reset and reconfigure the licensing setup: Close all WorkStation sessions or windows on the local machine. Stop the Enterprise Server service. Return the current license. Uninstall License Administrator. Perform an SBO full according to License server Reset   or Manual License server Reset Install License Administrator. Activate the license. Add the secondary License Server address after a semicolon in the address field and apply the changes. Start the Enterprise Server service using Software Administrator. Launch WorkStation.  

Issue A customer asks whether events generated by an SP-C controller while it is offline from Security Expert will be uploaded when communication is restored. Product Line EcoStruxure Security Expert Environment SP-C Controller EcoStruxure Security Expert Cause The SP-C controller stores events locally when it is offline from the Security Expert Event Server. The controller retains up to 50,000 events in its event buffer using a FIFO (first in, first out) method. Resolution When the SP-C controller reconnects to the Security Expert Event Server, the buffered events are uploaded to the Security Expert server. The controller can store up to 50,000 events while offline. If the buffer reaches capacity, older events are overwritten by newer events. For extended offline periods, only the most recent 50,000 events are retained. Be aware that performing a firmware update clears the controller event buffer, so ensure required events have been logged to the event database before updating firmware.

Issue After reinstalling Project Configuration Tool (PCT), the user is unable to log in using the "admin" account and receives an invalid login attempt. The issue may also be accompanied by installation-related errors such as: "The setup has detected no version of SBO Project Configuration Tool is installed" Error code 1603 Error code 1722 Product Line Project Configuration Tool Environment Project Configuration Tool (PCT) 2.x Cause The default password may not be used after reinstallation, or residual PCT installation files may remain on the system and prevent the login issue from being resolved.   Starting a new PCT installation before removing the existing PCT folder can leave residual files in place and may prevent the login issue from being resolved. Where project data must be retained, export projects and create any necessary server backups before removing the PCT virtual machine or performing cleanup activities required for reinstallation. Resolution Verify that you are using the correct default administrator password for PCT. If the issue persists, fully remove the existing PCT installation: Open Hyper-V Manager Shut down and delete the PCT virtual machine. Delete the PCT installation folder: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool If installation or uninstallation errors occur, back up the Windows Registry and remove the registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Reinstall PCT 2.3.1 and log in using the default password Admin-11. If the issue remains unresolved, contact local Schneider Electric support.    

Issue After upgrading previously licensed AS-P controllers to EcoStruxure Building Operation 7.1.2, JCI/N2 SmartDriver licenses were no longer recognized correctly by the Enterprise Server. The Enterprise Server reported license deficits and licensing alarms, while AS-P controllers appeared licensed locally. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 7.1.2 Enterprise Server (ES) AS-P controllers SmartDriver license supporting communications with N2 bus and devices using AS-P for one COM port and TCP Cause In EcoStruxure Building Operation 7.0 and later, the SmartDriver license no longer functions as an AS-P local license in the previous manner. Upgrading AS-P controllers does not automatically migrate SmartDriver licenses from the AS-P controllers to the Enterprise Server, resulting in a licensing mismatch where the Enterprise Server reports deficits while the AS-P controllers appear licensed. Resolution Return the existing SmartDriver license entitlement, re-add and reactivate the license using Device Administrator 7.1, and assign the license to the top-level Enterprise Server. After the license is assigned to the Enterprise Server, allow the Enterprise Server to distribute the licensing to the AS-P controllers. After the license was returned, reactivated, and assigned to the Enterprise Server, the licensing error was resolved.

Issue Older controllers and takeover installations may not provide access to the Connection Type field in the controller web page. This field contains the communication settings required to connect the controller to the Access Expert host server. When the Connection Type field is unavailable, the controller cannot be commissioned or brought online.  Product Line EcoStruxure Access Expert Environment Access Expert Client Panel Utility (PanelUtil.exe) OEM Conversion Tool Cause When using older versions of firmware, the controller web interface does not provide access to the Connection Type setting required for host communication configuration. In some cases, the controller is configured as IP Server when IP Client is required. Older firmware versions may also prevent the Panel Utility from accessing or displaying all communication settings. Resolution Acre recommends using the Panel Utility to modify the controller communication settings and configure the controller for IP Client operation. The PC running PanelUtil.exe must be connected to the same local network as the controller. 1. Obtain and Launch the Panel Utility Request a copy of the Panel Utility from Product Support. Extract the utility files. Launch PanelUtil.exe. 2. Discover the Controller Click Discover. If no controllers appear, disable TLS through the controller web page (Data Security Field) Note: SSC controllers do not appear in the discovery list. 3. Attach to the Controller Select the desired controller. Click Attach. Verify the communication details. Click OK. Note: The example shown displays the Communication Type as 103 IP Server, which must be changed to IP Client. 4. Change Communication Settings Select Comm Settings. Open the Host Comm tab. Select IP Client as the Connection Type. Configure the required host communication settings. Click Apply Settings. Reboot the controller. 5. Browser Access from Panel Utility Selecting Browse while a controller is highlighted launches the controller web page. The utility is known to work with Microsoft Edge and Mozilla Firefox. Google Chrome may not function correctly. Multiple attempts may be required before establishing a successful connection.  6. OEM Conversion and OEM Credits Once the controller communication type is configured as IP Client, OEM Credits can be applied directly from within Access Expert. The OEM Conversion Tool displays available OEM codes and automatically assigns a code when available from within Access Expert.  7. Blank Communication Settings For very old controllers, the Panel Utility may not provide access to the required settings. In these cases, use the OEM Conversion Tool. (Request via PSS). If all communication settings appear blank after attaching to the controller, upgrade the controller firmware using the OEM Conversion Tool. After the firmware upgrade, the communication settings should become visible and editable. Open the Access Expert Client. Open the controller. Click Update OEMCode. Allow the system to assign an available OEM code. Proceed with normal commissioning. 8. Additional Troubleshooting if having issues connecting to the Panel Utility The controller is not on the same subnet as the PC running the Panel Utility. The controller firmware is too old for the Panel Utility to access all settings. TLS remains enabled during configuration. A firmware upgrade is required before communication settings can be modified. 9. Validation After the Connection Type is changed to IP Client, the host settings are configured, and an OEM code is applied if required, the controller can be commissioned through the standard Access Expert workflow. 

Issue During upgrades of AS-B controllers, some controllers upgrade successfully while others fail multiple times before eventually succeeding. Reported errors include timeout messages, download failures and connection loss during file transfer. In some cases, the controller became unresponsive after a failed upgrade and required recovery before another upgrade attempt. Product Line EcoStruxure Building Operation Environment Automation Server Bundled(AS-B) Cause Finding from the investigation was that a process timed out because an operation on the AS-B side was taking too long to complete. Resolution Recommendation if similar issues is seen. Perform a power cycle of the AS-B before the upgrade. Running the upgrade with the AS-B disconnected from the network and field bus connections where possible. If an upgrade fails, restore a backup taken before the upgrade and retry the process. . 

Issue Does EcoStruxure Building Operation (EBO) support virtualization? Can Enterprise Server, Enterprise Central, and Reports Server be deployed in virtual machines? Can EBO be deployed in containerized or cloud-hosted environments? Product Line EcoStruxure Building Operation Environment VMware Microsoft Hyper-V OCI-compliant container platforms Docker-compatible runtimes Kubernetes Microsoft Azure Amazon Web Services (AWS) Private Cloud Environments EcoStruxure Building Operation 2.0 through current release. Cause Customers increasingly deploy applications using virtualized, containerized, and cloud-hosted infrastructure to improve scalability, resiliency, system management, and operational efficiency. Questions often arise regarding the supportability of EcoStruxure Building Operation in these environments and where Schneider Electric support responsibilities begin and end. Resolution Virtualized Environments Virtualization allows multiple operating systems or servers to run on shared physical hardware through software platforms such as VMware and Microsoft Hyper-V. EBO has been successfully deployed in virtualized environments for many years. Enterprise Servers, Enterprise Centrals, Reports Servers, WorkStations, and other EBO components may be installed within virtual machines, provided the deployed operating system and allocated resources meet the requirements specified in the applicable product documentation and specification sheets. Benefits of virtualization can include: Reduced hardware footprint Simplified backup and recovery Improved scalability Easier system lifecycle management Enhanced infrastructure resiliency Schneider Electric supports the operation of the EBO software itself. Customers and system integrators remain responsible for the design, configuration, maintenance, and operation of the virtualization platform. Containerized Environments Current EBO offerings support deployment models utilizing Linux operating systems and OCI-compliant container technologies where described in the applicable product specification sheets and deployment documentation. Examples of OCI-compliant container technologies may include: Docker-compatible runtimes Kubernetes-based container platforms Container runtimes, orchestration platforms, host operating systems, storage infrastructure, and supporting services remain the responsibility of the customer, hosting provider, or system integrator. Cloud Environments The supportability of cloud-hosted deployments has evolved across EBO releases. EBO 6.x and Earlier EcoStruxure Building Operation versions 6.x and earlier were not developed, qualified, or supported for deployment in public cloud environments such as Microsoft Azure or Amazon Web Services. Customers who choose to deploy EBO 6.x or earlier releases in cloud environments do so at their own risk. Schneider Electric Product Support may not be able to provide assistance when cloud infrastructure, cloud networking, or cloud platform services are contributing factors to the reported issue. EBO 7.x and Later With EcoStruxure Building Operation 7.x, support for modern hosted deployment architectures has significantly evolved. Current EBO offerings support deployment models utilizing supported operating systems, Linux-based deployments, OCI-compliant container technologies, and hosted infrastructure environments when deployed according to published product requirements and specification sheets. Cloud-hosted deployments may include: Microsoft Azure Amazon Web Services (AWS) Private cloud environments Hosted infrastructure services The deployed operating system, allocated resources, network configuration, storage configuration, and connectivity requirements must comply with the applicable EBO documentation and specification sheets. Support Boundaries Schneider Electric Product Support provides support for issues determined to be within the EcoStruxure Building Operation software itself. Support is provided regardless of whether EBO is installed on: Physical hardware Virtual machines Containerized environments Supported cloud-hosted infrastructure However, Schneider Electric does not provide support for the design, administration, configuration, or troubleshooting of third-party infrastructure technologies. Examples include: VMware administration and configuration Hyper-V administration and configuration Kubernetes administration and orchestration Container runtime troubleshooting Microsoft Azure infrastructure configuration Amazon Web Services infrastructure configuration Cloud networking and routing Firewall and security policy configuration Operating system administration Storage platform administration Third-party backup solutions If an issue is determined to originate from the underlying infrastructure rather than the EBO application, customers may be required to engage their cloud provider, virtualization administrator, operating system administrator, or other infrastructure specialists for further investigation. Additional Considerations Successful deployment of EBO in virtualized, containerized, or cloud-hosted environments requires careful consideration of: Network latency and bandwidth DNS and name resolution Internet connectivity requirements Time synchronization Storage performance Backup and recovery strategies Cybersecurity requirements High availability and disaster recovery design Schneider Electric recommends that all deployments follow the requirements and recommendations documented in the applicable EBO product specification sheets and deployment guides.