Building Automation Knowledge Base

Issue WorkPlace Tech application was created with constant tags for writing test values to the application.  After uploading a previously downloaded application that contains constant tags with a [NA] value, none of those constant tags are drawn on the regenerated application drawing. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool version 4.x (any release) I/A Series WorkPlace Tech Tool version 5.x.x (any release) Cause The default input value for any unused control object input is a value of [NA].  Since all unused inputs have the implied [NA] constant, they are not drawn on a regenerated WorkPlace Tech application drawing. Resolution This action is by design.  By design, a constant tag can be added to any previously unused control object input and a value written to the controller via that constant tag using the Write to Ram function.  When adding constant tags to inputs, it is not necessary to recompile and download the application unless you desire that the new "Non-NA" value be saved in the application hex file.  With this in mind, remember that constant values are written to an installed application using the "Write to Ram" function will be lost when the controller is rebooted.

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

Issue Is there is an application that will display the duress (panic) button alarm to the operator, when pushed, along with sound. Product Line TAC I/NET Environment I/NET Seven Automatic Page Display, Event Definitions & Sequences, User Defined Button  Cause Sample application / guide to program duress alarms in I/NET. Resolution I/NET provides various functions that allow it to provide a pop-up duress alarm, one feature is to use one (or many) graphic page(s) which automatically appear (pop-up) on activation of an alarm. Along with this, it is also possible to generate a sound either PC based or, the more preferred option, to an externally wired Buzzer / Siren at the same time.  The attached document shows a few steps as a guide to make a start on your own application using the following features: Automatic Page Display AMT Audible Alarm Event Definition / Sequences User-Defined Tools and Buttons If you are not familiar with these items you should refer to the TCON documents mentioned in the attachment.

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

Issue The Niagara 4 JACE's platform daemon fails to start making it impossible to login and configure using Workbench tools such as the Commissioning Wizard or Dist File Installer. The error within the serial shell typically indicates ... /proc/boot/ksh: niagarad: cannot execute - No such file or directory. Product Line TAC IA Series Environment Niagara 4 JACE-603 JACE-645 JACE-600E JACE 8000 Cause This can occur as a result of an Incorrect or failed upgrade or improper downgrade without first installing a clean distribution. Resolution Requirements - You will need the following to complete the recovery steps: A terminal emulator such as PuTTY A SFTP client such as FileZilla Serial-Shell cable for your JACE hardware model (specified in the .PDFs below) The Niagara 4 Clean Dist file for your JACE hardware A zip file utility such as 7-Zip The hardware and startup documentation for your JACE model (provided with Niagara 4 installer) Obtain recovery files from the Niagara 4 Clean Dist File for the matching hardware: The clean dist files can be found in your Niagara4 $system_home directory, or in your Niagara 4 image files under the cleanDist directory or in the overlay\cleanDist directory. Open the .dist file for your JACE's platform using a zip utility like 7-Zip and extract the zip/n4clean.tar.gz file. Also, extract the dev/shmem/n4-xxx.image file, where xxx will be different, depending on the JACE's platform type. JACE 300 ... qnx-jace-n4-npm3xx-etfs2048-clean.dist JACE 600 ... qnx-jace-n4-npm6xx-etfs2048-clean.dist JACE 600E ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 603 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 645 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 700 ... qnx-jace-n4-javelina_booke-etfs2048-clean.dist JACE 8000 ... qnx-jace-n4-titan-am335x-clean.dist Make a Serial Connection to the JACE The .PDFs in the N4 documentation set describe how to make a serial connection to a JACE in the "system shell" section(s) of each document. Once connected, the controller will boot and display the "login:" prompt.  Enter your Platform credentials. After login, either a "#" or "$" shell prompt or configuration menu similar to the following is shown.   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011     dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255         inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------     1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot     L.  Logout     Enter choice:   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011   dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255             inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------   1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot   L.  Logout   Enter choice: Verify correct system time and update as needed The RTC time may not be correct if the unit has been unpowered for longer than the on-board capacitor backup period. Using menu ... the first item in the menu list allows you to Update System Time.  The current date/time is displayed. Enter the new date/time in the form YYYYMMDDhhmm[.SS].  Note that entering the seconds is optional. For example: 201801111420 for 11-Jan-2018 at 8:20am UTC or 8:20am CST. Enable SFPT The Secure FTP service is not enabled by default on a JACE.  Enable the SFPT from the menu above or the shell prompt (if required). Using menu ... the fourth item in the menu list allows you to enable SSH/SFTP.  Enable it now, using port 22. Once enabled, enter another choice, "sh" (without quotes).  This will give you the "#" or "$" prompt that you need. If you could not enable from the menu in the step above, manually start by issuing the command tsudo syssh_sshcfg at the shell prompt.   If the command fails, issue the syssh_sshcfg command.  If the command fails again, enter the following ... $ cd /sys/bin ... then enter $ ./syssh_sshcfg ... then enter Transfer the n4clean.tar.gz and OS Image Files using SFTP Client Using an SFTP client such as FileZilla, transfer the n4clean.tar.gz file previously extracted for the platform from the clean dist file to the JACE's /zip directory. If the transfer fails with a permissions error, issue the command tsudo chmod 777 /zip at the shell prompt and try it again. Next, transfer the .image file you extracted from the clean dist file to the JACE's /dev/shmem directory. Run osupdate From the login menu prompt, type sh.  This will exit the menu system and enter the shell mode.  At the "#" or "$" shell prompt, issue the command osupdate.  After a short delay, the shell prompt will return. Reboot the JACE Finally, reboot the JACE.  This can be done by issuing the command shutdown hf 0 at the shell prompt.  When the JACE restarts, the unit will automatically process the clean dist file.

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 Services for assistance. Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue Need requirements for email notifications Environment Continuum Cyberstation Email Eventnotification Outlook 2007 (32bit Only) Outlook 2010 (32bit Only) Cause Requirements for sending email notifications with Continuum Resolution Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have a MAPI-compliant email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book. How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook(32bit). Other mail applications may have different menu names and choices but the general procedure is the same. Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. Select New Entry from the Address Book File menu. Select the entry type Personal Distribution List and put this entry in the Personal Address Book. In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages. ** Ensure that there are not 2 PCs using the same email account for Outlook.

