Issue Can AC-powered sensors be connected to the same Central I/O module that already has DC-powered sensors? Or is it better to separate them across different I/O modules? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch UI Cause Is it technically feasible and advisable to mix AC and DC powered sensors on the same Central I/O module? Resolution Yes, AC and DC powered sensors can be connected to the same Central I/O module. Here's why:   Signal vs. Power Supply Regardless of whether a sensor is powered by AC or DC, the signal transmission (e.g., 0–10 V or 4–20 mA) is always DC-based. The type of power supply (AC/DC) does not affect the signal processing by the I/O module. Module Design Considerations All Central I/O modules share the same backplane, so separating AC and DC sensors across modules does not provide any electrical isolation benefit. The Signal Ground Rail (SGR) is critical. Each I/O module must be connected to the SGR to: Prevent current from flowing through the backplane. Ensure stable and accurate signal measurements. RET Terminal and Jumper Use Even if RET terminals are at the same potential, using a jumper between them can cause: Unintended current flow through the jumper. Measurement inaccuracies due to shared current paths. The SGR is designed to handle these currents safely and independently, avoiding interference between devices. Best Practice Recommendation Use the Signal Ground Rail (SGR) for all RET connections. Avoid relying on jumpers between RET terminals to prevent cross-device current interference. Mixing AC and DC powered sensors on the same module is acceptable, provided proper grounding practices are followed.

Issue Which port (P1 or P2) should be connected to the high and low pressure? Product Line Field Devices. Environment EasyLogic CP Series Differential Wet Pressure Transmitter (CP-LI-DP-TR-xxxx) Cause The product documentation does not clearly specify which port corresponds to the high-pressure side and which to the low-pressure side. Resolution P2 is the high-pressure port. P1 is the low-pressure port.  

Issue After installing or upgrading the Security Expert SOAP Service to 1.7.0 (or above), the Building Operation EcoStruxure Web Services (EWS) Hardware folder (container) under SecurityExpert appears blank, preventing users from viewing or Not possible to Host EWS Objects Objects in Building Operation no longer update Product Line EcoStruxure Security Expert Environment Building Operation Enterprise Server EcoStruxure Web Services Security Expert SOAP Service: Version 1.7.0.0 or greater Smart Connector Framework Version 2.5.5.108 Security Expert Smart Connector Extension: Version 1.2.0.22 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 correctly. Before beginning these steps, make sure all essential 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 This issue typically occurs when: Incompatible versions of SOAP, Smart Connector, or Security Expert are installed. The latest (or higher) Security Expert Smart Connector Extension (v1.2.0.22) is not used. The installation guide referenced is outdated and does not reflect the latest version requirements. Resolution To resolve the issue, follow these steps: If upgrading Security Expert, it is recommended to Uninstall any existing versions of: EcoStruxure Security Expert SOAP Service SmartConnector Framework Security Expert Smart Connector Extension Install the following versions as per the Instructions provided in Step 3: SOAP Interface: 1.7.0.0 or greater SmartConnector Framework: 2.5.5.108 EcoStruxure Security Expert: 4.3.370.1 or greater Security Expert Smart Connector Extension: 1.2.0.22 Follow the instructions in the updated installation manual: schneider-isc.uk/file/  Search for Document name Security Expert SmartConnector Version 1.2.0.22 - Installation & User Manual Download Extension v1.2.0.22 → Using this link schneider-isc.uk/file_download/, navigate to Smart Connectors Security Expert Smart Connector Extension V1.2.0.22.zip Additional Notes The current Security Expert - Smart Connector Extension - Installation Guide on the EcoXpert site does not yet include version 1.2.0.22. An update is pending. Please use the link above. Always verify that all components are aligned with the supported versions listed above.   .

