Building Automation Knowledge Base

Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "tac vista"

View in: "Building Automation Knowledge Base" | Community

2045 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue Privilege software version 2.01 crashes during installation on Windows XP. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Privilege Administrator Incompatibility with XP Resolution Uninstall any previous Privilege Administrator (Please see How to uninstall Privilege Administrator 2.01 software for details on uninstalling the software) Download "Privilege Windows XP crash hotfix" (PS202.zip) Install PS202 by running setup.bat. Install Privilege Administrator 2.01 again.

Issue Errors in Vista Workstation alarm window: "Failed to execute report XXXXX-YYYY, Error in "DDE Execute" command[27]" "Warning logged in B0WARLOG.TXT on node XXXXXX" Contents of B0WARLOG.TXT: "Could not open report XXXXX-YYYY, hRes=[-2147467261]Invalid pointer" Product Line TAC Vista Environment Vista Server Microsoft Windows 7 Microsoft Windows Server 2008 Cause Vista Server does not support running as a service under the local system or interactive user account. A PC account that has local administrator rights must be used to run Vista Server. Resolution Follow the registration instructions for Vista Server in Registering/Unregistering TAC Vista Server as a Windows service when registering TACOS.exe as a service.

Issue Launching Menta by opening an MTA file causes a Buffer Overrun Error The error message: "Buffer overrun detected ... A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated." Product Line TAC Vista Environment Menta Cause Menta's buffer for opening files is limited; if the file you are trying to open by double-clicking has a very long path (of 142+ characters), you will receive the Microsoft Visual C++ Runtime Library Buffer Overrun error message. Resolution Work arounds: Shorten the path to the Menta file. If it is possible to decrease the number of subdirectories or the length of the directory names to make the total path length less than 142 characters, this will correct the problem. Note: Never modify a Menta file name within Windows; only change Menta file names using the Menta application by using "Save As..." from the File menu. (See "Cannot open file" error when opening a Menta file for resolution if this occurs.) If it is not possible or practical to change the path to the file, files with long paths can still be opened by launching Menta using the Start Menu or a desktop icon. Select File > Open and browse to the Menta file, then click "Open". Opening the file via this method will expand the path length limitation to over 200 characters.

Issue Cannot attach the Network interface to Lonmaker database when the Vista Server (Tacos) is started as a service. The error message is that the 'NIC interface is not connected'. Product Line TAC Vista Environment Echelon Lonmaker 3.1 Echelon Lonmaker 3.2 TAC Vista (all versions) Cause When updating Lonmaker and Vista databases as applications, it is important that Lonmaker be started first. Failure to do so can result in issues like this when Vista is reconfigured to start as a service. Resolution To get Vista and Lonmaker running together: Stop the Vista service and unregister it. If using a Loytec interface, set the Loytec Legacy Driver to run as a service (click the Advanced tab in LConfig). Start Lonmaker and attach the correct network interface. Ensure that Lonmaker is online. Start Vista Server as an application. From Lonmaker open the System Plugin. In the TAC Network properties, check that the correct network interface is selected. Update the Vista database. Start Vista Workstation and check that everything is online. Stop Vista and Lonmaker. Reregister Vista as a service. For details of these operations see Registering/Unregistering TAC Vista Server as a Windows service. Also see section 16.3 of the TAC Vista Technical Manual.

Issue Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization Product Line TAC INET, TAC Vista Environment I/NET 2.31 with MSDE Vista 5.1.4 with SQL2005 Express Windows XP Cause When Installing I/NET and Vista on the same PC and MSDE is desired for use with I/NET, I/NET must be installed first. If you are not using MSDE, please see Installation guidelines for installing I/NET and Vista on the same PC. Resolution Completely Remove I/NET, Vista and all versions of SQL and MSDE from the system. See Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL and How to uninstall and completely remove TAC Vista 5 for more details. Begin the I/NET Installation Select MSDE for the database installation. Complete I/NET and MSDE installation Install Vista Start Vista Server Start I/NET Configure I/NET as a Filemaster Build Database or restore from a backup.

