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 The Media Gateway Card is unable to send panel messages to the converter, which translates the panel language into Modbus/BACnet protocols. Product Line ESMI Fire Detection. Environment FFSULH1007. Cause The TCP/IP port on the Media Gateway Card is not functioning correctly, impacting BMS integration with the panel. Resolution Check Firmware Version Navigate to Engineer Options → System Information. Ensure the LAN cable is connected to ETH 1 port. ETH 0 should be set to DHCP. Verify the firmware version: Expected version: S794_V01.109 Firmware Update (if needed) If the version is not visible or outdated, update the firmware. Refer to this article: Esmi Ultima Media Gateway Card Firmware Update Configure Graphics / Third Party & VR Settings Go to Engineer Options → Configuration → Panel Module → Media Gateway Card Select Graphics / Third Party Settings and apply changes as per reference images.   Submit the settings. Then go to VR Settings and apply changes as per reference images. Outcome After applying the above steps, the issue should be resolved

Issue Understanding common Modbus error codes that appear in Building Operation trace logs. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Modbus Cause Modbus protocol errors are seen when looking at Building operation trace logs. Resolution Below are common Modbus error codes observed in trace logs, their meanings, and example log entries. Error Code 4 – Server Device Failure Message: RESP_DATA_MISMATCH Meaning: This error indicates that the Modbus slave device encountered an unrecoverable internal error while attempting to execute the requested command. This is a problem within the slave device itself, not a communication error on the client side. Possible Causes: Attempting to write to a protected memory area Device in an unsuitable state for the command Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.767 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 4 Error Code 10 – Illegal Data Value Message: Flush buffer. Protocol error code = 10 Meaning: This error suggests the slave device rejected a data value sent by the master. Possible Causes: Value out of acceptable range Attempt to write to a read-only address Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.774 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 10 Error Code 7 – CRC Header Issue Message: Flush buffer. Protocol error code = 7 Meaning: This error indicates a CRC (Cyclic Redundancy Check) mismatch in the response message. Possible Causes: Incorrect CRC calculation by the device Incomplete or corrupted packet Example Log Entry: 2025-07-22 10:14:39.636 [1666360064] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 7

Issue Need a Menta programming solution to monitor pulse signals from water, electric, or gas meters. Product Line TAC Vista Environment Vista Workstation Cause A Menta program is required to interpret pulse signals from various utility meters. Resolution The Menta macro provided below is configured to receive and process pulse signals from three types of meters: Water meter Electric meter Gas meter You can download the source file by clicking the image of the Menta macro below: Additional Notes This macro can be customized to suit different pulse rates or meter types. Ensure proper signal conditioning if the pulse signal is noisy or irregular.

Issue When attempting to install the Loytec NIC software, the USB driver installation fails and an error screen is displayed. Installing USB Drivers Failed LOYTEC NIC Driver Installer Error Installing USB Drivers: Could not pre-install Drivers Product Line TAC Vista Environment Vista Server Cause The failure occurs due to insufficient administrative privileges, even when logged in as a domain administrator. The installer requires local administrator rights to successfully install USB drivers. Resolution To resolve the issue, follow these steps: Locate the installer executable file (.exe) for the Loytec NIC software. Right-click on the file and select “Run as…”. Choose the local administrator account (not the domain admin). Proceed with the installation. The USB drivers should now install successfully. Additional Notes This issue is commonly encountered in environments where domain policies restrict driver installations.

