Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,209
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,845
  • TAC IA Series 1,824
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 330
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 148
  • CCTV 53
  • Project Configuration Tool 47
  • EcoStruxure Building Activate 13
  • EcoStruxure Building Advisor 12
  • ESMI Fire Detection 8
  • Automated Engineering Tool 4
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
  • Previous
  • 1 of 2
  • Next
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Building Automation Knowledge Base

Sort by:
Helpfulness
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 40
    • 41
    • 42
    • …
    • 508
  • Next »

Web Service - Is JSON supported?

Issue Is JSON supported in a web service environment? Product Line EcoStruxure Building Operation Environment Web Services JSON StruxureWare Building Operation Cause Many third party application only communicate JSON. Resolution JSON is not a supported format in StruxureWare Building Operation as an HTTP response in Generic Consume. Only Simple XML Web Service and SOAP Web Service are supported. It must be an XML document. There is a tool developed on the Community to automatically convert the JSON response from a Web Service to XML, and though it is not officially supported by PSS, it has proven to be a valid work around. Refer to SBO - Web Service through a Proxy, JSON and Image conversion.
View full article
Picard Product_Support
‎2018-09-11 04:27 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 04:03 AM

Labels:
  • EcoStruxure Building Operation
5133 Views

Can two card readers be wired to one card reader input?

Issue Will there be any problems wiring two HID iClass RP40 readers to one reader channel?  Environment ACX57xx, AC-1 Cause Need two readers on a vehicle entrance at different heights Resolution Tested (2) HID RK40 (iClass with keypad). The RP40 uses less power but should be very similar. Not recommended to power the two readers from the same reader input unless you are sure the reader input can handle the combined peak mA rating of the two readers. ACX5720 - worked fine. The RK40s were powered with different reader channels and then just doubled up the 1-DATA, 0-CLK and LED1 terminals on the ACX with the DATA1, DATA0 and Green LED leads from the readers. AC1 - worked fine. The AC-1 terminals are small so a single piece of wire was used off the DATA/1, CLK/0, and LED terminals of the AC-1 and landed on a terminal block with DATA1, DATA0 and Green LED leads from the readers. The RK40s were powered with an external power supply.  
View full article
Picard Product_Support
‎2018-09-06 10:35 AM

Labels:
  • Andover Continuum
2124 Views

How to transfer a XBuilder project to a different type of Xenta Server

Issue Prior to XBuilder 5.1.1, it was not possible to change the type of an Xenta Server in an XBuilder project once it had been created.  Sometimes there is a need to move the project to a different type of Xenta Server without losing all the links and bindings within the project. Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In XBuilder 5.1.0 or earlier, it is not possible to edit the Xenta Server type in the network pane of the XBuilder project Resolution Upgrading to Vista/XBuilder 5.1.1 or later will allow you to easily change the device type directly from XBuilder.  Note that this must be done from an XBuilder project that is saved to the computer. If the project is in a Vista database start by opening the XBuilder project, clicking on File > Save as and then save it to the computer. Then, close XBuilder, reopen XBuilder and open up the saved copy of the XBuilder project from the PC. In the XBuilder Project menu select 'Change Target type...'.  Choose your preferred target device from the drop-down list.   If it is not possible to upgrade, the following instructions allow an XBuilder project to be transferred to a different type of Xenta Server without losing graphic bindings or bindings between objects on the System pane and the Network pane.  The one proviso is that the target Xenta Server's hardware must be able to support any network defined in the source project and have the same or better Menta and User graphic capabilities.   There are many different combinations of Server types and BMS platforms that these instructions could apply to in general.   The example given here transfers an Xenta 555 project to an Xenta 731.  The Xenta 555 has a Lonworks network and a Modbus network and is part of a Vista database.   Creating the Xenta 731 in the Vista database: Open the Vista database containing the Xenta 555 project. Right-click on the 555 and select Edit from the dropdown menu. The XBuilder project opens.  Keep this open for the following steps. In the Vista database create a new Xenta 731.  The name is not important but it should be similar but not identical to the 555 it will replace. Transferring the Lonworks network to the Xenta 731: In Vista, drag and drop the LON network from the 555 to the 731. Right-click on the 731 and select Edit from the dropdown menu. The 731 project opens in a new instance of XBuilder.  Rename the default folder in the system pane to the same name as the top level folder in the 555 project. In the 731 project right-click on the LON object in the Network pane.  Select 'Refresh network from TAC Vista'. Transferring the Modbus network to the Xenta 731: In the 555 project, right-click a Modbus device and select 'Edit Device template' When the device editor opens, select File | Save as.. Save the file in the default location with the default name. Repeat steps 2 to 3 for all Modbus devices in the network. In the 731 project recreate the Modbus network using the templates just saved.     Transferring the System objects to the Xenta 731: In the 555 project, right-click an object below the top level folder and select 'Copy'. Move focus to the 731 project, right-click on the top level folder and select 'Paste'. Repeat steps 1 and 2 for each object and folder below the top level in the 555 project.  Selecting a folder also selects all the objects and folders beneath it.  Although it is possible to copy the top level folder in the 555 project, it is not possible to paste it into the 731 project. Graphics bindings are retained and the reference paths are automatically updated with the new network tree i.e. 'TAC_Xenta_555' is replaced with 'TAC_Xenta_731'. Some object bindings will be broken e.g. Time objects.  These must be rebound manually. When all objects have been copied across and rebound if necessary, close the 555 project. Deleting the Xenta 555 and downloading the project to the Xenta 731: In the Vista database, delete the Xenta 555. Generate the 731 project.  There will be a warning message offering to copy the original TGML files to the new default location.  Select 'Yes'. The 731 project should now generate without errors. Download the project to the Xenta 731.   If the 555 only contains a Modbus network, a similar methodology will also work with standalone 555 and 731 projects.  
View full article
Picard Product_Support
‎2018-09-06 10:35 AM

