Issue Reverting to an older version of Vista / Downgrading Vista Environment TAC Vista Server IV Cause Typically done on an engineering PC, downgrading a version of Vista can result in problems since this is not a practice that is rigorously tested. Resolution When restoring a previous version or downgrading Vista the first thing to do is to delete the TAC Shared Folder (Program Files/ Common Files/TAC Shared). After the directory is removed then run the older version install files. If you are using Vista 4.3.0 or higher, be certain that your Computer Name in Instance field of Server Setup/SQL Server is correct, (ComputerName/TACVISTA). You can test the SQL connection to verify it is correct after the installation is complete.

Issue Displaying “??781”, “??782”, ”??787” or similar values. Environment Vista Workstation Cause The "??781," "??782," "??787" are in fact a Vista error codes, however, these codes are not documented. We have used the following approaches to get the device talking. Resolution In Vista right-click and upload parameters to the devices. Right-click > Properties > XIF File, browse in the XIF file to the Vista database.  In LonMaker Recommission the devices and Update the Vista Database. Try to delete the device from LonMaker, update the Database then reinstall the device. There is not a known proven method; these are things to try. Observe the results of the steps and please call if you are unsuccessful at seeing a change

Issue Vista licensing dongle has been lost or stolen from the site. Vista will not run without a valid license. Product Line TAC Vista Environment Vista Licensing Dongle Cause The user dongle has been lost, stolen, or is missing. Resolution You must contact Order Entry for a replacement dongle PN=000857510. Order Entry, Phone: 888-444-1311, E-mail: ccc.service@buildings.schneider-electric.com. See Vista Dongle Guide to get the old Dongle number. Call or email PSS when you receive the new Dongle with both Dongle numbers. PSS will then rehost the license to the new Dongle number. Note: Order Entry/Product Support will be able to assist in verifying which licenses were previously purchased for the site if you do not know.

Issue   LonMaker repeatedly prompting to drop items on a resynchronize command Environment Echelon LonMaker Cause When LonMaker resynchronizes there is an option that is sometimes overlooked to "Automatically add shapes to drawing." If this is unselected then the process may take a very long time to fix the drawing of large networks because of the manual placement of shapes. Resolution Select "Automatically add shapes to the drawing" in the Resynchronize prompt to avoid manually placing each new shape.  

Issue   Microsoft Visio will start stand-alone but will not start if launched from Echelon LonMaker Environment Microsoft Visio Echelon LonMaker Cause Without an administrative login, the software will have limited functionality or not function at all. Resolution Ensure the logged in Windows user has administrative rights.   

Issue If you take a DCUxxxx.sav file from an older version of I/NET Seven and open it up thru the "Work Offline" editor, in a newer version of I/NET Seven (Rev 2.xx) and modify that save file, you will have issues with this DCUxxxx.sav file.  For instance: If you return this modified DCUxxxx.sav file back in the older version of I/NET Seven, you will see changes in the Time Schedules and in other functions. In the "Door ATS" schedules, using a Mipped 7920 board, you will see two new schedule entries with “APB” (Anti-Passback) this could effect the way the door functions. Environment I/NET Site Cause hazards using the “Work Offline” function in I/NET Seven Resolution The Basic rule to follow - If the Sav file came from an I/NET Seven rev (1.xx) system, then use the “Work Offline” from the same I/NET Seven rev (1.xx). The same rule applies for the I/NET Seven rev (2.xx) – stay within the same system. Never try to use any I/NET Seven “Work Offline” function on any I/NET 2000 DCUxxxx.sav files. This will corrupt the I/NET 2000 DCUxxxx.sav file beyond repair.

