Issue A license violation warning is displayed on an EcoStruxure Building Operation server when using ION client interface features, even though an Advanced license is activated. There is also uncertainty about which license tier includes the ION client interface. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 7.1.x Advanced Tier license activated Cause The license warning is triggered because ION client functionality (including tenant billing) is currently classified as preview capability and is not mapped to any available EcoStruxure Building Operation license tier. Resolution This is expected behavior in EBO 7.1.x and no corrective action is required, the warning can be safely ignored when it appears in relation to ION client features. The warning may be triggered when interacting with ION-related functionality. Core EcoStruxure Building Operation functionality remains fully operational. There is no impact on system performance, stability, or licensing compliance for supported features. Validation To confirm the condition is understood and no issue remains: Verify that standard Building Operation functions continue to operate normally. Confirm that no other unrelated license violations are present. Ensure the warning is only associated with ION-specific features. Additional notes ION functionality, including tenant billing capabilities, is not currently part of standard licensing and may have limited or controlled availability. Availability of these features may change in future releases.

Issue After installing SmartConnector components and configuring the EBO EWS interface according to the official integration guide, the EWS server remains in an offline state in EBO, generating alarms “Gsoap_Communication__Error: 65535” and “Device offline.”     Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert WorkStation EcoStruxure Building Operation Security Expert SmartConnector Cause The EWS Server is disabled by default; if not enabled, communication between SmartConnector (SC) and EBO via EWS cannot be established, preventing SC values from being updated or reflected in EBO. Resolution Enable the EWS Server in EBO WorkStation to allow SmartConnector communication via EWS. Log in to EBO WorkStation to the Enterprise/Automation Server. Navigate to Control Panel - Web Services under the target server. Open EWS Server Configuration. Select Enable EWS Server.      

Issue After performing server upgrades using Device Administrator, attempts to download the database fail. The server remains in a "Ready for download" state, which cannot be cleared.   Device Administrator Download Fail error Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server. Building Operation 2023 (version 5) and above Cause This happens when a Consolidation Point (CP) or Hotfix has been applied. These updates do not include server packages in Device Administrator, causing download failures during post-hotfix upgrades.  DFU upgrades and base version upgrades of the installed Device Administrator still function as expected. Resolution This issue is cosmetic and does not impact server functionality; there’s no operational need to upgrade (download) servers after applying a hotfix or CP. However, to clear the persistent "Ready for download" state: Navigate to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.0\Device Administrator Note: The listed path is within a hidden folder in Windows. Enable Windows to view hidden folders if unable to locate this path.  Locate the folder: Find the folder named tmp[SerialNumber] (e.g., tmpSM22111234) that correlates to the server(s) serial number showing the state "Ready for download" Delete all files inside that folder. Restart Device Administrator if it’s open. This will clear the "Ready for download" status.  

