Building Automation Knowledge Base

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 Not commercialised - (n/a) 2023 5.0/2023 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) New PME 2023 now offers EWS Client 1.2 which can be used to transfer data from EBO to PME instead of ETL.  The merits for and against using this new EWS Client rather than ETL are discussed at length in the PME 2023 System Guide

Issue While trying to login to either WorkStation or WebStation, or during the startup of the Enterprise Server, an error "Error -25: License server system does not support this version of this feature." appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 2.0.x or later Building Operation Webstation version 2.0.x or later Building Operation Software Administrator version 2.0.x or later Cause The activated license is not at an appropriate version for the corresponding software. The licenses activated in the EBO License Administrator need to be at a version greater than or equal to the version of the Building Operation software being used.  Resolution 1. Workstation - If the Workstation license activated in License Administrator is at Version 1, this license will need to be upgraded to be compatible for any system EBO 2.0 and beyond. To do this, simply notate the Entitlement ID and then return the Workstation License. Once returned, reactivate the license from the previously recorded Entitlement ID. This will upgrade the 1.X License to be used with newer systems. 2. Enterprise Server - If the error is received on an ES, verify that all ES licenses are in place. If the system was upgraded, it is necessary for all previous versions of ES/AS licenses to remain activated in the License Administrator. 

Issue Need to edit StruxureWare Building Operation Reports Product Line EcoStruxure Building Operation Environment SmartStruxure Report Server Report Builder 3.0 Cause Users wish to directly edit or create customized versions of existing reports. Resolution Open Microsoft Report Builder In the Menu, Select Options Change the database path to "http://localhost/reportserver_SQLEXPRESS' Where localhost is changed to the PC name or IP address and SQLEXPRESS is changed to the installed instance of SQL Click OK You can now open existing files on the server and save new files directly to the Reports Server. You must Synchronize the StruxureWare Reports Interface for newly published reports to be available from the StruxureWare Interface.

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue Need to use a controller that has no BACnet functionality due to network security limitations on site. Environment Continuum bCX1-CR-INF (bCX9640) Cause A customer has a site with restrictive network security requirements and BACnet devices (or any other open protocol) are not allowed. Resolution The bCX9640 is an Infinet protocol controller only. This version of the bCX firmware does not have the BACnet stack installed, and there are no BACnet points able to be created in this controller. You will be fine to use this controller where BACnet support is not required or allowed.

Issue When trying to activate an embedded license on a SmartX Server using Device Administrator, the activation fails with the following error message: Failure (error) received when reclaiming an embedded license on an Automation Server   "Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created." Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) All of the above v. 3.0 or higher Cause The cause of this problem is that the trusted storage, i.e., the embedded license database on the SmartX server, is corrupt. The embedded licensing framework undertakes internal checking and if it determines there is a consistency problem, it will consider the trusted storage to be corrupt. This means that no operations to the trusted storage, such as activating licenses, will succeed. At the time of writing, it is unclear why the consistency problems happen. In the server log, you may also observe the following error message: 10:08:06: Executing licensing command 10:08:06: Executing embedded operation: Activate ActivationID: ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX 10:08:11: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created 10:08:11: Licensing command completed 10:08:11: Activating licenses failed (Real Activation ID replaced with ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX)   Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the steps shown in the resolution. Please attempt all steps before contacting support.   Resolution   Building Operation 2022 v4.0.4  and above Upgrading to the above versions will now resolve the trusted storage corruption and inhibit license activation. Building Operation 3.2.X and up to EBO 2022 v4.0.3   Note: Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the below steps. Please attempt all steps before contacting support.    Clear trusted storage within the server Using Device Administrator select the affected server and Open a PuTTY Console An alternative way of connecting to the server is to use WinSCP. Use File protocol SCP and the admin user. When connected, follow the instructions as per the Word Document also attached below Warm or Cold Start the AS-P If failures still occur, attempt the Offline Activation of Licenses Workflow; The key step is that the license is activated offline and then transferred to the server in two different steps, allowing the license activation process to complete successfully.   Warm or Cold Start the AS-P If there are still failures with either of these options, send a support request through your local support center including the errors seen with each activation attempt.     Building Operation version lower than 3.2.X   If the embedded license is a Client license, there is no need to activate the license. Install the EBO Hotfix 3.0.3.2001 (CP1) or later. This will remove the enforcement of SmartX server Clients in the licensing system. See also article Embedded WebStaion client license when logging directly into a SmartX server no longer needed. Other licenses like SmartDrivers, SNMP, and Personal Dashboards may still need to be activated. Contact your local support center to fix this problem.

