Building Automation Knowledge Base

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue Error Messages: Windows - Delayed Write Failed Windows was unable to save all the data for the file D:\VISTA DB _23032011\$queues\insertevents. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Windows - Corrupt File The file or directory \VISTA DB _23032011\$queues\insertevents is corrupt and unreadable. Please run the Chkdsk utility. Product Line TAC Vista Environment TAC Vista Cause Problem with Operating System (or) Hard Disk Fault (or) Link between $queues with Vista Database. Resolution As there may be several issues that are causing this, there are three options to look at: OPTION 1: Restore the OLD TAC Vista Data Base Backup. Refer to TAC Vista Technical Manual chapter 26 for re-storing database procedure.   OPTION 2: There might be a linking problem with this folder and Vista.  Here are the steps to check if this is the problem: If the problem still exists, Check for hard disk errors. Find the $queues - folder in existing database folder ( \DB\$queues) Copy the files to an other location and delete current folder (Refer to An efficient method for deleting all queued files in the $queues folder) Recreate it with same folder names and copy back the files into $queues-folder. If the problem still exists, Check for hard disk errors.   OPTION 3: Check for hard disk errors, follow the below procedure: Go to "My Computer", Right click on Hard Disk Drive – typically - C, and Click on Properties. Go to Option "Tools" and Click on "Check Now" under "Error-Checking"

Issue Is there a limitation to the size the database can be on a Single User system in Continuum? Product Line Andover Continuum Environment Single User Continuum system MSDE database Cause Microsoft has put a limitation in the size of the MSDE database. Once you hit this limitation your Single User Continuum system will not operate properly. Resolution The size limitation is 2 Gb. It may be possible to recover after hitting this limit by removing un-needed log entries from the database, but this is not always a guarantee you will be able to recover the database. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation. From this point you can remove any unwanted logs and shrink the database. Then you can back up the database and restore it back to the Single User system. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation and convert the Single User system to a LAN installation. Finally if all the above do not work for your system you will have to restore from the last known good backup of the database. See Microsoft Database size Limitations and Continuum for SQL Express information.

Issue Set extra DCOM Settings when TAC Vista Server and Remote Work Station in Workgroup. Environment TAC Vista Server Remote Workstation Cause Cannot access TAC Vista Server from Remote Workstation, even though DCOM's set properly (in Workgroup). Resolution When using Remote Workstation and TAC Vista Server in same Workgroup and completing the DCOM settings based on the TAC Vista Installation Manual (04-00001-xx) and you still cannot access the TAC Vista Server PC, try the settings in the attached the document. Click here to download. Also refer these articles for more information: Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET Error: The RPC server is unavailable. Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Necessary Accounts for DCOM and Firewall Security Settings

Issue Need to use a Xenta I/O module on another channel from the base device Product Line TAC Vista Environment Xenta I/O Modules Xenta Programmable Controllers LON Channels Cause Using traditional I/O modules you are not allowed to span channels when placing your base unit and I/O modules. Resolution Use the 421A/422A or 451A/452A models. You can span channels by using SNVT based communication rather then Xenta group communication. You will be required to bind the values to the base unit. See Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node for more information on configuring the Xenta I/O modules for stand alone operation.  

Issue How to disable credential access on Doors at different controllers using a single variable. Product Line Andover Continuum Environment Continuum Access Control Cause Require a method of securing multiple Doors at the same time. Resolution The best way to secure a number of Doors from a single variable is to use the Door Force Lock Schedule attribute in the Door object. This is accomplished by adding a numeric to the attribute on the Options tab of the Door object; IMPORTANT: The attribute name Door Force Lock is misleading, it DOES NOT lock the door in any way, all it does is disable credential access at the door. For Area/Door Lockdown refer to the linked KB article And also on the Entry Reader or Exit Reader tabs, ticking the checkbox under either Normal and/or Comm Fail for Door Forced Lock Schedule. Setting this Door Force Lock Schedule field to a local or remote InfinityNumeric point will provide the following conditions: When the Numeric is on, access is permitted to all personnel by card swipe and/or keypad entry. (Allow use of the door.) When the Numeric is off, card reader and keypad access are denied to all personnel. (No Access) You could have this numeric located in a central controller and all the rest of the controllers reference this numeric from the Door objects. No other points or plain English is required. If you want to ensure that the updates are received, you can force the IE entry for this numeric to update on a regular interval, see Use just one schedule to control doors or access to areas across different controllers that discusses how to accomplish this.  

