Issue After configuring the system per Setting up a Local / Internal NTP Server, the Automation Server's time would not sync to the local NTP computer's time. Wireshark capture shows a 'Root Dispersion' greater than 10 seconds. In the screenshots below, 10.169.90.13 is an Automation Server (NTP client), and 10.169.90.6 is the NTP server. CLIENT REQUEST SERVER REPLY This behavior of adding 10 seconds to the root dispersion is only observable when using the internal clock otherwise it is 0. This appears to be the intended behavior by Microsoft so that this NTP server would rank lower if using multiple NTP servers that might have more reliable time. Product Line EcoStruxure Building Operation Environment Automation Server (AS) Network Time Protocol (NTP) Cause The NTP client in the AS ignores the time sent by the NTP server if the root dispersion is greater than 'X' seconds (not known at this time) Resolution In the Windows registry of the machine being used as the time server, make the following change:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalClockDispersion The default for this key is “A” in hex. Change this to “0” and then restart the Windows Time service.  Do this by running the following command net stop w32time && net start w32time. Here is what Wireshark shows after the time has been synchronized. SERVER REPLY

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation 1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After:   NOTE Similar steps can be used to convert b3 device to i2 device, but once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost  

Issue How to get server date and time into a datetime variable. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building  Operation Enterprise Server Cause Documentation Resolution Create a 'Value' object of type 'Time Stamp Value' in the server. Right click on the server's name and select 'Edit bindings' Find the time stamp value created in step 1 in the object tree on the right. Bind the value of the time stamp object to the server's time as seen in the screen shot below.

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue When creating an ETL task the "Run Once" option works, but when configured to run as a service, it doesn't work and an error occurs in the error log: 2015-05-22 17:13:59,069 ERROR ETLEngine (TaskName) - Thread ID (119) - Power Monitoring Expert Load Task: Task Power Monitoring Expert Load Task failed System.ApplicationException: Failed to populate the MetaDataSet. ---> System.Data.SqlClient.SqlException: Cannot open database "ION_Data" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'. Product Line EcoStruxure Building Operation, Other Environment Power Monitoring Expert Energy Expert (formerly Power Manager) ETL Tool Cause When testing the ETL task using "Run Once", the Windows account currently logged in, will be used to access the SQL database. However, when the same Task is then configured to run as a service, the account configured on that Service will be used to access the SQL database instead.  By default that account is the built-in account 'NT AUTHORITY\SYSTEM'.   The Position values for all of the mapped trend logs are set to an unreasonable timestamp. The timestamp is either very old or a date the preceeds the oldest values in the database.  Resolution Changing the Windows system account for the ETL service Either give the system account access to the database, or change the account used to run the service. Correct/Adjust the timestamp values in Positions tab of ETL The timestamps can be changed all at once by setting the Initial value field at the top of the "Positions" window in the ETL tool. 

