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 The F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Issue You need to forward specific events from Security Expert to a third-party Syslog server for monitoring or logging purposes. Product Line EcoStruxure Security Expert Environment Security Expert software Syslog server (e.g., SolarWinds) Cause There is a requirement to send filtered Security Expert events (e.g., operator activity, user access, door unlocks, output activations) to an external system for analysis or integration. Resolution Security Expert allows you to forward events using the Send Event action. Follow these steps to configure it: Step 1: Create an Event Filter In Security Expert, go to the Events menu. Create a new Event Filter that captures the specific events you want to forward. Example: Filter for events like  Output <PGM_NAME> On By <DOOR_NAME> Function <DOOR_FUNCTION> . Tip: You can trigger these events by manually unlocking a door from the client to test the filter. event filter Step 2: Create a Send Event Action Still under the Events menu, create a new Action. Set the following parameters: Type:  Send Event Event Filter: Select the filter you created in Step 1. IP Address: Enter the IP address of the Syslog server. Port: Enter the port number used by the Syslog server (e.g., 514 for standard Syslog, or a custom port used by Packet Sender). action Step 3: Test with Packet Sender Use Packet Sender to simulate a Syslog server. In Packet Sender: Note the TCP port number shown in the bottom right corner. Ensure this matches the port configured in your Security Expert Action. The IP address should be the one assigned to your Security Expert server (e.g., your laptop’s IP if testing locally). Manually trigger the event (e.g., unlock a door or activate a relay). status page Confirm that the event is received in Packet Sender’s log window. packet sender

Issue How are user profiles (accounts) configured in Esmi Ultima Fire Panels? Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Access levels allow permissions to be assigned to different user types. Resolution User Accounts Maximum Accounts: Up to 63 user accounts can be created. Permissions: Access group or singular permissions as set out within each user group. Profile Configuration User Levels: The example above shows User Level 2 in Group 1. Group numbers increase as more groups are added. Session Timeout: Range from 1 to 255 seconds for the function button availability after login. Function Buttons: Selected according to users who need access to the group. Panel Permissions: Additional permissions can be set in the User Menu Options section. Event Log: Records individual user activity. User Profile Example Username: Up to 20 characters. Passcode: Should contain 5 or 6 numerical characters. User Level: Mike Allerton is the 4th user, placed in User Level 3. User options Panel Control Interface: User activates the interface and enters their passcode to unlock screen and panel permissions. Function Option Button: Provides access to the buttons as described earlier.

Issue Detector showing internal trouble. Product Line ESMI Fire Detection. Environment FFSULH2001. FFSULH2003. 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 If the analogue value of a detector measured by the panel is outside of the normal operating range (≤41 to ≥95) the panel will show “Internal Trouble” indicating that the detector is faulty and should be serviced. Resolution Replace the faulty detector.

