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.    

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 Alarms cannot be sent to recipient CyberStation (Workstation) when controller has lost the link to the CyberStation in regard to the alarmed point in Import/Export table. The new alarm shows up in Active Alarm View only after the CyberStation is rebooted Product Line Andover Continuum Environment Workstation, CyberStation NetController (CX99xx, CX96xx) Cause Import/Export table in the NetController does not have the link to the workstation for the alarmed point. Resolution Backup current DB. Shutdown Continuum from all the CyberStations. Execute ImpExpFixupUtil.exe from Continuum install folder (C:\Program Files\Continuum). Reload all the NetController with the "Do not reload attached objects" option.

Issue Are username and passwords encrypted during transmission from the remote client or the web client to the Sigma server? Product Line Satchwell Sigma Environment Sigma Remote Client WebClient Cause Are username and passwords encrypted during transmission from remote client to the Sigma server? Are username and passwords encrypted during transmission from web client to the Sigma server? Resolution Usernames are not encrypted during HTTP transmission from the remote client and web client to the Sigma server. Passwords are encrypted during HTTP transmission from the remote client and web client to the Sigma server.

Issue Access Expert On-Premise setup needs procedures and tools to backup and restore the database Product Line Access Expert Environment Access Expert Premise Software V3 MongoDB Cause The procedures for backing up and restoring the MongoDB is documented online at the link below. https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ However, these instructions do not outline how to use the commands (mongodump and mongorestore) within the Windows OS environment using specific examples. Resolution The following procedures are designed to fill in the gap for Access Expert administrators who need to do manual MongoDB Backup and Restore. These procedures assume that Access Expert V3 has been installed and is functioning normally. You will need 2 separate Command Prompts, run as Administrator, open for these procedures. Mongo DOS Shell to attach to and run commands within MongoDB environment Standard DOS Shell to run the Mongo backup and restore commands MongoDB Backup Ensure MongoDB service is running (Start> Run> services.msc) Open a Command Prompt as Administrator (referred to as the Mongo DOS Shell) Type mongo(command) Type show dbs (command) - shown above, to give a list of the dbs available) If the MongoDB service is "Running," but the client cannot connect when typing mongo, it's probably because the path to the mongo bin folder hasn't been added to the PC's environment. To Add a local path locations variable to a PC environment https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ee537574(v%3Doffice.14) Ex. C:\Program Files\MongoDB\Server\3.6\bin (This will vary based on the version of Mongo) Open another Command Prompt as Administrator (Standard DOS Shell) Use the CD command to navigate to where you would like the backup files to be created Ex. C:\Data mongodump (command) The mongodump command creates the dump folder with admin, Keep, Signalr subfolders MongoDB Restore In the (Mongo DOS Shell) Prompt show dbs (command) use Keep (command) (Case sensitive) db.dropDatabase() (command) Use the Command Prompt as Administrator (Standard DOS Shell) mongorestore (command) The window should indicate "Finished Restoring Keep.Events," "done" and RESTORE COMPLETE If there are “E11000 duplicate key error collection” Keep.Events errors, it’s because the collection events are already in the folder and need to be deleted first.   Steps to correct the E11000 duplicate issue: (Stop the service, delete and recreate the DB folder, restart service) Right-click on the MongoDB service and Stop (you can’t delete files while the service is running) Delete C:\Data\db folder (not the Data, only DB) MANUALLY CREATE THE DB FOLDER - Right Click > New Folder and name it DB Restart the MongoDB service - this creates the necessary files in the DB folder Once these steps have been done, rerun the mongorestore command mongorestore (command) Verify that users can log into Access Expert with this database

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 When external internet access is not possible an alternative NTP Server is required to allow ES and AS to by time synchronized onsite. Product Line EcoStruxure Building Operation Environment Enterprise Server / Automation Server on closed network Eg Windows 7 Cause AS will not synchronize the time with a local NTP such as Windows 7 (32 or 64 bit) without it first being configured. Even then, increasing Cyber Security features within EBO means that the use of a 3rd Party NTP is becoming a much better option. Resolution Preferred Solution The very best option for the latest versions of EBO would be to investigate. Meinberg NTP which is a third party NTP server that runs on the Win7 or Win10 OS and provides NTP by synchronizing with four or more Internet clocks and is a trusted time source in NTP.  It is not an officially supported PSS tool, but it does fix the issue of the ES/AS not trusting the time.   Windows 7  Config If you still wish to attempt the Windows 7 NTP option first the procedure to setup is as follows:    In the 'Services' window (part of Administrative Tools) Stop the 'Windows Time' service if already running. The 'Startup Type' could be set as Manual or Automatic depending on the user needs. In the Registry Editor following changes to be made under the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time: ** Config -> AnnounceFlags = 5. ** HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer -> Enabled = 1. Start the 'Windows Time' service in the 'Services' window(part of Administrative Tools). Note: NTP uses UDP Port 123 Below is a Wireshark capture using filter udp.port == 123 indicating the “Leap indicator” bits are 11, meaning “clock unsynchronized”. NOTE: The NTP client in the AS may ignore the time sent by the NTP server if the root dispersion is greater than 'X' seconds (unknown at this time). See Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for information on how to determine whether this is a problem at the site and how to resolve it. Note: Test Lab results show that once validated and synchronized, the AS asks the time from the NTP about every 17 minutes. Two enhancements have been requested for a future release: Workstation gets an alarm if the NTP is not a valid reply A tick box setting in Workstation so the ES/AS can accept an invalidated reply(time)

