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.

Issue Users expect the Repair function in EcoStruxure Building Operation (EBO) to automatically detect, identify, or fix missing or replaced DALI lights. However: The replaced light is not detected The Repair process fails The wrong device may be addressed No action occurs despite running Repair Product Line EcoStruxure Building Operation Environment Dali Expansion Module Cause The misunderstanding comes from assuming that Repair is a discovery or automatic fixing tool. In reality: Repair is a controlled addressing process, not auto-discovery It only works under strict conditions It does not scan or identify multiple devices It cannot overwrite existing addresses Typical incorrect expectations include: Repair finds and fixes any faulty lamp Repair works with multiple new devices connected Repair can reuse or overwrite occupied addresses Resolution To successfully use the Repair function, all prerequisites must be met: 1. Replacement device must be unaddressed The new DALI ballast or driver must have no short address Devices with an existing address are ignored or cause failure Use factory default or reset devices ✔ Correct use: Repair assigns the address ✖ Common mistake: Attempting to repair an already addressed device 2. Only one unaddressed device on the DALI bus Exactly one unaddressed light must be connected Multiple unaddressed devices create ambiguity Possible outcomes if multiple devices exist: Repair fails Wrong device receives the address ✔ Best practice: Disconnect or isolate all other new devices 3. At least one free DALI short address available Valid address range: 0 to 31 Repair requires one unused address If all addresses are in use: Repair cannot proceed No reassignment occurs ✔ Best practice: Free an address before running Repair ✖ Common mistake: Expecting automatic overwrite Summary When used correctly, Repair is a precise and reliable method to reassign a DALI short address to a single replacement device. Ensuring: One unaddressed device No pre-existing address At least one free address will result in consistent and predictable behavior.

Issue Bindings between: Enterprise Server and Automation Server, or Two Automation Servers ...appear as "Unresolved" in the system. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Binding Diagnostics Cause This issue is typically caused by: Incorrect communication configuration Firewall or antivirus blocking communication Port conflicts or usage by other applications Network adapter misconfiguration Unsupported architecture (e.g., EC and ES on the same PC) Resolution 🔒 1. Firewall Configuration Ensure Windows Firewall is correctly configured: Use the Firewall Config Tool to set inbound/outbound rules. Refer to: Creating Windows Firewall Rules for Building Operation. If unsure, temporarily disable the firewall to test connectivity. Watch for network profile switching (Private ↔ Public) during commissioning. ⚠️ Even if ASs appear online, unresolved bindings may still occur due to firewall issues. 🧩 2. Special Character in Server Name For v1.4 or v1.5 servers with an ampersand (&) in the name: Request hotfix: v1.4: R1.4.1.16201 or later v1.5: R1.5.0.1601 or later 🌐 3. Network & IP Configuration Confirm ES IP address matches the PC’s active NIC IP. If not, follow: How to Set the Enterprise Server IP Address. Use an IP address instead of a domain name if DNS resolution is unreliable. Ensure all required ports are open and configured correctly between ES and AS. Automation Server Ports are set and must be changed through WebStation - see Changing the Automation Server HTTP / HTTPS ports  Refer to: Information Technology System Planning Guide → Search “Network Ports”. Disable unused network adapters (e.g., Wi-Fi, VMware, VirtualBox). ES should use the primary NIC. 🔄 4. Repair Communication Right-click the ES → Advanced > Repair Server Communication This refreshes the communication tables. Detach and re-add ASs to the ES if needed. See: Unable to Add an Automation Server Underneath an Enterprise Server. 🛡️ 5. Antivirus & Security Software Disable network monitoring features in antivirus software. For Schneider laptops: Right-click Trellix in system tray → Enable Firewall Timed Groups. ⚠️ 6. Unsupported Architecture Enterprise Central (EC) and Enterprise Server (ES) should not run on the same PC with default ports. If testing: Stop EC service or Reconfigure ports to avoid conflicts. 🔍 Additional Tips Use the Communication tab on each server to verify peer visibility. Example of mis-configured IP Port settings Configuration after IP Port change on Automation Server

