Building Automation Knowledge Base

Issue Security Expert Smart Connector integration is working but Alarms states are not updating, the following error is appearing in Smart Connector logs:   2021-01-07 15:19:22.2621,Info,Processor,<no principal>,Validation Prompt for Security Expert Alarm Update Processor: MayNotContinue : The EwsServer was not located or the credentials you supplied were incorrect. Please verify your credentials and try again. Product Line EcoStruxure Security Expert Environment Smart Connector Cause It appears that the SOAP credential within the Security Expert Discovery Processor does not match the credential within the Security Expert Client SOAP operator credential.   This is a known issue where the credential does not update when changed/edited within the Processor Configuration of the Security Expert Discovery Processor configuration.   Resolution A workaround is to log on to your local Smart Connector portal and edit the credential value within: Setup/Processor Values/SecurityExpertSettings      Change the username and password as required here.                Then save and the new credentials should be updated.  

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

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 ES takes up to 30 minutes to perform a shutdown. Trace log contains multiple entries indicating "Subscription service forcefully shutting down; [sub-server name]"  "Subscription service forcefully shut down; [sub-server name]"   A secondary issue - When performing Windows Updates automatically, Windows attempts to shut down all running services within one minute which can end the Enterprise Server service prematurely Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server 3.1.x and below Large Multi-server installation  Cause During a shutdown procedure of the Enterprise Server a call to every sub server is made to remove subscriptions. However, the thread pool that executes these commands may already be stopped and the server then waits the 15 seconds timeout period prior to moving to the next item.  On a large 100+ multi-server installation, this 15 second delay can accumulate to a lengthy shutdown period.     The trace log will contain the messages shown  in the issue and the 15-second delay between each server  Enterprise Server Trace log messages seen during shutdown showing the 15-second timeout delay. Resolution Upgrading to 3.2.2 (and above) will rectify the timeout issue provided that the subscription thread pool has already stopped.  These versions now ignore the 15-second timeout for each sub-server if the thread pool has already stopped.   It is possible to extend the Windows service shutdown time by adding or adjusting a registry entry called WaitToKillServiceTimeout .   To change the timeout: Start the registry editor (“Regedit”) In the tree on the left, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control In the right panel, find the WaitToKillServiceTimeout value. If you don’t see it, create it by: Selecting Control on the left Choosing Edit > New > String Value (not DWORD) from the menu Naming the new value WaitToKillServiceTimeout. Double-click the WaitToKillServiceTimeout entry to bring up the Edit String window. Enter a numeric value (e.g. 60000) in the Value data field in milliseconds and click OK to save your change. Reboot your computer. The new timeout setting will not take effect until Windows restarts. Note that this modification will not make Windows wait indefinitely for your service to finish. If your service takes longer than the entered time (in this example 60 seconds), it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown time intolerable.

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue Unable to access the SE7xxx Room Controller configuration parameters menu - displays an error code. Product Line EcoStruxure Building Expert, Field Devices  Environment SE7xxx Room controller SE7000 Series Ex. Viconics branding VT7000 Series Cause The display shows an error code when used, this is indicating a password is required, an example of the error code may be 977 or 996. Resolution Contact your region's Customer Care Center for a temporary password. The error code which is unique to that controller will be required by the Customer Care Center to calculate the temporary password. Note for PSS; Check Internal article. 

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Environment SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).   Also see similar KB article - SigmaX reports a missing DLL.

Issue After transitioning an INET security system to Security Expert, SCU1200 and SCU1280 controllers do not come online Product Line Security Expert, TAC INET Environment Security Expert Controller (SP-C) I/NET SCU1200 I/NET SCU1280 Cause The INET-to-Security Expert transition brings each SCU1200/1280 into Security Expert as an Input Expander but there is a known issue that causes the devices to remain offline. R&D is working on a fix. Resolution The workaround for bringing a SCU1200/1280 controller online in Security Expert is to create a Reader Expander and then edit the inputs and outputs associated with the SCU1200/1280 to point to the Reader Expander you’ve just created.   Important:  Create a backup of your Security Expert database before proceeding with the instructions that follow.   For a transitioned SCU1200/1280, create a Reader Expander as follows: In Security Expert, navigate to Expanders > Reader Expanders. Choose a Controller from the drop-down list. Click the Add icon. Define a Name for the expander.  The transition tool would create a name like SCU1200 <703503> for the expander.  In this example, the SCU’s link address is 70, its station address is 35, and its point address is 3. When manually defining the name of the new expander, you may wish to use this naming convention to keep the system uniform. Set the Physical Address of the expander.  This address should be 1 higher than the point address of the SCU.  So, for SCU1200 <703503>, the point address is 3 (703503) and so the physical address of the expander should be set to 4. Set Port 1 Network Type to “Third Party Generic”. Set Port 2 Network Type to “Third Party Generic”. Expand the Commands section and enter the following commands:       PortOne=INET       HardwareType=INET Navigate to the Reader 1/2 tabs and perform the following steps: Set Reader 1/2 Keypad Type to “None”. Uncheck Allow Reading Opened/unlocked. Uncheck Display Card Detail when Invalid. Navigate to the Reader 1/2 Options tabs and perform the following steps: Uncheck Door Sense Enabled. Uncheck REX Enabled. Uncheck Invert REX Input R1/2. Uncheck Always Allow REX R1/2. Save the expander. When presented with the Configure Module wizard, perform the following steps: Set Inputs to 0. Set Outputs to 0. Uncheck Add Trouble Inputs. Uncheck Add Doors. Click Add Now.   Edit the inputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Inputs. For each input associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the input.   Edit the outputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Outputs. For each output associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the output.   When you have finished with all of the steps above, perform a Module Update on the Reader Expander.  Repeat these steps as necessary for other SCU1200/1280 devices.  Once you have verified all SCU1200s/1280s are working properly, you can delete the Input Expanders that were created by the transition tool since they are now unnecessary.

