Building Automation Knowledge Base

Issue When trying to run an EBO virtual server in PCT2 the following error message is received: Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information. Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The maximum number of running servers in PCT 2 has been exceeded. Resolution PCT 2 supports a maximum of 250 running servers. If this limit is reached with 250 servers already operational, no additional servers can be started.

Issue In some projects there is demand for importing a large number of individuals from an existing spreadsheet for individual information at one time. Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft SQL Server Management Studio Express Cause In some cases the customers have a spreadsheet or database of employees and/or users which they want to quickly import into their I/NET Seven Access control database. Resolution The whole process is to import the data from the excel file to the IDWorksView table of SQL database of I/NET. The steps below needs to be followed: Prepare the Microsoft SQL Server Management Studio Express. Click here to down this tool for version 2005 free of charge. If for version 2008, click here to download. Then install this tool. Download the individual spreadsheet Excel template and SQL script here. Save to the C:\. Ensure that the Tenant, Group have been added in I/NET already. Also ensure that all the card numbers in the spreadsheet don't conflict the ones already in I/NET. Enter the individual information into this template. If there are photos for individuals, the folder of the photos also need to be entered. Open the Microsoft SQL Server Management Studio Express and connect to the database. Find the InetDb database, and open the SQL script just downloaded from the File menu. Click Execute to run the script. Then if without any problems, the successful result will be shown in the output message window. The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality.  There is also a method that download the imported data without any operation in I/NET software by a function called Automatic DPU Restore. Refer to Automatic DPU Restore and Individuals added via Datacard ID Works are not getting access to doors for detailed information about how to set Automatic DPU Restore in I/NET. This is the method using SQL Server Management Studio Express. The Microsoft Access can also be used to do the importing work. Refer to How to import a large number of Individuals into an I/NET Access Control database for detailed information.

Issue When a SED-TRH-G-5045 sensor is positioned outside the range of the main EBO Zigbee wireless mesh, what is the recommended method or product to extend the wireless coverage? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause The SED-TRH-G-5045 is a Zigbee pro sleepy end device. Resolution Any Zigbee router within the system can function as a repeater to extend the radio communication. The router should be positioned within the radio range of the sensor and within the range of the RPx or another router. If a Zigbee device is powered by mains, it typically operates as a router. While there are currently no SE products designed solely with "repeater capability," several SE products possess router capabilities in addition to other capabilities, SE8000 SpaceLogic room controller Wiser plug CCTFR6500 Wiser Power Micromodule CCTFR6730 Wiser Room Thermostat with display CCTFR6400 or CCTFR6401. We have not officially tested any 3rd party Zigbee routers, however the IKEA TRÅDFRI repeater is known to work effectively.

Issue In Andover Continuum, the model name of a field device (i2/b3) is always obtained from the SQL database as there is no direct way to retrieve the model directly from the controller. Consequently, discrepancies between the model stored in the SQL database and the actual controller may lead to uprev errors like "This Uprev file does not match this type of controller"     In the screenshot above, note that both the device's editor as well as the command line, report the controller's model as i2800, when in fact the hardware associated with the device is an i2920.   Note: In EcoStruxure Building Operations, where a distributed database design is employed, the device's model type is always obtained from the proxy representing the device in the Automation Server. Product Line Andover Continuum Environment All i2s All b3s Cause Frequent model mismatches for i2/b3 devices in Continuum installations often result in errors when attempting to upgrade the device's firmware. Resolution To obtain the device's model (controller type) from the Continuum controller hosting the device follow the steps below: In the master controller, create an InfinityNumeric, in this example we will name it 'DevModel' In the master controller, create an InfinityProgram, in this example we will name it 'GetDeviceModel' Enter the following lines of code in the program... DevModel = <device_name> CntrlType Stop ***Replace <device_name> with your i2/b3 device's name   Note in the screen capture above, that the program reports the actual device's model to be i2920. The mismatch needs to be corrected by either installing the correct hardware or adjusting the model in the device editor in Cyberstation to align with the hardware.

Issue When attempting to update the firmware on the SP-MRDM module, the update process fails, and the module appears offline with the fault LED activated. A "Module not responding" error message is displayed that indicates the module should be disconnected, and a utility used to restore the firmware.   Product Line EcoStruxure Security Expert Environment SP-MRDM SP-MRDM2 Cause The module has lost its firmware during a failed firmware update attempt, leading to the offline status and fault LED activation. Resolution To resolve this issue, follow these steps: Establish a connection to the SP-C controller using a web browser. Force a module update operation from the Application Software tab. Note that it may be necessary to check the "Skip Verification" checkbox during the update process.

