Building Automation Knowledge Base

Issue Unable to connect Enterprise Server or Enterprise Central to the Building Advisor Cloud Portal  Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment Building Operation Building Advisor EBO Health Module Building Operation Enterprise Server Building Operation Enterprise Central Cause There are some Operating System Requirements that need to be checked and enforced. Resolution Incompatible versions lead to missing trust certificates that could hinder the connection to Azure cloud services.  The table below provides a compatibility matrix of EBO versions and supported Windows OS that is necessary for the cloud-connectivity to work reliably.   Enterprise Server Software Requirements               EBO Version v2.0 v2.1 v3.0 v3.1 v3.2 v3.3 v4.0 Microsoft Windows 7 (64-bit) Yes Yes Yes Yes No No No Microsoft Windows 8.1 (64-bit) Yes Yes Yes No No No No Microsoft Windows 10(64-bit) Yes Yes Yes Yes Yes Yes Yes Microsoft Windows Server 2008 R2 (64-bit) Yes Yes Yes No No No No Microsoft Windows Server 2012 (64-bit) Yes Yes Yes No No No No Microsoft Windows Server 2012 R2 (64-bit) Yes Yes Yes Yes Yes Yes Yes Microsoft Windows Server 2016 Yes Yes Yes Yes Yes Yes Yes Microsoft Windows Server 2019       Yes Yes Yes Yes Microsoft .NET Framework 4.5 or 4.6 Yes Yes           Microsoft .NET Framework 4.7.2 or later     Yes Yes Yes Yes Yes The SmartX servers also require TLS1.2 to be enabled to communicate with the BA cloud properly. Automation servers (AS-P/AS-B) have TLS1.2 enabled by default. Check that the Windows OS running Enterprise Server has TLS1.2 is enabled by following the steps in this link: How to Check if TLS1.2 is Enabled 

Issue The units of measurement or time zone on the Advanced Display differ from what is displayed in Workstation or Webstation.  Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display (AD v1 v2 v3) Building Operation Technician Tool Cause If the language settings on the Advanced Display are not set properly, then the units of measurement and time zone can be displayed incorrectly. For example, the temperatures in EcoStruxure Building Operation WorkStation or WebStation may be in degrees Fahrenheit while the Advanced Display shows the values in degrees Celsius.  Resolution Ensure that the Language used by the Advanced Display is set properly to the region it is located. Advanced Display V1&2 Note: The SBOTechTool supports English, French, Swedish, Finnish, German, and Spanish. On the Advanced Display, go to Settings. If you cannot open up settings, ensure the AD Link app is in the disconnected state first. Go to Controls > Voice and input methods > Language and input. Verify that the Language is set to match the region where the Advanced Display is located. Advanced Display V3 WebStation uses the language settings of the operating systems to detect the units that should be used and the time display format. To access the Advanced Display v3 language settings: Exit the Kiosk application and drag up up from the bottom of the screen Click Settings Click System Click languages and input Click Add a language Reorder (Press and hold, then drag the desired language to position 1) To access the Advanced Display v3 Date & Time settings: From System, click Date & Time Click Select time zone and select the correct local time zone

