Issue Error: "Could not load file or assembly 'vjslib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified." when starting TGML editor    Can not start TGML editor. Product Line TAC Vista Environment TAC Graphics TGML editor Cause TGML editor needs Microsoft Visual J#® 2.0 Redistributable Package to be installed on the machine for the TGML editor to run. If this for some reason is missing it needs to be installed. Resolution Go to the following link http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=e9d87f37-2adc-4c32-95b3-b5e3a21bab2c Download and install the program

Issue A floating-point value is displayed incorrectly in a TGML graphic. The presentation field appears to show random numbers. The example shows how the value 11.60 is represented in a TGML graphic. 11.60 is actually stored as 11.600000381469727. In format presentation mode: In none presentation mode: The last 6 digits of the stored floating-point value are seen! Product Line TAC Vista Environment TAC Vista 5.1.X TGML editor 5.1.X A presentation text bound to a floating-point value. Cause Vista uses the PC's default settings for number of decimals, when presenting values in TGML graphics. Resolution To resolve the issue, either set the format property to "Presentation" for the binding object or change the PC's settings to view fewer decimal places eg. 2.

Issue Is it possible to use TAC Vista WebStation over ISDN Routers in a WAN Intranet? Product Line TAC Vista Environment TAC Vista Webstation ISDN Routers WAN Intranet Cause This is possible to configure. Resolution To run TAC Vista Webstation, log into a NT domain. An ISDN router can be a link on an Intranet.

Issue When TAC Vista is setup as an OPC Server, Can you access the Historical Data (HDA) from TAC Vista SQL DB Product Line TAC Vista Environment TAC Vista OPC Server OPC Client Cause When TAC Vista is acting as an OPC Server and providing integration with a third party software / device, online and alarm values are all that is supported. Historical data is not supported via the OPC interface. Resolution It is not possible to access the historical data from the Vista SQL database, when using Vista's OPC Server . It may be possible to get historical data with the help of some third party OPC-HDA-Server for SQL software.  This option has not been tested, and issues related to this interface are also not supported. Click on below link to see an example of OPC-HDA Server for SQL. http://www.opcti.com/OPC-HDA-Server-for-SQL.aspx

Issue TAC Vista appears to keep trying to retrieve logs from controllers despite them being offline. This causes a lot of event messages to be created and fills up the log database quicker. Product Line TAC Vista Environment TAC Vista 5.X Older RPU (remote processing unit) under a PLB ( 5751), containing logs to be retrieved by Vista. Cause TAC Vista appears to keep trying to retrieve logs from controllers despite them being offline. This causes a lot of event messages to be created and fills up the log database quicker. Resolution Vista continues cyclically trying to retrieve the log/s even when the RPU under the PLB is offline.

