Issue Clicking on a URL in Workstation gives the error message "Navigation to the webpage was canceled". Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The website owner has added additional code to prevent their webpage from being displayed in a 3rd party application e.g. EBO. However, the webpage can be viewed in a web browser e.g. IE, Chrome or Firefox. This additional measure makes use of a feature called X-Frame-Options and is used to prevent 'clickjacking' and prevents embedding in other websites. In 2009 Internet Explorer 8 introduced a new HTTP header X-Frame-Options which offered partial protection against clickjacking and was shortly after adopted by other browsers (Safari, Firefox, Chrome and Opera). The header, when set by the website owner, declares its preferred framing policy: values of DENY, SAMEORIGIN, or ALLOW-FROM origin will prevent any framing, framing by external sites, or allow framing only by the specified site, respectively. See Mozilla article for further information. Resolution If a web site implements the usage of X-Frame-Options to limit which other web sites it can be embedded into, there is nothing to be done about that. It is the providers' decision, and cannot be circumvented. In Building Operation release 1.9 and later, there are two global policy settings used to protect Building Operation presented web content, so it is resilient against clickjacking. Option 1 - Enable external content to be embedded in WebStation This option must be selected to permit another web page to be rendered in a WebStation <frame> or <iframe>. To protect against clickjacking for all use cases, this option should be turned off. Option 2 - Enable WebStation to be embedded in another site This option permits Building Operation web pages to be rendered in a <frame> or <iframe> from the local server. If this option is selected with option 1, then there is no protection against clickjacking. The most secure and recommended configuration is when both options are turned off. However, when an application requires embedded web content, one or both these options can be turned on. Since this is a global policy, these settings will affect all embedded content. If only some content is required to be embedded then there is no solution or workaround within EBO unless the website owner can remove or change this feature.

Issue SmartX Living Space Sensor Touchscreen SXWSCDXSELXX display has a background color indication for the "Heating cooling status" setting in Workstation, but the Heat/Cool/Off colors Red/Blue/White are very faint and it is nearly impossible to tell them apart. The colors are a bit better when viewed from an angle, but when looking straight at the display they are very faint. The photos below show the states Cool (Blue), Heat (Red) and Off (White) in that order from left to right.       Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Cause Low color quality of the SmartX Living Space Sensor Touchscreen SXWSCDXSELXX display. Resolution This is a hardware limitation in the current version of the touchscreen display SXWSCDXSELXX. The issue will be resolved in a coming release of the display.

Issue Unable to control the field device with a Triac output. Product Line EcoStruxure Building Operation, Andover Continuum Environment Continuum b3 Controllers Continuum i2 Controllers Building Operation Multi-purpose Controllers with Triacs Cause Triac outputs cannot switch DC loads. Triac outputs require a minimum 30 mA load in order to switch.  Resolution If the inductive load draws less than 30mA a resistor needs to be wired in parallel with the switched load.

Issue SSC or EP1501 is bouncing offline and online Product Line Access Expert Environment Access Expert Controller Cause Not configuring the DNS suffix or misconfiguring the DNS IP or DNS suffix, may cause Access Expert to lose connection to the controller. Resolution Add in the DNS IP and DNS suffix for a local DNS server DNS resolution issues can happen when using a site’s internal DNS. It is recommended to use Google's DNS of 8.8.8.8 to resolve any names to our hosted servers. Per the documentation https://support.feenics.com/hc/en-us/articles/360019852374-Mercury-Controllers See the “Configuring a Controller for IP Client” section Note: You will need your Feenics login credentials. If the 2 options above do not correct the issue, increase the retry interval to 20 seconds. (5 is the default) If needed, as a test, configure a controller with the Host IP field as connect.feenics.com This will reach the V3 US stack

Issue The Continuum Database Transition Tool does not transition the doors even though they are present in the Continuum database being transitioned   Product Line Security Expert Environment Security Expert Server Cause Incorrect configuration of the Continuum Transition Tool Resolution In the 'Record Types' tab of the Continuum Transition Tool, there is a checkbox labeled 'Include Anti passback Programming' If the doors on the Continuum system are configured for anti-pass-back then the checkbox has to be ticked to match the Continuum configuration of the doors.

