Building Automation Knowledge Base

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server  Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately  For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log  Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: NOTE: The steps below are no longer valid for EBO 2022 and above. See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation.   Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server.                   Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities  

Issue Configuring NTP and troubleshooting in the Niagara Frameworks Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause Guide to configure and test NTP server and Jace sync operations Resolution Please familiarize yourself with the official documentation of the NTP functionality. NTP and its configuration are comprehensively documented in the Niagara Platform Document. The official documentation is updated frequently and may contain information that supersedes the content of this article. Using the ntpq utility program The NTP Project maintains the NTP software that is compiled and included with Red Hat Enterprise Linux (and other most other Linux distributions). To get the software for Microsoft Windows, Meinberg ports the software and provides it. With this software, you not only get the ntpq utility program, you also can run the NTP client/server on your PC. In this way, you can use your PC as an NTP time server to your JACE. NOTE: The Client and Server (Time Only) options were added in 4.9. Using Server creates potential attack surface for 'Mode 6' queries. But to query with ntpq as described below, it must be set to Server, at least temporarily. Be advised that you should not have your JACE exposed to the Internet. Consult the Niagara Cyber Defense page for more details. Using the ntpq utility program, you can query a JACE that is configured for NTP, and get a list of the peers known to the JACE and a summary of their state. For this use the -p option, and provide the IP address to the JACE. The command will look like this: ntpq -p 192.168.1.140 The output of the command will look something like this: The ntpq man page at ntp.org fully documents the details of the table above. Only a few details will be covered here.  The row that begins with * (asterisk), has been declared the system peer. The second row begins with a space, indicating that it is an unreachable peer.  The third column is for the stratum. Stratum 0 is an actual time source, like an atomic clock, that provides time to a stratum 1 NTP server. A stratum 2 server gets its time from a stratum 1 server. A stratum 3 server gets its time from a stratum 2 server, and so on.  Reach is a circular log buffer containing a set of eight bit-flags, expressed as an octal number. Convert octal to binary to determine the reach for the last eight attempts. For example, 376 converts to 11111110, which means that we failed to reach the server the last time, but the other 7 were successful.    Using the NtpPlatformServiceQnx spy page Right-click the NtpPlatformServiceQnx and select Views > SpyRemote.         As you scroll down the first section of interest is the one that shows the NTP Configuration File. It reads what we've written to the file ntp.conf and displays it.                                          NTP Configuration File #/home/niagara/etc/ntp.conf: Niagara Network Time Protocol Configuration File #Use the NtpPlatformService UI to modify this file. #Created: 24-Sep-19 4:53 PM EDT # #Niagara NtpPlatformService variable, do not modify #ntpEnabled true #syncAtBoot true #server list server 192.168.1.2 burst prefer server 192.168.1.3 burst server 192.168.1.4 burst peer 192.168.1.5 peer 192.168.1.6 #ntp features enabled enable ntp stats #ntp panic value, if offset exceeds this, ntpd should exit (disabled if 0) tinker panic 0 #gather information about statistics statistics clockstats loopstats filegen clockstats file clockstats type none nolink enable filegen loopstats file loopstats type none nolink enable The next section of interest is for the NTP Daemon Log. You'll only see this section if Generate NTP Statistics is set to true. It's generally not necessary to consider these statistics.                                                       Generate NTP Statistics Jan 30 08:45:14 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd161a.aa0c9b85 Jan 30 08:46:14 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1656.2b9be356 Jan 30 08:46:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd165a.aa0c9453 Jan 30 08:47:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1696.2b9bca8b Jan 30 08:47:22 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd169a.aa4e33f0 Jan 30 08:48:22 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd16d6.2b9bd269 Jan 30 08:48:29 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd16dd.aa8fa9b9 Jan 30 08:49:27 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1717.2b9bcbe9 Jan 30 08:49:34 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd171e.aad12b7e Jan 30 08:51:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1203.21caf133 does not match aorg 0xe1dd175e.153d05cf from sym_active@172.16.11.205 xmt 0xe1dd1786.c4cb59c2 Jan 30 08:51:33 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd11bb.218961dc does not match aorg 0xe1dd175c.153d0991 from sym_active@172.16.10.171 xmt 0xe1dd1795.1de9a94c Jan 30 08:51:40 nto ntpd[8740900-1]: receive: KoD packet from 172.16.10.158 has a zero org or rec timestamp. Ignoring. Jan 30 08:52:44 nto ntpd[8740900-1]: receive: KoD packet from 172.16.10.158 has a zero org or rec timestamp. Ignoring. The next section is NTP Daemon Drift. After NTP has synchronized with reliable time servers for a significant amount of time, it will write the calculated drift (in PPM) to a file, such that it can initialize with this value on reboot. It will use this calculation of how far the clock drifts, to correct the clock in real-time, in increments too small for any application to detect.   NTP Daemon Drift 20.185   NTP Daemon Clock Stats is next. It reads what is in the clockstats file. In this example output, the file does not exist and the spy page tells us so.                                                     NTP Daemon Clock Stats Modified Julian Day | Secs. Past UTC Midnight | Clock Address | Last Time Code Error reading /var/run/ntpdstats/clockstats: /var/run/ntpdstats/clockstats (No such file or directory) The final section of interest is NTP Daemon Loop Stats. If you're not getting data here, then the configured servers/peers might not be reachable.    NTP Daemon Loop Stats Modified Julian Day | Secs. Past UTC Midnight | Time Offset Secs. | Drift Compensation | Estimated Error | Stability | Polling Interval 58860 29871.775 0.000000000 20.226 0.000976563 0.000000 6 58860 30081.780 0.000753215 20.226 0.000976563 0.000000 6 58860 30150.781 0.000753034 20.226 0.000976563 0.000000 6 58860 30688.793 0.000018819 20.227 0.000976563 0.000213 6 58860 31155.803 -0.000220479 20.220 0.000976563 0.002179 6 58860 31221.804 0.002128888 20.229 0.001234668 0.003595 6 58860 31233.872 -0.001539013 20.228 0.001736532 0.003385 6 58860 31385.925 -0.000336908 20.225 0.001679057 0.003345 6 58860 31498.941 0.000431773 20.228 0.001608116 0.003294 7 58860 31841.815 0.000467697 20.230 0.001543370 0.003195 7 58860 32276.675 0.000795988 20.235 0.001484403 0.003499 7 58860 32546.942 0.009518751 20.274 0.003382136 0.013979 7 58860 32666.611 0.000412569 20.274 0.004513791 0.013078 7  

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 Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.

