Building Automation Knowledge Base

Issue EBO can't overwrite notification report file. "System alarm: File access error: sharing violation:" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Notification file is used by another program and "Uniqueness" paramter is set to "None" so EBO can't write on it, ex, Microsoft Excel opens the notification report.  Resolution Make sure that notification report is not used be another program, ex. Microsoft Word or Excel. If the program locking the notification file is not known, Windows Resource monitor can be used to know which process is locking the file, as below: Press Windows key+R to open "Run" dialog box. In "Run" dialog box, write “resmon” and pres Enter. In Resource Monitor "CPU" tab, expand "Associated Handels"  In "Search Handels" box, write the notification file name. In "Image" tab, note the process name. To end the process which is locking the file, Right-click on the process and then click on “End Process”. It is also possible to append or prepend a timestamp to the file name, so EBO can generate a new file each time.

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue How to create custom reports in Building Operation WebReports Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Custom reports are typically created by modifying another report and then saving these changes. Typically used are the factory-supplied reports as the base for a new report then enter the filtering criteria that are required to be used in the new report. Assign a unique name to the custom report and save the new report as a dashboard or prompted report.  There may be a need to create a report not based on any of the standard reports provided in these Report Packs, this article covers this process. Resolution To create a non-factory-supplied report within WebReports it is necessary to use an editor.  Since WebReports use Microsoft Reporting Services it is recommended to download the Microsoft SQL Server 2008 R2 Report Builder 3.0 or MS MSQL Server 2012 Report Builder.  This is a free tool provided by Microsoft that provides an intuitive report authoring environment for business and power users. This download provides a stand-alone installer for Report Builder 3.0.  Please note that Product Support does NOT provide support for Report Builder.  After downloading and installing the Report Builder application, the steps are as follows:  Each of these steps is also located on the Building Management System WebHelp site, a link for each of these steps is provided for additional reference and guidance. Start Report Builder and create a new blank report, see Creating a Basic Report for the steps.  After Creating the report create a data source that connects this report to StruxureWareReportsDB, see Creating a Data Source for these steps Then create the Data set, so add to the report which tables, views, stored procedures, and fields from the StruxureWareReportsDB are required to use in your report, see Creating a Dataset for these steps. This data can then be added to the custom report as required.  See Setting Up a Report for an example of setting up a report. See Adding an Image to a Report  on how to add images to the report  The new report now must be deployed to the Reports Server where it can be accessible to WebReports. To complete this procedure use SQL Server Reporting Services Report Manager. See Deploying a New Report to the Reports Server to view these steps in detail.  Finally, the report must be synchronized in WebReports to be deployed and therefore appear in the WebReports Reports Tree. Use WebReports with a Web browser to complete this procedure.  See Synchronizing WebReports with a New Report for the steps to complete this. Once all these steps have been completed successfully the new Report should be visible in the tree - the placement of these reports will depend on where they have been uploaded in step 5 above.  See the image below:

Issue The room controller is replaced on-site, and you need to copy the same configuration of the faulty Controller. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 SSL SE7000 Cause The wrong file format might have been used Resolution This Video explains detailed steps to copy the configuration to a new or a replacement controller:   Please note that the older controller will probably have an older firmware version, and thus, you might have to downgrade the new controller to the same version. Also, note you can’t downgrade to below 2.0.0. If the older controller has a version before 2.0.0, this solution will not work and will have to configure the new one manually. Only After the configuration has been transferred successfully you can upgrade the controller to a new firmware version.

Issue A new feature in EBO 3.2.X where the value is grayed out when the binding on the priority of a BACnet object matches the BACnet Default priority level Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Missing Release note documentation about the new feature added to EBO 3.2.X. Resolution In EBO versions prior to 3.2.X, when a bind in Priority matches the Default BACnet Write Priority, the values can be changed without forcing. From EBO 3.2.X, users need to force the value, let it change, and then un-force it. The following screenshots show this feature in more detail. The following image shows the Default BACnet write priority has been set to 16. Now, for example, if a program output is bound to Priority 16 of an analog value: The value property would be greyed out and has to be forced if changes are needed.   This is a new feature in EBO 3.2.X which is not mentioned in the Release Notes documentation.   Hint: A defect # 45570 has been documented in Release Notes 3.2.X about “Webstation - BACnet analog value's value property is not greyed out when there is a bind to the default priority.”. This issue has been fixed in EBO 4.0.X.   

