Building Automation Knowledge Base

Issue Blinking red lights Solid red lights Blinking orange light Blinking green light Solid green light Environment Xenta Server Controllers 511, 527, 555, 701, 711, 721, 731, 911, 913 Cause The indicator lights on the face of the Xenta Server controllers can help explain the state of the controller in many different situations. Resolution A number of light-emitting diodes (LEDs) on the Xenta device indicate that the application program is running and when communication is in progress.    Fig. 1: LED diagram on the Xenta Server device.   Table1: LED description on the Xenta Server device.     Position Description 1 Neuron status indicator • Off – Normal mode • Red, blinking – Unconfigured mode • Red, steady – Hardware fault 2 Serial RS-232 B port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 3 Overall Run indicator • Green, steady – Normal mode • Green, blinking – Start mode • Red, steady – Fail-safe mode (see    description below) • Red, blinking – Unit fault 4 Serial RS-232 A port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 5 Serial RS-485 C port activity indicator. 6 Ethernet 10Base-T activity indicator Note • The LEDs for the RS-232 A interface (position 4) do not indicate communication when using the RS-485 A interface although internal port A is used for both.               Fig. 2: Internal serial ports and RS-232/485 interfaces.

Issue License needs to be activated or repaired but there is no Internet access on the computer that the license is being hosted on. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator  Cause There is an inability to move the computer to a location with Internet access, activate or repair the license, then move it  back to the site. In other situations the IT Department is so strict that they will not allow internet access on the computer just for licensing activation. Resolution SBO Offline Activation Tool There SBO Offline Activation tool posted on the Community outlines the step by step process to perform an offline license activation. It can be accessed here: SBO Offline Activation Tool. Click on "Instruction and Help" in the tool for the step by step process and other helpful videos/charts.  SBO Offline License Repair The same SBO Offline Activation tool used for activation can also be used to repair an offline license. Download the tool here: SBO Offline Activation Tool. After launching the offline tool, click on the "Special Operations" menu and click on Repair License.  If this does not repair the license, then please contact PSS for further troubleshooting assistance. 

Issue Unable to log into Workstation because the user password is unknown. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P, or AS-B) Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Project Configuration Tool (PCT) Cause The password for an Automation server or Enterprise server/Central has been forgotten. Resolution IMPORTANT: The session ID is unique for this session of WorkStation. You cannot close WorkStation until the password has been reset. If you close WorkStation, before the password has been reset, a new session ID is generated that cannot be used with the temporary password provided by your local Schneider Electric Buildings support team.       The following are the steps to populate the session ID, which is required for doing the password reset.   For servers with EBO older than V3.1.X In the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon.   This will populate the Session ID. Copy the Session ID.   For servers with EBO V3.1.X:   In Device Administrator, select the server you need to perform the reset to. Check the box and click the hyperlink   From the top bar select Password Reset Select OK when you get the “Password reset token created” pop-up Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.    For servers with EBO V3.2.X and higher In Device Administrator, select the server you need to perform the reset to From the top bar, select the “Edit Connection Password/Reset password” and press OK Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.   NOTE (for servers with EBO V3.1.X and higher)  For the Automation Server password reset, ensure that the Automation Server is connected to your PC machine via a USB cable. For the Enterprise server and Enterprise Central password reset, add the server to the Device Administrator using the “Add Server” button on the top bar. Please note even if you enter the wrong password, the Server would still be added to the Device Administrator.     After having the Session ID:   Send the Session ID to your local Schneider Electric Buildings support team Once PSS provides you with the unlock key In WorkStation, ensure that the Session ID is still visible, enter: User Name: admin Password: paste the result from the webpage Domain: Local and click Log On This will pop-up the Change-Password form Fill in the “old password” field with the unlock Key Put in a new password you want to use and then enter the new password in again. Click OK   NOTE:  When attempting to reset the password and unlock with the sessionid/temp password, you receive the error: "Your account has insufficient permission to use the system. Contact your administrator. "  Open a case with your local Product Support group and submit a request to unlock the user.   NOTE: WebHelp article 6749   The following video shows the password reset procedure for EBO older than V3.1.X. It covers most of the important steps for newer versions. Quick-Help video    

