Issue After updating the firmware on an SP-C-WEB controller via the web interface, the login page may fail to display the username and password fields, preventing access to the controller.   Login page Product Line EcoStruxure Security Expert Environment SP-C-WEB Controller Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This issue occurs when the login page web files are not properly updated during the firmware upgrade. Specifically, upgrading SP-C-WEB controllers from pre-cybersecurity firmware versions (4.00.1505 or earlier) directly to version 4.00.2402 or later can result in missing login fields. Resolution   Recommended Upgrade Path This issue has been addressed in version 4.00.2510. SP-C-WEB controllers can now be upgraded from 4.00.359 directly to 4.00.2510 or higher, eliminating the need for the previous staged upgrade approach. Upgrade to 4.00.359, if not already on that version Upgrade to 4.00.2510, or higher This ensures all necessary web files are correctly updated.   If the Issue Has Already Occurred If you've already upgraded to a version between 4.00.2402 and 4.00.2510 and cannot access the login page: A workaround is available. Please raise a Product Support case. Support will assist you via a remote session to restore access.

Issue The Security Expert SOAP service cannot be reached at: http://localhost:8030/SecurityExpertSOAPService/service.svc or https://localhost:8040/SecurityExpertSOAPService/service.svc   When browsing to the service URL, an HTTP 404 error is displayed. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause There can be confusion regarding how Windows indicates whether features are enabled. The Security Expert SOAP Service installation documentation shows a checkmark next to the required.NET Framework feature. A checkmark indicates that the feature and all associated sub-features are enabled. If only some sub-features are enabled, Windows displays the feature with a black square (filled checkbox) instead of a checkmark. This state is often misinterpreted as meaning the feature is fully enabled when it is not. Windows Feature Indicators To verify exactly what is enabled, expand the parent feature and inspect the child items individually. Indicator Meaning ☑ Checkmark Parent feature and all child features enabled ◼ Black square Partial selection. Some child features enabled, others not ☐ Empty box Feature disabled Resolution When a feature check box is shown with a checkmark in the documentation: Expand the feature in Windows Features. Verify that all sub-features under the parent feature are enabled. Do not assume that a black square (filled checkbox) indicates the same state as a checkmark. Ensure the feature state matches the documented configuration before installing or troubleshooting the SOAP service. All required sub-features must be enabled for the feature to match the documented configuration.

Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT, which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementations cannot process BACnet services such as RPM, COV, etc. Resolution GLOBAL Rules are implemented in versions where the first patches are applied, but then are deprecated when surfaced via Workstation, which is targeted for the next Major.Minor revision. When deprecated from service_blacklist, the trace log will show the event record of: Blacklist <feature> is no longer used. Setting available in BACnet Interface.   Feature Supported in Version Available in Workstation (deprecated) <ignore-unhosted-devices/> 3.2.3.9005 and higher (*) /BACnet Interface <disable-force-polling/>   <enable-force-polling/>   <restrict-backup-service/>   <evaluate-alarms-on-startup/>   <enable-execute-time-sync/>   /System/Interface Manager/BACnet <disable-mstp-fast-offline-detection/>   MSTP Network under BACnet Interface   Vendor/Model Rules For particular BACnet devices, the 'Vendor Identifier' and 'Model Name' are specified and must match exactly as shown in that device's Properties - Advanced Tab. Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <no-get-event-information/>   <no-broadcast-who-is/>     Users can create a rule in the BACnet interface to configure the BACnet Plug-in to avoid using the service. Some rules are global, while others can be for specific BACnet devices.    Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. It will also list a warning for Global Rules that have been deprecated because they are now available in Workstation.