Issue How can the IP address of a Standalone Automation Server be determined so that the password reset session ID can be retrieved? Product Line EcoStruxure Building Operation Environment Automation Server Cause Due to the lack of available information regarding the Standalone Automation Server, it is not possible to determine its IP address. Beginning with version 3.2, a password is required to log in via USB in order to obtain the IP address. Consequently, obtaining the session ID is not feasible under these circumstances. Resolution To reliably obtain the IP address of the controller, an alternative discovery method should be employed. The most robust and effective approach is to perform network traffic analysis using Wireshark. By monitoring broadcast or ARP packets during the controller's startup or communication phase, the IP address can be identified.    Prerequisites: Access to the device’s physical label to obtain its MAC address. Administrative access to a PC on the same network segment as the device. Procedure: Obtain the Device MAC Address: Locate the MAC address on the device’s label (e.g., 00:80:f4:46:d6:d2). Network Setup: Connect both the device and the PC to the same network segment (broadcast domain). For optimal results and minimal background traffic, connect the device directly. Start Packet Capture: Launch Wireshark on the PC. Select the appropriate network adapter and begin capturing traffic. Power Cycle the Device: Reboot or power cycle the device to initiate network communication. Apply MAC Address Filter: In Wireshark, use a display filter to isolate traffic from the device’s MAC address, e.g. eth.addr == 00:80:f4:46:d6:d2 or eth.addr == 00-80-f4-46-d6-d2 (It is possible to use either colon or dash notation) Identify the Device IP Address: Observe the captured packets for DHCP, ARP, or other IP-based communications from the device. The source or destination IP address in these packets will reveal the device’s assigned IP. Next Steps for the EcoStruxure Automation Server: Once the device IP is identified, access the EcoStruxure BMS Server. Set the server to Password Reset Mode. After resetting the password, Copy the Session ID  as required.  

Issue How to find the IP address information on a PC? Product Line EcoStruxure Building Operation Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows including and after Windows7 run a COMMAND window and run IPCONFIG.  

Issue Users are visible in the Security Expert thick client, but when accessing the Web Client, a persistent “Loading” icon is shown instead of user data. Web Client Loading Product Line EcoStruxure Security Expert Environment Security Expert Web Client 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 This issue is caused by hidden control characters—specifically the Unit Separator (US)—embedded in user data during the initial import into Security Expert. These characters are invisible in most editors but can be detected using tools like Notepad++ by enabling: View > Show Symbol > Show All Characters Unit Seperator Resolution Step 1: Identify Affected Users Copy the Unit Separator (US) control character between the brackets below: [] Open the Security Expert thick client. Navigate to the Users tab. Paste the US control character into the search field. This will return all users containing the hidden character. Step 2: Clean Up User Data For each affected user: Open the user record. Re-edit the First name, Last name, and Name fields. Ensure no invisible characters remain. Save the changes. Prevention – Best Practices for Data Import To avoid this issue in future imports: Sanitize data before importing into Security Expert. Ensure control characters (ASCII 0–31) are removed, except for common ones like tab, newline, and carriage return. Follow these recommendations: Export data in plain text (UTF-8) format. Use a text editor or script to scan for and remove non-printable characters. Validate CSV files using tools that highlight or strip out control codes before importing.

  Issue Timeout errors appear while attempting to download a controller assigned to the secondary download server after editing the configuration file to add a secondary Download Server Product Line EcoStruxure Security Expert Environment Security Expert Application Server Security Expert Download Server Pre 4.3.370.xxx versions 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 A Download pending and a timeout error may show when trying to download a controller assigned to the secondary server if the secondary download service isn't started or the configuration files have not been properly edited.     The Application Note AN 290 Security Expert - Setting up a Secondary Security Expert Download Server - Integration Guide describes changes to the SecurityExpertSV2.exe.config file required for the second download server. The SecurityExpertSV2.exe.config Modified Connection Strings section needs additional clarification and there is no mention of SecurityExpertSV.exe.config file in the application note which also needs to be configured. Resolution Open the An-290 Security Expert - Setting up a Secondary Security Expert Download Server from the link above. Follow all the steps up to the Server Configuration section on page 7. This article is to clarify just that section of the application note. (The app note will be changed in the future) Ensure both Security Expert download server installations are on a domain. Note: A multiple download server configuration will not work within a workgroup. Make a copy of 2 files: C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertSV2.exe.config and SecurityExpertSV.exe.config                                  Note: the different names of these files). Rename the original files or delete them Download SecurityExpertSV-SV2.exe.config.BLANK.zip from this article's attachment section and unzip both files into the C:\Program Files (x86)\Schneider Electric\Security Expert folder on the secondary download server Edit the new SecurityExpertSV2.exe.config file with Notepad++ or Notepad with admin rights Change the fields highlighted in yellow in the image below (PrimaryServerIP address, database name(if not using the default) and password), to match the site and save the file. Edit the new SecurityExpertSV.exe.config file with Notepad++ or Notepad with admin rights Change the fields highlighted in yellow in the image below (PrimaryServerIP address, database name and password), to match what the site configuration and save the file. Continue to Page 8 of "Setting up a Secondary Security Expert Download Server Integration Guide" to complete setting up the Secondary Download server