Issue Installing a Flex server/gateway that supports multiple industrial and building automation protocols (e.g., BACnet IP, BACnet MSTP, Modbus RTU, Modbus TCP/IP, SNMP, OpenThread, and LoRaWAN) at a live site is complex and requires careful planning. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal 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. 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 Improper installation often leads to degraded performance or unreliable device behavior Resolution Site Survey & Environmental Considerations Physical Location: Choose a secure, climate-controlled, and accessible location (e.g., equipment room or control panel). Install in a locked cabinet or secure room to restrict access. Power Availability: Ensure a dedicated, stable power supply with proper grounding. Use a UPS for critical applications to prevent data loss during outages. Network Infrastructure: Confirm availability of Ethernet ports for BACnet/IP, Modbus TCP/IP, and internet access. Install Ethernet cables in wall cavities or conduits. For cellular networks, monitor data usage and set up alerts to avoid over usage charges. RF Environment (LoRaWAN & OpenThread) LoRaWAN: Conduct a radio-mapping survey to determine optimal gateway placement. Use high placement, clear line-of-sight, and low-loss coaxial cables (e.g., LMR-400). Select appropriate antenna gain (e.g., 6 dBi for urban areas). Consider multiple gateways for redundancy. OpenThread: Identify interference sources (e.g., Wi-Fi, Bluetooth in the 2.4 GHz band). Ensure strong signal strength for reliable mesh networking. RS-485 Cabling (BACnet MSTP, Modbus RTU) Cable Type: Use shielded twisted-pair cables (e.g., Belden 3105A). Termination: Install 120-ohm resistors at both ends of the bus. Topology: Use a daisy-chain layout. Avoid star or stub configurations. Length Limits: Follow RS-485 specs (typically up to 1200 meters). Grounding: Maintain a common ground to prevent loops. Polarity: Verify A (+) and B (-) connections. Device Compatibility & Data Mapping Object/Register Mapping: Map BACnet objects, Modbus registers, and SNMP MIBs to internal gateway points. Document data types, scaling factors, and offsets. Device IDs & MAC Addresses: Assign unique IDs for Modbus (1–255) and BACnet MS/TP (1–127). Document all assignments. Adjust network priority if BACnet uses Ethernet and Wi-Fi is used for internet. Baud Rates & Serial Settings: Match baud rate, data bits, stop bits, and parity across all serial devices. Disable unused interfaces to reduce noise and resource usage. Conclusion By following these best practices, you can ensure a successful and reliable Flex server/gateway installation, enabling seamless communication across diverse automation protocols.

  Issue It is not clear if an INET SubLAN device, such as an MCU, is counted as a connected device for licensing purposes. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation version 7.0 onwards Cause With the re-introduction of INET in EBO 7.0, it is unclear how INET SubLAN devices contribute to the connected device license count.  Resolution INET SubLAN devices below a host INET device increase the connected device count. As a result, a connected device license is required for each SubLAN device. Ensure that your system has sufficient connected device licenses to accommodate all INET SubLAN devices added under host INET controllers.

Issue The LCES firmware for MP is universal, covers all models. The LCES firmware learns its model from the STM32 (the IO processor). If the LCES FW is unable to get an answer to the question, "what model am I", it defaults to MPC15A. When we see this, the reason is usually due to missing/corrupt STM32 firmware caused by a power fail during an uprev of the STM32 Product Line EcoStruxure Building Operation Environment Multi-purpose Controller Multi-purpose VAV Multi-purpose IO 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 STM32 flash corruption is caused by interruptions during firmware activation, such as: Power cycling the controller before activation completes. Network disruptions during upgrade. Premature assumption that upgrade is complete based on “100%” progress bar. Resolution To recover, try the following: Manually factory reset the MP controller (Press and hold the reset button between 20-29 seconds) Upgrade the MP controller to a revision close but NOT the same as the current firmware version. When the firmware upgrade is complete, reset the controller or power cycle the MP controller. Collect the device report again and check if the model has been updated to the correct one. If the model is correct, upgrade to the original or desired firmware version. If the model is incorrect, attempt another upgrade with a different version , aside from the initial firmware, from Step #2. You may need to repeat the firmware upgrade two more times if unsuccessful. 

Issue The Otis Destination Dispatch integration with Access Expert is not enforcing badge requirements for access to restricted floors. Users can select any elevator key without presenting a badge. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Mercury EP/LP4502 controller Otis Destination Dispatch elevator Compass System Cause The issue stems from missing routing table entries in the Mercury EP/LP4502 controller. These entries are essential for enabling communication between the Otis system and the Access Expert controller, which is required to enforce badge-based access restrictions. Resolution To resolve the badge enforcement issue: Verify Routing Table Entries on the LP/EP4502 controller’s web interface. Ensure the following entries are present: 192.168.50.0 – Enables communication with the Otis Compass Server. 192.168.1.0 – Enables communication with the Otis Destination Entry Computer. Important: If either entry is missing, the systems will not communicate properly, and badge enforcement will fail. Refer to the Hardware Setup section in the integration guide for detailed instructions: Access Expert Otis Elevator Integration Guide   Detailed instructions for installing the Otis Destination Dispatch Access Expert Integration can be found in the Access Expert Otis Elevator Integration with Destination Dispatch Knowledge Base article.