Issue How many client licenses are currently used? Which host is using the licenses? Product Line EcoStruxure Building Operation Environment Licensing Cause Information about license usage is needed to ensure licensing is adequate. Resolution Information about current license usage can be found in the FlexNet License Administrator found on the server where the Building Operation License Administrator is installed. FlexNet License Administrator has a web interface accessed through a web browser. The address is the server address and port 8888. If on the license server go to: http://localhost:8888 If on a remote machine to access the FlexNet License Administrator go to: http://[license server ip address]:8888 Once accessing the FlexNet License Administrator, switch to the Concurrent licenses view by clicking on the Concurrent icon. Scroll down to the client.station in the Feature column. The column In Use (Available) shows the number of client licenses used. (The number of client licenses available is displayed in parentheses). (Click on Hosts to display a list of hosts taking client licenses.)

Issue After importing a new template into AET, the different folders and objects are all different colors. What does each color represent? Product Line EcoStruxure Building Operation Environment AET Folder View Cause Each color indicates a different status for the object. Some must be resolved before proceeding and others are information only. Resolution Below is the list of the different status colors and their meanings:  Red – Duplicated object. This must be corrected. Green – Existing folder. Orange – Folder with duplicated object below. Black – New object or folder. Blue – Existing object in EcoStruxure system tree Brown – Device that will be created automatically by AET Light Blue – Empty IO Channel

Issue A license violation alarm is shown in the alarm viewer even though the system has all licenses necessary. The alarm returns to normal without any action from the operator. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Enterprise Server / Central contacts the License Server installed on the computer to determine what licenses are available. The License Server will then contact the "Trusted Storage" on the computer which is created when activating the licenses and ask how many licenses are available. The issue comes when the "Trusted Storage" creates some metadata once a day.  The metadata is a file created showing which licenses are used at that moment.  This is not currently used but could be by a third-party client who is interested in the license information for the system.  When the "Trusted Storage" creates the metadata it will be busy and not answer the License Server.  This is when the license violation alarm will be activated.  The alarm will return to normal after the "Trusted Storage" has finished creating the metadata. Resolution An investigation is ongoing. This issue has been fixed in EBO 2022. Please refer to License Violation Alarm 

Issue Does Security Expert support HTML graphics? Product Line Security Expert Environment Security Expert Cause Continuum transitions, INET transitions, and greenfield sites require HTML graphics Resolution The Security Expert software v4.2.259.19 and previous builds do not support HTML graphics.

Issue Windows update KB4519976 causes all Xenta servers to go offline in TAC Vista every few minutes. Product Line TAC Vista Environment TAC Vista Server Microsoft Windows 7 or Microsoft Windows 2008 Server Xenta 500 Xenta 700 Xenta 900 Cause After the Windows update, KB4519976 is installed, the SSL handshake behavior is changed. This affects TAC Vista and its communication with the TAC Xenta server. Resolution There are two workarounds available at the moment. Solution 1: Uninstall Windows update KB4519976 Solution 2: Turn off SSL for the communication between TAC Vista and the TAC Xenta server using the registry setting shown below. This means that only the login will be encrypted when TAC Vista is communicating with the TAC Xenta servers. Run the utility TacosTweak.exe, located in the program folder where TAC Vista is installed. Set "Only use SSL for login to TAC Xenta Servers(5xx/7xx)" to 1 to run the communication between TAC Vista and TAC Xenta servers without SSL. Restart the TAC Vista server for the changes to take effect.

Issue While moving a SmartX Controller from one AS-P to another, there is an error stating "The following devices appear to be hosted by another server. In order to host them, you must first right click the device and select 'Clear host information' ".   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation IP-IO Building Operation Room Controller Cause SmartX controllers can only be hosted by one automation server at a time. Resolution Use the Device Discovery tab in the AS-P Once the MP is found, right-click on the device Select clear host information    

Issue Need to replace discontinued Erie actuator model AH13U020-Z but unsure if the current model AH13U020 can be used as a direct replacement Product Line Field Devices Environment Erie actuators Cause Unable to find any documentation for the AH13U020-Z Resolution The '-Z' models for the Erie actuators indicates it is the Made in China version of the actuator. We have since stopped manufacturing the actuator in China.  The AH13U020 can be used to replace the AH13U020-Z

Issue Workplace Tech or Workplace Tech Editor is crashing when accessing a specific Visio file. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Cause There are a number of possible issues with the Visio 2013 and Visio 2016 files when running in Compatibility Mode.  Compatibility Mode is required for Workplace Tech and Workplace Tech Editor since they are both designed to use the older .vsd file format.  The mentioned Visio versions both use .vsdx as a native file format. Resolution