Issue Receiving warnings such as Import[SNMPv2-CONF] not found for mib [ACC-NC-ALARM-MIB] when loading EBO/Continuum MIB files into SNMP NSM tool Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Enterprise Server Continuum NetController II Cause Required base MIB files referenced in the IMPORT section of the EBO/Continuum MIB files not present Resolution The EBO/Continuum MIB files contain references on their IMPORT section to base MIB files that are commonly included with the SNMP tool used to compile the MIBs. (See screenshot below) Those files are typically included/installed by the SNMP NMS tool, in cases where the tool does not include the base files they must be located and either loaded manually before loading the EBO/Continuum MIB or placed at the appropriate folder for the tool being used. For example, when using MG-SOFT SNMP MIB browser, the tool places the base MIB files @ C:\Program Data\MG-SOFT\SMI Modules\MIB Modules\SMI

Issue Will public signals in TAC Xenta show up in Echelon Lonmaker? Will AI, DI, AO, DO, PVR, PVI, PVB blocks show up in Echelon Lonmaker?  Product Line TAC Vista Environment TAC Menta LonMaker or NL220 Xenta 30x, 401, 28x Cause Public signal are proprietary and can only be viewed from Schneider Electric products such as TAC Vista Workstation or EcoStruxure Building Operation. Resolution The answer to both questions is no. Only SNVTs are displayed in Echelon Lonmaker, and the SNVTs have to be added in TAC Menta and then downloaded to the TAC Xenta devices.

Issue Which Java version is supported for Xenta servers version 5.1.9? Product Line TAC Vista Environment TAC Xenta Server Cause Java  is used for TGML Graphics in the dynamic TGML viewer in a TAC Xenta Server or in TAC Vista Webstation. Resolution The recommended java version for TAC Xenta Server 5.1.9 and TAC Vista Webstation 5.1.9 is java 1.7 update 51. If you are currently running a version prior to 1.7 update 51, it is recommended to upgrade your java installation to the recommended version.

Issue How can the IP address of an MPX controller that is configured for DHCP be determined when there is no attached display Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to know the IP address of an MPX that does not have a display for troubleshooting and commissioning multiple MPXs,  Resolution

Issue Is it possible to command the outputs on an MP-C controller before it has been commissioned in EBO? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to verify the field device wiring and control prior to the MP-C controller being brought online. Resolution The following video demonstrates how temporary outputs can be created and controlled in an MP-C controller without the use of a front end system.

Issue When a TGML graphic is opened from Webstation red crosses is shown on the whole graphic or sometimes over certain components. After a few seconds the red crosses disappear. Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 2.x and 3.0.x Cause The red crosses only appear when values from field bus devices are displayed in in the TGML graphic, and only in Webstation version 2.x and 3.0.x. When the graphic is opened from Workstation no red crosses are shown in the graphic. Resolution This issue is fixed in EBO version 3.1.1

Issue The system memory usage for an Automation Server slowly increases over time and finally the AS restarts with a system alarm "Server restarted because of low memory"  System memory usage for the AS (In this case an AS-B): Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause One reason for this issue to occur is that two Enterprise Servers (ES) are running with the same database and are connected to the AS at the same time. This is not a common scenario but can happen by mistake if for example an old computer with an ES installed is switch on. The ES runs as a service and can be running in the background on the computer with no one noticing it.  Resolution Stop the Enterprise Server that is started by mistake.

Issue Analog consumer values referencing the temperature of a SmartX Sensor shows in metric units when setup to display imperial units. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Building Operation Multi-Purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller Building Operation IP-IO Building Operation SmartX Sensor Cause SmartX Sensor is configured in the device as metric measurements (SI System). Setting Fahrenheit in Display of SmartX Sensor does not convert the values from metric to imperial. Consumer values are configured to use the object being referenced and do not convert measurements. Unit conversion is done within the binding and not the device itself. Resolution There are two workarounds: Option 1: Create an analog value and then bind to consumer value Step 1: Create an Analog Value. Setup unit settings to (°F) and Save.  Step 2: Bind Analog Value to temperature from SmartX Sensor and Save Step 3: In the created Consumer Value, bind the Analog Value to the input binding reference and setup unit settings to (°F) and Save   Option 2: Bind to Consumer Value directly and keep the value in metric Step 1: In the created Consumer Value, bind the SmartX Sensor temperature to the input binding reference Step 2: Setup unit settings as configured in the object (°C) and Save.

Issue During startup of the Lon FlowBalance software, an error is displayed indicating that the program "cosmo.exe" failed to register Product Line TAC IA Series Environment MNL-FLOW-BAL 3.0 - MicroNet Software Microsoft Vista, Windows 7, and Windows 10 (64-bit installations) Cause The software installer installed the software into the C:\Program Files (x86) folder on the Windows system drive. When the software is started up, it needs to initialize some internal driver and data modules. These modules are expected to be in the C:\Program Files\TAC folder, however, that folder was not created during the installation of the software. The LON FlowBalance version 3 software is not supported on 64-bit versions of Windows because fully-supported Echelon (LON interface) drivers are not yet available. Resolution Reinstall the LON FlowBalance software on a computer or virtual machine running Windows XP, Windows Vista (32-bit) or Windows 7 /10 (32-bit).