Issue During or immediately after a firmware upgrade, the RP-C controller may experience corruption of the STM32 processor's flash memory. This results in the controller misreporting its model type and becoming non-functional. Affected RP-C controllers may exhibit the following: Incorrect controller model appears during BACnet discovery or in the device report. Controller defaults to RP-C-16A-F-230V when STM32 is unresponsive. No communication between STM32 and main processor (LCES). Controller reset button has no effect (no LED blink sequence). Even if the actual model is RP-C-16A-F-230V, it will not operate correctly if STM32 is corrupted. Lack of response to the reset button is a key indicator of STM32 corruption. Product Line EcoStruxure Building Operation Environment  Room Controller (RPC) 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 STM32 flash corruption is caused by interruptions during firmware activation, such as: Power cycling the controller before activation completes. Network disruptions during upgrade. Premature assumption that upgrade is complete based on “100%” progress bar. Resolution To prevent the issue, perform the following: Do not disturb controller operation during firmware activation. Ensure the following indicators are met before removing power: Firmware revision is updated in the “Firmware revision” column. “Upgrade status” shows Operational. Controller is Online (not just showing 100% progress). If STM32 corruption has occurred, follow these steps to restore the RP-C controller: Ensure prerequisites for your laptop: Enterprise Server with Demo License running 5.0.2.109 or higher EBO Workstation compatible with Enterprise Server version instructions are for DHCP network that laptop and controller are connected. Adapt for direct connection using Auto IP, if needed. Multiple SpaceLogic firmwares, as needed to use one different from the version the controller is currently running Launch EBO Workstation and log into Enterprise Server. Connect RPC to network via Ethernet. Apply 24VAC power to RPC. Open Device Discovery and initiate BACnet discovery using Discover All button. If RPC is not discovered, cycle power and retry discovery. Once discovered (likely as RP-C-16A-F-230V), host it to the ES IP network. Ensure ES has a different firmware version than the one currently on RPC. Go to Firmware Upgrade screen: Select a different firmware version. Choose Activate Immediately. Click OK to start upgrade. Wait for the status to change: “Download firmware in progress” → “Activate firmware scheduled” → “Activate firmware in progress”. RPC will go offline in 1–3 minutes. Wait 1 minute, then power cycle RPC (off for 5 seconds, then on). Wait another minute, then repeat power cycle. Within 10–30 seconds, Status LED flashes Red & Green (STM32 reprogramming is being performed). After ~1:15 minutes, LED flashes White & Green, then toggles Red & Blue (Bluetooth FW upgrade is being performed). There is an expected white and green flash of LED where the final LED state is Solid Green. Rediscover RPC in EBO. The controller should now report the correct model and be fully operational.

