Issue Can the xPUI4 and xPDI8 expansion modules be configured in CyberStation to have the supervised ElecType? Environment xPUI4 xPDI8 xPUI-4 xPDI-8 Cause Can the xPUI4 and xPDI8 be used for supervised inputs? Resolution The xPUI4 can be configured with supervised inputs. The xPDI8 cannot be configured with supervised inputs. Note: For UL1076 listed security systems, the xPUI4 Expansion Module inputs must be configured as Supervised. Note: The xPDI8 Expansion Module does not support supervised inputs and cannot be used in UL1076 installations.  The above notes come from Document # 30-3001-504 UL 294 Access Control and UL 1076 Proprietary Burglar Alarm Systems Reference If using an ACX or bCX controller the xPBD4 and xPBA4 modules may also be used for supervised inputs, these are not compatible with the i2 or b3 controllers.

Issue Can Satchsize the valve sizing software be used with Windows 7? Environment Valve sizing Satchsize Cause Customer wishes to use Satchsize on Windows 7. Resolution Satchsize is no longer available and is not supported with Windows 7, but a new program is available. TAC Valve 1.8 UK can be downloaded from the Buildings Business Extranet. Once installed please use the help files installed with the program.

Issue Can I set up Auto Dial Auto Answer (ADAA) on a Host without using a 78041 Tap? Environment I/NET site Cause Can I set up Auto Dial Auto Answer (ADAA) on a Host without using a 78041 Tap? Resolution Yes. I/NET 2000 allows the host workstation to emulate a 78041 Tap. (TCON 209, 2-15)

Issue Can I install the Java7u25 patches in 3.5.25? Environment I/A Series G3 with multiple browsers Cause JAVA 7u25 prevents the Java applet from loading Resolution You must be at a level specified in the TPA before applying these patches.  See TPA-IA-13-0007.01 Java 7 Update 25 May Cause I/A Series G3 Niagara Applet to Fail.

Issue COV subscription links are being lost between MNB controllers Product Line TAC IA Series Environment MNB Controller Cause This is caused specifically by changing certain required link properties or by removing the objects that contain the link data. Resolution See TPA-RKFD-08-0001.00 "Avoid accidentally removing COV subscriptions (links) between MNB controllers" on The Exchange Download Center.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

Issue Alarm DB View Filter only works for timestamp. Other filter properties do not work. Below is an example of filtering the Source to find any alarms with the '1' in the source name. However, the results still include alarm with source names that do not contain '1'.  Environment I/A Series G3 version 3.5 and 3.6 Cause This is a known issue in the above versions of I/A Series G3. Resolution This issue is fixed in I/A Series G3 version 3.7.10 and above. Schneider Electric has released I/A Series 3.7.46 and 3.7.106 and they are available for download from The Exchange Download Center. It is recommended that you use the latest release version which is 3.7.106 as it includes many fixes for other issues. 

Issue Different Continuum products are approved to different approval standards and where are copies of these certificates held? Product Line Andover Continuum Environment All Hardware products: Standards listings to UL, BTL C-Tick, CE Cause Copies of the approval certificate or clarification on the different standards are required. Resolution The Agency listings each controller is approved against are defined on the datasheet, for more information see How do I get the part numbers and datasheets for Continuum products?. An example of the approvals for the bCX1 controllers are: UL/CUL 916, UL 864 9th Edition, FCC CFR 47 Part 15, ICES-003, EN55022, AS/NZS 3548, Class A, VCCI, EN61000-6-1, CE   All of the Regulatory Compliance documents including: UL, CUL, ISO,  European CE Certificates, Australia/ New Zealand  C-Tick Certificates and WSP Cert can be downloaded from The Exchange Download Center -  Regulatory Compliance   Confirmation of BACnet testing can be seen at the BTL website: http://www.bacnetinternational.net/btl/ European Standards - Continuum has been tested to the following as part of the 89/336/EEC Electromagnetic Compatibility Directive and over the years the standards have changed. Emissions -Continuum is tested against EN55022-Class A This is the emission standard for Information Technology equipment and another emission standard is the EN50081-1 but this is a generic emission level and less stringent than the IT standard that Continuum complies with. Immunity - These standards have changed over the years, older controllers were tested against the International IEC1000-4 and we state the specific levels our controllers are tested against, then when it was released in 2000 we used the EN50082-1 standard which replaced the IEC standard in Europe. But newer controllers have now been tested against the EN61000-6-2  standard that have since replaced the other immunity standards.    There is also the EN60730-1 standard that Continuum is approved to, this defines the standard controls specifications it can perform. These standards are required for us to apply the CE marking to our products.