Issue Upgrading to I/NET Rev 2.13 steps to follow if changing to Server/Remote Client configuration Environment I/NET site with release prior to 2.13 Cause Help with upgrade to 2.13 Resolution Rev 2.13 Introduces a Server/Client option for I/NET Seven. The following steps should be taken if the upgrade is to change from a Filemaster with Equalized Clients to the new Server/Remote Client Configuration. Otherwise the normal upgrade procedure should be used. Note there are new DCU binary files as well as new DPU48k and SCU1284 binary files in this release. The DCU files introduce the Reliable messaging capability and the DPU48k and SCU1284 binaries introduce the door code control option. Open I/NET Config on each Equalized Client Host and drop the equalization. Open Host Masking on each Equalized Client and Clear all masks on all Links. Open I/NET Config on the Filemaster and make sure all Clients have been dropped. Open Host Masking on the Filemaster and make sure masks have been set to receive messages and trends from all hosts and NPRs on the network. Open Network Configuration on the Filemaster and make the Filemaster the Restore Host for all Links. Stop I/NET on all hosts. Start DbCreate on the Filemaster and make a backup. Install I/NET Seven Rev 2.13 on all hosts. Configure one host (Filemaster most likely) to be the Standalone Host which will act as the Server. Configure the remaining hosts to be Remote Clients pointing to the Standalone host. If ID Works was installed on an Equalized Client pc, use Administrative Tools on that pc to configure the System DNS Seven ODBC to connect to the SQL Server on the I/NET Seven Server pc. If there were Seven Trend definitions only on an Equalized Client, they must be created on the Server after the upgrade since Trends are no longer saved on the Remote Clients. Make sure the message and trend archiving is configured as desired on the Server since archives are no longer saved on the Remote Clients. If there were any Network Functions specified only on an Equalized Client they must be created on the Server since the Remote Clients no longer perform Network Functions.

Issue Controlling a SNVT_Occupancy from a Vista Time Chart Environment SNVT_occupancy Vista Workstation Time Chart Cause Vista Server allows you to create local time charts that run a user defined schedule, however the output values of the chart are not directly editable and this can lead to a problem when you are trying to control an occupancy signal which expects a zero for an on value. Resolution To resolve this problem you can send the time chart output to a Menta program, however if you had a Menta application available you likely would have just created the schedule in the programmable controller. If a programmable controller is not available and you only have Vista Server and an ASC controller with an occupancy input you can follow these steps to control the input: Create a local time chart in Vista. Under the general tab change the Paired texts to "1,0" instead of "0,1". Create an object transfer object in Vista. Under the Transfer tab specify the time chart as the From object and set the property to "Auto Value". Set the To object to the occupancy input and the property to "Value". The destination of the object transfer will now reflect an occupancy value based on the time chart. Warning: Vista Server must be running for this connection to work  

Issue "TrendLogWizProfiles not found" error when trying to create a trend log Environment Vista Workstation Trend Log Cause This error can be caused when the Trend Log wizard profiles file has become corrupted. Resolution Browse to the TAC Vista directory in Vista Workstation Double click on the $TrendLogWizProfiles object. At the bottom is the "Source File Name". Click on the data field and click the browse button "...". Browse on your hard drive to $ini directory found in the Vista Installation directory (C:\Program Files\TAC\TAC Vista 4.5.0\$ini for Vista 4.5.0). Select the $TrendlogWizProfiles.xml file and click "Open" and then "Ok". The profiles should now be updated and you should be able to use the create trend log wizard again.

