Building Automation Knowledge Base

Issue Editing TAC Xenta 280/300/401 that has the same XIF file Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta NL220, LonMaker Cause The second method can cause a total mess in the LNS database regarding which Device Template the different devices then will belong to. Resolution Tested both with LonMaker and NL220. If you have several Xenta280/300/400 that has the same XIF file (which is a not an unusual scenario), and you want to edit a few of the MTA files, maybe regarding the SNVTs, then it is recommended to: Edit Device A, Download app and params Device A Edit Device B, Download app and params Device B Edit Device C, Download app and params Device C etc and NOT: Edit Device A Edit Device B Edit Device C Download app and params Device A Download app and params Device B Download app and params Device C

Issue TAC Vista 5.1 installation hangs on installing Video Functions. CPU is at 100% and the installation will never finish. Environment Vista Installation Cause It seems like the MSI process for the Video components sometimes gets into a loop. Resolution Start the installation and let it run until it “hangs" Go into Task Manager-Processes and end the process “msiexec” that is using all the CPU. The installation should proceed and everything should be installed correctly

Issue Lost all Xenta Server trendlog values in TAC Vista Environment Vista Workstation Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Changing a folder name in XBuilder and updating TAC Vista. Resolution If you change a folder name in XBuilder and update TAC Vista, all trendlogs in this folder will be recreated and will have to be started again. This also means that you will lose all the log data.

Issue It is not possible to add graphics to a folder in TAC Vista The binding window can not be opened for graphics in that folder When trying to add a graphic or open the binding window an error message saying “error creating object” is shown. Environment Vista 5.0 to 5.1.1 Workstation I/NET gpg graphics upgraded to OGC OGC graphics upgraded to TGML Cause The problem is that a lot of objects are created in the background when the graphic is upgraded from OGC to TGML, especially if the OGC graphic have been imported from I/NET. The path for an object in OGC can look like this: RGD-link54C-I/NET-54-02-02.08.AI.value.PV The binding name in TGML after upgrading the graphic to TGML will then look like this: WSUS11387.RGDC.I.NET.54.02.02.08.AI.value.PV The binding name in TGML is the problem, every part of the name that is separated with a “.” will be a new object in the background, a user will not see it but it will be in the database. In this case 10 objects are created for one binding. Note: The limitation for a folder is 32000 objects. If there are many bindings in the graphics this number will be reached pretty fast. Resolution Workaround: Change the “-“ sign in the path for the object in the OGC graphic to something else for example a “:”, to do this use the OGC editor, Edit-References. Then the path will look like this: RGD:link54C:I/NET:54:02:02.08.AI.value.PV. You can use any character which is valid in Vista but not used when naming the objects in your database. Now when upgrading the OGC graphic to TGML the binding name will not have dots(.) in it and only one object is created. The problem now is that the signal path in the TGML graphic isn’t valid. So you have to use the change reference tool in TAC Vista to change it back. From: RGD:link54C:I/NET:54:02:02.08.AI.value.PV To: RGD-link54C-I/NET-54-02-02.08.AI.value.PV. Change the “:” sign back to “-“ in the object path. Note: This issue has been corrected in Vista 5.1.2.

Issue Vista IV Webstation licenses are not releasing after logging out of the webpage. Environment Vista IV Webstation Aladdin Privilege Administrator 2.01 Vista IV Licensing 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. Cause This problem appears to be caused by configuring to run Webstation IV under ASP.NET version 2.0.5727 rather then version 1.1.4322 which is the supported version. Resolution Open IIS manager on the Webstation PC Expand the local computer, Web Sites, and Default Web Site. Right click on Webstation and select properties. Click on the ASP.NET tab and change the ASP.NET version to 1.1.4322. It is possible that you might encounter some error messages when you log into Webstation and log out again. If so please run the following commands in a command prompt: C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -c

Issue If you are having an issue where a heavy TGML graphic is taking all your CPU power, you can adjust the TGML FPS (frames per second) in TAC Vista Workstation 5.1.1 and later. Environment Vista Workstation 5.1.1 and later TGML Graphics Cause A very large or complex TGML graphic can sometimes slow the system as it tries to render every object on the page so many times per second. Slowing this down, while decreasing quality slightly, can increase performance. Resolution Goto the this location in the registry editor: \HKEY_LOCAL_MACHINE\SOFTWARE\TAC\TAC Vista Workstation\5.1.1 (Replace 5.1.1 with the current TAC Vista version.) Change the MaxTGMLFPS Default is 15 frames per second. Decreasing this value will decrease the number of times the graphic is repainted in a second. If you decrease it to 10 frames per second, then any animations will travel the same distance, but with fewer repaints, making them appear more choppy, but using less of the CPUs resources. Values below 10 are not recommended.