Issue The process of acquiring a license Entitlement ID and how to activate, release and/or transfer a license in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Enterprise Server Building Operation WorkStation Cause There are two different ways to activate a license and different types of licenses that can be purchased. Resolution This article discusses Building Operation Software licenses applied to software platforms such as EC, ES, and Workstation. For details on applying licenses on SmartX Server devices, refer to the Automation Server Licensing Workflow Webhelp topic and/or the Offline activation of embedded licenses Knowledge Base article.   Purchasing a License The licenses that can be purchased are listed in the Part Number Summary. After an order is placed, you will receive an email with an Entitlement ID certificate attached. For further details, see the Order Information Request Webhelp topic.   Evaluation Licenses Evaluation licenses are used for demonstration purposes, training, or site engineering. The evaluation license is a file that can be downloaded from the Exchange and is valid for up to 3 months. Refer to the Activating an EcoStruxure Building Operation Demo License webhelp topic for the activation process.   Activating an Entitlement ID Entitlements can be activated online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online Activation If the computer that the License Administrator is installed on has an internet connection, then refer to the Activating EcoStruxure Building Operation Software Licenses Webhelp topic for the activation process. Offline Activation If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. Once a license file or Entitlement ID has been activated, and the Status reads "Valid" in the License Administrator, the activation process has been completed. The license does not need to be re-hosted after an upgrade and will remain on the computer if the Building Operation Software is uninstalled and reinstalled. To check the status of the license server and licenses that have been activated on the local machine, the Flexnet License Administrator can be accessed by navigating to localhost:8888 in a web browser. The licensing system is the same as used in TAC Vista, which can be seen in License troubleshooting in Vista 5.1.8 or greater.   Returning an Entitlement ID License If the computer on which the License Administrator is being replaced, or it has major operating system changes. In that case, licenses may become invalid and should be returned before those changes. Entitlements can be returned online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online License Return If the computer that the License Administrator is installed on has an internet connection, then refer to the Returning an EcoStruxure Building Operation Software License Webhelp topic for the return process. Offline License return If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. Transferring an Entitlement ID License There is no separate process when transferring a license from one system to another.  Simply return the License from the current system as indicated above and then check that the available seat count has increased by one via the original Entitlement ID. Once returned, activate this same License on the new system as detailed earlier.   Note: Releasing and reactivating licenses can only be carried out a finite number of times per year (4 license returns each year) to prevent misuse of the licensing system.

Issue Basic Modbus RTU configuration to read a register from PM800 Power Meter. Product Line EcoStruxure Building Operation Environment Automation Server Modbus RTU PM800 Power Meter Cause Integrate power meters to a Building Operation front end for the user to view data and trend logs. Resolution Here are the steps to Configure a ModBus RTU interface in Building Operation to read the Line Voltage register from a PM800 Power Meter. (Assuming meter has already been properly wired to one of the serial ports on the AS) Create the Modbus Interface, in this case a Modbus Master Network.   Link the interface to a serial port in the AS in the Port Reference field, in this example to RTU device is wired to RS485-COMB   2. Under the interface create the RTU device. In this example the device id is 11, enter the appropriate id for the device. Once the device object is saved, the status should show 'Online' unless there is a communications issue. This is provided you have the online poll interval set. If this is disabled the device will stay offline until a Modbus register is polled and a valid response is received.    You can confirm that Building Operation is able to correctly detect the communications status of the device by disconnecting it from the commport and observing the status change to 'Offline', upon re-connection the status should once again display 'Online'   3. Under the device create a Modbus Point of type AnalogInput to get the value of the Line Voltage from the device. According to the documentation for the PM800 the register holding the line voltage is Function Code 3  and register  1124 The value of the point should now correspond to the line voltage in this case 125 volts.

Issue View forced values in a EcoStruxure Building Operation TGML graphic Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation TGML Graphic Cause There are no variables for forced value to trigger an object in a graphic. Resolution In the graphic editor do as follow. Add a text object Add a binding to the text object and name it Change attribute to content Add a convert status Under behavior add text you want to show when the value its forced Edit binding for the graphic, bind the created textobject to the value of the point The text object should now show the text forced when the value is forced.  

Issue What is Domain Name Service (DNS)? Product Line Andover Continuum,EcoStruxure Access Expert,EcoStruxure Building Expert,EcoStruxure Building Operation,EcoStruxure Security Expert,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment TCP/IP Networks Cause DNS is a distributed hierarchical system for resolving host names into IP address. Under DNS, there is no central database with all of the Internet host information. The information is distributed among thousands of name servers organized into a hierarchy similar to the UNIX file system. DNS has a root domain at the top of the domain hierarchy that is served by a group of name servers called the root servers. Source: TCP/IP Network Administration by Craig Hunt, O’Reilly & Associates, Inc. Resolution Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.  