Issue Does Vista support virtualization? Will Vista run on a virtual PC, VMware, virtual environment? Product Line TAC Vista Environment TAC Vista all versions VMWare, Player, Workstation and Server Microsoft Virtual PC Cause For many companies, the largest benefit of server virtualization is in reducing the amount of hardware that is required to run all the software needed by the business. Consolidating servers using a virtualization process not only provides savings in terms of how many physical machines must be bought and maintained, but also potentially reduces the amount of physical space that a company needs for its servers or data centre. Resolution Virtualization is a term that allows software in emulating environments, such as VMware / Virtual PC. These software packages emulate a PC environment so that many computers appear to be running on one single machine, thus “virtualization”. The general impression is that the emulation packages work very well. The user must be familiar with the emulating product in order to be able to do the correct settings. No matter if it runs on PC hardware or in an emulating environment, the specific product is supported given the problems are related to the Software itself, but not for problems related to the environment it runs on. Particular note and understanding is required when dealing with multiple applications trying to access a single piece of hardware, such as serial ports, USB and the like. Please see the following TPA-MALI-09-0013.00 for additional information. Also note that Vista Licensing system is NOT supported when using Remote Desktop. Refer to the following article for further details: Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system.

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Issue "Read-only because object refers to a standard file" when trying to change Menta application (.mta file) from TAC workstation. "File object is locked by another application" when trying to edit a Menta application (.mta file) (file is not marked as reserved) Product Line TAC Vista Environment Menta Workstation Cause If a standard file is used, it is not possible to edit the "local" Menta file. Other causes are explained in "File object is locked by another application" error when trying to edit Menta file. Resolution If the referenced file is supposed to be a standard file, locate and edit the file referenced. If the referenced file is not supposed to be a standard file: Click on the more button under the MTA tab in the properties for the device. Uncheck "Reference standard file object.