Issue No standard test or performance validation procedure is available. Each EcoStruxure Building Operation system requires a site-specific approach based on its configuration. Guide on what to check after EBO / Windows updates Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Central (EC) Enterprise Server (ES) Automation Server (AS) WebStation WorkStation PostgreSQL / Timescale Database (if used) SQL Server (if used) External databases (if used) Third-party interfaces (if used) Cause When validating system performance (for example, after an upgrade or Windows updates), a standard procedure may be expected; however, EcoStruxure Building Operation systems differ significantly in server roles, databases, and integrations, requiring a site-specific validation approach. Resolution Use the following structured approach to create and execute a site-specific performance validation procedure for EcoStruxure Building Operation systems. 1. Prepare Baseline (Before Changes) Capture current system performance to enable comparison. Record CPU usage (Enterprise Central / Enterprise Server) Record memory usage (Enterprise Central / Enterprise Server) Measure network latency between Enterprise Central / Enterprise Server and Automation Servers Capture system load indicators: Active alarms Trend logs Connected users Measure user experience: WebStation load times WorkStation login times Graphics load performance 2. Perform Immediate Post-Change Validation Confirm the system is operational after updates or changes. Confirm all servers are online Expected result: No offline or red cross states Verify licenses are valid Confirm all required services are running Validate communication between: Enterprise Central Enterprise Server Automation Servers 3. Inspect Logs and System Health Identify early warnings or failures. Review Windows Event Viewer Review EcoStruxure Building Operation logs Check for: Service failures Certificate issues Database warnings 4. Verify Core Functionality Ensure key features are operating correctly. Verify alarm generation and acknowledgment Confirm trend data is being recorded Validate graphics loading and bindings Test access via: WorkStation WebStation Mobile clients (if applicable) 5. Validate Performance Assess system responsiveness and resource usage. Validate WebStation responsiveness Expected result: Acceptable page load and navigation times Monitor CPU usage trends Monitor memory usage trends Check database performance Trend retrieval speed Alarm list loading Verify network latency Confirm communication stability Expected result: No intermittent offline or red cross states 6. Perform Soak Testing (24–72 Hours) Validate stability under normal operating conditions. Operate the system under typical load Monitor: CPU stability Memory trends Communication reliability Confirm no gradual performance degradation 7. Confirm Regression Checks Ensure no functional or performance regression. All servers remain online No communication drops WebStation operates reliably Trends and alarms function correctly Reports generate successfully 8. Define Rollback Plan Prepare recovery actions if issues are identified. Define rollback criteria: Persistent communication issues Sustained high resource usage Performance degradation Database latency issues Define rollback method: Restore from backup Revert to the virtual machine snapshot 9. Document and Sign Off Capture results and confirm validation completion. Record system version and Windows update details Document test results and identified issues Obtain stakeholder or customer sign-off Reference Materials Use relevant documentation to support the validation approach:   EcoStruxure Building Management Overview Architectural Guidelines  Backup and Restore Overview Information Technology System Planning Guide Hardening Guidelines Overview

Issue After configuring External Log Storage with an MS SQL or PostgreSQL database, event and alarm timestamps viewed directly in the database do not match the timestamps displayed in EcoStruxure Building Operation. The timestamps in the External Log Storage database appear offset by several hours compared to what is seen in WorkStation or WebStation.  Product Line EcoStruxure Building Operation Environment External Log Storage MS SQL Server database PostgreSQL/Timescale database Building Operation WorkStation and WebStation Cause All historical and event data in EcoStruxure Building Operation is stored in UTC. EBO clients automatically convert timestamps to the local time zone when displaying data. When querying the External Log Storage database directly, the raw UTC values are returned and no time-zone conversion is applied, resulting in an apparent timestamp offset. Resolution Apply the appropriate UTC-to-local time conversion within the SQL query or reporting layer when retrieving data from the External Log Storage database.   Examples: Note: Use your system’s applicable Windows time zone name Example 1: Using modern SQL Server (AT TIME ZONE): SELECT AlarmId, EventText, TimestampUTC, TimestampUTC AT TIME ZONE 'UTC' AT TIME ZONE 'West Asia Standard Time' AS LocalTimestamp FROM dbo.AlarmEvent;   Example 2: Using basic offset calculation: SELECT AlarmId, EventText, DATEADD(HOUR, 5, TimestampUTC) AS LocalTimestamp FROM dbo.AlarmEvent; Alternatively, calculate the system UTC offset dynamically and apply it in the query. Note: External Log Storage is intended for data storage only and is not a reporting solution. SQL-based reporting, transformations, and time-zone handling are the responsibility of the customer or integrator. For supported reporting within EcoStruxure Building Operation, use Notification Reports to generate scheduled or on-demand exports without requiring direct SQL queries.

