Issue When attempting to log into a remote Enterprise Server using EcoStruxure Building Operation WorkStation, the following error is displayed: “No valid client license available. (Error -5: No such feature exists.)” This occurs despite the Enterprise Server having available client licenses   Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation  EcoStruxure Building Operation License Administrator Cause The WorkStation application is attempting to acquire a client license from the local machine’s default license server address ( @localhost ). However, the active license is hosted on the Enterprise Server, which is configured as the central license server. Since no license is available locally, the request fails with error code -5 . Resolution To redirect the license request to the correct server: Launch License Administrator On the WorkStation client machine, open the License Administrator utility. Modify License Server Address Navigate to the License Server Address field. Replace the default value @localhost with the IP address or hostname of the Enterprise Server hosting the license. Example: From: @localhost To: 192.168.1.100 Apply and Restart Save the configuration and restart WorkStation to apply the new license server settings. Notes: Ensure network connectivity between the WorkStation client and the Enterprise Server. The Enterprise Server must have the License Server service running and properly configured. Refer to the WebHelp documentation for detailed steps on configuring license server addresses  License Server Address 

Issue The Niagara 4 JACE's platform daemon fails to start making it impossible to login and configure using Workbench tools such as the Commissioning Wizard or Dist File Installer. The error within the serial shell typically indicates ... /proc/boot/ksh: niagarad: cannot execute - No such file or directory. Product Line TAC IA Series Environment Niagara 4 JACE-603 JACE-645 JACE-600E JACE 8000 Cause This can occur as a result of an Incorrect or failed upgrade or improper downgrade without first installing a clean distribution. Resolution Requirements - You will need the following to complete the recovery steps: A terminal emulator such as PuTTY A SFTP client such as FileZilla Serial-Shell cable for your JACE hardware model (specified in the .PDFs below) The Niagara 4 Clean Dist file for your JACE hardware A zip file utility such as 7-Zip The hardware and startup documentation for your JACE model (provided with Niagara 4 installer) Obtain recovery files from the Niagara 4 Clean Dist File for the matching hardware: The clean dist files can be found in your Niagara4 $system_home directory, or in your Niagara 4 image files under the cleanDist directory or in the overlay\cleanDist directory. Open the .dist file for your JACE's platform using a zip utility like 7-Zip and extract the zip/n4clean.tar.gz file. Also, extract the dev/shmem/n4-xxx.image file, where xxx will be different, depending on the JACE's platform type. JACE 300 ... qnx-jace-n4-npm3xx-etfs2048-clean.dist JACE 600 ... qnx-jace-n4-npm6xx-etfs2048-clean.dist JACE 600E ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 603 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 645 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 700 ... qnx-jace-n4-javelina_booke-etfs2048-clean.dist JACE 8000 ... qnx-jace-n4-titan-am335x-clean.dist Make a Serial Connection to the JACE The .PDFs in the N4 documentation set describe how to make a serial connection to a JACE in the "system shell" section(s) of each document. Once connected, the controller will boot and display the "login:" prompt.  Enter your Platform credentials. After login, either a "#" or "$" shell prompt or configuration menu similar to the following is shown.   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011     dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255         inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------     1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot     L.  Logout     Enter choice:   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011   dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255             inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------   1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot   L.  Logout   Enter choice: Verify correct system time and update as needed The RTC time may not be correct if the unit has been unpowered for longer than the on-board capacitor backup period. Using menu ... the first item in the menu list allows you to Update System Time.  The current date/time is displayed. Enter the new date/time in the form YYYYMMDDhhmm[.SS].  Note that entering the seconds is optional. For example: 201801111420 for 11-Jan-2018 at 8:20am UTC or 8:20am CST. Enable SFPT The Secure FTP service is not enabled by default on a JACE.  Enable the SFPT from the menu above or the shell prompt (if required). Using menu ... the fourth item in the menu list allows you to enable SSH/SFTP.  Enable it now, using port 22. Once enabled, enter another choice, "sh" (without quotes).  This will give you the "#" or "$" prompt that you need. If you could not enable from the menu in the step above, manually start by issuing the command tsudo syssh_sshcfg at the shell prompt.   If the command fails, issue the syssh_sshcfg command.  If the command fails again, enter the following ... $ cd /sys/bin ... then enter $ ./syssh_sshcfg ... then enter Transfer the n4clean.tar.gz and OS Image Files using SFTP Client Using an SFTP client such as FileZilla, transfer the n4clean.tar.gz file previously extracted for the platform from the clean dist file to the JACE's /zip directory. If the transfer fails with a permissions error, issue the command tsudo chmod 777 /zip at the shell prompt and try it again. Next, transfer the .image file you extracted from the clean dist file to the JACE's /dev/shmem directory. Run osupdate From the login menu prompt, type sh.  This will exit the menu system and enter the shell mode.  At the "#" or "$" shell prompt, issue the command osupdate.  After a short delay, the shell prompt will return. Reboot the JACE Finally, reboot the JACE.  This can be done by issuing the command shutdown hf 0 at the shell prompt.  When the JACE restarts, the unit will automatically process the clean dist file.