Issue Some connectors appear in red on the Workplace Tech Visio drawing.  Connectors cannot be bound to objects. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Microsoft Visio  Cause Drawing objects become placed off the normal boundaries of the Visio drawing page causing file corruption.  This can occur during improper file saves, Visio crashes or for unknown reasons. Resolution

Issue Workplace Tech or Workplace Tech Editor is crashing when accessing a specific Visio file. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Cause There are a number of possible issues with the Visio 2013 and Visio 2016 files when running in Compatibility Mode.  Compatibility Mode is required for Workplace Tech and Workplace Tech Editor since they are both designed to use the older .vsd file format.  The mentioned Visio versions both use .vsdx as a native file format. Resolution

Issue All efforts to move a Continuum Virtual License from one host machine to another are unsuccessful. Product Line Andover Continuum Environment Continuum Cyberstation Cause The license type is not shown as Re-hostable in the Sentinal Admin Control Center webpage.   The license type is not shown as re-hostable after applying the Re-hosting upgrade activation file received from Andover Upgrade Services.   The error Invalid Recipient information, process canceled! is displayed when entering the recipient id file (.id) in the RUS Key Utility.   The HaspRuntimeForContinuum.exe is the wrong version. Resolution Contact Andover Upgrade Services and provide them with a new host information file (.c2v) produced using the RUS Key Utility. On the host from which the license is to be transferred... HaspRuntimeforContinuum.exe is the most current version available on Exchange. Rus Key Utility is the latest version available on Exchange. Contact Product Support Services for assistance. On the host the license will be transferred to... The most current version of HaspRuntimeForContinuum.exe must to be installed prior to using the RUS Key Utility to generate the recipient fingerprint file (.id). The HaspRuntimeforContinuum must be installed As Administrator. On the host licensed host… HaspRuntimeforContinuum.exe is the most current version available on Schneider Electric Exchange.   A demonstration of the rehosting process can be viewed here.

Issue Changed MNL controller application engineering units to Metric (Celsius temperature) using the hardware wizard. After downloading the modified application, the setpoints and setpoint range on the MN-Sx sensor are still reading in degrees Fahrenheit. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software. I/A Series MNL I/A Series MNB Cause Changing the engineering units from English to Metric using the Hardware Wizard does not alter the values already configured for the setpoints or setpoint ranges in the MN-Sx sensor. The standard applications have predefined setpoint values and setpoint ranges based on the application type and MN-Sx type. These setpoints and setpoint ranges are configured with values appropriate for the operation of the controller using English engineering units (Fahrenheit temperatures). When the controller's engineering units have been changed to Metric, the appropriate temperature setpoint values and temperature setpoint ranges must be entered via the appropriate screen of the Resolution After using the WorkPlace Tech Tool Application Wizard to change the controller's application engineering units, the entered values for any setpoints and setpoint ranges must be reentered as numbers appropriate for the new engineering units. The application template files are configured for English (standard) engineering units with temperatures in Degrees Fahrenheit. For example, the default space temperature setpoint is 70 degrees. By default, the controller is configured for English engineering units, resulting in the space temperature setpoint is 70 degrees Fahrenheit. Changing the controller engineering units to Metric will result in the default space temperature setpoint being 70 degrees Celsius unless the setpoint and setpoint range is redefined using the Hardware Wizard.

Issue When attempting to start the Enterprise Server, the user receives the following error message: "Windows could not start the Building Operation Enterprise Server service on Local Computer: Error 216: 0xd8" Product Line EcoStruxure Building Operation Environment Microsoft Windows Building Operation Enterprise Server Building Operation Enterprise Central Cause Windows error 216: 0xd8 means "The version of %1 is not compatible with the version you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher." It is likely that this error is being received due to the EBO Enterprise Server/Central being installed on a 32-bit Windows Operating System. Resolution Beginning in EBO 2.0 it is no longer supported for the Enterprise Server to run on a 32-bit Operating System. Reference the Enterprise Server Specification Sheet for the appropriate product version you are using to find the list of supported Operating Systems. The Enterprise Server/Central should then be installed on one of the supported 64-bit Operating Systems.