Issue READ is a Script programming system function that reads trend data from a trend log into a Script program. If there is an External Logs Storage configured, is it possible to access trend log records from the External Log Storage? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause READ Script function doesn't return same number of records as trend log list or chart. Resolution The Script READ (for Trend Logs) system function can only read from the server's internal database and doesn't access records stored in the External Log Storage. For more information, refer to: Trend Log Access Functions.

Issue How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see the below video demonstrating how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. Also please note the following: In the video the "Host address" in EBO is set to the IP address or DNS name\SQLserver instance like this: localhost\SQLEXPRESS. If the SQL server is not located on the same computer as the EBO server only use the IP address or DNS name and no instance on "Host address". The video demonstrates using the version 5 script when configuring the database in the MSSQL server, search External Log Storage - MSSQL Installation Script  to download the appropriate EBO version script. For the example query to manage user permissions download User Rights Script or see attached script.txt. If using MSSQL Express rather than the full MSSQL version it may be necessary to consult External log storage not working with SQL Server Express.    

Issue Using a Security Expert SX-RK-XW reader to work with Continuum Product Line Andover Continuum Environment Continuum 2.03 ACX 5740 CX9702 Cause It can be useful prior to a transition from Continuum to Security Expert to use Security Expert readers with Continuum Resolution Minimal functionality testing was done using the Security Expert reader model SX-RK-XW Continuum 2.03 ACX5740 with firmware: 1.100013 and 1.100052 CX9702 with firmware: 1.200036 Tested with Pin Only mode by setting up a door, a card holder and entering in the appropriate PIN code   5740 with SX Reader ACX 5740 PIN Only Active Event View CX 9702 with SX Reader CX 9702 PIN Only Active Event View

Issue Schedules are not unlocking or locking doors according to the dates and times specified by the scheduled events Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The Security Expert system has a number of variables that schedules take into consideration when determining control of doors and if one of these isn't configured correctly, it will affect proper schedule function and control. Resolution 1. Verify that the schedule has the appropriate dates and times set 2. Check Holiday Groups and ensure that any calendar actions created to repeat each year have the same start and end date. Having different start and end dates with a repeat can cause the action to span long periods which can affect scheduled operations. 3.   