Issue Replacements for Satchwell AY series actuators Product Line Field Devices Environment AY Actuator Cause Obsolescence of AY series actuators from Satchwell Options range Resolution The following pop top actuators can be used to replace the AY actuator series:   AY1201                                              AG13U230 AY1251                                              AG23U230 AY1301                                              AG13A230 AY1351                                              AG23A230   For further Knowledge Base information - Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK.

Issue After installing SigmaX version 5.0 or later, when running the software an error message reports a missing DLL. Product Line Satchwell Sigma Environment SigmaX version 5.0x, 6.0x and 7.0x Cause System Path variable is missing C:\Sigma\Bin in Environment Variables Resolution Make the following modification to the PC's System Properties. Note: This addition is only required on machines running SigmaX.   For Windows XP and Windows 7 Right click the My Computer icon on the desktop and select Properties Choose the Advanced tab and select the Environment Variables button From the System Variables section, highlight Path and select Edit The statement ‘;C:\Sigma\Bin’ must be added to the end of the Variable value line For Windows 10 In the search bar type and type 'environment' and go to 'edit the System Enviroment Variables' Bottom right go to Enviroment Variables In the bottom window 'System variables', find 'Path' and double click In the 'Edit environment variable pane - create a 'New' variable and add in c:\sigma\bin

Issue Error message "The Parameter is incorrect" when clicking OK in TAC Vista Server Setup Emailing alarms from TAC Vista is not working Product Line TAC Vista Environment TAC Vista Server Setup Cause The text encoding method has not been selected. Resolution Open TAC Vista Server Setup Click on the Mail Tab Check if the Text encoding Field is empty. If it is, select an encoding from the dropdown. Unicode (UTF-8) is suggested in the US with an Exchange Mail server.

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue TLS Error seen when attempting to export WebReports data from the displayed report as follows: Unable to download ReportsView.aspx (IP address) Unable to open Internet site, the requested site is not accessible or can not be found  Product Line EcoStruxure Building Operation Environment Building Operation WebReports 3.0.x and above  Internet Explorer (used within WorkStation) and Google Chrome Web Browsers Cause To download files, Internet Explorer must create a cache or temporary file. In Internet Explorer 9 or a later version, if the file is delivered over HTTPS, and any response headers are set to prevent caching, and if the Do not save encrypted pages to disk option is set, a cache file is not created. Therefore, the download fails Resolution See Microsoft documentation on how to correct this.  Typically Method 1 will correct the issue. Cannot download files from secure websites - Browsers | Microsoft Docs

Issue PCT workstation displays message “Server version not compatible with client", when restoring a server configuration with new IDs. Product Line EcoStruxure Building Operation Environment Buildings Operation Project Configuration Tool Cause When backing up and restoring an AS-P/AS-B with a new ID in PCT at EBO 3.2.2.61, when logging back on with PCT using the installed EBO workstation,  the message “Server version not compatible with client" is displayed Resolution PCT is the offline programming tool but, it launches the workstation installed on the computer. If the workstation version on the computer is EBO 3.2.2.61, Hotfix 3.2.2.4002 (CP3) is required to be installed on the computer running PCT, taking the computer’s installed workstation version to 3.2.2.4002.

Issue Clarity is needed on the new ES License Inheritance feature available in EBO 3.x Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Enterprise Central Building Operation SmartX Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in SmartX Servers, such as SNMP Licenses, since EBO 2.x.  The concept of Inheriting Licenses from an ES into a SmartX Server is a new option which can be used from EBO 3.1 onward, although the original Embedded License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   In EBO 3.2 SNMP and TimescaleDB. Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   'Inheritance' means that an ES License will be shared down to its child SmartX Servers while also being retained for use by the ES.   Note: SmartX Servers must be running the minimum supported 3.x version for Inheritance to function There is no such thing as a 'Site License' that can accommodate multiple ES There is no Licenses Inheritance from an EC