Issue Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see the below video demonstrating how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. Also please note the following: In the video the "Host address" in EBO is set to the IP address or DNS name\SQLserver instance like this: localhost\SQLEXPRESS. If the SQL server is not located on the same computer as the EBO server only use the IP address or DNS name and no instance on "Host address". The video demonstrates using the version 5 script when configuring the database in the MSSQL server, search External Log Storage - MSSQL Installation Script  to download the appropriate EBO version script. For the example query to manage user permissions download User Rights Script or see attached script.txt. If using MSSQL Express rather than the full MSSQL version it may be necessary to consult External log storage not working with SQL Server Express.    

Issue When attempting to log into a server, the error message "Failed to establish connection with server" appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Servers Cause WorkStation is unable to make a connection to the desired server for one of several reasons. Resolution Unable to log into the Enterprise Server Verify that the Enterprise Server is running Go to Start Software Administrator Verify that the Server Status is Running. If it is stopped, then click the Start Service button, and click OK. Log into the server through Workstation. Lockout after restoring a backup set If an enterprise server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Unable to log into the Automation Server Verify the Ethernet connection Go to Run > cmd. Ping the IP address of the automation server. If it fails to communicate to the controller, verify that the ethernet connections are good and that there are no IT issues. Lockout after restoring a backup set If an automation server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Verify the IP address Go to Device Administrator  Connect to the Automation Server with a USB cable. Select the automation server once it is visible in the Device Administrator window and click on its name. Note: If the device indicates "Password Required," - Login into the automation server (default login is admin, and password is admin). Once the details open - Select the Ethernet 1 Configuration option and verify or enter the IP address details. After applying the information, enter this IP Address in WorkStation "Server" option to log on.  For further troubleshooting help see the following online help topic: Failed to Establish Connection

Issue There is no quick and efficient way to configure a TAC Xenta 102-AX controller after adding it to a LonWorks Network in Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC Xenta 102-AX controller is typically configured using the LNS plug-in that is currently not available in version 1.4.0 and newer. Resolution As an alternative to the LNS plug-in, the graphic page available on the Community [1] can be used. This zip file contains the TGML graphic, binding template, and a full import file with a Xenta 102-AX that is already bound. [1] Xenta 102-AX SXW TGML Plugin v1.6.1 (SBO 1.8.0 to 1.9.3) Example Plug-in TGML Graphic Page