Issue Customer gets a yellow warning message (a warning triangle) on the values presented in the graphic in Vista. The node is blinking for a while and then disappears. If mouse is held over the node when the warning comes they get message "WSAhost_not_found" This behaviour occurs from time to time and the data that are suppose to shown is then zero. After a while the data is updated again and shows the correct value. Environment Vista IV Workstation OGC Graphics Cause It appears customer is having a local workgroup in the building that runs the application's. There are several computer connected with different OS and known is that several of this computer is using NT. Since this message only occur time to time and only for a brief moment a conclusion be made that it is a network error. Resolution Possible solution: What needs to be tested in the location is what or whom of the computer's that has become the master browser since the master browser is holding the master list of the other computers in the network. NT system's are normally suitable of becoming a Master browser in the network since they are a "server OS" If several of this OS is on the same network a argue can occur between them who should be the master browser and this can be confusing when the clients is sending the network list to the master browser. When the client is sending the list they send it to the "server that responds first. Now when another client asks for information the server that responds first is sending the data, but this time another server can be the one answering first and don’t hold the updated list. A possible solution to this problem is to narrow down what computer's that is master browser's on the network and choose one that always should act as one "mainly a computer that is turned on all the time" If more master browser is needed after that (most common after 32 computers) the master browser will choose one to act as a "backup Master browser". This information can be read about on Microsoft homepage. NOTE: This can be the fault in the system, since the "list" talked about above is updated after a while when the Master browser is asking the client's on the network for a update. So when Vista make's another request of the value it works again since now the list is correctly updated.

Issue Problem when attempting to read/write trends and event. Environment Vista Workstation SQL Cause This could be because of a damaged COM+. Check the Windows eventlog for COM+ related errors.  TAC Vista uses COM+ to host DSS, the interface between TAC Vista server (TACOS) and SQL server, in versions from 4.3.0 to 5.0.1. As always, make sure to backup your computer before tampering with COM+! The COM+ catalog is a catalog of all the available COM+ applications, classes and attributes on a given system. Windows keeps this catalog to make sure that there's consistency between the various COM+ attributes and exposes it through various programming interfaces. If the catalog becomes damaged, programs that rely on COM+ won't work properly (or at all!). One example of such a service that depends on COM+ is the Volume Shadow Copy Service used by (among other programs) the Microsoft NTBACKUP application. NTBACKUP can make backups of system files or other locked files by using Volume Shadow Copy. However, if NTBACKUP fails with an error in the Volume Shadow Copy COM+ service, odds are the catalog has been damaged and needs to be repaired. (Another symptom of a damaged COM+ catalog is when many programs hang continuously for minutes on end, but this is a minor, less well-documented symptom.) Resolution To repair a damaged COM+ catalog, do the following: Locate the file %WinDir%\System32\Clbcatq.dll and rename it to ~Clbcatq.dll (note the tilde). %Windir% is an environment variable that usually translates to C:\Windows. Reboot the computer in Safe Mode. Open the Registry and delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3. Look in the %WinDir% directory for a subdirectory named Registration. Delete Registration entirely, including any files inside it. Reboot the machine normally. At a command line, type regsvr32 %windir%\system32\ole32.dll, and click OK on the acknowledgement that comes up. Open Control Panel | Add/Remove Programs | Add/Remove Windows Components. Click Next to reinstall COM+. You do not need to select any components to add or remove; COM+ is reinstalled automatically as a matter of course. You shouldn't have to reboot after this; the re-registered COM+ services should work immediately.

Issue I/NET shortcut utility in Vista 5.1 does not create shortcuts when browsing in the I/NET link. Environment I2V Integration Vista 5.1 Cause The shortcut utility will fail if there is a "\" in any of the I/NET point names contained in the .sav files. This character is not a legal character in Vista, however the shortcut utility should replace it with an "_" and it doesn't. Resolution Change any "\" characters to "/" Re-run the wizard.  As always, it is good practice to only use Vista legal characters when integrating anything to Vista. Vista legal characters (space) [ ] _ : /

Issue Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Environment Vista Server Remote Workstation PCs in a network workgroup, not a domain Cause Connecting a TAC Vista Remote Workstation to a TAC Vista Server where both PCs are in workgroup rather than a domain. Resolution It is important to set the right DCOM permissions AND also remember that the Administrator password has to be the same on both PCs.

Issue Getting error message in Vista that Menta is in 'stand alone' mode and cannot edit the .MTA Environment Vista Menta Cause This happens usually when Menta has previously been installed on the system in a "stand alone" fashion and then Vista was installed at a later time. Resolution Go to Start > Run and type "regedit" to open the Registry Editor Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > TAC > TAC Menta Double click the key named StandAlone. Change the value data to "No"   For a 64 bit OS, the path in the Registry Editor is HKEY_LOCAL_MACHINE>SOFTWARE>Wow6432Node>TAC Menta

