Building Automation Knowledge Base

Issue 'Failed to connect to SQL Server (local\TACVISTA). "[18470] Login failed for user 'xxx\xxxxx'. Reason: The account is disabled." message appears when trying to install Vista using another account than the account that is logged on to the server. Product Line TAC Vista Environment TAC Vista 5.1.X SQL installation/connection Cause The TAC Vista installer SQL configuration settings page states 'Select authentication and specify SQL Login or Windows account and password to set how TAC Vista Server will access the SQL server.' This means how TAC Vista will access the SQL server when Vista is running, not during installation. Resolution Ensure that the user running the TAC Vista installer has the correct permissions to install an SQL server (if this is a new database) and configure it. The specified user will be used during runtime, but the launching user during installation. The installing user can then be removed from the SQL server security settings after installation is complete.

Issue Do you have a standard template listing all the actions that are possible for an operator on a Continuum Workstation.   Environment CyberStation Activity Log Cause A list of CyberStation user (operator) actions is required for a bid submittal. Resolution This list is available in the file Stsvc.txt which is located in the \continuum directory. Search that file for:  // SVC_ACTIVITY_EVENT Also attached is a copy of that file from v1.93.

Issue Does Sigma run on Windows 10? Product Line Satchwell Sigma Environment Sigma Windows 10 Cause Is Sigma 4.08 supported on windows 10? Resolution No version of Sigma is supported on a Windows 10 platform except: Sigma 4.08 can only be installed on Windows 10 when the software is used as a transition into EcoStruxure Building Operation ( EBO ) and used with the correct version of transition component. For full details of Sigma 4.08 versions, build numbers and operating systems supported, see What operating systems is Sigma 4.08 supported to run on?.

Issue TC3XX thermostat is off when power is restored after a power loss Product Line Field Devices Environment TC300 TC303 TC353 Cause The default operation mode when the TC3xx thermostat is powered up is in OFF mode. Resolution An internal system setting (parameter 03) allows the possibility to alter the behaviour of the thermostat upon power restoration. 00 = Restores with previous status  01 = Restores with power off.  (this is the factory default setting) 02 = Restores with power on. Once power is restored, the thermostat will remember all parameters (** with the exception of the TC303-3A2DPMS and TC303-3AADPMS) that were in place before the power failure. The following specification numbers allow the thermostat’s restored state to be configured: - TC303-3A2L TC303-3A4L TC303-3A2DLS * TC353-3A2DLS TC303-3A4 * TC353-3A2L TC303-3A2DLMS * TC353-3A4DLS TC303-3A2LM * TC353-3A4L TC303-3A4DLMS ** TC303-3A2DPMS       ** TC303-3A4DPMS For guidance and instruction on how to perform the adjustment of internal system parameters, please contact your local/regional support team. * The TC353-3A2L, TC353-3A4L, TC353-3A2DLS and TC353-3A4DLS have been discontinued. Refer to PA-00686 - Product ObsolescenceNoticefor EMEA and APAC for further details. ** The TC303-3A2DPMS and TC303-3A4DPMS temperature set point will revert back to the default value after power is restored. This is as per designed. Please note: internal system parameters MUST ONLY be changed by a trained Schneider Electric or an approved Partner technician.Incorrect setting of such internal system parameters may result in either undesired operation of the thermostat or irreversible damage.

Issue How to Lockdown your facilities using Continuum area/door lockdown functionality. Product Line Andover Continuum Environment CyberStation CX9680 ACX5740/20 Cause Need a fast and efficient way to lock down multiple areas in one operation when a threat is perceived at a site. Resolution The Continuum Physical Access Control System supports an advanced feature that allows for quickly locking down parts of or an entire building or campus via the areas/doors that are under physical access control by the Continuum system. This functionality is available in second-generation access controllers such as the CX9680 (NC2) and the CX5720/5740(ACX2) In Continuum, lockdown of an area or door means that access to the area/door via the physical access control system is restricted in such a way that prevents the movement of individuals into the locked-down area/door as well as keeping individuals from leaving the area/door under locked down. Locking down an area automatically locks down all doors associated with the area; Continuum also allows doors to be locked down individually. When a door/area is locked down, all credential access attempts and exit requests are denied. The only way to gain access into the locked-down door/area is by the use of a credential that has been designated with ‘Executive Privilege’ in the system. Note though, that a person with executive privilege may gain access into a locked-down area/door via the credential reader but if the mode of egress from the area is via Exit Request then such person would not be able to exit the door thru the normal exit request mechanism as there is no way for the person to indicate her ‘executive’ privilege by any means other than presenting the proper credentials (card or PIN) at a reader. This document outlines several methods of implementing area lockdown for a building or campus such as a school, the methods outlined in the document are provided for illustration purposes only and are not to be taken as a complete solution but rather as general guidelines. On legacy controllers that do not support the Area Lockdown feature (CX99xx, ACX7xx), we can still secure the doors by setting their state to disabled which prevents the doors from processing credential access attempts as well as Request to Exit, please note that in this case, NO ONE (including executive privilege personnel) will be able to gain access to the door until it is re-enabled How to Lockdown your facilities using Continuum area lockdown outlines several methods of implementing area lockdown for a building or campus such as a school, the methods outlined in the document are provided for illustration purposes only and are not to be taken as a complete solution but rather as general guidelines.

