Building Automation Knowledge Base

Issue When opening an OGC graphic using Vista Webstation as a window inside StruxureWare Webstation, the OGC graphic shows "Loading..." with a small cross in the upper left corner, and the graphic never loads. Product Line EcoStruxure Building Operation Environment TAC Vista Webstation Building Operation Webstation   Cause The authentication in the communication between the browser and Vista Webstation is based on sessions and cookies. Due to a security setting on some sites, the initial cookie can not be set in the browser, and the authentication between the OGC graphic page showed in the browser and the web server therefore fails. If the graphic is opened in full screen (see below) or in a new window it will load, and subsequently all OGC graphics will work until the browser is restarted. Button to open the graphic in full screen Resolution On each PC that needs to access the OGC graphics using StruxureWare Webstation do the following: 1. Open Internet Explorer settings by clicking the gear in the upper right corner 2. Click "Privacy" and then "Sites" 3. Write the address of Vista Webstation (e.g. http://ip_address/webstation), click "Allow" and "OK" 4. Restart Internet Explorer   Note: This solution also applies to following issue; After clicking  a Vista Webstation url (direct link to a TGML graphic) in SBO Webstation from a Windows Server 2012 PC using Internet Explorer 11, Vista Webstation is expanding to fill the entire screen (it doesn't stay in the right hand window of SBO Webstation)

Issue Is it possible to upgrade TAC Xenta 401 and TAC Xenta 300 HW1 to latest system version? Product Line EcoStruxure Building Operation  Environment TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 Cause Whenever possible, upgrading to the latest system version will give you all of the latest product fixes and enhancements. Resolution You can upgrade TAC Xenta 300 as well as TAC Xenta 401 to any system version BUT you cannot use HW1 in EcoStruxure Building Operation. All HW versions can be upgraded for use in TAC Vista Classic system.

Issue The functionality of StruxureWare Domains changed substantially in 1.2. There has been some discussion that the inability to communicate or the failure to transfer data from one SmartStruxure server to another is somehow related to the servers not being in the same StruxureWare Domain. This is not the case. As of 1.2 StruxureWare Domains are not used for communication at all. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server Premium (AS-P) Cause StruxureWare Domains are NOT used at all for establishing communication within SmartStruxure 1.2 and later releases If the AS can be added under the ES and no alarms are generated by the added AS, then full data sharing is possible regardless of StruxureWare Domain creation or membership. Resolution If the AS can not be added under the ES then there is a network problem that is preventing communication from the ES to the AS. If the AS can be added, but communication errors or lead verification alarms are generated that show the added AS as the source server, then there are network (or firewall) issues that are preventing the AS from communicating with the ES. If all engineering and configuration is done from the ES with the admin account in the Local Domain All bindings can be created by admin in the local domain All data can be viewed in graphics, trend charts, etc. by admin in the local domain Only data within the local AS can be viewed  by admin logged into the local domain of the AS This is true regardless of WorkStation or WebStation A StruxureWare Domain other than the local domain must be created and the other servers must be added to that StruxureWare Domain in order for users to have access (viewing or otherwise) to objects in the other servers.

Issue A TAC Xenta programmable controller has issues, and more information is needed to analyze what is happening in the controller. Product Line EcoStruxure Building Operation Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 401 XentaErrorLogViewer Cause The TAC Xenta 280, 300 and 401 series has an internal Error Log, that in some cases could give more information about the way the device is acting, storing restart reasons etc. Resolution The XentaSystemErrorLogViewer is used to read out the internal error log file from a TAC Xenta 280, 300 or 401 device. The XentaSystemErrorLogViewer is a program that runs in your PC, and you have to connect to the TAC Xenta device by the use of a serial cable. You must have at least the same version number of the XentaErrorLogViewer as the device you want to read the information from. Please note that the XentaSystemErrorLogViewer program only works with released version of the TAC Xenta 280, 300 or 401 devices. 1. Download XentaSystemErrorLogViewer 2. Install the program 3. Connect the TAC Xenta to the PC using the TAC Xenta programming cable. Refer to the cable guide for further information. 4. In "Preferences", select the COM port to which you connected the serial cable 5. Check "Write System Error Log to file" 6. Click "Get new information" 7. The information is written to "C:\Windows\Temp\XentaSystemErrorLogg.txt"

Issue What alternatives are available for accessing Continuum WebClient from browsers other than Internet Explorer? Product Line Andover Continuum Environment Continuum WebClient Server Cause While Internet Explorer is the only officially supported browser for Continuum WebClient, Microsoft has announced that support for Internet Explorer will end in June 2022.   When accessing WebClient sites using Microsoft Edge in Internet Explorer mode. WebClient server returns an error, indicating that Internet Explorer is needed to access WebClient. Resolution It is possible to access WebClient using Microsoft Edge in Internet Explorer Mode. 1. In Edge click on the ellipses (...) top right then select Settings and set like the snapshot below. a. Allow sites to be reloaded in Internet Explorer Mode(Allow) b. Add the webclient machine's login page (http://webclientservername/webclient/logon.aspx) 2. Setting Internet Explorer compatibility mode and Internet Explorer mode for future use. Navigate to the webclient URL with Edge and select Reload in Internet Explorer mode By default, these settings will be Disabled, Set both of the buttons to Enable as shown below. Note: you may have to go through the process twice to enable both buttons   A snapshot of a successful login to webclient with Edge and also the selection in yellow to Exit Internet Explorer Mode if necessary to run other web applications.   The method of specifying Internet Explorer Mode for a site’s webClient URL will depend on how the customer treats the configuration of Edge – either settings at the individual Edge level or via group policy settings.

Issue Want to modify the type of a block in the Function Block Editor while retaining the original block's name Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Function Block Editor. Cause Altering the block type without removing the block first can result in the persistence of old block parameters even if they are incompatible with the new block type. For instance, transitioning from an "Integer Input" block type while the input is in a forced state may cause the new block to retain the forced state, even if it is not applicable, leading to potential issues with un-forcing. Resolution To ensure correct functionality, it is recommended that the old block is removed and the application saved before adding the new block with the original name. This process effectively clears out the old configuration, enabling the new block to contain only the parameters of the new block type.

Issue Will EcoStruxure Building Operation provide any indication of a failure sending a SNMP trap? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Need to receive an alarm and event if an EBO server couldn't send an SNMP trap. Resolution If there is a failure sending an SNMP trap, EBO will generate a system alarm/event indicating that the trap could not be sent. Note though, that if the trap is sent successfully there is no indication or log entry to indicate so. System Alarm ID Description SNMP send trap failure Failed to send SNMP message.

Issue Need to serve data via Web Services to 3rd party systems.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Cause Generic Web Services SOAP, Simple XML or Script Web Services cannot act as a server. They can only act as a client to other web servers. Resolution EcoStruxure BMS servers can serve information to another EcoStruxure system using the EcoStruxure Web Services standard. For 3rd party systems, SmartConnector RESTful EWS Gateway can be used to serve EBO data to 3rd party system in a RESTful manner, refer to: Configure SmartConnector RESTful EWS Gateway to serve EBO data - Schneider Electric Community

Issue How to change the priority of system generated alarms in EcoStruxure Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Cause Need to change EBO system priority. Resolution Currently, it is not possible to change the priority of system alarms. The default is value 100.  There are currently no plans to add the feature. 

Issue Device Administrator requires CRT certificate file to add a certificate to CA Certificates. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause If you rename the filetype from .pem to .crt and add via Device Administrator, the Automation Server will still present the following alarm: Alarm Text: System alarm: unable to get local issuer certificate System alarm ID: Invalid certificate for https communications   NOTE: The alarm will be known to have originated from the Automation Server because, in the Source field, the Automation Server will be the root, and the server it is connecting to will be the last. Example: /AS01/System/Communication/Server Certificate/To/ES01 AS01 - Automation Server with the CA Certificate issue ES01 - the EBO server which is was connected as client, which generated the alarm Resolution Reference this article to find OpenSSL installed: OpenSSL installed with EBO Use and modify this command with your filenames:  openssl x509 -in ca.pem -out ca.crt​ Add the .crt certificate file via Device Administator's CA Certificates tab. Reference: CA Certificate Tab (WebHelp)

Issue Ensure a version of TLS is disabled using OpenSSL Product Line EcoStruxure Building Operation Environment Enterprise Central Enterprise Server Automation Server Cause Need to verify TLS is disabled on an EBO server in case of incorrect text entry Resolution It is possible to check which TLS protocols are set to be disabled using WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. If the version required is not disabled then consult Disabling TLS and SSH. Once the protocol is set to disabled follow the steps below to verify using OpenSSL Open a command prompt and change directory to the OpenSSL folder. If OpenSSL is not available consult OpenSSL installed with EBO or install OpenSSL as mentioned in Ensuring the SSL Host Certificate and key file are a matching pair To check if TLS is disabled enter the command openssl s_client -connect 'server address':'port'-'TLS version'.  For example if the server IP address is 192.168.5.95 and using port 443:- openssl s_client -connect 192.168.5.95:443 -tls1    openssl s_client -connect 192.168.5.95:443 -tls1_1 openssl s_client -connect 192.168.5.95:443 -tls1_2 openssl s_client -connect 192.168.5.95:443 -tls1_3 If an error is returned (1) and no certificates are available (2) then the TLS version is Disabled. If a certificate chain (3) and certificate details (4) are returned the TLS version is Enabled. The image illustrates only the start of the returned information, more will be available.   For additional information search "OpenSSL s_client" using an online web browser.  The s_client command can be used to test TLS server connectivity, TLS/SSL version support, check cipher suites, and verify server certificates.  

Issue The following errors are seen when trying to run SigmaX, RegSigmaX or SigView.  The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.  Application event log: Activation context generation failed for "C:\SigmaX\Bin\RegSigmaX.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis. Product Line Satchwell Sigma Environment SigmaX 7.0.6 on Windows 7 32-bit SigmaX 7.09 on Windows 10 64bit SigView Cause Microsoft Visual C++ 2005 redistributable has not been installed. It appears that SigmaX requires this version to run. Resolution Either the Microsoft C++ 2005 is not installed, or if it is, then the Service Pack 1 (SP1) is required to be installed. This can be checked under the Windows 'Apps and Features'. Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86). In some cases,  Microsoft Visual C++ 2005 SP1 Redistributable Package Security Update (x86) is required to resolve the issue. The 32bit (x86) version should be installed if installing Microsoft Visual C++ 2005 SP1 does not fix the problem. 

Issue Changing the Module ID after physically replacing a modules gives error "Incorrect response (or no response) from IO module" Product Line Andover Continuum Environment CyberStation CX9900 CX9940 CX9680 IOU Module Cause Controller's OMS database is out of sync with SQL database. Resolution To synchronize the OMS database with the SQL database:- Put CyberStation in offline edit mode. Edit the IOU Module object and enter the new Module ID. Save the object Return CyberStation to online edit mode. Perform a Send to controller, reloading the controller will sync the OMS db in the controller with the SQL database. Note the following: Make sure to use the option to reload attached objects but not attached controllers If IOUs go offline when sending to controller after doing this, manually get IOUs online, perform a send to database and send to controller. If a number of IOUs were replaced this process may need to be repeated several times until the send to controller works with no errors.

Issue A dialog of "Cannot open .NET editor with .NET Framework" comes up with new installation of Webclient or after a Microsoft update of .NET 4.5.x. There was an error trying to create the .NET control for this page. Product Line Andover Continuum Environment Continuum Webclient Windows 7 Windows Server 2008 Windows 10 Internet Explorer Cause Microsoft changed the behavior of Internet Explorer when .net 4.5.x is installed on a PC. It turns off .net 2.0 support which is needed for several editors to function on Webclient browser PCs Resolution See web.Client v2.0 .Net Editor Hotfix on the EcoXpert Extranet This is a registry key file that installs the registry keys mentioned further down in this article. It allows Internet Explorer to utilize .net 2.0 that several webclient editors use. This hotfix contains a .reg file which changes the registry, it is recommended to make a Windows Restore point or a backup (export) of the existing registry folder (hive). The hotfix only updates the following keys, so the changes can also easily be made manually. On an 32-bit (x86) Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Set the value to 1 On an 64-bit Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Set the value to 1 A reboot of the webclient browser PC is required after the change is made. Each browser PC will need to have this fix applied. Microsoft Edge can also be used on newer client PCs, see the following article: Microsoft Edge can be used for webclient client PCs   

Issue When trying to activate a license in an AS-P/B the following error message was shown and the activation failed: Online activation: 12:57:24: Executing licensing command 12:57:24: Executing embedded operation: Activate ActivationID: ACT-xxx 12:57:32: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: Z(BACK_OFFICE%DEBACK_OFFICE+']\dBl&%MSM230312018I|B}~%ACT-xxxxx/jlSkkj1%<K!,b7OnpUy7 zqDFG#I$QGGR0:SYWJVGIuW}+iea 0\wR/`;yX'HGX*;;nEl]d0I+nHWh(VD"+a uwpf%XF[N6~!,^?R]y?VPCw\gB{"dSy2K7ph;_=qw.|c]Vp;.nlMbLl-~Z!UY<:=TFZEL~h=\V)>ML)ld0g'PPcjrosy&]p9Y((?II#*B5/U16X;o- 12:57:32: Licensing command completed 12:57:34: Activating licenses failed   Offline activation: 12:56:02: Executing licensing command 12:56:02: Executing embedded operation: ProcessResponseFile ResponseFile: C:\Users\Mitthem\Desktop\Garage\response\xxxxxxx\8ba20b60-b19c-4a5d-8fea-693ef9282c8c.bin 12:56:03: Embedded operation: ProcessResponseFile failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information:  12:56:03: Licensing command completed 12:56:05: Activating licenses failed Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA)  Embedded Licenses Cause The reason for the issue was that the number of available licenses for activation was 0, but the error message in DA was not indicating that. The Device Administrator (DA) showed that two licenses were available but were out of sync. Resolution When looking at the Entitlement in DA, it had a yellow dot on it, indicating that it was added offline. In DA version 5.0.2 and later, DA contacts the License server directly when adding an Entitlement in prior versions this was done through the AS-P. In DA version 5.0.2 and later, it is enough that the computer where DA is installed has an internet connection when adding an Entitlement online. After upgrading DA to version 5.0.2 and refreshing the Entitlement, the Device Administrator showed the correct number of available licenses.    If upgrading the site to this version is not possible, the Entitlement ID / Activation ID availability and device list can be verified by using the User Portal FlexNet Login (flexnetoperations.com) It is also possible to run Device Administrator version 5.0.2 with the concurrent site version used as long as the Servers are at 4.0.4 and above to check, verify and activate licenses.     Important Note: Device Administrator 5.0.3 and above will NOT support lower-version Automation Servers as 5.0.2 does.  This is due to new features of embedded licenses for servers as well as the handling of servers without internet connections.  In this case, ALL servers must run the same version as the Device Administrator version when handling licenses.         Further information on Automation Server Licensing Overview is available through the online WebHelp.  

