Building Automation Knowledge Base

Issue Does EcoStruxure Building Operation support virtualization?  Can the Enterprise and Reports server be on a virtual machine? Can EcoStruxure Building Operation be installed in cloud environments? Product Line EcoStruxure Building Operation Environment VMWare Hyper-V Microsoft Azure Amazon Web Services EcoStruxure Building Operation 2.0 through current release. Cause Desire for virtualization or cloud environment. Resolution Emulating environments Virtualization has several interpretations. In this article, we'll specifically address running EcoStruxure Building Management software in emulating environments like VMware or Hyper-V. These emulating environment software packages replicate a physical PC environment, allowing multiple computers to operate on a single machine, hence the term "virtualization". Several software vendors offer emulating systems, with VMware and Hyper-V being the most prominent. The advantages of running an emulating environment include reduced physical machines, minimized space requirements, and lower maintenance costs.   It's important to note that other potential meanings of "virtualization" such as remote desktop, remote control software, terminal server environment, or cluster environment are not covered in this article.   EcoStruxure Building Management in emulating environments Currently, numerous installations are running EcoStruxure Building Management on VMware and Hyper-V without significant issues. Some challenges have been observed related to Veeam setup, which doesn't seem to integrate seamlessly with ES (and possibly EC).   VMware is utilized internally in R&D and Product Support teams with positive feedback on its performance. Users should have familiarity with the emulating product to configure settings correctly, ensuring network functionality. It's important to highlight that no specific efforts have been made to develop EcoStruxure Building Management to comply with emulating environments. Additionally, there are no specific tests to verify its functionality in emulating environments. Certain issues have been seen with the License system used by EcoStruxure Building Operation when running on specific emulating environments due to limitations in the license system's support for these environments.   Support for EcoStruxure Building Management installations running in emulating environments Product Support provides support for EcoStruxure Building Management software, irrespective of whether it runs on PC hardware or in an emulating environment. Support is provided for problems related to the EcoStruxure Building Management Software itself, but not for issues related to the environment it runs on. Except for approved operating systems and minimum memory requirements, Product Support does not offer guidance on configuring specific PC hardware or emulating environments. Cloud environments Cloud computing environments such as Microsoft Azure and Amazon Web Services provide on-demand availability of computer system resources without direct active management by the user. Cloud computing relies on sharing of resources and typically uses a pay-as-you-go model, which can help in reducing capital expenses.   One of the challenges of cloud computing is reduced visibility and control. Cloud users may not have full insight into how their cloud resources are managed, configured, or optimized by their providers. They may also have limited ability to customize or modify their cloud services according to their specific needs or preferences.   Support for EcoStruxure Building Management installations in Cloud environments EcoStruxure Building Operation has not been developed or tested with Cloud environments in mind and it is therefore not currently a supported environment.  

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue When logging into Workstation one of the following error codes is given.  Invalid returned data from license server system. (Error code: -12) Cannot connect to license server system. (Error code: -15) License server system does not support this feature (Error code: -18) The desired vendor daemon is down. (Error code: -97) Product Line EcoStruxure Building Operation Environment Workstation License Server Cause These type of issues are contributed to the License Server, Vender Daemon being down or not having a valid license for the application which is used. Here is a complete list of error codes Resolution If Workstation is installed on a different PC than the license server, refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96). If you get license error -18 refer to Error "Requested license is not available on the license Server" even though the license for the StruxureWare Building Operation is valid. Start by working through the troubleshooting steps below. In some cases the Building Operation License Server was unable to start due to antivirus programs on the computer.    Cannot connect to FlexNet License Admin Using your internet browser and go to localhost:8888. If you are unable to connect to this address then the License Server is not running.  Ensure that the Building Operation X.X License Server is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services.  Scroll through the list and select Building Operation X.X License Server. Click start in the top left corner of the window. Some times the following Windows Error 1067 is given when trying to start the License Server. Note: In the past this error has been caused by antivirus software on the computer. In this situation the antivirus program had to be uninstalled in order to allow the License Server to start.    If the Building Operation License Server will not start then it may be due to another program using TCP port 8888. Use TCPView to search for programs running on local port 8888 and stop the other program.      Vendor Daemon is Down Note: If working with a 32 bit PC, replace "Program Files (x86)" with "Program Files" in the file paths below. Using your internet browser go to the address localhost:8888. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password.  Click on the Vendor Daemon Configuration tab and then select the taclic daemon.  Verify that the path in the License File or Directory field matches the location of the taclic.lic file. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start.    Vendor Daemon is Down issue caused by ipv6 Cases have been seen where having ipv6 enabled on the same computer where the license server is running causes the Daemon is down error.  Often there will be entries in the license server logs that are similar to: 17:46:44 (demo) Lost connection to lmgrd, heartbeat timeout expired, exiting. 17:46:44 (demo) EXITING DUE TO SIGNAL 37 Exit reason 5 17:46:44 (demo) IN: "f1" user1@host1 (SHUTDOWN) 17:46:44 (lmgrd) demo exited with status 37 (Communications error) To confirm whether this is the issue ask the site if it is OK to disable ipv6 on the machine temporarily. In Windows control panel disable ipv6 Reboot the computer. In some cases, it might be needed to disable IPv6 completely in the registry: https://tweaks.com/windows/40099/how-to-properly-disable-ipv6/ If the issue is resolved then inquire with the site if it is OK to leave ipv6 disabled. If SIGNAL 37 errors are seen in the license server logs, these can be caused by having the localhost name associated with the IPv6 loopback address in the hosts file. This can cause communication problems between the license server daemon (lmgrd) and the vendor daemon, resulting in shutdown of the latter. If you have a line like the following in the /etc/hosts file: ::1 localhost ip6-localhost ip6-loopback please change it to ::1 localhost6 ip6-localhost ip6-loopback so that the localhost name is associated only with the IPv4 127.0.0.1 address. Please note that modifying this file requires Windows administrative privileges.  

