Building Automation Knowledge Base

Issue When update Vista database through System Plug-in got error message saying “Update Vista database failed”. Open Workstation, in the alarm window, there is error message saying “unable to request license”. Environment CIRCON Network Integrator or other LNS network builder, customer license file Vista 5 Cause Vista cannot recognize the LNS server license. This happens when you use some LNS network builder besides LonMaker or NL-220, and you are using a purchased license file instead of a demo license file or an engineering dongle. Resolution If you get the “Update Vista database failed” error message in system plug in. Make sure you have done the group binding or redo the group binding. If the issue still exists, check the system plug-in output window and see if there is any error message before the “update vista database failed” message. If not, open TAC Vista Workstation and check the alarm window. If you see the error message says “unable to request license”, this means TAC Vista server cannot file the LNS server license. The TAC Vista demo license or an engineering dongle has a full version of all licenses which includes the LNS server license. You will see a line below in your demo license file: FEATURE Vista.Server.LNS taclic 5.1 31-oct-2010 uncounted HOSTID=DEMO However, the purchased customer license file does not have “Vista.Server.LNS” license included. The solution to this issue is either rebuilding the LNS network in LonMaker or NL-220, or purchasing an engineering dongle or using the demo license file.

Issue In Vista / Menta 5.1.4  it is possible to have illegal characters such as spaces or - in the program specification name of a Menta file. This will cause this $.mta file to fail when transferring to the Vista DB inside of the system plug-in. It will also cause a Xenta controller to never come online if installed in a Vista Classic DB.  Environment TAC Menta 5.1.4 Cause When leaving the program specification blank in a 5.1.4 Menta file, it will automatically be filled in with the name of the entire Menta file when it is saved for the first time. So if you do not fill in the program specification and name/save the Menta file "AHU-1," the program specification will be filled in with AHU-1. This "-" in the AHU-1 is not a legal character and will not be accepted within the Vista DB or the system plug-in.  Resolution When creating a Menta file for the first time, always remember to set the program specification to a name and without any illegal characters (maximum 12 characters). Once you are in the program specification name editor, it will let you know if you have entered proper syntax. 

Issue Remote Serial Port  Driver, RSPD, is not working. Environment Windows 7 Windows 2008 Cause Security in OS . Resolution Install and start the program as administrator. Right click on the program and select run as administrator.

Issue OPC Server setup for TAC Vista will not save the information when you change the user type from Windows account to TAC Vista account. Product Line TAC Vista Environment TAC Vista OPC Server 1.6.1 Cause This is a known issue that requires a specific reinstall procedure. Resolution Install version 1.6.0 of OPC Server Change to TAC Vista login in the TAC OPC setup Uninstall it Install 1.6.1 again. For more OPC Server issues please Vista OPC Server Installation and Known Issues.

Issue If steps used in creating a LNS network are performed in an incorrect order, you can get many errors which can be easily avoided. While this should not replace the Engineering LNS Networks manual  it can be used as a quick reference. Follow this link to access the complete Manual Environment LonMaker 3.X Vista System Plug-in Cause There are several steps to perform in order to create and update an LNS Network using LonMaker. Resolution LonMaker Cheat Sheet Create new LNS Network in LonMaker Set path to Vista DB in Server Setup Start TAC Server Open TAC System Plug-In Drag and drop Devices from Stencils Assign .MTA to Xenta Devices You will be prompted to Resynchronize, say no. Assign I/O Modules Set Neuron IDs Update Vista DB Create Group Bindings Resynchronize drawing (fix up) Download Application and Parameters Commission Base Units and Modules Commence Communication

