Building Automation Knowledge Base

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 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.

Issue During Energy Expert installation an error is shown, and the floating license manager is never installed Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) Installation Cause "Error 1722" occurs due to a conflict between the version of Java installed on the PC and the version included in the EE installation package Resolution Uninstall all versions of Java from the PC Install the JavaRuntime manually from the install media "..\setup\SetupSupport\Licensing\JavaRuntime\x86\jre1.7.0_02.msi" Run the complete installation again

Issue How is the Real Time Clock (RTC) maintained when a Automation Server loses power since there is no battery on the AS. Product Line EcoStruxure Building Operation Environment Automation Server (AS-P, AS-B, AS) Real-time clock Cause Documentation Resolution Each Automation Server has a dedicated capacitor that backs up the RTC chip.  Please consult the tables below or use the Webhelp links and search for 'Real-time clock':-   AS-P Real-time clock Accuracy in runtime mode NTP server Accuracy in backup mode, at 25 °C (77 °F) +/-52 seconds per month Backup time, at 25 °C (77 °F) 10 days   AS-B Real-time clock Accuracy in runtime mode NTP server Accuracy in backup mode, at 25 °C (77 °F) +/-52 seconds per month Backup time, at 25 °C (77 °F) 10 days   AS Real-time clock Accuracy, at 25 °C (77 °F) 47 to +73 seconds per month Backup time, at 25 °C (77 °F) 30 days

Issue Users are getting two possible errors when trying to open WebReports page Error #1 - "The Web Site URL for Reports is not configured. Please contact the administrator" Error #2 -  "The webpage cannot be found" can also be generated. Product Line EcoStruxure Building Operation Environment Web Reports Cause These Errors can occur when the link to the Reports Server is not correct.  This is usually caused by having the Enterprise Server and Report Server on the same PC It should be noted that having both the Enterprise and Report Server's on the same PC is not recommended.   The reason the Workstation can not access the Web site / Web service URL's is because the Report Manager points to the "Localhost".  When you try to use a Workstation that is not local to the Report Server it can not locate this URL, hence the error.   This issue is not seen if when installing the Report Server on a different machine to the Enterprise Server as designed. Resolution Even though the Enterprise Server is local to the Report Server if access required by any other Workstation or WebStation you must enter the IP or PC Name of the Report Server within the Report Manager's Web site URL.  In this instance changing only the Web site URL will rectify the problem but it is recommended to change both the Web site and Web Service URL settings. This will allow any remote Workstation / Browser to find the Report Server. In workstation, Browse, to the System folder Click on System>Report Manager Set the Web site URL to http://localhost/SchneiderElectric/WebReports/Login.aspx Set the Web Service URL to http://localhost/SchneiderElectric/WebReportsService If the Enterprise Server resides on a different PC than the Reports Server, change "localhost" to the Report Server computer name or IP address After making this change WebReports should display correctly:

Issue The following error is generated during the SQL Configuration step for 1.8 Reports Server Product Line EcoStruxure Building Operation Environment WebReports Installer Cause This can happen for various reasons: Possible cause 1 The Microsoft .NET Framework installation is damaged after installing Microsoft SQL Server. Possible cause 2 In one of the steps during SQL installation, we have to configure NT AUTHORITY\SYSTEM. If user fails to change this and move ahead with default user then create database step would fail. Possible cause 3 The operating system is not using English as its selected language. Resolution Solution 1 Quit the WebReports Installer Package Remove/reinstall or repair .NET Framework 4.5 (Available from Microsoft .NET download site or direct download - WebInstaller - OfflineInstaller) Repeat the installation of WebReports Solution 2 Set the SQL server service log on properties to "Local System" (NT AUTHORITY\SYSTEM) Restart the SQL server service Repeat the installation of WebReports Solution 3 Replace the WebReports OS with an English version of Windows. 

Issue BACnet 3rd party controller will not respond to Find New BACnet Devices (Who-Is/I-Am), so will not come online to Continuum or EBO Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Continuum Cyberstation Continuum bCX4040 (BACnet) Cause BACnet MSTP device can be master or slave. BACnet MSTP slave will only respond to a request from a master device, and will not respond to the Who-Is broadcast so it can not be discovered. EBO: EBO does not support slave devices. EBO does not currently have a way to statically configure MAC addresses as it relies on dynamic discovery.   Continuum: Slave only devices cannot come online. Resolution Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network. Use 3rd party interface to convert to a protocol that can be directly supported by EBO or Continuum. Examples of BACnet MSTP Slaves that are known not to respond to EBO or Continuum Who-Is request and so not come online are: - The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here. - Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here.  

Issue When adding a document to an EcoStruxure server an error message appears. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server (AS-P/AS-B) Cause There are size limitations to take into consideration. Resolution It is possible to upload any file type, including .doc, .jpg, .pdf, or .txt.  However, importing files larger than 20 MB will result in an error message.     Refer to Documents Overview for additional information

Issue If an Automation Server should be used as a LON Device in an OpenLNS Database using the OpenLNS Commissioning Tool? Is that possible to do? Product Line EcoStruxure Building Operation Environment Automation Server 1.4.1.68 or newer   Cause Some sites may wish to use other Lonworks configuration tools than EcoStruxure Building Operation Workstation. Resolution This is possible in 1.4.1.68 and newer. Add a Lonworks Local FT-10 interface and then add an Externally Managed Lonworks Network.