Issue Trying to open TGML Graphics Editor and an error appears before the editor crashes.  Crash report shown below: Font 'Arial' does not support style 'Regular'. ArgumentException at System.Drawing.Font.CreateNativeFont() at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont) at System.Drawing.Font..ctor(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit) at SE.Graphics.Viewer.Windows.GDIPlus.RenderText..ctor(Double left, Double top, String textContent, Double fontSize, String fontFamily, Int32 fontStyle, Int32 fontWeight, Int32 horizontalAlign, Int32 verticalAlign, Int32 textDecoration) at SE.Graphics.Viewer.Windows.GDIPlus.DrawingFactory.createText(Double left, Double top, String textContent, Double fontSize, String fontFamily, Int32 fontStyle, Int32 fontWeight, Int32 horizontalAlign, Int32 verticalAlign, Int32 textDecoration) at SE.Graphics.DOM.TGML.TgmlText.getUncachedShape() at SE.Graphics.DOM.TGML.TgmlStrokeShape.getShape() at SE.Graphics.DOM.TGML.TgmlTextShape.getShape() at SE.Graphics.DOM.TGML.TgmlStrokeShape.getUncachedBoundingBox() at SE.Graphics.DOM.TGML.TgmlShape.getBoundingBox() at SE.Graphics.DOM.TGML.TgmlShape.HandleAfterBoundingBoxChanged() at SE.Graphics.DOM.TGML.TgmlShape.OnAfterBoundingBoxChanged() at SE.Graphics.DOM.TGML.TgmlShape.OnChildElementChanged(Node element, ChangeType changeType) at SE.Graphics.DOM.TgmlInheritedElement.FireChildElementChanged(Node element, ChangeType changeType) at SE.Graphics.DOM.TgmlInheritedElement.insertBefore(Node newChild, Node refChild) at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(Node newChild) at com.sun.org.apache.xerces.internal.dom.ParentNode.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ElementImpl.cloneNode(Boolean deep) at SE.Graphics.DOM.TGML.TgmlShape.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ParentNode.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ElementImpl.cloneNode(Boolean deep) at SE.Graphics.DOM.TGML.TgmlShape.cloneNode(Boolean deep) at TAC.Graphics.Editor.Core.GraphicsComponent.ExtractContent() at TAC.Graphics.Editor.Core.ComponentStencilItem.LoadItem(String file, String imageFile, String& description, Image& image) at TAC.Graphics.Editor.Core.FileStencilItem.Load(String file) Product Line EcoStruxure Building Operation TAC Vista Environment TGML Graphics Editor Multiple installations of Microsoft Office Cause If a PC comes with Microsoft Office 2010 (which is not currently compatible with Vista) and additional versions of Excel 2007 are installed, for example, it could remove or corrupt the installation of certain fonts. Resolution Obtain a fresh copy of the font .TTF file.  In this example, Arial.ttf. Install the font by dragging and dropping the .TTF file into C:\Windows\Fonts directory.

Issue Is it possible to see which user that have disabled an alarm? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Cause It is possible to see from the "show history" view for a disabled alarm. Resolution Open the disabled alarm view. Right click on the disabled alarm and choose "Show history". Right click on the columns field and add a column called "User name" in that column you can see which user that disabled the alarm.

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue No alarms are being displayed in the alarm queue. This includes alarms from any automation server that has been added underneath an enterprise server database or enterprise server alarms. Product Line EcoStruxure Building Operation Environment WorkStation Alarm Queue Cause This is a result of the alarm queue filter containing active filter conditions. Resolution Remove alarm filters: Click the Alarm Filter icon on the toolbar of the alarm queue. In the Select Conditions window, make sure that all of the alarm conditions have been removed or only the filters that you want remain. To remove an alarm condition, simply click the trashcan button on the far right side of the condition. Note: If a blank condition is left behind, it will prevent any alarm from being displayed in the alarm queue.

  Issue No more equation characters can be entered into a Function Block application Product Line EcoStruxure Buildings Operation Environment Buildings Operation WorkStation Buildings Operations Function Block Editor Cause You have exceeded the maximum number of characters allowed in a Function Block expression editor.   Resolution Expression text must have less than 500 characters. Split larger equations into two Function Blocks if needed. How to add an Expression Block  Expression Blocks 