Labels:
  • Satchwell BAS & Sigma
  • Satchwell MicroNet
  • TAC INET
  • TAC Vista
2121 Views

WorkPlace Commissioning Tool Windows 7: "A critical error occurred in the communication server rtmonitor.exe"

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  
View full article
Picard Product_Support
‎2018-09-11 05:58 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 06:56 PM

Labels:
  • TAC IA Series
3709 Views

Do NOT use Backup and Restore to duplicate Automation Server databases! (1.5 and below).

Issue It has come to our attention that people are using Backup and Restore to duplicate Automation Server databases, this is not supported and should not be used as it results in various issues.  Some of the known issues at this time are listed below: When attempting to update Server IP addresses using the advanced feature "Repair server communication"; one or more Automation Servers are listed as Offline even though they are shown as Online within the System Tree. (Click on image for larger view)   When performing a backup / restore from the Enterprise Server the Automation Server(s) are not listed as part of the Child view.    Right-clicking on the Automation Server does not give all the options available and most are grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server 1.2, 1.3, 1.4 and 1.5 Cause This situation arises because each Automation Server receives a unique identifier, global unique identifier (GUID), when using the backup and restore function this GUID is retained.  Therefore when restored to other Automation Servers these will retain the same identifier.  The only course of action available within this environment is to detach the Automation Server from the Enterprise Server and create a new database from scratch. The correct duplication process across Automation Servers is to use the export and import feature or copy and paste (drag and drop) across Automation Servers.   Resolution StruxureWare Building Operation 1.6 and above update:   You can now use the Restore function to re-use the configuration data from a backup set in a new standalone Automation Server. Rather than manually configuring your preferred Automation Server configuration, you can save time and configure the standalone Automation Server from a backup set. Online help topic: Duplicating an Automation Server Using Restore Backup and Restore feature should NOT be used to duplicate multiple Automation Server's databases it should only be backed up and restored to the same server.  Instead the Export / Import and copy and past features are designed for this function.   A warning note in the Technical Reference and IT Reference guides (versions 1.2, 1.3, & 1.4) has been added warning the users not to use the backup and restore function for duplication.  See the online StruxureWare WebHelp for this current Important Note (login required): Backup and Restore Overview However if you have this situation then it may be possible to recover some or most of the database, please contact Product Support and reference this article number so that this issue can be confirmed.  
View full article
Picard Product_Support
‎2018-09-11 06:04 AM

Last Updated: Kirk Mahmoud_Sayed Kirk ‎2022-08-21 05:36 AM

Labels:
  • EcoStruxure Building Operation
