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/9000 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.  * CPs are available on: EBO Hotfix List Note: 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   Note: RP-C is only supported on EBO 3.0 and later SpaceLogic/EasyLogic versions compatibility 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: Previous to Version 1.0, SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 2.0 (Build 77) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well. Release Notes  Starting with Version 3.1 (Build 85), firmware 6.00.03.03007 CP2 and 7.x RC can be employed. The EasyLogic controllers are supported by the Niagara modules with these releases.  N4.10, 4.13, 4.14 and 4.15 are the only versions with these modules. Product Announcement      

Issue What to do if the password for the Advanced Display v3 (AD v3) is lost or forgotten? How is a factory reset done on an Advanced Display version 3 (AD v3)? Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause If the kiosk password for AD v3 is lost, there is no recovery option available. The only way to regain access is to perform a factory reset on the device. Resolution To reset the AD v3 and set a new password, follow these steps: Power Cycle the Device Press and hold the power button for at least 10 seconds until the device powers off. Initiate Factory Reset Once the device restarts, tap the screen to bring up the reset options. Highlight “Factory Reset” until it turns green. The device will reboot with factory default settings. Reconfigure the Device After reboot, select the SmartX HMI Kiosk app. Enter your new desired password to complete setup. The following video will guide you through the factory reset process on an AD v3:

Issue At first, TGML graphics in Building Operation WorkStation load correctly and display real-time values. However, after the Enterprise Server has been running for an extended period, the graphics begin to load slowly, and values stop refreshing or updating. Restarting the Enterprise Server temporarily restores functionality, but the issue eventually reoccurs. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Enterprise Server TGML Graphics SmartConnector Cause This issue is typically caused by the behavior of a SmartConnector that: Polls values too frequently Creates a new login session for each poll instead of reusing an existing session This results in a high number of open sessions with the Enterprise Server. In the SmartConnector view, multiple active sessions can be observed. The problem tends to occur when there are more than 150 active connections, although this threshold may vary depending on the server’s processing load.     Resolution To resolve this issue, request the SmartConnector developers to: Adjust the polling rate to a more appropriate interval Reuse existing login sessions instead of creating a new one for each poll These changes will significantly reduce the number of active sessions and improve the performance and reliability of graphic updates in the Enterprise Server.   Additional Notes Monitor the number of active sessions via the SmartConnector view. Consider implementing session management best practices to avoid similar issues in future deployments.

Issue When opening a Function Block application in WorkStation, adjusting the zoom level does not retain the setting the next time the Function Block is opened. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation v6.0.4 and earlier Building Operation Builder for Function Block Cause There is currently no setting in versions 6.0.4 and earlier that allows the zoom level to be retained in the Builder for Function Block editor. Resolution Starting with Building Operation 7.0.2, a new feature has been introduced that allows the default zoom level to be retained when reopening Function Block Program.

Issue A customer would like to install an Enterprise Central(EC)  on the D drive instead of the C drive is that possible to do?   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause In this case the customer is not allowed to install any files on the C drive so all EBO files should be installed on the D drive instead. Resolution It is possible to install the EC or ES on the D drive, when installing you specify the programs and backups should be installed on the D drive instead of the C drive. And the programs and the backups are installed on the D drive as specified. But there is some files that always will be installed on the C drive:     The backup is installed at D:\ProgramData\Schneider Electric EcoStruxure as it should but we also get a S2Connect folder at C:\ProgramData\Schneider Electric EcoStruxure. When installing Workstation that will be installed on D:\Program Files (x86)\Schneider Electric EcoStruxure as the EC is installed there. But then we also get a GraphicsEditor folder and Workstation folder at C:\ProgramData\Schneider Electric EcoStruxure. And then installing the License Administrator also add LicenseFiles folder at C:\ProgramData\Schneider Electric EcoStruxure These files will always be installed on the C drive and this is not possible to change. NOTE:  If Workplace Tech Editor is being used by Workstation on the PC, the accompanying Visio installation has to be installed, per Microsoft in the C: drive.

Issue PCT project folder size increases when an object is deleted. Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause Any change made in PCT increases the size of PCT project folder. This is by design and it is a normal behavior of PCT. The reason for this is that a project is a virtual machine using a dynamically allocated image that grows when memory is needed, but the image will not shrink when something is deleted.  Resolution The only way to reduce the folder size of a project is to backup all servers in the project, create a new project, restore the server backups to the new project and then delete the old project.

Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above 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. Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue How do I put a different application in an existing MNL controller under an AS? Environment AS with MNL controllers 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. Cause An incorrect application has been installed in a device. Resolution First, the correct application must exist in the WorkPlace Tech editor list.   Expand the System Tree to expose the MNL device to be changed and the Application file under it.  Right click on Application and select delete.  Now right click on the MNL controller select MNL and Assign application and assign the correct application from the list. Once assigned right click on the controller select MNL and select Download application.

Issue The database files used by the WebReports SQL database need to be moved to another location. Product Line EcoStruxure Building Operation Environment WebReports SQL Server 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. Cause There are numerous reason for wanting to do this, but the most common reason is that there is not enough space on the disk where the WebReports databases are located. By moving to another disk this will allow space for future expansion. Note that this article only describes how to move the database files to another harddrive. The SQL server and database files must still be on the same PC where WebReports is installed. Resolution To move the database files, follow this process: Start by backing up everything. Stop the reporting agent service (name: ReportingAgentService). Open SQL Server Management Studio and locate the database. Right-click on the database and select Tasks-->Detach. Locate the SQL database files (*.mdf and *.ldf) in Windows explorer. Cut or copy these files and move them to the desired location. Go back to SQL Management Studio and select the Databases folder. Right-click and select Tasks-->Attach database. When the dialogue opens up, locate the 'ADD' button and click on it. Browse to the database files' new location and click on OK. Restart the reporting agent service.