Issue Step-by-step instructions for installing and configuring a Loytec NIC852 dongle (Orion Stack) for enhanced LNS communications. Product Line TAC Vista Environment Vista Server Cause A single Vista server typically supports up to four average-sized LNS networks. Larger networks or multiple LNS ports on one server can degrade communication reliability. The Orion Stack modifies how Vista communicates with the LNS Server, allowing support for up to 28 LNS Ports. Resolution Pre-Installation Notes If LonWorks Interfaces were previously configured as your Network Interface, delete the computer’s IP address from the IP-852 tab before proceeding. Installation Steps Insert the NIC852 Dongle into a USB slot on the Front-End computer. Ensure the dongle remains plugged in at all times for Orion Stack functionality. Install Required Software using the Loytec CD: Hardware drivers LConfig interface Update Drivers Download the latest NIC interface drivers from: Loytec Driver Downloads Verify Installation The Loytec symbol should appear in the Windows system tray. Right-click the icon and launch LConfig. NIC852 Configuration via LConfig In LConfig, go to the NIC852 tab: Enable the device Set Transceiver to IP-10L Select the number of LNS Applications (LNS databases) Click CNIP Configuration: Enter IP addresses for: Device (Front-End Computer) Configuration Server Enter the Device Name (Computer Name) Click OK twice to apply settings Test the configuration before closing Vista & LonMaker Setup Open LonMaker: Open the first drawing directory with “Show all network options dialogs” checked Configure the Network Interface: Check “Network Attached” Select the first NIC_852 entry Proceed through dialogs by clicking “Next” Save and exit To configure each LNS network interface: Go to LonMaker > Network Properties in Visio Use the Network Interface tab to select the correct NIC   TAC Network Communication Port Setup Open TAC Vista System Plug-In: Navigate to LonMaker > System Plug-In > TAC Vista System Plug-In Right-click the Network (top of controller tree) Click Settings Under the Network tab, select Communication Port – Loytec Click OK Update the TAC Network Repeat Steps 6–10 for each LNS database: Use a different Network Interface for each Final Notes Once all NICs are configured, the Orion Stack setup is complete. Tip: Add a note on the site’s main graphics page indicating that an Orion Stack is installed. This helps inform remote support engineers and other users.

Issue The TAC Vista to SmartStruxure Interface fails to connect when the operating system is set to a non-English format. Product Line TAC Vista Environment Vista server Cause This issue occurs due to the Windows Format setting being configured to a non-English language. The interface requires the format to be set to English for proper connectivity. Resolution To resolve the issue: Open Control Panel in Windows. Navigate to Region and Language settings. Under the Formats tab, change the format to English. Click Apply to save the changes. Note: This issue is resolved in Vista version 5.1.9. For instructions on creating the Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. It uses the OPC Server to retrieve data from or send commands to the hardware. Resolution Supported Functionality OPC UA Client functionality is available in EBO version 6.0.1 or higher. Refer to: OPC UA Client Support Currently Not Supported OPC UA Server OPC DA Client/Server DDE Configurations Alternative Integration Options If integration with unsupported protocols is required, consider the following alternatives: Protocol Conversion Use a converter to translate between OPC and a protocol supported by EBO. Examples: OPC Server → BACnet Server EBO BACnet Points → OPC Recommended 3rd Party Tools (not supported by Schneider Electric): Kepware Matrikon SCADA engine Note: Ensure the EBO server's role is clearly defined (e.g., exchanging point values) to determine compatibility. SmartConnector Extension Use a SmartConnector Extension as middleware between EBO and an OPC client/server. Resources: Exchange shop SmartConnector Server EBO SmartDriver and Smart Connector Additional Notes These integration methods involve 3rd party software and may require additional configuration and validation. Schneider Electric does not provide support for 3rd party tools.

Issue When attempting to connect from a TAC Vista Remote Workstation, the following error appears: "Ensure that TAC Vista Server is started" This occurs even when DCOM settings appear to be configured correctly. Product Line TAC Vista Environment Vista Server Workstation Cause This issue typically arises when both the TAC Vista Server and the Remote Workstation are part of a workgroup rather than a domain. In such configurations, authentication and DCOM communication can fail if certain conditions are not met. Resolution To resolve this issue: Verify DCOM permissions are correctly configured on both the server and the workstation. Ensure that the Administrator account password is identical on both machines. This is necessary for authentication in a workgroup environment. Restart both the TAC Vista Server and the Remote Workstation after making changes. Additional Notes This issue does not typically occur in domain-joined environments, where centralized authentication handles these permissions. For more information on DCOM configuration, refer to the TAC Vista DCOM setup guide