Issue When adding License Entitlements via Device Administrator using the online method. After clicking activate, a "Communication failed" message is displayed:   Could not establish contact with License Server using SmartX Server Followed by a "License Operation Failed" message:   Add entitlement failed. License Server is offline. Error code: 41 Error message: CURL error: Product Line EcoStruxure Building Operation Environment Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When activating a SmartX Server license online, the SmartX server will try to connect to the license activation server to activate the license. If it cannot resolve the license activation server site name and connect, it will show up as offline. Resolution Make sure that the SmartX Server DNS is properly configured in the AS-P.  In Device Administrator select the Ethernet 1 Configuration tab. Check the Primary, Secondary, and Tertiary DNS settings If unsure of the correct DNS address, enter the Google DNS address of 8.8.8.8 or 8.8.4.4. The example below shows a local router address as the Primary DNS and Google DNS as the Secondary and Tertiary DNS.   To confirm that the SmartX Server can resolve the license activation server address Open a Console session on the SmartX Server in Device Administrator. Enter the command: ping schneider-electric.flexnetoperations.com If the DNS is correctly set in the SmartX Server, the result should look similar to that shown below: Note: Ensure that the ASP is fully connected to the Internet in order to perform Online Embedded License Activation. You need to be connected to the Automation Server using IP (Not via USB) to activate the embedded license.

Issue Is there any adaptive tuning in the flow control loop that drives the MP-V or RP-V damper loop that will be negatively impacted by extended periods of non-zero box flow setpoints when the associated AHU is disabled (i.e. no pressure at VAV so the damper will open fully and the flow control loop will saturate). Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV EasyLogic RP-V Cause No information on the internal Variable Air Volume Data object Resolution Airflow control in the MP and RP VAV controllers is not impacted by extended periods of non-zero box flow setpoints when the associated AHU is disabled. The damper is actuated by a single-speed motor with three states (open, close, hold), and to avoid windup or saturation effects, the flow control algorithm is not a PID loop. There is no need to link the AHU enable to the MP or RP flow control logic.

Issue Upgrading  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Guidelines for upgrading to higher releases Resolution Non-Sequential Upgrades: Versions 1.9.1 and Newer Starting in version 1.9.1, non-sequential upgrades can be performed from versions 1.5.X and newer. Please refer to the "Upgrading" section of the Release Notes for the software version you are upgrading to. The "Upgrading" section will direct you to prior release notes that you need to read through before upgrading and point out items with limited runtime compatibility during the upgrade process.  NOTE: If upgrading a system at 1.5/1.6/1.7/1.8 with LON devices, please be aware that there are special steps that must be taken to prepare the database for upgrade. These steps can be found in the Release Notes as well.  Sequential Upgrades: Versions 1.8.1 and Older For versions 1.8.1 and older, the upgrade process is sequential. In other words 1.2.0, 1.3.0, 1.4.0, 1.4.0.4020, 1.5.0, 1.6.1 The upgrade process can be found in the System Upgrade Reference Guide. The primary released versions were 1.0.0.161 1.1.0.362 1.2.0.767 1.3.0.938 1.3.0.10100 SP1 1.3.0.20011 SP2 1.4.0.4020 1.4.1.68 1.5.0.532 1.6.0.250 (RC) 1.6.1.5000 1.7.0.255 (RC) 1.7.1.89 The minimum upgrade path would be: 1.0.0.161 Official Release 1.1.0.362 Official Release 1.2.0.767 Official Release 1.2.0.2207 1.3.0.938 Official Release 1.3.0.10100 1.4.0.4020 1.4.1.68 Official Release 1.5.0.532 Official Release* 1.6.1.5000 Official Release 1.7.1.89 Official Release Note: On one site, the AS would not upgrade from 1.5.0.532 to 1.6.1.5000. Going to the 1.6 RC resolved the issue.   1. In order to upgrade to 1.5 the site must be at 1.4.0.4020 or higher. Some sites may be still running at 1.4.0.818, which was the original 1.4.0 release. Although this is not officially supported and will not be tested, it is likely to experience the same upgrade as one from 1.4.0.4020. 2. An upgrade from 1.4.0.4020 to 1.5 will NOT offer any runtime compatibility, while an upgrade from 1.4.1 to 1.5 will offer runtime compatibility. Consequently, for a site to maximize its operational status through the upgrade, we have two different upgrade scenarios as described below. a. 1.4.0 to 1.5 – this process flow is designed to allow as much of the plant as possible to continue to operate through the entire upgrade. For the first three steps of the process the Enterprise Server will continue to aggregate the alarms from all of the 1.4.0 Automation Server. Once the halfway mark is reached the Enterprise Server can be upgraded and will begin to aggregate the alarms from the 1.5.0 Automation Server.              i. Upgrade one WorkStation in order to be able to communicate directly to any of the 1.5 Automation Server that are upgraded in b below.             ii. Upgrade 50% of the Automation Server             iii. Upgrade Enterprise Server and all but one WorkStation             iv. Upgrade the remaining Automation Server             v. Upgrade the remaining WorkStation b. 1.4.1 to 1.5 - In this process, we can take advantage of the support for runtime compatibility and the Enterprise Server will receive alarms from both the 1.4.1 and the 1.5 Automation Server.             i. Upgrade Enterprise Server and all but one WorkStation which can be used to talk directly to unupgraded Automation Server if configuration changes are needed             ii. Upgrade Automation Server             iii. Upgrade final WorkStation Note: some sites have experienced issues with the ES restart after upgrade because of the .Net Framework 4.5 upgrade and port 80 usage. Adjusting this port to an available port resolves the problem. The conversion log may indicate an upgrade warning similar to warning shown below, this warning can be safely ignored, and furthermore the upgrade program corrects the problem in the 1.5 database.           :02:11  WARNING:      Property PFE202_PF601.SI in (~/BACnet/Application/ELE/GRAPHIQUES/ECLUSES CD S4/PORTES_CE_S4) is not defined in the new system, skip           PFE202_PF601.SI. <script src="chrome://dce.addin/content/content_javascript.js"> </script>