Issue In Swagger user can login but can't get the id of the root container. Below response is received: "Message": "Container Id not found" Product Line EcoStruxure Building Operation Environment SmartConnector Cause EBO user password need to be changed due to Password Expiry configured in the password policy. When user tries to login to WorkStation or WebStation, below change password dialog will be recieved.   Resolution Make sure to change the user password before reaching the limit the days configured in the Password Policy. Password expiry can also be reconfigured to change number of days or disabled if not needed, refer to Configuring the Password Policy using WorkStation or Configuring the Password Policy using WebStation

Issue The en1 network adapter is not an option for assignment when configuring an IP port Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series N4 Jace 9000 Building Operation Multi-purpose Controller / VAV (MP-C / MP-V) Building Operation Room Controller / VAV (RP-C / RP-V) Building Operation IP-IO Cause With the switch to Linux for the Jace 9000's operating system, some functions such as sensing adapters work differently when configuring a controller station.     Resolution In N4.13, we have added a new action to find adapters when Jace's are being pre-configured offsite. Start by confirming in the TCP/IP Configuration page that the desired port is configured and enabled. Make sure that some communicating device is connected to the desired port, exhibited by the port's lights on the unit. Examples include a workbench connection, a BACnet IP device/router, or another Niagara Device. Right-click on the "Link" component under the port, and select the "Query For Adapters" option. You should now see the port in the dropdown. Note: With N4.14, using the en1 as a DHCP server is possible.  If using this with BACnet IP MP, RP or IP/IO in Space Logic controllers engineering with Niagara, this is an important consideration for network applications.

Issue New user is unable to complete the BDP registration process Product Line EcoStruxure Building Data Platform Environment Building Data Platform Cause User clicks the registration button which has been mailed to them but get an “Opps! This page cannot be found.” error Resolution The user is already logged into BDP using another User account. This can occur if a SE user is using more than one email address to manage accounts with different business relationships. This can also occur if the user is a SE employee who is testing the system. The user should log out of BDP. Or use Incognito mode.   NOTE: If the user is logged into another SE app, this could also pose a problem. TBD

Issue New user with an external email account was created but never received an email invite Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Incorrect email User registered for the wrong platform (UAT or Prod) IDMS issue Resolution Attempt to log in, this should kick off the registration process again Verify that the email is correct Verify which platform the user should be registered to

Issue Receive API error codes while trying to connect my API to BDP. Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Receive the following Error codes: 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 500 Internal Server Error Resolution 400 Bad Request The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing) 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server 404 Not Found The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web 500 Internal Server Error The server has encountered a situation it does not know how to handle   Successful responses 200 OK The request succeeded. The result meaning of "success" depends on the HTTP method: GET: The resource has been fetched and transmitted in the message body HEAD: The representation headers are included in the response without any message body PUT or POST: The resource describing the result of the action is transmitted in the message body TRACE: The message body contains the request message as received by the server 201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests. 202 Accepted The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

Issue Graphics updates are very slow, it takes over 1 minutes to load a graphic, Opening objects from Continuum Explorer is slow, sometimes it will failed to open an object if clicked too frequently. When using the BACnet path for objects on graphics it is fast. Product Line Andover Continuum Environment b4920 version 4.2000026 b3s version 4.5000035 Cyberstation 1.81 or above Cause For the old BACnet IP controller b4920, versions prior to 4.200029 could have some communication issue with b3s MSTP enhance mode not enabled on b4920, Resolution Upgrade b4920 to version 4.2000029 or above, preferably the latest version  Go to the webpage of b4920, check "MSTP Enhance Mode" and then click submit Wait for b4920 to go back online and test graphics operation

Issue Continuum operation unacceptably slow. Product Line Andover Continuum Environment CyberStation All CXs, i2s and b3s Cause Wireshark capture shows lots of SMB traffic between the machine running CyberStation and the server. The Server Message Block (SMB) protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. Resolution Identify the application/service responsible for generating this traffic and stop it or relocate it to a different machine where it will not interfere with CyberStation operation.