Issue Users are unable to open files from a TGML graphic in TAC Vista Webstation using the OpenFile command. Product line TAC Vista Environment Vista Webstation Vista Workstation Cause The OpenFile command is not supported in web browsers, which prevents documents from opening directly in Webstation. Resolution To enable file access from TGML graphics in both Workstation and Webstation, follow these steps: In TAC Vista Workstation Use the OpenFile button as usual. Files (PDF, DOC) open without issues. In TAC Vista Webstation The OpenFile command does not function in a browser. Instead, define a hyperlink in TAC Vista: Place the document in the server folder: C:\Inetpub\wwwroot Use the format: http://<ip_address>/<docName> Typical Graphic Behavior Document Type Workstation Behavior Webstation Behavior PDF Opens normally Opens in same window (even with _blank target) DOC Opens in extra window (must be closed manually) Opens normally Additional Resources For an alternative way of viewing the reports and other files, refer to TAC Vista - Web Reports - Schneider Electric Community

Issue Is it possible for multiple Automation Servers to be placed on the same backplane and use one power supply? Some known issues in this unsupported configuration: Automation Server only partially discovers the IO Modules Function Block Programs (FBP) remain in an unloaded state (see FBP Unloaded) EBO 2022 (v4.0) and higher, Alarm: IO Driver unexpectedly timed out Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (EBO 2022 and above) EcoStruxure Building Operation Power Supply (PS-24V) EcoStruxure Building Central IO Modules Cause The terminal bases provide a path for communication between all connected units on the same backplane; as such, the connection of two or more Automation Servers will cause communication issues between all connected units on that same backplane. See the following article on how to check the CIO node the Automation Server is using: How to identify Automation Server(AS) ID node count   Resolution From EBO 2022 (v4.0.1) due to changes in the Central I/O (CIO), checks are now made in the Automation Server to verify that the server is physically in SLOT 2; if this is not the case, then all Tasks are disabled and will not run.    You cannot connect more than one Automation Server to the backplane. Only one Automation Server is allowed per power supply, the architecture is always "PS-AS-....." and after that I/O modules with additional PS units as needed, but only one Automation Server can exist on the same backplane.   Note that an alarm will also generate if you attempt the following configuration (also not supported)  PS-AS-PS-AS  Alarms will only clear after a restart (warm) of the server 

Issue After adding an OPC UA server to EBO an export is done from the Device discovery tab to find the objects in the OPC UA server. When the OPC UA server database is big this can take up to a day to finish and sometimes the export is never finished. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause In EBO version 7 there is a workaround for this issue, it is possible to split the export up in smaller pieces and export objects from specified folders from the OPC UA server instead of all objects in the OPC UA server database.   Resolution Introduction The ‘Export configuration’ section in the settings dialog for discovered devices makes it possible to configure the export procedure. By setting the parameters in this section, you can specify the start node and the depth for each export file. This means that you can break down the export into many files instead of one large file containing everything. When importing the series of export files it is recommended to keep the same structure as the OPC UA server has, but it is not a requirement. You can import the export file anywhere under the device, but again, the recommendation is to keep the same structure as on the OPC UA server.   Selecting start node for browse The start node is specified by setting the ‘Start node namespace index’ (specified as an integer value) and the ‘Start node identifier’ (specified as a string value). The supported ‘Start node identifier’ types are string (s=), integer (i=), opaque (o=) and guid (g=). Both ‘Start node namespace index’ and ‘Start node identifier’ are found as properties on each OPC UA object. If these values are empty, faulty, equal to the object node or equal to the root node, the device object is included in the export file. Otherwise, it is omitted. Selecting the depth of browse The depth of an export file is specified as an integer value. It is recommended that this is set to a low number if the export time is expected to take a long time. Values 0, -1 or empty means that no depth limit is used. Getting started   A first step could be to export the root objects. The following configuration will handle that: The export file with this configuration will produce the following result when imported. Since the ‘Start node namespace index’ and the ‘Start node identifier’ are empty, the device object is included, and the import can be done on the ‘OPC UA Client Network’ object Only the root objects were included in the export file since the ‘Export depth’ was set to ‘1’. Next, we would like to populate the ‘BuildingAutomation’ object with 2 levels of child objects. For that we need the namespace index and the identifier of the ‘BuildingAutomation’ object found at the bottom of the property list:   These values are entered into the export configuration: The export file with this configuration will produce the following result when imported on the ‘BuildingAutomation’ object: Now we have a structure with all the root objects. All of them are empty except for BuildingAutomation that has two levels of child objects.   If you realize that the depth chosen was to low, you can simply set the ‘Export depth’ to a higher value and create a new export file from the same start node. The ‘Export configuration’ will now look like below: When importing the new export file we still use the ‘BuildingAutomation’ object as the start object, but since we already have two level of child nodes we need to select the merge option in the import dialog as in the picture below:    