Issue Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. Users have been advised to uninstall and then reinstall MSDE to change the password. Product Line TAC INET Environment I/NET Seven MS SQL Server (MSDE) Cause Need to change password Resolution Use the Microsoft OSQL Utility to change the Sys Admin account (user name, SA). Developed for Course 2002 I/NET Seven Installation and Startup - MSDE SQL Server OSQL Utility; Rev. 1/4/2007, by: M. Myers, TAC-KSG How to change your INetDb SQL Server SA account password using the OSQL Utility: On the I/NET Seven host workstation computer, shut down I/NET Seven completely, including the I/NET Seven I/O Server. Open the command prompt window. Select Windows Start > Run. Type the command, cmd, in the Run window, Open the dialog entry space, and click on OK. Enter the text exactly as is between the quotations. Connect to the I/NET Seven MSDE instance using the sa account. At the operating system drive, command prompt (i.e. C:\>), type the following OSQL command and press ENTER: osql -U sa Enter the command text exactly as it appears, including a dash before the capital U, and the spaces after the l and the U. OSQL will reply with the following prompt: Password: At the Password: prompt, type in the current SQL Server sa account password, and press ENTER. If the log-on command is correct, OSQL will return a line prompt:1>. Type the following string command at the 1> line prompt and press ENTER: sp_password @old = ‘old password‘, @new = 'new password', @loginame = 'sa' Enter the old and new passwords and the SQL System Administrator account name, sa, in apostrophes. Be sure to type each space and comma in the command. OSQL will return a second line prompt: 2> Type the go command at the 2> line prompt and press ENTER: go OSQL will return the password changed message and the 1> line prompt: Password changed.1> To close OSQL, type Exit at the 1> prompt and press ENTER. The Command Prompt will appear: C:\>_ To close the Command Prompt window, type Exit at the command prompt and press ENTER.  

Issue A Xenta 5/7/9xx used as a LON node is not showing data from Xenta programmable controllers, but the values are working in Vista and LonMaker. SNVTs from ASCs are showing up correctly in the Xenta 5/7/9xx. Product Line TAC Vista Environment LonMaker 3.1 XBuilder 1.6 Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause If the LNS database that is browsed into the XBuilder project has programmable controllers with spaces in the names, they will not show data properly. Resolution Go back into LonMaker and rename all programmable controllers that have a space in the name. Example: Use an underscore in place of every space. Update the Vista database Reimport the LNS database into XBuilder Download the Xenta 5/7/9xx

Issue How to create a link to an Alarm/Eventview in a TAC Vista graphic (OGC). Environment TAC Vista IV OGC Graphic Editor Cause This feature is really good if you have multiple sites in the Vista database and need to access events or alarms from one site from your graphic. Resolution In Graphic editor, create a link area. In the link area, browse other graphics. You can also manually write a path to an object. Write the path to your Event or Alarmview object Save the graphic to database Close the editor. Open the graphic in Vista Workstation, click on the link area and your personal alarm view will appear.

Issue Why are transactions/messages showing up in double, triple, etc in I/NET Product Line TAC INET Environment I/Net revisions 2.xx Cause The table linking for each of the reports and establishing a link between RptIndividualHistorz.TenantNdx and the RptCards.TenantNDX Resolution In versions of I/NET when using the I/NET client as a remote client, you must uncheck all the Host Masks on each remote client, otherwise, the Messages and transactions show up multiple times. If not using a Remote Client, the following solution may help you. Refer to the TCON301.

Issue In I/NET 2.13, cannot access NP Routers, when Link Type is equal to Netplus Router (NPR) Environment I/NET Site Cause I/NET 2.13 site and cannot access NP Routers Resolution As a workaround... Edit the configuration profile Choose None, or Direct Link, enable TCPIP, then close the window. Restart I/NET (close I/NET and I/O Server, re-open) Go back to I/NET Configuration. Click modify and then should be able to access the NP Routers button. (You need to do this every time you need to access the Netplus Router directly.)

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue Vista Workstation Alarm: "The SQL database size has fallen below the size threshold" Environment Vista Workstation Cause TAC Vista always monitors the database size of the SQL server and if the size grows bigger than the limit set in TAC Vista, there is an alarm (this is because the limitation in the free desktop version of SQL server MSDE). If the size has been above the limit and returns below the limit again, the alarm reads "The SQL database size has fallen below the size threshold." Resolution Sometimes this alarm will display in the alarm list even though the size never grew above the size limit. If there hasn't been any alarm that says that the size has grown over the limit, the alarm "The SQL database size has fallen below the size threshold" is nothing to worry about.  

