Building Automation Knowledge Base

Issue During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. Product Line TAC Vista Environment TAC Vista 5 Cause During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. PSS is creating demo license files with a monthly validity. Resolution Monthly demo license files are made by the Malmö PSS team, and may be requested from PSS. The "TS_OK" demo file is used for "Remote Desktop" applications, giving access equivalent to the demo file available for download from the The Exchange Download Center, usually valid until the end of the month. Additionally, a OPC Server license file with the same validity is also available by request. Evaluation license for TAC Vista 5.1 Demo TS License TAC Vista 5.1   More information can be found in Where to find Evaluation license for TAC Vista and Struxureware Building Operation.

Issue There have been questions about how the new EcoStruxure Building Operation 2.0 demo license works with the new scalable pricing structure. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and up All previous builds of SBO 1.9 and below Cause Understanding what the EcoStruxure Building Operation evaluation license will allow to function in the newer versions of the product.  Resolution The EcoStruxure Building Operation Evaluation License is a temporary license used when a database is being brought online before the permanent license has been deployed or on engineering laptops. All authorized Schneider Electric employees and partners can download the file from the Exchange Extranet. The file is updated every quarter as each one has an expiration date. The functionality of the demo license has not changed in version 2.0 and newer. This license file will still allow functionality and engineering of a database to take place as long as the file is valid. The only difference is the new warning banner that will be present until permanent licenses are installed.  Note: With the new scalable pricing starting in version 2.0, once the evaluation license is removed from the site, a license is needed for each Automation Server attached to the Enterprise Server.  More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info. 

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Cause The Enterprise Server and the Automation Server (ASP/ASB) do not synchronize time to each other, they must use an NTP server for synchronization Resolution The information below is mainly concerned with synchronizing the time setting but not the actual time.   Overview To synchronize the server times an NTP Server will be required, they do not synchronize time with each other. A common misconception is that the Automation Servers sync time with the Enterprise Server via server-to-server communications. To find an external NTP server consult support.ntp.org . Alternatively, an existing internal NTP server can be used or consult Setting up a Local / Internal NTP Server to configure the Enterprise Server computer as a time server The time settings on the Enterprise Server are configured through the operating system settings on the computer where Enterprise Central is installed.  EcoStruxure Building Operation cannot be used to configure the NTP server for the Enterprise Server. Please refer to Network Time on WorkStation, Enterprise Server, and Enterprise Central To find the Network Time Protocol (NTP) configured on a WorkStation, Enterprise Server, or Enterprise Central computer open a command prompt and enter w32tm /query /peers. If configured the peer NTP server(s) will be listed If you need to ensure an NTP server is actually running on certain IP or DNS address, please reference Ensure IP or DNS address is valid NTP server The time settings on the Automation Servers can only be configured via the Workstation. As per the image they can be configured to look at an NTP server (1) or set manually (2). For synchronization, they must use an NTP Server. Please refer to  Network Time Server on an Automation Server on Webhelp Starting in version 1.5, the time adjustment depends on how much the Automation Server drifts from the NTP server. The faster the Automation Server drifts, the more frequently the time is updated.  Please refer to How often will an Automation Server ask the NTP server for the time?  If the time server is a URL, such as time.nist.gov, then it is critical that a Primary DNS is set for each Automation Server, and possibly a Secondary DNS via Device Administrator. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. Please refer to Configuring the Automation Server IP Address on Webhelp The time displayed for a server in Workstation (Properties -> Basic) will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of the server adjusted to client local time zone, while the fields below "Server time" represent the settings of the Automation Server.   How to synchronize date and time settings on multiple Automation Servers   IMPORTANT: Only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.   The synchronizing of multiple Automation servers can be achieved with a lead/shadow relationship. The primary and secondary network time server settings for connected shadow Automation servers are defined on the Enterprise server. Setting up the Primary and secondary time servers in the Enterprise Server only passes those configuration settings to the AS controllers, it does not send the actual time and date value.   Select the Enterprise server (1), click the Date & Time tab (2), select Enable (3) and enter the Primary time server (4) and, if used, the Secondary time server (5) the Automations Servers will use. Ensutre the time zone for the Enterprise Server is set correctly (6).   Save the settings  From EBO version 2.0 all Automations Servers are automatically configured to shadow the date and time settings configured in the Enterprise Server. To verify this expand the System folder of an Automation Server and select Time Settings -> Date and Time (1). Observe the Date and Time are Shadow-Read only (2), replicating the Enterprise Server settings. Attempting to change any of the settings, other than the Lead object (3), will result in an error. All the Automation Servers will be 'looking' to the same Primary (4) and Secondary time servers, i.e. they will all receive the same time and be synchronized Similarly, select the Time Zone (1) of the Automation Server in the System Tree; this will also be shadow-read only (2). The lead object is set to the Time Zone on the Enterprise Server (3) Before EBO version 2.0 the Automation Servers were not automatically set to shadow the Enterprise Server settings but this could easily be achieved en masse using Search . In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search (1) to find the date and time object of all connected servers. In the Search view select the servers (2) that require their Date and Time settings synchronized to the Enterprise Server, the Enterprise Server does not need selecting. Select the Time tab (3) and then click the triple dots (4) to navigate to and select the Date and Time object on the Enterprise Server (5)   You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers Note: To set up synchronization of the time zone settings follow the above search steps for date and time but search on Time Zone Tip/Tricks To see the time of on the Enterprise Server and multiple Automation Servers use the Search to find the Date and Time object (1). Individually select each server (2) and then drag the Date and Time object (3) into the Watch Window (4) It is the Automation Server that initiates the synchronization. To check the Automation Server communication settings select the Automation Server (1) and in the Communication tab (2) select the Enterprise Server (3) and make sure the Automation Server has the correct IP address (4) To check the Enterprise Server communication settings select the Enterprise Server (1) and in the Communication tab (2) select each Automation Server (3) and make sure the correct IP address is specified for each Automation Server (4).  If a firewall exists ensure that the ports are open so the Automation Server can connect to the Enterprise Server. Please search for the EcoStruxure Building Operation IT Reference Guide on Exchange for details Further Information Release 1.2.0 and higher Until the time is set, b3 data will not update in the Watch Window Until the time is set, BACnet COV will not be functional Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server To adjust the Automation Server time, time zone, and DST, access to the Automation Server is through a WorkStation