Issue Encounter Queue Full Exception in context of "Error writing BACnet point" Product Line EcoStruxure Building Operation, TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Jace 9000 Niagara Station running as SoftJace or 3rd Party Jace Cause If you notice queue overflow messages in the station dialog, it is essential to know which queue is overflowing. There are many different communications mechanisms in BACnet, and they use different queues. Resolution The canonical reference article is located on Niagara Community: BACnet Tuning Suggestions I have excerpted the following as a Rule of Thumb for the recommended starting configuration: Configure your tuning policies so that write-on-start is not enabled on some of the points - otherwise, the JACE may start with a to-do list that is larger than the queue can handle. The recommended configuration from Tridium is to set BACnet WriteWorker queues to 1.5 times the number of writable points. However, as initial configuration, Product Support has found these values to perform better than the defaults, so change the following values from 1000 to 3000. View the BacnetNetwork Property Sheet Expand Bacnet Comm Expand BACnet Comm -> Server -> Worker and Confirmed Worker Expand BACnet Comm -> Transport Change the various Queue Sizes from 1000 to 3000. Please consult PSS if a change to a value higher than 3000, as that has been found to adversely affect performance. 

Issue  EBO can have license violation bar without a known reason. 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 License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community See this article if you do not see the License banner, but still get a License Violation alarm: License Violation Alarm Triggered Without License Violation Banner displayed - Schneider Electric Community  Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.

Issue Unable to configure reverse proxy for SAML-based Single Sign-On (SSO) in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause Although EBO 7.0 has enhanced reverse proxy support, this does not include SAML SSO and EBO does not support reverse proxy configurations for SAML SSO.  This limitation prevents successful integration when a reverse proxy is used in the authentication flow. Resolution At this time, EcoStruxure Building Operation version 7.0 does not support reverse proxy configurations for SAML SSO. This is a known limitation. An enhancement request has been submitted to the Idea Forum to address this functionality in future releases.   To support this request, please visit the Idea Forum and click the thumbs-up icon on the SAML reverse proxy support idea to increase its visibility to the product management team.

Issue Users need a way to identify all Forced Variables without manually inspecting each point. The goal is to have a summary view—not via Reports Server—but directly accessible on the Automation Server (AS) or Enterprise Server (ES). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no built-in summary page in versions 1.4.1 and older that lists all Forced Variables. This makes it time-consuming to locate which points are currently forced. Resolution You can locate Forced Variables using the system tree in the Workstation. Navigate to: ES/Servers/AS/System/Modules/RuntimeDBManager/VariableManager/Variables Ensure the isForced column is enabled to view which variables are forced. Additional Notes: This method provides a quick overview without needing to open each individual point. It is especially useful for troubleshooting and auditing system behavior.

Issue What does it mean when a TAC controller is said to have a Universal Input? Product Line TAC Vista Environment Xenta Programmable Controllers Xenta I/O modules Cause The term “Universal” is commonly interpreted to mean compatibility with all types of inputs. However, this definition does not accurately apply to TAC Xenta controllers. Resolution In the context of TAC Xenta controllers, the term “Universal Input” refers to compatibility with multiple types of input signals, but not necessarily all types.   Key clarification: It is essential for project planners and system designers to consult the specific device’s datasheet to understand the exact definition of “Universal” as it applies to the particular TAC Xenta model in use. This ensures proper configuration and avoids misinterpretation during system design and implementation.

Issue After the "Windows is shutting down" message, Windows displays a non-specific memory error: lmadmin.exe - Application Error The instruction at "0x00000000" referenced memory at "0x000000". The memory could not be read. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause This issue is caused by Flexera Software, the licensing software used within Building Operation. Flexera does not support Windows XP, which leads to this error during system shutdown. This is a known limitation and will not be addressed in future updates. Resolution There are no known operational impacts associated with this error. It only occurs during shutdown of a Windows XP machine. Upgrading the operating system to a supported version will eliminate this error. Additional Notes This issue is cosmetic and does not affect system performance or licensing functionality. Users are encouraged to migrate away from Windows XP due to broader security and compatibility concerns.

Issue How can the firmware version of Security Expert Smart Card Readers be determined. Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause It is not possible to easily identify the firmware which a reader has been shipped with. Serial Numbers are not sequential and cannot be used as general guide. Resolution There are two supported methods to determine the firmware version of a Security Expert Smart Card Reader: 1. Via Product Support If you need to identify the original firmware version shipped with a reader: Raise a case with Schneider Electric Product Support. Include the reader’s serial number in your request. Product Support will contact Manufacturing to obtain confirmation of the firmware version originally installed on the reader. 2. Via Controller Web Interface (Requires Reader Expander Firmware 1.12.605 or later, Security Expert Controller Firmware 2.08.1498 or later, SP-C-WEB Firmware 4.00.2261 or later) From firmware version 1.12.605 and above, the Security Expert Controller’s web interface displays the serial numbers and firmware versions of connected card readers via RS-485 or OSDP. Steps to View Firmware Version: Log in to the Controller Web Interface. Navigate to Application Software. Open the Module dropdown to view connected readers. Important Notes: Wiegand-connected readers are not displayed in the web interface. If the Reader Expander address has changed, a power cycle is required for the readers to reappear in the interface.  

  Issue Understanding the size of individual tables within the Security Expert databases is essential for effective database management. This insight helps optimize system performance and supports archiving strategies. Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Server Cause Managing SQL database size is critical to maintaining system performance. Identifying which tables consume the most space provides actionable data for optimization and archiving. Resolution To determine table sizes in the Security Expert and Security Expert Events databases, follow these steps using SQL Server Management Studio (SSMS): Open SSMS Right-click on the relevant database (e.g., Security Expert or Security Expert Events). Navigate to: Reports > Standard Reports > Disk Usage by Table Review the report to identify tables with the largest data footprint. Examples: Security Expert DB Security Expert Events DB Exporting the Report You can print or export the report for documentation or analysis: Print Export to Excel, PDF or Word Right-click on the data results and select Export Note: The “Disk Usage by Table” report is available in SQL Server 2008 and later.

Issue Sites using Report Server need to upgrade to EcoStruxure Building Operation (EBO) 2022 or higher, where WebReports/Report Server is no longer supported. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server is not supported in EBO 2022 (version 4.0) or higher. Resolution To address this, Schneider Electric provides a Data Migration Assistant (DMA) tool that: Reads data from WebReports 3.x Writes data to External Log Storage Download the DMA Tool External Log Storage Overview Stores historical data from EcoStruxure BMS Storage capacity is limited only by your hardware Historical data is displayed in WorkStation and WebStation (event and trend views) Any server can be configured to write data to TimescaleDB   Any server in the system can be configured to write historical data to the TimescaleDB database. Licensing Requirements External Log Storage requires a license Refer to: Software and Features that Require Licenses Part Number Summary and Hardware Software Matrix Hardware & Software Requirements Ensure compatibility with: TimescaleDB PostgreSQL Recommended specs for large systems (e.g., 100 BMS servers): High-performance SSD Minimum 64 GB RAM Additional CPU capacity Refer to: IT System Planning Guide Merging Log Data External Log Storage reduces extended trend logs on BMS servers You can merge extended trend logs into source logs in External Log Storage See: Merging of Trend Log Data Enhanced Reporting (XLSX Templates) EBO servers (v3.2 or higher) support native reporting with: Text and XLSX formats Advanced XLSX features: formulas, conditional formatting, charts, sparklines Historical data pulled from External Log Storage (PostgreSQL/TimescaleDB) Refer to: Examples for Native EBO Notification Reports