Issue The automation server password policy is grayed out making it unavailable to make configuration changes. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium   Cause When an Automation Server is attached to an Enterprise Server, all of the password policy configurations are inherited from the enterprise server. Therefore the AS settings cannot be changed.  Resolution The password policies of the Automation Server must be administered from the ES when it is connected to an Enterprise Server.   In order to make changes to the password policy settings in the Automation Server directly, it must be detached from the Enterprise Server. Note: For EBO V 1.9.X and lower, the password policy settings can be located under Control Panel > Security and Communication > Security settings area. For EBO 2.0.X and higher, the password policy settings can be located under Control Panel > Security and Communication > Password policy.

Issue Resource Advisor platform, which serves as a repository for water, gas, and electric invoices, enabling customers to focus on evaluating metered data. Assisting organizations that are committed to sustainability. Setup information. Product Line EcoStruxure Building Operation, EcoStruxure Resource Advisor Environment Building Operation Automation Server Premium Building Operation Enterprise Central Building Operation Enterprise Server Cause Information on setting up Resource Advisor is not available for download Resolution Click this link for an overview of Resource Advisor. Attached is a more detailed document including EBO Setup Guide and links for additional Resource Advisor information.

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF

Issue When the Vista export file is converted using the Vista conversion to an EBO Server the Xenta devices are created with an empty application. Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Conversion tool Cause The user name that was used to log into Vista Database to run the Database export does not have full access to the Xenta devices Function Block Program. Resolution Log in with the System user that has full access to the Vista Database and export the database for the conversion tool to use.

Issue The Alarm Priority does not display the correct value (110) in the Alarm View or Event View when the Alarm is in the "Alarm" state and displays 100 Value instead. It displays correctly in the Alarm view when the alarm state is "Acknowledged" or "Reset", and it displays correctly in the Event view when the alarm state is "Reset Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Incorrect configuration Resolution There is an"Alarm decorator override" that seems to override the priority for the alarm If in alarm state and priority is 110, then the priority is overridden to 100 as configured in the alarm decorator object Removing the override in the decoration will resolve this issue

Issue IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue Embedded WebStation client licenses were needed when logging directly into a SmartX server as of 3.0.1 but are no longer needed Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation SmartX Server Cause The license requirement is being removed due to market feedback. The quantity of direct web connections to the SmartX server is restricted by the Architectural Guidelines only. Resolution Important for version 4.0 (EBO 2022) and above:  Note that in Building Operation 2022 (v4.0.x) and above, WebStation licenses have now been enforced at the server level and are required.   If there is no embedded server license for example "XWSWXBU0000SD ASP Bundle - Standard" in the SpaceLogic server it will not be possible to login to the server using Webstation. The Webstation license is included in the embedded server license.   For version 3.0.x The change is available via a HotFix to version v3.0.3 and will be incorporated into Maintenance Release v3.0.4. In both the HotFix and the Maintenance Release, license status presentations in the Device Administrator and Control Panel will indicate the availability of 99 client licenses. However, the supported quantity of direct web connections to a single SmartX server is established by the Architectural Guidelines; currently, the maximum is five concurrent connections. In v3.1, the Device Administrator and Control Panel will not list client license availability at the SmartX server level since it is not constrained by licenses.  

Issue After editing an MNL-800 application with the WorkPlace Tech Tool Editor, an error is displayed indicating that the application file could not be saved. Product Line EcoStruxure Building Operation Environment Building Operation Workstation >1.4 Building Operation WorkPlace Tech Editor Cause The name of a LON Network Variable (nvi or nvo SNVT) or a LON controller configuration constant (nci SNVT) contains a space. Echelon standards do not allow spaces in network variables or configuration constant names. Resolution Edit the application file removing any spaces or other non-supported characters from network variable and configuration constant names. More information is contained in the SBO WebHelp topic "WorkPlace Tech Editor"

