Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

Issue Is it possible to see how many simultaneous users are logged in via for example Webstation, Workstation and iPad to an ES? Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause This information is not saved in any file or any object in the ES. Resolution Within the Enterprise Server this is not possible. An enhancement has been written for this function to be implemented in the future. However, it can be achieved by using the FlexNet Licensce Administrator, see Number-of-client-licenses-used Knowledge Base article.

Issue The technical documentation for the RP-C-EXT-DALI-M-PD states a guaranteed DALI current limitation of 64 mA. It is unclear whether this limitation applies per DALI port or to the controller as a whole. Product Line EcoStruxure Building Operation. Environment RP-C-EXT-DALI-M-PD. Cause The product documentation lists two current values: 250 mA: Theoretical DALI standard maximum bus current. 64 mA: Guaranteed current output of the RP-C-EXT-DALI-M-PD module. This discrepancy has led to confusion regarding whether the 64 mA applies to each port individually or to the total output across all ports. Resolution The RP-C-EXT-DALI-M-PD module provides a total guaranteed DALI current of 64 mA, which is shared across all four DALI ports. Key points: If only one port is used, it may utilize the entire 64 mA. If multiple ports are used, the combined current draw must remain within the 64 mA limit. This limitation is enforced by hardware and cannot be exceeded, even with external devices. Use of external DALI repeaters with integrated power supplies (e.g., Helvar 405) is not supported due to certification constraints and potential conflicts with the module’s internal power supply. The 250 mA figure refers to the DALI standard, not the module’s actual output capability. As illustrated in the attached diagram, all four DALI ports are powered by a single internal DALI driver, which is the source of the 64 mA limitation.    

Issue Users encounter the following error when launching Device Administrator: “The following error(s) occurred while reading the server list file: - The site-specific server password could not be loaded. It will be set to the default password ‘admin’. - One or more SSH public keys are invalid.” Additionally, devices may show: - “SSH public key fingerprint changed!” - “Wrong logon” errors for connected Servers  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Device Administrator Access Method: Remote Desktop Multiple Windows user accounts or sessions Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This issue is caused by shared use of a single server list file across multiple Windows user accounts or sessions. When another user opens Device Administrator—even without modifying or saving the server list—the SSH keys become invalid due to security hardening measures. This behavior is by design to prevent unauthorized access and is part of Schneider Electric’s cybersecurity strategy. Resolution Recommended Workflow  Create and Save the server list on the original user account or PC. Export the server list using the built-in export feature in Device Administrator. Import the server list on the target user account or PC. ⚠️ Do not copy the XML file manually between users or systems. This will invalidate SSH keys and passwords due to security restrictions. Best Practices Use unique filenames when exporting server lists (e.g., include user initials). Avoid using shared server list files across users or sessions. If the server list becomes corrupted or invalid: Re-import the previously exported working server list. If unavailable, recreate the list and export it immediately for future use. Additional Notes This issue can occur even if only one user accesses the system, especially if the server is accessed via Remote Desktop and multiple sessions are involved. The server list file ( Servers.xml ) should always be managed through the export/import functionality to preserve encryption and key integrity. Affected devices may require re-authentication or re-adding if the server list is corrupted and cannot be recovered. References Import and Export a List of Field Server Workflow

Issue Where can I find documentation and network architecture diagrams for the Building Analytics service? Product Line EcoStruxure Building Analytics Environment Building Analytics Cause Users require access to product documentation and network architecture information to support: Deployment Configuration Troubleshooting Resolution Documentation and diagrams for Building Analytics are available through the following resources: 📂 Schneider Electric Download Center Access product manuals, guides, and technical documentation. Visit the Download Center 🗺️ Network Architecture Diagrams A diagram illustrating typical Building Analytics network architectures is available: Building Analytics Network Architecture PDF