Issue When attempting to use the Door Entry Requires Verification option in a Door Type the verification window does not pop up when a User badges at the door. Product Line EcoStruxure Security Expert Environment Security Expert Cause This option requires a Camera record to be assigned to the Door record even if there is no physical camera at the door. Resolution Create a Door Type that has the Door Entry Requires Verification option enabled. Door Type Create a Camera under Monitoring | Setup | Cameras and set the Type to Direct Camera and URL to any value (this needs to be set even if it is not correct). Camera Configuration In your Door set, the Door Type to the new one created earlier and the Camera (Entry) to the camera just created. Door Configuration Operation: Badging a valid User at the Door will create an Entry Verification event (1) that pops the camera window that includes an Unlock Door button (2) allowing the Operator to manually open the Door (3) once visually identifying the User. Operator Verification

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 Unable to view PINs in the User screen if “Allow PIN Duplication” is checked   Product Line EcoStruxure Security Expert Environment Security Expert Server Cause This is viewed as a Site Security Enhancement feature Resolution Disable both the "Require Dual Credential for Keypad Access" and "Allow PIN Duplication" options

Issue When attempting to log in the below network errors, or similar, are displayed. Connect: The server was unable to process the request due to an internal error. Could not log on to Server. Please check your remote connection setup Further checking the Windows Application Event logs on the Server you may also find error messages similar to the below being logged against the Security Expert services. CDTNames::GetTagName : Cannot open database "SecurityExpert" requested by the login. The login failed. Product Line EcoStruxure Security Expert Environment Security Expert MS SQL Cause The Security Expert services do not have the correct credentials to access the SecurityExpert database. Resolution Confirm the user account that the Security Expert services are using in Windows. Go to Start > Run > and type "Services.msc". Confirm the account that those services are being run under. By default, and in the example, this is the Local System account. Run Microsoft SQL Server Management Studio and under your server browse to Security > Logins. Find the user account that your services were used in step 1 In the Server Roles page of this user account. Enable the "sysadmin" server role Save changes and restart the Security Expert services.  

Issue Network scanning software causes a loss of Jace network communication. Product Line TAC IA Series Environment I/A Series Jace 8000 N4.9 and later Cause As network security awareness continues to expand, software-based scanners, such as industry-standard Qualys and Nessus, intended to detect and report on vulnerabilities within internal networks will likely continue to gain popularity.  Today, Tridium is seeing these scanners being deployed and run against Niagara-based platforms like the JACE-8000 and Edge 10.  In some cases, these scans are causing Niagara platforms to become unresponsive or reboot via an Engine Watchdog Timeout, all of which are not acceptable for the critical applications that Niagara facilitates. Resolution While Tridium has no control over how these scanners behave, or how and when they are executed within an organization, Niagara 4.9 introduces a number of changes intended to allow a Niagara-based hardware platform to appropriately respond to the scanning utilities, and also maintain operation.  Below is a brief explanation of how Niagara will function under the different known circumstances currently employed by these scanners, and how to interpret the results.   Recognition of non-Niagara Traffic on the platform In the event a scanner is interrogating a Niagara 4.9+ platform connection, the Niagara Daemon has been modified to recognize non-Niagara traffic over a period of time, shut down the connection if necessary, and wait for a pre-determined amount of time before re-enabling connectivity.  Under these conditions, a scanning utility may report that the Niagara instance has encountered denial of service, when in fact, Niagara has simply disabled the communication mechanism by which the scanner was attempting its interrogation. During this time, normal platform communication will also be affected; however, the Niagara platform and station will continue to run.   Prioritization of Internal vs. External Communication on the Niagara station In the event, a scanner is interrogating a Niagara 4.9+ station (external communication) and Niagara detects that this interrogation may cause an Engine Watchdog Timeout, the station’s web server will be stopped and restarted. Under these conditions, a scanning utility may report that the Niagara instance abruptly stopped communicating, and may have encountered denial of service.  During this time period, normal/expected client web connections to the station will also be affected; however, the Niagara platform and station will continue to run. As mentioned, these scanners are outside the control of Tridium, and likely always evolving to meet the needs of the various threats they are intended to protect against. As a best practice, Tridium recommends not scanning in production if possible, as any findings would be just as legitimate during scheduled downtime. Additionally, it may be prudent to work with the scanning tools to configure the appropriate priority of a scan, as the intensity of which you scan a production multicore, failover redundant web server host, is likely not the best choice for scanning a single-core JACE. Should you encounter an issue with a network scanning utility and Niagara 4.9 and above, please contact your support organization.