Issue Files required to install EcoStruxure Building Operation Web Reports Server Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Tutorial for configuring Web Reports Resolution EcoStruxure Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and WebReports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for EcoStruxure has a tutorial which will walk you through configuring the report Server, and running reports: WebReports Overview  If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing WebReports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user".

Issue What is a Software Bill of Materials (SBOM) and how do I obtain one for EBO? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause A Software Bill of Materials (SBOM) is a comprehensive list of all software components used in a particular application or system. It provides details such as the names and versions of libraries, modules, frameworks, and other software elements integrated into the final product. SBOMs are used for several purposes:   Security: They help in identifying and addressing vulnerabilities in the software by providing transparency into the components used, making it easier to track and remediate security issues. Compliance: SBOMs assist in ensuring compliance with licensing requirements and open source software usage, helping organizations manage legal and regulatory obligations related to software distribution. Supply Chain Management: They enable organizations to understand and manage the dependencies and origins of software components, facilitating supply chain risk management and resilience. Support and Maintenance: SBOMs aid in effective support and maintenance of software by offering insights into the various components and versions used, allowing for better troubleshooting and updates. In essence, SBOMs enhance transparency, security, and governance in software development and deployment processes, thereby contributing to overall software quality and risk management. Resolution Since libraries and components contained within software may change between releases a SBOM is a dynamic document that needs to be compiled upon request. Please contact your local Product or Account management team, specifying the exact EBO version you require an SBOM for. 

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 Need to setup SAML SSO with Azure EntraID Product Line EcoStruxure Building Operation Environment Building Operation Workstation Azure Cause The SAML configuration requires details setup Resolution Part 1: EBO configuration Creating and Configuring the SAML Configuration Object To create and configure a SAML configuration object. In WorkStation, in the System Tree pane, expand the System folder. Expand the Federated Authentication folder. Select the SAML Authenticator object. On the File menu, click New object. Select SAML Configuration. Enter a name, path, and description on the object you want to create. Click Create. Configure the settings. Enabling Federated Authentication To enable federated authentication In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to configure. Click the Control Panel tab. Click Security Settings. Select Enable federated authentication. Click the Save button. Configure SAML Configuration object Service Provider To configure the service provider. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Service Provider Settings tab. Configure the settings. Identity Provider To configure the identity provider. In WorkStation, in the System Tree panel, click the SAML Configuration object. Click the Identity Provider Settings tab. Configure the settings. Configuring the Security To configure the security. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Security Settings tab. Configure the settings. Create and configure domains Create and configure a domain to be used for Federated Authentication. Create a Domains Create a group Configure the permission for the group Part 2: Azure Configuration Login to https://azure.microsoft.com/ Create SAML application under Entra ID Click Microsoft Entra ID Click Enterprise Application Select Create your down application Enter the name of the App Select “Integrate any other application you don’t find in the gallery (Non-gallery)” An Enterprise Application is created with the name Create a group Select Groups Click New Group Select “Microsoft 365” for the Group type Enter the name of the group, the “Group name” must match the Domains Groups name in EBO. Add Owners and Members to the group Configure Entra ID Select Assign users and groups in the Enterprise Application Overview Select Add user/group then click Assign The selected group is under the application Select Set up single sign on in the Enterprise Application Overview Under Basic SAML configuration Enter the information from EBO SAML Authenticator Basic Tab The Sign on URL is Base URL The Identifier is Entity ID The Reply URL is AAssertion Consumer Service URL Click on Edit from Attributes & Claims Click on “Add a group claim” Select Groups assigned to the application Select Cloud-only group display names under Source attribute update the “Unique User Identifier” Value to user.displayname Download the “Federation Metadata XML” certificate Open the XML file and find the line with certificate, it will start with <XXXXCertificate> Copy the string between the two brackets and paste it in Public key certificate under Identity Provider Settings Copy the Entity id and Single Sign On Service URL from Azure to EBO. The Entity Id is Microsoft Entra Identifier. The Single Sign On Service URL is Login URL. Part 3: Testing Test Single Sign On Go to Webstation by entering the SmartX Server network address. Click on Log on with SSO Select the account within the Azure Group Successful login screen