Issue Users are unable to change the value of a Sigma object using the standard Trackbar component in a Building Operation (SBO) graphic. Product Line Satchwell BAS & Sigma Environment Ecostruxure Building Operation (EBO) Sigma transitioned graphics Cause Sigma objects are inherently non-writable. Unlike typical objects in EBO, Sigma objects require a manual override (also known as a “force”) to change their values. The default Trackbar component in EBO does not support this behavior, as it attempts to write directly to the object’s value, which is not permitted for Sigma objects. Resolution To enable value changes for Sigma objects via a graphic, the standard Trackbar component  Trackbar component must be modified to include a call to the setForce function. This mimics the behavior of legacy Sigma graphics, where moving a slider would automatically override the object. Steps to Modify the Trackbar Component: Open the existing Trackbar component in the graphic editor. Locate the setCurrentValue function. Modify the function to include the setForce call before setting the value: setForce(fullName, true); return setValue(fullName, value);​   Ensure the modified Trackbar is bound to the “Value” property of the Sigma object, just as it would be in legacy Sigma. Important: Do not bind the Trackbar to configuration values such as “Fixed value” or “Alarm High Limit,” as these cannot be changed via graphics in transitioned Sigma systems. Limitations: Only specific values can be overridden in transitioned Sigma systems. Configuration parameters like “Alarm High Limit” or “Fixed value” cannot be modified through graphics. Additional Resources: Modified Trackbar Component

Issue An end user has requested guidance for their IT department on how to secure a Building Automation System (BAS) effectively. Product Line Andover Continuum, EcoStruxure Building Activate, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Building Automation Systems (BAS) IT/OT Network Infrastructure Cybersecurity Best Practices Cause With the increasing convergence of IT and OT systems, securing Building Automation Systems has become critical. Customers are seeking best practices to ensure their systems are protected from cybersecurity threats and vulnerabilities. Resolution To assist with securing your Building Automation System, Schneider Electric provides a comprehensive white paper authored by the Buildings BU IT Security Group. 📄 Download the white paper here: Best Practices for Securing an IBMS (PDF) This document outlines: Key cybersecurity principles for Building Automation Systems Network segmentation and access control strategies Secure configuration and hardening guidelines Monitoring and incident response recommendations Compliance with industry standards (e.g., IEC 62443, ISO/IEC 27001) 🔍 Additional Resources Schneider Electric Cybersecurity Solutions Scheider Electric Cybersecurity Support Portal IT System Planning Guide - EcoStruxure Building Management EcoStruxure Building Operation Webhelp

Issue The HVAC Optimization module in the Building Advisor (BA) portal is currently displaying data that is two months behind the current date. Snapshot: The image below illustrates the data available within the HVAC Optimization module as of October. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Advisor HVAC Optimization Module Cause This does not represent a defect in data collection or in the functionality of the Building Advisor Portal Resolution The limited data display is intentional and aligns with the system’s design principles. Energy providers often apply retroactive adjustments to consumption records, and interim placeholder values can be unreliable. By excluding these, the system ensures data integrity and accuracy. Additional Notes: This behavior is expected and documented. No action is required unless data is missing beyond the expected two-month delay.