Issue The humidity calibration offset field is greyed out or unavailable when attempting to calibrate a SpaceLogic sensor in the property sheet. Product Line EcoStruxure Building Operation Environment SpaceLogic sensors (SXWS series) SpaceLogic IP controllers (MP-X/RP-X) Building Operation versions prior to 2023 Cause Humidity calibration and offset functionality for SpaceLogic sensors is not supported in earlier versions of EcoStruxure Building Operation. The calibration offset property for relative humidity was introduced in EBO 2023(5.0) and is unavailable in older releases. Resolution Upgrade EcoStruxure Building Operation and associated SpaceLogic IP controller firmware to a supported version that includes humidity calibration functionality. Once upgraded to EBO 2023 or later (with compatible firmware), the humidity calibration offset property becomes available and can be adjusted as required.

Issue It is not clear how to replace an existing AS with a new AS-P Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (AS-P) First detected in version 1.7 Cause Detailed instructions on how to replace an existing AS with a new AS-P are needed Resolution WebHelp references SmartX Server Replacement Using Restore SmartX Server Replacement Using Restore Workflow Overview Main differences between an AS and an AS-P: In the AS-P, the RS-485 ports have been relocated to the top. The AS-P has 2 Ethernet ports; port 2 can be used as a switch only as of SBO version 1.81. AS-P device USB port format changed to mini USB. Operator Panel port has been removed. Hardware factory reset has been removed. AS-P uses pluggable connectors for field buses. (not shown in picture above) Consider the power consumption. AS-P requires 10 watts, while the Automation Server only required 7 watts. Preparations In preparation for replacing an Automation Server with an AS-P the following considerations must be made: Power consumption Since the AS-P consumes three more watts than the classic Automation Server, the power budget needs to be reviewed to check whether an additional power supply and/or rearrangement of the current configuration is needed, if the configuration includes IO modules. Terminal base The terminal base for the classic Automation Server can be used with the new AS-P after removal of the upper terminal block. Note though that all field buses wiring has to be moved to the pluggable connectors used with the AS-P. RS-485 field bus re-wiring Since the RS-485 ports and connectors have been relocated, the termination at the server of any field bus located on those ports will need re-wiring. Also, the physical specification of the RS-485 port is changed in the AS-P, so review whether the termination resistors needs to be replaced. Refer to Configuration Selection for Generic RS-485 Network Devices AS-P firmware Unlike the classic Automation Server, the AS-P ships from the factory with no firmware installed. Make sure to procure the appropriate Device Administrator firmware to install in the unit. First version that supports the AS-P is 1.7. Note once again that the USB port format in the AS-P is mini USB, so procure the appropriate USB cable. Backup file Make a backup of the classic AS to be replaced, the AS-P will restore from a classic AS backup but this is a one way process, the classic AS will not restore from an AS-P backup file. If the classic AS is running an older version of firmware, it will have to be upgraded first to at least 1.7.2. Power budget review Since the AS-P consumes 10 watts of power versus 7 watts for the classic Automation Server, it is necessary to review the power budget to ensure there is enough power for the AS-P, if the Automation Server being replaced is hosting IO modules. One power supply (PS-24V) can supply 30W. The following table shows power consumption for the different device types Device Power AS-P 10 AS 7 DO-FA-12-H 1.8 DO-FA-12 1.8 DO-FC-8-H 2.2 DO-FC-8 2.2 DI-16 1.6 RTD-DI-16 1.6 AC-4 11.1 UI-16 1.8 AC-2 5.5 AO-8-H 4.9 AO-8 4.9 AO-V-8-H 0.7 AO-V-8 0.7 UI-8-AO-4 3.2 UI-8-AO-4-H 3.2 UI-8-DO-FC-4 1.9 UI-8-DO-FC-4-H 1.9 UI-8/AO-V-4 1.0 UI-8/AO-V-4-H 1.0 In case one or more additional power supplies are needed, refer to the example given in last part of this article.   Note: The following "replacement procedure" applies to SBO 1.7.x, 1.8x, 1.9x, EBO 2.0x and 3.0.x and 3.1.x. The AS-P must be running the same version as the original AS backup. The AS was no longer supported from EBO 3.2.x. If the site needs to take the AS-P to EBO 3.2 or later, the following should be followed at the AS supported version, then once the AS backup has been restored to the AS-P, the AS-P can be upgraded further, following the supported upgrade path, which can be found in the release notes for the specific EBO version.   Replacement procedure The following procedure assumes the classic Automation Server is being replaced with a brand new AS-P from the factory If the Automation Server is hosting IO modules then perform the steps in the 'Power Budget' section below before going to the next step. Perform pre-maintenance procedure per site requirements, i.e. put equipment in hand control mode etc. Pull out the classic Automation Server from the terminal base. The hardware is designed for hot swapping so there is no need to power down the system. Remove the terminal block from the terminal base as indicated above. Insert the AS-P in the terminal base. Connect Device Administrator to AS-P via USB and install a new database on it. You may want to check the 'Set time on device' check box to initialize the time in the AS-P since its current time is most likely at default if this is a brand new unit or a unit that has been powered down for a while. Using Device Administrator set the communication parameters of the AS-P (IP address etc) to match the settings of the classic Automation Server being replaced. Connect Ethernet cable from network switch to Ethernet 1 port on the AS-P. If a hotfix was installed on the Automation Server that is replaced, apply any hotfix needed to match the version of the firmware in the AS-P to the version of the backup from the Automation Server. Since the AS-P should now be able to communicate over IP the application of any HF can be done either over USB or IP. Using WorkStation, log in directly into the AS-P and restore the backup from the classic AS. Insert pluggable connectors for field buses. If there is an Enterprise Server, log into Enterprise Server from WorkStation and verify the newly swapped AS-P is online. Verify IO modules (if any) are online. Verify field devices (if any) are online. Return the system to software control per site requirements. Verify the system is operating correctly then perform a backup of the AS-P. Power supply addition example Consider the following system If we do the math, the power consumption of this system is 29.8 watts. To avoid exceeding the capacity of the existing PS we need to add an additional PS to the configuration before we replace the Automation Server with an AS-P. In order to maximize the use of the capacity of the first PS we will add a new PS at slot #7 and move the UI8AO4 IO module from slot #7 to slot #8.   Steps Disconnect the UI8AO4 IO module making sure it powers down. It is necessary that any IO modules being relocated on the IO bus are powered down so that they 'forget' their current module IDs. *** Logon to the Automation Server, make sure UI8A04 shows offline then edit the module and change its Module ID from 7 to 8. Insert power supply at slot #7 Attach the UI8A04 after the new PS (slot #8), when it powers up it will obtain its new Module ID (8) from the Automation Server. Last, if the module’s name contains the ID (Slot07:UI8AO4) it may be a good idea to rename it using the new ID to avoid confusion. (Slot08:UI8AO4) *** It is absolutely necessary that all the modules that will change IDs be powered down, if there are multiple power supplies in the chain make sure to power down all power supplies that are supplying power to any modules that will change slot #. When removing or inserting IO modules or handling S-Cables, care should be taken not to bend or otherwise damage the pins that connect the module to its IO terminal base, any damage to the pins may cause the module address to shift.   Tip There is a tool on the community (SBO xbk Analyzer) that can be used to automatically calculate the power budget from a backup of the AS/AS-P. Here is the power budget report generated from the tool after addition of second power supply at slot #7 before replacing the classic AS with an AS-P. The total power consumption is 29.8 watts but we have increased the power capacity of the system to 60 watts with the addition of the second power supply.   The instructions above are available as a PDF: Replacing a classic AS with AS-P