Issue How to do alarm escalation in Continuum? Product Line Andover Continuum Environment PEAlmFunction, PERtnFunction Cyberstation Alarm Workstation PE function Cause The customer requires the ability to time how long an alarm is active, and based on its status (acknowledged-unacknowledged), escalate the active alarm, by email or other means. Should the alarm be acknowledged in time, the escalation does not occur. Resolution One method is to use the PEAlmFunction and PERtnFunction in a Workstation Program to capture the various alarm conditions off the alarm stack to trigger the activity that you want. As an example, the PEAlmFunction could be used to initiate a timer for the alarm by recording the time of the alarm and the alarm point. The PERtnFunction is then used to clear this recorded information if the alarm is acknowledged. A Workstation program is then used to constantly monitor this alarm information and comparing the recorded alarm time to the current time, if this is above the escalation time then a numeric is set to trigger another alarm that is then escalated. For details on how to configure the PEAlmFunction and PERtnFunction, consult Can Plain English interact with the Continuum Alarm Engine?

Issue When accessing Webstation through Internet Explorer, receive the error “8000401A. Code:-2147467238” Product Line TAC Vista Environment Vista Server 5.x and Webstation. Internet Explorer Windows 7 Cause Improper DCOM settings. ASP.NET not installed Incorrect Remote work station License used Resolution Set DCOM settings as per Vista Installation Manual (04-00001-04) Section 3.6. ASP.NET Start - Controlpanel- Programs - Turn windows feature on or off Navigate to Internet Information Services - Word Wide Web Services - Application Development Feature Make sure ASP.Net are checked, if not install it.Try webstation again. Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET is a link to a tool that can assist with setting DCOM and ASP.NET   Ensure correct Webstation licenses are installed.  Below are the options available.   0-008-8270-1      "Vista 5.1 Web station 1 CAL - One concurrent user license for Web station 5" 0-008-8271-1      "Vista 5.1 Web station 3 CAL - Three concurrent user licenses for Web station 5" 0-008-8272-1      "Vista 5.1 Web station 6 CAL- Six concurrent user licenses for Web station 5" 0-008-8273-1      "Vista 5.1 Web station 12 CAL- Twelve concurrent user licenses for Web station 5" 0-008-8274-1      "Vista 5.1 Web station Unlimited- License for unlimited users for Web station 5"

Issue Where to obtain the documentation for I/A Series G3 software. Product Line TAC IA Series Environment I/A Series G3 software and hardware Cause Documentation is provided as a part of the software package.  Resolution The current documentation for any release of the I/A Series G3 software (except for proprietary drivers) is installed with the full software installation.  The documentation can be found in the docs folder under the \Niagara\niagara-x.x.x\ installation folder. Refer to Documentation for the I/A Series G3 Schneider Electric proprietary drivers for information on the availability of the I/A Series G3 Schneider Electric (TAC) proprietary driver documentation.

Issue LonWorks Device is Offline in Vista, but Online in LonMaker. For Xenta Programmable devices refer to Xenta Programmable Device is Offline in Vista but Online in LonMaker. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation LonWorks Device Cause If the Vista database has some LonWorks devices that are not communicating, one cause could be due to changes in the system such as moving controllers to a new channel for example. Updating the Vista database with the system plug-in might not fully overwrite all the node properties causing the device not to communicate in Vista Workstation even though it is communicating in the LNS database. Resolution Delete the LonWorks device from the TAC Network in the System plug-in. "Update Vista Database" in the System plug-in to remove the device or devices from Vista Workstation. "Update TAC Network" to add the devices back to the TAC Network. "Update Vista Database" again to add the devices back to the Vista database.

Issue Database initialization completes with errors Product Line Andover Continuum Environment Cyberstation installation Cause When running database initialization you will need full access to all of the database. Otherwise you may see errors similar to the following: Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'syscategories', database 'msdb', schema 'dbo'.> Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the procedure 'dt_IsColumnDifferent', because it does not exist or you do not have permission.>   Resolution Ensure that the Andover97 account has DBO privilege to the ContinuumDB, if not run the "Change DB Owner" query to restore Andover97 as the DBO, see Unable to Initialize Continuum Database following installing no SQL instance.   The above errors relate to setting up the SQL Server Agent Jobs that are held in the MSDB part of the database. Check that Andover97 does have the user mapping to this part of the database as per the following screenshot:     Also ensure your Windows User account has the required Administrator privileges to allow full access to the SQL database and its files.