Issue Need to deliver I/NET alarms and events to a third party SNMP client Environment I/NET site Cause Desire to deliver alarms/events to third party Resolution There are two mechanisms in the Xenta 527 related to SNMP: MIB - sends a block of data about the status of the I/NET system, LAN re-config, loading etc. SNMP traps - use filters to look at the incoming message stream from I/NET or any other connected system to capture specific messages and send them as alarms to an SNMP server. The default configuration for a Xenta 527 out of the box has alarms enabled but events disabled. There is a check box in the 527 Config Screen that turns this on/off. To change this: Go to your project Add Page/SNMP Trap Page Right click on SNMP Trap Page Select SNMP Trap Filter Select Status Check the Event check box.

Issue The global object $Eventview is missing in the TAC Vista database. How to recreate global objects: $Alarmview $Eventview Environment Vista Workstation Cause The alarm and event view global objects have been deleted or are missing. Resolution Login to the master server by using TAMAIN.exe (located in the TAC Vista program folder) and check if the objects are missing. If they are, please do as follows: Creating a Abstract object e.g. $Eventview in TAC Vista 4.3.1 and later To see the object global eventview in workstation you need to press shift+CTRL+refresh in the object window. Assuming TAC Vista is installed as default: C:\Program Files\TAC\TAC Vista 4.4.1\$cfg Find a file named objtmpl.cfg and make sure to make a copy of that file, just in case Edit the file with notepad and find the string eventview_gl, here you can see how this object is defined. Remove AB , (stands for abstract object), save and close. Open the TAC Vista database folder and open the subfolder called $thisdb. Change the name of the file TacVista.cfg, to TacVistaold.cfg Restart TAC Vista. Start the testclient (testclt.exe) in C:\Program Files\TAC\TAC Vista 4.4.1. Log in, open services, create, ID=EventView Type=eventview_gl push create. Now you have to change the name of the created object to $Eventview. In the testclient(testclt.exe) open services, access. Log in, open services, create, Enter ID=EventView.$name. Push request, now you should see the actual name in the value field. Write $Eventview in the New Value field, press poke. Reset AB for the eventview_gl object in the objtmpl.cfg (the one you removed earlier), save and close.

Issue The Continuum BACNet MSTP devices (b3 controllers) are created and do not appear in the BACNet View of the Continuum Explorer when the "Find New BACNet Devices" is performed.  In rare cases, they are all showing online in Infinity View and stay stable but some of them are not showing in BACNet View at all.  Product Line Andover Continuum Environment Continuum Explorer BACNet MSTP devices (b3 controllers) Cause Most of this issue happens when these BACNet objects are left over in the Continuum database due to an incomplete/unsuccessful delete operation on the BACnet devices that previously existed in the database.  Resolution When this happens, deleting all the objects from BACNet view from Continuum Explorer and redo the "Find New BACNet Devices" will fix it most of the time.  If the issue persists, it is necessary to run the "ACCTrace.exe" utility located in the Continuum directory of the workstation to start a capture.  Wireshark will also need to be run at the same time whilst completing a  "Find New BACNet Devices" again.  Wait for about 5 minutes then stop the ACCTrace and Wireshark captures and save the log files.  Send the log files to Product Support with a Continuum Analyzer log file and the names of the issued MSTP devices which are not showing in the BACNet View. SQL Enterprise Manager will need to be available to fix the issue in the database.

Issue I2V graphic conversion has unpredictable results Environment I/NET Site Cause Sometimes the graphics being generated by the I2V conversion do not seem to match the original I/NET graphic pages or include additional graphic items or the size and position of the recognizable I/NET page is significantly different. These problems are typically caused by hidden items in the I/NET graphic page. Resolution To verify if this is the case open the I/NET graphic page in the I/NET editor and use the View-Page Properties option to change the page size. By increasing the page size to 4 times the current values you should be able to see if any of the unexpected items are present. If these object should not be in the graphic then you can delete them and then reconvert the graphic page after returning the page size to normal.