Issue Users encounter problems assigning entitlement licenses to AS-B and AS-P controllers in EcoStruxure Building Operation (EBO) 2022 (4.0) and later using Device Administrator. Common symptoms include: Entitlement assignment fails. The assignment option is greyed out. No license product appears after the entitlement is added. "No valid license found" is displayed. The entitlement is visible in Device Administrator but cannot be assigned to the controller. A newly purchased license appears incompatible with the controller. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2022 (4.x) to 2024 (6.x) Device Administrator Building Operation Automation Server AS-P AS-P-NL AS-P-S AS-P-NLS AS-B AS-B-P Family Cause Starting with EBO 2022 (4.0), Schneider Electric introduced a scalable licensing model that decouples hardware and software. As a result, two different licensing models exist for AS-P and AS-B controllers: Older controller hardware requires an Upgrade License. Newer controller hardware requires a Bundle License. If an Upgrade License is purchased for hardware that requires a Bundle License, or a Bundle License is purchased for hardware that requires an Upgrade License, Device Administrator will not allow the entitlement to be assigned to the controller. This is the most common cause of entitlement assignment failures in EBO 2022 and later. Resolution Automation Server License Assignment Guide I cannot assign my AS-P or AS-B license Step 1 Find the Automation Server hardware part number from the controller properties or the controller label. Do not rely only on the model name (AS-P or AS-B). The required license depends on the hardware part number. ↓ Match your hardware to the correct license AS-P Upgrade Hardware SXWASPXXX10001 SXWASPXXX10002 SXWASPXXX1S001 Use an AS-P Upgrade License SXWSWASPUPxxxx AS-P Bundle Hardware SXWASPSBX10001 SXWASPSBX10002 SXWASPSBX1S002 Use an AS-P Bundle License SXWSWXBUxxxxxx AS-B Upgrade Hardware SXWASB24X10001 SXWASB24H10001 SXWASB36X10001 SXWASB36H10001 Use an AS-B Upgrade License SXWSWASBUPxxxx AS-B Bundle Hardware SXWASB24PX10001 SXWASB24HP10001 SXWASB36PX10001 SXWASB36HP10001 Use an AS-B Bundle License SXWSWXBBUxxxxx ⚠ License Mismatch If the purchased license does not match the Automation Server hardware, Device Administrator will not allow the entitlement to be assigned. Purchased the wrong license? If the entitlement has not been consumed or assigned, contact your local Schneider Electric Order Entry or Customer Care team to discuss returning the unused entitlement and purchasing the correct license. AS-P Hardware Compatibility Hardware Part Number Model Required License Type SXWASPXXX10001 AS-P AS-P Upgrade License SXWASPXXX10002 AS-P-NL AS-P Upgrade License SXWASPXXX1S001 AS-P-SMK AS-P Upgrade License SXWASPSBX10001 AS-P-S AS-P Bundle License SXWASPSBX10002 AS-P-NLS AS-P Bundle License SXWASPSBX1S002 AS-P-NLS-SMK AS-P Bundle License Examples of AS-P Upgrade License Part Numbers SXWSWASPUP30SA SXWSWASPUP30SD SXWSWASPUP30EN SXWSWASPUP30FU SXWSWASPUP40SA SXWSWASPUP40SD SXWSWASPUP40EN SXWSWASPUP40FU Examples of AS-P Bundle License Part Numbers SXWSWXBU0000SA SXWSWXBU0000SD SXWSWXBU0000EN SXWSWXBU0000FU AS-B Hardware Compatibility Hardware Part Number Model Required License Type SXWASB24X10001 AS-B-24 AS-B Upgrade License SXWASB24H10001 AS-B-24H AS-B Upgrade License SXWASB36X10001 AS-B-36 AS-B Upgrade License SXWASB36H10001 AS-B-36H AS-B Upgrade License SXWASB24PX10001 AS-B-24-P AS-B Bundle License SXWASB24HP10001 AS-B-24H-P AS-B Bundle License SXWASB36PX10001 AS-B-36-P AS-B Bundle License SXWASB36HP10001 AS-B-36H-P AS-B Bundle License Examples of AS-B Upgrade License Part Numbers SXWSWASBUP30SD SXWSWASBUP30FU SXWSWASBUP40SD SXWSWASBUP40FU Examples of AS-B Bundle License Part Numbers SXWSWXBBU010SD SXWSWXBBU050FU Example License Mismatch Controller Hardware: SXWASB24X10001 (AS-B-24) Correct License Type: AS-B Upgrade License Incorrect License Type: SXWSWXBBU050FU (AS-B Bundle License) Result: The entitlement will be visible in Device Administrator but cannot be assigned to the controller. Additional Information Original AS-P and AS-B hardware models require Upgrade Licenses even when running EBO 2022, EBO 2023, EBO 2024, or EBO 6.x. AS-P-S, AS-P-NLS, AS-P-NLS-SMK, and AS-B-P family hardware use the scalable licensing model and require Bundle Licenses. Refer to the latest Part Number Summary and Hardware & Software Matrix when purchasing hardware or licenses.

Issue The DALI Emergency Status Light object contains several status-related properties that are represented as an Integer value. Each Integer value corresponds to one or more status flags reported by the DALI device.   The purpose of this article is to provide a clear mapping between the Integer values and their corresponding flags for each DALI Emergency Status property. Product Line EcoStruxure Building Operation Environment Dali Expansion Module Cause DALI Emergency Status properties are reported as integer values that represent one or more status flags combined using a bitmask calculation. A single displayed value may therefore correspond to multiple active device conditions. Resolution The DALI Emergency Status Light object reports several status-related properties as Integer values. Each value represents one or more active status flags using a bitmask calculation. How to interpret a status value Identify the property being evaluated (for example, Emergency Mode or Emergency Status). Locate the corresponding flag table below. Compare the reported Integer value against the available flag values. Determine which flag values add up to the reported Integer value. The resulting flags represent the current state reported by the DALI emergency device. Example A device reports an Emergency Mode value of 10. Value Flag 2 Normal Mode 8 Extended Emergency Mode Because: 10 = 8 + 2 the following flags are active: Normal Mode Extended Emergency Mode Multiple flags can be active simultaneously, resulting in a combined Integer value. Light Information Value Flag 1 Control gear failure 2 Lamp failure 4 Lamp on 8 Limit error 16 Fade running 32 Reset state 64 Short address not assigned 128 Power cycle seen Emergency Mode Value Flag 1 Rest Mode 2 Normal Mode 4 Emergency Mode 8 Extended Emergency Mode 16 Function test in progress 32 Duration test in progress 64 Hardwired inhibit is active 128 Hardwired switch is on Emergency Features Value Flag 1 Integral emergency control gear 2 Maintained control gear 4 Switched maintained control gear 8 Auto test capability 16 Adjustable emergency level 32 Hardwired inhibit supported 64 Physical selection supported 128 Re-light in rest mode supported Emergency Failure Status Value Flag 1 Circuit failure 2 Battery duration failure 4 Battery failure 8 Emergency lamp failure 16 Function test maximum delay exceeded 32 Duration test maximum delay exceeded 64 Function test failed 128 Duration test failed Emergency Status Value Flag 1 Inhibit Mode 2 Function test done and result valid 4 Duration test done and result valid 8 Battery fully charged 16 Function test request pending 32 Duration test request pending 64 Identification active 128 Physically selected Validation After decoding the reported value, compare the active flags against the current device condition, including: Emergency lighting operating mode Test status Battery status Reported device failures or alarms Confirm that the decoded flags accurately reflect the observed state of the DALI emergency device before proceeding with further troubleshooting. Important Notes Each status flag is represented by a unique bit value. Multiple active flags are combined into a single Integer value. A higher value does not necessarily indicate a more severe condition. Always decode the Integer value into its component flags to understand the actual device status being reported.

