Issue EBO 4.0.3.176 When trying to import anything (Custom type, Script Program, etc.), Workstation will crash immediately with an error stating "The path is not a legal form.". You cannot navigate to the location that the file will be imported from. It will generate a Workstation error after clicking import. The issue only occurs on Windows 11 machines.     Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The wrong file format might have been used Resolution When you select "import", WorkStation looks in the bin file for the last path used. If it finds a path entry it tries to use that path. If it can't find that path, it defaults to the users' Documents folder. In this case, there was no entry in the bin file, which means WorkStation defaulted to MyDocuments. For some reason, the MyDocuments path on that PC could not be parsed, and WorkStation crashed.   The resolution is to manually add an entry in the bin file (you can get the file from support), pointing to the user's desktop. That means, that when the user selects "import", it first tries to open the user's desktop, and when it succeeds, it never falls back to the MyDocuments folder.

Issue How many concurrent users can connect to the system Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause In the datasheet it is unclear how many concurrent users can connect to an AS without affecting performance Resolution The intent in the guidelines is to provide the concurrent user connections given that the clients are not all accessing data through the same Automation Server to the same Field Controller.  Therefore, if the load is distributed –  ES Clients viewing data from the ES (or a scattered variety of Automation Servers and below) AS Clients viewing data from that AS  Then it should be safe to add the client totals for all AS and ES clients together. The local AS connections are intended to help with scaled use of clients at a site-wide or multi-site system. The typical use case is for operators within a building, floor or tenant to connect locally to the AS, while central operators connect to the ES without impacting each other.  If all ES Clients and all clients on a single AS are all accessing data from that AS and below then the performance could drop below acceptable levels.

Issue Binding to a Graphic, what is the correct method? Product Line EcoStruxure Building Operation Environment Bindings Graphics Cause In the chapter "Binding Templates - Binding Values Using a Binding Template" in the "EcoStruxure Building Operation - Technical Reference Guide" it states "When creating bindings, follow the recommended general guidelines: create binding between Inputs and Outputs only, and do not create binding to Public Signals". Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Resolution Bindings from public signals to graphics is appropriate. When dealing with directional bindings (i.e. in from a schedule, out to an alarm, in from or out to another program, etc.), it's best to bind to input blocks or output blocks.  Graphics bindings are a different animal, though.  Among other things, they are bi-directional and only affect the system when the graphic is displayed.  They also exist to give the user access and control to values throughout the system (rather than to control routine data flow). Our primary reason for communicating this best practice is to help with the binding process.  Programs will operate with un-bound points, but we're encouraging users to simplify the binding process by relying on just inputs and outputs to interconnect a program with other logic and alarms.  In this way, you can visually scan the list of inputs and outputs to see which points still need to be bound. Since most programs typically have a much longer list of public signals, it's easier to overlook a missed public signal binding. Missed graphics bindings should be easier to catch but bindings to another program or alarm may be difficult to identify.

Issue Memory and System Memory in the AS Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause What is the definition of the two different memory types shown in the AS? It is not clearly defined in the documentation. In various places, one can see Memory and System Memory, or even add a column to show.  Resolution For the AS, System Memory is the RAM used by the AS Linux OS. The rest of the memory is what is being used for the processes, such as programs, trends, etc. Memory is the amount of memory consumed by the AS (nsp_servers application), system memory is that used by the Linux OS, however there is much debate about how this is calculated and allocated, so too much should not be read into this, it is there primarily for developers.

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue The port range used by the Project Configuration Tool is unclear Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The ports used by PCT are located in different documents Resolution • TCP on port 4444 (fixed) • HTTP on port 80 (default) • HTTPS on port 443 (default) • Server port 9091 (default) • Server port 9090 (default) • Engineering port 32768-61000