Issue TGML pages are slow to load in Workstation TGML objects are not responsive Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation TGML Cause The driver of the graphic card is outdated or not supported. Resolution Visit the webpage of the PC's brand and update the driver for the graphic card.

Issue The following error message appears when trying to change the system security settings of an Enterprise Server in Webstation:   An error has occurred Object protected ~/System/Security Manager/Global Security Settings     In Workstation the same settings are disabled (greyed out) and cannot be edited at all:   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Webstation Building Operation Workstation Cause The probable cause of this issue is that the Enterprise server is part of an EC - ES multiserver system setup. Then some settings are in a Lead - Shadow relationship and can only be controlled from the top EC (Enterprise Central) server. Resolution Edit these settings on the top Enterprise Central server.

Issue Graphics are not displayed via the WebStation. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Graphics Trends Display issues Long hyphen # character Cause When a graphic is requested on a Building Operation Webstation, it is not displayed. The display will remain blank. Resolution Try the following steps below to correct the WebStation loading issue. Check the file size of the graphic page. If the TGML graphic size is too large it can have issues loading in WebStation. Majority of the times it is due to an image that is too large such as a floor plan.  If a graphic, or trend chart object, is created through a EcoStruxure Building Operation WorkStation and its name contains a "long hyphen", the graphic and trend chart objects cannot be viewed through WebStation. The long hyphen is not a supported character. When creating object names do not use the long hyphen (—) only use the short hyphen if required (-) If the version being used is 1.3, upgrading to 1.4.1x may resolve the issue. Check the name of the AS, an unsupported character may have been used e.g.#, to resolve, remove the character.