Issue Clarification needed on whether AC-1A door modules are supported in Security Expert. Product Line EcoStruxure Security Expert Environment SP-AC1 Controller Andover Continuum door modules: AC-1 AC-1 Plus AC-1A Cause The AC-1A door module is not explicitly listed in the Continuum Transition documentation, leading to uncertainty about its compatibility. Resolution Although the AC-1A door module is not specifically mentioned in the documentation, it is supported by the Continuum Transition Tool. This means it can be used with Security Expert when transitioning from a Continuum system.   For detailed transition steps, refer to the Continuum Transition documentation available on the Schneider Electric Exchange portal.

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 Need to perform a diagnostic verification as a preventative measure during routine maintenance or reactively in response to cabling that is causing RSTP issues. Product Line EcoStruxure Building Operation Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller (RPC) IP-IO Cause Issues can be caused by cabling or cabling terminations between controllers in the RSTP Loop. Resolution Reference RSTP Troubleshooting for BACnet/IP Controllers - Schneider Electric Community to ensure that: the managed switch is appropriately configured for RSTP all SpaceLogic controllers, on the RSTP loop, report RSTP Status = Operational Leave one side connected to the managed switch Plug the other end into a laptop running Wireshark Evaluate based on the information below Ensure both ends are not plugged into the managed switch at the same time by: Unplug the end from the managed switch Unplug the end from the laptop and plug it into the manage switch Take the free end and plug it into the laptop Evaluate based on the information below If it fails either evaluation, check the cables based on Message Age using a cable tester. It is optional but highly recommended to use a cable tester that displays cable length, as they tend to be more accurate, pointing out failures that other testers may report as passing. If it passes the evaluation on both ends, then one can plug in both ends into the managed switch Evaluation This capture shows a topology change (TC + Root) in RSTP, then settles out to a consistent Root Bridge Priority and Message Age. Your capture should only show a topology change when Wireshark is capturing on one end and the other end is connecting/disconnecting from the managed switch. Review the following fields: Root Bridge Priority - should be consistent and show the Priority of the Root Bridge. The root bridge can be the switch to which the RSTP loop is connected or a managed switch upstream. If it shows 32768, then another SpaceLogic controller assumed the root because it is not communicating properly back to the root bridge. (See Message Age Note) Message Age - should be consistent and show the expected number of controllers away from the root bridge. When Root Bridge Priority is 32768, you can use Message Age to determine how many controllers away the issue is occurring, checking the cabling connected to or close to that controller.

Issue The IP address of a standalone Automation Server cannot be identified, and the Session ID required for password reset cannot be retrieved. Product Line EcoStruxure Building Operation Environment Automation Server Cause Due to the lack of available information regarding a 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 to obtain the IP address.  Consequently, obtaining the session ID is not feasible under these circumstances. Resolution Please note this article’s resolution requires a USB to Ethernet adapter.  If one is not available, please consult Identify Automation Server IP address to retrieve the password reset Session ID for an alternative solution to obtain the session id when the IP address is unknown.   The AS-P and AS-B Server Communication Ports include a USB host port, commonly used to connect the AD v3 or a Wireless Adapter.  However, this port can also be used to obtain a known IP address (10.110.220.1).   Prerequisites: USB to Ethernet Adaptor and network cable Physical access to the server to connect the adaptor Procedure: Connect the adaptor: Connect the adaptor to the host port on the AS-P/AS-B. Network Connection: Use a network cable to connect the PC’s network port to the adapter’s network port. IP Address Range: Configure the PC’s network adapter with the IP settings 10.110.220.2 / 8. Confirm Connection: Use a Command Prompt and Ping to test connectivity to the IP address 10.110.220.1.   Copy Session ID: After placing the EcoStruxure BMS Server into Password Reset Mode, use Workstation and the IP address 10.110.220.1 to access and Copy the Session ID.    

Issue After updating the firmware on an SP-C-WEB controller via the web interface, the login page may fail to display the username and password fields, preventing access to the controller.   Login page Product Line EcoStruxure Security Expert Environment SP-C-WEB Controller 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. 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 occurs when the login page web files are not properly updated during the firmware upgrade. Specifically, upgrading SP-C-WEB controllers from pre-cybersecurity firmware versions (4.00.1505 or earlier) directly to version 4.00.2402 or later can result in missing login fields. Resolution   Recommended Upgrade Path To avoid this issue, use a staged upgrade approach: Upgrade from 4.00.1505 or earlier to 4.00.2073 Then upgrade from 4.00.2073 to 4.00.2402 or later This ensures all necessary web files are correctly updated.   If the Issue Has Already Occurred If you've already upgraded to 4.00.2402 or later and cannot access the login page: A workaround is available. Please raise a Product Support case. Support will assist you via a remote session to restore access.   Future Firmware Update A future firmware release will address this issue directly, eliminating the need for a staged upgrade.