Issue Automation Server has license violation although correct embedded license is activated. ASBaseLicenseStatus has license violation status "inform"   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Adjusting the Automation Server time and date to an earlier time, ex. prior to license activation time, causes license violation. Resolution Make sure that Automation Server has correct date, time and timezone or configure the Automation Server to synchronize its clock with a network time server, refer to: Time and Time Zone Configuration in Automation Server.

Issue When trying to open WorkPlace Tech Editor the following error is shown in a pop-up window.   The following error occurred while trying to launch the WorkPlace Tech Ribbon Bar: The add-in could not be installed. Product Line EcoStruxure Building Operation, TAC IA Series Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause An installation of the Visio Ribbon has not closed correctly from previous use of WorkPlace Tech Editor or standalone WorkPlace Tech. Resolution Open the Add and Remove function in Windows Select "Program and Feature" Look for an instance of the SE.WorkStation.IA.VisioRibbon when no WorkPlace Tech Editor is running. Right-click and uninstall. Open Workstation and launch WorkPlace Tech Editor  There are other conditions that can cause the ribbon not to run as well.  They are detailed in other articles Similar Error Message Regarding Ribbon Bar  Unable to Load Ribbon 

Issue The "Display on alarm" feature for the Alarm view object does not display when the Alarm is triggered. This occurs even though the checkbox is checked, as shown below.    Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When the user is logged in with a Workspace view that does not show any Alarm viewers, no alarms are presented to the Workspace; hence the "Display on alarm" function does not load.  This is as intended. An example of this type of Workspace would be the Administration Workspace which presents no alarms to the user while they are using this Workspace. Resolution For the Alarm view to "Display on alarm", it is necessary to add the Alarm Pane to the Workspace (as shown below) or use a Workspace view with the Alarm Pane included.  

Issue When attempting to log into a server, the error message "Failed to establish connection with server" appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Servers Cause WorkStation is unable to make a connection to the desired server for one of several reasons. Resolution Unable to log into the Enterprise Server Verify that the Enterprise Server is running Go to Start Software Administrator Verify that the Server Status is Running. If it is stopped, then click the Start Service button, and click OK. Log into the server through Workstation. Lockout after restoring a backup set If an enterprise server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Unable to log into the Automation Server Verify the Ethernet connection Go to Run > cmd. Ping the IP address of the automation server. If it fails to communicate to the controller, verify that the ethernet connections are good and that there are no IT issues. Lockout after restoring a backup set If an automation server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Verify the IP address Go to Device Administrator  Connect to the Automation Server with a USB cable. Select the automation server once it is visible in the Device Administrator window and click on its name. Note: If the device indicates "Password Required," - Login into the automation server (default login is admin, and password is admin). Once the details open - Select the Ethernet 1 Configuration option and verify or enter the IP address details. After applying the information, enter this IP Address in WorkStation "Server" option to log on.  For further troubleshooting help see the following online help topic: Failed to Establish Connection

Issue The following record is seen in trace logs of EBO servers that have a BACnet Interface:   nsp.pin.BACnet.VariableProperty PollingVariableProperty: variable is a zomby!! Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server Cause A zomby variable is the BACnet plugin coming across an object that will be deleted but has not yet. Resolution No further action is required.

Issue There is a requirement to change the WebReport server name. Product Line EcoStruxure Building Operation Environment Building Operation Report Server Building Operation WebReports SQL Server Cause Changing the WebReports server name after the WebReports software has been installed, does not change the PC name references in the WebReports or the database. Resolution If possible, ensure that the PC name will not need to be changed after the PC has been configured for WebReports. If having configured a PC for WebReports, the PC name has to be changed, then backup all SQL data first then uninstall the WebReports software, ensuring that the following process is followed step by step. Below is an overview of the uninstall process, the exact details are shown in section 15.11 of the WebReports Reference Guide. 15.11 Uninstalling WebReports Complete the following tasks to uninstall WebReports and the WebReports database: Uninstall the WebReports application and services using Windows Control Panel Delete the WebReports database using Microsoft SQL Server Management Studio Delete the WebReports reports using SQL Server Reporting Services Report Manager Remove the virtual directories for WebReports and the WebReports service using Internet Information Services (IIS) Manager Remove the WebReports application pools using the Internet Information Services (IIS) Manager Delete the appuser and IUSR accounts (if they exist) using SQL Server Reporting Services Report Manager, Microsoft SQL Server Management Studio, and Windows Computer Manager. Please note that having uninstalled the WebReports software, follow the steps shown on the following Microsoft website: Rename a computer that hosts a stand-alone instance of SQL Server - SQL Server If this procedure fails then SQL Server should also be reinstalled after having changed the PC name first.

