Building Automation Knowledge Base

Issue SmartConnector 2.5 uses the Flexera licensing model. Version 2.4 and below used native licensing. How can the existing license be upgraded for SmartConnector 2.5? Product Line EcoStruxure Building Operation, Flexera Environment Building Operation Enterprise Server Flexera FlexNet Operations Cause SmartConnector 2.5 uses the Flexera licensing model. That means you will license SmartConnector using the License Administrator interface. Prior to version 2.5, SmartConnector licensing used a native licensing model.   Resolution SmartConnector 2.5 will still support the native licensing structure that we have for SmartConnector today for its core license. The way this works is as follows...   There are two parts to SmartConnector licensing.  There is the core, or runtime license which is used to license the web portal and the windows service. There is a second part that licenses the integrations and SmartConnector extensions.  These are licensed separately. When installing SmartConnector for the first time at version 2.5 a single comprehensive license (incorporating the core and integrations licenses) is purchased.  This license is applied using the License Administrator application.   In cases where SmartConnector is being upgraded from a pre-2.5 version, the core license will remain installed as a native license. Your integrations license upgrade would be installed using License Administrator.   Obviously, with SmartConnector you could run lots of different extensions on the same machine. You would still only have one SmartConnector core license but you would license your extensions individually. So you could have many integration licenses running on the Flexera server, while your core license remains in place.

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 When adding an Enterprise Server (ES) to Enterprise Central (EC), the process fails with Error - Object Does not exist Domain: Data Access. Details: Modules: Connect Plugin Module Code 73 Trace log shows the following text: nsp.csc.csm.ChangeSetTransaction Rollback due to Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.AddServerCommandPassThrough Execute: Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.ConnectionPool Terminating. GetConnection aborted [IP Address: port#] Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central  Building Operation Enterprise Server  Registered System Cause In this instance, the ES added to the EC is currently registered.  Registered Servers can only be the parent server and therefore cannot be added to a non-registered system or a different system.  Parent servers can only be registered, and any sub-servers inherit this registration from the Parent sever.    Resolution The registration should always be on the parent server. To remove the registration from the ES, the SystemID needs resetting as per the following procedure:  Resetting the System ID Once reset, the system is no longer registered, and adding the ES to the EC will be successful. 

Issue SP-RDM2 Reader Expanders running firmware 1.12.544 appear to fail whenever an attempt is made to update their firmware revision. Product Line Security Expert Environment SP-RDM2 SP-MRDM2 Cause There is a known defect in 1.12.544 (Build .544) which prevents the SP-RDM from being upgraded or even downgraded. However, a number of SP-RDM units have been shipped from the factory with this build pre-installed. Any attempt to select an SP-RDM running this firmware and upgrade or downgrade it to a different revision will consistently fail with an error: 'Module not responding'. There is also a possibility that the SP-RDM can be permanently disabled in the process Resolution Since the .544 Build defect cannot be resolved the only recourse at this time is to swap out the unit via the Returns Material Advice (RMA) process for a new unit.      List of SP-RDM2 Serial #s affected thus far: Note: All other SP-RDMs running firmware both above and below .544 Build are unaffected

Issue A method is require to provide an Executive Privilege function to a Door to allow tailored credential requirements for specific Users. Product Line Security Expert Environment Security Expert Cause Doors are currently set up for two credentials (Card + Biometric) but there is a need to allow certain Users access through those Doors without having to present the second credential. Resolution The Access Level Door Type feature allows for this functionality. The option overrides the Door's Door Type with the one set in the Access Level (e.g. to allow a VIP to override 'Card + Biometric' to just 'Card' at a door). Required Objects Door Type Access Level User Configuration In the Door Type set the Access Level Door Type to the door type you wish to use whenever Access Level Door Type is enabled - in this example it would be "Card". Fig.1 - Door Type In the Access Level enable the Use Access Level Door Type option. Fig. 2 - Access Level Assign the Access Level in step 2 to your User. Fig. 3 - UserFor a Video KB article showing a similar configuration process see:  Security Expert user specific access vs standard door access 

Issue What actuator can be used as a replacement for the MF-63123? MF-631x3 Series_F_24732_8.pdf (209 KB) MFC 8000_F_25124_4.pdf (260 KB) Product Line Field Devices Environment MF-63123 Cause Original actuator has failed, or requirement for a non US actuator. Resolution Using the installed valve details, the actuator can be selected from the Schneider Electric Valve and Actuator selection Tool.

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue What SQL collation is supported by CyberStation Product Line Andover Continuum Environment CyberStation SQL Server Cause Which SQL collations are supported by CyberStation. Resolution Only the SQL_1xCompat_CP850_CI_AS collation has been tested with CyberStation. Note: In more recent versions of SQL server (i.e 2005), you can have the Collation on a per-database basis so ContinuumDB will have its collation set to SQL_1xCompat_CP850_CI_AS and another database can use a different collation setting. Also when the continuum database is restored it will retain the original collation that it was created with.

Issue CyberStation is unable to connect to the database. ODBC test also fails when testing the connection to the database. Product Line Andover Continuum Environment CyberStation SQL server SQL management studio Cause SQL server not on UPS. Server shut down due to a power failure. Looking at the ContinuumDB using the SQL Management Studio shows the database has been marked as suspect.  ContinuumDB (SUSPECT) The database may be marked suspect for the following reasons System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System (as mentioned above) Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Resolution The database may have been damaged by the ungracious shutdown. The restore option is grayed out and must first be re-enabled before a restore operation can be allowed. How to recover a database in suspect mode Clear the suspect mode of the database using sp_resetstatus DatabaseName. This will clear the suspect flag and make the database available online. The SQL Server must be stopped and re-started. Change the database status to Emergency using the following command. ALTER DATABASE DatabaseName SET EMERGENCY; Restrict database to single user by changing the access mode as mentioned below ALTER DATABASE DatabaseName SET SINGLE_USER; If the restore option is now enabled skip step 4 Run the CHECKDB command with “REPAIR_ALLOW_DATA_LOSS” option. This option should be tried as the last option as it always behaves the way it is named. We are not sure of what data it removes. DBCC CHECKDB (DatabaseName, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS If the repair operation is successful the database is now usable but if a recent backup is available it is strongly recommended to restore the database. Restore the most recent backup of the Continuum database. Set the ContinuumDB owner using the query SP_ChangeDBOwner 'Andover97'  

Issue A b3 controller that is shown as offline in CyberStation can incorrectly change to online when RoamIO2 is connected to the bus.   Product Line Andover Continuum Environment RoamIO2 bCX CyberStation b3 Cause When a RoamIO2 is connected to the MSTP bus and the BACnet Service Tool software is started, it assigns itself a BACnet MAC Address. It may assign itself the BACnet MAC Address of an offline b3. If at the same time you are running a listview of b3 controllers on that bus in CyberStation, and displaying commstatus, the offline b3 with that BACnet MAC address will appear online. However, attributes such as VersionNum, BACnet DeviceID, Port, and InstanceID will be blank in the listview - tipping you off that this is bogus.   Resolution Be aware of this situation and add the attributes described in the cause section above to confirm what you are seeing.  

Issue Receive an Error message "Outlook not installed"  when starting  Continuum Product Line Andover Continuum Environment Windows 7,  64Bit Continuum  1.9X Microsoft Outlook  64 Bit. Cause Outlook 64 Bit is not supported at this time. Resolution Uninstall 64-bit Outlook.  Then install 32-bit Outlook.

Issue The SQL Server 2008 is running the 64-bit version as well as the Continuum Workstations are using 64-bit Operating Systems. In the interest of increasing the SQL access speeds can the ODBC connection between them also utilize the 64-bit ODBC driver? Product Line Andover Continuum Environment Continuum v1.94 (or greater) Microsoft SQL Server 2008 64-bit Microsoft SQL Server 2012 64-bit Microsoft SQL Server 2014 64-bit Microsoft SQL Server 2016 64-bit Cause Want to know if the SQL access speeds can be increased by taking advantage of using the 64-bit ODBC drivers. Resolution The Continuum application itself is a 32-bit application, this will require the 32-bit ODBC drivers to make a connection to the SQL Server. Even though we support Continuum in a 64-bit environment, it is still only a 32-bit application so the 32-bit ODBC drivers are used for the SQL connection. Be aware that this is just the communications on the SQL side, the SQL application itself will still process data at 64-bit speeds if the 64-bit version is used.

Issue What are the email addresses used for I/A Series license requests? Product Line TAC IA Series Environment I/A series license Cause Request license to upgrade existing devices. Resolution All TIP and end customer WorkPlace Tech license requests and Niagara license requests are emailed to: bms.licensing@se.com

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 VTR Valve Body requires replacement due to obsolescence. Product Line Field Devices Environment VTR VTRE MB MBF Cause Obsolescence of VTR Valve Body. Resolution VTR Valve Bodies are obsolete and have been for many years.  VTR Valve Bodies were available with either Flanged or Screwed connections.   REPLACEMENT OF VTR FLANGED CONNECTION VALVE BODY  A replacement for the VTR Flanged Valve Body (20-150mm only) may be selected from the VTRE range of flanged valve bodies, N.B. It should be noted that the VTRE Valve Body is rated PN6 whereas the VTR was rated PN10. The VTRE Flanged Valve Body may be operated by the EM9 Actuator. Alternatively the VTRE Flanged Valve Body may be operated by the M9B actuator. No Linkage Kit is required to mount the EM9 or M9B Actuator on the VTRE Flanged Valve Body. Alternatively a replacement for the VTR Flanged Valve Body (65-100mm only) may be selected from the MBF range of Flanged Valve Bodies. N.B. It should be noted that the MBF Valve Body is rated PN6 whereas the VTR was rated PN10. The MBF Flanged Valve Body may be operated by the MD20B series actuator. Alternatively the MBF Flanged Valve Body may be operated by the MD20A actuator. A Linkage Kit (914-1070-000) will also be required.   REPLACEMENT OF VTR SCREWED CONNECTION VALVE BODY  A replacement for the VTR Screwed Valve Body (15-50mm) may be selected from the MB range of screwed valve bodies. The MB Screwed Valve Body may be operated by the MD10B series actuator. Alternatively the MB Screwed Valve Body may be operated by the MD10A actuator. A Linkage Kit (914-1071-000) will also be required.   The datasheets concerning all the above options are available for download.

  Issue Using active directory with Change Control  feature does not authenticate when signing  Product Line EcoStruxure Building Operation Environment Building Operation release 3.1 and above Building Operation Enterprise Central  Building Operation Enterprise Server Building Operation SmartX Controllers Cause The interaction of Active Directory and Change Control is not clearly defined in the documentation when both are in use.  Although Active Directory within Building Operation Domains can use both the Fully Qualified Domain Name (FQDN) and Netbios Windows Domain names it is recommended that only the Netbios Domain name be used if Change Control is implemented. Refer to EBO Known Issues & Solution topic  Change Control and Windows Active Directory not authenticating - Communities (se.com)  for updates.   Resolution When using Active Directory with Change Control only add the Windows Netbios name to the Building Operation Windows domain name entry:   Using the Full DNS Domain Name (examples include - apa.gad.schneider-electric.com ; pss.apa.local etc.) although these will allow user accounts to log on to servers it currently does not work when used to authenticate change control.    The easiest way to identify which domain name to use is to open WorkStation and refer to the name shown next to:  Log on as:    Secondly when authenticating change control actions with active directory user accounts, irrespective of the Default Building Operation Domain selected, the user account name must be prefixed with the Windows Domain Name 

Issue Various changes to the PC operating system can alter the IA Series software host ID causing the license to be invalid. When this occurs the window below will be displayed providing the new Host ID read from the PC. Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Workbench I/A Series SoftJace platforms    Cause Upgrading the Operating System (Windows, Linux, etc.) always changes the Host ID.  Making other changes to a Niagara host platform may also change the Host ID.  These are the types of changes that can alter the Host ID: upgrading from Windows 7 to Windows 8 upgrading from Windows 8.0 to Windows 8.1 upgrading from Windows 7 or 8 to Windows 10 installing the 2 August 2016 anniversary update to Windows 10 upgrading from RHEL5 to RHEL6 Upgrade from RHEL6 to RHEL7 will change your Host ID. Installing certain Microsoft Windows updates (patches/fixes) may also cause the Host ID to change. Resolution Email the hostID from the current license or a copy of the current license as well as the new hostID provided in the "Request License window" to Schneider Electric Customer Care (Email Information) and request a license replacement.

  Issue TAC Xenta devices suddenly indicate that they Needs commissioning. Product Line EcoStruxure Building Operation. Environment • Building Operation Workstation • Xenta 401 • Xenta 301 • Xenta 281 Cause The flag "Needs commissioning" is suddenly set.     Resolution If the property "Needs commissioning" is set, something has changed in the settings. This could be Subnet/Node address in the Domain table, or a change in any LonWorks binding, that caused a change in the Selector, Address, and or Alias tables.   The property Needs commissioning may also be set after a TAC Vista upgrade (conversion) or similar situations.  

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

Issue After a Sigma transition into EBO, alarm clears are requiring acknowledgements. In the Sigma Interface, the object alarm and hardware alarm 'Type of Acknowledgement are set to 'Extended' and cannot be changed to 'Single' Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Clear Controls are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm clear acknowledgement type is set to a specific type. If acknowledgement on alarm clears is no longer required in EBO then it will need to be changed on the Sigma server,   To change to 'Single' so that alarms only are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Alarm Controls.   Uncheck the 'Alarm Clears Acknowledgeable' box.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'No', then the KB article Type of Acknowledgement set to 'No' on Sigma Interface object alarm will explain how to change this.