Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line Andover Continuum Environment Continuum b3920 controller Continuum i2920 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Issue What is the unit load of the SpaceLogic SLP Room Units that will help me to calculate how many SLP Room Units that can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SLP Room Unit SmartX Server Cause Documentation does not state the Unit Load (UL) of the SpaceLogic SLP Room Unit. Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SLP Room Unit range use the SN65HVD1781DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1781DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. Since the SpaceLogic SLP Room Unit does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SLP Room Units should only require a 120 ohm termination resistor at each end of the bus and not require any bias resistors. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials.  When logged on the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites which have restricted this in some way which may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. You need to use HTTPS. Use your Windows username and password.  The Windows domain must be defined (It needs to be the actual Windows domain, not what you named the domain in SmartStruxure). Download a TVDA for Single Sign-On Instructions

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue After connecting a new Optimum Living Space Sensor, the LCD is blank other than being backlit. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Optimum Building Operation Multi-purpose VAV fw 2.00.03.02000 or older Cause Only Living Space Sensor bases running application version 1.0 or later can read the Optimum cover models Resolution Upgrade EBO to v3.1.x or later and SmartX controller to fw v3.01.x or later. At the time of this being published, firmware revisions prior to 3.01.x are not compatible with the Optimum Living Space Sensors (SXWSCDPSELXB, SXWSCDPSELXW, SXWSCDXSELXB, SXWSCDXSELXW).

Issue Information not available in product documentation. Product Line Satchwell Sigma Environment Windows versions Cause Documentation not updated to show additional operating systems now supported. Resolution Sigma 4.0.8.57, as a front-end user interface, is supported on the following operating systems: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 80 – 89), as an engineering tool for Sigma when transitioned into SBO/EBO Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 104 onwards), as an engineering tool for Sigma when transitioned into SBO/EBO system Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 **1 Windows 10 **1 Windows Server 2012 **1 The additional operating systems support is only applicable when Sigma is part of a SBO/EBO installation. (This confirmation was provided to PSS by R and D).

Issue "Ethernet 1 Configuration" of a SmartX Server in the Device Administrator for EBO version 3.2.1 or higher shows "Dynamic DNS" as enabled and grayed out. Is it possible to disable "Dynamic DNS"? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium version 3.2.1 or higher Cause The  Dynamic DNS  service procedure supports the assignment of  dynamic  IP addresses to a particular domain. A comparison with the internet provider's  DNS  databases takes place automatically. The Dynamic DNS automatically ensures that changes to the IP address are detected and  DNS  entries are updated accordingly. Resolution In EBO version 3.2.1 or higher it will not be possible to disable Dynamic DNS, it will always be enabled.

Issue BACnet Interface has "!" with unresolved references Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v2.0 or later Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause During the startup of a Smart-X controller, the auto-association feature fails and the data becomes corrupted Resolution Go to BACnet Interface -> Time Sync Recipients Find any devices listed as DEVICE_<Instance ID>, select & delete Verify all devices listed are configured as follows: SmartX controllers Recipient Type: Reference Recipient Device Object Reference: <Device in System Tree> If Recipient Name does not match, copy from Object Reference and paste in the field. This helps humans troubleshoot the issue. DO NOT set Recipient Type = MAC Address, Network ID = Global Network or Local Network, Mac Address = Broadcast. This will set time on other ES/AS with BACnet Interface on the BACnet System.

Issue Many campuses are configured with 1 BACnet Network ID number for Primary IP that is unique per building whether or not they are in the same IP subnet or multiple (with BBMDs). Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Page 2887 of the 3.0.x technical reference guide does not clearly explain the configuration and it also does not extend to multi-building systems using BBMDs. Resolution BACnet network numbers are assigned at BACnet routers, with a Range of 1-65,534 (where 65535 is reserved for broadcasts). Routed networks are assigned unique network numbers and can only have 1 router per network. Routed networks are usually BACnet MSTP, BACnet Ethernet, and Secondary IP networks. Standard practice is to have primary IP networks consisting of IP routers/devices in the same IP subnet or across multiple IP subnets joined by a BBMD and/or foreign device configuration uses the default BACnet network number 1.