Issue Error 'The UPREV engine was asked to process an invalid code type' when flashing the firmware in the controller. Product Line Andover Continuum Environment bCX9640 CX9680 ACX5720 ACX5740 Cause RAM issues Resolution Using a browser login to the controller and perform a 'Clear Database Backup', commit changes and restart the controller. When the controller has re-started  disconnect the battery, power down the controller and after a minute power the controller up and re-connect the battery. Wait for the controller to come back online and then try the uprev operation once again.

Issue When attempting to detach an AS, PCT continues to shown the server as being attached to the ES.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool 1.x (PCT) Cause In PCT, when an AS is detached from its parent ES, the ES name still appears in the Added to parent column of the Servers list. Resolution Once the AS has been detached from an ES it can be added to another ES though Workstation using the following steps even though the "Added to parents" column shows otherwise.   To create a SmartX server In WorkStation, in the System Tree panel, select the Servers folder. On the File menu, point to New and then click Server . In the Create Object wizard, in the Name box, type a name for the SmartX server. In the Description box, type descriptive information about the SmartX server. Click Next . In the Configure IP/DNS Address and Port page, in the Address box, type the IP address or fully qualified domain name of the SmartX server. Notice If the SmartX server has been assigned a dynamic IP address, use the fully qualified domain name of the SmartX server instead of the IP address. In the Protocol box, select a protocol for the SmartX server. For more information, see EcoStruxure BMS Server Communication . In the Port box, enter a port number. Click Create. In the Log on dialog box, in the Password box, type the custom password if required. Click OK.   For more information, see Creating a SmartX Server

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * To be compatible with the 6.00.0x FW, your system must run at the minimum the following CP (Hotfix) versions of EBO. For EBO 3.2.x, use 3.2.4 CP2 or higher. For EBO 4.0.x, use 4.0.5 CP1 or higher, for EBO 5.0.x, use 5.0.3 CP4 or higher. CPs are available on: EBO Hotfix List Note: Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   Note: v3.02.0x and earlier are not supported and should be upgraded to a fully supported version. Refer to earlier versions' release notes for the older versions' compatibility matrix. Note: RP-C is only supported on EBO 3.0 and later MP-V/RP-V compatibility   SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: Previous to Version 33 (Build 70), SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 33 (Build 70) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well.  The EasyLogic controllers are not supported by the Niagara modules at this time.    