Issue A 7792 is used specifically for what? Environment I/NET site Cause A 7792 is used specifically for what? Resolution It is the interface to Micro Regulators (MRs) and Application Specific Controllers (ASCs), (TCON 209, 1-21)

Issue 7770, 7771, 797, 7801 TAP replacement needed with existing system. Product Line TAC INET Environment Existing TAC I/NET Seven environment Cause The 7771 was the first generation ICI that the 7797 platform replaced. The 7771 was built on the old 7801 tap hardware where was the 7798 was built on the 7790 MRI platform. Neither of which are supported or available to purchase anymore. System upgrade for more capabilities or capacity, or hardware failure Resolution For the 7801 tap hardware, the Xenta 527 would be a suggested choice for replacement. For the remaining TAPs, the Xenta 913 would be a direct replacement. The TAC Xenta 913 is a cost-effective way to integrate a large variety of products into a TAC network. The TAC Xenta 913 supports the most commonly-used open protocols, like Modbus, BACnet and LonWorks. It also supports some manufacturer-specific protocols, like I/NET and Clipsal C-bus. The TAC Xenta 913 acts as a gateway and transfers data point values from one network to another. Configuration is carried out using the TAC XBuilder programming tool. For more info including the documentation, manuals, and datasheets, visit the Schneider Electric Extranet at the following link, which guide you to the replacement for the ICI. TAC Vista > Technical Documentation > Specifications Sheets  

Issue 7718 and Expansion Modules Environment I/NET Site Cause What Expansion Modules come with the 7718 controller? Can those be bought separately? Can the ribbon cable or stand-offs be purchased separately from the P16UI expansion module also referred to as the P16UISO Resolution P16UISO 16 Point Universal Input Module 7718 PCU module, 8.6” x 3.4” (21.8 cm x 8.6 cm). Standoff mount. The Sixteen Point Universal Input (P16UI) expansion module provides sixteen universal (analog or contact) inputs. The expansion module card is 3.25"L x 8.60" W (8.25 x21.8 cm). It attaches on top of the 7718 with standoffs supplied with the module. Signals are passed from the P16UI through a ribbon cable type connection between the terminals of the two boards. The input points on the Sixteen Point E16UI Expansion Board occupy point addresses 0100 through 0107 and 0200 through 0207. Please find the 7718 Expansion board Input testing procedure below. Also here is the Datasheet Below is the part number from iPortal: This is the Model numbers and brief description:  Expansion Board Testing Procedure: 7718 Expansion board Input testing All 8 AIs (TBX1-1,4,7,10 and TBX2-1,4,7,10) come in thru the same analog multiplexer IC U3. The only components in front of the Mux is a .47uF capacitor on each input and a 100K resistor on each, and then the user plug-in resistors. I assume reference to TBX1 is associated with 1st input channel on pin 1 and 249 ohm is being plugged in to SIP socket RS3 position A1. Assuming no other resistors are plugged in to any of the Bx, Cx or Dx positions, there isn't much left that can be wrong. Get the specifics of what input signal level is causing what count to be seen. Use M & B of 1 & 0 to report straight counts. Make voltage measurements on the TBX1-1 and TBX2-1 terminals with signal being injected, and record the counts seen on the HHC, or PC, for a low medium and high level signal. An external power supply can be used in place of the sensor to easily set a 0V, 2.5V and 4.90V signal input. We want something less than 5V so we don't get the high end max count of 4095 which can mask a high end + error. If they don't have a supply, differing values of resistance can be plugged in to positions A1 (pull down) and B1 (pull up) with J10 set to B-C position so the B positions are pulling up to 5V. 1K in A1 position and B1 open produces 0V input. Measure and confirm volts and counts 1K in both A1 and B1 positions produces mid scale of approx 2.500. Measure and confirm volts and counts 10K in A1 and 1K in B1 positions produces high end of approx 4.545V Measure and confirm volts and counts This can be repeated on TBX2 using resistor positions A5 and B5 The A/D Counts should equal (measured volts / 5 * 4095) 2.500V = 2047 counts 4.545V = 3722 counts See what the above shows as a possible indication of where something is going awry. An A/D count that is correct on one input and wrong on another with only the specified resistances plugged in, or no resistances plugged and an external voltage source being used, would suggest a faulty multiplexer chip (on only specific selected channels) or a faulty capacitor. Return for repair.  

