Building Automation Knowledge Base

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue Script advise for xPDisplay on a b3/i2 controller Product Line EcoStruxure Building Operation Environment i2 and b3 Controller xP Display Cause The xP Display was designed when only Continuum was available (before EBO) and there was no documentation for EBO. Scripts need to be used to control the xP Display Binding to Object LCDAnswerString directly via "String Input" or "String Output" in a script program Then doing a check  If LCDAnswerString <> ""  then causes the script to disable with errors. "" = Null Resolution A simple way around this is to do the script check on another (manually created) string that is bound to the object LCDAnswerString Thus the following will work:  Numeric Input LCDKeyStroke       'bind to LCDKeyStroke    - this can also be used to set to zero. eg. LCDKeyStroke = 0 String Input LCDAnswerStrCopy   'bind eg LCDAnswerStrCopy  - use this to read the LCDAnswerString value String Output LCDAnswerString    'LCDAnswerString  - use this to set to Null eg. LCDAnswerString = "" Numeric Output AAA Line Wait4Value If LCDAnswerStrCopy <> "" then  'check if a value has been input    AAA = minimum(maximum(0, StrToNum(LCDAnswerStrCopy)), 100) 'Make AAA equal the input (min0, max100)    LCDAnswerString = ""     'reset LCDAnswerString back to Null Endif Outside this script, the manually created string object LCDAnswerStrCopy needs to be bound to LCDAnswerString, this can be achieved directly (change the binding type to COV) or via another script (use Print LCDAnswerString to LCDAnswerStringCopy) Note v4.0 export, script text attached and install guide attached

Issue An error message is displayed when trying to download all objects to a SpaceLogic controller. The error message says:   Offline '/SiteServer' Communication   Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Premium (AS-P) Automation Server Bundled (AS-B) Multi-purpose or Room-purpose (MP/RP) controller Cause This error can occur when the controller is an instance of a Custom Type (CT), but the CT only exists in the type library of the Enterprise Server, and not in the Automation Server hosting the controller. A BMS Server can only access it's own type library. See WebHelp article Custom Types for more information. Resolution Log in to the Automation Server where the MP/RP controller is hosted, and import the custom type to type library.

   

Issue The error "Failed to Invoke the Security Expert Suprema Component" is seen when attempting to register/enroll a user's biometric credential at a Security Expert Client Only machine.   Figure 1 - Suprema scan error   When doing a registration/enrollment from the Security Expert Server this error is not seen and the registration is successful. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause The Suprema.dll has not been properly registered on the local machine. Resolution First check in C:\Program Files (x86)\Schneider Electric\Security Expert folder and confirm that the three files Suprema.dll, BS_SDK.dll, and BS_SDK_V2.dll are all present. If they are not you will need to copy them over from a working installation of Security Expert Server Installation.   Now run the below commands via an Administrator authenticated command prompt session: For 64-bit machines cd C:\Windows\SysWOW64 regsvr32.exe “C:\Program Files (x86)\Schneider Electric\Security Expert\Suprema.dll” For 32-bit machines regsvr32.exe “C:\Program Files\Schneider Electric\Security Expert\Suprema.dll” You should get a pop-up saying the .dll was registered successfully. Close and re-open the Security Expert client and re-test enrolling a user's fingerprint.

Issue Valid Users are randomly unable to gain access when presenting at a Suprema biometric reader. Sometimes they are able to gain access but others they are not and see user denied events in the events window. User denied entry by entry mode error door mode is not correctly programmed using invalid reading device User Denied Event Product Line EcoStruxure Security Expert Environment Security Expert Suprema BioEntry W2 fingerprint reader Cause The sensitivity settings in the Suprema software are too sensitive resulting in missed fingerprint reads. Resolution Reducing the fingerprint sensitivity from the default setting of 7 to a setting of 5 may allow fingerprints to be read more reliably.   The sequence used to authenticate the User can also result in more frequent read failures. Presenting a valid card then an invalid (or bad read) fingerprint and then presenting the card again,  the sequence starts all over again and will result in a user denied event. If the user presents the correct finger (after presenting the wrong finger) or tries the same finger again within the configured timeframe they will be granted access.