Issue Confused by RF-Series sensor wiring instructions. Do the controller's input return and the supplied power ground connect to the same termination on the sensor? Environment RH-Series sensor Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Documentation Resolution *** If connecting to a voltage input on the controller then use the VOUT termination instead of the 4-20 mA

Issue User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation 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. Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Issue Difficulty getting b3 controller online in order to replace a failed one Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Continuum b3 Controller Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause A b3 controller has failed and needs to replace with the same model. Resolution Remove the failed b3 controller. In EcoStruxure Building Operation Workstation change the serial number of the failed b3 to that of the replacement b3. Install the replacement b3 and ensure the MSTP bus is connected so it autobauds to the correct rate. Then power it up. Remove the battery tab from the replacement b3 (if applicable). In Workstation right-click on the replacement b3 and select Device -> Commission. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Download all objects. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Device -> Backup to flash.

Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server 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. Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue How does one get a clean database for the Enterprise Server or Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central 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. Cause Need for clean database either for testing or start from scratch.  Resolution Stop Enterprise Server or Enterprise Central using Software Administrator Go to the location of your database using Windows Explorer. In EBO V3.2 or higher, software administrator has a shortcut button for the databse folder. For this example it is C:/ProgramData/Schneider Electric EcoStruxure/Building Operation 2.0/Enterprise Server/db Delete the following folders if (some might not exist): Configuration, Historical, Persistent, System, UDT Start Enteprise Server or Enterprise Central using Software Administrator, the system will create a new folders and files as needed. Note: Restoring a different database over the current database does not require the clean database state. Using the backup and restore procedure allows you to switch databases.

Issue Function Block Editor does not open. Product Line EcoStruxure Building Operation Environment SmartStruxure Function Block Editor 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. Cause There could be many reasons but in one of the case we found a malware called "sprotector.dll" somehow trying to hook into the Function Block Editor dll's. This malware is then crashing and prevents Function Block Editor from starting. SProtector.exe is typically added when you install another free software (video recording/streaming, download-managers or PDF creators) that had bundled into their installation this program. Resolution Reinstall this computer's Operating System completely, if that's not an option you can read more about how to remove "sprotector" here: http://malwaretips.com/blogs/sprotector-exe-virus-removal/

Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 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. Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue V-Box fails to install network interface/Virtual Adapter during Project Configuration Tool Installation. Product Line EcoStruxure Building Operation Other Environment OracleVM VirtualBox (all versions) Project Configuration Tool (all versions) 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. Cause Some security or anti-virus software prevents V-Box from installing virtual adapter during PCT/V-Box installation or prevent PCT from connecting to a virtual adapter.   Example: The anti-virus software can flag V-Box file as possible threat. Resolution Uninstall or Disable security and Anti-virus software. Install PCT. Install or Enable the software after PCT works properly.   NOTE:  You may have to disable and/or completely remove the security software even after PCT is installed and works properly.  Contact your IT group to get assistance with getting exceptions entered to have PCT work correctly in conjunction with your security software.

Issue During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software 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. Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  

Issue Even though "Clear when enabled" is configured on a trend log, the trend data is not cleared when the log activation is triggered. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Trend Logs 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. Cause The property "Clear when enabled" only affects the trend data when the trend log goes from disabled to enabled. This is not the same as the activation method of the trend log. Activation method changes the Status from Stopped to Started etc. Resolution To activate the "Clear when enabled" setting configured on the trend log: Select the Trend log, right-click on it and select Activation, then select "Disable trend log". Select the Trend log, right-click on it and select Activation, then select "Enable trend log". See the following online help topics for further information on Activation: Trend Log Activation Actions Menu - Activation Submenu

Issue When upgrading to 1.8.1 a Xenta Central Schedule that resides outside the LonWorks network it is not upgraded to the current version. If the upgrade is attempted it breaks all the Xenta time schedule bindings with the Xenta Cental Schedule. Product Line EcoStruxure Building Operation   Environment StruxureWare Building Operation 1.8.1   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. Cause During the LonWorks Pre-upgrade only the objects under the LonWorks networks are upgraded. If the Xenta Cental Schedule is located outside the LonWorks network this is not included in the upgrade process. Resolution Options to resolve this issue. Before upgrading to 1.8.1 If the site uses Xenta Central Schedules, then use the server Hotfix 1.8.1.5101 to upgrade all the servers. Please contact Product Support and request Hotfix 1.8.1.5101. After upgrade to 1.8.1 There are two options in this case: You can delete the Xenta Central Schedule and add a new Xenta Central Schedule. You are then able to bind the Xenta Schedules to the new Xenta Central Schedule.   If there are many Xenta Schedules that refer to a Xenta Central Schedule you can use the export function to resolve the problem as shown here Export the  Xenta Central Schedule as shown here Once you have exported the Xenta Central Schedule you need to edit the exported XML file with Notepad++ and change the Xenta Central Schedule attributes from "lon" to "lon2".  This is what the change should look like Once this change has been made the XML File can be saved ready for an import to the Server. Delete the existing Xenta Central Schedule from the database, making sure you check the box keep references. Then import the edited XML to the server and this will re-establish the Xenta Central Schedule binding with the Xenta Schedules.