Issue NC2 and ACX57xx controllers with network security applied will no longer respond to a ping command after upgrading to newest firmware. Product Line Andover Continuum Environment Network Security ACX5740 ACX5720 NC2 CX9680 Cause The ping command was used to monitor controllers offline/online status.  CX9680 and ACX57xx controllers (with network security applied) stopped responding to  a ping command after respective firmware versions  v2.100048 and v1.100052 were applied. Resolution This is functioning as designed due to the hardening of the controller's firmware for security reasons when network security has been applied.

Issue As of Continuum version 1.82 the standalone Database Engine is SQL Express, which offers inbuilt backup and restore functionality via Microsoft SQL Server Management Studio (SSMS). What is the process for backing up and restoring Databases prior to 1.82? Product Line Andover Continuum Environment Standalone CyberStation v1.81 and below. Backup/Restore  Cause As of Continuum version 1.82 the standalone Database Engine is SQL Express. Prior to that it was MSDE. What is the procedure to backup/restore an MSDE database? Resolution Visit the Download Center for MSDE Database Utilities:  MSDE Database Utilities Move SQL DB to a different hard drive

  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

  Issue EBO 4.0.3.176 When trying to import anything (Custom type, Script Program, etc.), Workstation will crash immediately with an error stating "The path is not a legal form.". You cannot navigate to the location that the file will be imported from. It will generate a Workstation error after clicking import. The issue only occurs on Windows 11 machines.     Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The wrong file format might have been used Resolution When you select "import", WorkStation looks in the bin file for the last path used. If it finds a path entry it tries to use that path. If it can't find that path, it defaults to the users' Documents folder. In this case, there was no entry in the bin file, which means WorkStation defaulted to MyDocuments. For some reason, the MyDocuments path on that PC could not be parsed, and WorkStation crashed.   The resolution is to manually add an entry in the bin file (you can get the file from support), pointing to the user's desktop. That means, that when the user selects "import", it first tries to open the user's desktop, and when it succeeds, it never falls back to the MyDocuments folder.