Issue Importing applications from the Schneider Electric BMS Applications portal into controllers fails with errors such as: “The import file contain only library meta data and types.” “Parent cannot contain objects of this type” Product Line EcoStruxure Building Operation Environment Building Operation WorkStation MP‑X or RP-X controller Standard Application downloaded from Schneider Electric BMS Applications portal Cause Scenario 1 (MP‑X / RP‑X – StdApp example) Files such as StdApp‑385, downloaded from the BMS Applications portal, are Custom Types, not Standard Application import files. This can be verified when viewing the Schneider - BMS Applications download of the Application, and it will indicate   A custom type import for ...... Custom Types must be added to the Custom Type Library, not imported into the system tree Scenario 2 (RP controller import attempt) Applications from the BMS Applications portal for RP controllers are also Custom Types These cannot be directly imported into the RP controller Attempting direct import results in object type mismatch error Resolution For Custom Type import errors (“library metadata and types”) Launch WorkStation with Engineering Workspace enabled (supports Custom Types) Navigate to the Type Library Pane Use Import Custom Type workflow Import the file into the Custom Type Library Apply the Custom Type to the controller after import For RP controller import errors (“Parent cannot contain objects of this type”) Do not attempt to directly import application files into the RP controller Recognize that the files from the BMS Applications portal are Custom Types Follow the proper Custom Type import workflow (as above)

