Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue Every item shown in the Objects window of the TGML editor can be considered a Node. In the figure shown below, this relatively simple TGML page has 14 nodes. Nodes are hierarchical with parent and children nodes. One important concept when scripting in TGML is finding the desired node. Examples of this are: Changing the color of a rectangle when a bound signal is offline Writing a new value to a text box every time the database value updates Opening a new page when the user left clicks on a component Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation TAC Vista TGML Graphics Editor Cause Within a script, there are two functions that will pinpoint a specific node, but have very different applications. These are: getTarget() getCurrentTarget() An example function of how to use these functions is: function click(evt){ target = evt.getTarget(); } Resolution getTarget() - returns where an event is coming from getCurrentTarget() - returns the parent of the script Both examples below chart the differences between the two functions using the screen capture below. If the bind object in the figure above changes its value, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Bind Component B Bind Rectangle C Bind Bind If the user clicks on the rectangle in the figure above, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Rectangle Component B Rectangle Rectangle C N/A N/A Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue Cannot open the FlexNet License Admin, the TAC license server is not running as a service, or the vendor daemon is down. Product Line TAC Vista Environment Vista LMAdmin FlexNet License Administrator Cause If the TAC Vista Server installation option "Use the local TAC License Server" is not selected during installation, the license server will be installed but not successfully configured. When the license server is not running it will prevent the LMAdmin web interface from launching. If the license file is not in the correct location when the license server is started, then the vendor daemon must be started manually. For general information on the new license system, see LMTools Licensing Administrator program is replaced with LMAdmin in Vista 5.1.8 or greater. Resolution Remember that a valid and un-modified License File is necessary for the following troubleshooting steps to work. If the License file was manually manipulated in any way, please revert to a File specifically licensed for the machine where the License Server resides. Before proceeding, make sure the setup of the license system is made correctly following No license after reboot when TAC Vista Server (TACOS) runs as a service Check out this video about the new Vista 5 licensing system on the Community website. Check out the TAC License Server Setting tool below for the new license system. Click here to download the zip file.       Could not reliably determine the server's fully qualified domain name This is a bug in the lmadmin.exe file. Either replace the lmadmin.exe file with the newest available or install the newest version of the license system available. You can have a newer version of the license system installed than the TAC Vista version installed. E.g. TAC Vista 5.1.8 will work together with a license server version 5.1.9 Cannot Open the Flexnet License Admin Ensure that the TACLicenseServer is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services. Scroll down and select TACLicenseServer. Click Start in the top left corner of the window. Make sure that the site license is the only file in the license server path. If there is a demo license in the file path when trying to start the license server, it will fail to start. Sometimes you will get the following Windows error. Error 1067: The process terminated unexpectedly. Note: TAC License Server with spaces is not the correct license server. If TACLicenseServer is not found in the list then move on to the next troubleshooting section titled "Setting up the TAC License Server as a Service".   If the TAC License Server will not start then it may be due to another program using the 8080 TCP port. Use TCPView to search for programs running on local port 8080 and either stop this program or use the TACLicenseServer Settings tool at the top of this page to change the port that the TAC License Server uses. If the TACLicenseServer still does not run then continue to the next section below, Setting up the TAC License Server as a Service.    Setting up the TAC License Server as a Service LMAdmin.exe must be registered as a service. When first installing Vista the option "Use the local TAC License Server" should be selected. When this option is selected it will install the license server, register it as a service and start it. When "Use a license file" is selected it will only install the license server without configuring its settings. This can be corrected by reinstalling Vista and making the proper selection or by a manual configuration procedure. The manual procedure steps are listed below. Note: The option "Use a license file" only applies to a demo license, not a site license file. Manual Procedure to Register the License Server as a Service Start a command prompt as an administrator. To do this go to Start > All Programs >  Accessories and right-click on Command Prompt, then select Run as Administrator. In the command prompt go to path C:\Program Files\Schneider Electric\License Server\ (This can be done by entering "cd" and then the directory path listed here.) For 64-bit OS go to "C:\Program Files (x86)\Schneider Electric\License Server\" Run the command: "LMAdmin.exe -InstallService TACLicenseServer".   Manually copy the license files that are to be used to the new license file folder location. 32 bit - C:\Program Files\Schneider Electric\License Server\taclic\licenses 64 bit - C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses   In the command prompt type, the following command to start the license server "net start TACLicenseServer". Note: If the license files are not copied prior to starting the license server, the vendor daemon will not be started successfully and must be manually started after the license files have been copied to the new license file location. For instruction on how to do this, follow the steps in the next section Vendor Daemon is Down When the license server is installed but not configured, as mentioned above, the TAC Vista Server installer will not create a shortcut to the license administration tool in the start menu; since the shortcut will not work. A shortcut is created in the installation folder and can be used to create a shortcut in the start menu manually. The shortcut can be found here "C:\Program Files\Schneider Electric\License Server\FlexNetLicenseAdmin". For 64-bit OS the shortcut is found in "C:\Program Files (x86)\Schneider Electric\License Server". Vendor Daemon is Down   Note: If working on a 64 bit PC, replace "Program Files" with "Program Files (x86)" in the file paths below. Go to All Programs > Schneider Electric > TAC Tool 5.X.X > Flexnet License Admin. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password). Click on the Vendor Daemon Configuration tab and then select the taclic daemon. Verify that the path in the License File or Directory field matches the location of the site license. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start. If the Vendor Daemon still does not start after checking the file paths, verify that the site license has been hosted to the correct MAC address. For help finding the MAC address, see How to locate a computer's MAC address. NOTE: Also make sure there are no other Flexnet License Servers installed on this same machine (SmartStruxure, Power Manager, etc). If there is another license server running on the same machine then this can cause a conflict. SmartStruxure license and TAC Vista license on the same PC can walk you through merging them together. If IPV6 is enabled, you may need to disable it and reboot the machine. Switching from a site license to a demo license Log into LMadmin and stop the license server Save the Demo License file in C:/Program Files/Schneider Electric/License Server/Licenses Open the desired engineering tool and point Vista to the Demo file When finished, log into LMAdmin and start the License Server.  This will tell Vista to continue using the site license. A site that has worked with the installation from a remote desktop or the different user logged in Open task manager Check for process "lmgrd" of 2 of them are running the FlexNet server might try to read from the wrong server. Shutdown down both processes and restart the FlexNet server Log in to FlexNet admin and start the vendor Reread the license file Also, check License Administrator error "EXITING DUE TO SIGNAL 28 Exit reason 5"

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue The Xenta 7xx from factory it has the default IP address 192.168.255.2, which also is stated in the manual. But when you run the “format” command on a Xenta 7XX, you will get IP address 172.22.1.5. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 527 NPR, 555, 701, 711, 721, 731, 901, 911, 913 Cause The format command will wipe all memory from the Xenta Server. Its IP address will need to be reset, system program will need to be reloaded, and XBuilder project will need to be redownloaded. Resolution The Xenta from factory has the default IP address 192.168.255.2 subnet mask 255.255.255.0 After the “format” command it will have IP address 172.22.1.5 subnet mask 255.255.255.0 See IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for instructions on setting the IP address to the desired address.