Issue Video of DigitalSentry system can't be seen in I/NET. Alarm of Endura system, for example Motion Detection or Video Server Offline can't be shown in AMT. Product Line Pelco, TAC INET Environment I/NET 2.41 Cause The possible cause is that when installing SarixSDK of I/NET 2.41, there will be an error: Error 1904. Module C:\Program Files\Pelco\Common Files\IntegralPelco4600 dll fail to register. HRESULT-2147220473. Resolution The possible resolution is to uninstall the SarixSDK, delete the Pelco folder in Program Files folder and reinstall the SarixSDK. The error should disappear during the installation. And then video and alarm should be able to appear in I/NET. For more issue about video that can't be seen in I/NET, refer to Video in Endura/Digital Sentry System Can't be Shown in I/NET.

Issue When starting Vista software (other than Vista Server) an error appears stating that the license has expired. lc_checkout failed: Feature has expired. Feature: Menta.View Expire date: 31-May-2011 License path: C:\Program Files\Schneider Electric\License Files\Demo_5_1_31_may_2011.lic FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "acresso.com". Product Line TAC Vista Environment Vista Workstation Menta TGML Editor Vista Webstation Cause The temporary trial license for Vista has an expiration. If Vista returns an error stating that the license is expired this may be due to one or more of the following reasons: The temporary license file being used has indeed expired Vista was pointed to a temporary license file that has now expired rather than being pointed to the license files folder The computer date is set incorrectly Resolution Start by checking to see that the computer date is set correctly. If it is set to a future date beyond the expiration date of the temporary license file this will prevent Vista from starting up. Check to verify that the temporary license file being used has not expired by opening Windows Explorer and browsing to the following folder: C:\Program Files\Schneider Electric\License Files or C:\Program Files\TAC\License Files if this is an older installation. The expiration date of the file is part of name of the file. For example, Demo_5_1_31_aug_2011 expires on the 31st of August, 2011. The terminal services licenses need to be updated every two weeks and the expiration date can also be found in the file name in a week-of-the-year format. The easiest way to find the exact date is to open the license file in a text editor  and the expiration date can be found in the first line. For example, the first line of the license file Demo+TS_OK_5_1_valid_through_week32_2011 is: "FEATURE Vista.Workstation taclic 5.1 14-aug-2011 uncounted \" therefore this license expires on the 14th of August 2011. If the exact license file rather than the license location was specified during installation, Vista may not be able to find a new temporary license file once the old one expires. The location where Vista looks for the license should be cleared out by following the steps in the resolution of Switching from the Demo license to the site License in Vista 5.1.7 or older. Once the registry value has been cleared Vista will ask where the license is found the next time it is started up.

Issue Drayton Theta ll ES4 Optimiser Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Optimiser Controller Theta ll ES4 Cause Obsolescence of Drayton Theta ll ES4 Optimiser Controller. Resolution Please note that the Satchwell SVT controller is no longer available, and that the only possible replacement is the DC1400. Please refer to What is the replacement for the SVT controller range? for more details.  Replace Drayton Theta ll ES4 Optimiser Controller with Satchwell SVT Optimiser Controller.  N.B.  Two models of the Satchwell SVT Optimiser Controller are available :-  SVT 4201 with Analogue Timeswitch  SVT 4251 with Digital Timeswitch, Details of the Satchwell SVT Optimiser Controllers may be viewed here. It should also be noted that the associated Drayton Theta ll ES4 Optimiser Controller Sensors are obsolete.  These Sensors are not compatible with the Satchwell SVT Optimiser Controllers and must therefore be replaced.  Unlike the Drayton Theta ll ES4 Optimiser Controller, which requires the installation of both an Outside Air Temperature Sensor and an Inside Air Temperature Sensor, the Satchwell SVT Optimiser Controllers require the installation of a Inside Air Temperature Sensor only.  A STR 614 Inside Air Temperature Sensor is packed with the Satchwell SVT Optimiser Controller when supplied new :-   Details of the STR 614 Room Temperature Sensor may be viewed here.