Issue Not possible to download an application(.mta file) to a Xenta 401, Xenta 301/302, Xenta 281/282 The download process looks fine until the file transfer should start. Then it just hangs and nothing happens. Product Line TAC Vista Environment Xenta 401 Xenta 301/302 Xenta 281/282  Cause The problem is that a file transfer is already running for something else (trend logs or alarms) and only one file transfer can run at a time for each LON network. Resolution Shut all graphics pages and try again. Restart the Vista Server and try again. If that doesn't help, restart the Xenta's to stop the ongoing file transfers If that doesn't help, ensure you are running TAC Vista 5.1.9 and  Start the TAC Vista server communication log, let it run for 10 minutes and send that to your local technical support for investigation. To start the communication log: open the Log tab in the TAC Vista server, open "Comm.Log", Set the Physical layer to "Active" The log will be saved in the $Log folder in the Vista database and called PL_"network name"

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue Get server error in '/webClient' Application when attempting to connect with the WebClient Environment WebClient 1.93 Windows 7 Cause Bad installation Resolution 1. Run aspnet_regiis.exe -i (This is done from a DOS prompt, C:\Windows\Microsoft.net\Framework\v2.0.50727)  2. Re-install Continuum WebClient

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.

Issue The file structure is incorrect for MNL-FLOW-BAL 3.0 software for use with Windows 7 64 bit OS.  The FlowBalance.exe needs to be run in Windows XP (Service Pack 3) compatibility mode. Product Line TAC IA Series Environment Windows 7 64 bit MNL-FLOW-BAL Balance Software Cause The paths for certain files being used by the software cannot be modified. When loaded on a 64 bit PC, the default paths are incorrect for the rest of the processes to find. Resolution Manually create and insert the folder structure required. Set the FlowBalance.exe compatibility Copy the TAC folder in the Program Files (x86) folder from Windows Explorer. Paste into the Program Files folder Open the pasted TAC folder and delete all the files except for the XIF folder and the FlowBalance.cfg file in the LON FlowBalance folder. Right-click the FlowBalance.exe icon created on the desktop Open properties/compatibility tab. Set as Windows XP (Service Pack 3)

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue When configuring a SmartConnector, the custom assembly cannot be seen in the Add Processor Configuration tab.   Product Line EcoStruxure Building Operation Environment Microsoft Windows Server 2012 and newer, Windows 10 Cause Microsoft Windows Server Unsigned or unknown certificates Some files need to be "unblocked" after download in order to avoid security warnings from tools like Visual Studio about potentially unsafe content.   This is because the dll’s for the custom processor have been downloaded from an internet based source.   Otherwise, all the required dll’s for the solution may not be available in the service installation directory (normally “C:\Program Files (x86)\Schneider Electric\SmartConnector”). This information can be seen in the SmartConnector log file. SmartConnector will log an error when going to the point of adding a new processor if it can’t find a reference. It will point to the assembly which is missing. Microsoft Windows 10 The service needs to be restarted once the dlls for the custom processor have been added in the service installation directory. (“C:\Program Files (x86)\Schneider Electric\SmartConnector”) Resolution Microsoft Windows Server range To "unblock" a file, Right-click it in Windows Explorer Choose Properties from the context menu Click the Unblock button in the lower right-hand corner of the resulting dialog Hit OK or Apply Important: ZIP files should be "unblocked" before their contents are extracted. Note: Depending on the security policy level on the system, you may need to perform the same action for the DDLs once uncompressed. Microsoft Windows 10 To restart the service by Opening the service windows Select the SmartconnectorService entry Either click on the Restart button, or Stop then start