2559 Views

Computer hardware requirements for Continuum Cyberstation

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.  
View full article
Picard Product_Support
‎2018-09-11 12:59 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 06:11 PM

Labels:
  • Andover Continuum
3675 Views

Menta module names disappear when importing a Menta file.

Issue Menta module names disappear when exporting a Xenta from Vista version 5.1.8 and importing it to Vista version 5.1.7  Environment TAC Vista 5.1.7 and 5.1.8 Cause Changes is made in the export/import function in TAC Vista 5.1.8 which will cause problems to import a export file from TAC Vista 5.1.8  in to TAC Vista 5.1.7. Resolution To be sure that the export/import function should work only export and import between Vista systems of the same version. 
View full article
Picard Product_Support
‎2018-09-06 10:34 AM

Labels:
  • TAC Vista
1363 Views

Diagnosing Trends that are Storing Excessive Data

Issue Diagnosis of a full Vista database shows that trend log storage size the culprit. Environment Vista trend logs SQL database Cause Excessive trend logging can quickly fill a database. Resolution This search will show both Xenta trend logs declared in Workstation/Menta and Vista Server logs. Search for ‘Type of devices or objects: Logical objects – Files – Trend Logs – Trend Log Vista’ Set Property Value – Status – Equal to ‘On’ Deselect the ‘interrupt if more than 1000 results’ if large Db with need for many logs. Once search populates right click on any result, Additional Property Value – Log space. This will add a column showing this setting in seconds.  Sort column to identify any trends that are set to store more than the desired amount of values and could be causing issues.  Note: 604800 sec = 1 week
View full article
Picard Product_Support
‎2018-09-06 10:32 AM

Labels:
  • TAC Vista
1007 Views

"BACnet" Extended Trend Logs

Issue Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause When configuring extended logging in the BACnet application folder, these objects are not available when performing a device discovery from the AS or ES. Prepare one AS with a BACnet point Create a trend log on the BACnet point Create an Extended log for that BACnet trend log From a second AS, the BACnet objects are available after a Device Discovery except for the Extended log object. StruxureWare Building Operation online help for “Configuring Extended Logging for a BACnet Trend Log” states:    ***Key Concept: Extended trend logs are not BACnet objects. These are StruxureWare Building Operation exclusive. The term "BACnet Extended Trend Log" does not exist and is a misnomer. Resolution The main reason is that extended logs are not defined in the BACnet standard; they are proprietary to EcoStruxure.  Everything that is proprietary to EcoStruxure Building Operation is not exposed to BACnet including graphics, script & function block programs and central IO points are not directly exposed, but have to be bound to BACnet I/O objects. The extended log serves the purpose of expanding a log on a larger capacity server.  A trend log on an AS would be more appropriate to extend on an ES. If you have a trend log in an external BACnet device (like a b3 or a 3rd party device/system) then you would want an extended log in the AS, to collect from that device (and then maybe a larger extended trend on a parent ES). If there is a local BACnet trend log in an AS (in the BACnet interface application folder) that is required to be larger, consider increasing the buffer size property of the one log that is needed (the default size of 10 may be too small, and increasing to 1000 up to 5000 (extended log size) may be an option). That would be most interoperable with other (3rd party) BACnet clients that need access to the trend log data.
View full article
Picard Product_Support
‎2018-09-11 01:20 AM

Labels:
  • EcoStruxure Building Operation
3470 Views

Clarification on how to wire Form A and Form K Triac outputs on i2/b3 865/866-V controllers.

Issue Clarification on how to wire Form A and Form K Triac outputs on i285-V / b3865-V controllers. Environment i2865-V b3865-V i2866-V b3866-V i2865-V-S b3865-V-S i2866-V-S b3866-V-S Cause Had issues in the past with blown Triac outputs due to wiring, need to confirm how they are properly wired for Form A and Form K Triac outputs. Resolution As per 30-3001-810 i2 b3 865-866 Controller Installation Instructions (see page 5), you can configure your Triac so they switch the 24VAC (hot) or the GND (ground), but all Triac outputs must be configured the same. The difference between the Form A and the Form K is that the Form A is two digital outputs using a single triac each while the Form K is a single tristate output using both physical triacs for the one (logical) output. The Form A Triac outputs can be configured as either a hot or ground switch but the Form K must be configured as a ground switch (TRIAC REF tied to GND, Load to 24VAC).
View full article
Picard Product_Support
‎2018-09-11 05:59 AM