Issue Enterprise Server will not start due to no valid license file error: "nsp.csc.licensemanager No valid Enterprise Server license found. Terminating server." or Cannot find license file. (Error code: -1) Product Line EcoStruxure Building Operation Environment Building Operation Software Administrator Building Operation License Administrator Building Operation Workstation Cause Enterprise Server is not started and states no valid license file is found. License Server is installed on the same computer and has valid license(s). Similarly, WorkStation may not start even with a License Server installed with a valid license. If you get error -1, it means that you didn't enter the required @ before the license server address. Resolution In general, any licensed Building Operation software (Enterprise Server, WorkStation, Editors) needs to know where the license server is located. That means that the license server path needs to be entered on any PC having licensed Building Operation software installed. The "License Administrator" part of the license installer can be installed on any PC, and the license server address set using the administrator. The license server itself does not need to be installed on all PC's, but only on the PC hosting e.g. the Enterprise Server. The IP or DNS name of the PC hosting the license server is entered with an initial @, e.g. if the IP of the license server PC is 1.2.3.4 you enter @1.2.3.4 Checkpoints Remember to enter the license server address starting with a @. For example, don't use "localhost" but "@localhost". Is your evaluation license current? If not, download from EcoXpert Extranet Check that antivirus software is configured to allow the operation of the license server. (refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96)) Reboot the machine where the License Server is running. It has been observed in some cases where the error 'No valid license or Cannot find license file error' appeared after an upgrade that rebooting the machine solves the problem. Check to see if there are multiple versions of the License Server installed on the machine. If multiple versions are installed, make sure to only run the highest installed version as a Windows Service. All other License Server and License Administrator software should be uninstalled from the machine.

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue How to remove an unknown Embedded Demo License Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Device Administrator v4.0.5 (EBO 2022) and below Cause The Embedded Demo Licenses are handled from the Device Administrator software. However, if the installed Embedded Demo License in the SpaceLogic servers does not comply with the file in the Device Administrator, the installed Demo License could not be removed. Resolution Instructions shown in the video below are for EBO 2022 (v4.0.5) and below. In the later releases EBO 2023 (v5.x) and above, a feature now allows the Demo licenses to be returned from selected servers.  See WebHelp topic Returning All Demo Licenses from the Selected SpaceLogic Automation Servers  For any License activations/returns to occur, there must be a trusted state (Certificate State) between the server and Device Administrator. Ensure that this is in place before attempting either resolution. For more info, see Certificates Managed using Device Administrator   If this function does not work, you can attempt the manual file name manipulation described below.    To check the name of the installed Embedded Demo License, log in to the SpaceLogic servers from Workstation. Navigate to System, LicenseManager, LicensingMetadata, ClientMetadata, Product 0. In ProductID, you will see the filename of the actual file.   Rename a Demo license file and import it into Device Manager to uncheck the selected Demo License file.   At the end of this session, you will be able to: Remove Unknown Demo License in SpaceLogic servers        

Issue How to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator is not connected to the internet. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause Device Administrator is used to manage licenses on SmartX servers The following features of a SmartX server need licenses: SmartDrivers SNMP Notifications Personal Dashboards TimescaleDB MQTT Resolution Building Operation 2022 Note: The offline entry of the Activation-ID License items is not all visible - ONLY the first 5 are shown.  This makes entering this information impossible. This has been fixed in the Maintenance Release 4.0.2 of the Device Administrator.  After activating the embedded license offline and transferring this license to the servers, a license violation may be still shown.  The license status should update within 24 hours.  Perform a warm start and then a Refresh License Status on the selected servers to force this update.   If an error is seen in the progress status indicating ASEmbeddedAPI internal error during the offline activation, check the following Embedded license activation fails - Communities to correct the corrupted storage.   This video will show how to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator and/or the server is not connected to the internet. IMPORTANT NOTES: You need to be connected to the SpaceLogic (SmartX) Server using IP (select +Add server on Device Administrator).  It cannot be connected via USB. Ensure always to run the Device Administrator with admin privileges. Select "Run as administrator." Should Device Administrator be running on a computer that has internet access, then there is no need to swap between online/offline computers.  The offline activation process can be run from the same Device Administrator with no need to change computers.  The offline workflow is always the same and detailed on the webhelp topic Offline Activation of Licenses Workflow  The video below shows version 3 licenses. In Version 4, there are a few more license features and quantities required to enter.  The following article may assist in entering this information. License Features list for version 3.0 and 4.0 Product names     At the end of the video session, you will be able to: Create a request file using the Device Administrator on an offline (to the Internet) computer. Activate request files from the Device Administrator on a PC connected to the internet. Send response files to the SmartX Server from the offline Device Administrator.

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 Services for assistance. Issue Orphan alarm exists in the Enterprise Server database and acknowledgment of the alarm does not remove the alarm. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v. 2.0.3 or lower,  Cause Backup of the Building Operation database that includes historical data will include the alarm that needs to be purged. IP changes or other reasons can contribute to alarms being orphaned. Resolution Note: Version 2.0.4 and from 3.0.2 and higher there is a built-in solution called Alarms Integrity Check which can be run to verify all alarms and purge any that are no longer in the system.     In order to completely purge an alarm database, it is necessary to delete the PersistedData.dat file that stores this information in the database. Perform an ES and AS full backups Using Building Operation Software Administrator click the "Stop Service" button for the Enterprise Server. Image from Windows XP Image from Windows 7 / 10 Browse to the database path listed in the Building Operation Software Administrator tool. Windows 7/10: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 2.x\Enterprise Server\db Windows XP:  C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db Browse to the Persistent subdirectory Move/Delete the PersistedData.dat  file Click the "Start Service" button in the Building Operation Software Administrator tool. When the Enterprise Server restarts and you log in the orphaned events will be removed and any currently present alarms will return to the Alarm window with their proper status and assignment. This process causes a re-evaluation of alarms on the ES and fetches all the alarms from each AS. This can take a few minutes and may cause some slowness in the system. Note 1: Historical perspective of previous alarms, operator actions, or other data recorded in the Event Log will be lost in this process.  

