Building Automation Knowledge Base

Issue Project Configuration Tool 2 can't be installed due to error "An error occurred trying to start process 'powershell' with working directory. The system cannot find the file specified." PowerShell can't also be started by Command Prompt, as shown in below screenshot, with error "'PowerShell' is not recognized as an internal or external command, operable program or batch file."   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Windows PowerShell path is not added to PATH environment variable, so it cannot be started by PCT installer.  Resolution Add PowerShell path to PATH environment variable by following below steps: Using Start menu, search for "Edit the system environment variables".                            Click on "Environment Variables".    Double click on "Path" variable located in the system variables list. Click New and add PowerShell path to the list then save the changes. %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\     Try to start Power Shell in Command Prompt. If it can be started as shown in below screenshot, retry the PCT 2 installation.   

Issue Debugging SpaceLogic MP and RP controllers Modbus RTU Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RP-C) Building Operation RP-V VAV Building Operation EZLogic RP-C Building Operation EZLogic RP-V Cause There is no packet data can be logged or viewed for Modbus MP and RP controllers and RP controller has no transmit and receive LEDs for the Modbus and no packet data can be logged or viewed. Article Modbus in the MP and RP Controller Introduction provides information on the differences between the Automation Server and MP and RP controllers Modbus operations. Resolution There are a couple of options, but they involve using another device connected to the Modbus network to view the packets Use a PC based Modbus slave simulator Use an Automation Server set up as a Modbus RTU slave, the packets can be sent to the trace log then viewed in the usual way.  Note: A defect with v3.2.1 EBO means this solution cannot be used to monitor a Modbus RTU bus because the AS replies to all requests and may cause conflicts on the network. All versions 3.1.2 and earlier work fine, as well the EBO 2022 (v4.0.1) as detailed in the Known Issue Modbus Slave incorrect response Can use Picoscope to perform Serial Decoding for Modbus RTU as detailed in Picoscope Configuration for Modbus RTU capturing and decoding

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Issue Modbus RTU communication is not performing as expected, and there is a need to review electrical installation or request/response packets. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller Building Operation Room Controller Building Operation EZLogic Room Controller Cause Picoscope hardware and software provide the ability to review the electrical waveforms and decode as Modbus RTU Resolution Ensure proper setup and connection of Picoscope probes Set the switch on probes to 1X Connect the probes using the color coding on each end to ensure the connection is as follows: Connect Probe A to TX/RX - Connect Probe B to TX/RX + Connect the probe black reference alligator clips to the cable shield drain wire. Ensure the drain wire is connected to EGND at one location. Connect the Picoscope to the PC, then open Picoscope software and choose the device connected. Set the Scope Use 1 ms/div for 38400 baud Follow this thread for more information since BACnet and Modbus are both RS-485 protocols. BACnet - PicoScope Basics - Schneider Electric Community  Select Channel A Set to +/- 5V Select Channel B and repeat the setting. One may change to +/- 10V if you encounter spikes above the 5V range (overvoltage warnings).  Add Math Channel Click the Math Channels icon Select A - B  Add Serial Decoding for Modbus RTU Click Serial decoding icon Select MODBUS RTU On Page 1 select Master A - B Change Baud Rate to known baud rate, usually 38.4 kBd Change Parity to known parity, usually NONE (1 Stop Bit) Leave the rest at default and click Next  On Page 2 Recommend leaving as default of HEX, knowing you will have to convert for Slave IDs over 09. Leave the rest at default and click Finish  Set Waveform Adjust thumbnail size to preference Leave Capture Time = On (default) Set Max Waveform to 2000 (example has 5000)  Start and stop capture and select Waveform as example Set Trigger Using a waveform, set the threshold voltage just above the blue line voltage. For example, the blue line is at 0.8V, and the threshold is set at 1.92V. Adjust based on your collected waveform(s) Set the Pre-Trigger 0% puts Yellow Diamond to the left and 100% puts Yellow Diamond to the right. The recommended setting is between 5% and 20% (for example, 20%).  Start capturing Set Serial Decoding for MODBUS RTU to show buffer The Current Buffer shows only the waveform on the screen.  All Buffers show everything.  NOTE: The Buffer Number column references the waveform number