Issue Is there a specific amount, or percentage of free memory that must be maintained for Continuum controllers to operate? Environment NetController CX9900 CX9940 Infinet i2 ACX2 b3 Cause Is there a specific amount, or percentage of free memory that must be maintained for Continuum controllers to operate? Resolution There are no published metrics or guidelines regarding the use of Continuum controller free memory. For most of the Continuum controllers there is no required minimum amount of free memory in order for the controller to function properly. The notable exception to this is the CX99xx. Remote validation will stop working in the CX99xx if freemem goes too low. This is because the system memory and the user memory come from the same heap. Also, in the CX99xx, if a Plain English program uses a commport to read and write data, and the controller has insufficient memory to switch from a RAW port to AutoSet, the controller will lock the commport. A safe target for freemem is 15% of the total. These issues were fixed in the NC2/ACX2 by having separate heaps for memory allocation by the system and OMS (object management system). The newer IP level controllers and the i2/b3 controllers can be loaded up until there is no freemem but be aware that as you load up the controller memory with programs, the scan time will typically increase.

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Dehumidification using Xenta 121-FC Environment Xenta 121-FC Xenta 121-HP Cause Some aspects of how the dehumidification mode in the Xenta-121 operate are undocumented. Resolution The dehumidification feature of the Xenta 121 can operate either by turning on external dehumidification equipment using one of the digital outputs or, if no external equipment is provided, it will use the cooling for dehumidification. In the latter scenario, the heat continues to be operational when the cooling is forced for dehumidification. Additionally, if there is an outside air damper, it will be controlled to its minimum position before forcing the cooling on. When is external dehumidification enabled? For On/off cooling, cooling is enabled for dehumidification when the nvoDehumidActive value is greater than 10% and is disabled when the nvoDehumidActive value drops below 5%. For all other types of cooling, nvoCoolPrimary is set to match the nvoDehumidActive whenever it is a greater than cooling PID output + 5% or whenever the cooling PID output is less than 5%. The dehumidification feature can be configured using the ZBuilder configuration tool. However, the individual features can also be accessed via the points listed below using either Vista Workstation or another Lon management tool such as LonMaker: Applic UCPTappOptions Bit Usage If FALSE If TRUE Additional notes 5 Dehumidification control enable Not active Active   6 Dehumidification type Internal External Only applicable if bit 5 = true. External control can be hardwired or via SNVT. Internal will force cooling as a dehumidification method. 7 External dehumidification active on Open contact Closed contact Only applicable if bits 5 and 6 are both true. UCPTappOptions2 Bit Usage If FALSE If TRUE Additional notes 7 External dehumidification type Digital Analog If true then the RH reading is mirrored to the analog output (0-100% = 0-10V). Only applicable if UCPTappOptions bits 5 and 6 are both true.

Issue Are there any redundancy options for Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Stratus everRun Cause Need to provide redundancy for the Security Expert Server. Resolution There are a couple of options for providing server redundancy that can be used with Security Expert. The first option would be to use a downtime prevention product such as Stratus everRun as a hot standby solution. The second option is having a secondary Security Expert server as a cold standby server, if the primary server fails/needs to be taken offline the Security Expert services on the cold standby server can be started to take over. This option is largely manual, there is no automatic switching between two servers with this configuration. There are also a number of considerations to take into account with this option: In this scenario the controllers would be programmed with 2 x event server IP addresses for the primary and cold standby server as a result only 1 server/set of Security Expert services must be running at a time, having both running and therefore the controller having 2 x valid paths back to 2 x different servers concurrently will cause issues with the upload of events, online status and downloads A suitable system/process would need to be put in place to ensure the databases are restored from the primary to the cold standby server There will be 2 different Security Expert servers running which will require 2 separate Security Expert Server license with the same feature set enabled on both Considerations will need to be made with regards to the name of the machine to ensure the Download and Event servers can run, either the machines must have the same name or the name of the server needs to be renamed when required to the name of the cold stand by server An operator would need to verify the state of programmable functions and services. If the primary server failed during the middle of the download when the cold standby server is up and completes a full download some functions/services may require manual starting.

Issue Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Environment CyberStation v1.7 Cause Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Resolution CyberStation v1.7 had CyberKeyWriter.exe not CyberKeyWriter2.exe. CyberKeyWriter2.exe will be added to the \Continuum directory during the upgrade. Once the upgrade to the new version of CyberStation is done, use CyberKeyWriter2.exe and the Key Code from the Repair Dept to upgrade the key.  

Issue When trying to open web pinpoint on a remote client session the users receive the error below: Product Line Andover Continuum Environment MS Server 2008 and newer Windows 7 and newer Continuum 1.9x and 2.x webClient Remote Desktop Cause This issue is caused when a remote desktop connection is made on a Windows 7, Windows 2008 server or newer Operating Systems.  The console becomes locked.  It will stay locked until the local session is restored with a logon. Resolution  Resolution: 1)      Create a Bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console ***********************************************************************************************   2)      Place this file on the desktop of the Web Server system. 3)      When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be ran “As an Administrator” This will disconnect the session and restore the console.