Issue A dialog of "Cannot open .NET editor with .NET Framework" comes up with new installation of Webclient or after a Microsoft update of .NET 4.5.x. There was an error trying to create the .NET control for this page. Product Line Andover Continuum Environment Continuum Webclient Windows 7 Windows Server 2008 Windows 10 Internet Explorer Cause Microsoft changed the behavior of Internet Explorer when .net 4.5.x is installed on a PC. It turns off .net 2.0 support which is needed for several editors to function on Webclient browser PCs Resolution See web.Client v2.0 .Net Editor Hotfix on the EcoXpert Extranet This is a registry key file that installs the registry keys mentioned further down in this article. It allows Internet Explorer to utilize .net 2.0 that several webclient editors use. This hotfix contains a .reg file which changes the registry, it is recommended to make a Windows Restore point or a backup (export) of the existing registry folder (hive). The hotfix only updates the following keys, so the changes can also easily be made manually. On an 32-bit (x86) Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Set the value to 1 On an 64-bit Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Set the value to 1 A reboot of the webclient browser PC is required after the change is made. Each browser PC will need to have this fix applied. Microsoft Edge can also be used on newer client PCs, see the following article: Microsoft Edge can be used for webclient client PCs   

Issue The time in TAC Xenta Server should be the same as the time on the TAC Vista Server PC. When Xenta Servers connect to the TAC Vista Server, they should synchronize their time with the Vista PC. Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 NTP Server Vista Server Cause There are different scenarios. Vista Server PC has no internet connection Vista Server PC has internet connection Resolution Corresponding to the causes above: Set the Xenta Server to synchronize with the Vista Server PC. You do that by adding this AuthoritativeNTPserver.zip reg file to the registry on the TAC Vista Server PC, and enter the IP address of the PC into the Xenta Server as described in Setting NTP in Xenta Server.pdf. Set the Xenta Server and the Vista Server PC to synchronize with a NTP server on the internet. Find servers here: http://support.ntp.org/bin/view/Servers/NTPPoolServers Area HostName Worldwide pool.ntp.org Asia asia.pool.ntp.org Europe europe.pool.ntp.org North America north-america.pool.ntp.org Oceania oceania.pool.ntp.org South America south-america.pool.ntp.org In general, make sure that firewall is not an issue. NTP uses port UDP 123

Issue If a Xenta I/O module has experienced a hardware failure it may be necessary to replace it with a new controller. Product Line TAC Vista Environment Xenta I/O Modules Xenta 411, 421, 422, 422A, 452, 452A, 471, 491 Cause Hardware failure of a Xenta I/O module requires it to be replaced. Resolution Physically replace the I/O module The next steps depend on whether the I/O module is part of an LNS system or a Vista Classic Network. LNS System Right click on the I/O module in the LNS management tool (LonMaker or NL220) Select Replace Service pin or manually enter the new neuron ID Open Vista System Plug-in Update the TAC Network Update the Vista database Download the base programmable controller Vista Classic Network Go to How to set the neuron ID of an I/O Module in a Vista classic network for instructions on setting the neuron ID for the new I/O module. Service pin or manually enter the new neuron ID Download the base programmable controller

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue How to read a controller error log Environment CX 9680 ACX 57xx BCX 9640 BCX 4040 i2 controllers B3 controllers Cause Need to decipher a controller error log Resolution Deciphering the controller error log can be accomplished by using a few of the fields of the error log. There is one field that is able to be deciphered very easily. The Error Code column of the error log is a code that can be matched to its text description. The other fields are used internally by PSS and engineering. To find out what one of the entries in an Error Code column means, open up the Continuum online help file. The Continuum online help file can be found by in the Continuum Explorer by selecting the menu item Help/Contents. From there select the Index tab and type in the keyword Error. A selection will be available for Error messages, Cyberstation. On this page you will be able to take the last 4 digits of the Error Code from the controller error log and match it up to its description. Example: Error Code  0x00001401 translated into decimal form would be 5121 The error code will be listed by both the hex and decimal format. Not all codes will be in the online Error description fields. Some of these codes are internal use only. If you find that you need a code deciphered, please open a case with Product Support.