Issue How do you define the number of decimal places displayed for a point? Is it possible to change the number of decimals displayed in WorkStation / WebStation? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation  Cause The operating system's regional settings determine the default resolution for decimal places displayed. This value cannot be modified within WorkStation; however, the regional settings in WebStation can be adjusted to show the desired number of decimal places. Resolution This setting applies to all displayed values except graphics, where the graphic editor can define the number of digits displayed.   WorkStation Open Control Panel Select under Clock and Region - Change date, time, or number formats As shown in the screenshot below, select Additional Settings [1]  Then adjust the Customize Format "No. of digits after decimal to your requirements" [2]. Restart WorkStation if already opened. WebStation  From the User Account drop down Select Settings Select Regional Change the Decimals from Auto to the desired number (0-6) required in WebStation.  Click Save Log off/on to WebStation to see these changes.   

Issue How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue When upgrading Building Operation do new licenses need to be purchased? Product Line EcoStruxure Building Operation Environment Building Operation (All Versions) Cause Is there a requirement to upgrade (purchase new) licenses when performing software upgrades to Building Operation to make use of the new features available. Resolution Building Operation software version numbering consists of 3 fields the first of these denotes the major release version. For example: 1.9.4 - Release 1 2.0.1 - Release 2 3.0.1 - Release 3 3.2.4 - Release 3 4.0.4 - Release 4 (EBO 2022) 5.0.3 - Release 5 (EBO 2023) 6.0.2 - Release 6 (EBO 2024) An upgraded license will be required when moving between major versions of Building Operation. For example: An upgrade license needs to be purchased when a 1.9.4 system is upgraded to 2.04. An upgrade license is not required to upgrade a 3.0.1 system to 3.2.4 There is currently one exception to this rule, licenses previously purchased for EBO 2022(4.0) can also run a EBO 2023(5.0) system.   From EBO 2.0 onward a scalable licensing model has been adopted and the cost of upgrades are determined based on the declared size and capability needs of the system. For more information please refer to the Pricing Policy - EcoStruxure Building Operation and the Part Number and Hardware and Software Matrix - EcoStruxure Building Operation 2023