Issue A streamlined and automated method is needed to move Enterprise Server (ES) backup files when the program is installed on the D:- drive and program data is stored on the C:- drive. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause   There may be operational or storage-related reasons to move or archive backup files. Installing the program on the D:- drive while retaining data on the C:- drive offers several benefits. Benefits of Separating Installation and Data Drives ✅ Storage Optimization The D:- drive often has more available space, allowing larger installations without impacting system drive capacity. ✅ Performance Improvement Separating installations from data can improve performance, especially if the D:- drive is a faster SSD. ✅ Simplified Backup and Recovery Storing data on the C:- drive simplifies backup and restore processes, avoiding the need to include the entire program installation. ✅ Improved File Organization This separation leads to a more structured file system, making application and data management easier. Resolution It is recommended to initially save backups in the default ProgramData folder on the C: drive and then move them to the D:- drive using a scheduled PowerShell script. PowerShell Script Example # Set variables $Now = Get-Date $Days = 5 $TargetFolder = "C:\\ProgramData\\Schneider Electric EcoStruxure\\Building Operation X.x\\Enterprise Server\\db_backup\\LocalBackup" $Extension = "*.xbk" # Backup file extension $LastWrite = $Now.AddDays(-$Days) $BackupLocation = "D:\\BackupArchive" # Destination folder for old backups # Ensure destination folder exists if (!(Test-Path -Path $BackupLocation)) { New-Item -ItemType Directory -Path $BackupLocation | Out-Null } # Move files older than $Days to the backup location Get-ChildItem -Path $TargetFolder -Filter $Extension -Recurse | Where-Object { $_.LastWriteTime -le $LastWrite } | Move-Item -Destination $BackupLocation -Force 💡 Tip: You can enhance this script with features like file compression, logging, or automatic cleanup of obsolete backups. Automation Recommendation Use Windows Task Scheduler to automate the script execution. 📘 How to schedule PowerShell scripts

Issue Integration between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO) fails due to default security settings that prevent embedding external web content. Product Line EcoStruxure Building Operation Environment Building Operation WebStation PME Web Applications Cause By default: PME restricts other applications from embedding its web content. EBO blocks external web content from being embedded in its UI. To enable integration, both systems must be configured to allow embedded content. Resolution  ✅ Enable External Content in EBO WebStation Log into Building Operation Workstation. Navigate to: Tools > Control Panel > Security and Communication > Security Settings Under WebStation, check the box: ✔ Enable external content to be embedded in WebStation  ✅ Authorize EBO to Embed PME Web Applications Open PME Web Applications. Go to: SETTINGS > Security > Authorized Hosts Add the Building Operation server URL to the Hosts That Can Frame list. Example: https://localhost:446 Click Save. Reset IIS (Internet Information Services) on the PME server to apply changes. Notes Ensure both systems are updated to compatible versions. Use secure URLs (HTTPS) when configuring host permissions. Resetting IIS may cause temporary downtime—schedule accordingly.

Issue Need to verify whether specific network ports are open, as certain ports may be blocked. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspected network port blockage affecting communication between devices or applications. Resolution You can check if a port is open using the Telnet command in Command Prompt. ⚠️ Note: Telnet uses the TCP protocol only. It cannot be used to test UDP connectivity. 📌 Command Syntax: telnet [domainname or IP] [port] [domainname or IP] – The server's domain name or IP address. [port] – The port number the server application is listening on. 🧪 Examples: telnet 192.168.0.20 9001 → Closed port: Displays a "connect failed" message.   telnet 192.168.0.20 9003 → Open port: Displays a blank screen.   🚪 To Exit Telnet Session: Press Ctrl + ] Type quit and press Enter. 📝 Note: Telnet may be disabled by default on some machines. Refer to Microsoft's documentation for instructions on enabling Telnet.

Issue A malfunction in Power Monitoring Expert (PME) may occur due to the installation of a 32-bit version of SQL Server. Product Line EcoStruxure Building Operation Environment Power Monitoring Expert Cause The issue may stem from using a 32-bit SQL Server, which is incompatible or suboptimal for PME. Resolution You can determine the SQL Server architecture using either of the following methods: Method 1: Using SERVERPROPERTY Open SQL Server Management Studio (SSMS) and connect to the target SQL Server instance. Click New Query. Ensure the master database is selected. Run the following query: SELECT CASE WHEN CHARINDEX('64', CAST(SERVERPROPERTY('Edition') AS VARCHAR(100))) > 0 THEN 64 ELSE 32 END AS [SQL Server Bit Version]; Click Execute. 🔍 Result: The query returns either 32 or 64 , indicating the bit version of the SQL Server instance. Method 2: Using @@VERSION Alternatively, run the following query: SELECT @@VERSION; 🔍 Example Output: Microsoft SQL Server 2008 R2 (SP1) - 10.50.2550.0 (X64) Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) Look for (X64) or (32-bit) in the output to determine the architecture.