Issue Unable to apply a Consolidation Point (CP) or Hotfix (HF) on an Automation Server Update process fails during execution How to identify the Automation Server ID node count Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server (AS-P/AS-B) Cause The Automation Server is not installed in the correct physical slot on the backplane The Power Supply or Base(s) is faulty Device PINs are misoriented (bent) or not seated correctly.  The requirement is stated in the WebHelp topic Automatic Device Addressing on the I/O Bus Position 1 is reserved for a power supply. Position 2 is reserved for an automation server. Resolution When the update process fails, collect the DebugInformation from the Automation Server Open the System.log file Locate and identify the reported node ID Verify the node ID: The Automation Server must have node ID = 2 If the node ID is not 2: This confirms the Automation Server is installed in the wrong physical position or one of the other items mentioned in the Cause above Example of an incorrect node ID Physically correct the installation: Ensure the power supply is in Position 1 Ensure the Automation Server is in Position 2 After correcting the hardware position, retry the update Relevant Resource:   Multiple Automation Servers on the same backplane

Issue During an upgrade preview for an ES, warnings appear in the conversion log, including: Invalid Data Error: The_Object_Property_Does_Not_Exist (0x1002c) in module Impex(57) Data Access Error: Object_Does_Not_Exist (0x40004) in module Impex(57) Disregarding property 'Status' - not defined in owning object The user wants to know what these warnings mean and whether it is safe to proceed with the upgrade. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The warnings are generated because some objects are bound to items that no longer exist or reference properties that are no longer valid. Additionally, a meter object in version 6.x is converted to a consumption monitor object in version 7.1, which does not include a "Status" property, resulting in that property being discarded during the upgrade. Resolution These messages are warnings only and are considered expected behavior during the upgrade process. It is safe to proceed with the upgrade. The system will automatically discard invalid or unsupported properties without impacting the upgrade outcome.

Issue Script Editor shows a blank canvas Script Editor closes immediately after launch Script Editor: Appears in the taskbar but no window is visible Opens but is not visible on screen Error message may briefly appear and disappear Error message may display: “Building Operation Script Editor can not be launched standalone” Issue occurs while: Editing a Script program Other editors (for example Function Block or Graphics) may work correctly Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Script editor Cause 1) Corrupt or incompatible user settings file User.settings contains entries that Script Editor cannot process correctly May contain malformed or excessive configuration data 2) Script Editor window positioned off-screen Window position stored from a previous multi-monitor setup Secondary display is no longer available Position values (Left / Top) place window outside visible area 3) Misleading standalone launch condition Script Editor is not designed to run as a standalone application Error message may appear even when underlying issue is related to settings Resolution Follow the steps below in order: A) Validate correct usage context Ensure Script Editor is launched from within Building Operation Workstation Do not attempt to run Script Editor as a standalone application If the error “Script Editor can not be launched standalone” appears, confirm it is not being launched independently B) Check for off-screen window (multi-monitor scenario) Determine if a secondary monitor was previously used If available: Reconnect the secondary monitor Move the Script Editor window back to the primary display C) Correct window position in settings file If a second monitor is not available: Open User.settings : %appdata%\Schneider Electric (StruxureWare or EcoStruxure)\Script Editor\<version> Modify: Left = 0 Top = 0 Save and relaunch Script Editor D) Reset the user settings file If the issue persists: Navigate to the Script Editor settings directory Backup: User.settings Delete or rename the file Relaunch Script Editor A new file will be created Note: This removes all user-specific configuration E) Advanced troubleshooting (optional) Restore the original User.settings file Open in a text editor Comment out suspected entries: <!-- --> Test iteratively to isolate problematic configuration