Issue The "BACnet device proxy base" type is missing in the Search type after EBO 4.0 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Building Operation SmartX Living Space Sensor BACnet B3 IA SE8000 VT8000 Cause The "BACnet device proxy base" was removed from EBO 5.x and later. Resolution To search for a specific type, add individual type to "Include types" For example 'BACnet device' will return all 3rd party (generic) BACnet devices. 'SpaceLogic Series Device' will return all MP and RP devices. Sample Search all BACnet devices(excluding AS/ES) XML attached

Issue How to create a write to file notification that creates a comma separated value (CSV) file. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) Cause Write to file notification has options for Excel and text formats, but no option for CSV format. Resolution As the name suggests, Comma-separated values (CSV) is a text file format that uses commas to separate values, and newlines to separate records. A CSV file stores tabular data (numbers and text) in plain text, where each line of the file typically represents one data record. This means that the text format can be selected in in the notification to provide a CSV file.   Building Operation 1.7 and earlier Under file name, use the extension .csv. See screenshot below:   This will produce a .csv file located in your database folder under the Notification folder.   Building Operation 1.8 and later With the introduction of "Variable Triggered Notifications" and "Alarm Triggered Notifications," users can now find the Write to File option within the "Distribution method" in the Triggered Notification Object. Within the Configure Write to File window, users will have the option to save the file with the .csv extension.   Using write to file option to save Text file with .csv extension This will produce a .csv file located in your database folder under the Notification Files folder.  File location in the system tree   For additional information and guidance, refer to the Notifications topic in EBO WebHelp.