Issue What is the unit load of a TC900 thermostat and what are the bias and termination requirements when used with a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment TC907-3A4LMA TC907-3A4DLMSA TC907-4FMSA TC907-3A4DPMSA TC907-3A4DPMSA-24 TC903-3A4LMA TC903-3A4DLMSA TC903-4FMSA TC903-3A4DPMSA TC903-3A4DPMSA-24 SmartX Server Cause Documentation does not state the RS-485 transceiver type for the TC900 range, making it unclear how many devices can exist under a SmartX servers RS-485 serial port ComA or ComB. Resolution Use the Worksheet for Configuration of RS-485 Bus with generic RS-485 devices on Webhelp to determine the appropriate Modbus configuration. The answers to the transceiver interface attributes below can be applied to complete the worksheet. Q1 Failsafe Receiver : The TC900 uses an RS-485 transceiver with an integrated idle-state failsafe receiver. Q2 Data Transmission Speed : TC900 thermostats can be configured to communicate at 4800, 9600, 19200 or 38400 bps. Q4 Isolated Interface : The TC900 does not provide an isolated RS-485 interface. Q6a Measured Resistance : With no electrical connections to the TC900, the measured resistance between the RS-485 low-side (-) signal and the communications common is 8.2K ohms. Based on this the unit load of the TC900 is 1.46 (12.000/8,200) Bias requirements and number of devices If there are only TC900 devices on the RS-485 bus then Generic RS-485 Network Device configuration 1 applies, configuration becomes very simple and no node or distance reductions are called for. The failsafe receivers can typically operate with no added bias resistors. Connect a 120 ohm termination resistor across the + and - data lines at the head end of the bus (typically at the SmartX server). Connect another 120 ohm termination resistor across the + and - data lines on the last node at the far end of the bus. Connect the shield drain wire to earth ground terminal rail in the panel with the SmartX server. This is the only ground connection of the shield for the complete cable segment. Connect the RET/Shield terminal (see the figure below) on the SmartX server to the ground rail in the panel using a 12 AWG (3.31 mm²) to 18 AWG (0.82 mm²) wire. Since the TC900 has a unit load of 1.4 the maximum number of devices that can be placed under each comm port using this configuration is 21 (31.5 / 1.46 = 21.5) Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange. Note:  Adding an RS-485 Repeater at this point provides another 32 Units Loads to the Network which can be continued up to the Architectural Maximum defined for the hosting controller.

Issue Customer are running an ES with version 3.2.3 sending emails through SMTP server using TLS protocol. After site is upgraded to version 4.0.3, emails are not sent and the following error is shown in the ES: "SSL routines: tls_process server_certificate:certificate verify failed. Email service failed to connect to SMTP Server." In version 6.0.3, the following error is also displayed in the ES: "error:16000069:STORE routines::unregistered scheme" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 4.0.1 and later Building Operation Automation Server Premium (AS-P) version 4.0.1 and later   Cause The following is stated in the EBO version 4.0.1 release notes: "Certificate validation for SMTP When choosing TLS as encryption method (i.e. encryption of all traffic) for SMTP, then the certificate will be validated from EBO 4.0. If a corresponding CA-certificate isn’t present in the server, then a system alarm is generated. See more in “CA Certificate Management” ( also in section 2.17.5) how to import CA Certificate." Resolution In EBO version 4.0.1 and later a valid certificate needs to be installed if alarms should be sent when using TLS protocol in the communication to the SMTP server.

