Building Automation Knowledge Base

Issue It has come to our attention that people are using Backup and Restore to duplicate Automation Server databases, this is not supported and should not be used as it results in various issues.  Some of the known issues at this time are listed below: When attempting to update Server IP addresses using the advanced feature "Repair server communication"; one or more Automation Servers are listed as Offline even though they are shown as Online within the System Tree. (Click on image for larger view)   When performing a backup / restore from the Enterprise Server the Automation Server(s) are not listed as part of the Child view.    Right-clicking on the Automation Server does not give all the options available and most are grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server 1.2, 1.3, 1.4 and 1.5 Cause This situation arises because each Automation Server receives a unique identifier, global unique identifier (GUID), when using the backup and restore function this GUID is retained.  Therefore when restored to other Automation Servers these will retain the same identifier.  The only course of action available within this environment is to detach the Automation Server from the Enterprise Server and create a new database from scratch. The correct duplication process across Automation Servers is to use the export and import feature or copy and paste (drag and drop) across Automation Servers.   Resolution StruxureWare Building Operation 1.6 and above update:   You can now use the Restore function to re-use the configuration data from a backup set in a new standalone Automation Server. Rather than manually configuring your preferred Automation Server configuration, you can save time and configure the standalone Automation Server from a backup set. Online help topic: Duplicating an Automation Server Using Restore Backup and Restore feature should NOT be used to duplicate multiple Automation Server's databases it should only be backed up and restored to the same server.  Instead the Export / Import and copy and past features are designed for this function.   A warning note in the Technical Reference and IT Reference guides (versions 1.2, 1.3, & 1.4) has been added warning the users not to use the backup and restore function for duplication.  See the online StruxureWare WebHelp for this current Important Note (login required): Backup and Restore Overview However if you have this situation then it may be possible to recover some or most of the database, please contact Product Support and reference this article number so that this issue can be confirmed.  

Issue Need to know what different system alarms can occur in EcoStruxure Building Operation?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause System alarms are alarms built into the system, such as "IO module offline" or "Server offline". In EcoStruxure Building Operation, over 230 system alarms exist. Resolution For all system alarms check WebHelp article: System Alarm ID Enumerations

Issue The Automatic Logoff feature is available in version 1.4 and higher. Starting in version 1.5, there is a default automatic logoff time of 10 minutes in both Workstation and WebStation for the Administrators user group. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation WebStation Cause To prevent unauthorized users access to the system the automatic logoff feature has been added to SBO/EBO. The default Administrators group is set to automatically log off of both Workstation and Webstation after 10 minutes of being idle. This setting cannot be changed for the Administrators group. Resolution The automatic logoff function makes it possible to decide when a user is automatically logged off after a specified time of inactivity. Inactivity means that no user initiated activity is ongoing, that is, no action has been made using the mouse or the keyboard. However, if a user has initiated a big operation in Workstation, for example an import or a large copy and paste, the user is still considered to be active as long as the process is ongoing in Workstation. This is to prevent loss of data. The automatic logoff function is used for security reasons and it also prevents that a Workstation user occupies a license when inactive. The automatic logoff time is set at User Group level and is always defined by the group that has the longest automatic logoff time. For example, if a user belongs to two groups, one group has an automatic logoff time of 5 minutes and the other group has an automatic logoff time of 15 minutes, the user is automatically logged off after 15 minutes. If a user belongs to a group that does not have the automatic logoff function enabled the user will never be logged off. Note: When a user is logged off by the automatic logoff function all settings that are not saved are lost.   Creating a new user group so the Automatic logoff time can be adjusted Starting in version 1.5, in order to change the duration of time before the automatic logoff occurs or turn it off a new User Account Group must be created. Follow the steps below. Go to the Control Panel in Workstation. Click on Account management. Click Add under the User Account Groups section. Name the new User Account Group. Click Next. Select the Users to add to the new group and then click the right arrow to move them to the "Selected User Accounts" window. Click Next. In the same method as step 4, select the Workspace to add to the new group and move it over to the "Available Workspaces" window. Click Next Set the group policies for the new group taking note of the Automatic logoff time which can be set to "Never" if desired. Click Create.   Changing the Automatic logoff time of an existing user group In the System Tree under System > Domains > Local > Groups, select the user group and click on the "Policies" tab. Here the Automatic logoff time can be changed and then click the save button on the tab at the top of the window.

Issue Alarm window either does or does not display on alarm as desired Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Alarm View Properties are not set correctly Resolution Right Click in the Alarm View window and select Alarm View Settings>Properties Change the Display on Alarm Property to the desired state.