Issue How to uninstall Privilege software Product Line TAC Vista Environment Vista IV Licensing prior to 4.25 Aladdin Privilege Administrator 2.01 Cause Need to completely remove a Vista IV installation including all traces of Aladdin Privilege Administrator. Resolution Version 2.01 is mentioned in the description below, but process is similar with other Privilege software versions. Also, process may look slightly different in different Windows versions. To remove: Run the uninstaller for Privilege 2.01 Go to the Windows Control Panel and if there is still an entry for Privilege Licenser - if there is - remove it Delete the Privilege directory (default location: C:\Program Files\Aladdin). Go to the system32 folder and delete the directories PLog and PData. From the same folder, delete the files: PLInst.exe, PLockDiag.exe, PLServ.exe, PLAdmin.dll, PLCLNT.DLL, PLEsd.dll, PLInstall.dll, PLLG.dll. Run Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems and delete Privilege Licenser. Go to HKEY_CURRENT_USER\Software\Aladdin Knowledge Systems and delete Privilege Licenser. Reboot and reinstall.

Issue During installation of Privilege software, the following message appears: "Critical file not copied!: c:Windows\Temp\~~IEWS~0\PLApiLangEng.dll" Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Error during installation of licensing software. Resolution Delete the “PLApiLangEng.dll” file that is located on your PC. (It will be reinstalled during the installation process below) Uninstall Privilege and TAC Software from the PC Reinstall Privilege and TAC Software.

Issue "License software is damaged. Contact product support." error when installing Privilege Administrator license file. Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause The file has been compromised during transfer. The file was generated with errors. Resolution The license file or its digital signature has been damaged.   Contact Product Support. Ask to resend your .plf it in a zipped format for better protection. 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 Get message "Could not open or create file.: AC_Xenta_721.cfg" in the Xenta Server error log and in TAC vista event log. The message appears about every 10 seconds. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731 Cause This is a defect in the software. Resolution This happens if you use the internal online signal e.g. as the input for an alarm. Take out the references to the internal online signal

Issue In LonMaker, an incorrect number of targets were selected when creating a connection resulting in NS Connections #1 lcaErrConninvalidTargetcount error. Environment LonMaker Vista Cause In LonMaker, an incorrect number of targets were selected when creating a connection. Resolution You must specify at lease one and no more than 25 targets when adding members. To add more members, you must invoke the Connect method multiple times.

Issue How to add another TAC Vista server node into an existing server in TAC Workstation. Product Line TAC Vista Environment Vista Workstation Cause Multi-sever Vista system is the system which has more than one Vista Server in the network. One Vista Server will be assigned as the master and the rest will be assigned as slaves. The order of setting multi-sever system is very important in order to make the system work properly. Common mistakes are: Vista servers have different versions. Adding slave computers before adding the master computer. Using same names of Vista servers. Using dynamic IP address. Vista Server object names are the same. All folders and objects found at the root level of the servers must be changed to unique names before merging the databases. Resolution Before doing that, please back up all TAV Vista databases on all computers. All computers should run the same version of TAC Vista. Also make sure all your IP networks are functioning. In addition, all Vista Servers need to be the same version. (eg. Vista 5.1.3 server will not be able to communicate Vista 5.1.4 server when they are noded together.) All computers’ TAC Vista Servers need to have different names. The server name can be checked by opening your TAC Vista Server. By default, Server name is the computer name. If the sever name needs to be changed, please following the steps listed below: Go to TAC Vista Server Setup Go to Vista Database tab Under “Rename Vista Server to” text field, type the new name Click ok and start the Vista Server to make sure the name has been changed Choose one computer to be the Master and the rest of the computers will be Slaves. Start by shutting down all instances of TAC Vista Sever and TAC Vista Workstations. Add Slave Servers into the Master Server. Start the Master TAC Vista Sever, and then start its TAC Vista Workstation. Right click on the Vista Server object. Select New>Object>Node. Type $LAN.SlaveServerName. If the Slave Server name is different from its computer name, change the IP/DNS address in the property window. (Note: this step requires a static IP address) Right click on the Slave Server Node and select Properties. Type in the IP address in the IP address/DNS name field. Repeat steps a-e for any additional Slave Servers. Leave the Master Server on, and start the Slave Server. Follow steps 4 a-e for adding Master Server into Slave Server but use the Master Server’s server name and IP address this time. Then, right click on the TAC Server object in Slave Server computer, select Properties. Under the General tab, change the Network Master to the Master Server name. Then click OK. If you have multiple Slave Servers, add the Master Server into each of them. Shut down all instances of TAC Vista Workstation and TAC Vista Server. Restart the Master Server’s TAC Vista Server and its TAC Workstation first. Then start the Slave Servers’ TAC Vista Server and their TAC Workstation. You should be able to view the Slave Servers under Master Server. Note: Master Server can view all Slave Servers’ projects, and each Slave Server can view Master Server’s project. However, each Slave Server cannot see other Slave Servers unless you node Slave Servers to each other. Any change made in Slave Server’s TAC Workstation will be reflected in the Master Server’s TAC Workstation. Vice versa also works.