Issue Need to know what different system alarms can occur in EcoStruxure Building Operation?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause System alarms are alarms built into the system, such as "IO module offline" or "Server offline". In EcoStruxure Building Operation, over 230 system alarms exist. Resolution For all system alarms check WebHelp article: System Alarm ID Enumerations

Issue Error when running the Checklic license utility: "InitCrypkey Error -103: NETWORK: REPLY FROM NETWORK DRIVER IS BAD" "InitCrypkey Error -102: NETWORK: NETWORK DRIVER APPEARS TO NOT BE SERVING THIS DIRECTORY" Product Line Other, TAC Vista Environment LNS 3.0 LNS Turbo Edition (Ver 3.2) LonMaker 3.0 LonMaker 3.1 LonMaker Turbo (Ver 3.2) Vista Cause A problem has occurred with the LonMaker licensing. Resolution There are two procedures for fixing this problem. Try Procedure 1 first, and if the license still has the same problem, try Procedure 2. Internet access may be required for Procedure 2 to in order to download the setupex.exe and cks.exe programs and request a replacement license. Procedure 1: Confirm that the Windows Crypkey License service is started. To confirm, click Start > Control Panel > Administrative Tools > Services. Verify the Crypkey License status is Started. Also verify that the startup type is Automatic. If not, right-click the name and then click Start. Double-click the name to enter the properties dialog and change the startup type to Automatic. Close the Service window.   Confirm the Crypkey NetworkX driver is started by running C:\Program Files\Common Files\Microsoft Shared\MSInfo\Msinfo32.exe. Expand System Summary > Software Environment > System Drivers in the category tree in the left pane, then locate NetworkX in the right pane. Confirm that the State is Running and the Status is OK. Close the System Information window. If you cannot find these software components, uninstall the Echelon Software product, reboot, and reinstall the product. Antivirus and Internet security software can interfere with the proper installation of the software. Disable such software before you re-install the Echelon software product. At this point, if you are still unable to run your LonMaker or LNS application because of a License Access error message and if the Checklic license utility still reports a -102 or -103 error, follow the steps in Procedure 2. Procedure 2: Check to see if two files exist in the C:\Windows\LNS Licenses folder. setupex.exe cks.exe The LNS Licenses folder is hidden; if you do not see it, open the Windows Explorer Tools menu, click Folder Options, and in the View tab, select Show Hidden Files and Folders and clear Hide Protected Operating System Files (Recommended). If you don't see these files, download them from Echelon and extract them to the C:\Windows\LNS Licenses folder. Open a Windows command prompt by clicking Start > Run and typing in cmd (or command for Windows 98). Type the following command to change your working directory: cd "\Windows\LNS Licenses" Type the following command: setupex /U Reboot the computer. Repeat steps 3 and 4, and then type the following command: setupex Reboot the computer. Open a Windows command prompt and enter "checklic lonmaker.vsl" for the LonMaker Tool or "checklic nsseng.exe" for other LNS tools and applications. If no errors appear, then the LNS application should start. Exit now. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening/creating network. If the -4/-1 error remains, use the license wizard to request replacement credits. If the InitCrypkey Error -102/-103 error is shown, delete the following files under C:\Windows\LNS Licenses (do not delete other files from the LNS Licenses folder): For the LonMaker tool: LonMaker.rst LonMaker.ent LonMaker.key LonMaker.41s For an LNS tool or application other than the LonMaker tool: nsseng.rst nsseng.ent nsseng.key nsseng.41s Delete esnecil.ind in the C:\windows\system32 folder. Reboot the computer. Run the Checklic license utility again. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening or creating a network. If the -4/-1 error remains, use the license wizard to request replacement credits. Once the license is fixed, download and install the LNS Licensing Update 2006.

Issue String comparison in TGML script is not working. Product Line TAC Vista Environment TGML graphics editor 1.1.X Cause Javascript has a string class and a string literal. String literals are denoted by double or single quotation marks ("" or '') and it is important to compare "like" with "like". String literal: string1 = "Apples" String class: string1 = target.getAttribute("Name"); Resolution A deeper comparison is required in the example below. Instead of: name = target.getAttribute("Name"); tmp = target.getParentNode().getElementsByTagName("Ellipse").item(i).getAttribute("Name"); if (tmp==name) Use: if (tmp.equals(name)) An example is shown in the TGML graphic attached. Download graphic Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue There is no quick and efficient way to configure a TAC Xenta 102-AX controller after adding it to a LonWorks Network in Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC Xenta 102-AX controller is typically configured using the LNS plug-in that is currently not available in version 1.4.0 and newer. Resolution As an alternative to the LNS plug-in, the graphic page available on the Community [1] can be used. This zip file contains the TGML graphic, binding template, and a full import file with a Xenta 102-AX that is already bound. [1] Xenta 102-AX SXW TGML Plugin v1.6.1 (SBO 1.8.0 to 1.9.3) Example Plug-in TGML Graphic Page