Issue Audible alarms not sounding when there are active alarms. Workspace has multiple tabs for graphics navigation and a tab for Alarm View. If a user is not on the alarm tab when an alarm is activated, the audible alarm is not heard, and the user does not know that an alarm has been activated. The audible alarm works when the user navigates to the alarm tab.  Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Cause The Workspace content does not have an Alarm Pane added.  Resolution Edit the Workspace to add an Alarm Pane to the Workspace content. If the user does not wish to display the Alarm View due to screen space etc., configure the Alarm Pane Default visibility to Hidden.  Note: Audible alarms are available in WebStation from 3.2 onward.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Enterprise Server or Enterprise Central Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Within the Enterprise Server and Enterprise Central logs are many records that are logged as a part of normal operations and unexpected events. Resolution Collect ES and EC Logs via EBO Workstation: Refer to the Workstation section of KB article: Collect logs from an Automation Server Collect ES and EC Logs via Windows Explorer, especially if ES or EC will not run as a service or keep crashing: The ES or EC database path is listed in Software Administrator.   For Windows 7, Server 2008, or higher, the default paths for the logs folder are: Enterprise Server: C:\ProgramData\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise Server\db\logs Enterprise Central: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation [n.n]\Enterprise Central\db\logs In EBO V3.2 or higher, shortcut buttons can be found in Software Administrator to go to the folder for logs and database directly.    By default, the "Program Data" folder is hidden, so Windows needs to be configured to view hidden files and folders. For Windows 10 or 11, open Windows Explorer and select View > Show > Hidden items. For other Windows versions, please refer to this Microsoft help article: Show hidden files (microsoft.com). Using Windows Explorer, Navigate to the ES or EC logs folder to find System and Trace logs. Copy the Logs folder contents and send them to Product Support as a compressed file if required. To open a log file, Right-click on one of the logs and select Open with... Expand the window and select WordPad. For Windows XP:   Other ways to review site-specific issues: Is the issue site-specific regarding workstation being used or applications/programs running on these machines? Always try to keep the programs on a workstation to a minimum. Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes - Communities Make sure that PCs and Windows OS used for WorkStation, ES or EC meet the requirements mentioned in Information Technology System Planning Guide (se.com) Make sure that the firewall and antivirus are correctly configured, and required ports are open for EBO, as explained in Information Technology System Planning Guide (se.com) Make sure that the current installed EBO version is supported, as per the Software Support Policy for EcoStruxure Building Operation - PA-00300. Check if Microsoft currently supports the installed Windows OS: Lifecycle FAQ - Windows | Microsoft Docs

Issue Are Xenta Servers supported in StruxureWare Building Operations? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Xenta 701, 711, 721, 731, 511, 527, 555 Cause Want to use Xenta Server as a controller in StruxureWare Building Operations. Resolution No there are no special support for Xenta servers. But you can add them as normal LonWorks devices. You can only read/write SNVTs from the Xenta server. Normal Lon rules applies here, you can have a maximum of 64 nodes to a segment (we recommend to keep it under that). TAC Xenta Server I/O modules will not be seen in StruxureWare Building Operation, but they will count towards the 64 nodes on the segment. See Maximum number using StruxureWare Building Operation (Scalability and Capacity) for more information on Lonworks units in StruxureWare Building Operation.  

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue If a Xenta 913 with SNVT(s) is added as a Lon device to an Automation Server Lonworks network the commission process fails in the last step with error 0 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server TAC Xenta 913 TAC Xenta 700 Cause This is a bug in the Xenta Server firmware. Resolution This issue will be fixed in Xenta 913 firmware version 5.1.9, however  hotfixes have been made for 5.1.8 and can be requested from PSS (TACXenta913-5.1.8.15 and TACXenta700-5.1.8.47). Note: All data will be lost in the Xenta Server when applying the hotfix.

Issue When converting an OGC graphic to TGML an error saying that the binding name is too long is displayed. Product Line TAC Vista Environment Vista Workstation Cause When a OGC graphic is converted to a TGML the bindings are named after the path to the value in the objects in the OGC graphic. Resolution After the conversion is done change the binding name in the TGML editor.  

Issue "Enable incoming http communication" option is grayed out and cannot be unselected. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When Building Operation Workstation is connected to the SmartX Server using a HTTP connection, the option to disable incoming HTTP connection is unavailable.     Resolution Use HTTPS in Building Operation Workstation to connect to the SmartX Server to allow this option to be unselected. Refer to the Online Help Topic: Disabling Incoming HTTP Communication

Issue Changing the Automation Server HTTP / HTTPS ports, 1.3 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause There is a need to change the Automation Server's HTTP and/or HTTPS ports from the default ports of 80 (HTTP) and 443 (HTTPS). Resolution The HTTP / HTTPS ports of the Automation Server can be changed from Struxureware/EcoStruxure Building Operation WebStation, requires SBO/EBO V1.3 or higher.  From a web browser*, connect and log on to the Automation Server. After you have logged on, click on the 'Account menu' near the top right corner: EBO 4.0.3 or higher,  From the "Options" select 'Setting'. From the network tab, you can change the HTTP / HTTPS ports.    EBO V4.0.2 or lower, From the "Options" select 'Device Configuration'.   The TCP/IP configuration page should appear. From here, you can change the HTTP / HTTPS ports.       3. Perform a Warm Start on the Automation Server to apply the HTTP / HTTPS port changes to the server.     * Check supported web browsers for Struxureware/EcoStruxure Building Operation at the WebStation specification sheet, make sure to select the correct SBO/EBO version: WebStation (se.com)     Firefox 4 or later (32-bit)