Issue Suprema Fingerprint Reader Integration Product Line EcoStruxure Security Expert Environment Security Expert Suprema Fingerprint Reader Cause Security Expert integrates with Suprema BioEntry, BioEntry Plus, and FaceStation devices. Enrolment is both quick and easy with users scanning their fingerprint or face at an enrolment reader. The Suprema reader uses the scanned data to create a credential template, including a card number, which it sends to the Security Expert Server. Security Expert then sends this template to any other Suprema readers that are attached to the system so that only one enrolment is required. Resolution The following information is available on integrating Suprema Fingerprint Readers with Security Expert A list of qualified Suprema devices and configuration details can be found in the Suprema Biometric Integration in Security Expert Application Note. There are some available help topics in the online help. In the Security Expert  Client go to ABOUT | HELP and search for "Biometric Readers" and "Suprema". Each Suprema reader requires a wiegand port on a controller / expander, a license (SX-BIO-SP) and an IP address. The amount of Suprema readers allowed is only limited by these 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 for assistance. Issue WebClient's PHP version causes alerts in scanning tools like Microsoft 365 Defender   Product Line EcoStruxure Security Expert   Environment Security Expert Controller   Cause PHP version is outdated   Resolution This video demonstrates how to manually upgrade PHP in a Windows environment   Navigate to https://windows.php.net/downloads/releases/archives and download the required "non-thread safe" PHP7.4 x64 or x86 Stop the IIS Web Server (WinKey + R, type inetmgr, press Enter) Rename the PHP folder in C:\Program Files (x86)\Schneider Electric\Security Expert Web Client\ from "PHP" to "PHP_7.3" Create a new folder in "C:\Program Files (x86)\Schneider Electric\Security Expert Web Client" and name it "PHP" Extract the downloaded zip PHP 7.4.29 to the new "C:\Program Files (x86)\Schneider Electric\Security Expert Web Client\PHP" folder Copy the file "PHP.ini" from PHP_7.3 to C:\Program Files (x86)\Schneider Electric\Security Expert Web Client\PHP Start IIS Web Server Browse to the WebClient and confirm you can log in and view/add records etc   Note: SX 4.3.344.20 requires SOAP 1.6.0.11 and WebClient 1.47.1.3. This version of Web Client uses PHP 8.1.13.  While it is possible to manually upgrade this PHP version as explained above, 8.1.13 is the latest version to be tested/supported at this time.

Issue In a multi-version system, will the database schema in the PostgreSQL database be compatible with EBO servers with lower versions? 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 Building Operation Timescale Database Cause In a multi-version system the database schema in the PostgreSQL database needs be compatible with all servers in the system. Resolution The DB schema is backward compatible. The same schema can be used for the complete system and it can be upgraded to the latest version compatible with the top-level server. Compression is done on the PostrgreSQL/TimescaleDB side and since it’s not configured in EBO, the compression will work for EBO servers with lower versions. Compression needs at least schema version 9 for EBO2023 or schema version 13 for EBO2024 and TimescaleDB version 2.0 or higher, refer to: Compression for TimescaleDB

Issue How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  

Issue Received error 'IO Channel number out of range' when creating a door on AC1/AC1A/AC1Plus on an IO module.  The same door configured on a module with a lower IOU number saves successfully. Product Line Andover Continuum Environment Continuum CyberStation Netcontroller  AC Module Cause The IO module is configured with an IOU number that is above the MAX IOU modules supported by the NetController.  Note this is true even if there is only ONE module configured. Resolution Check the IOU module number entered in the door object (1) Check the Max IOU module supported (2)   Delete the IOU module and recreate it using an IOU number at or below the max IOU number supported by the Net Controller.

Issue Infinity controller error: Type not valid for this IO channel Product Line Andover Continuum Environment Continuum Cyberstation Cause ElecType mismatch between what is in the database and the field controller hardware. An example of this problem would be offline creating a voltage output on a DO-4.  It will save to the DB since it is a valid InfinityOutput configuration.   Although when attempting to do a Send to Controller the controller knows that point type is not valid on the specific IOU module hardware. This can also happen when an object is imported into Continuum because the database error checking is less strict than when creating the object online. Resolution Go into offline editing Check the point configuration If it does not match the field hardware, then correct it, save it, go to online mode and reload.