Issue Issues with some portions of Vista 5.1 on Microsoft Windows Vista Environment Microsoft Windows Vista TAC ToolPack TAC Signature TAC Webstation TAC OPC Server for Danduc Cause Not all portions of Vista 5.1 are supported on Microsoft Windows Vista. Resolution While TAC Vista supports Windows Vista in release 5.1.0 the following programs are not supported: TAC Toolpack TAC Signature TAC Webstation TAC OPC Server for Danduc Note: This is still true for version 5.1.1 despite this only being stated in the Vista 5.1.0 release notice.  

Issue Trend Log Values in Xenta Server are not displayed in Trend graph but there are values if you select view data. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause If the PC time and the Xenta Server times have gotten off, it may appear that there is no data for the selected time interval. Resolution Check that you have to same date and time settings in the Xenta Server and in the PC that you are viewing the trend chart in.

Issue In trend log page in Xenta Server I only see the name for one of the Y-Axis even though I have defined the name and range for both Y1 and Y2 Environment Xenta Server Xenta 511, 527, 711, 731 Trend Chart Cause If you want to display both Y-Axes 1 and 2 you have to have at least 2 logs in the chart. Resolution To see the 2nd Y-Axis you have to use it. Select the log that you want to use the 2nd Y-Axis and change the Display settings.

Issue Error says, "Can not connect to Vista Server" when logging in to Workstation with a certain user. Other users work fine. Environment Vista Workstation Cause If the Authority is set to “No Access” on the global object $SYSTEM, the user can not log in to TAC Vista Workstation. Resolution Log into Vista Workstation using an account that is a member of the $Administrators group (System). Navigate to the root TAC Vista folder in the folders view. Right click on the $System object and select Authority Make sure the Access control list has $Administrators set for Full Control (All) and Everyone set for Read (R). If the authority has been completely removed and logging in even as an Administrator has been disabled, contact Product Support to re-establish a log in to the database.

Issue Having issues adding a SNVT to an existing controller in a NL220 system? Or possibly a new device template is not showing up after the .xif change? Environment NL220 Cause In some cases, when you are uninstalling (or decommissioning) a controller, it get into an unconfigured state, not allowing it to take a download.   Resolution Take the database offnet Use the Tools drop down and Uncheck the "Attached to Network" option. Do an "uninstall" or decommission the controller Browse in the Menta file with the new SNVT to the System Plug-in and NL220 should have a new device template for the controller.   

Issue Editing any time schedule weekly charts in Vista Webstation 4.5 results in the schedule being ON ALL DAY regardless of what changes were specified in the editor. Environment TAC Vista Webstation 4.5 Cause Webstation is configured to use the wrong ASP.NET version. Resolution Open IIS Manager Open the properties window of the Webstation application by right clicking on it. On the ASP.NET tab change the version to 1.1.4322 and click OK. Stop the website and restart it in IIS Manager and the problem will now be fixed.  

Issue Initiate Xenta 102-AX service pin messages (Neuron ID) from an M/STAT It is not required to hit the service pin button on the Xenta 102-AX itself, this can be done remotely from the room stat, provided it has an M/STAT jack (STR-250). Environment Xenta 102-AX M/STAT Cause If the Xenta 102-AX is installed up in the ceiling out of arms reach (which is typical) it can be cumbersome to get to each board to press the service pin button. Resolution Plug in an M-STAT to the room sensor (assuming you ordered the sensors with the M-STAT jack) Hold the service button in for about 5 seconds. This will tell the controller to broadcast its Neuron ID.

Issue Unoccupied mode on an Xenta 102-ES is really shutdown mode. Unoccupied setpoints are not maintained in the unoccupied mode. Heat and damper are forced to 0%. Standby setpoints are used in the unoccupied mode. Environment Xenta 102-ES Cause The structure of SCPTsetpoints includes unoccupied setpoints. That is the only reason they are available for a Xenta 102-ES. Resolution If the controller is in occupied or bypass mode, it uses the occupied setpoints. All other modes use the standby setpoints. When unoccupied, all heat operations are forced to minimum (locked out) and so is the damper. In the end, standby mode may provide more desirable results than unoccupied.

Issue Recover deleted graphic files Environment Vista Server TGML Graphics Cause You can recover graphic files deleted from your Vista database. Resolution TAC Vista stores a cache for quicker opening of graphic files. C:\Documents and Settings\your_initials\Local Settings\Temp\TemporaryGraphicFiles C:\Documents and Settings\your_initials\Local Settings\Temp\TgmlCache