Issue When using a calculation method on a trend log list or trend chart with the period "Month" the timestamp is always on the 16th of each month. See the example below: Why is the time stamp always the 16th and is it possible to change the collection date Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When doing a calculation in a trend log list or trend chart the timestamp will always be in the middle of the chosen period. Resolution This is currently not possible to change in EBO. Alternative ways of presenting the data are to use Dashboards or Notification reports

Issue Bindings made under the Infinet interface using Import/Export system (IE) stop updating. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Continuum i2920 Controller Cause Objects under the Infinet interface sometimes lose their Object IDs for reasons that are not yet fully understood. The issue has been seen during up revision of the AS-P from 1.9x to 3.x Resolution Under the Infinet interface, right-click on the Application folder of the AS-P or Infinet device and select "Resolve object ids" The system automatically re-assigns the missing ids Download applicable i2 devices

Issue Importing Infinet devices into AS-P fails with the following error "Invalid Data Error: Invalid_Data (0x10000) in module Coml(11). "Invalid cast from null": CreateObjectRequest".  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause Infinet devices have a space character within their names Resolution Remove the space character and use an underscore in its place.

Issue After starting the Enterprise Server(ES), the memory usage increase constantly until it finally hangs, which happens in a couple of days.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 3.2.x Building Operation Automation Server 3.2.x Cause Running a Notification report including many trend logs can take a long time to finish; for example, a report including 91 trend logs can take up to 10 minutes. If the Notification report is triggered more often than 10 minutes, reports will start to queue up, making the memory usage for the ES increase over time, and it will finally hang. Resolution When having a Notification report which includes many trend logs, make sure that it is not running too often as it is a rather slow process to create a report including many logs. Example: A Notification report which includes 91 trend logs with 168 log records takes 10 minutes to finish.

Issue After a successful commission of MP-x SmartX controller, the device is online and operating properly but fails to come back online after a warm start. The issue is seen more often when MP-x device is configured for DHCP but can also happen when configured for static IP address. (See the attached video which demonstrates the issue) Product Line EcoStruxure Building Operation Environment Building Operation SmartX IP Multi-purpose Controller (MP-X) Building Operation SmartX IP Room Controller (RP-C) Building Operation SmartX Controller IP-IO Series Cause Communication settings out of sync between the physical device and configuration database Resolution To synchronize the IP settings between the device and the configuration database follow these instructions from the online help   Discarding MP Series Controller IP Network Settings Changes

Issue Webhelp and the Technical Reference Guide supply information for using the AS-P/B DHCP server option, however, a number of relevant questions have not been answered. Product Line EcoStruxture Building Operation Environment Building Operation Automation Server Premium (AS-P 0.62 hardware) Building Operation Automation Server Bundled (AS-B) Building Operation SmartX IP Multi-purpose Controller (MP-X) Building Operation SmartX IP Room Controller (RP-C) Building Operation SmartX Controller IP-IO Series Cause There are typically a number of options to configure DHCP servers, but since the DHCP server included with the AS-P/B is very basic and NOT configurable, it's important to understand which options are and are not available. Resolution Webhelp has some helpful information about the DHCP Server Options. The AS-P/Bs built-in DHCP server assigns unrouted IP addresses within the range of addresses from 10.110.210.2 to 10.110.210.254. This was developed to allow for a quick configuration of a private MP-X/RP-C network. The AS-P/B DHCP server can be disabled and another DHCP server can be used. Here is a list of other questions and answers that may come up based on typical options in other DHCP servers: Can the scope of the IP range be configured? There is no way to configure or limit the range of the standard IP address range or to have multiple scopes. Can IP exceptions be configured? There is no configuration option to prevent the AS-P/B DHCP server from assigning a specific IP address. The AS-P/B DHCP server is unaware of static IP addresses, so if a switch or other device has a static IP set in the 10.110.210.2 to 10.110.210.254 range, you run the risk of having the AS-P/B DHCP server assign an IP address twice which can cause a number of issues. Can a Default gateway be configured? Not configurable Can a Subnet mask be configured? Not configurable Is IP6 supported? No Can lease types be configured? No Can multiple DHCP servers be installed on the private LAN? No Should MP-X/RP-C IP level devices only be hosted within the private AS-P/B network? Most site IT departments prefer that the BAS networks be isolated, however, if the network switch (Not the AS-P/B) is used for assigning DHCP IP addresses, it could hand out addresses to the AS-P/B and the MP-X/RP-C devices if they are on the same subnet. A managed (RSTP Enabled) switch can reside as a client to the AS-P/B. This is due to how the Private DHCP option is advertised. On-site IT departments may not want the switch on the customer's LAN so it is placed in the private AS-P/B network. Does the AS-P/B DHCP server assign addresses to 3rd party devices? Yes, if the 3rd party device supports this. This would be a configurable option in the device.