Issue When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The error may arise due to either the server's name not being unique or one of its child servers' names not being unique. Resolution To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.

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.

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 Log data is not being logged into SQL. The Reports Server indicates that the database is full.   This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL. Product Line EcoStruxure Building Operation Environment Reports Server Cause In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server. If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.   Resolution To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."   If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.     The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database: Download the latest SBO Reports Agent Config tool from the community. Load the Tool onto the Reports Server PC. Stop the Reporting Agent Using the Tool Press F7 to get to the Advanced Agent Configuration Page Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database. Press Ok Under the Maintenance tab of the tool - there are two options under Events  Delete future events, alarms, and trends  Delete events and alarms older than... Restart the Reporting Agent This will stop any further Events from being passed through to the SQL Database.  

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 The first batch of White TRCs (produced in 24H1) could appear too bright in some low-light level situations. All future batches (post 24H1) do not have the issue. See the precise list of affected serial numbers in the appendix section below. Product Line EcoStruxure Building Operation Environment SpaceLogic Touchscreen Room Controller Cause The housing color is set in the device’s manufacturing configuration to tell it what color the screen bezel is (black or white). White TRCs produced with an incorrect housing color will read a higher value for light level. This has a direct impact on the backlight dimming levels, and the only effect will be the screen staying brighter in dark rooms. Resolution Customers experiencing brightness issues may simply adjust the backlight brightness parameters to a lower value, which are configurable in the TRC configuration screens and via BACnet/Modbus. This would reduce the overall brightness of the devices immediately, without fixing the housing color. We recommend going with a permanent fix, by setting the housing color via the USB port. The steps to fix this permanently would be: Connect USB-C cable to TRC Log in as an administrator into the TRC’s configuration screens (to enable USB connection) Open a terminal app like hyperterm or putty, with settings: Speed (baud): 115200bps Data bits: 8 Stop bits: 1 Parity: None Paste in the command: #001000061009FE00009C! Device responds: #000E00071009FE0051! To confirm or test, paste in the command: #000C00001009FEE8! Device responds: White housing: #001200011009FE000000F9! Black housing: #001200011009FE000001FA! Examples Below is an example of 4 white TRCs: The two (2) outermost devices are too bright (leftmost and rightmost white TRCs). The two (2) devices in the middle have been corrected to show adequate brightness. Appendix Since the Touch Room Controller’s serial number includes the date code, knowing whether a unit is impacted is very straightforward. Follow these instructions to determine if the unit of interest is impacted: Retrieve the serial number from the unit you suspect has the incorrect housing color. Example: FL24075TRC00002 Examine the serial number date code, wrapped between the “FL” and “TRC” substrings. Example: 24075 Decrypt the date code, using this logic: 24: year 2024 07: week 07 of 2024 5: day 5 of week 7 of 2024 If the date code is between the values 24074 and 24285, the product is impacted. Products outside of this date code range are not impacted, and no fix to housing color will be needed.