Issue An alarm goes on and off several times in a short amount of time. Each time the alarm condition clears and reasserts itself, by default, another email will be sent. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SMTP alarms Cause Every time an alarm goes off, the email notification checks its parameter and, if true, sends an email. Resolution Filter the email notification by "count." Set it to "from 0 to 1" and you will only get a email on the first alarm (count).

Issue Various items are not being displayed in the system tree or the binding tree of EcoStruxure Building Operation Workstation. When navigating through the tree, items such as folders or parameters may be missing. Product Line EcoStruxure Building Operation Environment Workstation System tree Cause If items are missing in the system tree or the binding browse tree then the filter settings are not set up correctly. Resolution If the expand icon next to a folder is missing or items are missing from the system tree, follow the steps below.     If the expand icon next to a folder is missing or items are missing from the system tree, make sure that the funnel icon is not clicked or activated (Show/Hide non-presentation objects)     If points are missing in the bindings browse window, make sure the funnel in the top left corner of that window is not clicked or activated (Hide parameters)

Issue Unable to back up the Automation Server Unable to retrieve a working backup from an Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Enterprise Central Cause Corrupt configuration.db Network environment issues Power failure Resolution Database Corruption When the server backup process is initiated, the server tests the integrity of the configuration.db.  If the database does not pass the integrity test, the backup process is terminated, and no resulting backup is produced. In this case, an older backup will need to be used.  The backup should be bench tested for integrity before restoring to the production server.   Network Environment In some cases, the AS may produce a valid backup file, but when the backup is saved off of the server the file size is unusually small.  This can happen when network issues interfere with the backup save to disk process.   In such cases, Automation Server backups taken from the Enterprise server will usually be damaged as well.    You can work around this problem by connecting a Workstation laptop PC directly to the AS with an ethernet cable, thus eliminating the network from the process. Backups can also be retrieved in this way using most versions of Device Administrator.    Power Failure The power fails while the EcoStruxure BMS server is backing up and the system displays a “Failed backup” message in the Event view. The solution is to initiate a new backup when the power resumes and the EcoStruxure BMS server goes back online. Power Failure Occurs During Backup     

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 PE Script program created in b3 or i2 has no error but its not executing. Product Line EcoStruxure Building Operation Environment Infinet i1, I2 BACnet b3 Automation Server, AS, ASP, ASB Cause Program compilation was not valid. Resolution Examine the code and determine what is causing the compilation issue. Known causes... 1. Variable declared in the code but not used (unbound)

Issue Unable to compile a b3 Script program if there is a bind to the priority array of a commandable property. How to command an object at a particular priority in b3 Script program. Product Line EcoStruxure Building Operation Environment b3 WorkStation Automation Server Cause Because of historical reasons (that are outside the scope of this article) in the evolution of the b3 firmware, binding to the priority array of an object within a Script program in the b3 is NOT supported. Resolution To command an object from a Script program in the b3 at a specific priority the WriteProperty command MUST be used. NOTE If the b3 firmware is 4.500064 then priority 10 will always be set rather than the one specified in the WriteProperty command. This was fixed in v4.500076, it is best to use the the latest firmware

Issue A network level controller is shown offline. Can a flash upgrade (Update OS) be done to it? Product Line Andover Continuum Environment BCX ACX5720 ACX5740 NC2 CX9900 Cause A bCX needed a flash upgrade but was offline in CyberStation. How can we update the OS? Resolution The Update OS function can sometimes be completed even if the controller indicates that it is offline. If it cannot be pinged from CyberStation, it will not likely be able to be upgraded in its current state and may require returning for repair. But if it can be pinged it, try doing the Update OS. Follow the progress in the Distribution window. If it completes, the controller will likely come back online a few minutes after the update is complete Completing this "Blind Update OS" can often restore to normal operation a controller that has its Operating System corrupted not allowing the Web page to be accessed, as long as you know the ACCNet ID and IP address (a reset IP can be performed) this process may be attempted. It is also possible to flash an offline controller if it has reverted to the default IP address (169.254.1.1) and ACCNet ID of 1 if the Workstation is set to be in the same subnet so it can ping the controller and these default settings are used for the controller configuration. If after a full cold restart and at least 2 attempts to flash the controller fail, then the controller may need to be returned for Repair. Some possible causes of this problem are listed in What can cause a controller to reset, cold start or lose data.

Issue Unable to access ES or AS after setting a new Domain as the default domain Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause If you set a domain as a default domain before logging in through that domain, it is possible that you do not have users set up and therefore will be locked out of the system. Resolution Open Building Operation Workstation Enter a Username and password for the Local domain or another previously functional domain Set the Domain as "Local", please note that this is case sensitive. Select the correct Server Log in Change the default domain back to Local until you have successfully logged in using the new domain.