Issue Will client licenses from previous EBO versions activated prior to EBO 7.0 in License Administrator still be applicable after upgrading? Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause With the release of EBO 7.0, Schneider Electric introduced tier-based licensing. This change affects how previously purchased client licenses are recognized. Customers upgrading to EBO 7.0 and selecting the Essential Tier (which includes 3 concurrent client licenses) may be unsure how their existing licenses are counted. Examples of License Questions SXWSWCLIENT0999 in License Administrator, selected Essential Tier → Do they have 3 or unlimited client seats? SXWSWCLIENT0001 in License Administrator, selected Essential Tier → Do they have 3 or 4 client seats? SXWSWWORK00002 in License Administrator, no editor programs running, selected Essential Tier → Do they have 3 or 4 client seats? Resolution When upgrading to EBO 7.0, it's important to understand how client licenses are handled. Unlike previous versions, EBO 7.0 does not recognize client licenses purchased in earlier releases. Instead, license availability is determined by the selected tier during the upgrade. Client licenses from previous EBO versions are not automatically recognized in EBO 7.0. License availability is determined solely by the selected tier during the upgrade. The Essential Tier provides 3 concurrent client licenses. If unlimited concurrent client access is required, customers must upgrade to the Advanced or Advanced Plus Tier. The Workstation Pro license is separate and does not add to the 3 concurrent client licenses included in the Essential Tier.   🔹 Recommendation: Choose a tier that aligns with your concurrent client needs and any additional feature requirements.

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 When opening a Function Block application in WorkStation, adjusting the zoom level does not retain the setting the next time the Function Block is opened. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation v6.0.4 and earlier Building Operation Builder for Function Block Cause There is currently no setting in versions 6.0.4 and earlier that allows the zoom level to be retained in the Builder for Function Block editor. Resolution Starting with Building Operation 7.0.2, a new feature has been introduced that allows the default zoom level to be retained when reopening Function Block Program.

Issue When the Flex Server/Gateway is unable to connect to the internet, it's important to verify the network priority settings to understand how the device attempts to connect to the cloud. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal 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. 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 The Flex Server/Gateway is not designed for direct exposure to public networks. Improper network priority settings may cause the device to go offline when connected to the internet. Resolution The Flex Server/Gateway supports multiple internet connectivity options: Cellular (GSM): Supports two SIM cards for redundancy. Ethernet Wi-Fi (via Wi-Fi receiver) USB Tethering (via the top USB port, usb0, for troubleshooting) Learn more about USB tethering: USB Tethering for Flex Server   Connectivity Priority (Default Order) USB Tethering (usb0) Cellular (GSM) Ethernet Wi-Fi Note: If GSM fails and Ethernet is connected, the server will automatically switch to Ethernet. If both GSM and Ethernet are unavailable, it will switch to Wi-Fi (if configured). SIM Card Failover If one SIM card loses internet connectivity, the server automatically switches to the second SIM after a few minutes.   Best Practices Install the server in a secure location to prevent tampering (e.g., unplugging Ethernet or removing LTE antenna). Avoid direct exposure to public internet to maintain security and stability.

Issue The Vendor daemon fails to start on the License Server. Product Line EcoStruxure Building Operation Environment Ecostruxure Building Operation License Server 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 The issue occurs due to special characters (e.g., ô, ã, non-breaking space) in the Computer Name of the operating system hosting the License Server. - see screen shot below. This can be observed in the FlexNet Publisher management page (localhost:8888). The taclic.log file may contain entries such as: 10:11:55 (taclic) Server started on Test-aã for: B 10:11:55 (taclic) client.station client.station graphdb.base 10:11:55 (taclic) server.cloud.customer server.enterprise.base server.es.as 10:12:08 (taclic) EXTERNAL FILTERS are OFF 10:12:11 (taclic) Unknown Hostname: Test-aã​ Resolution To resolve the issue: Edit the Computer Name of the host machine. Remove any special characters (e.g., accented letters, non-breaking spaces). Restart the License Server after making the changes.