Issue When trying to run webLauncher.exe, an unknown error occurs. An error popup with a red X appears, and the Application will fail afterwards.   Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 / 9000 Cause With a recent migration to Web Launcher in 4.14 (launcher version 24.14.0.2), a bug has been reported in new installations. Any computer that is missing a folder named niagara storing the launcher's configuration info will encounter this issue. The folder is located, by default, in the following spot: C:\Users\<Windows username>\AppData\Local\niagara Resolution Go to the location of the launcher executable, and there will be a file named webLauncher_debug.exe. Running this once will create the necessary directory and the Web Launcher will be able to function normally. The default location of the executable is: C:\Program Files\Niagara Web Launcher This issue is known internally at Tridium as defect NCCB-68211, and it will be resolved with the release of Web Launcher 24.14.0.3 and later releases.

Issue The en1 network adapter is not an option for assignment when configuring an IP port Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series N4 Jace 9000 Building Operation Multi-purpose Controller / VAV (MP-C / MP-V) Building Operation Room Controller / VAV (RP-C / RP-V) Building Operation IP-IO Cause With the switch to Linux for the Jace 9000's operating system, some functions such as sensing adapters work differently when configuring a controller station.     Resolution In N4.13, we have added a new action to find adapters when Jace's are being pre-configured offsite. Start by confirming in the TCP/IP Configuration page that the desired port is configured and enabled. Make sure that some communicating device is connected to the desired port, exhibited by the port's lights on the unit. Examples include a workbench connection, a BACnet IP device/router, or another Niagara Device. Right-click on the "Link" component under the port, and select the "Query For Adapters" option. You should now see the port in the dropdown. Note: With N4.14, using the en1 as a DHCP server is possible.  If using this with BACnet IP MP, RP or IP/IO in Space Logic controllers engineering with Niagara, this is an important consideration for network applications.