Issue How to back up a full version of SQL (not express)? Product Line TAC Vista Environment SQL 2005, 2008 full versions, i.e. Enterprise, Standard etc. TAC Vista 5.1.X Cause A customer may wish to backup the TAC Vista log database to prevent data loss if the SQL server crashes. Resolution There are 2 options available, depending on the TAC Vista SQL configuration the customer has configured. If the customer has selected "Typical" on the TAC Vista Server setup "SQL" tab, you can configure this through Vista workstation. Right-click on the Server object in Workstation and select "Properties". Select the "Log Backup" tab and configure the backup schedule there. If the customer has selected "Custom" on the TAC Vista Server Setup "SQL" tab, this can be configured through SQL Management Studio (which is free to download from Microsoft, if the customer doesn't already have it). Start SQL Management Studio and connect to the SQL server instance that is being used for TAC Vista. Expand the SQL server in the tree (in SQL Management Studio) and locate the "Management" folder. Expand that folder and locate the "Maintenance Plans" folder. Right-click on the folder and either select "Maintenance Plan Wizard" or "New Maintenance Plan". Configure as required.    

Issue By default, you are not allowed to shut down/restart the TACLIC/TAC License server when logging in to the Flexnet license admin web application from another PC than local. Product Line TAC Vista  Environment TAC Vista versions 5.1.8 and higher, using the web-based TACLIC tool.  Cause A remote shutdown/restart is required when adding/removing/editing license files in the License Files folder. Resolution The following steps should be done on the PC where the license server is located: In the "server.xml" file located in the "conf" catalogue (...\License Server\conf), edit the following string from " stopServerRemoteAllowed="false" "  to  " stopServerRemoteAllowed="true" " Then save the file and restart the license server.   The setting can also easily be changed using the tool called "TACLicenseServer Settings."

Issue Is it possible to save a copy of a TGML graphic in a standard format such as jpeg, bmp etc? Product Line TAC Vista Environment TGML graphics editor 5.1.X Cause For documentation purposes a customer may wish to have an image of a TGML graphic, perhaps in a system reference guide, with explanatory text. Resolution Open the graphic in TGML graphic editor. Select "Export..." from the file menu and then select the file format in the dialogue that appears.

Issue Specific Trend log stops working in TAC Xenta Get estimated values in some trend logs; others are working Trend log is not retrieved from TAC Xenta Product Line TAC Vista Environment TAC Xenta 301 TAC Xenta 302 TAC Xenta 401 TAC Xenta 282 TAC Xenta 283 TAC Vista Cause The issue can be that there is a "Non value" in the log. For example, if you are logging an expression block with division in it and there is a division by 0. This seems to lock the trend in TAC Vista, and no other values can be collected. Resolution In the properties for the log, click on erase log. This will delete all values in the device. Open your menta and make sure that there is no possibility of division by 0.

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.  

Issue TAC Vista reports an error in the Alarm view that no more threads can be created and remote workstations cannot connect to the Vista server. Product Line TAC Vista Environment TAC Vista Workstation Cause This issue occurs when the TAC Vista remote computer that connects to the TAC Vista Server computer is left logged in and the Remote computer goes into hibernation. This causes the TCP/IP Thread between the TAC Vista remote computer and the TAC Vista server PC's to remain in use. Then once the TAC Vista remote computer is taken out of hibernation another TCP/IP Thread is created. Eventually this will use up the allocated thread count and generate an error. Resolution Restarting the TAC Vista Server PC will fix the issue until the TCP/IP Thread count increase to the limit again. The TAC Vista Remote Workstation computer can be setup so it doesn't go into hibernation and remains on, then the TAC Vista log off function works correctly and closes down the TCP/IP Thread. Alternatively change the TAC Vista Remote Workstations to TAC Vista Servers and configure them to look at the mastern TAC Vista server. This configuration uses a different communication setup for Server to Server communications. See the Creating TAC Vista multi-server network Knowledge Base article for further information on this configuration

Issue Not possible to get a Xenta Server / 911 online in TAC Vista. It is possible to ping it and connect to it via a Web browser using ports 443, 80, and Port 1068 is open, but it is not possible to get online in Vista. Product Line TAC Vista Server Environment TAC Vista TAC Xenta 911 TAC Xenta Server Cause The problem, in this case, was that another Vista server was connected to the Xenta Server / 911.  This could have been from a technician or the customer who started Vista with this database loaded and had the device online in their Database. The Xenta Server / 911 will only communicate with one Vista Server at a time and will close the connection if another Vista tries to communicate with it.    Using Wireshark it is possible to monitor this scenario as shown below:  Packet number 57439: Vista is trying to establish communication with the Xenta Server or 911( sending an SYN). Packet number 57440: The Xenta sends an acknowledgment on the SYN from Vista, but with the window size set to zero, this is because the Xenta can't buffer information as a computer does. Packet number 57441: Vista  sends an acknowledgment on the message from the Xenta Packet number 57448: The Xenta sets the correct window size. Packet number 57449: Vista starts to communicate Packet number 57452: The Xenta closes the communication to the Vista server  Resolution Ensure only one Vista server is started when the Xenta server / 911 is included in the database.

Issue TAC Vista database export/import. Description texts are missing when the .zip file is imported. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Export/Import Cause Changes to the object description text fields made in TAC Vista Workstation are not automatically saved in the .mta file. Resolution To make sure that the description texts will be included in a database export (physical structure only): Edit the Xenta application with text description fields added or modified through Workstation. Save the Xenta application to the database. If you do this, the description text will be written in the .mta file and will be included in a database export.

Issue How can a webpage be integrated into Vista graphic pages for a seamless transition between a graphic page and a 3rd party website such as: Static information, such as a site webpage Device webpage (power meters, sensor, etc. Product Line TAC Vista Environment Vista Server 5.x.x Cause The Hyperlink database object in Vista can store a URL address. By linking to this Hyperlink object with a standard link in a Vista graphic page, standard components can be used and support common graphic pages for different sites and reusability. Note:  More complicated integration can be accomplished with javascript, but this requires custom components such as accessing web services such as weather.com data for actual display on your graphic page. Resolution Create a Hyperlink object in the Vista database for each page you want to make available. Use a link in the TGML graphic page to access this Hyperlink object. Clicking the link on your graphic page will display the webpage in the Vista Workstation window. Target Property The target property can be configured for Webstation display to control the window or frame the link is opened in. The options _top, _self, and _parent will be ignored in WebStation and treated as _blank, which will open a new tab or frame depending on your browser settings. If you specify a target frame you must match the exact syntax of the WebStation frame names from the following list: TAC_WebStation_header TAC_WebStation_left TAC_WebStation_contents TAC_WebStation_footer

Issue In many situations, customers need to integrate more than one LNS database into a single Vista database. Product Line TAC Vista Environment Vista LNS LonMaker NL220 TAC Vista System Plug-In Cause This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database. This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database. Resolution Some general rules must be followed when integrating multiple LNS databases into one Vista database. These rules are: You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication. NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack. When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously. If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed. Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server. It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below. The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2. Please follow these instructions: Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.   The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database. As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400

Issue .MTA file not updated .MTA file does not show the correct value when exported/imported The Menta project does not have the correct value when imported into a new database Product Line TAC Vista Environment Vista Menta Xenta OP Cause The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save. Resolution  Below is the correct way to edit a project in a new database.  On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database. Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.  Export the database/project Import the database/project to the new PC Make the desired changes Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file. Export the database/project Import the database/project into the client's PC Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE StruxureWare Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions