Issue When modifying a Function Block program in EcoStruxure Building Operation, will outputs cycle or fluctuate after saving changes? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Function Block Programming Cause Function Block programs process signals in cycles, passing values between connected blocks. Each block retains its last value in memory when changes are committed. Stable Output: If logic affecting the output remains unchanged and no Delay blocks are used, outputs typically remain stable. Fluctuating Output: Logic changes that directly impact output signals. Use of Delay blocks in control logic. Delay blocks reset to their default value upon saving, which can cause a one-cycle fluctuation in output. Resolution To prevent physical device damage during program changes: Apply software overrides by forcing output values on I/O modules. Use Hand/Auto/Off (HAO) controllers on output devices. These measures safeguard equipment and allow validation of logic changes after saving.

Issue The EBO system previously operated as expected with Active Directory (AD) integration. Following an upgrade or hotfix, AD users are unable to authenticate and log in to the Enterprise Server (ES). Workstation login error: User account not associated with a group The Workstation Error when trying to login is: User account not associated with a group.     Error(s) message in ES trace log may include: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28). Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved since version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution To enable the legacy method of matching groups during logon, configure the following property: Steps: Open the ES.properties file, typically located at: C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config Add the following line: NspServer.Windows.Group.MatchByName = true Save the file and restart the Enterprise Server for the changes to take effect.     To take advantage of the Active Directory (AD) performance enhancements introduced in recent versions of EcoStruxure Building Operation, it is necessary to re-establish the link between AD groups and their corresponding EBO groups. Procedure: Open the relevant EBO group configuration. Locate the Windows group name property. Temporarily change its value to an empty string or any placeholder text. Re-enter the correct value, which should match the associated AD group name. Save the changes to complete the re-connection process.   Completing the previously described procedure ensures that the hidden External SID property for the EBO groups is correctly populated. This property was not updated during the upgrade because the process was performed without an active connection to the AD server.  

Issue The NW8000 Optimal Start-Stop (OSS) block in EcoStruxure Building Operation (EBO) shows “Abnormal Input” status even when configuration appears correct. Bound parameters display valid values, but the object status remains abnormal. Product Line EcoStruxure Building Operation Environment Building Operation Server NW8000 OSS objects available for use outside NW8000 interface from EBO 2022 onward. Cause Incorrect Input Configuration: Both Heat Enable and Cool Enable inputs are set to ON (true) simultaneously, forcing conflicting modes. Missing Bindings: Required bindings to the Value and TimeToNextTransition properties of the digital schedule are not configured. Parameter Mismatch: Heat/Cool changeover temperatures and PreStart/PreStop tables must use correct values for the measurement system used (Fahrenheit/Celcius). Digital Schedule Misconfiguration: OSS relies on the TimeToNextTransition value from the referenced Digital Schedule. If the schedule has no events within the next 8 days, the schedule outputs a “maximum” value (millions of minutes until year 2106), causing OSS to enter Abnormal Input. Resolution Correct OSS Inputs: Set Heat Enable and Cool Enable to Null for normal operation. If forcing mode is required, only one input should be ON at a time. Both ON = Abnormal Input. Verify Bindings: Bind OSS block to: Digital Schedule → Value Digital Schedule → TimeToNextTransition Ensure schedule outputs correct ON/OFF states. Configure Digital Schedule Properly: Include an accurate weekly schedule and exceptions. Ensure at least one event exists within the next 8 days. Refer to: Adding a Weekly Event Adding a Date Exception Event Adding a Date Range Exception Event Adding a Calculated Exception Event Check Parameters: Heat/Cool changeover temps (OA values) must use correct values for the measurement system used (Fahrenheit/Celcius). PreStart/PreStop table range must match the measurement system used. Heat and Cool Enable Truth Table Heat Enable Cool Enable Actions EMPTY / NOT ACTIVE EMPTY / NOT ACTIVE Use Heat/Cool Changeover Temperatures OFF OFF No Heating or Cooling Pre-start or Pre-stop EMPTY / NOT ACTIVE OFF No Heating or Cooling Pre-start or Pre-stop OFF EMPTY / NOT ACTIVE No Heating or Cooling Pre-start or Pre-stop ON OFF / EMPTY / NOT ACTIVE Enable Heating for Start. Use Heat Start/Stop Tables OFF / EMPTY / NOT ACTIVE ON Enable Cooling for Start. Use Cool Start/Stop Tables ON ON Outputs set to ABNORMAL INPUT

Issue How to calculate and display Mean Kinetic Temperature (MKT) for a temperature sensor in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment EBO version 3.2 or later (required for Log Processing Trend Log functionality) Trend logs available for temperature sensors Customer requirement: MKT based on hourly averages or 30-minute intervals over a 24-hour period Cause Mean Kinetic Temperature (MKT) is a derived temperature that represents the cumulative thermal stress experienced by a product over time. Unlike a simple average, MKT gives greater weight to higher temperatures because chemical degradation accelerates exponentially with temperature (based on the Arrhenius equation). Why it matters: Used in pharmaceutical, food, and logistics industries for stability studies and cold chain monitoring. Sensitive to temperature spikes—short excursions at high temperatures significantly increase MKT. Recognized by FDA, EMA, and ICH guidelines for stability and excursion analysis. Formula for equal time intervals: ​ Where: TK​ = Mean Kinetic Temperature (Kelvin) ΔH = Activation energy (~83.14472 kJ/mol for pharmaceuticals) R = Gas constant (0.008314472 kJ/mol·K) T1,T2,…Tn​ = Temperatures in Kelvin n = Number of readings EcoStruxure Building Operation does not have a native MKT function, so it must be implemented using custom calculations in Log Processing Trend Logs. Resolution Use three Log Processing Trend Logs to compute MKT from trend logs: Step 1: Prepare Hourly Average Temperature Create a Log Processing Trend Log named HourTemp. Period Interval: 1 hour Calculation Type: Average Input: Temperature trend log Persist Data: False Step 2: Calculate Denominator for MKT Formula Create a second Log Processing Trend Log named MKTdenom. Period Interval: 1 hour Calculation Type: Average Input: Reference HourTemp log Log Unit: Celsius → Target Unit: Kelvin Custom Calculation: var dH := 83.14472; // Activation energy (kJ mol^-1) var R := 0.008314472; // Gas constant (kJ mol^-1 K^-1) exp(-dH / (R * @(HourTemp))) // Temp in Kelvin Step 3: Compute Final MKT Create a third Log Processing Trend Log named MKT. Period Interval: 1 day Calculation Type: Summary Input: Reference MKTdenom Custom Calculation: var dH := 83.14472; var R := 0.008314472; ((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15 This converts back to Celsius. For Fahrenheit: (((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15) * (9/5) + 32 Important Note You may have to adjust the substitution code based on what you have named your log references. Ensure the variable names in the formula match your Log Processing Trend Log names. Additional Notes Ensure @(MKTdenom:Count) matches the number of samples per day. Adjust constants if customer specifications differ. Set the unit on the final Log Processing Trend Log (°C or °F). You can alarm on MKT values or display them in dashboards and trend charts.

Issue Users encounter problems assigning entitlement licenses to AS-B and AS-P controllers in EcoStruxure Building Operation (EBO) 2022 (v4.0) and later using Device Administrator. Common symptoms include: Entitlement assignment fails for AS-B/AS-P. Assignment option is greyed out. Entitlement added but no license product appears. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA) Cause Starting with EBO 2022, Schneider Electric introduced a scalable licensing model that decouples hardware and software: Hardware is sold at a lower price. Sites purchase license bundles sized for their needs (Standalone, Standard, Enhanced, Full). Impact: Pre-2022 AS-P/AS-B models included most software capabilities and require upgrade SKUs when moving to EBO 2022 or later. Post-2022 Secure Boot AS-P and Scalable AS-B models require new entitlement bundles and support flexible licensing. Secure Boot adds cryptographic firmware validation. Resolution Verify Hardware Model AS-B: SXWASBXXX10001 → Requires upgrade bundle license. SXWASBXXHP10001 → Compatible with EBO 2022 and later bundle. AS-P: SXWASPXXX1000X → Requires upgrade bundle license. SXWASPSBX10001 → Compatible with EBO 2022 and later bundle. Check EBO Version For EBO 2022 and later, confirm entitlement compatibility. Assign Correct License Use upgrade license for older controllers. Activate via Device Administrator with internet access. Confirm Assignment After activation, assignment option should be enabled. If “No license product available” appears, verify entitlement type. Reference: Part Number Summary and Hardware-Software Compatibility Matrix. License Compatibility by Hardware Model Hardware Model EBO Min Version License Type Notes AS-P (SXWASPXXX1000X) 1.7.1 Upgrade Bundle Non-secure boot, pre-2022 hardware AS-P Secure Boot (SXWASPSBX10001) 2022 New Entitlement Bundle Standard, Enhanced, Full bundles AS-B (SXWASBXXX10001) 1.8.1 Upgrade Bundle Older AS-B models require upgrade AS-B Scalable (SXWASBXXHP10001) 2022 New Entitlement Bundle Standard or Full bundles  

  Issue A License Violation alarm is triggered without displaying a License Violation banner. Alarm reactivates after acknowledgment, approximately every 10 minutes.   Device Administrator also shows a license violation in "License status," when all servers show no violation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Potential communication issue, possibly related to return path or port configuration. An incorrect ES port may be in use, which could be contributing to the issue. The Communication Tab [Communication View] and Server List in xbk Analyzer show only the ES, indicating limited server visibility. Resolution Verify Communication Path Ensure the ES is defined as using the same ports across all servers. Confirm that the ports are correctly configured and open on all relevant servers. Review the Communication Tab [Communication View] and Server List Check that all expected servers are listed and actively communicating. If only the ES is visible, investigate potential network or configuration issues. See article for additional information: Updating a Enterprise Server IP Address - Schneider Electric Community Check AS Logs Log in to the Automation Servers to identify any communication errors. These errors may not be visible from the ES alone. Next Steps If the above steps do not resolve the issue or the root cause remains unclear: Refer to the article for possible communication-related troubleshooting options: Enterprise Server and Automation Server Bindings show Unresolved - Schneider Electric Community Refer to the article for additional license troubleshooting options: Troubleshooting EBO license violation issues - Schneider Electric Community Contact your local support organization for further assistance.

Issue Automation Servers in an EcoStruxure Building Operation (EBO) system are unexpectedly changing their time. Investigation shows that a third-party BACnet IP device is sending BACnet Time Sync messages, causing the time drift. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet IP Cause A third-party BACnet device is broadcasting BACnet Time Synchronization messages on the IP network. By default, older EBO versions honor these messages, resulting in unintended time changes. Resolution Option 1: Modify Third-Party Device Configuration If possible, disable BACnet Time Sync on the third-party device. This is the most direct solution but depends on vendor capabilities. Option 2: Upgrade EBO From EBO 5.0.3.16010 (CP15) onward, AS-P controllers ignore BACnet Time Sync by default. This behavior is first included in: EBO 5.0.3.16010 (CP15) EBO 6.0.4.6003 (CP4) EBO 7.0.2 release To re-enable honoring BACnet Time Sync (if required): Configure a service_blacklist Add the following to the file to enable the time sync: <blacklist> <global> <enable-execute-time-sync/> </global> </blacklist>

Issue Confusion exists around which MicroNet controllers are supported in EcoStruxure Building Operation (EBO), especially during upgrades to EBO 7. The term “MicroNet” covers multiple product families with different protocols and support timelines. Product Line EcoStruxure Building Operation, TAC IA Series, Satchwell MicroNet Environment EcoStruxure Building Operation (EBO) MicroNet 2000 (NW8000) I/A MicroNet (MNL and MNB) Satchwell MicroNet Cause The term “MicroNet” can refer to multiple unique product ranges. In EBO documentation, MicroNet typically refers to Satchwell MicroNet, the European range of controllers using NCP, ARCnet, or LON protocol, which are not supported from EBO v4.0 onward. Other MicroNet families (MicroNet 2000 and I/A MicroNet) have different support histories. Resolution Refer to the table below for family types, lifecycle dates, and EBO support history: Family Protocol Introduced Withdrawn EBO Support History MicroNet 2000 (Barber Colman) MNet under ASD Late 1980s 2011 Supported up to EBO v3.2 Not supported in EBO 4.x–6.x Reintroduced in v7.0 I/A MicroNet – MNL Series LonWorks ~1998 2023 Supported in all SBO/EBO versions I/A MicroNet – MNB Series BACnet ~2003 2023 Supported in all SBO/EBO versions Satchwell MicroNet NCP / ARCnet / LON ~1998 2013 Supported up to EBO v3.2 Not supported from EBO v4.0 onward Additional Notes: MicroNet 2000 support was reintroduced in EBO 7 after being dropped in EBO 4–6. I/A MicroNet (MNL and MNB) support has never been removed from EBO. Satchwell MicroNet is unsupported from EBO v4 onward.

Issue During an Automation Server upgrade using Device Administrator, you may see warnings or errors in the Conversion Log. Errors block the upgrade process. Warnings allow the upgrade to complete, but may indicate invalid values or bindings. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS-P, AS-B Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause Starting with EBO v1.4, new binding rules were introduced: Public Numeric/Signal bindings removed Multiple bindings per point prohibited (only the first remains) Bindings to Local-Node NVIs dropped Older configurations that violate these rules trigger warnings or errors in the Conversion Log. Resolution Run the Device Administrator upgrade. Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see: SmartX Server System Upgrade Workflow - EcoStruxure WebHelp  Opening the Conversion Log - EcoStruxure WebHelp Export and review the Conversion Log: The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue Need to quickly and accurately count field devices in an EcoStruxure Building Operation (EBO) system for license validation or upgrade planning. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SEAL Script: Standard Scripts → Field Device Count Cause Manual counting of devices is inefficient and error-prone. SEAL provides an automated script to scan the system and report the total number of licensed field devices. What is SEAL? SEAL(Schneider Electric Automation Library) is an external Schneider Electric toolbox designed to automate and simplify engineering tasks for EBO. Key features include: DWG to TGML converter for graphics. Script utility for automating EBO engineering tasks such as: BACnet object conversion. Generating trend logs. Advanced bindings and search/replace. Automated duplication of devices or folders. Ability to run standard scripts (like Field Device Count) or create custom scripts. Further information on SEAL can be found in the EcoStruxure SEAL Forum Access: SEAL is available to EcoXpert partners (Registered, Certified, Master) and Schneider Electric employees. SEAL can be downloaded from the EcoXpert Extranet Resolution Steps to Use the Field Device Count Script Open SEAL Launch the SEAL application. Access the Script Click Scripts in SEAL. Use the Quick Filter to search for Field Device Count. This script is part of the Standard Scripts package. Configure and Run Connect SEAL to the top-level server (Enterprise Server or highest Automation Server). Set options: Include Subservers: Checked (to scan the entire system). Output to Results View: Optional (for quick review). CSV File Path: Optional (to export device list).   Review Results The script outputs a list of detected field devices and a total count. Use this count for license compliance or upgrade planning. Export Data (Optional) If a CSV path was specified, review the exported file for detailed device information.