Issue User is unable to remove existing registration details (such as Building or Company name) in WorkStation (Enterprise Central / Server). The fields can be edited but not cleared. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation WorkStation Cause Registration details are linked to the system ID and cannot be removed independently. Resolution Reset the System ID to clear the registration details:     After resetting the System ID, close the WorkStation and reopen it. The registration details will be cleared.

Issue When attempting to register a System ID in EcoStruxure Building Operation (EBO), the user is redirected to a registration web page. The page fails to load and displays a “502 Bad Gateway” error, preventing completion of the System ID registration. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Versions below 2.0 Cause Older EBO versions use a legacy registration URL that has since been retired. Accessing this retired page now results in a “502 Bad Gateway” error, preventing the registration process from completing. Resolution Use the current EBO registration portal to register the System ID: https://registration.smartstruxure.schneider-electric.com/ebo/Home Alternatively: Upgrade the system to a supported EBO version (2.0 or later) Then, perform the System Registration using the updated system

Issue After a power outage, SpaceLogic controllers report an incorrect model type (for example, an MP-V-7A appearing as an MP-C-15A). Controllers display hosting errors, IO objects are missing terminal assignments, and downloads fail (e.g., during flow balance log download). Removing and re-adding the controller does not resolve the issue. Product Line EcoStruxure Building Operation Environment SpaceLogic MP-V Cause After an upgrade, the CPU board may instruct the main board to restart, after which the main board stops responding to commands. When the CPU board comes back online, it is unable to retrieve the model number from the main board and incorrectly identifies the controller model. Resolution First, power cycle the controllers manually. Then perform a BACnet device discovery with a refresh to update the controller information. Once the correct model numbers are displayed, execute a Download All Objects to the controllers. This restores the correct controller model type and terminal assignments, and the download process completes successfully.

Issue Object symbols and System Tree icons for programs, devices, and other items appear blank in WorkStation after clearing temporary memory or application data. Reinstalling WorkStation alone does not restore the icons. System tree with Icons missing Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Windows OS user profile (AppData) Cause WorkStation cache and application data located in the Windows AppData directory were manually cleared, which removed required files. All installed WorkStation versions share the same cache, so partial uninstall or improper cleanup can result in missing icons and inconsistent behaviour. Resolution Uninstall all installed versions of EcoStruxure Building Operation WorkStation, then fully clear the WorkStation cache before reinstalling: Close WorkStation Uninstall all installed versions of WorkStation Navigate to: %AppData%\Schneider Electric EcoStruxure\Building Operation\ Delete the WorkStation folder Reinstall the required WorkStation version(s) All WorkStation versions share the same cache, so removing all versions and clearing the cache is required to resolve the issue. After completing these steps, the object symbols and System Tree icons are restored and WorkStation functions normally.