Issue Can the EasyLogic range of controllers & RP-IO Modules work under Building Operation 3.2 as BACnet MS/TP third-party devices  Product Line EcoStruxure Building Operation Environment EasyLogic Controllers, EasyLogic RP-V, EasyLogic RP-C, EasyLogic MP-C EasyLogic RP-IO SpaceLogic Advanced, Pro, and Pro Plus Controllers that support native BACnet MS/TP (via a SpaceLogic RS-485 Adapters.   Cause The documentation states that EasyLogic Controllers can be used as a Native BACnet MS/TP device. These devices must be configured using their respective supported Building Operation versions, such as Building Operation 2022 and above. However, there are no guidelines on whether they can be used as a third-party BACnet device, in particular in earlier versions such as Building Operation 3.2.    Resolution EasyLogic controllers can be used as BACnet MS/TP third-party party devices in Building Operation 3.2 since the EasyLogic range of RP and MP controllers, and RP-IO I/O modules natively communicate using the BACnet MS/TP protocol.  This same concept applies when using the devices as true 3rd-party devices (e.g., with Continuum and I/A systems) when older controllers fail, and these EasyLogic controllers are used as temporary replacements before a full transition.   What MUST be understood before taking this approach is that there is no automatic conversion when migrating the site (and devices) to later Building Operation versions that support these devices natively. After the upgrade, the controller must be deleted from the database and hosted as a native EBO controller.   During this process, some programming may be lost. This risk may be mitigated by creating Custom Types for the application once engineered in Building Operation 2022 (or higher) to future-proof the site for upgrades.  Using the latest firmware for the EasyLogic range of devices is also recommended.     Furthermore, the SpaceLogic Controller Range that supports native BACnet MS/TP (via an RS-485 Adapters) can be configured in the same fashion as described for the EasyLogic range.   Refer to Hardware Overview for further details on each product line. 

Issue The automation server was added successfully; however, it never appeared in the server list. It did, however, get added to the communications tab. The System Tree server list varies from the Communication tab list of servers. No servers shown under "Servers" List in System Tree but is seen in Communications tab Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause This is typically caused by the Group account not having permission to access the root path.  To verify this is the issue, log in with the "admin" user account and verify that the server lists match.    Looking at the screenshot below: If the Add (+ icon) option has been used to add the ES-1 Path Permissions, no server will be visible.  Additional Path Permissions need to be added for each server. If the Add System (Hierachial icon) option is used (the default for the local admin account group), this is the System's top-level path. Then, all servers will be seen.       See online WebHelp topic User Account Group – Software Permissions Tab Resolution Depending on which method is required by the end user. If using the Add (+icon) option  Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add (+) the Automation Server(s) to the path permissions as shown below: Repeat the above step for every server Each time a new Automation Server is added, repeat all steps.  If using the Add System (Hierachial icon) option Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add System (Hierachial icon) to the path permissions as shown below: Users must log off and log on to see any of the implemented changes.    

Issue  EBO can have license violation bar without a known reason. 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 Building Operation Edge Server - Standard Cause License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.

  Issue The IoT alarm is being displayed, and acknowledging the alarm removes it temporarily, but it returns. Product Line EcoStruxure Building Operation Environment Building Operation EnterpriseServer Building Operation Workstation Lead/Shadow enabled System Alarms  Cause In Building Operation version 3.0.1, Cloud Connectivity was enabled at the Automation Server.  The alarm indicates that the Automation Server cannot connect to the Cloud server, whether attached to an Enterprise Server or Standalone, typically because there is no internet access.   By default, the option for Cloud Connectivity is set to Auto. Once the Automation Server is attached to an Enterprise Server, this option is applied in all sub-server settings and controlled from the lead object in the Enterprise Server. Resolution To prevent the alarm from triggering, Navigate to the Enterprise Server Control Panel Under the "Security and Communication" section, select Cloud Connectivity Switch the function from Auto to Disable. This change will be passed down to all sub-servers. Should the alarm not clear, a power cycle may be necessary to clear this alarm. See the following online WebHelp topic, Cloud Connectivity Overview, for further information. 

Issue The site has cloud connectivity issues, and R&D requires the trace log to see the communication. The trace logging for the cloud plugin (/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.Cloud) has been enabled and set to Trace, and there are no records of nsp.pin.Cloud referenced within the trace log. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment EcoStruxure Building Advisor EcoStruxure Building Operation v3.0.3 or earlier  Cloud Connectivity Cause In versions before 3.0.4, by default, the cloud plugin does not report on the trace log. Enabling trace log reporting for nsp.pin.Cloud is a high-level procedure that requires support intervention.     Resolution This version (3.0.4) and lower are now out of support, so it is recommended that to upgrade to a supported version. Cloud messages are now recorded in the trace when enabling the logging level to TRACE on the /System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.Cloud object. 

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 When viewing License Information, the Activated count still shows 0 for all features. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation License Server Cause There are multiple causes for this, as we are aware: Running Demo license License Server not running / uninstalled.  It is possible to activate licenses and then uninstall the License Server, and licenses will still be active and available to EBO components.   Firewall setting Recently, we have located an issue where multiple paths exist for the License Server in the Windows Registry. The specifics of how this occurs is still unknown, but it has been seen on a few installations.   Resolution Before starting, remove the demo license and restart the license server.  The systems, that is, the Enterprise Central/Server, will continue to run until the servers are restarted.   This will be necessary after completing the registry reset.    SBO License Server Reset Has been updated to check the known locations of the registry and provide the ability to make these entries the same as those entered in the License Administrator      A pop-up will appear during the initial running of the Reset Tool to indicate this, as shown below.   If the tool is unavailable or you wish to check this manually, then a Windows Registry search for the key TACLIC_LICENSE_FILE and its data should show its value and indicate the different (or the same) paths. Updating the TACLIC_LICENSE_FILE data to match the License Server path shown in the License Administrator should resolve the issues.     SBO License Setup This registry check is also included in the SBO License Setup tool.  In this instance, it automatically details the changes.  After selecting OK (in the screenshot below), you'll have the option to Apply (or cancel) any of the changes applied by the tool.        

Issue The properties of any server, Enterprise Server or Automation Server, in SmartStruxure has a Communication tab that will list the IP addresses of all associated servers on the network. Changing the IP address of an AS requires every other AS to know about the change in order to preserve any server-to-server communication. In the example below, the system has been engineered in-house on a 10.10.x.x network domain. It was then moved to site where the domain of the ES and all AS were changed to 10.159.x.x. Viewing the Communication tab on the ES shows all IP addresses have been properly updated: However, if the DNS/IP Address column is viewed from the Communications tab of one of the Automation Servers, the results vary as to which IPs have been properly updated: Automation Server A Automation Server B Automation Server C If there is any communication between two Automation Servers, and the IP addresses have not properly updated, then communication between them will break. 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 Building Operation Edge Server - Standard Cause Any change to an Automation Server's IP address must be represented in the Enterprise Server (if there is one). It must also be updated in all associated Automation Servers. It is best practice following the change of any IP address on the system to perform a refresh of the addresses from the Enterprise Server. Note: This is also applicable in a network with Enterprise Central hosting Enterprise Servers. Resolution Right Click on the ES. Select Advanced>Repair Server Communication. Refer to: Repairing EcoStruxure BMS Server Communication

Issue How to identify what ports are being used on a PC. Product Line All product Lines. Environment Any Windows OS Cause Running multiple applications on the same PC without managing TCP/UDP port assignments can lead to conflicts. Resolution TCPView will help you identify all ports and services to each application. Download from Microsoft's website http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Detailed instructions are available at the site.

Issue Can an Automation Server operate as an MSTP device on a third party BACnet MSTP network? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Want to connect an Automation Server to a 3rd party system as an MSTP device, is this supported? Resolution An Automation Server operating as a device on a third party BACnet MSTP network is NOT a supported solution. An MSTP network needs to be managed and usually accessed from a network master, the AS is designed to be that device. The Automation Server is supported as the management and routing device for an MSTP network. From the PIC statement, an Automation Server will operate as a MSTP Master.

Issue Continuum i2 and b3 devices share the same hardware platform, however, power consumption on the devices IO Expansion Port differs depending on the communication protocol firmware (Infinet or BACnet) running in the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment All i2 devices All b3 devices Cause Even though the hardware of an i2 device is identical to that of its counterpart b3 device, the difference in firmware causes variation in power consumption on the device's Expansion IO port, specifically, it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  Now that conversion of devices from one protocol to another is occurring in the field, it has become evident that there are cases where the 180 mA limit is exceeded in an i2 device without any negative results, but once the i2 device is converted to a b3 device, all IO on the expansion port stop working. Resolution Before converting an i2 device to a b3 device in the field, it is crucial to review the Expansion IO Datasheet (attached) to ensure that the configuration does not exceed the specified power consumption limit. If the configuration exceeds the 180 mA limit, take the following steps: Remove any additional xP module causing the limit to be exceeded. Reconfigure the xP modules to ensure that the configuration does not consume more than 180 mA.

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 Services for assistance. Issue When upgrading to 1.8.1 a Xenta Central Schedule that resides outside the LonWorks network it is not upgraded to the current version. If the upgrade is attempted it breaks all the Xenta time schedule bindings with the Xenta Cental Schedule. Product Line EcoStruxure Building Operation   Environment StruxureWare Building Operation 1.8.1   Cause During the LonWorks Pre-upgrade only the objects under the LonWorks networks are upgraded. If the Xenta Cental Schedule is located outside the LonWorks network this is not included in the upgrade process. Resolution Options to resolve this issue. Before upgrading to 1.8.1 If the site uses Xenta Central Schedules, then use the server Hotfix 1.8.1.5101 to upgrade all the servers. Please contact Product Support and request Hotfix 1.8.1.5101. After upgrade to 1.8.1 There are two options in this case: You can delete the Xenta Central Schedule and add a new Xenta Central Schedule. You are then able to bind the Xenta Schedules to the new Xenta Central Schedule.   If there are many Xenta Schedules that refer to a Xenta Central Schedule you can use the export function to resolve the problem as shown here Export the  Xenta Central Schedule as shown here Once you have exported the Xenta Central Schedule you need to edit the exported XML file with Notepad++ and change the Xenta Central Schedule attributes from "lon" to "lon2".  This is what the change should look like Once this change has been made the XML File can be saved ready for an import to the Server. Delete the existing Xenta Central Schedule from the database, making sure you check the box keep references. Then import the edited XML to the server and this will re-establish the Xenta Central Schedule binding with the Xenta Schedules.

Issue Opening the Vista SmartStruxure Interface setup, found in the status box, message "service not found" is displayed. Product Line EcoStruxure Building Operation Environment TAC Vista server Vista SmartStruxure interface Cause Some dll may be missing causing the service could not start. Resolution Manually run the VistaInterface execution file. By default TACVistaSmartStuxureInterface.exe file is stored in C:\Program Files\Schneider Electric\TAC Vista SmartStruxure Interface 1.0.5. Double click on the TACVistaSmartStuxureInterface.exe file, if the service could not be started, it will pop out an error message window. If it is a dll file missing, can find the corresponding dll on the internet, and solve this issue. If the error message shows some other error, please make a copy of the error message and contact the local support team for further assistance.