Issue A service that requires the system to be open has been accessed prior to successfully opening the System object. TAC Vista System Plug-In The system is not open. (Subsystem: LNS, #67) Error: LNS #67 lcaErrSystemNotOpen Product Line TAC Vista Environment LonMaker Vista LNS Cause There are many circumstances that could cause this. For example, if you call the Validate method to validate a network database before opening the system, or if you call the Backup method to copy a network database before opening the system, this exception will be thrown. Resolution If registering or launching the TAC System Plug-in results in the error "System is not open, LNS #67" followed by "TACOSSysPin.Document launch failure Exception occurred," and "lnsplugin.api launch failure," then your LNS credits may be corrupted despite indications that they are not. First reboot and try again. If still fails, replacement credits have to be reordered from Echelon. See description of LNS #147 in Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147). It is also possible to get LNS #67 without having corrupted credits. This has been seen a couple of times on databases that are upgraded from LNS 3.1 to LNS Turbo. It seems to be hit or miss whether the upgrade will cause this issue or not. The Licensing Upgrade 2006 discussed in LNS #147 should be installed. Defragmenting the computer can also cause this corrupted credits with no indication and a TACOSSysPin error. Replacement credits will fix the issue even though there is no indication that they are corrupted.

Issue Does TAC Vista Support MySQL Server? Product Line TAC Vista Environment TAC Vista MySQL Cause User may wish to integrate TAC Vista with a MySQL installation for access to data or reporting. Resolution TAC Vista can not support MySQL Server. It only supports various types of Microsoft SQL Servers. For details, please refer to the compatibility matrix which is available on Exchange Extranet, or refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Adding a Xenta Programmable Controller to an NL220 System Product Line TAC Vista Environment NL220 Cause Commissioning a Xenta programmable controller in NL220 needs to follow a certain procedure in order to prevent various issues from occurring, such as controllers not showing online in Vista Workstation, etc. Resolution Adding a Xenta Programmable Controller to an NL220 LNS system. Preparation: Create the Menta File Install the Controller Adding the Device to the LNS database NL220:Create a Template for the device type. See NL220 Useful Functions and Shortcuts on how to create a template. NL220:Add a node using the correct device Template System plug-in: Assign Neuron ID and Menta file Add and match I/Os if applicable Bring the Device to the Vista Database System plug-in: Update TAC Network Drag controller to an existing group if desired, and delete the now empty group Create group bindings Assign Neuron ID for the I/O modules Update the TAC Network again Check TAC Network Update Vista Database Check that your network is attached and OnNet Download Application and Parameters Bring Vista Db online NL220: Commission and download the device (ignore I/O modules.) System plug-in: Commence Communication (if needed) NOTE: It is very important that you Download Application and Parameters in the Vista system plug in THEN Commission the device in NL220.

Issue There are two sets of terminals on the Xenta Repeater that are labeled identically. Product Line TAC Vista Environment Vista Lon Network Cause The duplicate power supply and communications terminals are internally connected. Resolution The power supply and communication connections can be made either to the upper or the lower terminals as they are internally connected. The extra set of terminals is strictly for convenience purposes. One segment of the Lon network should be connected to the COM1 terminals and the other segment should be connected to the COM2 terminals. The only other wiring required is to connect the Xenta Repeater to a 24V power supply. Wiring Example #1 This is the most traditional wiring schematic used with a Xenta repeater. Segment #1 comes into COM1 and is the end-of-line for a bus topology. A terminator is placed at the repeater. Segment #2 continues on out of COM2, and represents the beginning-of-line for the next segment, thus is also terminated at the repeater. Wiring Example #2 This example is actually the same as Example #1, but is showing that the upper or lower terminals can be used for convenience, as they have electrical connectivity from top to bottom. Wiring Example #3 Example #3 shows Segment 1 coming into COM1 on top and carrying on out of COM1 on bottom. This segment does not get terminated at the repeater because it is not the end of line for this segment. However, COM2 does represent the beginning-of-line for the second segment, and is therefore terminated at the repeater. For more information on how the Xenta Repeater works see the following article: The Xenta Repeater provides signal restoration and conditioning on LON networks.

Issue Xenta 102-ES configuration and wiring for 2 position (on / off) heating actuators or other digital heating control Product Line TAC Vista Environment Vista Xenta 102-ES Cause Wiring for 2 position heating control on the Xenta 102-ES is different than increase / decrease type actuators. Resolution The Xenta 102-ES documentation refers to two position heating control as thermal actuators, thermo or TAO and can be somewhat confusing. The same info applies whether using a two position hot water valve, any on / off type electrical heat (such as baseboard heaters or electric heating strips. Here's what you need to know: If using only one stage of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin or if configuring from Vista Workstation or the OP set nciAppOptions bit 5 to 1 and leave bit 6 as 0. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. If using two stages of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin and select Enable for Secondary Heating. If configuring the device from Vista Workstation or the OP set nciAppOptions bit 5 and bit 6 to 1. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. Only terminal V6 will be switched for second stage of heat. Note: The triac outputs of the Xenta 102-ES are ground sourcing and should be wired accordingly. See Digital outputs (V) on most Xenta 100 series controllers are ground sourcing (voltage sinking) for additional information.

Issue "PSU device driver failed, It may be missing or disabled!” error or “An External installation failed : Hasp" error error when attempting to install Privilege Administrator. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Incompatibility with Windows Server 2003 Resolution Uninstall any previous installation attempts (Please see How to uninstall Privilege Administrator 2.01 software for instructions on uninstalling the software) Download HDD32.zip from Exchange Online located at Previous Vista Software \ TAC Vista IV License System Unzip and run HDD32.exe Install Privilege Administrator again. Only Vista version 4.20 and later is supported for use in Windows 2003 Server. Please observe that HDD32 may also solve some problems when installing Privilege License on Windows XP Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue New laptops do not support hardware for Echelon PCC-10 cards Product Line TAC Vista Environment Laptop Computers without PC Card slots or with ExpressCard Slots Cause Some new Laptops do not come with a PC Card slot or have an ExpressCard Slot that does not fit the PCC-10 card Resolution If the PC does not have a PC or express card slot then use NIC-709 USB Lon Talk adaptor. These are available from Loytec. See the procedure for changing from a PCC-10 LTA to a NIC-709 LTA. If the PC has a express card slot, see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for a solution.

Issue Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding. This can be an issue in a Vista classic scenario using a Xenta Server to do the connection in XBuilder. Product Line TAC Vista Environment Xenta 102-AX version 2.14 or prior Vista Classic Network Cause The Xenta 102-AX version 2.14 and prior requires a true SNVT binding on nviSpaceTemp from an LNS Management software (LonMaker, NL220). The controller does a check to see if there is a true bound value on the nviSpaceTemp and if it does not exist, it reverts to the hard-wired room temperature sensor. When using the Xenta 700, Xenta 500, or Xenta 900 the controller simply connects the desired temp value to nviSpacetemp via a connection object. This is not a true LNS binding and the controller WILL NOT honor the connected value. Resolution Upgrade the firmware of the Xenta 102-AX to version 2.16 or later. Firmware 2.16 allows the use connection objects in XBuilder to send a value to the nviSpaceTemp SNVT of a 102-AX. Download the latest Xenta 102-AX firmware Instructions on upgrading the firmware are located here: Upgrading a Xenta 102-AX to version 2.16 or later.

Issue Error: "Event Receiver Failed - Could not retrieve any events from the event log" Product Line TAC Vista Environment Replacement PC running Vista 4.5 Vista IV Cause This is typical of a <4.5 Vista installation where the original PC running Vista Server has failed. The replacement PC name has not been changed to match the original PC name. It could occur from a name change of the PC or Vista Server after TAC Vista installation. This can be the result of a failed installation of the TAC Vista Config which creates communication issues between SQL and Vista. Resolution Reinstall Vista making sure the PC has the proper name and follows the correct naming convention before you start installing. This will create new users including the proper PC name on the PC and in the SQL server. If the installation continues to fail, send Product Support all error messages along with a copy of the Windows Event Log. Failed to Read Event From Event Log Database - Vista IV may also be of interest.

Issue In a web graphic hosted on a Xenta Server, clicking to change a value displays the dialog momentarily, then it immediately disappears. Product Line TAC Vista Environment Xenta server Cause The Java version is too new or too old. Resolution Make sure The java versions installed have been tested against the installed Xenta version. A Compatibility Matrix can be found on The Exchange Download Center. Or see Software and Firmware compatibility matrix for older versions of the traditional product lines. If the wrong versions are installed, download the correct version and install it.

Issue Error "Critical file not copied! c:\~\PLAiLANGEng.dll" during installation of Privilege License software. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause This error occurs when 'PLApiLangEng.dll' already exists from previous installation. Resolution Uninstall both the Privilege and TAC software Find the existing 'PLApiLangEng.dll' file and delete it (It will be replaced during the installation process). Install Privilege and TAC software again. Please refer to How to uninstall Privilege Administrator 2.01 software for detailed instructions to uninstall Privilege software.

Issue The Vista Remote workstation cannot request the license fro the vista server with the firewall on. If all the ports are opened the license works fine. Product Line TAC Vista Environment Windows 7 32-bit Vista 5.1.6 Cause Even though ports 135 and 27000 to 27009 are open Vista license will not work. The Vendor Daemon (TACLIC.exe) port is by default not specified, and is chosen by the operating system at run time. However, it is possible to specify the TCP/IP port number the daemon use in the license file. Windows 7 on some installations does not assign a port for TACLIC.exe causing this error. Resolution The solution is to manually setup ports for the operation of the license system. This can be done by editing the Vista License file. Open the lic file in a text editor Here is a sample of a standard license header lines. Please Do not delete this comment line. SERVER this_host TAC_HL_ID=608806830 VENDOR taclic USE_SERVER Here are the changes to fix ports for the license system: #Please Do not delete this comment line. SERVER this_host TAC_HL_ID=608806830 27000 VENDOR taclic port=1700 USE_SERVER This will setup up the LMGRD to use port 27000 and TACLIC.exe will use port 1700. See Setting the firewall port 135 for a Vista Server running on Windows 7 for information on how to open ports in Windows 7. You will need to select the ports you have defined in your lic file.

To The Top!

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Privilege software version 2.01 crashes during installation on Windows XP

Periodic report will not run when Vista Server is running as a service

Launching Menta by opening an MTA file causes a Buffer Overrun Error

Cannot attach the Network interface to Lonmaker when Tacos is started as a service

Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization

Running Vista software on an emulated environment

Xenta 102-AX temperature sensors reading incorrectly, very high

"Read-only because object refers to a standard file" when editing Menta from Workstation

The system is not open. (Subsystem: LNS, #67)

TAC Vista does not support MySQL Server

Adding a Xenta Programmable Controller to an NL220 System

How To Wire a Xenta Repeater

Xenta 102-ES configuration and wiring for 2 position (on/off) heating control

"PSU device driver failed, It may be missing or disabled!" or "An External installation failed : Hasp"

Echelon PCC-10 card does not fit in new Laptop PC Card slots

Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding

Event Receiver Failed - Could not retrieve any events from the event log

Xenta graphic - Change setpoint popup disappears within a second

Error "Critical file not copied! c:\~\PLAiLANGEng.dll" during installation of Privilege License software

Vista Remote workstation cannot get license in Windows 7 with firewall on

Building Automation Knowledge Base

Related Forums

Welcome!