Issue What ground connections are required when wiring a voltage input? Product Line EcoStruxure Building Operation Environment AS/ AS-P Power Supply AS-B Universal Input Modules 0-10V, 0-5V sensors Cause The required connections are different for isolated and non isolated voltage inputs. Consideration of the system grounding is also required. Resolution If your input sensor is isolated it can be directly connected to the UI and RET terminals of the Universal Input module. An isolated sensor will have 4 terminals (2 power terminals G0 and G, 2 output terminals M and X) the power ground G0 is not directly connected to the output ground M terminal. However for non isolated sensors (usually 3 terminal devices) the signal terminal X will be wired to the UI input, but the sensors signal common G0 should be wired directly to the Signal Ground for the installation, not to the RET terminal of the IO Module. On every Input modules ensure that one RET terminal from the IO Module is wired directly to the Signal Ground. Full details of the required wiring and an example wiring drawing showing isolated and non-isolated voltage inputs can be found in "Wiring" section of the Hardware Reference Guide available on the Download Center or in WebHelp: Wiring.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

  Issue Is it possible to host the same third party BACnet device on the AS-P private networks on multiple automation servers, which are all connected on the same network? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause The design in question is a 3-storey accommodation building which includes 1 x BMS panel/AS-P per level. However, only 1 x Mitsubishi EW-50E BACnet gateway is being provided for the building. Resolution It is possible to host the same 3rd party BACnet device in multiple AS-Ps. Some caution is required, however, because if the user makes changes to an object in that device through one AS-P, that change may not be reflected in other AS-Ps. When viewing runtime variables, such as 'Value' and 'Status Flags', this is not a problem because the EBO server will always get new values from the wire. Where the problem can present itself, is when changes are made to configuration values because these are only updated in an EBO server during an upload operation. For example, if you set the hi-limit and low-limit values in an analog-value object from one AS-P, those values will not be updated in other AS-Ps until you do an upload of that object.   The other place where this problem may present itself is in schedules. An EBO schedule only writes values to a device when that value changes. For example, if you have a schedule configured to change the setpoint to 65 degrees at 5pm, EBO will only write a value of 65 if the current 'local' value is not 65. If this schedule only writes 1 time per day and someone has set the value to 70 from another AS-P, the first AS-P does not realize the value has changed so that schedule will not generate a write request to set the value to 65 (it will stay at 70). However, if you have a program or trend-log monitoring the value, the AS-P will be tracking that value and realize it is not 65 so you will see a write request at the scheduled time.   The system works this way because reading all values of all devices and all objects all the time is simply not practical. As long as the user is aware of how the system is designed, they can avoid these potential issues.   Make sure to use Static IP, so IP do not change, or you get multiple DHCP servers on the same network.   Another alternative is to host the BACnet device in one AS-P only, then using internal bindings to share the data with other AS-Ps.

Issue When attempting to save & deploy a function block program using Modernized Programming, the following errors are seen: EBO 2022 - Deploy program error: The program was not deployed! (Error Code - 1073740940) EBO 2024 - Deploy program error - Invalid data "Empty binary file' Invalid data  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation EBO 2022 EcoStruxure Building Operation WorkStation EBO 2024  Function Block Programs (Builder for Function Block) Cause Related to known issue Modernized Programming Builder program error during deploy This is when the TEMP / TMP User variable folder paths contain a space; this can be edited in the Environmental Variables.  Resolution Edit the TEMP and/or TMP paths so that they do not contain any spaces.  To edit the Environmental Variables, follow these steps:  1. Click on the Start Menu button located at the bottom-left corner of your screen. In the search bar, type "environment variables" and press Enter.  Click on the "Edit the system environment variables" option from the search results. This action will open the System Properties window, which contains various tabs and settings for your computer. In the System Properties window, click the "Environment Variables" button located at the bottom right. Clicking this button will open another window specifically for managing environment variables.  In the Environment Variables window, under the "User variables" section, "Edit" the path that contains any "spaces".  These paths can be located anywhere on this PC.  User variables apply only to your account, while system variables affect all users on the computer. Choose accordingly, and then add or edit variables as needed. Once you have completed these steps, your new or edited environment variables will take effect.  Restart WorkStation, and the program should now deploy successfully.   

Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementation cannot process BACnet services such as RPM, COV, etc. Resolution Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <ignore-unhosted-devices/> 3.2.3.9005 and higher (*)   Users can create a rule under the BACnet interface to configure SBO not to use the service. Some rules are global, while others can be for specific BACnet devices. For particular BACnet devices, they are specified by 'Vendor Identifier' and 'Model Name,' which need to match exactly as shown in that device's Properties - Advanced Tab.   Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. 