Issue Need to connect MicroNet system to EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause MN-Mi interfaces are obsolete, need to find another way to connect to EcoStruxure Building Operation system. Resolution A MicroNet system uses one of two communications protocols, Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet). If the protocol being used is NCP, the MicroNet LAN can be connected directly to the AS-P/ES, A MicroNet interface can be added and configured. If the protocol adopted is ARCnet, this does require the MN-Mi, to convert from RS 232 to ARCnet, the MN-Mi would be connected to the AS/ES using an RS232-485 converter. If the MicroNet controllers are the older 100 series version, it may be possible to remove the auxiliary ARCnet cards, and reconfigure the MicroNet controllers and LAN to use NCP protocol. If the MicroNet controllers are the 50 series type the cannot be re-confirmed as the communications components are on the main board. PA-00246 provides more information on the possible connections.

Issue With a Sigma 4.0.8 installation using a software license, when adding the entitlement ID to License administrator. The message “Unable to connect to "Server" is displayed. Product Line EcoStruxure Building Operation Environment Enterprise Server Sigma License administrator Cause When adding the Sigma entitlement ID to EBO License administrator, an internet connection is required to allow the license administrator to connect to the on-line licensing server. Resolution When a PC is not connected to the internet, and you need to activate a software license entitlement, an Offline Activation Tool is available, this can be downloaded here.

Issue Attempting to log in with WorkStation and receive the following license error: No license available. Error -83: Version of vendor daemon is too old The following error is seen in System Log / Trace log:  Error Code: -83 Error message: Version of vendor daemon is too old Building Operation Software Administrator Product Line EcoStruxure Building Operation. Environment Building Operation License Administrator Building Operation License Server Cause The most common cause is that the License Server is older than the current release of Building Operation software.  This occurs during upgrades and if the License Server used for the product has not been upgraded.  Ensure both components of the License Administrator are selected (as shown below) when performing the upgrade/installation.     Resolution To confirm the issue open the Windows Services and check that the version shown in the services is valid for the products installed.  The version shown should be at the same version or higher than the other Building Operation software installed.     To resolve the issue, upgrade the License Server component of the License Administrator installation software. 

Issue When being discovered by a 3rd party system what names will be seen? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS-P, AS-B, AS) Cause How is an Enterprise Server or Automation seen by a 3rd party system? Resolution The Enterprise Server (ES) and Automation Server (AS) conform to a specific BACnet Protocol Revision depending on version and firmware and the capabilities of a particular BACnet implementation are described in the Protocol Implementation Conformance Statement (PICS).  The PICS contains, amongst other details, a list of all standard and proprietary object types that are supported.  Please see BACnet Testing Laboratories (BTL) for a Listing of Tested Products.    For each object type supported the PICS describes: any optional properties that are supported which properties can be written-to using BACnet services if the objects can be dynamically created or deleted using BACnet services any restrictions on the range of data values for properties For a third party to discover an ES or AS it needs to be a BACnet Operator Workstation (BOWS).  Please see BACnet Testing Laboratories (BTL) for a list of tested BACnet Operator Workstation (B-OWS) and BACnet Advanced Operator Workstation (B-AWS)   Of the objects types detailed in the PICS the specific BOWS will determine what properties are shown.  An application such as YABE can provide an indication of these properties.  For example with a device the Vendor Name (1), Protocol Revision (2), Object Name (3),  Model Name (4) and Firmware Revision (5) are amongst the properties available. For an object such as an analog point the Object Name (6), Present Value (7) and Object Identifier (8) are examples of what will be seen.    Every BACnet device contains a device object that defines certain device information, including the device object identifier or instance number.  For additional information please see Introduction to BACnet.  