Issue The database is logging multiple alarm entries each time a point goes into alarm. Product Line Andover Continuum Environment Alarms MSMQ SQL Server Event Notifications Cause Various causes. Resolution The following is a list of conditions which may produce multiple alarm event logging. Network Latency  In cases where the network is extremely slow or workstation are overburdened, the process of logging alarms may be slowed to the point where a second alarm is sent by the controller while the previous alarm is still in the process of being logged. In one particular case the logging workstations associated with the duplicate log entries were all in India while the database server was in the US.  The problem was resolved by changing the ACCID of all of the India workstations to 253 or higher so that they were not involved in logging alarms. Database insertion errors If there are database insertion errors in the ACCTrace, Cyberstation cannot send an acknowledgement that the alarm event has been logged. Consequently the controller will continue to send the alarm event until it receives notification that the alarm has been successfully logged. Database Server latency It is not unusual to see Database Insertion errors when a Continuum DB server is struggling to keep up with the demands that the system has placed on it. A use Task Manager and other tools to evaluate the processor and memory consumption. Enhanced Alarm Logging and Enhanced Alarm Delivery. If Enhanced alarm logging/delivery is broken due not shutting down all workstations before doing a database update, it is possible to have combination of enhanced and old style alarm delivery.  The solution is to shut down all workstations and perform a db update with Enhanced Logging and Enhanced Delivery selected. Workstation Resources.  If the logging workstation is over burdened with reports, programs, extended log downloading, etc.

Issue This condition will arise after successfully installing and running Project Configuration Tool for some time. PCT 1.x can no longer initialize the virtual host adapter as a result of the adapter being deleted or removed. The errors may be a result of but not limited to: Introducing a new VPN software package to your PC/Laptop. Manually removing or modifying the Virtual Box Host Only - Network Adapter. Malware or Antivirus platforms that have removed or disabled the adapter. Example: PCT Version - 1.1.2.57 Local mode was set up on a physical laptop and used to offline engineer a project. The job was completed and PCT was not used again for roughly a month. A new project was sold and required PCT for offline engineering. The laptop was booted up and PCT failed to open. The user was presented with the following errors: "Get System State Command: 'Could not connect' " "Get predefined properties command: 'Could not connect' " "GetDashboardErrors Command: 'Could not connect' " "Get System Memory info Command: 'Could not connect' " Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only) Project Configuration Tool 1.x Cause PCT 1.x can no longer initialize the virtual host adapter as a result of the Vbox adapter being deleted or removed. Resolution Reinstall PCT 1.x on top of your current installation. Your projects will not be modified in the process. Locate the installer. Run the installer, it will ask you to remove the previous version. Press ok. Progress will show as uninstalling. PCT will prompt for installation. Click Next. Select default installation paths. Click Next. Select desired PCT mode. Click next. Ready to Install selected mode. Click Next. PCT software installed. Click Finish. Now PCT will set up the Virtual Host Adapter. Press Ok. Status bar. Compted setup dialog. Click Ok. Run PCT. If successful you will see the template sets getting installed via the top right of the window. Open a project and test an AS/AS-P. If the above steps do not work, here are a few more to try:   Restart the machine after the PCT software finishes re-installing Right-click and select “Run as Administrator” Uninstall PCT software and Oracle VirtualBox and re-install once more   If PCT 1.x still will not work, please open a support case with your local Product Support Group.