Issue What type of objects can be viewed using "Edit in Spreadsheet" mode Product Line EcoStruxure Building Operation Environment Edit in Spreadsheet mode Building Operation WorkStation Cause The objects that can be edited in Spreadsheet mode vary depending on the device or object you are viewing Resolution When you are viewing the AS IO Bus or an AS IO module, then clearly the only objects that cab be configured are Points. Below you can see the "IO" tab, but the "New" tab is greyed out. When viewing a "Folder" in an AS then possible tabs are "Alarm", "Value", "Folder" or "Trend". Below this can be seen (v1.3) LON device, Modbus Devices etc. will allow different access via the spreadsheet mode. This will vary for different versions If you need to find out what spreadsheet access is possible with your chosen device/folder, then it is best to navigate to the relevant Object, folder or device, enter Spreadsheet mode, then check what tabs are available when "New..." is select NOTES: If there is only a single possible spreadsheet object type, then even if there are zero of these object types created, then a blank spreadsheet is shown. If there is more than a single possible spreadsheet object type, and none of these object types are created, then no blank spreadsheet is shown. "New..." needs to be selected. When a row is selected, then an entry modified, all the text data in that row that is visible will be modified. Most EBO objects can be edited using Spreadsheet View with the exception of BACnet Objects. It follows that all objects that exist within MP/RP series controllers cannot be edited in Spreadsheet View as these are all BACnet Objects (This would include Modbus objects within the RP controllers that are actually BACnet objects) For further information refer to the Spreadsheet Overview EBO Webhelp topic  

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue When discovering the SLP Series Living Space Sensors they show up in the BACnet discovery summary as Non-conformant. Attempting to add this non-conformant sensor results in a WorkStation error similar to the following:  Validation Error Workstation Error in "~/BACnet Interface/MSTP Network/Living Space Room Unit 4E5932F5_«1»_07/ForeignAddress". Property value "<device, 10000>" already assigned to "~/BACnet Interface/MSTP Network/SLPSTC2/ForeignAddress". COML Validator0 Product Line EcoStruxure Building Operation Environment BACnet MSTP Living Space SLP Series Air Quality Sensors Living_Space_REV2.05.21 Cause Building Operation does not allow duplicate BACnet IDs and hence, during discovery, if a device is found with a BACnet ID (Object Identifier) the same as an existing device it shows as a non-conforming BACNet device. The default device ID for SLP devices should be equal to (Vendor ID * 1000) + MAC Address. Where vendor ID is our Schneider Electric BACnet vendor ID = 10 and the MAC address is unique to each devices MAC address DIP switch setting. This will be corrected in a future release of the Living Space firmware.  Until corrected, and since the Device ID is a read/write attribute the customer is able to change it to avoid duplicates on the bus. Unfortunately, Building Operation does not currently have a method to write a new device ID. Resolution The current workaround is to use a third-party BACnet Explorer such as Yet Another BACnet Explorer (YABE) to write a new device ID value. Once the new ID has been updated the SLP device can then be rediscovered within Building Operations'. 

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate with SmartStruxure Script programming Environment b3 AS ES ASP ASB MSTP bacnet Cause Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate or cannot be used with SmartStruxure Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   * New v4.0 features are not supported when used with EBO v3.x.x.. Note: RP-C is only supported on EBO 3.0 and later ** In release 4.0.2, two new commercial references for MP-V products were added. Please see section 2.1 in 4.0.2 Release notes for more details. MP-V/RP-V compatibility Supported* means there is no support for configurability between BACnet IP / MSTP system bus (northbound)   SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 currently for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 33 (Build 70) firmware v4.00.04 is approved for use.    

Issue When using EBO's registration page, the registration website that is opened allows the user to login and enter the new system ID, however, the user then cannot proceed any further. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The link https://registration.smartstruxure.schneider-electric.com/, which redirects to the https://registration.smartstruxure.schneider-electric.com/WebConnectUI/RegisterUser/home This page may not allow the user to complete the site’s registration with the new system ID. Resolution Register the site’s EBO new system ID using the following website address. https://registration.smartstruxure.schneider-electric.com/ebo/Home

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

  Issue For an AS-P running on EBO 4.0.3.176, in Device Administrator, it is showing the State-Ready (Device crash logs available). When trying to download the debug info, it populates the below error and does not get rid of the logs.   ERROR: Failed to run devadmin3 command cmd with arguments -u -m devadmin3 --sa -v cmd 172.20.214.78 -b *** "rm -f /var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz" :rm: can't remove '/var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz': Permission denied   Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Not running Device Administrator correctly Resolution When opening Device Administrator, ensure to run as administrator as below. This will clear device logs.  

Issue Enterprise Server is taking a very long time to run after restoring the database. Example: in EBO 3.2.3, It would start after 2.24 hours with about 20,000 trend logs, and with 10,000 it would take about an hour. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause When restoring the configuration only of a Database, specifically one that has a lot of Trend logs configured, EBO initializes the Trend DB before starting the ES. Resolution Select to restore ALL DATA of the database, thus the Trend Database has already been initialized and the Enterprise Server will Run.  

Issue The site has a program that writes to a Value where the value is bound to Priority 16. The graphic maps to that same point at Priority 16. Previously they were able to click on the point on the graphic and edit the value, and the program could still count it down or clear it out. But they cannot do that anymore. Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Prior EBO versions allowed to modify the value property of the BACnet object bound to priority 16 and vice versa, however as of 3.1 the system now makes each property read-only. Resolution There are a couple of options : It is recommended to use Numeric Public in the script Program. It will allow the modification without having to Force the value. There is also a feature in EBO 4.0 that will allow the change of the value without having to force it