Issue Missing Admin user password for the Loytec L-Gate Universal Gateway or LIP router. Product Line TAC Vista Environment L-Gate Universal Gateway LIP Cause Forgot the default admin password. Resolution The default login for L-Gate and the NEW style LIP (blue-grey in color) is: Username: admin Password: loytec4u The default login for OLD style LIP (off-white in color) is: Username: admin Password: admin

Issue What are the PinOuts for the RS-232 Connection of the older 1st Generation CX controllers to connect through Hyper terminal. Product Line Andover Continuum Environment Hyper Terminal Continuum CX Gen 1 CX9900 Continuum CX Gen 1 CX9940 Continuum CX Gen 1 CX9400 Continuum CX Gen 1 CX9410 Continuum CX Gen 1 CX9200 Cause Need to direct connect to a first-generation controller to configure its IP address and ACC Net ID. Resolution The Hyper Terminal cable needs to have the below pinouts. RJ Connector - - - - - - - - - - - - - 9 Pin RS-232 PC Controller Comm3 Pin 1 - DTR - - - - - - - - - - - - - Pin 6 - DSR Pin 2 - CTS - - - - - - - - - - - - - Pin 7 - RTS Pin 3 - CXD - - - - - - - - - - - - - Pin 1 - CXD Pin 4 - RTS - - - - - - - - - - - - - Pin 8 - CTS Pin 5 - GND - - - - - - - - - - - - - Pin 5 - GND Pin 6 - RD - - - - - - - - - - - - - Pin 3 - TD Pin 7 - DSR - - - - - - - - - - - - - - Pin 4 - DSR Pin 8 - TD - - - - - - - - - - - - - - Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you (download drawing). For the CX9200 and CMX controllers download the pinouts here. Download Command Terminal Reference Guide here

Issue There is no official internet download available for VisiSat documentation since the withdrawal of the Satchwell MicroNet and IAC products Product Line Satchwell MicroNet Environment Satchwell VisiSat Cause Documentation is no longer available for download. Resolution Further information and configuration details can be found in the following resources: VisiSat V1.2 Documentation Engineering Guide: Covers configuration for: IAC 400 IAC 420 IAC 600 IAC Touchscreen VisiSat V2.1 Documentation Engineering Guide (185 & 196 builds): Includes configuration for: MN300, MN440, MN500, MN620 MN350, MN450, MN550, MN650 MNLCD and MN Touchscreens Installation and User Guide Data Sheet Release Notes Attachments VisiSat V1.2 Engineering Guide.zip VisiSat V2.1 (185) Engineering Guide.zip VisiSat V2.1 (196) Engineering Guide.zip VisiSat 2.1 (196) Installation and User's Guide-0713.pdf VisiSat 2.1 (196) Data Sheet DS10202-0713.pdf VisiSat 2.1 (196) Release Note.pdf Related Articles MicroNet 100 Series Controller MLIs and Data Sheets MicroNet 50 Series Controller MLIs and Data Sheets Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue Users need specifications, setup details, and documentation for EH Series Humidity Sensors. Product Line  Field Devices Environment EH Series Humidity sensors Cause  Lack of readily available technical details and installation guidance for EH Series sensors. Resolution Refer to the following resources for complete specifications and installation instructions: EH Series Specification Sheet EH Series Humidity Sensor Installation and Operation Instructions Legacy EH Series Installation Guide (for models with two dip switch sets) Key Specifications: Power Supply: +15 to 36 VDC or 24 VAC Output Options (Field-selectable): 4–20 mA, 0–5 VDC, 0–10 VDC Measurement Range: 0–100% RH Accuracy: ±2% RH (model dependent) Operating Temperature: -40°C to +70°C Applications: HVAC systems, clean rooms, humidity-controlled environments. Additional Notes: Ensure correct dip switch settings for output signal selection. For legacy models, use the “Old EH Series” guide.

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1A Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1A Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1A Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Network administrator needs a document explaining the impact of GCM NIM communications on his Ethernet network. Environment GCM-86xxx with GCM-ETH-001 network interface Cause Customer wants to know impact of adding GCMs to his Ethernet network. Resolution GCM NIM configuration information and general Ethernet networking information is in the "NIM Networking and Configuration Guide", F-25955-4.  This document is available via the Publication Zone on iPortal. Bulletin 96-42, provides answers to frequently asked questions regarding the GCM NIM communications. NOTE: This information is based on the use of firmware version 11.2T in the GCM-NIM-001 interface.