Issue A network level controller is shown offline. Can a flash upgrade (Update OS) be done to it? Product Line Andover Continuum Environment BCX ACX5720 ACX5740 NC2 CX9900 Cause A bCX needed a flash upgrade but was offline in CyberStation. How can we update the OS? Resolution The Update OS function can sometimes be completed even if the controller indicates that it is offline. If it cannot be pinged from CyberStation, it will not likely be able to be upgraded in its current state and may require returning for repair. But if it can be pinged it, try doing the Update OS. Follow the progress in the Distribution window. If it completes, the controller will likely come back online a few minutes after the update is complete Completing this "Blind Update OS" can often restore to normal operation a controller that has its Operating System corrupted not allowing the Web page to be accessed, as long as you know the ACCNet ID and IP address (a reset IP can be performed) this process may be attempted. It is also possible to flash an offline controller if it has reverted to the default IP address (169.254.1.1) and ACCNet ID of 1 if the Workstation is set to be in the same subnet so it can ping the controller and these default settings are used for the controller configuration. If after a full cold restart and at least 2 attempts to flash the controller fail, then the controller may need to be returned for Repair. Some possible causes of this problem are listed in What can cause a controller to reset, cold start or lose data.

Issue TRD-IO-16 and TRD-IO-34 Installation (Wiring) & Configuration Guides Environment Niagara G3 Cause Quick access Resolution These guides are also available at http://www.niagara-central.com. TRD-T-IO-16 TRD-T-IO-34

Issue How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.

Issue What does default.db contain? Which objects does config.db contain? Do i need to upload both files to the MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to download config.db from Building Expert; There are two files for the database Resolution When the database is saved using the "save database to flash" button, the MPM saves its data into two files; config.db and default.db 1 - Configuration Objects (config.db): The config.db file includes "system configuration objects" which show up in Building Expert when logging into a brand-new MPM. BAC1,C2G1, CFG1, EOC1, ETH1, MOD1, SNTP1 and ZBC1 Note: Depending on the model of the MPM, some objects in the above list may not be there. Note: CBC1 is part of default.db   2 - Control Objects (deafult.db): Objects that are manually added in Building Expert are part of the default.db database. Some examples are - Analog Values (AVs) - Binary Values (BVs) - Lua Programs (PGs) - etc...   The following items are also part of default.db: - Devices (ZigBee, EnOcean, Modbus etc...) - Dashboards - Permissions - Login Credentials (Username and password)   Backing up the database: The files can be downloaded by entering the following in the address bar of the browser: (assuming the IP address of the MPM is set to the default IP 10.50.80.3) 10.50.80.3/root/default.db 10.50.80.3/root/config.db   To upload the database to an MPM refer to Uploading Database files to an MPM (Cloning).

Issue Upgrading SQL Express to a paid Edition of SQL for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Express Cause SQL Express 2008 R2 (for example) is limited to 10 Gb of Storage and 1 Gb of Ram usage. Many sites need a larger, more robust database than this allows. Resolution NOTICE: Before beginning, it is important to understand the difference between the Instance name and the version of SQL running.  The default instance name used in the the SQL Express version of SQL is SQLEXPRESS. This can be changed to anything during installation, but cannot be changed later.  This means that when upgrading to SQL Enterprise edition, the SQL instance name will still need to be SQLEXPRESS. The instruction below assumes the instance name is SQLEXPRESS and will be typed in that manner.   Perform a full backup of the Enterprise Server and Reports Server before beginning any upgrade process. Save these files to an external drive. Purchase a supported edition of SQL for the revision of EcoStruxure Building Operation WebReports being used. Please check the data sheet for the release to obtain this information. Open the Command Prompt and Browse to the location of the installation files for SQL. This should be the folder containing the setup.exe file for the new version of SQL Enter the Command "setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS /PID=XXXXX-XXXXX-XXXXX-XXXXX" NOTE:If  not using the default instance name, enter the correct instance name in place of SQLEXPRESS. PID is the product ID that came with the installation media. In some cases, this will be left out of the command string and entered later. (setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS) The SQL Installer will open. After the Setup Support Rules operation runs, click OK Click Next Verify the Product Key and click Next. Accept the License Agreement and click Next Ensure that the correct instance of SQL is selected and click Next. After the Edition Upgrade Rules runs, click Next Review the Upgrade Summary and click Upgrade When Complete click Close Open the SQL Server Configuration Manager using the start menu and verify that the SQL Server (SQLEXPRESS) service is running and that the SQL Server Reporting Services service is running. If either are stopped, right click and select the start option. Verify the upgrade is successful by opening a Web Browser and entering the URL "http://localhost/Reports_SQLEXPRESS" It should now be possible to see the option to directly edit reports in Report Builder. Log into the WebReports Interface. Notice that the initial report showing Database usage no longer runs.