Issue There are new versions of Continuum Reports, Archiver, Elevator Control, etc. that were updated by the Center of Excellence development team. These applications need to be upgraded prior to using Continuum 2.0 SP1 for sites that use these applications because of new memory mapping. Environment Windows 7 Windows Server 2008 Continuum Cause Continuum 2.0 SP1 uses a new memory mapping scheme that allows for better use of large memory addressing. The Continuum Add-on applications needed to be updated in order to work properly, so each of the applications has a new version. Installers need to know which versions to update. Resolution Below is a list of Continuum Add-on applications and versions needed to work properly with Continuum 2.0 SP1. Prior to installing Continuum 2.0 SP1, you need to upgrade certain Continuum Add-on Applications with new versions. It is recommended that you be prepared to rollback to Continuum 2.0 should critical applications fail to operate after the upgrade to SP1. You can download new versions of the following Add-on Applications from The Exchange at this URL: https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp Search on 'continuumreports' and locate the application.   Add-on Application 2.0 SP1 Compatible Version Access Groups 2.5.1 BioScrypt 4G V-Station Integration 1.12.1 CFR Extended Log Archiver CFR Access Event Archiver CFR Alarm Event Archiver CFR Activity Event Archiver Continuum Reports 23.0e Cogent MiY Integration 1.8.1 DVTel 6.x Video Integration 2.3.2 Elevator Control V2.6.6 2.6.7 EZ-GuardTour 1.2 EZ-Trap 1.9 Genetec Omnicast 4.8 Video Integration 1.1.1 Genetec Security Center 5.2 Video Integration 1.2.1 Personnel Data Importer Continuum Reports 23.0e Salient Video Integration 1.3.1 Stentofon Integration 1.8 Video Inquire 1.9.1   Customer-Specific Custom Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following customer-specific custom applications:   AckAlarm Area Templates PIM CADS DVTel Alarming Continuum-Excel Elevator Control V3.x Elevator Control V4.x Elevator - EasyLobby Integration Extended Log Exporter PIM 2.0 ScanShell Scanner Interface Surgard Integration Vicon Video Integration xTra    Legacy Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following legacy applications:   Area PIM Door PIM Elevator Control V2.4 Elevator Control V2.5 Unlisted Application       Download a pdf copy of this list click the following link:  Continuum Add-On Application version list

Issue Bindings to graphics and programs on SpaceLogic IP controllers are being unexpectedly added or removed. Product Line EcoStruxure Building Operation Environment SpaceLogic IP Controller Custom Types 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. Cause When a custom type is modified, a re-typing process is automatically triggered. The outcome of this process—specifically whether bindings are retained or lost—depends on the reference type used within the custom type. Resolution Care should be taken when designing custom types, as bindings within the type can be defined using one of three reference types: - No Reference Inner Reference Outer Reference Each reference type behaves differently during re-typing operations and can impact whether bindings are retained, added, or removed.     When a custom type is modified or re-applied (e.g., attached to an object instance, version-changed, or undo check-out), a re-typing process is triggered. The behavior of bindings during this process depends on how they are defined in the custom type:   No Bindings in Custom Type If the custom type does not contain any specific bindings, then during re-typing, existing bindings in the instance will be removed. Bindings Should Be Defined in the Custom Type To preserve bindings during re-typing, they should be explicitly added to the custom type using either: Inner References Outer References (with inner reference locked) Inner Reference Behavior If inner reference bindings are defined in the custom type, they will be automatically added to the instance during re-typing, even if they were not previously present. Outer Reference (Locked) Using outer references with inner reference locked ensures that bindings are preserved and not unintentionally modified during re-typing For more detailed information on the re-typing process and reference behavior, please refer to the Re-Type section in WebHelp.

Issue When a controller undergoes a cold start and has a valid backup archive, it defaults to retrieving files from the archive rather than requesting updated files from the server. Product Line Satchwell BAS & Sigma Environment Sigma UNC controller Cause The controller prioritizes its local backup archive during a cold start. This behavior prevents it from fetching potentially updated files from the server, which may be necessary in certain operational or troubleshooting contexts. Resolution There are two recommended methods to ensure the controller retrieves new files from the server: Option 1: Clear the Controller’s Archive Using SDCU Launch SDCU (Sigma Device Configuration Utility). On the main screen, click the Advanced button. Select Clear Archive to remove the existing backup. Upon the next cold start, the controller will request files from the server since no local archive is available. Option 2: Use Sigma System Diagnostics to Re-trigger File Download Open Sigma System Diagnostics. Initiate a file download from the server to the controller. Re-trigger the archive time schedule to ensure the new data is added to the controller’s archive.