Issue Unable to retrieve license file for Vista 5.x.x. You may receive an error from Vista stating "Unable to retrieve license file". You may also see the following error within read pain in LMTOOLS/Server Status. FLEXlm Error: The desired vendor daemon is down 1) Check the lmgrd log file, or 2) Try lmreread Feature: ARC/INFO Vendor:Host: ESRI : server License path: @server;@client; FLEXlm error: -97,380. System Error: 10061 "" For further information, refer to the FLEXlm End User Manual, available at "www.globetrotter.com". Program not run. Product Line TAC Vista Environment Vista 5.x.x LMTOOLS License Server Cause License Server cannot start until it is able to connect to and checkout a license from this license server. One known cause of this error is an incorrect license Host ID in your license file. Resolution Open LMTOOLS Select the Config Services Tab Click the "View Log" button to view the debug log text file. Review the contents to see the actions taken by your license server. The MAC address on the Vista Server machine may have changed if you see the below error within this log file -Wrong hostid on SERVER line for license file: -C:\Program Files\Schneider Electric\License Files\LicenseFilePro5.1.lic -SERVER line says 001c4213f460, hostid is 0050569d001a -Invalid hostid on SERVER line You must log on to the License Activation Portal to rehost this license to the new MAC address using the original entitlement ID. Please see Rehosting a Vista 5 License on the FlexNet License Server.

Issue Where can I find help on TGML scripting and advanced features? Which javascript functions are supported and how do these impact performance. Product Line TAC Vista Environment TAC Vista TGML graphics editor 5.1.7 Cause More advanced graphics often require scripting and the engineer needs to know which functions are supported. Resolution In the TGML editor under Help there is a section called TGML Format Specification. Details of scripting methods as well as examples can be found here. Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue When the time is changed on any TAC Xenta unit using the TAC Xenta OP, all TAC Xenta devices in that group will have their time changed by the same amount. Product Line TAC Vista Environment TAC Xenta Programmable Controllers TAC Xenta Group TAC Xenta OP Cause The time parameters will be considered during this broadcast. This occurs when you change ANY controller, not just the group master. Resolution For example, the time is changed on one controller. It will add the minutes in its time zone field and broadcast the time as GMT. The other controllers in the group will receive the message, subtract their time zone minutes, and change their own time. 