Issue When a very long path is included in a request to the SmartConnector RESTful EWS gateway, such as when attempting to acknowledge an alarm with a long path, the gateway returns the error "HTTP Error 400: The request URL is invalid."   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Bad Request - Invalid URL</h2> <hr><p>HTTP Error 400. The request URL is invalid.</p> </BODY></HTML> Product Line EcoStruxure Building Operation Environment SmartConnector Cause In Windows, the default maximum number of characters in a URL path segment (the area between the slashes in the URL) is 260 characters. When the object path, after double URL encoding, exceeds 260 characters, it triggers error 400. Resolution To resolve this issue, follow these steps: Add a registry key "UrlSegmentMaxLength" to the following path in the SmartConnector PC registry: Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Name: UrlSegmentMaxLength Type: DWORD Value: 0 - 32,766 (e.g., set the value to 1000) After adding the registry key, restart the HTTP services or restart the PC. Detailed instructions for this process can be found in the "Http.sys registry settings for Windows" guide on the Microsoft Learn website. Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn

   

  Issue Packets from the EBO onboard packet capture utility are not ordered correctly. In the example below it can be seen that the sequence number of the ACK comes before the REQ despite the timestamp for the ACK being later than the REQ.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation SpaceLogic Server   Cause Out-of-order packets are quite normal on a TCP level. Earlier packets can arrive later due to buffering and other reasons. Applications are able to buffer these messages and rearrange them before they are written to the application.   Since the standard Wireshark pcap utility that EBO uses to capture packets does not sort packets in a batch by time stamp before delivering them to the capture file it is subject to the same irregularities that we would see on any OS.   Resolution This is a common enough issue that Wireshark includes a command line utility named reordercap that can fix packets that can't have been on the network in that order (like an answer being sent before you see the request for it).   In the example below the utility has run through a capture and reordered items and saved the file as a new file.     See the Wireshark reordercap help topic for further information on this utility.

Issue Any third party BACnet client can initiate an EBO backup. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause As of EBO 2023 (5.0.2.109), EBO's BACnet backup operation requires no password which means any BACnet client with the EBO server BACnet interface's device ID can initiate an EBO backup without any restrictions. Any such backup can be identified by looking at the backup description in EBO, the backup will explicitly indicate that it was generated by third party BACnet Workstation.   Resolution EBO 2024 (V6.0.1) or higher: In BACnet Interface basic tab, "Restrict backup and restore service" can be set to Yes to ensure that third-party BACnet clients cannot perform a BACnet backup or restore on the EcoStruxure BMS server. Refer to: BACnet Interface for an Automation Server – Basic Tab and BACnet Interface for an Enterprise Server – Basic Tab   EBO 2022 (4.0.4CP2 or higher) and EBO 2024 (V5.0.3 or higher): A rule can be added to the BACnet service_blacklist to disable BACnet backup service. See https://community.se.com/t5/Building-Automation-Knowledge/BACnet-RULES-implementation-to-disable-features-such-as/ta-p/839 for details on how to create service_black list.   Use the following syntax to create a rule that restricts BACnet back up initiated by 3rd party BACnet client on the EBO server.   <blacklist> <global> <restrict-backup-service/> </global> </blacklist>   Any BACnet client requesting backup from EBO server configured with the above rule will be presented with error similar to screenshot below.

Issue WorkStation can't connect via secure communication (HTTPS) to EBO server, although it can connect via non-secure communication (HTTP). Cloud connectivity also fails. WebStation can still connect via HTTPS. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation WorkStation Cause TLS V1.3 is supported in Windows 11 and Windows Server 2022 or later. Enabling it in earlier Windows versions is not support it can lead to problems, as explained in Protocols in TLS/SSL (Schannel SSP) - Win32 apps | Microsoft Learn Resolution Do not enable TLS V1.3, If the installed Windows version doesn't support it (Windows 10 and Windows Server 2019 or earlier), or disable it if it is already enabled by following the below steps:  Open Windows Registry Editor, by writing "regedit" in Start menu.  Goto registry path "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client" Make sure that "Enabled" is set 0, and "DisabledByDefault" is set to 1, this will disable TLS V1.3 for clients.  Restart WorkStation.   For more information, refer to: Transport Layer Security (TLS) registry settings | Microsoft Learn Warning! Improper use of regedit may damage PC’s operation.

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 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 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.