Labels:
  • Andover Continuum
2280 Views

Updating firmware and software on a RoamIO2 and Service Tool Guides

Issue At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.  
View full article
Picard Product_Support
‎2018-09-11 02:10 AM

Last Updated: Sisko GavinHe Sisko ‎2023-09-21 02:25 AM

Labels:
  • Andover Continuum
3207 Views

Integrating Windows Active Directory user accounts with EcoStruxure

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. NOTE: It is best to only use the Domain (Netbios) name (as shown above) when adding the Windows Domain name to this property.  Using the full DNS Domain name, for example, eur.gad.schneider-electric.com will cause issues when utilizing other features that require active directory authentication.  One example where this has been identified is with Change Control.   Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials. When logged on to the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. Must use HTTPS. Must enter your Windows username and password. Must enter the domain as the Windows domain as defined within Building Operation.  See below: An example log-on format is shown below when using the above configuration when using WebStation:    Alternatively, if the following is configured in Building Operation: WebStation log-on will look as follows:  Download a TVDA for Single Sign-On Instructions
View full article
Picard Product_Support
‎2020-11-04 03:42 PM

Last Updated: Guinan RobertAndriolo Guinan ‎2021-10-11 04:49 PM

Labels:
  • EcoStruxure Building Operation
18626 Views

Report can not be displayed - The request failed with HTTP status 503: Service Unavailable