Issue When upgrading a site from EcoStruxure Building Operation (EBO) 6 to EBO 7, questions arise about whether SpaceLogic Advanced Display v3 (ADv3) units also need to be updated, what versions are required, and how to verify the installed version on the display. Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause Compatibility with EBO 7.0 depends on the browser applications installed on the Advanced Display v3. Earlier ADv3 units do not include the required browser APK versions needed to work correctly with EBO 7.0. Resolution SpaceLogic Advanced Display v3 compatibility with EBO 7.0 depends on the display hardware revision: ADv3 Refresh (SKU: SXWADBUND10013) Released in October 2024, this revision is shipped with updated browser APK files and works with EBO 7.0 without any additional updates. Sites using ADv3 Refresh can upgrade from earlier EBO versions to EBO 7.0 without display-related issues. Original ADv3 (SKU: SXWADBUND10003) Existing sites using the original ADv3 must upgrade the browser APK files on each display individually to ensure compatibility with EBO 7.0. Updating the ADv3 browser APK files requires direct connectivity to each display. Contact product support for guidance and access to the required APK files. Minimum required versions for ADv3 to work with EBO 7.0: Webviewer: 119.0.6045.194 Kiosk: 8.0.15 In most scenarios, using Kiosk mode or WebViewer provides sufficient compatibility with EBO 7.x. However, if the Advanced Display v3 is operating on an older Android version and issues persist, upgrading the Android OS becomes the next recommended step to address web rendering and performance limitations To find the version of the SmartX HMI Kiosk and Webviewer refer to the attached video.

Issue Customer query regarding whether the EcoStruxure Building Operation (EBO) application server automatically reconnects to the SQL Server after database server maintenance or patching, or if a manual restart of the Enterprise Server is required to restore the connection. Product Line EcoStruxure Building Operation Environment Microsoft Windows Server 2022 Microsoft SQL Server 2022 Two-server architecture: Server 1: EBO Enterprise Server (BMS application) Server 2: Microsoft SQL Server used for external log storage/reporting Scenario involves scheduled SQL Server maintenance or upgrade causing temporary database unavailability. Cause Customer uncertainty due to common application behavior where database connections are only established at startup, requiring application restart after database downtime. Concern about maintaining BMS availability and avoiding unnecessary restarts during SQL Server maintenance windows. Resolution System Behaviour The Enterprise Server automatically attempts to reconnect to Microsoft SQL Server at approximately 10-second intervals when the database is unavailable. No manual restart of the Enterprise Server is required after SQL Server maintenance or upgrade. External log storage resumes automatically once SQL Server becomes available, including transfer of data stored locally. Operational Impact Temporary system alarms related to SQL connectivity may occur during the maintenance period. These alarms can be acknowledged after SQL Server connectivity is restored. Data Handling Considerations Any gaps in logged data depend on: Duration of SQL Server downtime Configuration of local sample storage Trend log and extended trend log sizing Local storage buffers data during SQL unavailability and forwards it when connectivity is restored. Optional Actions (Not Required) Disabling and re-enabling external trend logging is not required for SQL Server upgrades. This action may be used optionally to reduce system alarms during maintenance but does not affect reconnection behaviour. Design Recommendation Trend Log and Extended Trend Log sizes should be configured to ensure sufficient local storage during expected downtime, within system architectural limits. Key Takeaway EBO Enterprise Server maintains resilience during SQL Server outages by automatically reconnecting and buffering data locally, eliminating the need for manual restart after database maintenance.