Issue Backup and Restore Process for WebReports Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Server 2008 R2 Cause Need detailed backup process Resolution Refer to Online Help Topic for details Backing Up the WebReports Database  On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect.   Note: When using a remote computer to connect to the Report Server SQL database, the Windows Accounts must exist on both machines and have administrative rights for the SQL database otherwise a successful backup will not occur.  In this instance, it is recommended to use the SysAdmin ' sa ' login / password details when connecting in remotely.   Expand the Databases folder. Right-click StruxureWareReportsDB , point to Tasks, then click Back Up. Under Destination, click Add. Click OK. In the Destination on disk box, select the backup destination. Click OK. Click OK.   Restoring the WebReports Database Ensure the Enterprise Server is up and running with the correct database.  Stop the SQL Server Reporting Services and WebReports Agent (if installed).  Note: If moving the WebReports Database it is recommended to restore the database then Install WebReports.  Then when Installing WebReports select Upgrade existing (as shown) and NOT New database  Restore the WebReports database to recover reports data from backup.  This will include any Dashboard reports saved. On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect. Expand the Databases folder. Right-click StruxureWareReportsDB and select Tasks, then select Restore, then select Database. In the Restore Database dialog box, select the database set(s) that you want to restore. Click OK. Click OK. If not already installed now complete the installation of WebReports 

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment Building Operation 1.5.x to 2.0.3 Modbus Device  Socomec Power Meters Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this work-around is that the online detection for the device is turned off, so the device will never go offline in Building Operation.

Issue TimescaleDB Installation Errors - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% - ERROR: could not get 'pg_config --pkglindir' : exit status 1 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.x External Log Storage TimescaleDB (third party)  Cause Missing environment variable paths in Windows is detailed in section 9.4.4 PostgreSQL and TimescaleDB Installation in the EcoStruxure Building Operation 3.0.1 Release Notes. Assistance in how to add these variables is described below. Resolution Using the EBO External Log Storage Installer tool available on the Community, there is no need to make any manual configuration, as the tool executes the installation without the need for e.g. environment variables. Alternatively, you can manually set these as detailed below: You can either view a video showing how it is done:  or follow the instruction below view, add and modify the environment variables from the Control Panel as follows:  In the Control Panel select System and Security Select System Select Advanced system settings Select Environment Variables . In System variables, highlight Path and click Edit. For the error - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% Add the New path 'C:\Program Files\PostgreSQL\11\bin' to the environment variable. For the error -ERROR: could not get 'pg_config --pkglindir' : exit status 1 Add the New path 'C:\Program Files\PostgreSQL\11\lib' to the environment variable. You should see something similar to the following after TimescaleDB has been successfully installed.

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps in WebHelp article 7742. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all .data files that start with taclic:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line TAC INET, EcoStruxure Building Operation Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

Issue How do I setup and configure the database when using External log storage in EBO? Product Line EcoStruxure Building Operation Environment PostgreSQL TimescaleDB pgAdmin Building Operation Workstation Cause When using External log storage in EcoStruxure Building Operation(EBO) PostgreSQL server and TimescaleDB are installed on a computer where the trend log data and events should be stored. The database used for External Log storage needs to be setup and configured correctly. Resolution The  EBO External Log Storage Installer  tool available on the Community assists with installing and configuring the PostgreSQL server.  But if you like to see how it is done manually please watch this video. The following steps are shown in the video: Create the database in the PostgreSQL server Create a user which will be used by EBO when it connects to the database Configure the database for use with EBO Configure EBO to be able to connect to the database  

Issue Are multiple Enterprise Servers in same system/site supported with Building Operation?  Product Line  EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central  Cause Large sites or customers may request a multi-tiered configuration to support multiple Enterprise Servers. Resolution A three tier server support containing multiple Enterprise Servers are not supported until Building Operation 2.0 and above.  The top tier of this EcoStruxure BMS been the Enterprise Central.  Refer to the following online help topic for further information: EcoStruxure BMS Server Hierarchy   

