Building Automation Knowledge Base

Issue Web Service addition Script Web Service Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add Script Web Service files and how to add to a project or site How to create values from Script Web Service Files How to add values to graphic that uses the values from Script Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: 1. are hardware, programming language, and operating system independent 2. Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services 3. Web Service interfaces are supported in both the AS and ES 4. Like BACnet, Lon, and Modbus, you can create a Web Service interface.      EWS Interface - EcoStruxure Web Services      Script Web Service - Generic Consume via Script      Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service)      SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Sunrise and Sunset for a particular location data using Script Web Service: -Select New...Interface...Web Service...Script Web Service This first example is for a Calculation program for Results=A+B -Enter the WSDL Service and Endpoint are auto-filled Not necessarily all the time IP Cameras -Script Web Services Interface: -Script Programs can bind to the web service with the "Webservice" declaration. -When the name bound service is typed and a "." is put after it, intellisense drop down will show the available methods WSDL file is brought into the database Drop down methods become available even if the URL of the WSDL is not -The web service capabilities can be used within the code for manipulation, data gathering, or whatever else. -Script Web Services Post and Gets -Script programs can send requests directly to a web service with the SendWebRequest keyword. -The syntax requires 5 specific arguments BaseURL - URL that will be processing the message Method - Method of processing the POST and GET (dictated by URL) Headers - Defines certain parameters that are meaningful to the URL (IsMobileApp:True;IsAndroidClient:True) Content-Type - Defined by the URL Message - What is actually being sent to the URL -Script Web Services - Considerations -Bindings to a web service require a recompile -Display of captured information will get localized   Next, Create a Script Program for Calculations Here is a simple script program which defines the calc and values The below shot is the values A=12, B=3, and the Results of the calculation. Below are the binding for the Script Calc program to the Values The below shot is the binding of the Calc program to the Script Web Service The results are a calculation in which we supply value A and B and the Script Web Service performs the calculation with results of 15.   We can change the value of A to from 12 to a value of 13 which Results in 16 as shown in the shot below.

Issue Infinity controller error: Type not valid for this IO channel Product Line Andover Continuum Environment Continuum Cyberstation Cause ElecType mismatch between what is in the database and the field controller hardware. An example of this problem would be offline creating a voltage output on a DO-4.  It will save to the DB since it is a valid InfinityOutput configuration.   Although when attempting to do a Send to Controller the controller knows that point type is not valid on the specific IOU module hardware. This can also happen when an object is imported into Continuum because the database error checking is less strict than when creating the object online. Resolution Go into offline editing Check the point configuration If it does not match the field hardware, then correct it, save it, go to online mode and reload.

Issue Modicon Switch Ordering options and how to configure the Ethernet Switch for RSTP for EBO Product Line EcoStruxure Building Operation Environment Modicon RSTP Switch (Not Connexium) Building Operation Automation Server Premium MPX and/or RPX Controllers Ethernet Switch Configurator Cause Schneider Electric Industry Offers an RSTP enabled Ethernet Switch that can be used with EBO instead of 3rd party Switches Resolution The following video will illustrate the following steps for Ordering and installing the Modicon Ethernet Switch with EBO The Modicon Connexium Ethernet Switch has been replaced by the updated Modicon Switch Modicon Switch Part Numbers and Email address for ordering Connect and use the SE Ethernet Switch Configurator executable for Switch configuration Set the Time and use the Syslog for troubleshooting Configure EBO and the controllers (MPX/RPX) for RSTP Test the Modicon Switch, EBO, and the MPX/RPX controllers for RSTP     Related Links: Modicon Switch Part Numbers and Ordering Information - (see attached Part Number slide) MCSESM Switch Installation Manual MCSESM Switch Configuration Manual Ethernet Switch Configurator Software - look for  SchneiderElectricEthernetSwitchConfigurator2303_Windows_x86.zip Other Modicon Switch documents RSTP Troubleshooting Community Thread TGML Graphic Setup Video (Training Department)

Issue NRE default configuration and RAM disk removal Product Line TAC IA Series Environment I/A Series N4.11 Jace 8000 Cause In Niagara 4.10u1 and earlier, the RAM disk was used to temporarily store alarm and history data. During station save, this data was copied from the RAM disk and zipped up, and stored on Flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the Flash. Resolution A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. JACE-8000 NRE Memory Default for (older) Niagara 4.10 - sizes in MB: System Reserve Size:          0 Heap Space Size:              360 Meta Space Size:              56 Code Cache Size:              16 RAM Disk Size:                384 Free Memory:                  ~16 JACE-8000 NRE Memory Default for (newer) Niagara 4.11 - sizes in MB: System Reserve Size:          0 Heap Space Size:              384 Meta Space Size:              64 Code Cache Size:              32 RAM Disk Size:                Not present (cannot be created) Free Memory:                  ~352   These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000.