Issue Information for replacement for the SPA1505 and SPA1506 Product Line Field devices Environment Pressure sensors Cause "PA-00167 Sensors and Input Devices New SPP930 Relative Pressure Switch" suggests SPP930 replaces SPA 1505 and SPA 1506. The link provided for the SPP930’s manufacturer’s data sheet, no longer works Resolution SPP930 Part number 004701160 replaces the SPA 1505 SPP930 Part number 004701170 replaces the SPA 1506 The site wiring should be checked, to ensure it complies with replacement switches reduced current ratings.   SPA 1505/1506 data sheet Huba Controls type 620/625 data sheet.

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 Creating a report that shows which visitor is being visited Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause The standard visitor report does not record who at the site is being visited Resolution This video demonstrates how to create a visitor report that includes which users have been visited in the Security Expert System.   The advanced Visitor Report is created in 4 main steps: 1. Create an Access level for each user who receives visitors 2. Assign this Access level to the user's visitor tab 3. Create (or use existing) User report with the new "access level" column selected 4. Configure and run the user report   Creating Access levels 1. In Security Expert client, go to Users|Users a-Select a user who receives visitors (ex: John Doe) b-Go to the Visitor tab c-Check the "User supports visitors" box d-Click the ellipsis (3 dots) to open the Access Level window e-Click Add button f-Name it '[User]'s Visitors' (ex: John Doe's Visitors) g-In the configuration section, configure the access level required for the user's visitors h-Save and repeat for each user who normally receives visitors. Close the window and go back to the User table.   Assign Access level 2. Select "John Doe's Visitors" for Visitor access level -Save changes   Create User Report 3. Go to Report|Setup|User -Create (or use existing) report for visitors -Go to the Columns tab -Click Add and choose "Access Level" User Field -Save report setup   Configure User Report 4. Return to the general tab and expand the "Default user report filter" section. Press "edit in report view" and edit your desired layout -Save report view   The next time you run the visitor report it will print who's being visited in the "Access level 1" column

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

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 Create a report of all expired cards Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause A custom report and its configuration are needed to find all expired cards at the site Resolution This video demonstrates how to create and configure a report to find all expired cards in a system   Create a User Report: 1. In Security Expert Client, go to Reports|Setup|User and Add a new (or use an existing) report. 2. Configure the desired Report Type and Sorting 3. Go to the Columns tab, click the Add button and select Columns.  Make sure to have: -Expiration date of badge AND/OR Expiry date 4. Save your report   Please note: The "Expiration date of badge" column pulls the date from Users|Users|Extended Tab|Expiration date of badge. The "Expiry date" column pulls the date from Users|Users|General Tab|User expiry date/time section's End date.   Customize the User Report's layout: 1. Go to Reports|Setup|User| General Tab| Default user report filter and click the "Edit in report view" button 2. Right-click "Expiration date of badge" (or "Expiry date") column and select the Filter Editor 3. Change the "And" condition (in red) to "Or" 4. Change Equals to DateTime Operators: Is Yesterday 5. Click "+" sign in green circle to a line and repeat changes 5 more times for the following: - Is Earlier This Week - Is Last Week - Is Earlier this Month - Is Earlier This Year - Is Prior This Year 6. Click Save Report Layout

Issue EBO server (ES/AS/Edge) Trace.log shows COV publisher errors. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server - Standard Cause A BACnet device is misconfigured and trying to perform COV subscription that produces an error. Resolution Review EBO server Trace.log EXAMPLE:  2023-12-28 13:54:05.124 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:54:07.354 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:55:05.173 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:55:07.420 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:02.921 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:56:05.213 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:56:07.673 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:09.862 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:57:02.932 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:57:05.247 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:57:07.719 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:57:09.874 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:58:02.945 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:58:05.288 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:58:07.767 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:58:09.889 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f​ Lookup the BACnet Error Code: Decoding BACnet Errors - Schneider Electric Community (se.com) EXAMPLE:  0x8001001f is unknown object, so a device is trying to subscribe to an object (Object Type + Object ID) that does not exist. NOTE: There could be other error codes not used in this example that are reported. Enable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Information to Trace. Wait for time to pass so Trace.log can collect more records. Review EBO server Trace.log to find the new line before the error, identifying the controller with the misconfiguration. Example: MSTP device (MAC 3) on local MSTP network is misconfigured for unconfirmed COV to BV 202  2023-12-28 14:11:08.439 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 3 process 1: <binary-value, 202>, lifetime 18000s, unconfirmed 2023-12-28 14:11:08.441 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f​ Example: IP Device (MAC 192.168.198.136:47808) is misconfigured for confirmed COV to AV 204  2023-12-28 14:07:03.073 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 192.168.198.136:47808 process 1: <analog-value, 204>, lifetime 18000s, confirmed 2023-12-28 14:07:03.075 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f​ Disable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Trace to Information. Inspect the listed BACnet devices and correct the misconfiguration.