Issue Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147) lcaErrNsLicenseViolation 147 LNS license access failure. Product Line TAC Vista Environment LonMaker, NL220 LNS Network Cause Feedback from Echelon on this error message. A variety of conditions may cause this error. Some relate directly to internal licensing components. For example, the license DLLs may not have installed properly, the files that identifies the license (nsseng.exe for the LNS Server, lonmaker.DSL for LonMaker) do not exist, or the Crypkey licensing components (crypserv.exe and ckldrv.sys) are not running properly. You can resolve these problems by deleting the files that may be causing problems, and re-installing LNS. The license DLLs, as well as the crypserv.exe and ckldrv.sys files, can be found in the Windows 'LNS Licenses' folder, and the Crypkey files can be found in the Windows 'system32' folder. Note that you must stop the 'CrypkeyLicense' service and 'NetworkX' driver before deleting the Crypkey files. Certain conditions on the PC operating the license may also cause this error. For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key. If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC. Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits. In this case, you need to purchase additional credits for the license. For more information on licensing, see Chapter 13 of the LNS Programmers Guide. Resolution It is very likely that you have corrupted LNS Credits. To determine if this is the case and how to solve it please reference Corrupted LNS Credits.  

Issue How to protect an OAT sensor from the sun? Product Line Field Devices Environment Outside Air sensors, Outdoor Temperature Sensor STO100 System Vista, Xenta STO200 System I/NET STO500 System Continuum STO600 System Satchwell STO600D System Drayton STO300 Outdoor temperature transmitter ETO100, ETO200, ETO500, ETO800 Cause Direct solar heating will affect the outside temperature reading. Resolution We do not supply sun shields for an Outside Air Sensors as there should never be a requirement to fit one. The Outside Air Temperature sensor for a building should always be fitted to the North side of the building where it will not be in direct sunlight (or the South side in the southern hemisphere). The temperature on the East, South or West sides of any building will always be higher than the North side (in the northern hemisphere) and give inaccurate readings if the sensor is mounted there. Also any sort of sunshade will also act as a shield to retain the heat also giving an erroneously high reading. For sites like weather stations where the measurements are to be taken in a field installation a Stevenson screen could be used, these are available from specialist instrument suppliers. A web search should provide local suppliers. Also see Recommended locations for Temperature Sensors, Valves, and Actuators for further details on sensor location.

Issue Problems installing Vista Webstation 5.1.5 or newer Product Line TAC Vista Environment Vista Webapps (Webstation) 5.1.5 Windows 2008 Server 32-bit or 64-bit. Cause In order to install TAC Vista Webstation successfully on Windows Server 2008, there are a number of steps and prerequisites to be checked. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: PC Preparation – Only if you can not access the Run as administrator context-menu! Log in as an administrator and create a new administrator group (eg. VistaAdmin) and add a user to this group. By doing this you will be able to access the Run as administrator context menu later on (users added to the Windows administrator group do not always receive full administrator rights). Install IIS 7 and ASP.net Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click Next and then click Install. NOTE FOR WINDOWS 7 USERS! Whilst Windows 7 is not officially supported for running Webstation it may be used in a test environment. It's important to note that the IIS and ASP.net installation is slightly different - the user is not asked to add roles, the user is asked to add windows features (see screenshot below). Ensure .net framework 4.0 is installed Open Server Manager and select Features. Scroll down and ensure .net framework 4.0 is installed. If not: Open Internet Explorer. From the menu select Tools\Windows Update (Safety\Windows Update in IE8) Run windows update and install .net framework 4.0 Install TAC Vista Server and any hotfixes Install TAC Vista Webstation and any hotfixes As administrator, register ASP.Net version 4.0 Click on start and then All programs\Accessories. Right-click on Command Prompt and select Runs as administrator. If using 32-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis. If using 64-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis. Ensuring that the directory is set to C:\ copy the file path into command prompt and the add the following text : aspnet_regiis.exe -i -enable Press Enter Confirm the installation was successful Click on start and then type inetmgr in the search box. This will open IIS manager. Expand the hierarchical menu on the left and then expand the Sites folder. Expand Default Web Sites and select Webstation Right-click on webstation and select manage application > Advanced Settings. In the Application Pool field it should say SE ASP.NET v4.0 Classic All that is left now is ISAPI, CGI (see "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server") and DCOM settings (see TAC Vista Installation Manual or Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET). License problem: Webstation - No license Available

