Building Automation Knowledge Base

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 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 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 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

Issue When Vista Server is running as a service how do you restore backup files? Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause The Vista Server program will not allow you to restore a backup when running as a service. Depending on the nature of the backup it might have to be deregistered as a service to do the restore. Resolution Vista backup is a zip file of the database directory Open Services from the Windows Control Panel. Stop the Vista Server service (TACOS.exe) Unzip the database backup into an empty directory of your choice. Start Vista Server Setup and browse to the directory the database was restored to in the Database folder path of the Vista Database tab. Click Ok. Start the Vista Server service (TACOS.exe) Vista backup is a full Vista backup (FVB) file Unregister Vista Server as a service, see Registering/Unregistering TAC Vista Server as a Windows service. Start Vista Server as a program. Login to the Vista Server program. Use the File\Restore Database option. Browse to the FVB file. Browse to a new folder. Click Ok. Close Vista Server. Start Vista Server Setup and browse to the directory the database was restored to in the Database folder path of the Vista Database tab. Click OK. Start Vista Server as a program. Ensure the database was upgraded. Stop Vista Server. Register Vista Server as a service, see Registering/Unregistering TAC Vista Server as a Windows service.

Issue Sporadic values in Vista or Vista Graphics show up as red X or "Invalid Value" Product Line TAC Vista Environment Vista Workstation Classic Environment Cause Vista is designed to only have one instance of Vista Server running per system.  If two Vista Servers are polling the same equipment, data will not be read correctly. Resolution Configure all machines as a Remote Workstation with the instructions below. The remote Workstation will be networked to the Vista Server you would like to remotely view. To allow for correct communication DCOM setting will also need to be set. See Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for the utility to complete this process. Shut down all Vista programs, including Vista Server Start Vista Workstation You will see this log in screen: Click on "Options" to display this screen Change "[Local Server]" to the IP address of the machine with Vista Server running Enter your username and password and select OK 

Issue Downgrade SQL 2008 to SQL 2005 Restore from SQL 2008 to prior version. Product Line Andover Continuum, TAC INET, TAC Vista Environment SQL 2008 used by Building Management Software Cause Have database loaded on one machine using SQL 2008 and would like to move or change to SQL 2005 Resolution Golden Rule: A SQL 2008 database cannot be downgraded or restored to a SQL 2005 version. It is not possible to downgrade a database or a database backup. The SQL schema will not allow it.  For your current version of SQL: C:\Program Files\Microsoft SQL Server \80, \90, \100 Folders are the client tools. 80 = SQL Server 2000 90 = SQL Server 2005 100 = SQL Server 2008 How ever, it is not a rule. Since 2008 creates both 80, 90. The only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.    For other SQL options related to I/NET, please visit SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL.

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue Using STR-350 Bypass button as On/Off button in Classic Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause Sometimes on/off function is needed when using STR 350/351 to start or stop a device. Resolution Following the steps below to realize this function in Classic Network: Create a Menta file and Click "Add STR Module" in the Device Specification. In the Bits field of HVAC settings, change the value of the last 3 rd bits of the first line from "0" to "1". This bit is to switch the using Bypass button as on/off function on. Create an STRIN and STROUT module. Bind the STRIN to OccManCmd variable, while bind the STROUT to EffectOccup. Connect the STRIN to an real DO point to control the start/stop of device. But an calculation is needed because when the button is off, the value is 2 while the button is on, the value is 3 instead of simple 0/1. Also connect the STRIN to STROUT to make the output synchronize with the input, like the program below. You can also download the sample from here. For the application used in the LNS network, refer to the Using STR-350 Bypass button as On/Off button in LNS Network.

