Issue Unable to upgrade SQL log database from a pre-5.1.7 database to the new Version 2 format that is used (for new installations and optional as upgrade) in 5.1.7. Get the error message: Test of connection successful. Connecting to TAC Vista SQL database. Checking SQL server version and database size. SQL Server Version: Microsoft SQL Server 2008 R2 (SP1) . SQL Server Edition: Developer Edition (64-bit). Data Allocated Space: XXXXXMB. Data Used Space: XXXXMB. Log Allocated Space: XXXMB. Checking TAC Vista SQL database schema version. Checking user access. Upgrading TAC Vista SQL database from version 1.0.0.15 to version 2.0.0.0. Failed to execute SQL upgrade script. Error : Error 9002, line 585: The transaction log for database 'taclogdata' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Environment Vista 5.1.7 SQL log database - either upgrade when installing Vista or using the SQL Database upgrade tool. Cause There is insufficient space for the transaction log to grow during the upgrade process. It is important to make sure that there is enough disk space available before upgrading the TAC Vista SQL database layout. During the upgrade procedure the database will increase its size with approximately 40%. If a SQL database is upgraded in a Microsoft SQL Server 2005 Express environment the database cannot exceed 2GB in size; the upgrade will not allow it. It is possible to upgrade to a Microsoft SQL Server 2008 Express environment where the database size limit for the upgrade is 5 GB. After the upgrade is completed, this additional storage space is not consumed by any data; the additional storage space will be allocated for future data entries in the TAC Vista SQL database. The actual data in the SQL database will decrease with approximately 30% after the conversion is completed. Do not shrink the SQL database size after a conversion; doing so will cause major fragmentation. Resolution Firstly, confirm that there is enough disk space (at least twice the size of the log database) for the database to grow during the upgrade. Secondly, changes the file settings for the database to allow for the increase in size during upgrade Open SQL Management Studio (download here if required) and locate the taclogdata database. Connect to TACVISTA (default) SQL instance. Expand the menu-tree and then expand the databases tree. Locate the taclogdata (default) database. Right-click on the taclogdata database and select properties. Go to the sub-property menu Files. Change the autogrowth settings for the database log file. Go to the list of database files and identify the log file (file type Log). Click the button in the field Autogrowth. Check the size given in the Restricted file growth (MB) field. Either increase this to roughly twice the size of the database to be upgraded or Click the Unrestricted File Growth radio button. Upgrade the database to Version 2 layout.

Issue Is it possible to get a offline alarm in Vista if  the communication with a LON device is lost? Environment TAC Vista 5.1.7 Cause Vista doesn't have a built-in online/offline detection for LON devices. Vista will set the device offline if it  can't read a value from the device.   Resolution Set the "Watch setting" on one of the values in the LON device to "alarm" or "watched", then Vista will continuously poll the value and set the device offline if it can't read the value from the device.

Issue Can I add the group bindings manually as the option to create group binding in the System Plug-in takes time and controllers are taken offline for the period of the process Environment Lonmaker Vista Cause This is  possible to do and works very well and effectively if you understand the process  Resolution Follow these steps to add TAG 0 system bindings and TAG 1 Xenta bindings to your new Xenta controller. In Lonmaker find the source of the TAG 0 binding buy finding any TAG 0 existing binding. Then right mouse click on the tag number and select Go to reference. This will take you to the source of the TAG 0 bindings. If a list of controllers appear then you are already at the source controller. Then Carry out a connection as normal in Lonmaker on that function block. Right click on the Virtual function block with the TAG 0 source and select the connect option. Select the TAG 0 option under the Hub tab then select the target tab and add the new Xenta controller to the system with the Add FB/SNs button. Then select the TAG 0 in the virtual function block of the new Xenta and click on the Add button. The select the OK button. This will add the TAG0 binding to the new Xenta device with the correct binding type. The next step is similar to the TAG 0 but for the TAG 1. You need to locate the TAG 1 Xenta group that you are adding the new Xenta controller into. Once you have located the TAG1 source use the same connection method as TAG0 but use the TAG1 in the virtual blocks. The final step is to download the added controller and the group master.