Issue How does the dynamic updates property work in TGML? Product Line TAC Vista Environment TAC Vista 5.1.7 TGML graphics. Cause A graphic can contain numerous bindings to values that you want to be able to display in the graphic. When there are numerous bindings, reading the values can be time-consuming and can slow down the performance of the graphic. By setting the DynamicUpdates attributes in the Bind elements of the graphic to either disabled or enabled, you can control which values are updated (which values the graphic subscribes to) when the graphic is opened. Resolution Created a Bind object in the TGML Graphic Editor Look at the Properties for the object. Under Behavior, the property DynamicUpdates is set to Enable by default. This can be set to Disabled and a Script can be added in an appropriate object which follows the following format: Example - activate a binding by clicking on a button function Click(evt){ button = evt.getTarget(); //Identify the target that has been clicked. parent = button.getParentNode(); //Find the parent node. binding = parent.getChildRecursive(""); //Identify the binding to be activated. binding.setAttribute("DynamicUpdates","Enable"); //Activate the DynamicUpdate property. } A simple example is attached. Click to download DynamicUpdate.zip.

Issue Blinking red lights Solid red lights Blinking orange light Blinking green light Solid green light Environment Xenta Server Controllers 511, 527, 555, 701, 711, 721, 731, 911, 913 Cause The indicator lights on the face of the Xenta Server controllers can help explain the state of the controller in many different situations. Resolution A number of light-emitting diodes (LEDs) on the Xenta device indicate that the application program is running and when communication is in progress.    Fig. 1: LED diagram on the Xenta Server device.   Table1: LED description on the Xenta Server device.     Position Description 1 Neuron status indicator • Off – Normal mode • Red, blinking – Unconfigured mode • Red, steady – Hardware fault 2 Serial RS-232 B port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 3 Overall Run indicator • Green, steady – Normal mode • Green, blinking – Start mode • Red, steady – Fail-safe mode (see    description below) • Red, blinking – Unit fault 4 Serial RS-232 A port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 5 Serial RS-485 C port activity indicator. 6 Ethernet 10Base-T activity indicator Note • The LEDs for the RS-232 A interface (position 4) do not indicate communication when using the RS-485 A interface although internal port A is used for both.               Fig. 2: Internal serial ports and RS-232/485 interfaces.

Issue License needs to be activated or repaired but there is no Internet access on the computer that the license is being hosted on. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator  Cause There is an inability to move the computer to a location with Internet access, activate or repair the license, then move it  back to the site. In other situations the IT Department is so strict that they will not allow internet access on the computer just for licensing activation. Resolution SBO Offline Activation Tool There SBO Offline Activation tool posted on the Community outlines the step by step process to perform an offline license activation. It can be accessed here: SBO Offline Activation Tool. Click on "Instruction and Help" in the tool for the step by step process and other helpful videos/charts.  SBO Offline License Repair The same SBO Offline Activation tool used for activation can also be used to repair an offline license. Download the tool here: SBO Offline Activation Tool. After launching the offline tool, click on the "Special Operations" menu and click on Repair License.  If this does not repair the license, then please contact PSS for further troubleshooting assistance. 

Issue Unable to log into Workstation because the user password is unknown. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P, or AS-B) Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Project Configuration Tool (PCT) Cause The password for an Automation server or Enterprise server/Central has been forgotten. Resolution IMPORTANT: The session ID is unique for this session of WorkStation. You cannot close WorkStation until the password has been reset. If you close WorkStation, before the password has been reset, a new session ID is generated that cannot be used with the temporary password provided by your local Schneider Electric Buildings support team.       The following are the steps to populate the session ID, which is required for doing the password reset.   For servers with EBO older than V3.1.X In the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon.   This will populate the Session ID. Copy the Session ID.   For servers with EBO V3.1.X:   In Device Administrator, select the server you need to perform the reset to. Check the box and click the hyperlink   From the top bar select Password Reset Select OK when you get the “Password reset token created” pop-up Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.    For servers with EBO V3.2.X and higher In Device Administrator, select the server you need to perform the reset to From the top bar, select the “Edit Connection Password/Reset password” and press OK Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.   For servers within PCT 2.X Start the server Left click on the Server Menu  Select "Set password reset mode"  Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.    NOTE (for servers with EBO V3.1.X and higher)  For the Automation Server password reset, ensure that the Automation Server is connected to your PC machine via a USB cable. For the Enterprise server and Enterprise Central password reset, add the server to the Device Administrator using the “Add Server” button on the top bar. Please note even if you enter the wrong password, the Server would still be added to the Device Administrator.     After having the Session ID:   Send the Session ID to your local Schneider Electric Buildings support team Once PSS provides you with the unlock key In WorkStation, ensure that the Session ID is still visible, enter: User Name: admin Password: paste the result from the webpage Domain: Local and click Log On This will pop-up the Change-Password form Fill in the “old password” field with the unlock Key Put in a new password you want to use and then enter the new password in again. Click OK   NOTE:  When attempting to reset the password and unlock with the sessionid/temp password, you receive the error: "Your account has insufficient permission to use the system. Contact your administrator. "  Open a case with your local Product Support group and submit a request to unlock the user.   NOTE: WebHelp article 6749   The following video shows the password reset procedure for EBO older than V3.1.X. It covers most of the important steps for newer versions. Quick-Help video    

