Issue Unable to read the Analog Inputs / Universal Inputs values in StruxureWare Building Operation. Product Line EcoStruxure Building Operation Environment Xenta I/O Modules Xenta  421A, 422A, 451A, 452A as standalone LON nodes StruxureWare Building Operation (SmartStruxure) Cause When using the Xenta Input Output modules 421A, 422A, 451A, 452A as stand alone Lonworks node, the UCPTConfiguration must be set to the necessary integer value for the required input, by default the values are set to zero so can not be configured. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network Expand the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the nciInput(x) variable within that module Set the value of Absolute count to one of the following : 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication   Up to SBO Version 1.7.x     SBO Version 1.8.x and on in the "Variable Fields" tab overwrite the string "Min" with for example 6 

Issue Unable to upload the same Lua script to multiple Room Controllers at the same time Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Automation Server Premium SSL SE8000 (all) Cause The alternative method of uploading the script to each of the room controllers using a USB cable Resolution To upload a script to multiple Room Controllers, follow the below steps: (This procedure assumes the BACnet MSTP network is already setup) 1 - Log in to Building Operation Workstation 2 - Right-click on MSTP network and click "Search" 3 - Search for "Lua program 1" or any other Lua program object 4 - Highlight all the Room Controllers that the script will be transferred to then click on the "show/hide property grid" button. 5 - Expand the "Basic" tab and copy the Lua script in the "Description" field then click Save. 6 - The script will be uploaded to each of the Room Controllers one at a time and will be played automatically. Recommendations & Limitations: - Each Lua Program can take up to 460 bytes of text (per script). (Total of 10 Lua programs) - Script must be placed on a single line. Use semicolons ( ; ) as carriage return - Use multiple Lua programs if the 460 bytes limit is exceeded - Encapsulate logic inside the following if statement if the logic is intended to run once: if not init then    ---Script logic here    init = true end For general information about Lua programming for SE8000 Room Controllers, refer to the following guide: Custom Programming Guide for SE8000 Series Room Controllers - Application Guide

Issue There is potential for confusion around the backward compatibility offered in EcoStruxure when the version of Enterprise Server differs from that of Automation Servers in the same system Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation SmartX Servers Cause The 3.1.1 Release Notes refer to a new 'Multi-version system' with the possibility of a v3.1 Enterprise Server but with v3.0 Automation Servers able to function long term within the same system (albeit with some engineering limitations).    This implies that AS running earlier versions than v3.0 cannot coexist, attempts to add AS running v2.0 to ES running v3.0 have produced errors. However........ The System Upgrade Reference Guide refers to 'Runtime Compatibility' with Version 3.1 that states that Automation Servers running v1.8, 1.9, 2.0 and 3.0 can all coexist with an ES running 3.1 without issue Resolution Both documents are true, but there are two possible situations that need to be considered: Situation 1) A site has a v1.9 or v2.0 system which is required to be upgraded to v3.1. When upgrading, the ES is usually the first device to be upgraded, then depending on the number of AS onsite it may take a period of time to upgrade all the AS (especially if some of these servers are used in hospital theaters etc). For this reason EBO has an Upgrade Runtime Compatibility from v3.1 back to to v1.8, 1.9, 2.0 and 3.0, which means that an AS already in the system when the ES is upgraded to 3.1 will maintain connectivity and functionality while the upgrade takes place. Situation 2) A site has an external v1.9 or v2.0 AS whichis required to be added to an ES which is already running at v3.1. When trying to add in a new controller to a v3.1 ES, an error is produced stating that the version of the AS being added needs to be updated to before it can be added. Error Message when adding v2.0 AS to v3.0 ES Error message when adding 2.0 AS to 3.1 ES (better explanation) To summarize EBO does have Runtime Compatibility from v3.1 back to 1.8 as stated, but only for AS already in the system at the time of upgrade. Once upgraded to v3.1 the multi-version environment can be used to operate AS at v3.0 but adding AS running versions before 3.0 will generate a descriptive error.

Issue What BACnet services and BACnet object types are supported in the AS and ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Automation Server StruxureWare Building Operation Enterprise Server BACnet IP BACnet MSTP Cause PIC statement for supported services and object types in StruxureWare Building Operation. Resolution Page 5 of the AS BACnet PIC shows the columns of the different types of BACnet devices. Whether it is a B-OWS or a B-BC etc… the x's in the columns show the required services for each particular device according to the BACnet Standard. The last green column in the PIC, show the Product Conformance (AS) and what services the AS supports. For instance COV is not a required service, but a optional one and is selected in the last column. Below are links to the AS and ES BACnet PIC. AS PIC statement link ES PIC statement link

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