Issue The “Restore configuration with new IDs” option is greyed out during a restore operation and cannot be selected. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Enterprise Server Building Operation Automation Server (AS-P/AS-B) Backup and Restore Cause The option is unavailable because the user is not logged directly into the Automation Server (AS-P) being restored. When a restore is initiated from an Enterprise Server or Enterprise Central, the system does not allow creation of new IDs. As a result, the “Restore configuration with new IDs” option appears greyed out. Resolution   Log in directly to the target AS-P using WorkStation and perform the restore from that server. Steps: Open WorkStation. Log directly into the AS-P you intend to restore. Initiate the restore operation from the AS-P. The “Restore configuration with new IDs” option will now be available for selection.

  Issue The status of the Lights and Blinds buttons on a TRC (Touchscreen Room Controller) is not updated, and the buttons do not function as expected. Product Line EcoStruxure Building Operation, Field Devices Environment TRC, all models, with firmware version 2.2.0 and newer Cause The Lights and Blinds control buttons on the TRC were originally developed for a specific application using an RP-C controller. When this application is not present, the buttons do not operate. The buttons depend on logic that is not built into the TRC by default. A Lua script is required to define the command behavior and update the status of these controls. Resolution A sample Lua script is provided in the article attachment: TRC3500 Lighting Scenes Test R1.zip This sample can be used as a baseline for implementation. General approach: Download and review the provided sample Lua script. Modify the script to match the required control logic, inputs, and outputs. Load the Lua script into the TRC using EcoStruxure Building Operation (EBO). Verify that the script is running correctly. Test the Lights and Blinds buttons to confirm proper operation. If further customization is required, adapt the Lua script to align with the system design and controller interactions.

Issue License requirements for a standalone Automation Server at a site Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause There is uncertainty about whether a standalone Automation Server can be operated without a software license. This confusion typically stems from differences between EcoStruxure Building Operation versions and from historical licensing models. In practice, operating an Automation Server without the appropriate license constitutes non‑compliance with Schneider Electric software licensing terms, regardless of whether optional features are enabled. Resolution All deployments of an Automation Server must comply with Schneider Electric software licensing requirements. Operating an Automation Server without the appropriate license is a violation of the Schneider Electric End User License Agreement (EULA) and applicable Terms of Use   Centralized Licensing The EBO 7.0 Standalone Automation Server license option provides an entry point for addressing small-scale system opportunities, offering the Automation Server at a competitive price when full flexibility is not needed. The Standalone Automation Server license provides the full capacity and capabilities of the SpaceLogic Automation Server, with the only limitations being that it is locked to the Advanced Tier of the EBO feature set and does not support a connection to an Enterprise Server. Always use the Power and Buildings Software Companion tool to build your bill of materials for a Standalone Automation Server initial license   EBO 2022 or higher: Standalone Automation Server needs a software bundle license in addition to an add-on option license if required; check Part Number Summary and Hardware Software Matrix. Webstation license is included in the embedded server license.   EBO 3.2 or lower: A standalone Automation Server where no web services, Technician Tool (discontinued), SNMP, MQTT, Personal Dashboards, and TimeScale DB  are used does not require a license. Using one of these features requires a license 

Issue Customers performing offline license activation for EcoStruxure Building Operation (EBO) 7.x using Device Administrator may encounter issues specifically during the import of the Entitlement Certificate. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator (v7) Software Companion Portal FlexNet Licensing Portal Offline systems (no internet access) Cause Due to security risks, retrieving Entitlement data via an HTML file is no longer possible. The option is still available in Device Administrator, but the HTML file has been replaced with a PDF attached to the purchase email, containing the same information. Unfortunately, we cannot import the PDF the same way as we did with HTML. This applies to all new licenses for Building Operation 7.1.1. A new method will be implemented in the next maintenance release   This limitation affects only the certificate import step, not the overall offline activation method described here: EcoStruxure BMS Server Licensing on Servers not Connected to Internet Workflow. Resolution The simplest way is to enable Internet access for Device Administrator and add the entitlement ID. To activate licenses offline in Device Administrator: New Feature in 7.1.2 has been implemented for the Export/Import of the Entitlements.  See page 12 in the attached Release Notes  If this is not possible/available, there are several options, each differing in complexity and time requirements. Webhelp (Adding an Entitlement without the HTML file when a Field Server is not Connected to License Server (FNO)), users can follow the following steps: In Device Administrator, click Entitlements. Click the Add Entitlement down arrow, then select Manually Enter the entitlement ID. Click Next. Click Skip. If you know there are no servers connected to the internet in the list, click Skip. If you do not click Skip, Device Administrator scans all servers on your list until it finds one connected to the internet. In the Entitlement Products - Enter Manually list, enter the Activation ID, Description, and seat count for the product. Click Add Product to add more products. Click Add. Note: It is recommended to verify the Activation ID, Description, and seat count in mySchneider licenses before proceeding with the steps. When there is no connection between the EcoStruxure BMS Server and the License Activation Server, the Device Administrator cannot synchronize the number of licenses available for activation in the entitlement. Instead, Device Administrator assumes that all purchased licenses can be activated.  Contact support with your Entitlement ID, and they will send you an HTML version of your license for import into Device Administrator. (see Internal use only) Create a server list away from the site, using Device Administrator, that has Internet access. Caution: this will wipe the current server list, remove all certificates (if used), and remove all servers added to Device Administrator. If the server list has already been created on site, save and export this list. Off-site or on a PC with Internet access, import (from step 1) or create a new server list in Device Administrator. Add the necessary entitlement IDs. Save and export the server list. Back on the on-site PC, import the exported server list to Device Administrator. If using a new server list (that is, no servers added from Step 1), add the required certificates and servers. Save this new list. It is advisable to export it as a backup in case of any issues. Proceed with the offline activation. EcoStruxure BMS Server Licensing on Servers not Connected to Internet Workflow. Once activated, remember to save and export the list for safekeeping.  

Issue After restarting the EcoStruxure Building Operation (EBO) Enterprise Server, system performance may degrade significantly or the server may crash. This behavior may occur when the server attempts to generate Notification Reports in Microsoft Excel (XLSX) format during startup. Product Line EcoStruxure Building Operation  Environment EcoStruxure Building Operation Enterprise Server Systems with large databases and extensive trend logging Scheduled Notification Reports exported to Excel (XLSX) Observed in virtualized or physical Windows Server environments Systems using standard HDD storage (non-SSD), where disk performance may be limited Cause This issue is related to high system load during server startup combined with Notification Report generation. The following factors can contribute: The Enterprise Server is starting up while Notification Reports are running at the same time Large amounts of trend data increase processing load Slower disk performance (for example, systems using HDD storage) When these occur together, the system may struggle to process the report and write the Excel (XLSX) file correctly. This can result in corrupted Excel files, which then further increase system load and may lead to slow performance, unresponsiveness, or crashes. Resolution Review Notification Report schedules. Check all Notification Reports to identify which are scheduled to run at or shortly after Enterprise Server startup Identify recently edited reports Focus on Notification Reports that were recently modified, as the issue may begin after a report is edited  Determine which Notification Report is triggering during startup and contributing to the issue. Disable the identified Notification Report or adjust its schedule so it does not run during server startup Remove that reports generated Excel files Delete previously generated XLSX files from the affected report as these corrupted files can be causing the issue. Retain one file if needed for validation Repair the Excel file. Open the retained XLSX file in Microsoft Excel Re-save the file to allow Excel to repair any corruption Review trend log configuration and reduce unnecessary extended trend logs where possible. Restart the Enterprise Server and confirm that startup and system performance return to normal, and that Notification Reports generate Excel files successfully.      

Issue A customer cannot upgrade or apply an existing EcoStruxure Building Operation (EBO) 6.x license to a system that has already been created and is running on EBO 7.x using Software Companion. The system is currently operating with an engineering license, and the customer wants to convert or reuse the existing EBO 6.x license for permanent use. Product Line EcoStruxure Building Operation, Software Companion Environment System created directly in EBO 7.x using Software Companion EBO 7 engineering license assigned to the system Existing, unused, or previously purchased EBO 6.x license Cause An EBO 6.x upgrade license cannot be applied to a system that already has an EBO 7 engineering license assigned. Creating a system directly in EBO 7 using Software Companion prevents the use of the EBO 6 upgrade paths, which are required for license reuse or upgrade. Resolution To use an existing EBO 6.x license for upgrading to EBO 7, the current system configuration must be reset and reconfigured. Follow these steps: If the engineering license has been activated on-site, return or deactivate it before proceeding. In Software Companion, navigate to the system and delete the assigned EBO 7 engineering license. Contact support to have the original project and system removed from Software Companion. Once the system is removed, perform the upgrade using the existing EBO 6.x license through the official upgrade workflow as described here Create or configure the system following the proper upgrade path to ensure license compatibility. Note: Direct upgrade or reassignment of an EBO 6.x license to an already configured EBO 7 system is not supported. The system must follow the correct upgrade process from the beginning.

Issue Uncertainty about whether an additional DALI power supply can be added to an EcoStruxure Building Operation (EBO) DALI installation, and confusion regarding the actual DALI current output capability of the CRS controller (64 mA vs. 250 mA). Product Line EcoStruxure Building Operation Environment RP-C Controller with DALI (CRS) DALI field bus integration Cause The confusion originates from documentation references to a 250 mA DALI value, which is a general DALI specification statement indicating that the controller includes an integrated DALI power supply. The CRS hardware itself is limited to a maximum DALI supply current of 64 mA. Additional misunderstanding existed between: Connecting an external DALI power supply in parallel with the CRS DALI output (not supported) Using a true galvanically isolated DALI repeater with its own external power supply (supported) Resolution Adding an additional DALI power supply is supported only when using a true galvanically isolated DALI repeater. The repeater must electrically separate the CRS DALI line from the output side and regenerate the DALI signal. The following configurations are supported: The DALI repeater draws minimal current (approximately 2 mA) from the CRS DALI line The repeater provides a new DALI output with its own externally powered DALI power supply No parallel connection exists between the CRS internal DALI power supply and another DALI PSU The following configurations are not supported: Adding a second DALI power supply directly in parallel with the CRS DALI output Using DALI expanders that act as DALI gear on the input and rebroadcast on the output Regarding DALI current capability: The CRS DALI supply current is 64 mA only The CRS cannot operate at 250 mA at any time The 250 mA reference is a DALI standard classification and not an operational capability of the CRS From a hardware and software perspective, the use of a galvanically isolated DALI repeater is technically safe and supported.

Issue There is uncertainty whether the solid-state relay (SSR) digital outputs on the RP-C-16C controller are suitable for controlling start/stop of external equipment when the required load current is very low (below 1 mA). Product Line EcoStruxure Building Operation Environment RP-C-16C controller using solid-state relay (SSR) digital outputs Cause The RP-C-16C uses solid-state relay (SSR) outputs instead of mechanical relay outputs. This raised concerns about whether the SSR outputs can reliably switch very low load currents, based on external manufacturer recommendations that specify minimum load requirements. Resolution The SSR outputs on the RP-C-16C are suitable for switching very low load currents below 1 mA without issue. The following conditions must be met: The connected load current may be below 1 mA The output voltage must remain within the SSR specifications of the RP-C-16C As long as the voltage ratings specified for the RP-C-16C SSR outputs are not exceeded, using the SSR outputs for start/stop control of external equipment is technically safe and supported.

Issue After a Daylight Saving Time (DST) transition, interval trend logs in EcoStruxure Building Operation may display two entries with the same local timestamp, most commonly 03:00 AM, on the DST changeover day. This can be interpreted as duplicated or incorrect trend data. Product Line EcoStruxure Building Operation Environment SmartX IP Controllers (MP/RP) EBO native Trend Log objects BACnet Trend Log objects hosted in SmartX controllers WorkStation and WebStation Cause EcoStruxure Building Operation servers and SmartX controllers operate internally using UTC (Coordinated Universal Time). Trend data is stored and processed in UTC Time zone and DST adjustments are applied only at the UI layer (WorkStation / WebStation) It is important to distinguish between EBO native Trend Log objects and BACnet Trend Log objects used in SmartX IP controllers, as their configuration options differ. EBO Native Trend Log Objects Created on Automation Servers or Enterprise Servers Support an Interval Time Zone setting The Interval Time Zone setting controls how the next interval sample is scheduled (UTC or Server Local Time), particularly for long intervals such as daily logs As described in the existing “Interval time zone setting in Trend log” article, using Server Local Time may result in intervals of 23 hours (DST start) or 25 hours (DST end) This setting affects interval duration only. It does not change how timestamps are stored. All samples remain uniquely timestamped in UTC. BACnet Trend Log Objects (SmartX MP/RP Controllers) Implemented as standard BACnet Trend Log objects Do not have an Interval Time Zone setting Interval sampling is based on elapsed time using UTC and is unaffected by DST changes at the controller level During a DST fallback (Autumn), the local clock hour is repeated. As a result, two distinct UTC timestamps may be converted by the UI into the same local time when displayed. This causes two trend entries to appear with the same local timestamp (for example, 03:00 AM). There is no duplication or ambiguity in the stored trend data. The duplicated timestamp is a local-time display effect caused by UTC‑to‑local‑time conversion during a repeated hour. Resolution This behaviour is expected and correct. Trend data remains accurate and uniquely timestamped in UTC Duplicate local timestamps appear only when UTC timestamps are rendered in local time during a DST fallback The Interval Time Zone setting does not prevent duplicate local timestamps BACnet Trend Log objects do not support Interval Time Zone configuration No supported fix exists to suppress one of the entries without discarding valid data Customers should be advised that DST transition days may show repeated local times in trend logs

  Issue Unable to load a LUA script in a Touchscreen Room Controller (TRC) via EcoStruxure Building Operation (EBO). Product Line TRC (Touchscreen Room Controller) – all versions Environment EcoStruxure Building Operation WorkStation 4.0 and newer Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in loss of configuration data if not performed properly. Before beginning these steps, ensure any important configuration or scripts are backed up. If you are unfamiliar with the steps in this article, contact Product Support for assistance. Cause LUA scripts cannot be loaded directly into TRC devices using the default object set in EcoStruxure Building Operation because the Custom Lua File Advanced object is not included by default and must be manually created. Resolution To load and edit a LUA script for a TRC device, perform the following steps: Under the TRC device, right-click Application. Select New object. Expand Program. Select Custom Lua File Advanced. Click Edit in the wizard. Set the Instance ID value to 1. Navigate to the TRC BACnet object list. Right-click the newly created Custom Lua File Advanced object and select Edit.   The LUA editor page will open, allowing the LUA script to be pasted and edited. Refer to any associated screenshots for additional guidance.  