Issue After performing successive ColdStart or WarmStart operations on an AS-P, the device becomes inaccessible over IP (Workstation, WebStation, Device Administrator). It can only be accessed via USB using Device Administrator. A power cycle is required to restore IP connectivity. Product Line EcoStruxure Building Operation Environment Automation Server Premium (AS-P)  AS-P running se3linux (EBO v3.2.x onward) Cause The underlying Linux systemd service manager interprets repeated restart commands as a failure condition. When multiple WarmStart/ColdStart operations occur in quick succession, systemd assumes the EBO server process is crashing and hits the start-limit threshold, preventing further automatic restarts. Relevant systemd configuration (from /etc/systemd/system/nsp_servers.service StartLimitIntervalSec=270s StartLimitBurst=2 This means: If the service restarts more than twice within 4.5 minutes, systemd stops trying to restart it. System logs confirm this: systemd[1]: se-nsp-server.service: Start request repeated too quickly. systemd[1]: se-nsp-server.service: Failed with result 'start-limit-hit'. Resolution Avoid performing multiple WarmStart/ColdStart operations in rapid succession. If the AS-P becomes inaccessible: Connect via USB using Device Administrator. Perform a power cycle of the AS-P to restore IP connectivity. Best Practice: Allow sufficient time between restart commands to prevent systemd from triggering the start-limit condition.

Issue Customers using Device Administrator for offline license activation in EBO 7.0.3 face challenges due to changes in how entitlements are delivered via Software Companion. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator (v7) Software Companion Portal FlexNet Licensing Portal Offline systems (no internet access) Cause The current Software Companion tool does not generate an HTML entitlement certificate compatible with Device Administrator. Instead, it provides a PDF summary, which the Device Administrator cannot read or import. Resolution The simplest way is to enable Internet access for Device Administrator and add the entitlement ID. To activate licenses offline in Device Administrator: Do not use the PDF summary generated by Software Companion — it is not compatible with Device Administrator. There are several options available, 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 follwing steps: In Device Administrator, click Entitlements. Click the Add Entitlement down arrow and click Manually Enter the entitlement ID. Click Next. Click Skip. If you know that you do not have any server connected to internet in the list, click Skip. If you do not click Skip, Device Administrator goes through all servers in your list until it finds one that is connected to 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 FlexNet Operations End-User Portal before proceeding with the steps. When there is no connection between the EcoStruxure BMS Server and License Activation Server, Device Administrator cannot synchronize the number of licenses in the entitlement that are available for activation. Instead, Device Administrator assumes that all licenses that was purchased can be activated.  Access the FlexNet Licensing Portal: FlexNet Operations End-User Portal Log in using the Entitlement ID. List all Entitlements. Select one Activation ID Use the View Certificate option. Download and save the certificate locally in HTML format. When using Save As - ensure you select the "Webpage, complete (*htm;*html) option  Repeat for each Activation ID listed in the Entitlement Import each HTML certificate into Device Administrator to load the entitlement offline. 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. Comment: Investigation into why Software Companion does not generate HTML certificates is ongoing.  Device Administrator still requires either the HTML certificate or manual entry of activation IDs.

Issue License needs to be activated or repaired, but there is no Internet access on the computer hosting the license. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator  Cause The computer cannot be moved to a location with Internet access for activation or repair. IT policies prohibit temporary Internet access for licensing purposes. Resolution SBO Offline Activation Tool Use the SBO Offline Activation Tool for offline license activation. Access the tool here: SBO Offline Activation Tool. Click Instruction and Help in the tool for step-by-step guidance and helpful videos/charts. SBO Offline License Repair The same tool can repair offline licenses. Access the tool here: SBO Offline Activation Tool. After launching the tool, go to Special Operations → Repair License. If repair fails, contact Support for further troubleshooting.

Issue After updating Java (e.g., to Java 7 Update 65 or later), WebStation graphics may appear blank or white.  Note: If the error you see is “Error. Click for details” and not a blank window, please refer to the article: WebStation graphics not working after Java updated to Java 7 Update 51. Customers also need clarity on when Java was removed from WebStation and replaced by HTML5. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Building Operation WebStation Cause Compatibility issues between Java and WebStation in TAC Vista or older Building Operation versions. Java applets were historically used for TGML graphics, causing security warnings and browser compatibility problems. Transition to HTML5 technology eliminated these issues. Resolution For Java-related issues (TAC Vista or SBO 1.5 and earlier) Update Java Install the latest Java version (e.g., 1.7u67). On x64 systems, install both x86 and x64 Java versions. If issue persists, perform clean reinstall: Close all browsers. Uninstall all Java versions. Backup exception.sites file: C:\Users\<username>\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites Delete folder: C:\Users\<username>\AppData\LocalLow\Sun Reinstall latest Java (both x86 and x64 if applicable). Verify Java installation using Java uninstall applet. Restore exception.sites file to its original location. Technology Transition Note Pre-2014 (SBO 1.0–1.5) TGML graphics displayed using Java applets. 2014–2015 (SBO 1.6) HTML5 Viewer introduced as Beta in WebStation. Users could enable HTML5 manually; Java remained default. 2015–2016 (SBO 1.7) HTML5 fully implemented as the default graphics viewer. Java completely removed from WebStation. 2017 onward (EBO 2.x and beyond) Modern HTML5 UI with responsive design. No plugins required; optimized for Chrome, Edge, Firefox.

Issue The instance values the Function Block program had when the backup was taken is lost when the backup is restored in an AS-P running in PCT. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause When the program is first initiated, the values for it is written to the database. If the “Program executions” Is turned off, the instance values the program had when the backup was taken is not read. Hence the values are set to 0.   On a real AS-P, a Cold start is performed after the restoring of the backup. When restoring a backup on an AS-P in PCT, one or two cold starts are done, followed by an additional warm start at least for the PCT 2. Resolution To get the instance values from the backup when it is restored, the “Program execution”/”Enable program” In PCT should be turned on before the restore is done.   Since a warm start is done for the PCT, the issue regarding Retain level vs. FB Backup property needs to be taken into consideration. Refer to Function Block Program - Retain Versus Backup

Issue There is no complete end-to-end guide on how to test SNMP alarms in EcoStruxure Building Operation (EBO). Existing documentation only covers creating SNMP alarms, not validating their functionality. Product Line EcoStruxure Building Operation Environment SNMP Notifications Cause Documentation provides steps for creating SNMP alarms but lacks instructions for testing and verifying alarm notifications. For general information regarding SNMP traps, refer to the following Web Help links: SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Follow these steps to test SNMP alarms in EBO: Install MIB Browser Download and install MIB Browser from iReasoning. Load Building Operation MIB File Download the Building Operation MIB file. In MIB Browser, go to File → Load MIBs, and select the Building Operation MIB file. Create and Trigger an Alarm in EBO Configure a simple alarm on a digital point in EBO. Ensure the alarm can be triggered manually for testing. Configure SNMP Notification in EBO Create an SNMP notification with the following settings: Address: SNMP manager IP (use localhost if manager is local). User Name: SNMP manager user credentials. In Filter Settings, select Normal and Alarm states. Add condition: Source server = * . Important: Open the SNMP notification object (double-click or press Enter) to access filter settings. Viewing properties alone will not display filters. Enable Trap Receiver in MIB Browser Navigate to Tools → Trap Receiver in MIB Browser. Trigger the Alarm Activate the alarm in EBO. Verify that the SNMP trap appears in the MIB Browser’s Trap Receiver window.

Issue Users need clarification on what happens when a Software Companion subscription is expired or approaching expiration. Key questions: What messages appear in EcoStruxure Building Operation (EBO)? Are email notifications sent to customers? Can expiration notices be silenced at the EBO front end? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation subscription licenses Cause The License Enforcement and Information page in Webhelp provides limited details regarding Software Companion subscription expiration behavior. Resolution 1. What messages appear at the EBO level? 30 days before expiration: A banner appears in EBO stating: “System license renewal date is approaching. Please renew.” After expiration: The banner changes to: “System license renewal date has passed. Renewal required.” 2. Are email notifications sent? EBO does NOT send email notifications. Software Companion notifications: Up to two designated Renewers per system receive email reminders at: 6 months 3 months 1 month prior to renewal date Within Software Companion: System status color changes as renewal date approaches Red indicates the renewal date has passed 3. Can the expiration notice be silenced in EBO? Users can temporarily hide the banner using the Hide button. Permanent removal requires applying a valid license (subscription renewal).

Issue There is no fully detailed explanation of how to install an SSL Certificate from an External Authority (CA) Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause When trying to install an SSL certificate from an external CA can fail Resolution Configure a DNS name for the AS/ES (This prevents the certificate from being locked down to a specific IP. I.E. Configure an A record for "AS_Name".com Purchase SSL Cert through a 3rd party, or use your organization's internal CA/ root CA Download and install OpenSSL or can use OpenSSL installed with EBO  Run Command Prompt as an administrator Use command "cd c:\program files\OpenSSL-Win64\bin Use OpenSSL to generate a CSR in order to obtain the certificate from the 3rd party openssl req -new -newkey rsa:2048 -nodes -keyout EcoStruxure.key -out EcoStruxure.csr Follow the prompts to fill out the information for the CSR Supply CSR, other certificate contact information, and a means of validating the request to the 3rd party CA Verify identity with CA (this may not be necessary if you use your company's internal CA/ root CA Receive host and intermediate CA certificates from 3rd party CA Make sure the CRT/CER files are in the C:\Program Files\OpenSSL-Win64\bin directory of Windows Explorer Use OpenSSL to convert the CRT or CER files into PEM files, as PEM is the only format EBO will accept openssl x509 -in certFileName.cer -outform PEM -out convertedCertFileName.pem Use OpenSSL to convert the private key file generated at step 6 from .key to .prv openssl rsa -inform pem -in filename.key -out filename.prv Run WorkStation as administrator In WorkStation, Control Panel > Certificates click on the server you are trying to add the cert to, either an AS or ES. Click on Manage Certificates > Add Existing  Put in a name for the certificate (it can be anything you'd like) Click the ellipsis next to host, intermediate, and private to add the appropriate PEM files and click ok  Select the newly added certificate from the drop-down and save the changes to activate Warm start the server After this process is completed, verify that connection to WebStation via HTTPS shows a secure connection/trusted certificate.

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) Cause It is often required that alarm notifications to be sent to multiple stakeholders simultaneously for timely response.   Best Practice: Use an email distribution list (DL) or group on your mail server and reference that DL address in EcoStruxure Building Operation. This simplifies recipient management and reduces maintenance overhead. Resolution   Open Email Setup in WorkStation (or Project Configuration Tool) > navigate to Notification > Configure Email. In the “To” field, enter multiple addresses using this syntax: user1@domain.com;user2@domain.com;user3@domain.com Separate addresses with semicolons ( ; ) and do not include spaces. Alternatively, select user accounts or groups to manage recipients dynamically. Ensure each user account exists on the BMS server and has proper alarm handling permissions. Configure SMTP settings (server, port, SSL/TLS, credentials) under right click  Server Properties > Email.   Choose how notifications appear: Inline email text, or As an attachment (TXT, XLSX, or PDF), with dynamic filenames if needed. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com If email delivery fails, Building Operation generates a system information alarm indicating SMTP issues. Recipient Limit Note: EcoStruxure Building Operation does not impose a hard limit on the number of email addresses in the “To” field. However, your SMTP server or email provider may enforce limits (e.g., Microsoft 365 allows 500 recipients per message; Gmail and ISPs have similar restrictions). To avoid delivery failures, use distribution lists or user groups for large recipient sets.

Issue After renaming a server, folder, or object, users may suddenly lose or gain access via WorkStation or WebStation. Access changes depend on the original permissions assigned to the user or group, and these permissions are not automatically updated following renaming. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES)  Building Operation Automation Server Premium (AS-P) Cause Permissions in EcoStruxure Building Operation are based on path names. When a Server, Folder, or Object is renamed, its path changes. Existing permissions remain tied to the old path—so users either lose or inherit permissions until these are updated. Resolution After renaming Servers, Folders, or Objects: Review all relevant Users and Groups in your system. Update path permissions to match the new names. Navigate in WorkStation to Control Panel → Account Management. Select the user or group, go to Software Permissions, and verify or adjust their assigned paths. Refer to WebHelp (Editing Path Permissions of User Accounts or User Account Groups - EcoStruxureWebHelp)  Validate effective permissions, ensuring they use the correct access levels: Read, Write, Create, Delete, Edit, Force, or Command. See also Relative Path Permissions. Refer to WebHelp (Assigning Relative Path Permissions to User Accounts or User Account Groups - EcoStruxure WebHelp)