Issue Can B-Link repeaters be used with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site release 1.xxx and higher Cause Need to add repeater(s) for EcoStruxure Building Operation Resolution For communication using RS-485, the versions of B-Link BACnet MS/TP Repeaters repeaters shown below were tested and passed for EcoStruxure Building Operation use. Part Number Description B-LINK-AC BACnet MS/TP Repeater, 120/240VAC B-LINK-AC-OP BACnet MS/TP Repeater, 120/240VAC, open class no enclosure B-LINK-AC-S B-LINK, AC, SMK B-LINK-DC BACnet MS/TP Repeater, 24VDC B-LINK-DC-OP BACnet MS/TP Repeater, 24VDC, open class no enclosure B-LINK-DC-S B-LINK, DC, SMK B-LINK-F-AC B-LINK, AC, FIBER B-LINK-F-AC-S B-LINK, AC, FIBER, SMK B-LINK-F-DC B-LINK, DC, FIBER B-LINK-F-DC-S B-LINK, DC, FIBER, SMK   Note the supported cable diameter in microns: 62.5/125. The first number, 62.5, refers to the diameter of the fiber cable's core. The second number, 125, refers to the diameter of the outside of the fiber cable's cladding. For more information see: BACnet b-Link MS-TP Repeaters - Andover Continuum - Specification Sheet b-Link Series - Andover Continuum - Installation Sheet Additional information about Fiber diameters from The Fiber Optic Association Fiber cabling information for an Infilink i2210 and the B-link-F Series

Issue Experiencing issues with I/O modules that may include: Backplane failure causing modules to assume wrong module ID Input filtering problems on RTD modules Stability due to electrical noise Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation StruxureWare Building Operation Automation Server I/O Modules Cause The latest I/O module firmware version will correct known issues while also ensuring that the system is up to date and compliant. Resolution The latest I/O module firmware can be located on the Exchange by searching for I/O Module firmware. Each firmware download zip file will contain a ReadMe file that explains what was corrected in that version.  Refer to Upgrading SmartStruxure IO Module Firmware for the procedure to upgrade the I/O module firmware. 

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com  

Issue Advanced Display Version 2.0 Tablets are loosing connectivity to their associated AS-P (connected via USB) when the AS-P is power cycled or the USB is briefly disconnected, even after the connection/power has been restored. Product Line EcoStruxure Building Operation Environment Advanced Display V2 Cause There are a number of internet browsers available to the user of an AD V2 once the SmartX Kiosk App has been entered. Chrome has been included in the standard view of the Kiosk for some time. and using the 'show/hide system apps' button within the Kiosk the other apps can be accessed on the tablet such as Samsung's own Samsung Internet App (as long as as the Kiosk pin is used). However since the release of Kiosk 8.1 only the Webstation App, which is built into the Kiosk is supported for connection to the AS-P and to use Kiosk 8.1 or greater the Android 8.0 build firmware of the AD V2 must also be brought up to T580XXU4CSA1 as a minimum.  (as detailed by TPA-EBO-19-0002.00) Using the Chrome or Samsung internet apps or having an older build of Android 8 OS firmware may appear to work fine on first impressions, but connectivity issues may then arise such as those detailed above Resolution As long as AD V2 build is T580XXU4CSA1 or greater and the inbuilt Webstation App is being used for all AS-P connection, then users should not encounter any connectivity dropout at all and any new issues which arise can be raised with Product Support Services.

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue When adding an Enterprise Server (ES)S to an Enterprise Central (EC) the following error is seen: "Cannot add a server to the system with an already existing unique ID". The option to restore an Enterprise Server (ES) backup with new GUIDs is greyed out and not available. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The error indicates that the ES has been cloned and has the same Globally Unique Identifier (GUID) as another ES in the system. The GUID is a unique identifier tied to the server's configuration and database structure. Changing the GUID of an Enterprise Server by restoring from a backup with new IDs is not supported due to system integrity and object referencing constraints within EBO.  Resolution Restoring an Enterprise Server with new IDs (GUIDs) is not possible or supported. The recommended approach is: Set up a new Enterprise Server instance. Use the Export/Import feature to transfer supported objects from the template ES. Manually configure any settings or objects that cannot be exported.  

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 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 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 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 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 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