Issue Automation Servers are being connected to an IT managed network. The network requires that devices broadcast their MAC address in order to be added to the network switch. Automation Servers are not broadcasting their MAC address to the switch  and cannot be added to the network Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause A stand alone AS-P server with a fixed IP address does not send out anything on the IP network. Resolution If you need the AS-P server to send out some traffic, you could define an NTP server that generates traffic when synchronizing the time.

Issue When opening a dashboard graphic, the system operates very slowly.  Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.  Product Line EcoStruxure Building Operation Environment Building Operation 3.2.3 and higher Building Operation Automation Server Bundles (AS-B) Building Operation WebStation  Cause Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.   Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available. Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation. Resolution Below are some considerations to look at improving the overall performance when dealing with this issue: Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000) Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.    If large storage is necessary, then create or use different logs for display within the Dashboards widgets.  If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount. Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.        

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location. Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix. Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2.3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6.1  1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1  1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1 1.9.x  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0 3.1 6 3.1.19319.1 4.6 Not commercialized  - (n/a) 2021 3.2.3 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2022 4.0.2/2022 6 Integrated - (n/a) 4.8   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems. (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community)

Issue There can be confusion on the differences between EcoStruxure Energy Expert (formerly Power Manager) and EcoStruxure Power Monitoring Expert (PME)  Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Building Operation  EcoStruxure Energy Expert (formerly Power Manager) EcoStruxure Power Monitoring Expert Cause Power Monitoring Expert (PME) is a long-established product in the Schneider Power (EMS) offer and so its place in the market is well known and its support path is very clear. Energy Expert is a much newer offering that intentionally sits nearer to EcoStruxure Building Operation (EBO) in the BMS community, while still remaining an EMS product and so its place in the market and support path is more easily confused. Resolution Definitions   EcoStruxure Power Monitoring Expert (PME) Schneider Electric's supervisory software dedicated to power monitoring that enables you to maximize operational efficiency, optimize your power distribution system, and improve bottom-line performance   EcoStruxure Building Operation (EBO)  Schneider Electric's premier building management system (BMS) providing integrated monitoring, control, and management of energy, lighting, HVAC, and fire safety.   EcoStruxure Energy Expert (EE)                                                    Designed to offer Power Monitoring Expert (PME) features to new and existing EcoStruxure Building Operation (EBO) projects, giving extra capabilities to manage power utilization in a BMS environment.   It utilizes EcoStruxure Web Services (EWS) to be able it to share data between the two EcoStruxure software platforms. (EBO and EE) and applications such as the ETL Tool and the Integration Utility in the integration process.   EcoStruxure Web Services (EWS) The Schneider Electric standard for sharing data among various Schneider software platforms to facilitate the creation of EcoStruxure Solutions. Based on conventional Web Services technology (SOAP, WSDL)   ETL Tool The function of the ETL is to extract select historical data (Trend logs) from EBO, and load that data into the Energy Expert SQL database for use in Dashboard and Reports etc.   Integration Utility The function of the Integration Utility is to export Energy Expert Dashboards, Reports and Alarms for import into EBO to enhance its Power Offer to the customer   Product Support Path: PME, Energy Expert, ETL and the Integration Utility are are all fundamentally Power Products and so should always be raised through your local Product Support Team (via your Customer Care Center (CCC)) under an EMS commercial reference. However in cases where an Energy Expert project needs specific assistance with the EBO side of the integration then a BMS commercial reference should be used instead.