Issue Can Sigma Logging Database be merged? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Server Cause Sigma Logging Databases are proprietary and not based on standard or open database formats. As a result, there are no commercially available tools capable of merging these databases. Resolution Merging Sigma Logging Databases is not supported. There are no internal or third-party tools available to facilitate this process.

Issue SDCU or Pocket Terminal fails to operate when connected to the service port of certain Sigma Controllers. Product Line Satchwell BAS & Sigma Environment   Sigma Controllers (UNCx96, UNC632, DNN, IC3) SDCU (Sigma Device Configuration Utility) Pocket Terminal Cause The issue may arise due to the PL* pluggable connector being occupied. This connector might be: In use by a SigmaCE device Connected to a serial device (e.g., Bluetooth) Pre-wired to another component Resolution   Identify the connector in use: UNCx96 → PL4 UNC632 → PL5 DNN / IC3 → PL5 Action Steps: Check if the PL* connector is currently in use. If so, unplug the connector. Reconnect the SDCU or Pocket Terminal and test functionality.  

Issue Clarifying the differences between Crompton and Modbus protocols when configuring IC Modbus networks, especially when integrating slave devices. Product Line Satchwell BAS & Sigma Environment Sigma IC3-Modbus Sigma IC-Modbus Cause Confusion arises when attempting to add Modbus slave devices to a network where IC Modbus is configured for Crompton. The two protocols handle data registers differently, which can lead to incompatibility. Resolution The key differences between Crompton and Modbus protocols lie in how they handle data registers: Modbus Mode: Reads 16-bit registers individually. Can combine two consecutive 16-bit registers to form a 32-bit word. Suitable for standard Modbus slave devices. Crompton Mode: Reads a single 32-bit register directly. Crompton devices inherently use 32-bit registers. Because of these differences: Modbus and Crompton slave devices cannot be mixed on the same IC Modbus network. Ensure the IC Modbus configuration matches the register format of the connected devices. Best Practices Always verify the register format of slave devices before configuring the IC Modbus. Use separate networks or gateways if both Crompton and Modbus devices are required in the same system.

Issue A local Sigma client fails to display the background image of a graphic, while remote or web clients display it correctly. Product Line Satchwell BAS & Sigma Environment Sigma Graphics Cause This issue typically occurs when a large image file is used as the background in a Sigma graphic. Local clients, especially those running on older hardware (e.g., netbooks or underpowered laptops), may lack the graphics processing capability to render these images properly. In contrast, remote clients or web clients offload rendering to more capable systems or servers. Resolution Recommended Actions: Check Hardware Specifications: Ensure the local machine has a dedicated graphics adapter. Recommended: 1GB graphics adapter supporting DirectX 11 (for Windows 7 systems). Reduce Graphic File Size: If upgrading hardware is not feasible, optimize or reduce the size of the background image files used in Sigma graphics. Avoid Unsupported Devices: Netbooks, servers, and low-spec machines are not supported for Sigma client graphics rendering. Consider replacing the PC with a modern workstation that meets or exceeds the recommended specifications. Additional Notes Most modern workstations can handle Sigma graphics without issue. Server-class machines are generally not suitable for running Sigma clients due to limited graphics capabilities. Users may also experience performance issues (e.g., slow loading, lag during editing) if the hardware is underpowered.

Issue Users and customers often confuse the terms hotfix and upgrade when discussing updates to the EBO platform. This article clarifies the distinction to help with proper planning and communication. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Central Server Building operation MP, RP and other upgradable field controllers. Cause The confusion typically arises due to: Similar version naming conventions (e.g., 4.0.1 vs. 4.0.1 CP1). Lack of awareness about the scope and impact of each type of update. Misunderstanding of the validation requirements for regulated environments. Assumption that all updates require the same level of planning and downtime. Resolution EBO Hotfix or Consolidation Point (CP) Purpose: Targeted fix for specific bugs or issues. Scope: Minimal — typically affects only a few files or modules. Impact: Low risk; does not change the database schema. Versioning: Minor version change (e.g., 4.0.1 → 4.0.1 CP3). Use Case: Applied when an issue needs resolution without waiting for a full release. Installation: Quick and simple; may not require full system downtime. EBO Upgrade Purpose: Introduces new features, performance improvements, and broader fixes. Scope: Comprehensive — affects multiple components and may include database schema changes. Impact: Higher risk and complexity; requires planning and validation. Versioning: Major or minor version change (e.g., 4.0.1 → 5.0.1). Use Case: Planned system enhancement, often requiring customer approval or validation. Installation: More involved; typically requires backups, downtime, and post-upgrade testing.

Issue A Plain English Script program that works correctly on an AS-P controller does not function as expected when used on a b3 or i2 controller. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server b3, i2 controller Script Program Cause Bindings are missing. Resolution To resolve this issue, ensure that all bindings are complete. The Script Editor provides a check that explicitly identifies this problem. For example, the Check may display the message Invalid Compilation:   Behavior Differences Enterprise Server (ES) and Automation Server (AS) Programs These programs can be saved and will function even if some bindings are incomplete. However, any logic relying on missing bindings may not behave as expected. b3 and i2 Script Programs These programs will save successfully but will not function correctly unless all bindings are complete. This is because b3 and i2 devices execute scripts at the firmware level, requiring all inputs and outputs to be fully defined and bound for proper operation.

Issue Editing a script program can result in bindings being lost or unintentionally removed Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Script Program Cause If a script program line labeled as "Numeric Input", "Numeric Output", or "Numeric Public" is modified and the change includes a syntax error or reserved word when saved, the binding for that line may be lost. For example, in the image below, all bindings remain intact   After editing the "Numeric Input" line and using a reserved word (e.g., allowed), the associated bindings are removed. Resolution Exercise caution when modifying script programs on an active site to avoid unintended disruptions. Always be especially careful when working with scripts running on a live plant.   In such cases, it is recommended to add a new "Numeric Input", "Numeric Output", or "Numeric Public" line rather than modifying an existing one. This approach helps preserve existing bindings and reduces the risk of introducing syntax errors or reserved words that could break functionality.   For example, the bindings shown below remain intact when a new line is added instead of modifying an existing one.   NOTE: This issue has been resolved starting from version 1.7.

Issue SpaceLogic MP-C and RP-C controllers may fail to download firmware to Room Units when sensors are connected to the sensor bus. Disconnecting and reconnecting the Room Units does not resolve the issue. Product Line EcoStruxure Building Operation Environment SpaceLogic MP Controller series SpaceLogic RP Controller series Cause The file system of the SpaceLogic IP controller has been re-initialized, resulting in the deletion of Room Unit firmware files. This can occur during a factory reset.  The Device Report can be used to verify whether the Room Unit firmware files are present on the controller. If the files are listed in the report—as shown in the image below—it confirms that they exist on the device.     If the Room Unit firmware files are not listed in the Device Report, the controller will not initiate a download to the Room Units. Resolution To resolve the issue, perform a firmware upgrade on the SpaceLogic IP controller.  Upgrading to the same version currently running will restore the missing Room Unit files. For further details, please refer to the RP Controller Reset Modes or MP Controller Reset Modes in Web Help, as extract below: - Important: A factory reset of an MP or RP controller affects the controller's ability to support upgrading connected devices, such as SpaceLogic Sensor devices, RP controller expansion modules, and Wireless Adapter - Advanced. This is because the necessary firmware files are deleted. After a factory reset, ensure that the controller is upgraded to restore the files needed to support upgrading the connected devices. For more information, see BACnet/IP Device Firmware Management .

Issue To run WebReports with EcoStruxure Building Operation (EBO) versions prior to 2022, specific versions of Microsoft SQL Server are required Environment EcoStruxure Building Operation (up to version 3.2) WebReports Cause Compability Resolution For EBO versions up to 3.2, the only currently supported SQL Server version is: Microsoft SQL Server 2016 (64-bit) Service Pack 1 or later Editions: Enterprise, Standard, Express with Advanced Services ⚠️ Important: SQL Server 2016 is in extended support until July 14, 2026 WebReports is not supported in EBO 2022 (v4.0) and newer Modern Alternatives For EBO 2022 and newer: Use External Log Storage with PostgreSQL + TimescaleDB. Schneider Electric provides a Data Migration Assistant (DMA) tool to help transition from WebReports to the new architecture. Installation Notes Ensure your Windows account has administrative privileges before installing SQL Server. Follow Schneider Electric’s SQL Server Installation Settings for optimal configuration.