Issue How to obtain an EcoStruxure Building Operation (EBO) evaluation license, engineering license, demo license, temporary license, or project license? This article explains where to download licenses for EBO 7.0 and later, as well as EBO 2024 (6.0) and earlier versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 7.0 and later EcoStruxure Building Operation 2024 (6.0) and earlier Cause   Users may be searching for "demo licenses", "evaluation licenses", "temporary licenses", "project licenses", or "engineering licenses". The terminology differs depending on the EBO version being used. EBO 7.0 and later uses Engineering Licenses, while EBO 2024 (6.0) and earlier uses Evaluation Licenses: EBO 7.0 and later Introduces the Engineering license, replacing previous demo or evaluation licenses. These licenses support system operation during the project phase without requiring commercial licenses. EBO 2024 (6.0) and earlier Evaluation license files remain available and must be downloaded manually. Resolution EBO 7.0 and Later — Engineering Licenses Engineering licenses can be downloaded from the EcoStruxure Power & Building Software Companion during the project phase. When the system is ready for commissioning or handover, you can convert Engineering licenses to Commercial licenses in the portal. No re-engineering or replacement of the license is required. Engineering licenses are valid for 6 months. They can be extended for another 6 months if required. WorkStation Pro demo licenses remain available for limited-time operation. Use commercial WorkStation Pro licenses for uninterrupted use. EBO 2024 (6.0) and Earlier — Evaluation Licenses Evaluation license files are available to BMS EcoXperts and Schneider Electric employees on mySchneider. Search for “Evaluation License” after logging in. The evaluation licenses are contained within the EcoStruxure Building Operation x.x Software package. The license files can be downloaded individually from within the software package.

Issue If folders are used under an Access Expert instance, errors similar to the following may be seen when the hardware list or view Live Monitoring views are refreshed.   An error has occured in the hardware document while trying to execute Refresh Product Line EcoStruxure Access Expert Environment Instances configured using Folders Grid Layouts Cause Folders within Access Expert instances have been deprecated and are no longer a supported configuration method. Environments that continue to use existing folders may experience issues when modifying objects or accessing folder-related functionality, which can result in Live Monitoring and Hardware List errors. Resolution Folders within Access Expert have been deprecated and are no longer the supported method for organizing objects within an instance. Schneider Electric recommends using sub-instances as the supported alternative.   While existing folder-based configurations may continue to operate, environments that still rely on folders can experience issues when modifying objects or accessing folder-related functionality. These issues may result in errors when refreshing the Hardware List or accessing Live Monitoring.   If the reported error persists after reinstalling the Access Expert client software and confirming all Access Expert components are up to date, the following workaround can be used to replace folder-based views with Grid Views.   For information about Grid Layout functionality, refer to: Using Grid Layouts to Filter, Group, and Search Data in Access Expert Workaround Open Live Monitoring. Enable the Include Child Folders option. This allows operators to view events and monitoring data without relying on folder-specific functionality. Create filters based on the existing folder names. Save each filtered view as a Grid View . Use the newly created Grid Views in place of the original folder-based views. Validation Confirm the workaround has been successful by verifying the following: Live Monitoring opens and functions without generating errors. The Hardware List refreshes successfully. Required events, monitoring data, and object visibility are available through the newly created Grid Views. Daily operational workflows previously performed through folders can be completed using Grid Views.