Issue Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see the below video demonstrating how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. Also please note the following: In the video the "Host address" in EBO is set to the IP address or DNS name\SQLserver instance like this: localhost\SQLEXPRESS. If the SQL server is not located on the same computer as the EBO server only use the IP address or DNS name and no instance on "Host address". The video demonstrates using the version 5 script when configuring the database in the MSSQL server, search External Log Storage - MSSQL Installation Script  to download the appropriate EBO version script. For the example query to manage user permissions download User Rights Script or see attached script.txt. If using MSSQL Express rather than the full MSSQL version it may be necessary to consult External log storage not working with SQL Server Express.    

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 Users may want to know how to perform the online activation of an embedded license  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause From Building Operation 2022, the Automation Server (Classic/Secure boot AS-B or AS-P) and features like Smart Drivers, SNMP notifications, Personalized dashboards, TimescaleDB, MQTT Publish/Subscribe, Modbus, Serial MS/TP, ES Connection, Server I/O, Field Devices, SAML Authentication, Zoning, and BACnet IP require a license. Customers need to know how to activate their embedded licenses to enable these features. Resolution This video will demonstrate how to Find the list of supported features by each activation ID. Activate an embedded license on an Automation Server Verify the embedded license status via the Device Administrator, Workstation, and the Flexnet operation license portal. Notes Check each activation ID's supported features using the part number or license description through the Features and Licensed Products Table.  The Flexnet operation license portal is a public FlexNet Login (flexnetoperations.com) accessible from anywhere with an Internet connection.  The Automation Server and the PC running the Device Administrator must have outbound connectivity to the license activation server over the Internet. Check the resolution section of this article Could not establish contact with License Server using SmartX Server - Communities to verify if the Automation Server has access to the Flexnet license activation server. For troubleshooting, refer to Embedded license activation fails. Web helps:  Assigning Licenses and Activating Licenses Online. An Embedded DEMO license is available for temporary use during project engineering and installation until you know each device's specific licensing needs. Please visit How to activate a demo license on an Automation Server at EBO 2022. If the Automation Server does not have access to the Flexnet license activation server (no Internet connection), you can perform the steps in the following article Offline activation of embedded licenses.  Please take note that starting from Building Operation 2023 version 5.0.3 and higher, Automation Servers are no longer required to be connected to the Internet. The Device Administrator can access the internet and manage communication and license activation for the 'offline' Automation Servers.   A shorter version of the Online Activation of Embedded Licenses for Automation Servers-Digital Job Book (nampss.com). is available on the NAM PSS site. (Note: Registration for access to this site may be required.)  

Issue There is no quick and efficient way to configure a TAC Xenta 102-AX controller after adding it to a LonWorks Network in Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC Xenta 102-AX controller is typically configured using the LNS plug-in that is currently not available in version 1.4.0 and newer. Resolution As an alternative to the LNS plug-in, the graphic page available on the Community [1] can be used. This zip file contains the TGML graphic, binding template, and a full import file with a Xenta 102-AX that is already bound. [1] Xenta 102-AX SXW TGML Plugin v1.6.1 (SBO 1.8.0 to 1.9.3) Example Plug-in TGML Graphic Page