Issue Are 64-bit operating systems supported on the Andover Continuum product line? Product Line Andover Continuum Environment CyberStation webClient Cause Compatibility requirements for Andover Continuum with 64-bit operating systems Resolution Release 1.93 and earlier: For all machines with CyberStation or webClient software installed, only operating systems running in 32-bit environments are supported. 64-bit environments are not supported.  However, for the Database Server on a LAN system where no Cyberstation or webClient software is installed, a 64-bit version of Windows Server 2008 (SP2) or Windows Server 2008 R2 may be used on systems running V1.92 and above. These will also require Microsoft SQL 2008 running in 64-bit mode. Release 1.94 and later: Release 1.94 supports 64-bit Operating Systems, however, Microsoft recommends the 32-bit version of Office 2010 because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems. Please refer to the release notes for compatibility notes in specific versions.

Issue When the fan speed is set to level II on the STR the fan enable turns off on the 121 fc controller Environment 121 FC Firmware 1.26-11 Cause Some units of the STR106 and STR107 may have compatibility issues with the TAC Xenta 121-FC unit, concerning the manual Fan speed wheel function. bvfbfbanxdddcvSome units of the STR106 and STR107 may have compatibility issues with the TAC Xenta 121-FC unit, concerning the manual Fan speed wheel function. Resolution Upgrade the 121-fc to 1.26-14 or above. Here is the link with the upgrade files: Ecobuildings

Issue Preparing LonWorks Configurations for Upgrade You use this procedure when you want to prepare LonWorks configurations for a version 1.5.x upgrade, a version 1.6.x upgrade, or a version 1.8.x upgrade to a final 1.9.X or Higher version. WorkStation ONLY hotfixes are needed to Prepare the LonWorks configuration in order to upgrade to an SBO system 1.9.X or higher. Links to locating hotfixes on Exchange are needed. Product Line EcoStruxure Building Operation Environment SBO Workstation Hotfix Only v1.5.0.17121 SBO Workstation Hotfix Only v1.6.2.1220 SBO Workstation Hotfix Only v1.7.2.11111 Note: AS-P HW.62 required for a LON system with a minimum SBO Software revision at 1.7.2.X Note: For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 -Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 Cause Difficulties experienced in locating these files on the Exchange. Resolution Prepare LonWorks Systems Running Version 1.5, 1.6, or 1.7. For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 - Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 SBO Workstation Hotfix v1.5.0.17121 - Contact Country Level PSS SBO Workstation Hotfix v1.6.2.1220 - Contact Country Level PSS SBO Workstation Hotfix v1.7.2.11111- Link To prepare LonWorks configurations for upgrade via the WorkStation Only Hotfix: Bring the system up to the base version within your respective site to SBO V1.5, 1.6.2, or 1.7.2. Then apply the WorkStation Only Hotfix from the list above to your respective version. 1. In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to prepare for the upgrade. 2. On the File menu, point to LonWorks and click Pre-upgrade LonWorks configuration. 3. Click Next. 4. Click Finish. NOTE: Any EcoStruxure BMS that is currently at 1.8 or higher can be upgraded directly to 3.1 with one added note,  if the system has LON it will need to go through the LonWorks Pre upgrade before you can upgrade to 1.9.X or HIGHER. If you are upgrading from a version that is older than 1.8, read the documentation that describes the upgrading process for the relevant version.