Issue Detailing configuration and starting DWiz on a computer running EcoStruxure for Buildings Operation. Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Xenta 281 Xenta 301 Xenta 401 Cause DWiz (Download Wizard) was a part of the TAC Vista installation, but not so commonly used in EcoStruxure Buildings Operation, and therefore no longer included in the Start menu. It is however still installed and could be started from Windows File Explorer. Resolution   Verify the Com port used. If your computer does have a serial port, this is normally Com1 or Com2. If you are using a USB to RS232 adapter (like Aten), you could get a much higher number. The program requires a port number between 1 and 9. You may need to change the port number. This could be done via Windows Device Manager. In Windows File Manager, go to the directory where EcoStruxure Buildings Operation Workstation is installed. Here you will find DWiz.exe as well as MentaSetup.exe. Start MentaSetup.exe, adjust Com Port, select Apply and Close. MentaSetup        5.  Now it should be possible to start DWiz.exe located in the same directory.

Issue How to troubleshoot a communication issue with the Sigma interface Is there a log available within the ES that shows the Sigma communication between Sigma controllers and the ES Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Workstation Building Operation Enterprise Server Cause When troubleshooting Sigma issues in an ES it can be helpful to see the communication between the Sigma controller and the Sigma interface in the ES to help identify this issue. The trace log within the ES is available and is configured as described below in the resolution. Resolution The level of logging for Sigma in the Trace Log needs to be increased: Open Workstation and navigate to [ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.sigma" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Sigma issue, then perform these steps now. e.g. If ifs a graphics issue then run the respective graphic. Retrieve the log by right-clicking [ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Sigma decoder can be used to assist in viewing/debugging the Sigma trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3).   Note: If the ES is restarted for any reason whether by manually stopping in the Software Administrator or other, the nsp.pin.sigma will default back to 'Information'.

Issue Many users are unsure of the implication of the field "Interval time zone" in the Trend Log configuration window. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause The setting "Interval time zone" under the Trend log configuration has caused some users to believe that this setting stores trend data in either "UTC" or "Server local time" Resolution The trend log data is always stored in UTC time, regardless of the option selected under this setting. This setting is intended for preventing problems with Daylight Savings Time (DST) when the logging interval is more frequent than 1 hour. See Interval Trend Log Properties – Basic Tab in EcoStruxure WebHelp. NOTE: When the interval is longer than 1 hour and you want to continue to log that interval after a DST change, use Server Local Time. For example, the log interval is every 24th hour at midnight and you want to continue to log at midnight even after a DST change, so you use Server Local Time. During the DST change in the Spring, the log sample will register after 23 hours. After the DST change in the Autumn, the log sample will register after 25 hours. Interval Time zone 

Issue AS-B/P is unable to upgrade to the EcoStruxure Building Operation V3.2.x from out-of-the-box or DFU mode. When checking the upgrade progress file, you receive the following error: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In V3.2.1, the change was made to use IP-over-USB as a way to communicate faster through the USB. Due to this, IPv4 and IPv6 need to be enabled on the connected device running Device Administrator. Resolution Check to make sure IPv6 is enabled on your machine. Open a Command Prompt window and run the "route print -6" command If it only shows two IPv6 addresses then IPv6 is disabled and you will need to enable it To enable IPv6 Open Registry Editor on your Windows Machine Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Double-click on DisabledComponents to edit Change value from "FF" (IPv6 disabled) to "00" (IPv6 enabled) Note: The Disabled Components registry value does not affect the state of the check box. Therefore, even if the Disabled Components registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is the expected behavior. Note: You must restart your computer for these changes to take effect.  

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.

Issue Sigma server fails when a Data Import is initiated during a Sigma transition Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or not used currently. Delete the file (located c:\sigma\data), it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary using SigmaX - Doctor. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary using SigmaX - Doctor. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue Customers may need a copy of their License Entitlement certificate Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Missing Entitlement certificate  Resolution Customers have access to the following link, where they can use the Entitlement ID or Activation ID to login to the Licensing page: License Page information After logging in, select the “List Entitlements” under “Activation & Entitlements” on the top. Tick the checkbox in front of one Activation ID (ACT), select View/View certificate Now, a new page pops up which contains the Entitlement Certificate information. This can be saved or printed.