Issue How many concurrent users can connect to the system Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause In the datasheet it is unclear how many concurrent users can connect to an AS without affecting performance Resolution The intent in the guidelines is to provide the concurrent user connections given that the clients are not all accessing data through the same Automation Server to the same Field Controller.  Therefore, if the load is distributed –  ES Clients viewing data from the ES (or a scattered variety of Automation Servers and below) AS Clients viewing data from that AS  Then it should be safe to add the client totals for all AS and ES clients together. The local AS connections are intended to help with scaled use of clients at a site-wide or multi-site system. The typical use case is for operators within a building, floor or tenant to connect locally to the AS, while central operators connect to the ES without impacting each other.  If all ES Clients and all clients on a single AS are all accessing data from that AS and below then the performance could drop below acceptable levels.

Issue Binding to a Graphic, what is the correct method? Product Line EcoStruxure Building Operation Environment Bindings Graphics Cause In the chapter "Binding Templates - Binding Values Using a Binding Template" in the "EcoStruxure Building Operation - Technical Reference Guide" it states "When creating bindings, follow the recommended general guidelines: create binding between Inputs and Outputs only, and do not create binding to Public Signals". Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Resolution Bindings from public signals to graphics is appropriate. When dealing with directional bindings (i.e. in from a schedule, out to an alarm, in from or out to another program, etc.), it's best to bind to input blocks or output blocks.  Graphics bindings are a different animal, though.  Among other things, they are bi-directional and only affect the system when the graphic is displayed.  They also exist to give the user access and control to values throughout the system (rather than to control routine data flow). Our primary reason for communicating this best practice is to help with the binding process.  Programs will operate with un-bound points, but we're encouraging users to simplify the binding process by relying on just inputs and outputs to interconnect a program with other logic and alarms.  In this way, you can visually scan the list of inputs and outputs to see which points still need to be bound. Since most programs typically have a much longer list of public signals, it's easier to overlook a missed public signal binding. Missed graphics bindings should be easier to catch but bindings to another program or alarm may be difficult to identify.

Issue Memory and System Memory in the AS Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause What is the definition of the two different memory types shown in the AS? It is not clearly defined in the documentation. In various places, one can see Memory and System Memory, or even add a column to show.  Resolution For the AS, System Memory is the RAM used by the AS Linux OS. The rest of the memory is what is being used for the processes, such as programs, trends, etc. Memory is the amount of memory consumed by the AS (nsp_servers application), system memory is that used by the Linux OS, however there is much debate about how this is calculated and allocated, so too much should not be read into this, it is there primarily for developers.

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue The port range used by the Project Configuration Tool is unclear Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The ports used by PCT are located in different documents Resolution • TCP on port 4444 (fixed) • HTTP on port 80 (default) • HTTPS on port 443 (default) • Server port 9091 (default) • Server port 9090 (default) • Engineering port 32768-61000

Issue Automation Server has license violation although correct embedded license is activated. ASBaseLicenseStatus has license violation status "inform"   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Adjusting the Automation Server time and date to an earlier time, ex. prior to license activation time, causes license violation. Resolution Make sure that Automation Server has correct date, time and timezone or configure the Automation Server to synchronize its clock with a network time server, refer to: Time and Time Zone Configuration in Automation Server.

Issue When trying to open WorkPlace Tech Editor the following error is shown in a pop-up window.   The following error occurred while trying to launch the WorkPlace Tech Ribbon Bar: The add-in could not be installed. Product Line EcoStruxure Building Operation, TAC IA Series Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause An installation of the Visio Ribbon has not closed correctly from previous use of WorkPlace Tech Editor or standalone WorkPlace Tech. Resolution Open the Add and Remove function in Windows Select "Program and Feature" Look for an instance of the SE.WorkStation.IA.VisioRibbon when no WorkPlace Tech Editor is running. Right-click and uninstall. Open Workstation and launch WorkPlace Tech Editor  There are other conditions that can cause the ribbon not to run as well.  They are detailed in other articles Similar Error Message Regarding Ribbon Bar  Unable to Load Ribbon