Issue Upgrading a Xenta 102-AX controller to a higher software version (eg. V2.16) Upgrading a Xenta Sever version (eg. V5.1.4) Error message says: System image is not compatible Environment Xenta 102-AX HW version below 2.0 Xenta Server HW version below 2.0 Xenta 511, 527, 701, 711, 721, 731, 913 HW version below 2.0 Cause This issue is due to Xenta 102-AX and Xenta Server earlier hardware versions. Resolution Check the hardware version of the controller. The hardware version is printed on the sticker with HW X.X on the controller. If the HW label is missing, that means this Xenta 102-AX or Xenta Server is hardware version 1.0.   Unfortunately, hardware version cannot be upgraded. If this error message appears, it means the controller cannot be upgraded to a more recent firmware version.

Issue Xenta 121-FC SNVTs show up in LonMaker or NL220 but are missing in Vista Environment Xenta 121-FC LonMaker/NL220 Vista Workstation 4.5 System Plug-in Cause A problem has occurred with the import of the controller into the Vista database. Resolution In the Vista System Plug in, delete the controller from the TAC Network.  In the LNS network tab, right click on the controller and disable it from being updated in the TAC Network. Update the TAC Vista Database Refresh the Folder View in Vista Workstation.  Verify that the controller has been removed from Vista. In the Vista System Plug in, re-enable the controller to be updated in the TAC Network Move it back into its former location in the TAC Network Update the Vista Database a second time. Go to Vista Workstation, verify that the controller has returned and values are being properly displayed.

Issue How to change the path of the points bound to for all bindings of a TMGL or OGC graphic simultaneously using the Change References command. Environment Vista Workstation TGML Graphic Cause There are many reasons why binding paths would need to be updated.  The network structure could have changed/been renamed.  Or it may be that a graphic has been copied, pasted, and renamed (say AHU1 to AHU2) and now all the points need to be redirected to another unit. Resolution Right-click on a graphic or a folder of graphics in the Folders pane of Vista Workstation, choose "Change References..." In the Change References window, hit the "Search" button.  This will populate all bindings and links in the graphics folder. There is no way to list just the bindings of a single graphic. The full folder is always displayed. Highlight the graphics points that need to be updated -- it is usually best to click on the "Name" header to sort the bindings by graphics pages. Then just one graphic page's links can be highlighted to edit. Hit the "Replace" button. Enter the "Search for:" and "Replace with:" strings.  It is often a good idea to include as many common characters as possible to prevent accidentally destroying bindings. Example:  Instead of search for "AHU1" and replace with "AHU2", search for "-LNS-AHU1-" and replace with "-LNS-AHU2-" If the desired string was found, the "New" column will now be populated with the new path.  Review the newly formed path to ensure no mistakes were made. When verified, commit the changes to the database by pressing the "Save" button at the bottom of the window.  References have been changed in the database.

Issue In-house Vista dongle is broken. Environment Vista 4 Vista 5 Dongle Cause Physical Damage has broken the dongle. Resolution Return the broken dongle to your local orders dept, using the Warranty Claim System, WCS, and get a replacement dongle (component part no 362140040 for Vista 5). Orders Dept should also be able to provide you with information about any eventual cost for this procedure. Part number for a Vista 4 inhouse - 000880460 (no longer available) Part number for a Vista 5 inhouse - 000885000