Issue Unable to connect Enterprise Server or Enterprise Central to the Building Advisor Cloud Portal  Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment Building Operation Building Advisor EBO Health Module Building Operation Enterprise Server Building Operation Enterprise Central Cause There are specific Operating System (OS) requirements that must be met to ensure successful connectivity to the Azure-based Building Advisor Cloud services. Incompatible OS or software versions may result in missing trust certificates, preventing proper communication. Resolution To ensure reliable cloud connectivity, verify that your system meets the following OS and software compatibility requirements: Enterprise Server Software Compatibility Matrix EBO Version Windows 10 (64-bit) Windows 11 Server 2012 R2 Server 2016 Server 2019 Server 2022 Server 2025 v3.2.4 Yes   Yes Yes Yes     v4.0 Yes v4.0.2 Yes Yes Yes Yes   v5.0 Yes Yes Yes Yes Yes Yes   v6.0 Yes Yes Yes Yes Yes Yes   v7.0 v7.0.2 Yes   Yes Yes Yes Yes Note: Always verify the official Microsoft support status for your OS version to ensure ongoing compatibility and security. Additional Requirements Microsoft .NET Framework: Required: .NET Framework 4.7.2 or later Note: Versions 4.5 or 4.6 are not supported for cloud connectivity. TLS 1.2 Support: SmartX servers require TLS 1.2 to be enabled for secure communication with the Building Advisor Cloud. Automation Servers (AS-P/AS-B) have TLS 1.2 enabled by default. For Enterprise Servers running on Windows OS, ensure TLS 1.2 is enabled. Refer to: How to Check if TLS1.2 is Enabled Summary To maintain a stable and secure connection between EBO and the Building Advisor Cloud Portal: Ensure your EBO version is compatible with your Windows OS. Use .NET Framework 4.7.2 or later. Confirm TLS 1.2 is enabled on your system. Always consult Microsoft's official documentation for the latest OS support updates.

Issue Access to the correct version of Device Administrator or WorkStation is unavailable, and a backup of the Automation Server is required. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause In certain scenarios—such as on-site troubleshooting or version incompatibility—the appropriate tools (Device Administrator or WorkStation) may not be accessible. In such cases, an alternative method is needed to perform a backup.   Note: In EBO 2022 (4.0.3) and later, backups can be performed and downloaded using WebStation Resolution Follow these steps to perform a backup using WinSCP, a secure file transfer tool compatible with all system versions. WinSCP is compatible with all versions of EcoStruxure Building Operation. It requires communication over port 22 (SSH). Download WinSCP Launch WinSCP Open the application after installation. Log In Use the Admin username and password. Select SCP as the protocol.   Navigate to the Backup Folder Browse to the folder containing the server backup files. Refer to the image provided below for the folder location. Download the backup files to your local machine. Additional Notes Ensure SSH access is enabled on the Automation Server. If login fails, verify credentials and network connectivity. This method is suitable for quick, manual backups when standard tools are unavailable.  

Issue How to check installed Power Monitoring Expert (PME) and Cumulative Update (CU ) versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Power Monitoring Expert Cause When troubleshooting integration issues between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO), it's important to identify the installed PME version and its corresponding Cumulative Update (CU). Knowing the exact PME and CU versions helps ensure compatibility and can assist in diagnosing integration problems between PME and EBO. Resolution To check the installed PME and CU versions: Open the Windows search bar and type regedit . Press Enter to launch the Registry Editor. Navigate to the following registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Schneider Electric\Power Monitoring Expert\X.X\CumulativeUpdate Review the values listed under this path. These entries will indicate: The installed PME version The Cumulative Update (CU) version, if applicable