Issue In EcoStruxure Building Operation (EBO) version 3.1 and later the password reset function have changed, how does it work, and what is changed from before? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Project Configuration Tool (PCT) Cause The changes have been done due to cybersecurity issues. The basic workflow is the same as before but the generation of the reset token has changed. Resolution IMPORTANT: The session ID is unique for each 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.  See online help topic: Copying the Session ID when Resetting the Password   To get a password reset token in version 3.1 and later you need to set the server in password reset mode(valid 24 hours)   For Automation Server(AS, AS-P, AS-B) this is done using the Device Administrator(DA), a USB connection is required between the computer and the server   For the Enterprise Server(ES) administrator privileges on the PC where the ES is installed are required. The ES is set in password recovery mode using the DA, the DA needs to be started as an administrator.   For the virtual server environment, Project Configuration Tool (PCT) tool is used. To get access to the password reset mode, the server needs to be started.     For detailed information please see the video: 

Issue MBus to Modbus TCP Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Mbus Modbus Cause How to read MBus devices into a BMS System using Modbus TCP Resolution There are different methods, but these are generally using a Modbus RTU / Mbus gateway and then converting it to Modbus TCP. The following ADFweb solution allows Mbus to be read directly into a Modbus TCP device. Click here for the datasheet.

Issue Satchwell FEU 4-port Unit Control Valve is obsolete. Product Line Field Devices Environment Satchwell FEU 4-port Unit Control Valve installations FEU4414 FEU4415 FEU4416 FEU4451 FEU4452 FEU4454 FEU4626 FEU4627 Cause Satchwell FEU 4-port Unit Control Valve requires replacement due to failure. Resolution Satchwell FEU 4-port Unit Control Valve may be replaced by Schneider Electric VZ419 series Unit Control Valve, although dimensional differences may apply.. It should be noted that VZ419 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required.   It should also be noted that any Actuator installed on the Satchwell FEU 4-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ419 4-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required. 

Issue In EBO 2022 or higher the "Semantic Engineering View" button is grayed-out in EBO WorkStation and "Semantic DB authentication failure" is shown in Alarm View. "Semantic Engineering View" button is grayed-out and "Semantic DB authentication failure" alarm   Semantic db authentication error   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause  EBO user that connects to the Sparql database has the wrong username and/or password. Resolution Make sure that the user configured in EBO semantic settings matches the user created in the GraphDB web interface. In WorkStation, in the System Tree pane, select the EBO server. Click the Control Panel tab. Click Navigate to Sparql database, this will open the GraphDB web interface. Login with the admin user account.  In the top right corner, make sure that correct repository is selected, default name is "nsp".  Go to Setup -> Users and Access. Edit user "nspService". Set a password for the "nspService" account and make sure it has access rights to the "nsp" repository then click save. In EBO WorkStation control Panel, open Semantic Settings. Set the password for username "nspService" to match the password set in the GraphDB interface. For more information, please refer to the GraphDB help: Secure GraphDB — GraphDB SE 9.10.0 documentation (ontotext.com)

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.

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 Need to verify whether specific network ports are open, as certain ports may be blocked. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspected network port blockage affecting communication between devices or applications. Resolution You can check if a port is open using the Telnet command in Command Prompt. ⚠️ Note: Telnet uses the TCP protocol only. It cannot be used to test UDP connectivity. 📌 Command Syntax: telnet [domainname or IP] [port] [domainname or IP] – The server's domain name or IP address. [port] – The port number the server application is listening on. 🧪 Examples: telnet 192.168.0.20 9001 → Closed port: Displays a "connect failed" message.   telnet 192.168.0.20 9003 → Open port: Displays a blank screen.   🚪 To Exit Telnet Session: Press Ctrl + ] Type quit and press Enter. 📝 Note: Telnet may be disabled by default on some machines. Refer to Microsoft's documentation for instructions on enabling Telnet.

Issue Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 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. Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue When adding License Entitlements via Device Administrator using the online method. After clicking activate, a "Communication failed" message is displayed:   Could not establish contact with License Server using SmartX Server Followed by a "License Operation Failed" message:   Add entitlement failed. License Server is offline. Error code: 41 Error message: CURL error: Product Line EcoStruxure Building Operation Environment Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When activating a SmartX Server license online, the SmartX server will try to connect to the license activation server to activate the license. If it cannot resolve the license activation server site name and connect, it will show up as offline. Resolution Make sure that the SmartX Server DNS is properly configured in the AS-P.  In Device Administrator select the Ethernet 1 Configuration tab. Check the Primary, Secondary, and Tertiary DNS settings If unsure of the correct DNS address, enter the Google DNS address of 8.8.8.8 or 8.8.4.4. The example below shows a local router address as the Primary DNS and Google DNS as the Secondary and Tertiary DNS.   To confirm that the SmartX Server can resolve the license activation server address Open a Console session on the SmartX Server in Device Administrator. Enter the command: ping schneider-electric.flexnetoperations.com If the DNS is correctly set in the SmartX Server, the result should look similar to that shown below: Note: Ensure that the ASP is fully connected to the Internet in order to perform Online Embedded License Activation. You need to be connected to the Automation Server using IP (Not via USB) to activate the embedded license.

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com