Issue When Continuum Explorer is launched it takes a very long time to update.  Product Line Andover Continuum Environment CyberStation WebClient Continuum Explorer Cause When Continuum Explorer is launched it must populate all objects that reside at the root.  When there are a very large number of Personnel objects or other object types in the root, Continuum Explorer will be slow or unresponsive until this population process is complete. Resolution Create a Folder under the Root of Continuum Explorer and move personnel objects to this folder. Consider doing this to other objects that exist in large numbers.

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 Active Event Viewer contents and column headers are blank.   Product Line Andover Continuum Environment CyberStation Cause Windows registry corruption. Resolution Method #1 Close Continuum and use Windows System Restore to put the system back at a point where the Event Viewer were fine. Method #2 NOTE: Any customization previously done to the event viewers such as column name changes etc  will be lost when this method is used Shut down CyberStation then backup the Windows registry as a precaution Edit the Windows registry and delete HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Access Event View Start CyberStation and open the event viewer which recreates the entry in the registry using default values.

Issue How to configure and test RP controller web service Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause In the RP application, a REST (Representational State Transfer) Web Service API is available to facilitate secure HTTPS communications and allow you to obtain BACnet objects and properties from the controller. Resolution The following video will illustrate how to: Use the SpaceLogic certificate configuration tool to configure keys and certificates in the RP controller. Configure RP controller Web Service settings. Use SoapUI to test RP controller Web Service. Things you need: Software EBO 2022 or later server (Enterprise Server, AS-P or AS-B) and WorkStation. SpaceLogic RP controller, RP-C Advanced, RP-C Pro, RP-C Pro Plus and RP-V Advanced, with firmware V4.00.01 or later. SpaceLogic Certificate Configuration Tool, available from Exchange. Tools SoapUI (to be used for testing) For more information and how to generate certificates, please check RP Controller | Developer Portal. Note: Before configuring the Web Services in RP controller, make sure that there no pending IP changes, by checking "Changes pending" property in IP Network Settings Properties – Basic Tab. If "Changes pending" is true, click Activate changes in the IP commands menu, as explained in Configuring BACnet/IP Controller IP Network Settings For EcoStruxure Building Operation version 4.0.3 or later, a new EBO Workstation command named Export device identifying information is available. It is found in the main context menu of SpaceLogic RP Series controllers and allows the user to save an xml file that can later be imported into the SpaceLogic Certificate Configuration Tool to aid in the efficient configuration of SpaceLogic controllers within the tool. The user may select one or more RP Series controllers when executing the command. Refer to: Exporting Device Information to the SpaceLogic Certificate Configuration Tool  

Issue When viewing WebReports one of the reports has a red dot Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause Need to understand what the red dot indicates Resolution When viewing the list of WebReports and the reports show one or more with a Red Dot, this designates the report as a dashboard report.  A dashboard report is a report that processes fixed or predefined filtering criteria to generate report output. Unlike prompted reports, dashboard reports process the report output based on the predefined filtering criteria and generate the report output when you select the report.  It is not necessary to enter filtering criteria or click the Run button to generate the report. Please see Dashboard Reports for additional information.

Issue When logging in to Web Reports, the "Reports Tree" to the left is not shown, and an error message is shown stating that login has failed for the user "NT AUTHORITY\IUSR". Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause This is a result of not following the Web Reports installation guide.  The SQL Server must be installed with an instance name, and the SQL Server must be started by the user "SYSTEM". Resolution There are two solutions to this issue: Reinstall the SQL Server and Web Reports following the installation guide Use the SBO Reports Agent Config tool on the Community to give access to the 'NT AUTHORITY\IUSR' Alternatively for a more in-depth answer consult How to Fix Login Failed For User NT AUTHORITY IUSRS to add the user "NT AUTHORITY\IUSR" to the SQL Server

Issue Remote Factory Reset of SmartX IP controller MPX RPC IPIO Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic RP IO Expansion Module Building Operation EasyLogic MP-C Cause From v3.1 there is a facility to remotely Factory Reset a SpaceLogic BACnet/IP devices (formerly known as SmartX) and EasyLogic BACnet MS/TP devices. A quick look at the process and what versions of SmartX controller firmware are required Resolution Remote Factory Reset fails if the Controller is at v2.00. Remote Factory Reset operates correctly if the Controller is at v3.00 or higher. A Remote Factory Reset on a Controller with Static IP is best avoided. Although a Factory Reset is now possible, it should not be considered standard work process, but it shows that using DHCP serving of IP addresses does have advantage if a factory reset is required.