Issue The Bluetooth adapter fails to power on when connected to the SmartX Sensor. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause The “Commissioning Tool Enable” property is set to Off, which prevents the Bluetooth adapter from receiving power. Resolution To resolve this issue: Open WorkStation. Navigate to the Sensor Bus Settings. Locate the “Commissioning Tool Enable” property. Set the property to On. Save the changes and verify that the Bluetooth adapter powers on.    

Issue Will client licenses from previous EBO versions activated prior to EBO 7.0 in License Administrator still be applicable after upgrading? Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause With the release of EBO 7.0, Schneider Electric introduced tier-based licensing. This change affects how previously purchased client licenses are recognized. Customers upgrading to EBO 7.0 and selecting the Essential Tier (which includes 3 concurrent client licenses) may be unsure how their existing licenses are counted. Examples of License Questions SXWSWCLIENT0999 in License Administrator, selected Essential Tier → Do they have 3 or unlimited client seats? SXWSWCLIENT0001 in License Administrator, selected Essential Tier → Do they have 3 or 4 client seats? SXWSWWORK00002 in License Administrator, no editor programs running, selected Essential Tier → Do they have 3 or 4 client seats? Resolution When upgrading to EBO 7.0, it's important to understand how client licenses are handled. Unlike previous versions, EBO 7.0 does not recognize client licenses purchased in earlier releases. Instead, license availability is determined by the selected tier during the upgrade. Client licenses from previous EBO versions are not automatically recognized in EBO 7.0. License availability is determined solely by the selected tier during the upgrade. The Essential Tier provides 3 concurrent client licenses. If unlimited concurrent client access is required, customers must upgrade to the Advanced or Advanced Plus Tier. The Workstation Pro license is separate and does not add to the 3 concurrent client licenses included in the Essential Tier.   🔹 Recommendation: Choose a tier that aligns with your concurrent client needs and any additional feature requirements.

Issue The Vendor daemon fails to start on the License Server. Product Line EcoStruxure Building Operation Environment Ecostruxure Building Operation License Server Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause The issue occurs due to special characters (e.g., ô, ã, non-breaking space) in the Computer Name of the operating system hosting the License Server. - see screen shot below. This can be observed in the FlexNet Publisher management page (localhost:8888). The taclic.log file may contain entries such as: 10:11:55 (taclic) Server started on Test-aã for: B 10:11:55 (taclic) client.station client.station graphdb.base 10:11:55 (taclic) server.cloud.customer server.enterprise.base server.es.as 10:12:08 (taclic) EXTERNAL FILTERS are OFF 10:12:11 (taclic) Unknown Hostname: Test-aã​ Resolution To resolve the issue: Edit the Computer Name of the host machine. Remove any special characters (e.g., accented letters, non-breaking spaces). Restart the License Server after making the changes.

Issue The LCES firmware for MP is universal, covers all models. The LCES firmware learns its model from the STM32 (the IO processor). If the LCES FW is unable to get an answer to the question, "what model am I", it defaults to MPC15A. When we see this, the reason is usually due to missing/corrupt STM32 firmware caused by a power fail during an uprev of the STM32 Product Line EcoStruxure Building Operation Environment Multi-purpose Controller Multi-purpose VAV Multi-purpose IO Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause STM32 flash corruption is caused by interruptions during firmware activation, such as: Power cycling the controller before activation completes. Network disruptions during upgrade. Premature assumption that upgrade is complete based on “100%” progress bar. Resolution To recover, try the following: Manually factory reset the MP controller (Press and hold the reset button between 20-29 seconds) Upgrade the MP controller to a revision close but NOT the same as the current firmware version. When the firmware upgrade is complete, reset the controller or power cycle the MP controller. Collect the device report again and check if the model has been updated to the correct one. If the model is correct, upgrade to the original or desired firmware version. If the model is incorrect, attempt another upgrade with a different version , aside from the initial firmware, from Step #2. You may need to repeat the firmware upgrade two more times if unsuccessful.