Issue Google Maps does not display in WebStation. Behavior observed after upgrading to EBO 7.1: No map rendered in version 7.1. Map renders with errors in version 7.0. Map works in version 6.0. In some cases, WebStation shows script errors and embedded content fails to load. Product Line EcoStruxure Building Operation (EBO) Environment EBO version 7.1.1.x WebStation (browser-based access) Enterprise Server (ES), including hosted environments Embedded Google Maps within TGML graphics or overview images Cause This behavior is expected and by design. Google services (including Google Maps) enforce security restrictions that prevent embedding via iframe using the header: x-frame-options: DENY In addition, EBO version 7.x introduced enhanced cybersecurity measures that enforce stricter browser security policies, which block such embedded content. Resolution There is no fix available within EBO to restore this functionality. Google Maps embedding in WebStation is not supported in EBO 7.x due to external provider restrictions and platform security enhancements. see Google Sites restriction As a result: Existing Google Maps integrations cannot be made to function in WebStation in EBO 7.1. This limitation is not resolved through configuration changes or patches in EBO.

  Issue After restoring or migrating an Enterprise Server (ES) or Enterprise Central (EC) to a different PC, the system exhibits abnormal behavior including: License violations reported on the top server All license values showing as zero on child Enterprise Servers Child servers not retrieving licensing data from the top server Binding transfers failing from child server to top server Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES)  Building Operation Enterprise Central (EC)  Cause When an ES or EC is restored or migrated to a different PC, the Server ID is automatically reset as part of anti-cloning protection. However, the System Identifier is not updated during this process, resulting in a mismatch between identifiers. This inconsistency prevents proper communication and licensing synchronization between servers. Resolution Contact Product Support to verify whether a Server ID and System Identifier mismatch is the root cause. Support can assist in validating the system state and applying the appropriate corrective actions.  

Issue After upgrading an EcoStruxure Building Operation (EBO) site to 4.0.3 or later, email notifications fail when TLS encryption is used for SMTP. Enterprise Server (ES) or Automation Server (AS‑P) logs may show errors such as: SSL routines: tls_process_server_certificate: certificate verify failed. Email service failed to connect to SMTP Server. In EBO 6.0.3: error:16000069:STORE routines::unregistered scheme Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 4.0.1 and later Building Operation Automation Server (AS-P, AS-B) version 4.0.1 and later SMTP email notifications using TLS encryption Cause Beginning with EBO 4.0.1, TLS SMTP connections require full certificate chain validation. This means EBO must trust the Certificate Authority (CA) that issued the SMTP server’s TLS certificate. If the issuing CA certificate (or intermediate CA) is not installed in the ES/AS‑P, the TLS handshake fails and email cannot be sent. This affects: Public SMTP services (Microsoft 365, Gmail, etc.) Internal SMTP servers (Exchange, Postfix, etc.) Resolution Install the CA certificate that signed the SMTP server’s TLS certificate. Step 1: Retrieve the CA certificate from the SMTP server Use OpenSSL, which supports STARTTLS and bypasses browser port restrictions. Run the following command, replacing the server name as needed: Microsoft 365 openssl s_client -connect smtp.office365.com:587 -starttls smtp -showcerts Gmail / Google Workspace openssl s_client -connect smtp.gmail.com:587 -starttls smtp -showcerts Internal SMTP server openssl s_client -connect <smtp_server_fqdn>:587 -starttls smtp -showcerts This displays: The server certificate One or more intermediate CA certificates Sometimes the root CA certificate Step 2: Extract the required CA certificate(s) From the OpenSSL output, locate the certificate blocks: -----BEGIN CERTIFICATE----- (encoded data) -----END CERTIFICATE----- Copy the intermediate CA and/or root CA blocks into separate files: intermediate.cer root.cer Save them in Base‑64 (.cer) format. The certificate EBO needs is the CA that issued the SMTP server’s certificate. This is normally the intermediate CA. Step 3: Convert CER files to PEM You must convert any CRT or CER files to PEM. EBO only supports PEM format. Open SSL using the Command Prompt. Type "openssl x509 -in certFileName.cer -outform PEM -out convertedCertFileName.pem" Step 4: Import the CA certificate into EBO For TLS communication to succeed, the SMTP server’s Certificate Authority (CA) must be trusted by the hosting device initiating the email connection. Depending on where the email is sent from: Enterprise Server (ES): Import the CA certificate into the Windows Trusted Root Certification Authorities store on the ES host machine. Automation Server (AS): Import the CA certificate using Device Administrator: Security → Certificates → Trusted Certificates Failure to install the CA certificate in the correct location will result in TLS handshake failures and prevent email from being sent. Step 5: Test the SMTP connection Trigger an email alarm or use a test email to confirm successful TLS communication.