Issue Under different circumstances, the comm port on infinet or bacnet devices will not be assigned and will show blank in their editor. The controllers may be controlling the equipment correctly, but they can't be reloaded and communication doesn't work to and from the device. Product Line Andover Continuum Environment CyberStation Webclient Windows XP, Windows Vista, Windows 7, Windows 10 Windows Server 2003, 2008, 2012, 2016 Cause This issue can happen on an upgrade where a send to database is used if the controller didn't exist previously or under other unknown database circumstances Resolution 1. Click the link to download the following TPA1498  NOTE: the TPA indicates the following at the bottom Save the new .dmp file Right click the NetController to reattach the Infinet controllers to -> select Import Into Right click the NetController to reattach the Infinet controllers to -> select Send to Database Commports will be reattached.  (THIS SHOULD BE SEND TO CONTROLLER) (The previous line, Import into, brings the corrected comm ports into the db) 2. It may be necessary to make changes to the database in order to reassign the ports to the controllers. Backup the database and send a copy to PSS for assistance The objects can be reassigned, but the queries should be tested prior to updating in the field.

Issue Xenta 102-ES configuration and wiring for 2 position (on / off) heating actuators or other digital heating control Product Line TAC Vista Environment Vista Xenta 102-ES Cause Wiring for 2 position heating control on the Xenta 102-ES is different than increase / decrease type actuators. Resolution The Xenta 102-ES documentation refers to two position heating control as thermal actuators, thermo or TAO and can be somewhat confusing. The same info applies whether using a two position hot water valve, any on / off type electrical heat (such as baseboard heaters or electric heating strips. Here's what you need to know: If using only one stage of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin or if configuring from Vista Workstation or the OP set nciAppOptions bit 5 to 1 and leave bit 6 as 0.   From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used.   If using two stages of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin and select Enable for Secondary Heating. If configuring the device from Vista Workstation or the OP set nciAppOptions bit 5 and bit 6 to 1. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. Only terminal V6 will be switched for second stage of heat. Note: The triac outputs of the Xenta 102-ES are ground sourcing and should be wired accordingly. See Digital outputs (V) on most Xenta 100 series controllers are ground sourcing (voltage sinking) for additional information.

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 Correcting failed links between programming objects after upgrading files from .vsd to .vsdx Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Cause After existing .vsd files from pre-WorkPlace Tech 5.10 versions can have corrupted links that stay red when programming objects are added or modified. Resolution This video demonstrates how to correct binding failures that can occur when existing Visio drawings are converted from .vsd to .vsdx format when upgrading to Workplace Tech 5.10 and EBO 4.0 and newer WorkPlace Tech Editor. Note: The objects in the original drawing will no longer show a Master Shape reference (below) The frame around the object appears a little different as well.  The Mega Master will not be changed so this has no effect on the performance of these objects.

Issue Are there any Example Reports for the new native Notification Reports which came out in EBO 3.2 to replace the now deprecated WebReports and Report Server? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause As of EBO 2022 (4.0) WebReports and the Report Server have now been deprecated and replaced by External Log Storage using Postgres SQL and Timescale DB, plus the new native Notification Reports which are now built into EBO 3.2 and above, but there are no examples to help new starters to get going. Resolution A Schneider-Electric Community page has been set up specifically for Notification Report users so that they can share their Reports and collaborate on Reporting ideas: https://community.se.com/t5/EcoStruxure-Building-Operation/Reports-showcase-share-your-reports/m-p/388619#M75732

Issue How to decrease the amount of LonWorks network traffic by using throttling. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause EBO servers could generate a lot of communication on the LonWorks Network. Throttling could be activated to decrease the amount of traffic. Resolution To decrease the amount of LonWorks Network traffic, it is possible to activate Basic Bandwidth Throttling. The setting is found under the Advanced tab for the properties for the Lonworks Local FT-10 Interface.   Picture showing default settings.   This video will show how to activate Basic Bandwidth Throttling and what impact this could have on the amount of LonWorks Network traffic.   At the end of this session you will be able to: Set up Basic Bandwith Throttling for the LonWorks network  

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server  Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately  For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log  Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: EBO 4.0 (2022) and higher NOTE: You may have to enter Private Browsing mode to disable extensions, as you may see a blank page when viewing logs. Ensure credentials used are for a local 'admin' user or have access to the ~/System folder of the EBO Server you are connected. Click the 3-bar menu to navigate Select System, then Modules, then Trace One will see System Log and Trace Log in the menu, and clicking on System Log or Trace Log will open them in a new tab. NOTE: Please be patient as it may take some time to transfer the file. Once you see text in the tab, right-click on a blank area and select Save Page As... (Firefox) or Save As... (Chromium-based browser). It should recommend saving as SystemLog.txt or TraceLog.txt automatically; however, to be helpful, please add the EBO Server Name and Date to the filename. EBO 3.2 and earlier See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation.   Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server.                   Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities  

Issue Metric vs. Imperial Units as displayed Using Webstation Regional Settings Any device, will by default, show configured units. Regional settings must be applied to normalize all devices. Product Line EcoStruxure Building Operation Environment Webstation TGML Graphics SNVT values Cause Incorrect Units will appear in webstation if webstation regional settings are not configured correctly. Resolution Log into Webstation Select Settings > Change Regional Settings   Select the desired Language Select the desired Measurement system Click Ok NOTE: Settings are preserved via a cookie stored on the local PC. Any time cookies are deleted this will return to its default setting.

Issue Cannot access SP-C web interface due to TLS error. Chrome error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Edge error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Firefox error: SSL_ERROR_UNSUPPORTED_VERSION Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause As per the table below, SP-C with OS  2.0.24 or lower does not support TLS 1.2.  A modern web browser will block access to sites that use TLS 1.0 or 1.1.     Resolution  If TLS 1.2 support is required, an OS upgrade to 2.0.25 or higher is required: Upgrade the controller's firmware to a version that supports HTTPS, as explained in:  AN 314 Security Expert - HTTPS Connection to the Security Expert Controller - Integration Guide If the current SP-C OS version is 2.0.24 or lower, contact Schneider Electric support to acquire the upgrade package and further documentation.

Issue The TA210U controller is obsolete since many years, but the manual is sometimes still requested Product Line Field Devices, TAC Vista Environment TAC210U TA210U 2107030QRW 2107030QRT 0844427005 0844428005 Cause Old controller Resolution The (Swedish-only) manual can be found here: TA210U Controller User Manual (L3238001.pdf).

Issue Creating binding templates. Product Line EcoStruxure Building Operation Environment Binding templates for Script and Function block programs. Binding template examples:  Type Binding Template Examples Path Matching Binding Templates and Syntax Path Matching Binding Template Examples  Cause 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. 2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. 3 - Binding Template Types examples Resolution 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. Under the system folder of the AS or ES there is a folder called "Binding Templates". In here you can create custom templates by right clicking and selecting "New", "Binding Template". To create a generic template that will bind both inputs, outputs, values and other object types follow these steps: Press Next and the following screen appears: Select All Types and press Next: Click twice on the Add Rule icon (Green +) then enter the three rules as follows: Press create and the new IO Binding template will be created.  If you have used a common naming convention in your points and within the programs, you will be able to use this template to bind all the points and values to your programs. Drag the AS across to the IO Binding template (as below) and it will match all of the point names and use Requested value attribute for the output points. This example shows 2 IO Binding templates, as one was created at the AS level and another at the ES level. Only 1 is actually required to provide this functionality. You can subsequently edit the binding template and it will show as follows:   2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. It is common for a system to consist of many controllers that have been created from the same import file. This will mean that there are many instances of the same names being used, but this is not an issue until a graphic containing several controllers are to be bound. Create a "Path Matching Binding Template" as shown above and configure as shown in the following screen shot. Notice that the Binding candidate has /Application/ between the "Unit" and "Point" to match the tree structure.        The screen shot below shows the site system tree structure, with part of the graphic binding page. Note that for the binding template to work, the bind names used in the graphic must be unique. eg. L6W1_CHB_006 (Unit) and ReturnAirTemp (Point).     For an Export of this template, click Binding Template Export 2013-08-15 083240.zip. 3 - Binding Template Types examples see the Online Help. An additional resource is the Exchange Community in particular the following Knowledge Reinforcement Session Also check out the SmartStruxure-Binding Templates-Lesson 1-7 Quick-Help video on the Exchange.

Issue How to find out if a user has created a personal and/or a public dashboard Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Cause Customers may want to know if there is a personal or public dashboard (or both) under a user Resolution We can search in Workstation to know if a user has created a personal or public dashboard (or both). Enter “Dashboard” on the “Include type” and search over the whole server.   Public dashboards can be created by any user anywhere under the server except under the system tree. In the following example, any results that appear under the “/Server 1/System/Domains” is a personal dashboard since it is tied to the users, and the rest are public dashboards.     Please note that creating a personal dashboard requires a Personal Dashboard License.    How Dashboards Work  Public vs Personal Dashboards  

Issue How to calculate the required disk space that will be used by WebReports? How to know if SQL 2008 R2 Express (with Advanced Services) will have adequate storage space for the sites Reporting requirements? Product Line EcoStruxure Building Operation Environment WebReports 1.9 / 2.0 Cause Require the ability to forecast how much space will be required to store and retain data within the Building Operation WebReports database. Resolution The attached Excel Spreadsheets can be used to forecast how much space is needed to store and retain the Building Operation WebReports database. WebReports_DB Usage Calculator.zip WebReports_DB Growth Estimator 2.0.zip Note that SQL 2008 R2 Express only allows a database size of 10 GB, so if your configuration is more extensive than that you should probably consider using the full SQL Server 2008 R2 editions. As a quick indicator here are the record sizes for each object type stored in the report server database: Object Type Size per record (bytes)   WebReports versions <1.8 >1.9   Ext. Trend 140 165   Meter 170 140   Alarm 900 500   Event 400 520  

Issue Cannot open the FlexNet License Admin, the TAC license server is not running as a service, or the vendor daemon is down. Product Line TAC Vista Environment Vista LMAdmin FlexNet License Administrator Cause If the TAC Vista Server installation option "Use the local TAC License Server" is not selected during installation, the license server will be installed but not successfully configured. When the license server is not running it will prevent the LMAdmin web interface from launching. If the license file is not in the correct location when the license server is started, then the vendor daemon must be started manually. For general information on the new license system, see LMTools Licensing Administrator program is replaced with LMAdmin in Vista 5.1.8 or greater. Resolution Remember that a valid and un-modified License File is necessary for the following troubleshooting steps to work. If the License file was manually manipulated in any way, please revert to a File specifically licensed for the machine where the License Server resides. Before proceeding, make sure the setup of the license system is made correctly following No license after reboot when TAC Vista Server (TACOS) runs as a service Check out this video about the new Vista 5 licensing system on the Community website. Check out the TAC License Server Setting tool below for the new license system. Click here to download the zip file.       Could not reliably determine the server's fully qualified domain name This is a bug in the lmadmin.exe file. Either replace the lmadmin.exe file with the newest available or install the newest version of the license system available. You can have a newer version of the license system installed than the TAC Vista version installed. E.g. TAC Vista 5.1.8 will work together with a license server version 5.1.9 Cannot Open the Flexnet License Admin Ensure that the TACLicenseServer is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services. Scroll down and select TACLicenseServer. Click Start in the top left corner of the window. Make sure that the site license is the only file in the license server path. If there is a demo license in the file path when trying to start the license server, it will fail to start. Sometimes you will get the following Windows error. Error 1067: The process terminated unexpectedly. Note: TAC License Server with spaces is not the correct license server. If TACLicenseServer is not found in the list then move on to the next troubleshooting section titled "Setting up the TAC License Server as a Service".   If the TAC License Server will not start then it may be due to another program using the 8080 TCP port. Use TCPView to search for programs running on local port 8080 and either stop this program or use the TACLicenseServer Settings tool at the top of this page to change the port that the TAC License Server uses. If the TACLicenseServer still does not run then continue to the next section below, Setting up the TAC License Server as a Service.    Setting up the TAC License Server as a Service LMAdmin.exe must be registered as a service. When first installing Vista the option "Use the local TAC License Server" should be selected. When this option is selected it will install the license server, register it as a service and start it. When "Use a license file" is selected it will only install the license server without configuring its settings. This can be corrected by reinstalling Vista and making the proper selection or by a manual configuration procedure. The manual procedure steps are listed below. Note: The option "Use a license file" only applies to a demo license, not a site license file. Manual Procedure to Register the License Server as a Service Start a command prompt as an administrator. To do this go to Start > All Programs >  Accessories and right-click on Command Prompt, then select Run as Administrator. In the command prompt go to path C:\Program Files\Schneider Electric\License Server\ (This can be done by entering "cd" and then the directory path listed here.) For 64-bit OS go to "C:\Program Files (x86)\Schneider Electric\License Server\" Run the command: "LMAdmin.exe -InstallService TACLicenseServer".   Manually copy the license files that are to be used to the new license file folder location. 32 bit - C:\Program Files\Schneider Electric\License Server\taclic\licenses 64 bit - C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses   In the command prompt type, the following command to start the license server "net start TACLicenseServer". Note: If the license files are not copied prior to starting the license server, the vendor daemon will not be started successfully and must be manually started after the license files have been copied to the new license file location. For instruction on how to do this, follow the steps in the next section Vendor Daemon is Down When the license server is installed but not configured, as mentioned above, the TAC Vista Server installer will not create a shortcut to the license administration tool in the start menu; since the shortcut will not work. A shortcut is created in the installation folder and can be used to create a shortcut in the start menu manually. The shortcut can be found here "C:\Program Files\Schneider Electric\License Server\FlexNetLicenseAdmin". For 64-bit OS the shortcut is found in "C:\Program Files (x86)\Schneider Electric\License Server". Vendor Daemon is Down   Note: If working on a 64 bit PC, replace "Program Files" with "Program Files (x86)" in the file paths below. Go to All Programs > Schneider Electric > TAC Tool 5.X.X > Flexnet License Admin. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password). Click on the Vendor Daemon Configuration tab and then select the taclic daemon. Verify that the path in the License File or Directory field matches the location of the site license. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start. If the Vendor Daemon still does not start after checking the file paths, verify that the site license has been hosted to the correct MAC address. For help finding the MAC address, see How to locate a computer's MAC address. NOTE: Also make sure there are no other Flexnet License Servers installed on this same machine (SmartStruxure, Power Manager, etc). If there is another license server running on the same machine then this can cause a conflict. SmartStruxure license and TAC Vista license on the same PC can walk you through merging them together. If IPV6 is enabled, you may need to disable it and reboot the machine. Switching from a site license to a demo license Log into LMadmin and stop the license server Save the Demo License file in C:/Program Files/Schneider Electric/License Server/Licenses Open the desired engineering tool and point Vista to the Demo file When finished, log into LMAdmin and start the License Server.  This will tell Vista to continue using the site license. A site that has worked with the installation from a remote desktop or the different user logged in Open task manager Check for process "lmgrd" of 2 of them are running the FlexNet server might try to read from the wrong server. Shutdown down both processes and restart the FlexNet server Log in to FlexNet admin and start the vendor Reread the license file Also, check License Administrator error "EXITING DUE TO SIGNAL 28 Exit reason 5"

Issue SoapEwsRestProvider serves data sourced from any EWS Server using the standard EWS SOAP protocol. The architecture for the SmartConnector REST Extensions integrates Swagger to provide a rich self-documenting API. Below errors indicate configuration issues. The User Name or Password were incorrect. "Message": "Authorization has been denied for this request. " "Message": "The HTTP request was forbidden with client authentication scheme 'Digest' " Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Building Operation Enterprise Central Cause Smart Connecter or EBO Incorrect configuration. Resolution Make sure that SboEwsRestProvider is started and has a correct port that is not used by any other Smart Connector data provider or other application.   Make sure that EWS server address has the following format: HTTP: http://ipAddress:port/EcoStruxure/DataExchange HTTPS: https://ipAddress:port/EcoStruxure/DataExchange For ES/EC, check software administrator to make sure there is no port conflict: Software Administrator shows red outline (box) on the Communication Ports (HTTP / HTTPS) - Communities (se.com) In EBO, make sure EWS server is enabled: Enabling the EcoStruxure Web Service Server Check if username and password used for the SOAP provide has correct permissions and can be used to login to EBO server. If the user is not located in the default domain, make sure to add the domain name in the Username string, ex. "Domain/User". If HTTP protocol is used (not recommended), check the following: In EWS server configuration, make sure that "Enforce Secure Communication" to Disabled. In Security Manager, make sure that "Enable Incoming http communication" is enabled.

Issue Sigma CE files are not created. Environment Sigma CE 4.06 Sigma 4.06  Cause Sigma CE files are not created when BuildCE.exe is executed.. Resolution A Sigma service pack is required. Sigma 4.06 SP1 is attached. There is a readme.txt file for installation instructions included in the download.

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)