Issue When Vista reports are opened in Microsoft Excel, various columns show trend log values as times.  The columns above in green are correct, they are formatted correctly. The column in red is in a time format instead of the expected percentage format. Environment Vista 5.1.7 Microsoft Excel Cause There is a formatting incapability between Vista 5.1.7 and Microsoft Excel. Resolution The formatting issue will be corrected in Vista 5.1.8. If using Vista 5.1.7, Hotfix 18 will correct this issue and can be downloaded here. The work around for this problem is to reformat the affected column(s) before saving or printing the report. To reformat a column in Microsoft Excel, following these steps: Open the Vista report. Select the entire column that has been formatted incorrectly. Right click on that column and go to Format Cells... Under the Number tab, select the format that is desired for these values. Click OK. Now print or save the report. Note: Once this change is made and saved into Vista, the issue may still occur in the future. This is just a way to correct the problem temporarily to view the correct values.

Issue Cannot adjust the setpoint up or down on STR-250, STR-202 or M/STAT that is connected to Xenta 102-AX. Also, effective setpoint may not be changing when device goes from unoccupied to occupied modes. Product Line TAC Vista Environment Xenta 102-AX Plug-in STR-250 M/STAT STR-202 Cause This problem is most often caused by a scenario similar to the following example: A 102-AX is in cooling mode with an effective cooling setpoint of 70°F. An STR-250 stat is connected to the 102-AX and has a stat adjustment range (nviSetpoint.SCPTmaxRnge) of 6°F. This allows the occupant to adjust the setpoint ±3°F from the stat. The occupant is hot and adjusts the stat down to its minimum of 67°F. (3°F less than the cooling setpoint) The building operator decides that ±3°F is too much adjustment range and changes nviSetpoint.SCPTmaxRnge to 4°F (±2 degrees F) from the front end. The effective setpoint is still 3°F less than the cooling setpoint but now the stat cannot adjust the setpoint up or down since it steps in .1°F increments and both 66.9°F and 67.1°F are outside of the adjustment range. Since the stat adjusted setpoint offset is not a visible point and cannot be adjusted from the front end, the setpoint offset will be stuck until the stat adjustment range is expanded to include the effective setpoint and the setpoint offset is changed from the stat. Resolution To correct this problem the nviSetpoint.SCPTmaxRnge should be set high enough to include the effective setpoint. This can be done from Vista and can be found in the VAV_Controller object of the 102-AX or it can be done from the 102-AX Plug-in where it is called Stat Adjustment Range and is found on the Operating Parameters page. The setpoint should be changed at the stat to match the setpoint of the mode in which the 102-AX controller is currently operating. (eg occupied cooling setpoint) The stat adjustment range can then be returned back to its previous setting and the occupant can adjust the setpoint up or down and it will stay within the limit.

Issue When creating Vista trend log or Xenta trend log, there are no data in it. The status on the trend log has already been on. And there are a lot of dump files in the $queues folder of the Vista database folder. Environment Vista Trend log Xenta Trend log Cause There is something wrong the SQL Server database so that the trend logs can’t be stored into the SQL Server and have to been stored in the $queues folder temporarily. Resolution Assign another SQL Server database for Vista. Open the Vista Server setup, and switch to the SQL Server tab. Choose the SQL configuration to Custom, and rename the Log database name to a new one, which is shown as below:   Pay attention that at that time TAC Vista integrated SQL backup/restore function will not be available in Custom configuration.

Issue The delay on and delay off functions do not work correctly inside of the 700 Menta alarm block. Instead of delaying the signal for the configured amount of time, the signal is delayed for a random amount of time before being passed on or turned off. Environment Vista XBuilder Menta Xenta Server 701, 711, 721 and 731 Cause Documented defect in 700 Menta alarm block. This defect has been confirmed in XBuilder 5.1.5 through 5.1.7. Resolution This 700 Menta issue has been corrected in XBuilder 5.1.8. If using a version of XBuilder 5.1.5 through 5.1.7 the following workaround can be used. Leave the delay on and delay off settings in the alarm block at zero. Add a delay block in front of the alarm block. Set the desired delay on and delay off values in the delay block.

Issue Vista user would like to search the network for property value settings on specific input and output points.  Including the ability to search for all physical points that have been forced by operator. Environment Analog Inputs Analog Outputs Binary Inputs Binary Outputs Physical Points Vista Search Function Cause User needs to obtain a list of physical points within a network to monitor values or to see a list of points that have been forced by operator. Resolution In workstation, select the search function icon in the taskbar located directly above the network pain. Select the browse button  located next to the drop down menu labeled "Types of devices and objects:" and a new search window will appear titled "Select Type"  In the "Select Type" window you will navigate through the tree to Points > Analog Point > Analog Input > Analog Input - RPU and check the box on the left. Repeat step 3 for Analog Output, Binary Input, and Binary Output To complete the search for ALL physical points in a network you will select "Search Now".  Once complete your points will appear in the lower view pain in workstation. NOTE: You will select "Forced by Operator" from the drop down picker under Property Value if you wish to search the network for all points that have been forced by operator (Typically, String: "*" and Equal to: "1"). You will select "Value" to get a list of points showing the live values of the points.