Issue TAC Vista SQL maintenance repeatedly fails. Not just once or twice, but on every attempt. Microsoft Management Studio View of error Vista Workstation view of error Environment TAC Vista 5.1.7 or newer. Cause The SQL maintenance feature was added to Vista in version 5.1.7, to regularly database defragment the database and prevent the follow-on effects of a fragmented database. This scheduled maintenance can fail for a number of reasons. Resolution Start by  taking a DSS writer server log using TACOS Tweak. Follow the steps below to do this. Goto the TAC Vista installation folder (C:\Program Files (x86)\Schneider Electric\TAC Vista 5.1.9 by default on 64-bit machines). Locate TacosTweak and double-click on it. Click on the "Category" drop-down box and select "DSS (Registry)". Locate the "DSS Server - Log Level" entry and increase the log level to "7" by entering the value in the value field and clicking the "Set" button. Locate the "DSS Server - Log file" entry and chose an appropriate path. Launch "TAC Vista Server Setup" and go to the SQL maintenance tab. Locate the "Run SQL Maintenance now" checkbox and check it. Click on "OK" or "Apply". Locate the DSS server log file and open it with a text viewer/editor. Search the log file for the following text "Maintenance Task - Starting" and check that the date time stamp is approximately when the "Run SQL Maintenance now" button was pressed. Examine the file carefully and follow the file line for line from this point until you reach "[ERROR] Fatal error : SQL Exception : Incorrect syntax near '('. NOTE: Contact Product Support Services if you are unable to interpret the log file or see another type of error than that described above. Once confirmed, launch Microsoft SQL Server Management Studio and follow the steps below: Locate the "taclogdata" database. Right-click on it and select "Properties"  Locate the "Options" tab and set the compatibilty level to SQL 2008 (or SQL 2005 if that is the installed version). Don't forget to set the DSS Server log level back to "5"!   A tool to simplify this process can be found here. Please note that this is not an official Schneider Electric utility.  

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue When opening LonMaker the LonMaker Menu list is not shown in Visio. Product Line TAC Vista Environment Echelon LonMaker 3.xx Microsoft Visio 2002, 2003, 2007, 2010 Microsoft Windows XP SP3 Cause Echelon LonMaker was not installed with Administrator rights or some of the default security settings have been changed. Resolution Older versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Go to the Tools menu > Options and then select the Advanced tab. Click the File Paths button. (For LonMaker 3.1, go to Tools > Options > File Paths) In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. The next setting to check is the Macro Security. Go to the Tools menu > Options > and then select the Security tab. Make sure that all of the below options are selected. Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events   Newer versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > All Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Select "Options" on the left hand side of the window. Click on the "Advanced" section and scroll down to the bottom. Verify that the "Enable Automation events" box is checked. Click on "File Locations..." In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should be DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. Uninstall LonMaker and reinstall with the administrator account used to log into Windows. The following articles have information about another problem that can cause the same issue: Visio menu not displaying properly after installing Lonmaker 3.1 with Visio 2002  Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst"  There are two other things you may try before uninstalling, that have solved the issue in some cases: Right-click any toolbar, Choose Customize > Toolbars tab, Choose the Menu Bar, Choose Reset Remove all registrations in the Tools menu, click Options, and then on the Advanced tab, click File Paths.

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.

Issue Is it possible to see how many users are logged in to Webstation? Product Line TAC Vista Environment TAC Vista Webstation 5.1.X Cause The number of users logged into Webstation at one time is limited by the number of available licenses.  Need to have a way to monitor this resource. Resolution There is no built-in function in TAC Vista Webstation to see how many users are logged in at a certain time. The only way to see how many users are logged in at the same time is to use the License Server Webpage. There it is possible to see how many Webstation licenses are in use. To access the License Server webpage: Open a browser and type in localhost:8888 Open the "Dashboard" and click on "Concurrent" See also Using Lmtools in Windows Vista/7/Server 2008 for Windows Vista/7/Server 2008 OS.

Issue When downloading a programmable controller with the Vista system plug-in, the process fails and reports the Error 80041195, Info: Communication port not connected. NOTE: Error 80041195 has also been reported when performing a commence communication command in the Vista system plug-in. Product Line TAC Vista Environment Vista Server 5.1.5 Vista System Plug-In 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine. This error has also been observed If the PC is running a a 64-bit operating system which is not supported for LonMaker or NL220. See Echelon LonMaker and Newron NL220 on 64-bit operating systems for more information.

Issue Commission and download command on a controller beneath a Xenta Server in a Vista classic network fails. Error: Completion event-failure, Info: $Address Product Line TAC Vista Environment Vista Workstation Vista classic network Xenta Server Cause This error does not indicate an error with the addressing of the controller.  What it refers to is the reading of parameters from the controller in an attempt to commission and download.  The first parameter it tries to read is the address, and if that fails, the $Address indicates which portion it failed on.  Since $Address is first, this indicates a complete lack of communication with the controller. If this issue occurs with a freely programmable controller (Xenta 280/300/401) under a Xenta Server (Xenta 5/7/913) it may be due to the Xenta Server firmware version not matching the Vista Server version. Resolution Go to the controller and look at it.  The green LED on the front should be solid green. Physically inspect the wiring of the controller.  A shorted LON, for example, would cause this error.  Make sure all wires are terminated firmly. For DDCs under Xenta Servers: Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server. If a Xenta Server's firmware version does not match the Vista Server version then either uninstall Vista Server and reinstall the correct version of Vista Server or reload the correct firmware version to the Xenta Server.

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.  DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE option is grayed out and cannot be selected, as it is not supported on Windows7)..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue Alarms stops coming into Vista from Xenta 280/300/401 in the Lonworks network under a Xenta 913 or a Xenta 701. Xenta 280/300/401 controller goes offline/online in Vista. Unable to disable an alarm from a Xenta 280/300/401 that are under a Xenta 913 running as Xenta Server in Vista. Product Line TAC Vista Environment TAC Vista TAC Xenta 913 TAC Xenta 701 TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 Cause There is no support for adding Xenta 280/300/401 to the Lonworks network under a Xenta 913/Xenta 701 running as Xenta Servers in Vista (even though if it is possible to do it in the software). Resolution Use a different Xenta Server that supports adding programmable Xenta controllers in the Lonworks network. Please see the table in chapter 1.1 of the TAC Xenta Server - Networks Technical Manual or Xenta Server version 5.1.5 and after Major Features.