Issue Unable to establish communication between the enterprise and automation servers through the TCP Port 4444. Values are not being passed between the enterprise to the automation servers or between automation server to automation server. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Windows Firewall is not allowing inbound or outbound information from passing through the TCP port 4444. Resolution First download and run TCP View. With TCP View running, sort the list by the Local Port and find all devices that are talking on port 4444. If the automation servers are in a state of LISTENING then rules must be created to allow communication. Copy the file path of SE.EnterpriseServer.exe in order to create the rules. This can be found by right clicking on one of the SE.EnterpriseServer.exe process > Process Properties... (C:\Program Files\Schneider Electric\StruxureWare 1.2\Enterprise Server\bin\SE.EnterpriseServer.exe) If the automation servers are in the state of ESTABLISHED, then take a look at Binding between ES and AS or two AS shows Unresolved and "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 for more troubleshooting help.   Change Windows Firewall Settings to Allow Programs Go to Start > Control Panel. Click on Windows Firewall. Click on "Allow a program or feature through Windows Firewall" on the left hand side of the window. Find "StruxureWare Building Operation" in the list of programs and make sure Home/Work and Public networks are selected.  Note: If you do not have permission rights to make changes in this area of Windows, move on to the next section where you can set up inbound and outbound firewall rules.   Creating Inbound and Outbound Windows Firewall Rules Go to Start > Control Panel.  Click on Windows Firewall. Click "Advanced settings" on the left side of the window. Select Inbound Rules on the left side of the window and then click New Rule... on the right side of the window. On the first screen of the New Rule Wizard, choose Program. Click Next. In "This program path:" either browse to SE.EnterpriseServer.exe or paste the file path that was copied earlier from the TCP View into the box. Click Next. Select the option to "Allow the connection". Click Next. Leave Domain, Private, and Public checked unless otherwise desired. Click Next. Name the rule StruxureWare. Click Finish. Select Outbound Rules on the left side of the window and then click New Rule... on the right side of the window. Follow steps 5 through 9 to create the Outbound Rule. Note that the SBO Firewall Config tool on the community can be used to automatically create the required firewall rules.

Issue Enterprise Server will not start due to no valid license file error: "nsp.csc.licensemanager No valid Enterprise Server license found. Terminating server." or Cannot find license file. (Error code: -1) Product Line EcoStruxure Building Operation Environment Building Operation Software Administrator Building Operation License Administrator Building Operation Workstation Cause Enterprise Server is not started and states no valid license file is found. License Server is installed on the same computer and has valid license(s). Similarly, WorkStation may not start even with a License Server installed with a valid license. If you get error -1, it means that you didn't enter the required @ before the license server address. Resolution In general, any licensed Building Operation software (Enterprise Server, WorkStation, Editors) needs to know where the license server is located. That means that the license server path needs to be entered on any PC having licensed Building Operation software installed. The "License Administrator" part of the license installer can be installed on any PC, and the license server address set using the administrator. The license server itself does not need to be installed on all PC's, but only on the PC hosting e.g. the Enterprise Server. The IP or DNS name of the PC hosting the license server is entered with an initial @, e.g. if the IP of the license server PC is 1.2.3.4 you enter @1.2.3.4 Checkpoints Remember to enter the license server address starting with a @. For example, don't use "localhost" but "@localhost". Is your evaluation license current? If not, download from EcoXpert Extranet Check that antivirus software is configured to allow the operation of the license server. (refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96)) Reboot the machine where the License Server is running. It has been observed in some cases where the error 'No valid license or Cannot find license file error' appeared after an upgrade that rebooting the machine solves the problem. Check to see if there are multiple versions of the License Server installed on the machine. If multiple versions are installed, make sure to only run the highest installed version as a Windows Service. All other License Server and License Administrator software should be uninstalled from the machine.

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue How to remove an unknown Embedded Demo License Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Device Administrator v4.0.5 (EBO 2022) and below Cause The Embedded Demo Licenses are handled from the Device Administrator software. However, if the installed Embedded Demo License in the SpaceLogic servers does not comply with the file in the Device Administrator, the installed Demo License could not be removed. Resolution Instructions shown in the video below are for EBO 2022 (v4.0.5) and below. In the later releases EBO 2023 (v5.x) and above, a feature now allows the Demo licenses to be returned from selected servers.  See WebHelp topic Returning All Demo Licenses from the Selected SpaceLogic Automation Servers  For any License activations/returns to occur, there must be a trusted state (Certificate State) between the server and Device Administrator. Ensure that this is in place before attempting either resolution. For more info, see Certificates Managed using Device Administrator   If this function does not work, you can attempt the manual file name manipulation described below.    To check the name of the installed Embedded Demo License, log in to the SpaceLogic servers from Workstation. Navigate to System, LicenseManager, LicensingMetadata, ClientMetadata, Product 0. In ProductID, you will see the filename of the actual file.   Rename a Demo license file and import it into Device Manager to uncheck the selected Demo License file.   At the end of this session, you will be able to: Remove Unknown Demo License in SpaceLogic servers        