Issue Grid Layouts are the backbone of the Access Expert platform. They provide the interactivity of the lists and event views within the system. Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Operators may be unfamiliar with Grid Layout customization features used to filter, search, group, and display Access Expert data. Resolution This article provides an overview of Grid Layout functionality in Access Expert, including filtering, grouping, searching, customization options, and methods for saving and reusing layouts. Training Resources There are several Tech Talks compiled by Acre's training team available on YouTube that contain more detailed information: Filter Query Editor Reporting Features The Power of Grid Layouts Understanding Grid Layouts Grid Layouts can be found throughout the platform. The most common examples are Live Monitor and Event History, the People List, and Reports. What Makes up a Grid Layout The Grid Layout is composed of lines of data, a sorted column, and optional groupings or filters. The data in a grid layout will vary by page, the Event History and Live Monitor pages will events in the system and the people list will show the cardholders. The rows in these pages contain a new entry into the grid. This works similar to a spreadsheet in other programs. Each column then shows the pieces of the data contained in the row. Let's look at a row in the Event History for example. This is an Access Granted Event. Within this event, we have several columns of data including priority, reader, card number and person, etc. If you expand the event, by clicking on the "+" button, you will see a list of extra information that can be added to your grid view as a new column. Priority Filtering Additional filtering can be done by selecting the Priority Legend or by manually entering a specific Priority number. The priority numbers are assigned to events to indicate priority. When using the Priority filtering, the system will only return results for events and alarms for that priority number and higher. The overall range is from 0 – 255. Additional Priority Color ranges can be configured also and will be addressed in the Alarm Priority Defaults section. Time-Based Filtering Information is displayed based upon what you have selected for the time frame in the upper right. Simple commands such as 1D (day) or 1h (hour) can be entered in the cell and the window will automatically be updated accordingly. Time-based filtering includes" (m) for minute (h) for hour (D) for day (M) for Month (Y) for year Operators can also search based upon specific date ranges by selecting ‘Date Range’ from the drop-down menu. Video and Floorplan Integration From the Live Monitoring and Event History pages, operators can easily access integrated cameras when recorded video exists with the event and even automatically link to relevant floor plans. These are configured by: Linking to cameras or camera views: See the “Video Integration” Section. Linking to floor plans: See the “Creating Floor Plans” Section. Customizing the View Customizing the grid view allows for the creation of a custom report using the data within the grid layout window. The windows can be modified by the operator to only show relevant information by adding, removing, and resizing individual columns as well as exposing hidden information by using the “+” button as seen in the People List window. This example shows the Event Data for an Access Granted Event. The default view shows the Message, Reader, Card Number, and the Person. By expanding the event you can easily see that there is additional information on the event such as Facility Code, Card Expiry Date, Encoded and Displayed Card Number, and the Controller the reader is attached to. By clicking the blue "+" button to the left of the data, we can add in extra columns such as Floor Number and Card Expiry Date as shown above. These columns can now be used to group related data together. The Column Chooser can also be accessed by right-clicking on one of the column headers and selecting the "Show Column Chooser Option. This will open the column chooser window and allow columns to be turned on and off by checking the associated box. Checking the box next to the column will show the column and unchecking the box will remove it from the Grid View. The column chooser has default columns to start with of: Priority Alarm Status Instance/Folder Occurred On Floorplan Camera Message Reader Card Number Person Event Type Application Message Short When new columns have been added to the Grid view using the expanded Event Data view, those columns will show in the Column Chooser and can be removed by unchecking the box. Grouping Grouping allows the data grid to organize the data by an attribute. This can be grouping columns by date, or grouping events by Reader. To Group the data by a column option, left-click on the column you want to group by and drag it to the top of the window where it says "Drag a column header here to group by that column" (you will see arrows on the left-hand side of that section showing that you have the header in the Group Panel or right-click on the column and select "Group by this Column". Once a column is used to group the data, the data will reorganize into sections based on the column grouped by. You can layer the grouping by adding another column into the Group Panel. For example, you can group by the reader and then secondarily group by Occurred On to group each reader event by the day it occurred on.   Group Interval Within the Group Panel, the Occurred On column has an extra feature when grouped on. The Occurred On column can have a group interval set to determine how the information is organized. The Group Intervals are: None: This will use the base Occurred On structure to organize the data. This will differentiate each occurred on time by second. Day: This is break up the dates by the day they occurred on. The days will start at midnight local time to the machine being used to look at the data. Month: This will break up the dates the events occurred on by the month they occurred on. Year: This will break up the dates the events occurred on by the year they occurred. Smart: This will break up the data by the intervals of today, yesterday, earlier this week, last week, etc. This is similar to how many mail programs organize data. Filter Editor The Filter Editor allows for additional customization and advanced logic on the data being displayed. To access the Filter Editor, right-click on a column header and select "Filter Editor". The Filter Editor window allows for the editing of the logic applied to the window. This can be done by clicking on the 'And' in the top left corner and then selecting the operator (Or, NOT OR, or NOT AND). The drop-down menu allows the user to change the logic being applied. This will also allow the user to add a new Condition (new sorting/logic line) or a new Group (subsection of logic steps). Clicking on the Column (blue text) allows a different column to be chosen for the logic to be applied. The green text allows the modification of the logic on that column. Each column chosen will have different modifiers. "Instance/Folder" will have the "Begins with" sort, "Occurred On" will not have that option but instead will have the "DateTime Operators" option. The value is the object to be sorted/searched on. For example, searching on a given reader or given cardholder within the Event History. In the example below, we are applying the logic of only viewing events where the reader name begins with "1st" or contains "Warehouse"  in the name AND if the person is either Ruth Ewert or Wendy Ewert. If the desired effect is to isolate a singular piece from the data, say a singular reader, the opening the Filter Editor isn't necessary. Simply hover over the column header and clicking on the orange Key that becomes visible. Then select the singular object from the Filter Values list. The Filter Editor bar is then shown at the bottom of the screen and can be edited as shown above. The Filter Rules option at the top allows for the selection of a rule to filter on. Think "Starts with 2nd" to isolate all 2nd-floor readers. Counting Rows It is often important to know how many events are within a subsection of the events you're viewing. The standard method of counting rows will work but within the Group Summary Editor, there is an ability to check the box to Count Rows to have the Feenics application count those rows for you. To Enable Row Count: Right-Click on the sorted column Select the "Group Summary Editor". From that window click "Show Row Count" Click "Ok". The row count will now show on the right-hand side of the sorted rows. Searching Information can further be searched by manually typing in specific information such as a name, or number. In the example below, we are searching for 30 days of information for two criteria. Criteria 1 is “Karen” and criteria 2 is “4th”. The system will automatically present information highlighted in Yellow which matches both criteria. Additional items can be added by including a space between the items being searched for.   Saving Grid Layouts Once a view is built, it can be saved and reused later. To save a filtered view simply click “Grid Layout” then select “Save”. Once a name is applied to the Grid Layout it will automatically be saved for that operator.   Event Sources If the operator wants to search for a specific Event Source instead of the full system, then clicking the Filters option then selecting Event Sources will open a filtering window. This will open the Event Sources window where the operator can add sources by typing in the device name. Feenics will automatically present the operator with relevant items. Once completed select OK and the system will re-filter the Event or Live windows for information only on those new sources.  

Issue A customer wants to know how many connected devices are included in each EcoStruxure Building Operation system tier and how the tier selection affects licensing. Product Line EcoStruxure Building Operation Environment EcoStruxure Power & Building Software Companion Centralized Licensing System tier selection (Essential, Advanced, Advanced Plus) Cause Connected Devices are not included within any system tier. They are licensed separately and purchased based on the total number required for the system. Resolution The selected tier determines the software capabilities available on the site and influences the required part numbers. Connected Devices (CDs) are licensed separately from the Essential, Advanced, and Advanced Plus tiers. Purchase Connected Devices in packs of 10 according to the total number required for the system. System sizing should then be completed by determining the required Enterprise Central, Enterprise Server, Automation Servers, and Connected Devices. The EcoStruxure Power & Building Software Companion can be used to build the system and generate the appropriate part numbers and bill of materials.

Issue When attempting to use the Save To function to create a local AS-P backup, WorkStation displays the error message "Value does not fall within the expected range" and the backup cannot be saved. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server Cause The issue is related to the backup path stored in the WorkStation user profile, where the previously used save location is no longer available. Resolution Close all WorkStation instances and delete the contents of the following folder: %appdata%\Schneider Electric EcoStruxure\Building Operation\WorkStation After clearing the WorkStation profile data, reopen WorkStation and perform the backup again.  The issue is resolved if the backup completes successfully and no error message is displayed.

Issue After consolidating multiple Enterprise Servers into a single Enterprise Server, Automation Servers are moved from the original Enterprise Server to the new Enterprise Server. Existing bindings and references may be impacted during the migration process. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Enterprise Central (EC) Building Operation Automation Server (AS / AS-B / AS-P / AS-P-3) Multi-Server System  Cause When an Automation Server is detached from an Enterprise Server, Enterprise Server-to-Automation Server bindings and references are removed. This is expected behavior because those bindings depend on the relationship between the Enterprise Server and the Automation Server.   If the Automation Server is subsequently attached to an Enterprise Server with an identical structure, some bindings may reconnect automatically. However, automatic reconnection is not guaranteed and should always be validated after migration. Resolution When an Automation Server is detached from an Enterprise Server, any Enterprise Server-to-Automation Server bindings and references are removed. This is expected behavior because these bindings depend on the relationship and object hierarchy between the Enterprise Server and the Automation Server.   After the Automation Server is attached to a different Enterprise Server, any required Enterprise Server-to-Automation Server bindings must be validated and recreated as necessary. There is no option to preserve these bindings during the detach process.   If the destination Enterprise Server contains an identical binding structure, some bindings may reconnect automatically. However, this behavior should be validated after migration and should not be relied upon as part of the migration strategy. If the destination Enterprise Server has a different structure, bindings may be unable to resolve and recreation will be required.   To reduce recreation effort before migration: Export binding information where possible. Create binding templates. Use Find and Replace to update bindings where appropriate. Use Bindings Diagnostics before and after migration to identify unresolved or invalid references. Where Automation Servers communicate with other Automation Servers, validate all cross-server references after the migration and recreate any references that are no longer valid.   Useful references:  [1] Binding Template Types [2] Binding Templates [3] Find and Replace Bindings [4] Bindings Diagnostics

Issue A customer wants one WorkStation to receive alarms from a specific Automation Server and reject alarms from other Automation Servers.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WorkStation Building Operation Automation Servers  Cause EcoStruxure Building Operation does not provide a native workstation-level configuration that allows a WorkStation to accept alarms from selected Automation Servers while rejecting alarms from others. Alarm visibility is determined by system configuration, user permissions, and the alarm view being used. Alarm notifications are generated by the system and presented to the logged-in user based on the configured alarm views. Resolution Alarm visibility and delivery can be managed using alarm views, user permissions, notification recipients, or enterprise-level segmentation. Use Separate Alarm Views Create alarm views that are filtered by Automation Server or server hierarchy. Operators can use alarm views that display alarms from specific Automation Servers. Different WorkStations can use different alarm views based on operational requirements. This controls alarm visibility but does not prevent alarm generation. Use User Rights and Permissions Restrict operator access to specific areas of the system database. Operators with access limited to specific servers may not see alarms from objects outside their assigned scope. This is the closest native method for operator-specific alarm segregation in EcoStruxure Building Operation. Use Separate Notification Recipients When alarm delivery is required through email, SMS, or other notification methods: Configure separate recipient lists. Filter notifications based on alarm source, alarm class, or alarm category. Use Enterprise-Level Segmentation For larger systems: Assign different operator groups to separate branches of the system hierarchy. Use separate Enterprise Servers where complete alarm segregation is required. Additional Resources Alarms Pane and Alarm View Customization Alarm Filters Software Permissions Notifications Multi-server Systems

Issue There is a need to identify the Ports and URLs which must be open through the customer's firewall and network security for EcoStruxure Building Activate Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause To ensure the Flex Server operates correctly, specific URLs must be whitelisted within the customer's firewall and network security settings. Resolution Below is the list of URLs which must be open through a site's firewall/network: Domain Name Protocol Description telemetry.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Used for sending IoT Sensor Data streams. mender.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Used to download firmware update. emqx.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Used for communication of Flex-Server with Schneider Electric cloud services such as configuration, data, or alarms. openvpn.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Allows Schneider Electric to remotely access the Flex- Server through VPN. timesync.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Time server allows the Flex- Server clock to remain synchronized. router.ecostruxure-building-activate. se.app HTTPS (TCP port 443) Allows the Flex-Server to download linux updates. zen-mender-artifact-storage-eu.s3.eu-central-1.amazonaws.com HTTPS (TCP port 443) Used to download firmware update.   Note: For the list of URLs to be whitelisted for the India Portal, please refer to Required list of URLs/Ports to be whitelisted under firewall/network for EcoStruxure Building Activate (India Only) 

Issue Loop Explorer (LE2) configuration software showing license expired and all the options are not working (like transfer configuration). Product Line ESMI Fire Detection. Environment Loop Explorer 2 (LE2) Configuration software. Cause The LE2 software was unable to validate the current license status using the locally stored license information. Updating the license information from the licensing server restored access to the restricted functions. Resolution To update the Esmi Ultima Loop explorer configuration software (LE2) license credentials: Connect the PC running LE2 software to the internet. Open the LE2 software. Navigate to the Help tab. Click Update. In the update window, select the License tab. Review the displayed license login credentials. Click Check Now. The software will automatically check for an available license update and update the license information if required. Confirm that the license expiry message is no longer displayed and that previously unavailable functions, such as configuration transfer, can be accessed and used successfully. If the update does not complete successfully, verify internet connectivity and contact local Product Support for further assistance.

Issue Two separate Twisted Pair Adapter networks connected to separate AS-P controllers appeared to be cross communicating. When viewed with the Twisted Pair Adapter commissioning tool, devices from both networks were visible from either network. This resulted in RP-C controllers experiencing IP address conflicts and communication issues. Testing also showed that multiple adapters placed near each other could be detected even when no field wiring was connected. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server SpaceLogic RP-C Twisted Pair Adapter (TPAE) Cause The issue was identified on the 2-wire side of the Twisted Pair Adapter networks. The twisted pair network cables from two separate communication legs were terminated on adjacent rail-mounted terminals within the same control panel. Although the communication legs were not connected together, devices from both networks became visible on either network, resulting in RP-C controller IP address conflicts and communication issues. Resolution The communication legs were re-established and modifications were made to provide greater physical separation between the rail-mounted terminals. After these changes, the two networks reported only their respective field controllers and the cross communication issue was removed. Validation confirmed that each communication leg reported only the controllers expected on that network.

Issue An EcoStruxure Building Operation system using External Log Storage requires different retention periods for separate groups of trend data. The requirement is to determine whether different retention periods can be applied to different groups of trends and whether a single Enterprise Server can write trend data to multiple External Log Storage databases. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server External Log Storage Cause EcoStruxure Building Operation supports a single External Log Storage configuration per Server and does not provide functionality to assign different retention periods to different groups of trend data within that configuration. Resolution A single Enterprise Server cannot connect to or write trend data to two separate External Log Storage databases. EcoStruxure Building Operation does not support applying different retention periods to different trend categories within a single External Log Storage configuration. Possible alternatives include: Disable logging to External Log Storage for selected trends so that data remains only in local server trend storage, subject to configured local trend capacity.  Use dedicated Automation Servers for specific trends and configure those Automation Servers to use a separate External Log Storage database from the Enterprise Server. Use dedicated Automation Servers for specific trends without External Log Storage, storing trend data only in local trend storage. Investigate retention management directly within the External Log Storage database if the required trend data can be identified separately. This approach is outside standard EcoStruxure Building Operation functionality and should be validated by the customer. This guidance applies to External Log Storage architectures in general and is not specific to a particular database platform.   Validation: Based on the supported EcoStruxure Building Operation architecture, a single Enterprise Server cannot be connected to two separate External Log Storage databases, and different retention policies cannot be assigned to different trend categories within the same External Log Storage configuration. References:   Disabling a Log External Log Storage Overview Information Technology System Planning Guide Architectural Guidelines 7.1.1 and 7.1.2

Issue When adding an Enterprise Server (ES) to an Enterprise Central (EC), the following error is displayed:  "Cannot add a server to the system with an already existing unique ID" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause The Enterprise Server has the same Globally Unique Identifier (GUID) as another Enterprise Server in the system. The GUID is a unique identifier associated with the server configuration and database structure. An Enterprise Server that has been cloned may retain the original GUID, resulting in a duplicate unique ID within the system. Changing the GUID of an Enterprise Server by restoring a backup with new IDs is not supported due to system integrity and object referencing constraints within EcoStruxure Building Operation. Resolution Restoring an Enterprise Server with new IDs (GUIDs) is not supported. To create an Enterprise Server with a unique GUID: Set up a new Enterprise Server instance. Use the Export/Import feature to transfer supported objects from the existing Enterprise Server. Manually recreate any settings or objects that cannot be exported. Retaining Historical Trend Data If historical trend data must be retained when rebuilding the Enterprise Server, the following options may be considered. These options are outside supported migration procedures and should be validated before use. Option 1: Export and Import Trend Log Data/ Extended Trend Log Data (XML) Export trend log data/Extended Trend Log Data from the existing Enterprise Server to XML. Right Click on the Trend or Extended Trend log and select "View" and open it in "In Trend Log List" view.  When exporting, ensure that the configured record count includes the full history that must be retained. For example, if the export is limited to 500 records, only those 500 records will be included in the XML file.   The XML data can then be imported into the corresponding Trend log/ Extended Trend Log created on the new Enterprise Server. Please ensure that the newly created Trend Log or Extended Trend Log retains the same configuration and bindings as the existing Trend Log/ Extended Trend Log configuration.  Right Click on the Trend Log/Extended Trend log created on the new Enterprise Server and select "Modification" - "Import Log Data" and navigate through the pop-up and select the required exported "Xml file". This process must be performed for each trend log requiring historical data retention. Option 2: External Log Storage If External Log Storage is being used, a similar migration approach may be possible. Additional considerations may apply depending on how the external database is linked to the original Enterprise Server. Validation and testing are required to determine whether any dependencies exist that could impact functionality after migration. Option 3: Export Trend Data to CSV If the objective is to preserve historical data for reporting or analysis rather than maintaining the data within EcoStruxure Building Operation, trend log data can be exported to CSV and retained externally for use in applications such as Microsoft Excel or other reporting tools. Important Test the selected approach on a representative trend log before proceeding with a production migration. Confirm that the retained history remains accessible and meets site requirements. There is no documented or supported method for preserving historical logging data when rebuilding an Enterprise Server with a new Device ID. Any method used to preserve historical data should be validated by the customer prior to production implementation.

Issue Intermittent or failed communications on an ASD bus used with legacy I/A Series Network 8000 controllers. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium (pre‑EBO 2022; see Additional Information for later versions) I/A Series N4 Jace 8000 Cause Communication issues may be caused by: Unsupported or incorrect topology (e.g. passive tees) Segment length exceeding ASD limits or being reduced by protectors Incorrect or duplicate addressing Missing/incorrect biasing or termination Cable polarity errors or shield issues Electrical noise or transient interference Incorrectly configured or damaged repeaters Fiber attenuation or dirty connectors in fiber‑based segments Controller power or LED‑indicated faults Resolution Follow this structured checklist below and attached to diagnose ASD bus issues: 1. Verify Supported Topology Supported: Daisy chain, Active Tee (with repeater), Active Star (with repeater). Unsupported topologies—especially passive tees—can appear to work but lead to intermittent failures as RS‑485 transceivers age. 2. Validate Bus Length and Device Limits Max wire segment: 4000 ft, 24 AWG or larger Each GCMA‑131‑1 protector reduces allowable length by 500 ft Up to 5 repeaters in series Max 31 devices per segment, 128 devices total 3. Addressing Rules No duplicate addresses among same model controllers Different controller types may share the same numeric address (undocumented behavior) 4. Biasing Requirements Minimum 1 Pull‑Apart pair per segment Maximum 2 pairs per segment 5. End‑of‑Line Termination Install 120‑ohm EOL resistor at end of each wire segment 6. Cable Requirements 24 AWG+ shielded twisted pair, polarity observed Shields connected at each controller terminal 7. Transient/Lightning Protection Outdoor/inter‑building runs must use GCMA‑131‑1 lightning protector and 470 pF shield‑to‑ground capacitor Proper earth bonding required 8. Repeater Configuration RPTR‑WIRE: Jumpers set for ASD baud; EOL/PA configured based on topology RPTR‑FIBER: Use approved multimode fiber; maintain cleanliness; set optical power per installation instructions 9. Controller LED Diagnostics RED: Power/microprocessor health GREEN: Transmit YELLOW: Receive (solid ON indicates a fault such as shorted or reversed wiring)  10. Divide and Conquer Divide the trunk into smaller sections to isolate problematic devices or wiring. Additional Information – ASD Support in EcoStruxure Building Operation Support Removed in EBO 4.0 (EBO 2022) through 6.x ASD device support is removed entirely starting in EBO 4.0 (EBO 2022) and remains unsupported in 4.x, 5.x, and 6.x. Support Reinstated in EBO 7.0 (with restrictions) ASD support returns in EBO 7.0 under these conditions: A NETWORK 8000 Interface is required ASD devices must reside under the NETWORK 8000 Interface Servers hosting ASD devices must upgrade directly from EBO 3.2 to EBO 7.0 Intermediate upgrades (3.2 → 4.0 → 7.0) are not permitted and may cause system incompatibility or data loss

  Issue The FDP panel emits a continuous beep sound when powered on, and the display does not start. Product Line ESMI Fire Detection Environment FFS00703910xx (Esmi Sense FDP221) FFS00703920xx (Esmi Sense FDP252) FFS00703930xx (Esmi Sense FDP292) Warning Electrostatic Discharge (ESD) Precautions Required Always follow standard electrostatic discharge (ESD) precautions when handling internal components. Discharge static electricity from your person by touching a grounded metal surface before touching internal hardware. Failure to do so may result in damage to electronic components. Cause Based on troubleshooting and expert assessment, possible causes include: Loose or improper ribbon cable connection between MCU and display unit.  SD card issue at MCU unit. Potential firmware corruption or damage. Possible defective display unit. Main CPU not functioning properly. Resolution Perform the following checks to rule out common hardware connection issues: Ribbon cable connection Verify that the ribbon cable between the MCU and the display unit is correctly seated and securely connected. Refer to the image below for ribbon cable location and orientation. SD card installation Power OFF the panel. Remove and re‑install the SD card at the MCU unit, ensuring it is fully seated. Refer to the image below for SD card location. Jumper Placing Power OFF the panel. Verify that the jumper installed behind Display on PCB. Refer to the image below for ribbon cable location and orientation.   Note: If the panel continues to emit a continuous beep and the display does not start after confirming these checks, no further user‑level troubleshooting is recommended. At this stage, the issue may be related to firmware integrity, display hardware, or CPU functionality and requires further assessment. Contact your local Schneider Electric support team (Customer Care) and provide details of the checks performed and the observed symptoms to determine the appropriate next steps.

Issue In a multi-server EcoStruxure BMS system, users and user groups created on higher-tier servers are not visible on lower-tier servers. Examples include: User groups or users created in Enterprise Central (EC) are not visible on Enterprise Servers (ES). User groups or users created in Enterprise Servers are not visible on Automation Servers (AS). Bound values, such as users and user groups, cannot be selected across domain boundaries. Product Line EcoStruxure Building Operation Environment Enterprise Central (EC) Enterprise Server (ES) Automation Server (AS) Multi-server EcoStruxure Building Operation systems Domain-based security architecture Cause This behavior is by design. In EcoStruxure Building Operation, users and user groups are scoped to the domain in which they are created. Servers do not automatically expose user or group objects across domain boundaries, even when they are part of the same server hierarchy. A field server is aware of the Enterprise Server to which it belongs, and an Enterprise Server is aware of its Enterprise Central and field servers. However, visibility of users and user groups remains limited to the applicable domain. As a result: Users and groups defined in an EC domain are not directly visible on an ES. Users and groups defined in an ES domain are not directly visible on an AS. User and group objects are not intended to be visible across server tiers. Resolution Manage domains, users, and user groups within the appropriate server tier and domain. Recommended domain structure: Add Enterprise Servers to the Enterprise Central domain. Add field servers to the Enterprise Server domain. Manage users and user groups within the domain where they are intended to be used. Use domain membership consistently throughout the server hierarchy. This architecture ensures that each server tier manages its own domain users and groups locally. Limited visibility of user and group objects between server tiers is expected behavior and does not indicate a communication or replication issue.   If you are having issues with access not being accepted, see the following article User names and passwords configured on a Building Operation Domain are not accepted by the AS's   Webhelp Topics: Domains Multi-server Systems