Issue BACnet AlignIntervals Error when downloading b3 controller after a Continuum conversion Product Line EcoStruxure Building Operation Environment Continuum conversion b3 Controllers Cause After a Continuum conversion the b3 controllers will not download correctly and AlignIntervals error is seen. Resolution This is most likely a result of have older firmware in the b3 controllers. No exact EBO supported version is stated for the b3 controller, but it is advised to always use the latest firmware version. Early versions of SBO (v1.0 to v1.9) would have been tested with v4.500064 (June2010) and v4.500076 (Mar2014). M ost EBO testing being done at v4.500077 (Nov2017). It is likely a b3 with firmware v4.500049(Jul2009) could operate correctly.   It is advised to use the current version of firmware in a b3 controller.   Continuum Conversion Tool Notes See   Known Issue v3.0   See   Known Issue v3.1 So for Continuum conversions, EBO v3.0.x, v3.1.1 and v3.1.2 up to CP4 should avoided. The work around for these versions is to convert using v2.0 then upgrade to the required version. Or for v3.1, use v3.1.2.6000 CP5 or later. The issues are fixed in v3.2.

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 What is the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line EcoStruxure Building Operation Environment Continuum Building Operation Automation Server (AS-P AS-B) 1.9 onwards Cause It is critically important to follow an approved and tested procedure when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site 1.          From Continuum Cyberstation,  the following must be completed to each Infinet controller that you are moving to an AS-P. a.      Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. b.         Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. 2.      If the conversion was done on the PCT, deploy the AS-P. 3.      Verify that the AS-P firmware is 1.9.0.73 or higher. 4.      Disconnect Infinet bus from the Continuum controller com port(s). 5.      Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. 6.      Confirm that the Infinet devices are all showing online under the AS-P 7.      Download the Infinet devices. * 8.      Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be  substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Continuum Conversion Tool NOTE V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly

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 both (http) Port 80 and (https) Port 443 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.

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited) Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016 1.9.1.95 Apr 2017 1.9.2.45 Maintenance Release Oct 2017 1.9.3.24 Maintenance Release April 2018 1.9.4.29 Maintenance Release April 2019 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) 2.0.2.67 Maintenance Release Sep 2018 2.0.3.45 Maintenance Release Dec 2018 2.0.4.83 Maintenance Release June 2019 3.0.1.104 May 2019 3.0.2.33 Maintenance Release July 2019 3.0.3.11 Maintenance Release Aug 2019 3.0.4.43 Maintenance Release Dec 2019 3.1.1.312 Dec 2019 3.1.2.29 Maintenance Release Mar 2020 3.2.1.630 Aug 2020 3.2.2.61 Maintenance Release Nov 2020 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building operation Automation Server BACnet Device, Device discovery Cause Upload of all objects in a controller can take a large amount of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.