Issue A list of all the default ports used by a typical Vista system. Product Line TAC Vista Environment Vista 5 TCP/IP Ports Cause Below is a list of some components and protocols associated with Vista 5 and their default port assignments. Resolution TAC Vista 5 Component/Protocol Default Customizable Comment TAC Vista Server and Workstation       TCPPORT 45612 No Vista Server to Vista Server DCOM 135 + dynamic No Remote Workstation LMGRD 27000-27009 Yes License Server TACLIC Dynamic Yes License Server. Will find an available port         TAC Vista Remote Workstation       DCOM 135 + dynamic No Remote Workstation LMGRD 27000-29000 Yes License Server TACLIC Dynamic Yes License Server. Will find an available port.         TAC Vista Webstation Client       HTTP 80 Yes Web Browsing HTTPS 443 Yes Web Browsing         TAC Xenta 5/7/9xx       DHCP Server 67 No Dynamic IP address DHCP Client 68 No Dynamic IP address DNS 53 No Name resolution HTTP 80 Yes Web Browsing HTTPS 443 Yes Web Browsing, Log-in FTP 20/21 No File transfer. FTP Server SMTP 25 No E-Mail SNMP 161 No Network management SNMP Traps 162 No Network management LTA IP 1068 Yes LonWorks Communication over IP. LTA for TAC Vista Variable transfer IP Network 1233 No Peer-to-peer communication between TAC Xenta Servers Variable transfer HTTP 80 Yes Read/write values from Web Browser UDP 9088, 9089 no Xenta Server to Xenta Server data point TX via UDP (>5.15)

Issue Unbound signals in Webstation appear as offline. Environment TAC Vista Webstation 5.1.4 and prior Cause In Vista Workstation, unbound signals are ignored; but in Webstation, and unbound signal is treated as offline.  This may result in a red X across the entire component if any binding is unbound.  This is an inconsistency across the two platforms. Resolution Make sure all signals are bound.  Even if it's a binding that is not used for any display purpose (like a multi-bind .[OBJECT] binding for example). Any signals that are unbound and unnecessary should be removed from components.

Issue After changing password of a user in webstation it is not possible to log in with the new password. This happens on machines were the TAC Vista server in installed, without language pack, on a server that have different regional settings than the operating system language. Environment Windows with regional settings set to another than the OS language. TAC Vista installed without language pack Cause There is a mismatch between localization settings for Tacos server, Webstation and the regional settings on the Windows system. Resolution Make sure you are using the same language pack for Vista as the regional settings on the host are set. If you are using a webserver and change the password via a webstation you can also workaround this issue by changing the language code in the “C:\Inetpub\wwwroot\TACVistaWeb514\web.config”. Look for the entry   The example above uses English settings. Change this to desired localized setting. For instance the culture code for Poland is pl-PL (language-country) and sv-SE for Sweden. Note: It is always recommended to use the correct language pack before changing the localization code by hand in the config file. Having a mismatch between the installed language pack (or manually changed culture code) and regional settings might cause problems with incorrect formats (e.g., for dates, times, decimal character, character sets, etc.).

Issue LDVD: Socket receive error (Error#:53526) in a Xenta 5/7/9xx Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause This error is displayed every time the LON communication is closed down. Resolution This message does not necessarily mean that something is wrong. Check LON communication to make sure there are no other symptoms. This is very minor and common unless it occurs at a high frequency.

Issue A list of I/O for each device can be provided to the commissioning agent. Environment Vista Menta Commissioning Cause A list of all I/O for each device can be used for checkout, or project documentation. Resolution Ensure that the Vista Server is running. The following steps must be done on the computer on which Vista Server is running. Open System Documentation from the TAC Tools folder located in the Start Menu. From the file menu select New List > Inputs/Outputs.  The Input/Output dialog box will open, select Browse. The Object Selection dialog box will open, at the bottom of the window change Object type to TAC Xenta Devices (or whatever is applicable) In the Units field, navigate to through the Vista Server object to select the device for which you wish to produce a list and select OK. Click OK.