Issue Identify which Access Expert LDAP Active Directory Keep version is installed Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Access Expert LDAP Active Directory Keep Integration Active Directory Cause Windows Control Panel Programs and Features doesn't indicate which version of the LDAP Active Directory Keep Integration is installed Resolution Login to Access Expert and the Instance that has LDAP Active Directory Installed Navigate to the General Configuration Tab> LDAP Agents LDAP Right Click on the LDAP agent and select View Event History Note: You may need to change the Priority from 50 to 0 and the Date Range to see an event Expand (Click the plus sign) of one of the LDAP Events (i.e LDAP Agent - Started) The version of the LDAP Active Directory Keep installation will show

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 NiagaraNetwork point subscriptions get stuck constantly reporting 'Pending Subscribe' or are 'unsubscribed'. Product Line TAC IA Series Environment I/A Series Jace (N4/AX) I/A Series Enterprise Server (Niagara Framework N4/AX) Cause Various configuration issues between the Jace and Enterprise sever. Resolution Troubleshooting 'Pending Subscribe' or 'Unsubscribed' (N4 or AX): Performing 'Manual Disconnect' on the Niagara Station 'Client connection' may clear this state. Perform 'Manual Disconnect' on each side of the Niagara Network connection between the two stations having issues. It is possible that one side of the Fox connection might show connected on the 'Client Connection' and the other side shows disconnected for the associated 'Server Connection'. The manual disconnect clears this state. Check for multiple FOX services. Typically there is only one service, though there are use cases for more than one. Sometimes the FOX service is mistakenly duplicated and both services then have the same ports, which is incorrect and causes problems. Use the ProgramService (Batch Editor) to look for 'custom object', 'fox', 'foxService'. Either delete the extra service(s) or edit the ports so to remove any conflicts. Duplicate station names can cause fox problems. Look at station 'Spy', 'fox', 'log index' to see all the fox connections. Look for duplicate station names that have different IP addresses. Duplicate station names can cause stations to keep getting disconnected as each station fights to be connected. Duplicate stations can be caused when an integrator connects their engineering laptop to a network and they have stations running on the laptop that were engineered for that job, thus resulting in more than one instance of a station running at once. In rare instances stations were installed multiple times at a site and not renamed before installation into the next platform. Fox connection getting dropped. Either network issues on the LAN or duplicate stations. Or denial of service attack on the Supervisor. Wireshark can help diagnose LAN problems or have the IT person on site look at your station IP addresses.  Try increasing the Request Timeout and the Socket Option Timeout in the Fox Service. Make Fox wait longer before timing out on messages. It is not typically needed to modify these defaults.  Regarding AX and N4 mix, make sure when an AX is connecting to an N4, the user in the N4 station, being used by the AX, must have the AXDigestScheme for the authentication scheme.  The Cipher Suite Group setting in the Fox Service must be set to 'Supported' when connecting any AX version prior to 3.8u3 (3.8.311) to an N4 station via NiagaraNetwork. Make sure Provisioning is correctly configured. If not being used, remove it. This might be an N4 only problem, but there have been instances encountered where a station that was converted from AX to N4 was having the 'Pending Subscribe' issue due to NiagaraProvisioning being only partially configured. Provisioning not correctly configured will cause the 'Pending Subscribe' problem  

  Issue Identifying table sizes is useful when managing Security Expert databases Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Server Cause Managing the size of a SQL database is crucial to system performance and archiving so understanding which tables are the largest provides needed data Resolution A report can be run from SQL Server Management Studio(SMSS) on the Security Expert and Security Expert Events databases to provide table sizes. Open SMSS Right-click on the database the report is needed (i.e. Security Expert or Security Expert Events) Select Reports> Standard Reports> Disk Usage by Table Scroll through and observe which tables contain the most data Examples: Security Expert DB Security Expert Events DB Print or Export the report to a file if necessary Print Export to Excel, PDF or Word Right-click on the data results and select Export

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

Issue Continuum NetController fails when a port scanning tool runs a network port scan on the ethernet network where the controller is connected. Some of the controller failures that have been reported to Product Support Services include controller scan locked, controller resetting, hanged, stuck in bootloader etc. In some cases the controller may be running but exhibiting very strange symptoms due to its tasks scheduling being disturbed by the scanning traffic and/or due to memory corruption. Product Line  Andover Continuum   Environment Continuum CX Gen 1 Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Continuum bCX4040 (BACnet) Continuum bCX4000 (Router) Continuum bCX9640 (Infinet)   Cause The legacy Continuum controller's network stack is not able to handle some of the packets generated by network scanning tools, most such tools explicitly point out that older internal systems may not be able to handle the port scanning traffic and may fail during the process.  The controller error log may show some variation of the following errors...   219 I 08/10/2024 13:14:53.35 0xbadd0018 0x00002500 0x001783f0 0x40602004 0x0017eeb4 Reset (Spurious interrupt)   4914 I 09/14/2022 09:00:54.00 0xbadd0002 0x00002600 0x02001bd4 0x48082600 0x020ffbb8 Reset (access error) Resolution The Continuum NetControllers are now legacy systems no longer in active development, therefore, the only known solution is to add  the controller's IP address to the tools white list so that no port scanning packets are directed to the controller.   It is important to note that NONE of the Continuum NetControllers listed above use Windows or Linux based OS, this makes them less vulnerable to the typical hacker attacks.    Andover Continuum is a legacy Schneider Electric product. We strongly encourage upgrading your system to the more secure and feature-rich platform, EcoStruxure Building Operation. 

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