Issue The Automatic Logoff feature is available in version 1.4 and higher. Starting in version 1.5, there is a default automatic logoff time of 10 minutes in both Workstation and WebStation for the Administrators user group. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation WebStation Cause To prevent unauthorized users access to the system the automatic logoff feature has been added to SBO/EBO. The default Administrators group is set to automatically log off of both Workstation and Webstation after 10 minutes of being idle. This setting cannot be changed for the Administrators group. Resolution The automatic logoff function makes it possible to decide when a user is automatically logged off after a specified time of inactivity. Inactivity means that no user initiated activity is ongoing, that is, no action has been made using the mouse or the keyboard. However, if a user has initiated a big operation in Workstation, for example an import or a large copy and paste, the user is still considered to be active as long as the process is ongoing in Workstation. This is to prevent loss of data. The automatic logoff function is used for security reasons and it also prevents that a Workstation user occupies a license when inactive. The automatic logoff time is set at User Group level and is always defined by the group that has the longest automatic logoff time. For example, if a user belongs to two groups, one group has an automatic logoff time of 5 minutes and the other group has an automatic logoff time of 15 minutes, the user is automatically logged off after 15 minutes. If a user belongs to a group that does not have the automatic logoff function enabled the user will never be logged off. Note: When a user is logged off by the automatic logoff function all settings that are not saved are lost.   Creating a new user group so the Automatic logoff time can be adjusted Starting in version 1.5, in order to change the duration of time before the automatic logoff occurs or turn it off a new User Account Group must be created. Follow the steps below. Go to the Control Panel in Workstation. Click on Account management. Click Add under the User Account Groups section. Name the new User Account Group. Click Next. Select the Users to add to the new group and then click the right arrow to move them to the "Selected User Accounts" window. Click Next. In the same method as step 4, select the Workspace to add to the new group and move it over to the "Available Workspaces" window. Click Next Set the group policies for the new group taking note of the Automatic logoff time which can be set to "Never" if desired. Click Create.   Changing the Automatic logoff time of an existing user group In the System Tree under System > Domains > Local > Groups, select the user group and click on the "Policies" tab. Here the Automatic logoff time can be changed and then click the save button on the tab at the top of the window.

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue SLP Sensor Modbus RTU issue when used with RPC or AS Communication errors are seen during normal Values are updated very slowly, can take up to two minutes to populate/update the 15 objects within the SLP.   Product Line EcoStruxure Building Operation Environment Modbus RTU RPC Modbus Automation Server + Premium  SLP SpaceLogic Sensors LSA_APP_REV2.03.19 and REV2.05.21 Cause Once the Modbus communication is set up between RPC (or AS) and the SLP,  although the values updates fairly regularly, multiple communication errors are also seen The SLP read speed needs to regulated to prevent overwhelming it The SLP Modbus transmission voltage is less than the AS Resolution Use with RP-C SLP struggles to respond to every request from the RP-C, changing the baud rate to 9600/19200 and increasing the "Silence characters" in the interface to 255 (maximum possible) should stabilize the communications.  The character spacing cannot be adjusted enough in the RP-C to allow communication at 38400 or 76800 Use with AS/AS-P  Adjust the “Poll point delay” in the Modbus Interface to 80ms The Silence characters and Transmit guard bits may also need to be increased Baud rate up to 38400 has been tested.  

Issue Finding the rules governing the BACnet device Instance ID in EBO and learning to change it if required. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled  Cause The BACnet device Instance ID must be unique within a BACnet system. There may be a need to find out or change the device Instance ID to ensure there are not duplicates.  Resolution When a BACnet Interface is added to an SmartX server, AS or ES, the Server will become a BACnet device and it will have an Instance ID (automatically generated or manually assigned).  To check an ES or AS BACnet device instance ID go to the properties of the BACnet Interface and then the Advanced tab. The device instance ID is defined as the Object ID. To check other BACnet device, SmartX controller or 3rd party BACnet device, go to the properties of the BACnet Device and then the Advanced tab. The device instance ID once again is defined as the Object ID.  No 2 BACnet devices in any system may have the same Instance ID/Object ID. The valid range of Instance Numbers for a BACnet device is 0 to 4194302.   Change BACnet Device ID: You can change BACnet device IDs for SmartX Server or Controller when there is a conflict with another BACnet device, move controller or in those situations where you need to change the originally selected value for some local or site-specific reason. In EBO V3.2.3 or higher (except V3.3), it is possible to change BACnet Device ID of an SmartX server (ES, AS-P or AS-B), as explained in: Changing the BACnet Device ID in a SmartX Server To change SmartX IP Controller BACnet device ID, follow: Changing a BACnet/IP Device ID