Issue The address used to access the Generate Authentication URL up to and including PME 9.0 no longer works. Product Line EcoStruxure Building Operation Energy Expert Power Monitoring for Building Operation Environment Integration  Cause Up to and including PME 9.0 the following address could always be used to access the 'Generate Authentication URL' page which allows a user to manually create urls/hyperlinks for specific PME pages (with and without authentication), to use in EBO http://<yourservername>/SystemDataService/Auth/GenerateAuthURL .     However with the advent of PME2020 this address is no longer valid Resolution The address for the 'Generate Authentication URL' page has changed in PME2020 and permission to access this new address must also be activated via an Query run on the SQL database of the PME2020 install. Page 1676 of the PME 2020 System Guide  - Manual integration steps without using the Integration Utility - shows the required steps and the new address to be used.

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 AS status LED solid red for a few seconds followed by a quick blink. Device administrator and/or event log shows ..."Error - Upgrade using DFU mode system alarm" Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB Building Operation Device Administrator Building Operation WorkStation Cause The indication of "Error – Upgrade using DFU mode" occurs due to the fact that a possible problem with writing to the file system has been detected when booting the system. This error can be seen in WorkStation as an Alarm Event, in in the Server Logs or in Device Administrator. The configuration of the system could had been compromised as a result, although the issue is not necessarily fatal and therefore the AS is allowed to run and the situation indicated via the red status light. A system alarm is also generated as a warning as seen in the screen shot above. Resolution Since the AS file system could have been compromised, it must be re-initialized from scratch. To clear the red light: Make sure a backup of the AS is available. Attach the Device Administrator to the AS via USB and put the AS in DFU mode (press the reset button 3 times in rapid succession) Install a new database Once the AS has had its FW and database reinstalled, restore the backup using Workstation. NOTES See https://ecostruxure-building-help.se.com/bms/Topics/show.castle?id=10005&productversion=3.3&locale=en-US&a=1 If this error occurs, especially if it occurs multiple times on the same server, check the site installation include Grounding/Earthing and power supplies and for possible EMC issues (Electromagnetic Compatibility)

Issue How to get the data to display automatically (expanded) when running the Trend Log Comparison report. When running the Trend Log Comparison Report, the data is not shown in the tabular format automatically, and the + must be clicked on to expand this table to show the values.  Product Line EcoStruxure Building Operation Environment Building Operation WebReports Microsoft SQL Server Report Builder Cause When either using a Dashboard report or Exporting reports, some situations require the data to be expanded automatically when generating the WebReport.  The following discusses the changes required to be made to this report to allow this to happen.  Resolution To have the report automatically display this data fully expanded, the default WebReport "Trend Log Comparison" needs to be edited using Microsoft SQL Server Report Builder.  See the following online Help Topic for additional detail on using Report Builder with Reports. Open the Trend Log Comparison report using Report Builder. Scroll down to the bottom section of the Report and select (left-click) the DateTimeStamp field Under the Row Groups, Right-Click on [DateTimeStamp] and open Group Properties. Select the Visibility and change this option to Show  Save the file - It is recommended to save the report with a new name and not alter the default factory report.  This new report must then be deployed to the WebReports Server.  This is done by Synchronizing the new report as detailed in the online help: Synchronizing WebReports with a New Report. Running the report should now automatically have this data expanded.  

Issue The hard drive fills up with logs generated by PostgreSQL/Timescale. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Trend meta table missing information Resolution In the ES, go to the TimeScaleDB configuration. Set Trend and Event storage to false and click save. Set Trend and Event storage to true and click save.

Issue During installation of hotfix for EBO you get an "Invalid hotfix file" error describing that the file does not have a valid Schneider signature.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue What utility in Windows XP can disable items in Startup? Environment Windows XP Cause Items that run on startup can sometimes make the boot up process for a PC very slow. Depending on which applications have been added to start automatically on startup, it can also cause problems if things load in the incorrect order. Resolution Click the Start button in Windows XP Select Run Type msconfig and click OK.

Issue How to find the IP address information on a PC? Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows NT / XP / Windows7 / Server 2008 PC, run a CMD window and run IPCONFIG.

Issue I'm not sure the network card is working on this PC. Is there a way to Ping or test the card? Environment PC Network Interface Card Cause Testing the network card is the first step in troubleshooting basic setup of an IP system. Resolution Assuming you have the correct protocols loaded, you can do a loop-back test. Go to Start > Run > and type "cmd" Type the command: ping 127.0.0.1  127.0.0.1 is the loop-back address. If the card is operating, you should get a reply