Issue Advice on the configuration of a Sigma DNN (Distributed Network Node) when connecting it to a "Flat" Ethernet network. The DNN provides a communications route to Sigma controllers connected to an Ethernet or ARCnet sublan. Product Line Satchwell Sigma Environment Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice. Resolution A "Flat" Ethernet network is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. On this type of network the DNN will only require an IP address and Subnet Mask to be entered. This information and details of the DNN's "Default Server" are added to the device using the SDCU (Sigma Device Configuration Utility). If the DNN has RIP (Routing Information Protocol) enabled then it will broadcast the route to the sublan onto the network, if RIP is not enabled, then a persistent route must be added to the Sigma server. Please refer to Persistent routing on the Sigma server for more information.  To modify the DNN RIP settings, use the Pocket Terminal programme. RIP is enabled by default. To disable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPD 5 and select send. To enable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPE 5 and select send. To review the status of RIP Enter RIPS and select send

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 There is no clear guidance on how to handle the SNMP settings for TAC Xenta Servers Product Line TAC Vista Environment TAC Xenta Server TAC XBuilder SNMP Cause Previously the SNMP feature has not been widely used and has not been a security concern. There are two types or flavors of SNMP. One is for browsing a device to get information about it (SNMP Agent), and the other is to automatically send alarms from a given device to a central alarm system (SNMP Alarm Trap). Now according to reports from the field, IT departments are starting to get concerned about the SNMP feature in Xenta Servers. A general overview of how SNMP can be used maliciously for intrusion can be studied here. Normally the IT department requests that: The default community string is changed SNMP is disabled Here is an example of what you see when you browse a Xenta Server (having the correct Xenta Server mib file) using a SNMP browser such as "MIB Browser" from iReasoning Here is an example of alarms received from a Xenta Server via SNMP Resolution All (or most) SNMP settings are changed through TAC XBuilder First step is to change the default community name. If the community name is either "private" or "public" (the latter is default), it can be browsed without knowing the name. You simply change the name in "Community Name" and "Trap Community Name". Download all project files to the Xenta Server afterwards. Now when you try to browse the Xenta Server from the SNMP agent without first defining the community name, you will not be able to retrieve data. Next, we can disable the SNMP Alarm Trap. Download all project files to the Xenta Server afterwards. After that, alarms will not be sent to the IP address configured. Following here are advanced steps to change the ports used for SNMP (161 and 162) If the settings described above are not enough, we can change the port number used for SNMP. This is however a little more complicated. You need to connect to the Xenta Server using FTP (Note that the FTP access may be disabled, refer to Disable FTP in the Xenta 5/7/9xx Controllers if unsure how to enable this), and fetch the following file: /sys/system/snmp.cfg Open the file in Notepad Change the two port number as below - you can choose other port numbers, but it is crucial that they are not the same as any other ports used by the Xenta Server. Upload the changed file to the same location on the Xenta Server Download the project from TAC XBuilder, choosing to download all files You now get this message Here you must click "Target system" or the changed settings are overwritten Note that the port numbers defined in XBuilder have not changed yet Save the project and close XBuilder Open the project again You will now see that the port numbers have the value you defined in the file earlier Now when you try browsing the Xenta Server with a SNMP tool, you can no longer connect on the default port 161

Issue If the PC is shut down or rebooted, Vista Server can be configured to run automatically on startup of the PC. This is not the same as running Vista Server as a service (for information on that, please see Registering/Unregistering TAC Vista Server as a Windows service). The server still runs as an application, but starts once at Windows Startup. Product Line TAC Vista Environment Microsoft Windows Vista Server Cause In the event of a power loss or reboot, the Vista Server will start automatically for the user, which enables trending and event logging, without requiring a manual start of the application. Resolution These instructions are tailored to the Windows 7 environment, but the process is very similar in all Windows versions (add a shortcut to the application to the Windows Startup folder): Open Windows Explorer and navigate to C:\Program Files\Schneider Electric\TAC Vista 5.1.X In that folder, locate Tacos.exe Right-click on Tacos.exe and select Send to > Desktop (create shortcut) This will place a shortcut on the desktop to be used in a later step. Click on Start > All Programs Locate the folder called Startup Right-click on Startup and select Open all users This will open a Windows Explorer window to the appropriate folder Drag and drop the Tacos.exe shortcut from the Desktop to this folder