Issue When trying to open a report, you get an error message like below: Msg=DDL creation failed ex=Error creating DropDownddlTopCount The request failed with HTTP status 503: Service Unavailable Ex=ButtonRunReport The request failed with HTTP status 503: Service Unavailable   Product Line EcoStruxure Building Operation Environment Reports server Cause Cause 1: The Report Server Service is not started To check if this is the cause, open the report manager. If you get the error below, continue to resolution 1.   Cause 2: The Report Server Service takes too long to generate the report and thus times out The root cause should also be investigated. It can be a slow network connection, fragmented SQL database, antivirus software or memory limitation that is slowing the request to compile a report down. Resolution Resolution 1 Open "Reporting Services Configuration Manager" Start the server   Resolution 2 Increase the timeout for the report service Open Report Manager Click "Site Settings" Change the Report Timeout. Default is 1800 which is 30 seconds.   Check that the memory usage for the SQL server is not limited (Microsoft's How to: Set a Fixed Amount of Memory (SQL Server Management Studio)) Open SQL Management Studio Open the properties for the SQL Server Click "Memory" and check that the value is default (2147483647)   Reindex and defragment the SQL database e.g. using SBO Reports Agent Config.
View full article
Picard Product_Support
‎2018-09-11 03:45 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 03:57 AM

Labels:
  • EcoStruxure Building Operation
5406 Views

Display uptime of Automation Server

Issue How long has an Automation Server been running since the last power cycle or reboot? Environment Automation Server SmartStruxure Device Administrator Cause The uptime of an Automation Server indicates how long the server has been operational since the last power cycle or system reboot. This is not currently visible in the StruxureWare Building Operation Workstation, but it is available through the Console interface in Building Operation Device Administrator. By monitoring the uptime of the device this can be a valuable diagnostic tool to determine if power loss occurred, crashes in Automation Server occurred, or other situations that might have resulted in a reboot and what time this occurred. Resolution In the Building Operation Device Administrator connect to an Automation Server (IP or USB) and select the "Open Console" option. Once logged into the Console issue the "uptime" command in the prompt. The uptime will be listed in Days, Hours, and Minutes as visible below: admin@AS-B-RKFDMW:~> uptime  14:18:20 up 1 day,  1:01, load average: 1.26, 1.16, 1.06   If you are using Report Server, this information is also available using SQL Server Management Studio from the Report Server PC. Enter the following query and the "Runtime" column will provide the current uptime for the specified ES or AS. SELECT Top (1) CAST(CURRENT_TIMESTAMP - DateTimeStamp AS Time) AS 'Runtime' ,DateDiff(Day, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Days Up' ,DateDiff(HOUR, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Hours Up' ,DateDiff(MINUTE, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Minutes Up' ,DateDiff(SECOND, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Seconds Up' ,[DateTimeStamp] ,[TYPE] ,[OriginatedServer] ,[OriginatedDevice] ,[SystemEventId] FROM [StruxureWareReportsDB].[dbo].[tbEvents] WHERE SystemEventId = 'Server initialized' AND OriginatedServer = '/Server 1' ORDER BY DateTimeStamp Desc   NOTE: Change the WHERE statement "OriginatedServer = '/Server 1'" so that '/Server 1' become '/yourServerName'
View full article
Picard Product_Support
‎2018-09-06 10:27 AM

Labels:
  • EcoStruxure Building Operation
1521 Views

Continuum version support for the CX9680/NC2 and the Conversion procedure from an NC1(99xx)

Issue Which Continuum versions support an NC2(9680)? Procedure for replacing a CX99xx with a CX9680 Product Line Andover Continuum Environment CX9940 CX9900 NetController 2 NCII CX9680 Cause Netcontroller II (CX9680) is supported in Continuum versions 1.80 and higher Resolution Upgrade the site to Continuum 1.80 or higher for NC2 support   Procedure for converting an NetController1 (NC1/99xx) to a NetcontrollerII (NC2/9680) To convert a NetController to a NetController II, perform the following steps:   Back up your SQL Server database. See the Andover Continuum CyberStation Installation Guide, 30- 3001-720, and Microsoft® SQL server documentation. From the Continuum Explorer, use the right-click popup menu for this controller, and select Send to Text File. This drops the controller object’s data into a text file. For various ways to customize this operation, whereby you can save the controller’s child objects, please see the Send to Database Options in the CyberStation online help. Update your workstation with a version of CyberStation that supports the newer NetController models. These models are supported by CyberStation Version 1.8 and higher. Physically remove the old NetController, and mount/connect your NetController II. When you configure and commission the NetController II, use the same controller name, network IP address, and network ID. This is performed via the controller’s embedded web commissioning pages and via the General tab and the Network tab of the CyberStation’s Infinity Controller editor. Switch to CyberStation offline editing mode in the InfinityController editor. On the General tab, from the Controller Type dropdown menu, change the model number to 9680 or 9681, depending on which NetController II you are installing. Make sure you actually want to replace the NetController. When you attempt to change the controller model, Cyberstation displays a few warning messages: Cyberstation warns that a model change is irreversible. Cyberstation warns that, if an XDriver is used with this controller, not all XDrivers are supported by the new model. If you proceed, the XDriver links are left in place regardless of the availability of a replacement Xdriver. XDrivers on NetController II — In general, Xdrivers that are available on the bCX1 model 9640 are also supported on the NetController II. For example, supported NetController II XDrivers include, but are not limited to, the following: Filter XdTest Modbus TCP Modbus RTU XDrivers built for the previous-generation NetControllers will not run on the NetController II. What is an XDriver? An XDriver is special, customized software that your site purchases separately from TAC. The XDriver software allows your controller to connect to and communicate with a special piece of third-party equipment needed at your site. In the CyberStation CommPort editor, you must configure a controller comm port for this special device that the XDriver software enables. * When you leave the InfintyController editor, go back to online editing mode. If necessary, provide an updated XDriver file compatible with your NetController II. CyberStation prompts you to do this. Note: You can specify an XDriver on the General tab of the CommPort editor. Specify XDriver for the Default Mode, and use the browse button in the XDriver File Name field to search for and specify the path of the XDriver. Determine whether this NetController II has network security. If so, configure network security for this controller. Note: Network Security is supported only in NetController II model 9680, as well as ACX controllers 5720 and 5740. Restore (reload) data from your database into the new controller. From CyberStation’s Continuum Explorer, use the Object dropdown menu or right-click the object popup menu for this controller object, and select Send to Controller. Back up to flash. In Continuum Explorer, right-click over this controller, and from the container popup menu, select Backup to Flash. This saves the controller’s RAM configuration to its flash memory, in accordance with the attribute value that is set for the ACCRestartMode system variable.
View full article
Picard Product_Support
‎2018-09-06 10:27 AM

Last Updated: Administrator CraigEl Administrator ‎2022-11-06 04:05 PM

Labels:
  • Andover Continuum
2585 Views

How to Export a Trend Log List as a .csv File

Issue Need to Export a Trend log file without using Reports Server Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation Cause Customer needs a log file, but does not have Report Server Resolution In Workstation, right click on a Trend and create a new Trend Log List View Once the List populates, click on the Icon showing a green arrow labeled .csv Save the file to an appropriate location. If this is a frequent action, save the Trend Log List View Please Note that this feature is not available in WebStation  At v2.0 WebStation introduced the option to export to Excel, creating an XLSX file, this can be opened in Excel and saved as a CSV if required (this option is not available if WebStation is directly logged on to the AS/P/B)
View full article
Picard Product_Support
‎2018-09-06 10:27 AM

Labels:
  • EcoStruxure Building Operation
3769 Views

SE7300 series BACnet controller does not come online in StruxureWare Building Operation

Issue SE7300 series BACnet controller does not come online in StruxureWare Building Operation if the communications address is greater then 127. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment StruxureWare Building Operation BACnet Cause The communications Address of SE7300 series BACnet controller can be set between 0 to 254. In StruxureWare Building Operation the highest address can be set only up to 127. Resolution Set the communication address less than or equal to 127 for SE7300 series BACnet controllers. Please refer to the Default Device ID / Device Instance of SE7000 series BACnet controllers to know the default Device ID / Device Instance of SE7000 series BACnet controllers.
View full article
Picard Product_Support
‎2018-09-11 03:49 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-09 05:36 AM

Labels:
  • EcoStruxure Building Expert
  • EcoStruxure Building Operation
  • Field Devices
2209 Views

Send SMS with EcoStruxure Building Operation

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.
View full article
Picard Product_Support
‎2018-09-11 03:50 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 03:41 AM

Labels:
  • EcoStruxure Building Operation
6268 Views

Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)?

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.
View full article
Picard Product_Support
‎2018-09-11 04:25 AM

Last Updated: Sisko GavinHe Sisko ‎2023-03-27 03:38 AM

Labels:
  • Andover Continuum
1736 Views

AS supports network authentication via Radius Server (IEEE 802.1X)

Issue Does the Automation Server support network authentication via Radius Server (IEEE 802.1X)? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause AS supports network authentication via Radius Server (IEEE 802.1X)? Resolution RADIUS and IEEE 802.1X are not the same thing, although they can be used together. Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport.   The RADIUS server is usually a background process running on a UNIX or Microsoft Windows server. RADIUS serves three functions: to authenticate users or devices before granting them access to a network, to authorize those users or devices for certain network services and to account for usage of those services.  IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. It is a mechanism used in (mostly) switches and wireless access-points to allow or block devices to access the network (or granularly allow access to parts of it).   For example, if you have a network port in a meeting room, you can enable 802.1x on the switch port and configure it in such a way that when an employee connects they have access to the entire network, but if a guest connects (with a temporary password) they can only reach the Internet and if a passer-by is tempted to try his luck, they cannot access anything at all. Does IEEE 802.1X also use RADIUS as it's underlying authentication mechanism? Yes and no. IEEE 802.1x uses Extensible Authentication Protocol (EAP), the drawing below shows that for wired 802.1x: EAP over LAN (EAPoL) is used between the Supplicant (software on a computer) and the Authenticator (switch). EAP is then usually tunneled over Radius between the Authenticator and the Authentication Server, but it can also be done over Diameter (the successor to Radius). For wireless, it is similar in the sense that there is also no Radius between the supplicant and the authenticator, only between the authenticator and the Authentication Server (to tunnel the EAP). From EBO 2022 the AS-P and AS-B can be configured as supplicants on a network protected by IEEE 802.1X security. See the IEEE 802.1X Security Webhelp topic for further details.   Note: MPx/RPx do not support 802.1x network authentication, see the SpaceLogic controllers MPx/RPx do not support 802.1x network authentication Knowledge Base article  for further details.    
View full article
Picard Product_Support
‎2018-09-06 10:26 AM

Last Updated: Administrator CraigEl Administrator ‎2023-06-07 07:29 PM

Labels:
  • EcoStruxure Building Operation
2674 Views
  • « Previous
    • 1
    • …
    • 40
    • 41
    • 42
    • …
    • 508
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of