Issue A method is required to purge orphaned ImageData records from the Security Expert database to free up hard drive space. Product Line EcoStruxure Security Expert Environment Security Expert  Microsoft SQL Server Management Studio (SSMS) 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 Running the SSMS Disk Usage report indicates what tables are the largest. The ImageData table is often one of the largest in the report and queries are needed to purge records. During transitions from Continuum, if Personnel/User records are removed, the GA_Blob table converts to the ImageData table. However, orphaned records may remain in ImageData because deletions in Continuum or Security Expert do not automatically remove associated image records. Resolution Use the instructions below to identify and select all ImageData records that do not belong to a user, then delete them from the database.   Note: Always validate the results of the SELECT query before running the DELETE command.   ✅ Step 1: Backup the Database In SSMS: Right-click the  SecurityExpert  database Navigate to:  Tasks > Backup Complete a successful backup before proceeding. ✅ Step 2: Identify Orphaned Records Run the following SELECT query in SSMS to identify orphaned  ImageData  records: USE SecurityExpert SELECT dbo.ImageData.ImageID FROM dbo.ImageData WHERE NOT EXISTS ( SELECT ImageID FROM dbo.Users AS T1 WHERE T1.ImageID = ImageData.ImageID ) This query will return all  ImageData  entries not linked to any user. ✅ Step 3: Purge Orphaned Records Run the following DELETE query to remove the orphaned records: USE SecurityExpert DELETE FROM dbo.ImageData WHERE NOT EXISTS ( SELECT ImageID FROM dbo.Users AS T1 WHERE T1.ImageID = ImageData.ImageID ) ✅ Step 4: Shrink the Database After deletion: Right-click the  SecurityExpert  database Navigate to:  Tasks > Shrink > Database ⏳ Note: Depending on the database size and number of records, this process may take several minutes.

Issue The Flex Server fails to power ON or boot up after first installation Product Line EcoStruxure Building Activate Environment ESXBFXSVR00B008 ESXBFXSVR0BC008 ESXBFXSVRBCW008 Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause “Live Insertion” of power supply to the Flex Server or “Hot plugging” the RS485 connector to the Flex Server can lead to internal component failures. These acts can induce transient voltage that exceed the design tolerances of sensitive components. These transients may cause internal components to fail, leading to MODBUS failures or Gateway boot-up failures.   What is “Live insertion”? “Live insertion” is the act of connecting or disconnecting a power connector to the device while the power supply is energized (powered ON).   What is “Hot Plugging”? “Hot plugging” refers to the practice of connecting or disconnecting a device to a system while it is powered on and running, without shutting down the system.   Resolution To protect the Flex Server and ensure long-term reliability, always adhere to the following steps (Safe Connection Procedure) when connecting or disconnecting the DC power supply or RS485 connectors: Connection Procedure: Before connecting or disconnecting the power supply or RS485 connectors, ensure the mains power supply for both the RS485 devices and FlexServer power adapter is completely switched off. Connect the DC terminal block and the RS485 terminal block to the correct sockets firmly, ensuring proper alignment and contact to avoid intermittent connections. Power on the power supply only after all connections are completed.     Disconnection Procedure: Before removing the DC terminal block and RS485 terminal block connectors, switch off the power supply first, verify it is de-energized. Then carefully disconnect the DC power supply and RS485 connectors.  

Issue How to get the data to display automatically (expanded) when running the Trend Log Comparison report. When running the Trend Log Comparison Report, the data is not shown in the tabular format automatically, and the + must be clicked on to expand this table to show the values.  Product Line EcoStruxure Building Operation Environment Building Operation WebReports Microsoft SQL Server Report Builder Cause When either using a Dashboard report or Exporting reports, some situations require the data to be expanded automatically when generating the WebReport.  The following discusses the changes required to be made to this report to allow this to happen.  Resolution To have the report automatically display this data fully expanded, the default WebReport "Trend Log Comparison" needs to be edited using Microsoft SQL Server Report Builder.  See the following online Help Topic for additional details on using Report Builder with Reports. Open the Trend Log Comparison report using Report Builder. Scroll down to the bottom section of the Report and select (left-click) the DateTimeStamp field Under the Row Groups, Right-Click on [DateTimeStamp] and open Group Properties. Select the Visibility and change this option to Show  Save the file - It is recommended to save the report with a new name and not alter the default factory report.  This new report must then be deployed to the WebReports Server.  This is done by Synchronizing the new report as detailed in the online help: Synchronizing WebReports with a New Report. Running the report should now automatically have this data expanded.  