Issue Some connectors appear in red on the Workplace Tech Visio drawing.  Connectors cannot be bound to objects. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Microsoft Visio  Cause Drawing objects become placed off the normal boundaries of the Visio drawing page causing file corruption.  This can occur during improper file saves, Visio crashes or for unknown reasons. Resolution

Issue When adding Shadow Schedule in AS, it isn't synchronized with the Lead Schedule in ES. This issue only happens when  there is an Exception schedule assigned with another Calendar added to the Lead Schedule in ES. Error: "cannot verify lead object status" Product Line EcoStruxure Building Operation Environment SmartStruxure Lead and Shadow Cause If a Lead Schedule contains an Exception with another Calendar assigned in ES, and a Shadow Schedule needs to be pointed to this Lead Schedule in AS, both the Shadow Calendar and Shadow Schedule need to be created and pointed to corresponding Lead Calendar and Lead Schedule. If only Shadow Schedule is created, it will fail to update to Lead Schedule, or even wipe the original setting with a blank schedule. When involving Calendars the following should be considered: The only way that the lead and shadow relationship can be maintained where calendars are concerned is where the calendar has the same name and is at THE SAME RELATIVE PATH as it does with respect to the lead schedule. Consider the following examples: Example 1 - Lead Schedule is at Root and Shadow Schedule is at root and Referenced Calendar is at root. - under these conditions there is only a need for one Calendar object. The Lead Schedule has an exception that references the calendar at the root and everything works great. Example 2 - Lead Schedule and Referenced Calendar are in Folder 1 and Shadow Schedule is in Folder 2. This will not work because the Shadow Schedule is trying to reference a calendar at the same relative path, i.e., in Folder 2, and there is none there. Example 3 - Lead Schedule and LEAD Referenced Calendar are in Folder 1 and Shadow Schedule AND SHADOW CALENDAR are in Folder 2. This will work fine. In simple terms keep the names and paths within the ES and AS consistent (the same) to avoid issues. Resolution Before the steps below, ensure the communication between AS and ES is OK. Refer to Binding between ES and AS or two AS shows Unresolved and Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server. If the communication is fine, continue to the following steps: Create Lead Calendar and Lead Schedule in ES, and assign the Lead Calendar to the Exception of Lead Schedule (Should already done before). Create Shadow Calendar and Shadow Schedule in AS, and point them to corresponding Lead Calendar and Lead Schedule in ES. Now the Shadow Calendar should be able to synchronized with the Lead Calendar after changes have been made to the Lead Schedule.

Issue How can the size of a program (Lua Script) be seen? Product Line EcoStruxure Building Expert Environment Site with MPM Cause What size is the program? Resolution The size of the script is the size of the exported as a txt file. For a graphical script, convert the graphical script to text format (ignore warning but do not save script otherwise you will lose the ability to edit your graphical script) then save it as txt file. Lua Program Information The CFG1 object of any given Manager can provide detailed information on the average execution time of all the Lua processes in the system (in milliseconds), along with their memory usage and available memory (in bytes). The "Max Size" will never change, since 16MB are always reserved for the Lua tasks. But the "Size Used" is a good indicator of how much memory is currently being used by the Lua tasks. Note that approximately 8MB are used by default. So anything above 8MB will represent the custom Lua programs current memory usage. The "Avg. Execution Time" is the most interesting value. It represents how many milliseconds it took for all Lua programs to complete. When the system is empty (no scripts, no trend logs, nothing) the value should be below 100ms. An average load would be around 500ms and an overloaded system will take above a second (1000ms) to complete all of its tasks.

Issue Unable to open servers in PCT from Webstation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The incorrect IP address or ports used in the browser. Resolution Select the server from a project. Expand the Properties tab from the right-hand sidebar Record the Engineering IP address and HTTPS port number Open a browser and enter "https://{IP address}:{port}" or ""http://{IP address}:{port}"  

Issue When using Advanced Display and logging in to Webstation, it startups in kiosk mode with limited functionality. Example:   Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display Cause When running Webstation in Advanced Display it is by default started in kiosk mode Resolution Open SmartX HMI Kiosk in Advanced Display In "Webstation setup" delete the part ?kiosk# Example: https://192.168.42.116/?kiosk#  Webstation be started in kiosk mode https://192.168.42.116/  Webstation will start normally

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue PCT utilizes a large volume of hard drive space when the backup limit is not set. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The virtual machine reserves additional hard drive volume each time a backup is created. Once this space has been allocated to the VM’s hard drive, it can not be reversed without deleting, recreating the project server then restoring the station from a backup.  (Once a VM grows, it cannot shrink.) Resolution The number of backups should be limited to a maximum of two (2).