Issue Can not edit time schedules (time objects, TSCHI, time object page) in TAC Xenta Server Changes in time objects doesn't get saved No times shown in time object  (no schedules shown in time object) Environment TAC Xenta Server 731, TAC Vista Server 721, TAC Vista Server 711, TAC Xenta Server 701 Cause If there are a time object (time schedule) that has an corrupt definition all following schedules will not work. We suspect that the corruption comes from a upgrade. Resolution To check for corrupt schedules Log in to the TAC Xenta Server Go to Configuration-time objects-View definition. Here is an example of a correct definition and a incorrect definition of the same schedule Once you have identified any definition that looks suspect open Xbuilder Edit the time object that contains the definitions Right click and select "Show events" Take a note of the times you want to keep Delete all schedules Close the schedule editor Edit the time object again and add back the schedules Download the project again.

Issue Trend chart settings aren't saved. The properties dialogue is opened by right-clicking on the open trend chart and then one or more of the settings are changed. After that OK is pressed and then the chart is saved using the save button. Product Line TAC Vista Environment TAC Vista 5.1.7. Cause It appears that the new settings aren't being saved, but by clicking the save button before refreshing the trend chart the current "view" is saved - not the new settings entered in the properties dialogue. Resolution Change the settings as described Click OK when finished with the settings Refresh the trend chart immediately Save it. The view with the new settings will be saved. Another option in Windows 7: Right click on the chart object. Go to the "general" tab Uncheck Autoscale Enter the desired value.

Issue Unable to log in to Vista workstation. Get error message "Failed to init session: Class not registered". Environment Vista 4.XX Cause This normally occurs after having downgraded Vista. The problem is that a number of files are stored in the C:\Program Files\Common Files\TAC Shared folder and a version compatibility problem occurs.  Resolution Uninstall Vista Locate the C:\Program Files\Common Files\TAC Shared folder Delete all the files in this folder Re-install Vista.

Issue The values for programmable Xenta controllers display "Failed to Read Signal" in Vista Workstation. Environment Menta Vista Workstation Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta Server 701, 711, 721, 731 Cause When Menta programming blocks that are specific to the 700 based menta are copied and pasted into regular menta, it will fail to complete a direct connect download. An error will pop up the reads "PARSER_CODE_ERROR". An example would be the RO output, that is a  700 based Menta programming block, being used in place of an AO output block in regular Menta. When performing a normal download through the system plug-in or workstation, the Menta will appear to download successfully. It is this situation that the value column will read  "Failed to Read Signal" for all points. Resolution The correct programming blocks must be used in its corresponding type of Menta. It is a wise practice to not copy and paste 700 based Menta programming into any other programmable Xenta controller. This will avoid accidentally adding a point that is not compatible.

Issue TGML Links or bindings disappear when upgrading to Vista 5.1.7 Environment Vista 5.1.6 or older that is upgraded to Vista 5.1.7 Cause Incorrect configuration of TGML graphic. The TGML editor and engine has been upgraded in Vista 5.1.7 and more checks are in place to detect user errors. There are now checks for both bindings and links without a name. Resolution Ensure that all links and bindings have a name. If a graphic is edited in Vista 5.1.7 a prompt will appear when saving the graphic if a link or binding doesn't have a name.  

Issue Connections between Menta function blocks not been allowed Environment Menta Cause If the rectangle (Dotted line) covers the pixel of the connection point of any function block / output, this stops the mouse from selecting the input connector to allow the connection to be made. This also occurs if you use any of the Comment, Line or Rectangle Menta features and overlay these too closely to the connection point. Resolution Select the rectangle (dotted line), (or overlaying object) and move it away from the connection point as shown below.