Issue An AS-P configured as a Modbus Serial Server stops all Modbus communication. After issuing a Warm Start, the AS-P does not complete startup and remains non-operational until power is cycled. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Modbus Serial Server configuration Cause Duplicate Modbus register numbers are assigned to multiple points under the Modbus Local Device folder. This register conflict prevents the Modbus stack from initializing correctly and can cause the AS-P to hang during a warm restart. Resolution Open the Modbus Local Device in the AS-P. Review all Modbus points exposed for sharing. Ensure each point has a unique Modbus register number. Modify any duplicate registers so all addresses are unique. Save the changes. Power cycle the AS-P if required for recovery. After correcting duplicate register assignments, the AS-P starts normally after a warm start and Modbus communication operates as expected. Important Note: Duplicate register numbers must not be assigned to points under the Modbus Local Device folder, as this can impact both Modbus communications and controller stability.

Issue In a multi-version EcoStruxure Building Operation system where the Enterprise Server has been upgraded to version 7.1 but some Automation Servers or AS-Ps remain on older versions (for example 3.1 or 3.2), historical data is not being sent to TimescaleDB. The database schema appears to remain at an older version and data collection or compression does not work as expected. Product Line EcoStruxure Building Operation (EBO) Environment Mixed-version EBO system (ES 7.1 with AS/ASP on versions 3.x, 5.x, and 7.x) PostgreSQL version 14 TimescaleDB version 2.5 TimescaleDB used as the external historical database (ebo_db) Cause The issue is caused by a combination of an outdated TimescaleDB version and misunderstanding of schema compatibility in multi-version EBO systems. While EBO database schemas are backward compatible to the lowest supported version, certain features (such as compression) require a minimum TimescaleDB version. Running an older TimescaleDB version can prevent proper data handling even when the Enterprise Server and schema have been upgraded. Resolution Ensure PostgreSQL and TimescaleDB are running versions that are currently supported for the EBO release in use. The database schema provided with the latest EBO version (for example 7.1) is sufficient; it is not necessary to sequentially execute schema scripts from earlier versions (V4, V5, V6). The latest schema includes all required updates. Automation Servers and AS-Ps on older versions can send data to a TimescaleDB using a newer schema, provided PostgreSQL and TimescaleDB versions are correct. To use TimescaleDB compression features, ensure TimescaleDB version 2.11 or later is installed, regardless of the EBO version. After upgrading PostgreSQL and TimescaleDB, verify connectivity and data flow from all servers to the TimescaleDB instance.