Issue Confusion about the current release version of Security Expert and the limited release Security Expert for the Enterprise Download Service. Product Line EcoStruxure Security Expert Environment Security Expert Enterprise Download Service Cause Two parallel development branches now exist for Security Expert: Maintenance Builds –  version 4.3.370.19 (Released 2025-Jun-30 - latest stable release) Limited Release Builds –  version 4.3.386.2, intended for use with the new Enterprise Download Service. This has led to confusion because: The limited release version (4.3.386.2) has a higher version number than the current maintenance release (4.3.370.19).  The Supported Software 2025 landing page does not host the actual installation files for the limited release. Instead, it now provides a ZIP file containing instructions and a request form. Initially, version 4.3.386.2 was directly downloadable, but it has since been replaced with the ZIP package. Resolution To Access the Current Maintenance Release Visit the EcoStruxure™ Security Expert – Software and Firmware page on the Extranet. Sort the list by date to find the most recent maintenance version (currently 4.3.370.19 Released 2025-Jun-30).   To Access the Limited Release (Enterprise Download Service) Go to the Supported Software 2025 landing page. Select either: “2025 Enterprise Download Service (VM Bundles)”, or “Client/Server Security Expert - v.4.3.386.2”. Both links download the same ZIP file, which includes: Instructions for requesting the limited release. A site evaluation form that must be submitted  to TeamVipers@se.com who will review and provide the installation files.   If You Need to Roll Back from 4.3.386.2 to 4.3.370.19 or earlier Due to database version incompatibility, rolling back requires the following steps: Backup the current SecurityExpert and SecurityExpertEvents databases. Record the site’s license SSN. Uninstall the current Security Expert version. Important: Any configuration or event data added after the backup will be lost and must be manually re-applied. Restore the database backups from version 4.3.370.19 or earlier. Install the maintenance version (4.3.370.19).

Issue Projects fail to open in PCT. When checking the Diagnostics tab, the "/var/pct" partition is shown as 100% full.     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Accumulation of Server backup files can consume all available disk space in the "/var/pct" partition. 🔍 Note: Starting from PCT version 2.2.1, a warning is displayed when disk usage approaches full capacity. Resolution For PCT version 2.2.1 and later: Use the “Free up disc space” command available in the Diagnostics tab to automatically clean up unnecessary files. Or if it is not possible to get to the home page for PCT use the "Free up disc space" button here For earlier versions of PCT: Manual cleanup is required. Please contact Product Support for assistance. Cleanup must be performed by R&D. Additional Recommendations Regularly monitor disk usage via the Diagnostics tab. Periodic cleanup old server backups to prevent recurrence. Consider upgrading to the latest version of PCT to benefit from built-in disk management tools.

Issue The MyGet site previously used by SmartConnector developers to access NuGet packages has been shut down. Developers now need an alternative source for these packages. Product Line EcoStruxure Building Operation Environment Building Operation SmartConnector Cause NuGet is a package management system for .NET that simplifies development by providing access to pre-built libraries and tools. With MyGet no longer available, developers must transition to a new package source. Resolution SmartConnector NuGet packages are now hosted on the GitHub Package Registry. Follow these steps to configure access: Step-by-Step Instructions Create a GitHub Account Visit github.com and sign up using your email address. Generate a Personal Access Token Navigate to Developer Settings. Click Generate new token (Classic). Under Select scopes, check: read:packages (required) write:packages (optional, for publishing) Name your token and set an expiration. Click Generate and copy the token immediately (you won’t be able to view it again). Configure Visual Studio Open NuGet Package Manager. Add a new package source: Name:  SmartConnector GitHub Source: https://nuget.pkg.github.com/SchneiderElectricBuildings/index.json   Authenticate When prompted: Username: GitHub username or email used to sign up. Password: Your Personal Access Token.   Access the Package Once authenticated, you should see the latest SmartConnector NuGet package: v2.5.5.108 Important Notes All future SmartConnector packages released by the R&D team will be published via GitHub. Ensure your token permissions are correctly set to avoid access issues.

Issue "Enable incoming http communication" option is grayed out and cannot be unselected. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When Building Operation Workstation is connected to the SmartX Server using a HTTP connection, the option to disable incoming HTTP connection is unavailable.     Resolution Use HTTPS in Building Operation Workstation to connect to the SmartX Server to allow this option to be unselected. Refer to the Online Help Topic: Disabling Incoming HTTP Communication