Issue When you select a trend chart from a Automation Server or a Enterprise Server the Internet Explorer Hangs and finally crashes. Product Line EcoStruxure Building Operation Environment WebStation 1.1 and 1.2 Internet Explorer 8 Cause The wrong version of Java is installed. StruxureWare 1.1 and 1.2 requires Java version 1.6 update 26 to function correctly. This error is the result of Java version 7 installed on the WebStation computer.  Resolution Note:  Java is no longer required from SBO/EBO version 1.7 and above.  Uninstall Java 7 and install the correct version of Java (Java version 1.6 update 26) stated on the WebStation data sheet. Refer to the Online Help Topic WebStation Specification Sheet and select the version of WebStation in use to determine the version of Java required.   

Issue Power Monitoring Expert (PME) is able to make its data objects and alarms visible to EBO via EcoStruxure Web Services (EWS). But when viewed, the Alarms from these EWS objects only shows a number rather than its actual object name in PME. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server EWS Integration Cause There are two stages to bringing data via EWS into EBO.  The first is to create the EWS interface in EBO so that the EWS source (in this case PME) can be discovered.  However, if those discovered EWS objects are not then hosted in EBO, the Alarm Source details will be not complete. Resolution 1. First Identify an object in PME which is also in Alarm and will also be Alarming in EBO when hosted. The date and time of the actual Last Occurrence can be useful here. 2. Notice that the Source name and Source of the same Alarm in EBO is only a number. In this case 3 or EWS Client/3. 3. Now select Host EWS objects from the EBO Menu and host that point or controller onto the EWS interface 4. Note now that all Alarm references previously showing just a number now immediately update with the correct Source name and Source now that the point has been hosted in the EBO Database.  In this case PDU_2B_1_6A_ION9200 Note:At this point it would be very easy to simply decide to Host the entire PME Server onto the EBO Interface rather than a single object or controller as this would then update the sources of all alarmed objects.  However care must be taken that at this point not to overload the system.  Every hosted object will then be polled for value and alarm status periodically adding greatly to the comms between the PME and EBO systems and while the polling rate for Value and Alarm can be adjusted to sensible values there is an argument to only host those EWS objects that data is required from.

Issue Unable to log into Workstation because the user password is unknown. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Enterprise Server Building Operation Project Configuration Tool (PCT) Cause The password for an Automation or Enterprise server has been forgotten. Resolution If the password is unknown or forgotten to an Automation or Enterprise Server, please refer to WebHelp article 6749. The Quick-Help video on the Exchange Community can be referred to. For servers 3.1 or later: *Ensure that you have the AS-P connected to your machine via USB cable In Device Administrator, select the AS-P you need to perform the reset to. Check the box and click the hyperlink From the top bar select Password Reset Select OK when you get the “Password reset token created” pop-up In WorkStation, hold shift and left-click the area near the SE Icon. This will populate the Session ID. Click the Copy button. Send the Session ID to PSS Once PSS provides you with the unlock key In WorkStation, ensure that the Session ID is still visible, enter UN: Admin and in the Password field, paste the unlock key you received from PSS and click Log On This will pop-up the Change-Password form Fill in the “old password” field with the unlock Key Put in new password you want to use and then enter the new password in again. Click OK

Issue Script editor shows blank canvas or shuts down immediately after launching. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Cause User settings file contains information the Script Editor application can't process correctly. Resolution First, to confirm that the issue is indeed caused by information in the user settings file, navigate to the location where the file is located (i.e. C:\Users\Your User\AppData\Roaming\Schneider Electric EcoStruxure\Script Editor\3.1.2.29) and make a backup of the User.settings file then delete it. If the Script Editor launches fine after deletion of the file, and you need to narrow down which setting was causing the problem, you can put back the original file then open the file in a text editor such as Notepad++ and comment out suspected lines until you identify the exact setting causing the issue. You comment a line or block of lines by inserting <!-- at the beginning of a line and ending the line(s) with -->  (see below)