Issue Is it possible to pre-define Workstation log-in settings for each user that  logs on to windows on the PC? This would enable each user to be directed to the correct Vista server without any user input. Environment Tac Vista 5.1.X workstation. Cause On some sites it's desirable to restrict access to certain Vista servers. It can also be desirable to pre-configure the server details so the customer does not need to remember it. Resolution The short answer is that it's not possible to pre-define these settings. However it is possible to change the registry HKEY_CURRENT_USER\Software\TAC\TAC Vista Workstation\5.1.7\ODLoginMgr\Settings\CLoginDlg for each user (this requires that the user or IT dept log in with this user account). Access can then be restricted in Vista so that certain user can only access certain servers. Edit the registry 1. Open the startmenu and click on Run... 2. Type regedit and click on OK 3. Browse to the  HKEY_CURRENT_USER\Software\TAC\TAC Vista Workstation\5.1.X\ODLoginMgr\Settings\CLoginDlg. 4. Set appropriate values for CLOGINDLG:211 (show options - 0 = don't show; 1 = Show); CLOGINDLG:217 (server name); CLOGINDLG:5006 (Windows User or Vista User); CLOGINDLG:5016 (Domain if Windows User selected). 5. Attempt to login in to Workstation and confirm the settings are appropriate.

Issue Is it possible to redirect all offline alarms to a certain alarm control object in Vista? Environment Vista 5.1.7 Cause Using the "Configure alarm" function in the Vista server all offline alarms can be sent to a special alarm control object in Vista. Resolution Start with creating a new Change of state object in Vista To create a Change of State Right-click the Vista server node/object Point to New, point to Object, and then click "Change of State - System". Type the name. In the example, "Offline_Alarms". Right-click the newly created Change of State object. In the example, Offline_Alarms. Click Properties. Type a descriptive text. In the example, "Handles alarms for devices going offline". Change the priority. In the example, change the priority to 1. On the Alarm tab, in the Alarm processing control box, type the name of the alarm control object for priority 1 alarms. In the example, Alr_Cntrl1. Click OK. Filtering and Linking an Alarm We can now filter out system alarms ($EE_Mess messages) tripped by devices going offline. The alarm texts contain the word "Offline" and we use this as the filter. To filter and link an alarm On the Windows task bar, click TAC Vista Server. On the File menu, click Log in and log in. On the Configure menu, click Configure Alarms. Click Add. In the Text match box, type the filter mask. In the example, "*Offline*". In the Event object box, click Browse. In the Units list, browse to the Change of State – System object. In the Objects list, click the Change of State – System object. In the example, Offline_Alarms. Click OK. Minimize Vista Server. When a Xenta device goes offline, a priority 1 alarm appears. The alarm is handled by the Alr_Cntrl1 object

Issue When you open a trend you get the following message Environment Vista 5.x.x Cause The period selected in the trend chart does not exist in the trends associated with that chart. In the sample below the trend only store 1 days worth of information and the chart is requesting last weeks information. This would result in this type of error. Resolution Modify the period selected in the chart so that trend values that are logged will be displayed.

Issue Is it possible to sort the Vista Workstation alarms only by date, not by group in alarm viewer? Environment TAC Vista 5.x.x Workstation alarms Cause When you sort the Vista Workstation alarms in the alarm viewer by date, No matter how you sort them they are arranged by date and type OR by groups (Unacknowledged, Acknowledged and then Acknowledged Reset..etc). See the below picture for example; Resolution No, It is not possible to sort the active alarms just only by the date in Vista Workstation alarm viewer. This will sort by groups.

Issue Generating or importing one XBuilder project into another directly from Vista takes very long time Environment TAC Vista TAC XBuilder Cause In v5.1.7, a new feature was introduced that made it possible to import one XBuilder project into another directly from Vista instead of from a file. TAC XBuilder will by default do a project reference check to determine if the project is included in any other TAC XBuilder projects in the TAC Vista database. If it is included in any other project, the user will be notified in the TAC XBuilder output pane. The reference check will increase the time it takes for TAC XBuilder to generate the project; depending on the amount of TAC Xenta Servers that exist in the TAC Vista database. Resolution It is possible to disable this automatic check in the TAC XBuilder project settings. From the menubar click Project and then select Settings... In the Settings dialog box uncheck the box that says Check project references in TAC Vista database.

Issue The following message appears after approximately 30 seconds when you attempt to edit a Menta file from the system Plug-in. Environment Windows 7 Vista 5.1.5, 5.1.6 and 5.1.7 Cause The login screen does not come to the forefront when required Resolution Use the ALT - Tab key combination to scroll through the open windows. Select the logon screen and continue with the normal process.