Issue How to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator is not connected to the internet. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause Device Administrator is used to manage licenses on SmartX servers The following features of a SmartX server need licenses: SmartDrivers SNMP Notifications Personal Dashboards TimescaleDB MQTT Resolution Building Operation 2022 Note: The offline entry of the Activation-ID License items is not all visible - ONLY the first 5 are shown.  This makes entering this information impossible. This has been fixed in the Maintenance Release 4.0.2 of the Device Administrator.  After activating the embedded license offline and transferring this license to the servers, a license violation may be still shown.  The license status should update within 24 hours.  Perform a warm start and then a Refresh License Status on the selected servers to force this update.   If an error is seen in the progress status indicating ASEmbeddedAPI internal error during the offline activation, check the following Embedded license activation fails - Communities to correct the corrupted storage.   This video will show how to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator and/or the server is not connected to the internet. IMPORTANT NOTES: You need to be connected to the SpaceLogic (SmartX) Server using IP (select +Add server on Device Administrator).  It cannot be connected via USB. Ensure always to run the Device Administrator with admin privileges. Select "Run as administrator." Should Device Administrator be running on a computer that has internet access, then there is no need to swap between online/offline computers.  The offline activation process can be run from the same Device Administrator with no need to change computers.  The offline workflow is always the same and detailed on the webhelp topic Offline Activation of Licenses Workflow  The video below shows version 3 licenses. In Version 4, there are a few more license features and quantities required to enter.  The following article may assist in entering this information. License Features list for version 3.0 and 4.0 Product names     At the end of the video session, you will be able to: Create a request file using the Device Administrator on an offline (to the Internet) computer. Activate request files from the Device Administrator on a PC connected to the internet. Send response files to the SmartX Server from the offline Device Administrator.

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 Orphan alarm exists in the Enterprise Server database and acknowledgment of the alarm does not remove the alarm. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v. 2.0.3 or lower,  Cause Backup of the Building Operation database that includes historical data will include the alarm that needs to be purged. IP changes or other reasons can contribute to alarms being orphaned. Resolution Note: Version 2.0.4 and from 3.0.2 and higher there is a built-in solution called Alarms Integrity Check which can be run to verify all alarms and purge any that are no longer in the system.     In order to completely purge an alarm database, it is necessary to delete the PersistedData.dat file that stores this information in the database. Perform an ES and AS full backups Using Building Operation Software Administrator click the "Stop Service" button for the Enterprise Server. Image from Windows XP Image from Windows 7 / 10 Browse to the database path listed in the Building Operation Software Administrator tool. Windows 7/10: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 2.x\Enterprise Server\db Windows XP:  C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db Browse to the Persistent subdirectory Move/Delete the PersistedData.dat  file Click the "Start Service" button in the Building Operation Software Administrator tool. When the Enterprise Server restarts and you log in the orphaned events will be removed and any currently present alarms will return to the Alarm window with their proper status and assignment. This process causes a re-evaluation of alarms on the ES and fetches all the alarms from each AS. This can take a few minutes and may cause some slowness in the system. Note 1: Historical perspective of previous alarms, operator actions, or other data recorded in the Event Log will be lost in this process.