Issue Graphics appear fine when viewed from WorkStation, but when a web browser (WebStation) is used to view the AS, dark lines appear across portions of the graphic. Some objects with transparent backgrounds (fill set to "None") may appear with a grey background when viewed through a web browser. Product Line EcoStruxure Building Operation Environment AS TGML Graphics WebStation Cause WebStation is less forgiving of some improper configuration settings than WorkStation. Objects attributes must follow proper syntax for Fill, Stroke, or Visibility. Resolution Open the graphic page in the TGML viewer Change lines, borders, and fills to some other value (black, for example) Change the attribute back to the desired setting (Visibility = Hidden or Fill = None) Save the graphic The improperly formatted attributes should be overwritten with the correct syntax and the graphic appears as desired in both environments.

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 When EBO servers (ES & AS) no more need to keep the unnecessary TrendLog objects, the obsolete objects need to be deleted from EBO servers, and their log data need to be removed from the Extended Log Storage (PostgreSQL/TimescaleDB) server as well.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server External Log Storage PostgreSQL (pgAdmin 4) TimescaleDB  Cause Deleting the obsolete TrendLog objects from EBO servers does not remove the old log data of the obsolete TrendLogs left in the PostgreSQL/TimescaleDB database. Resolution Once the obsolete TrendLog objects are deleted from EBO servers, their log data are no longer saved in the PostgreSQL/TimescaleDB. The next task is removing the old log data left in the PostgreSQL/TimescaleDB database.   1. As always, backup current EB & AS’s databases from EBO workstation.   2. As always, backup the current PostgreSQL/TimescaleDB database and save to a safe location. Backup the “ebo_db” from the PostgreSQL/TimescaleDB server using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html , or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail).  3.Remove the obsolete TrendLog from the PostgreSQL/TimescaleDB database (the “ebo_db”). Method_1: Delete the EBO TrendLog object from ES & AS’s & TimescaleDB using EBO workstation. (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (2) From the EBO workstation, go to the TimescaleDB folder (/Server 1/System/External Log Storage/TimescaleDB/Trend /Logs/Tree View), and delete the Trendlog object from PostgreSQL/TimescaleDB database. (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.   Method_2: If the above Method1 takes a long time to complete, you can delete the TrendLog objects from PostgreSQL/TimescaleDB database directly.  (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (Same as item (1) of the above Method_1) (2) From the PostgreSQL/TimescaleDB server, run the pgAdmin 4, select the “ebo_db”, open the “Query Tool”, and execute the below scripts: Find the ID of the obsolete TrendLog from the trend_meta table. Select Externallogid, source from trend_meta where sources like '%TrendLog Name or Path%' Remove the TrendLog from the 2 tables using the above found Externallogid as below. Delete from trend_data where externallogid = 1234567890 Delete from trend_meta where externallogid = 1234567890 (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.  

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 After deleting unnecessary TrendLog objects from EBO and their logged data from the Extended Log Storage (PostgreSQL/TimescaleDB) by selecting the “Clear log” from the System folder (i.e.: Server1/System/Extended Log Storage/TimescaleDB/Trend/Tree View/…”), the Windows still shows the same free disk space size as it was before the deletion. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server External Log Storage PostgreSQL (pgAdmin 4) TimescaleDB  Cause PostgreSQL databases require periodic maintenance known as vacuuming for Windows to recover or reuse the freed-up disk space occupied by PostgreSQL/TimescaleDB. Resolution There are two variants of VACUUM: standard VACUUM and VACUUM FULL.  VACUUM FULL can reclaim more disk space but runs much more slowly.  VACUUM FULL requires an exclusive lock on the table it is working on, and therefore cannot be done in parallel with other use of the table. Refer to the documentation mentioned at  https://www.postgresql.org/docs/9.5/routine-vacuuming.html  before performing the VACUUM command.   Below is an example of the procedure to get the freed-up disk space occupied by PostgreSQL/TimescaleDB back to Windows.   1. Back up the current PostgreSQL/TimescaleDB database and save to a safe location. Backup the “ebo_db” from the PostgreSQL/TimescaleDB server using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html , or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail).   2. Stop the External Log Storage from EBO. Open the Properties of the TimescaleDB object (/Server/System/External Log Storage/).\ Remember (take a note) the current value settings of the “Host Address” & the “Database Name” attributes. Change them to the wrong value (or clear them) so that EBO fails to connect to the PostgreSQL/TimescaleDB server. Repeat the above operation for all the other servers (AS’s) that are enabled/connected to the PostgreSQL/TimescaleDB server.   3.Delete the old logs from the PostgreSQL/TimescaleDB database (the “ebo_db”). Run the pgAdmin 4, select the “ebo_db”, open the “Query Tool”, and execute the below scripts:   Delete from trend_data where DATE_PART('day', now() - timestamp) > 365   Delete from event_data where DATE_PART('day', now() - timestamp) > 365   4. Vacuum the Database with Full option. From the same Query Tool on the “ebo_db”, run the below command: Vacuum Full Wait until it completes (this may take a while depending on the number of old logs that have been deleted from the tables).   5. Start the External Log Storage from EBO. Open the Properties of the TimescaleDB object (/Server/System/External Log Storage/). Set the value of the “Host Address” & the “Database Name” back to the correct value, so that the EBO server successfully connects to the PostgreSQL/TimescaleDB server. Verify the EBO server is connected to the PostgreSQL/TimescaleDB server, and it works normally.    Repeat the above operations for all the other EBO servers (AS’s) that were disabled/disconnected from the PostgreSQL/TimescaleDB server.