Issue Depending on the environment of installation, IP classification of products is a prerequisite for the choice of the enclosure where TAC Xenta products are mounted. Product Line TAC Vista Environment TAC Xenta TAC Xenta OP Cause In some older versions of product documentation, the IP class was stated to be IP30, which was incorrect. Resolution All TAC Xenta products are, due to their hardware design, IP20. TAC Xenta OP is also IP20 unless cabinet mounted which then makes it IP43. See each product's data sheet for more information and details.

Issue Xenta OP menu items: Status, Sub menu, Week chart, Holiday chart, Alarm, Access Code, Edit Access Code, Date and Time, Daylight Saving have defined Access Levels: Low Level Medium Level High Level Accessing the medium or high-level menu items requires a password. What is the default password and how can they be changed? What if the passwords have been lost? Product Line TAC Vista Environment Menta Xenta Controllers Xenta OP Cause Accessing the medium or high-level menu items requires a password. Resolution The default password for accessing medium level menu items is: 1111 The default password for accessing high-level menu items is: 2222 These can be changed via the Xenta OP only provided the "Edit Access Code" menu item is present in the OP Tree. Downloading the controller may reset the access level passwords back to the default.

Issue When the Vista export file is converted using the Vista conversion to an EBO Server the Xenta devices are created with an empty application. Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Conversion tool Cause The user name that was used to log into Vista Database to run the Database export does not have full access to the Xenta devices Function Block Program. Resolution Log in with the System user that has full access to the Vista Database and export the database for the conversion tool to use.

Issue When connecting to several OPC servers, is it necessary to have several OPC Client licenses? Product Line TAC Vista Environment Vista OPC Server Cause In some cases, several counts of the same license module is required if several simultaneous sessions are in use. (Example: Workstation) Resolution You can connect to several OPC servers simultaneously while you just have (1) one OPC Client license.  

Issue A message saying "no license available" or starting the license finder popup.  Sometimes Flex license system needs a little extra time to load the licenses. Product Line TAC Vista Environment FLEXnet Licensing Cause The problem is in the Flex license system and not in TAC Vista, the same issue occurs on other Software vendors using the same license system. Resolution Make sure that you are logged in as an admin on the computer. Right-click on This PC > Properties > Advanced system settings Click the button in the lower-left corner labeled "Environment variables" Add a new system variable named FLEXLM_TIMEOUT Give it the value 3000000, press OK Restart TAC Vista Server and Workstation, the Flex license system will now have 3 more seconds before throwing out a message saying "no license available" or starting the license finder popup.

Issue When a SE7000 is setup in Vista you cannot configure the device using the nciCfg1FcuZn and nciCfg2FcuZn Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The configuration NCI's are not made available for Vista. Resolution To edit these values the lonworks plugin can be used or the front keypad on the sensor itself.

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue Windows System Information may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment Microsoft Windows Operating System Cause Unspecified cause. Resolution Press WINDOWS + R on the keyboard of the Windows system that you wish to obtain the report from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Msinfo32.exe and click OK The System Information tool will start. Click on File > Sav When prompted, save the *.nfo file to an accessible location. Email the *.nfo file to your support representative.    Note: This application can also be accessed from Start, All Programs, Accessories, System Tools, and System Information. Using this method will open the System Information for XP and Windows 7, 32 and 64-bit computers. Refer to: Description of Microsoft System Information (Msinfo32.exe) Tool

Issue Windows update KB4519976 causes all Xenta servers to go offline in TAC Vista every few minutes. Product Line TAC Vista Environment TAC Vista Server Microsoft Windows 7 or Microsoft Windows 2008 Server Xenta 500 Xenta 700 Xenta 900 Cause After the Windows update, KB4519976 is installed, the SSL handshake behavior is changed. This affects TAC Vista and its communication with the TAC Xenta server. Resolution There are two workarounds available at the moment. Solution 1: Uninstall Windows update KB4519976 Solution 2: Turn off SSL for the communication between TAC Vista and the TAC Xenta server using the registry setting shown below. This means that only the login will be encrypted when TAC Vista is communicating with the TAC Xenta servers. Run the utility TacosTweak.exe, located in the program folder where TAC Vista is installed. Set "Only use SSL for login to TAC Xenta Servers(5xx/7xx)" to 1 to run the communication between TAC Vista and TAC Xenta servers without SSL. Restart the TAC Vista server for the changes to take effect.