Issue After renaming the Enterprise Server (ES) in an EcoStruxure Building Operation system, Active Directory (AD) users can no longer log on directly to an Automation Server (AS). The login attempt fails with the error message: “Offline Windows logon is unsupported.”   AD authentication continues to work when logging in to the Enterprise Server or when accessing the system via Workstation connected to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Cause To login to EC and ES is working good with AD user, it is only an issue to login directly on the AS. Renaming the Enterprise Server causes an inconsistency in the AD domain configuration stored on the Automation Server. Although the ES continues to authenticate correctly with Active Directory, the AS retains stale or invalid domain information, which prevents direct AD-based logins at the AS level. Resolution Recreate the domain membership on the Automation Server: Using Workstation, remove the affected Automation Server from the EBO domain. Verify that the domain object is removed from the AS. Add the Automation Server back into the EBO domain. Confirm that the domain is recreated successfully on the AS. Retry logging directly into the Automation Server using an AD account. AD login should now function correctly.

Issue A TGML graphic generates a script alert such as: TypeError: Cannot call method "getAttribute" of null (cmd#xx) TypeError: Cannot call method "setAttribute" of null (cmd#xx) The error may occur when the graphic loads, when a bound value updates, or when a user interacts with the graphic (for example, mouse click). Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphic Cause The error is caused by a TGML JavaScript attempting to execute a method on a null object reference. Most commonly, this occurs when: A TGML component has been deleted or renamed, but one or more scripts elsewhere in the graphic still reference the original object. A script calls a method such as getAttribute() or setAttribute() on an object that does not exist at runtime. In some environments, scripts may also encounter transient null values during initial graphic load. In these cases, bound values may briefly evaluate to null, causing method calls or value conversions to fail even though the graphic later operates normally. This behavior has been observed more frequently during first-load timing conditions rather than as a persistent configuration error. Resolution Follow these steps to identify and correct the offending script, prioritizing validation of object references: Determine when the error occurs On initial graphic load When a bound value changes On user interaction Once only or repeatedly This helps narrow down the script responsible for the error. Isolate the faulty TGML script Save the graphic under a new name. Incrementally remove sections of the graphic until the error no longer appears. The removed section contains the script referencing a null object. Identify the exact failure point Use the cmd# number in the error message to locate the script line. Open the Script Editor using the “…” button next to the script Content attribute. Navigate to the indicated line and identify which object or method is referenced in the error message. Correct invalid object references Verify that all objects referenced in the script still exist and are correctly named. Update the script to reference valid objects, or restore or rename deleted components as required. Confirm that method parameters are valid and reference existing TGML elements. Handle potential null values defensively If the error occurs during value retrieval or string conversion, review any use of toString() on bound values. Improved stability is often seen by converting values using safe type coercion (for example, concatenation with an empty string) to avoid exceptions when values are temporarily null during graphic load. Investigate bound point types and data sources, particularly remote or multistate values, if null behavior is observed intermittently.

Issue EcoStruxure Building Operation Automation Server, Enterprise Server and BACnet object names limitation Dragging converted I/NET TGML graphics into Workstation causes Workstation to crash with following message: Exception message: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SE.WorkStation.Base.Windows.Views.TgmlFileDropHandler.Drop(FileInfo, Path, IOperationContext, IProgressInfo) at SE.WorkStation.Base.Windows.Views.FileDropCoordinator.ExecuteDrop(Path, IList`1, IProgressInfo) at SE.WorkStation.Base.Windows.Views.<>c__DisplayClassd.b__9(IProgressInfo) at SE.WorkStation.Framework.Services.<>c__DisplayClass1.b__0(IProgressInfo) at SE.WorkStation.Framework.ProgressIndication.ProgressActionOperation`2.Run(IProgressOperationInternal, IProgressResult, IProgressOperationInfo) at SE.WorkStation.Framework.Services.ProgressItem`1.b__1a(Task) at System.Threading.Tasks.<>c__DisplayClasse`1.b__d() at System.Threading.Tasks.Task`1.InvokeFuture(Object) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute() Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The number of characters and the use of special characters in a EcoStruxure Building Operation object name and EcoStruxure Building Operation BACnet objects names Resolution Refer to the Webhelp Object Names topic for information on naming restrictions The statements in Webhelp also apply to EcoStruxure Building Operation BACnet objects unless is it a Continuum b3 object.  If you are creating a Continuum b3 object etc., the b3 object display name is limited to 16 characters consisting solely of letters, digits, and underscores (as per Continuum limitation). Basically, any objects you create for Continuum, for example, a 'BACnet Analog Input (Continuum)' will be subjected to the Continuum limitation. If you add a standard 'BACnet Analog Input' into an Automation Server or an Enterprise Server, then it is not limited by the Continuum limitation of 16 characters. The most common issue when bringing I/NET TGML converted graphics into Workstation is not checking for spaces at either the beginning or end of the converted file name.  Make sure there are no spaces (white space) before or after any characters of the file name before copying into Workstation.

Issue Customers need to determine how many SpaceLogic TC900 Protocol Series thermostats can be connected to the COM A or COM B RS-485 ports of a SmartX Server on a BACnet MS/TP network. The unit load contribution of the TC900 device is not clearly documented, making it difficult to calculate the maximum supported device count. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TC900 Protocol Series thermostat SmartX Server BACnet MS/TP (RS-485) network Cause Public documentation does not explicitly state the BACnet MS/TP unit load (UL) of the SpaceLogic TC900 Protocol Series thermostat. Without this value, planners cannot accurately calculate the allowable number of devices per RS-485 segment. Resolution The Worksheet for Configuration of RS-485 Bus with Generic RS-485 Devices can be applied with answers to the transceiver interface attributes below. The TC900 Thermostat uses a TP8485E RS-485 transceiver, which has the following characteristics: Reduced 1/8 unit load (0.125 UL) Failsafe transceiver (does not require external biasing) Onboard bias resistors of 47 kΩ Because of the onboard bias resistors, the effective contribution to the MS/TP bus is higher than the transceiver UL alone. Effective Unit Load Calculation Transceiver Transceiver Unit Load Transceiver Failsafe TC900 Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus TP8485E 0.125 Yes 47k ohm 0.255 0.38 No   Based on the BACnet MS/TP standard maximum of 32 UL per RS-485 segment: 32 ÷ 0.38 ≈ 82 devices Up to 82 TC900 Sensor Units can be connected per SmartX Server COM port, based on unit load calculations. RS-485 Network Considerations The TC900 does not have an isolated RS-485 interface and conforms to Generic RS-485 Network Device Configuration 1. A network made up only of TC900 Thermostats typically requires: One 120 Ω termination resistor at each end of the bus No additional bias resistors Additional Notes The maximum recommended node count may be further reduced by system architecture, cabling, baud rate, or performance requirements. Increasing the number of MS/TP devices increases bus latency. RS-485 repeaters may be required for networks approaching higher node counts. When both LonWorks and BACnet MS/TP are used on the same Automation Server, the network with more than 10 devices is treated as the main network, and the other is limited to 10 devices. Refer to the Architectural Guidelines for further limitations and guidance.

Issue A license violation occurs in a multi-version EcoStruxure Building Operation (EBO) system after upgrading the top-level server to EBO 7 when embedded or legacy licenses on lower-version servers are removed or not retained. Product Line EcoStruxure Building Operation (EBO) Environment Multi-version EBO system where: The top-level server (EC, ES, or standalone AS) is running EBO 7.0 or later One or more underlying servers remain on EBO versions prior to 7.0 Centralized Licensing is used with Device Administrator Legacy embedded or Windows-based licenses previously existed on individual servers Cause From EBO 7 onward, a centralized licensing model is used where licenses are activated on the top-level server and inherited by other servers in the system. Servers running EBO 7 automatically inherit both base and feature licenses from the top-level server and no longer require local license activation. In a multi-version system, however, servers that remain on EBO versions prior to 7.0 do not fully participate in centralized licensing. These older-version servers still require their own locally activated base licenses (such as Enterprise Server, Automation Server, and Connected Devices) that match their installed EBO version.   A license violation occurs if these existing licenses are removed, expired, or not carried over when the top-level server is upgraded to EBO 7, even though the system entitlement is valid and active on the top server. Resolution When deploying Centralized Licensing in a multi-version EBO environment: Keep all existing base licenses active on any servers running EBO versions prior to 7.0. Do not remove or deactivate embedded or legacy licenses on lower-version servers during or after upgrading the top-level server to EBO 7. Once an underlying server is upgraded to EBO 7, its local legacy licenses can be safely removed, as it will then inherit licenses centrally. This behavior is expected and by design. License violations in this scenario indicate missing or removed licenses on servers that remain on earlier EBO versions and must be resolved by restoring the appropriate licenses until all servers are upgraded.