Issue Cannot activate embedded license on Automation server, either online or offline, with error: FlexNet Embedded error: The allowed time to process the response has expired.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Automation Server has wrong date and time. Resolution Make sure that Automation Server has correct date, time and time zone. Automation Server can be connected to NTP server to synchronize its clock, refer to Synchronizing the Automation Server Clock.

Issue In SpaceLogic BACnet/IP controllers, a DHCP configuration takes longer than a Static IP configuration to start BACnet communications after a power cycle or restart. Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller (MP-C) Building Operation Multi-purpose VAV (MP-V) Building Operation Room Controller (RP-C) Building Operation Room VAV (RP-V) Cause The DHCP IP address assignment flow diagram is depicted in this WebHelp article: IP Address Settings for IP Communications. As a part of the failover process, once the controller receives a DHCP lease, it will send multiple ARP requests to ensure the IP address is not being used by another device, further delaying BACnet communications. If it does not detect another device using that IP, it will use the IP it was given to lease. Also, SpaceLogic BACnet/IP controllers store the IP address and port of the controllers for which they have External Binds (Consumers/Producers). If a device is unavailable at that IP address because the DHCP lease has changed, the controller will have to use WHO-IS to find the new address of that controller. Resolution Configure the SpaceLogic BACnet/IP controller with a Static IP address, so the controller will boot directly using a Static IP address and start communicating via BACnet/IP. If on the AS-P Secondary Network with 10.110.210.0/24 network where AS-P DHCP server leases IP addresses from 2 and goes higher, assign static IP in a higher number range (0-254) for the last octet.