Issue TAC Vista interface stops  Environment Vista StruxureWare Building Operation TAC Vista SmartStruxure Interface 1.0.0  Cause When acknowledging an Vista alarm in SmartStruxure, the TAC Vista SmartStruxure interface stops.  Resolution Please download and install the latest Vista hotfix versions for your system from the Exchange.

Issue From time to time TAC Vista Server stops communicating with LonWorks devices and needs to be restarted. Product Line TAC Vista Environment TAC Vista Server LonWorks Cause There can be various reasons for this. One of the reasons can be, that one or more devices is flooding TAC Vista Server with communication, and the communication finally stops. Among other things, this can be due to one or more TAC Xenta's suffering from the rare memory fault issue described in TAC Xenta 401 - Rare Memory Fault Issue - TPA-MALI-09-0011.01, or that the system program in the TAC Xenta device has become corrupt. To identify the issue, make a communications log as described in Start TAC Vista Communications Log, and open the log with the "TAC Vista Comm. Log Decoder". Filter on "C1" messages, and check if there's extensive communication from one or more devices. If that's the case, you have identified that file transfer loop is the issue. Resolution The first thing to try, is to update the system program in the Xenta. Follow article Download an .MOT file into a Xenta Programmable controller for instructions on how to do that. If that doesn't work, replace the Xenta device(s) causing the massive file transfer.

Issue What is the requirement of the PC when installing TAC Vista software? Environment TAC Vista Cause Minimum and recommended hardware and software requirements for installation of TAC Vista and its components. Resolution All minimum requirements are listed in the data sheets for each component respectively. All TAC Vista data sheets and other related documentation is available for download on The Exchange Download Center. Navigate to TAC Vista within The Exchange Download Center Narrow results by Asset types (Manual, Specification Sheet, Release Notes, etc...)

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue The System Plug-In had a failure and when reopened the TAC Network was missing. Environment Microsoft Window XP SP3 TAC Vista 5.1.4 Cause The failure on the System Plug-In has caused the TAC network to be removed. Resolution To reinstate the removed TAC Network in the System Plug-In follow these steps. Ensure that the Vista Database has not been updated with the blank System Plug-in TAC Network view. If this has been done restore a recent backup of the Vista DB. See TAC Vista Technical Manual for restore process. From the heading bar on the System Plug-in select TAC Network   Then select Import TAC Network Enter the database user name and password where prompted. Select Yes to the "Overwrite current edited TAC Network" prompt. Select your current Lonworks network. The current Vista database will then be imported into the system Plug-In.

Issue Echelon LON USB not recognized by TAC Vista 5 in a Classic network. Echelon U10/U20 USB interface is not supported in Vista installations. It oftentimes will not come online under a Vista Server. Product Line TAC Vista Environment Echelon LTA U10/U20 USB to LON converters Vista Server Classic Network Cause Because of numerous problems integrating an Echelon U10/U20 USB interface, Echelon's USB to LON converters are not supported by TAC Vista. Resolution Download the TAC Vista Server Data Sheet and reference page 11 for supported LTAs. The supported LonTalk Adapters are: PCLTA TAC Xenta 511 PCLTA-10 TAC Xenta 527 PCLTA-20 TAC Xenta 555 PCC-10 TAC Xenta 701 i.LON 1000 TAC Xenta 711 NIC709-PCI TAC Xenta 721 NIC709-USB TAC Xenta 731 NIC709-USB100 TAC Xenta 911 NIC709-IP TAC Xenta 913 NIC852       FT 10 TP 1250 RS 485 IP 852 Ethernet NIC709-PCI X X N/A N/A NIC709-USB X X N/A N/A NIC709-USB100 X X N/A N/A NIC709-IP X X N/A N/A NIC852 N/A N/A N/A X

Issue The process for opening up port 135 in Windows 7 is not documented in the installation manual. Vista Workstation connections to remote Vista Server will not work. Environment Windows 7 Vista 5.1.X Cause With DCOM port 135 blocked by the windows firewall Vista Server communications will not work between Vista Servers and Workstations over a network. Resolution Set the DCOM setting as needed using the Vista installation Manual. Note - You will need to be logged on to Extranet for this document to be accessed. Then create a new Inbound Rule for port 135 as described on the Microsoft Website with the following settings: Rule Type: Port Protocol and Port: TCP and type specific port 135 Action: Allow the connection Profile: Domain; Private and Public Name: DCOM Finish Link to Microsoft website.

Issue A Xenta 102-AX accepts a 0-5V input on all external inputs. If Universal Input 3 is designated as CO 2 , the range of the input needs to match the range of the sensor. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Universal Input 3 CO 2 sensor Cause The default setting (a gain of 1/1) results in 0V = 0ppm 5V = 1023ppm (1023 is a resolution of the onboard analog to digital converter.) Resolution Refer to page 3-66 of the TAC Xenta 102-AX Software & Hardware Manual for more detail. Calculate the required gain for the range of the CO 2 sensor. Ensure the sensor outputs a 0-5V signal. Note the CO 2 level at 5V. In this example, 2000ppm. Divide the maximum CO 2 reading by the analog to digital converter bit resolution (1023). Multiply the result by 1000. (2000 / 1023) * 1000 = 1955 Locate the value for Universal Input 3 SCPTgain. There are four locations to alter this value: Xenta 102-AX Plug-in Go to the Browser Tab > Xenta102AX > UnivIn3 Sense > SCPTgain > multiplier. Over on the right, enter in 1955/1000 and hit Set Value. LonMaker or LNS browser Open the browser window by right clicking on the 102-AX in the drawing and selecting Browser. Look in the Functional Block column for UnivIn3Sense. In that category is a point called SCPTgain. Click on it and then enter up top 1955/1000. Hit the red down arrow to download the value to the device. Enable monitoring on the nvoCO2sensor value or reopen the browser to view the new CO 2 value. Vista Workstation Go to the 102-AX.UnivIn3_Sense module and locate the SCPTgain point. Double click it. By Multiplier enter 1955 and by Divisor enter 1000. StruxureWare WorkStation Go to the 102-AX and click on UnivIn3Sense module and in the Variables tab locate the nciGainUIx point and expand it. For Multiplier, enter 1955 and save. For Divisor, enter 1000 and save.

Issue Using the selection tool to select the correct meter. Environment Heat Meters Cooling Meters Cause Selecting the incorrect meter can lead to loss of water flow and increased system pressure. Resolution Selecting an appropriate Heat Meter can be achieved using the selection tool. To view or download the tool click here. For the Product Announcement click here. To view the Online version of the tool please click here. The selection of a Heat Meter requires the following information; 1 - The maximum water flow through the system. 2 - The location of the meter, (Flow or Return). 3 - The size of pipe work where Heat Meter is to be installed. 4 - The media type, heating, cooling or both. 5 - Using the selection tool is made easier by using the Auto filter drop down selection arrows. These allow you to filter the selection on a particular area, i.e. "Flow Rate" as shown below. The Heat Meter part number is established as follows; 1 - Digits 1,2 - Heating, Cooling or Combined. 2 - Digits 3,4 - Flow rate. 3 - Digits 5,6 - Body length and connections. 4 - Digit 7 - Threaded/Flanged. 5 - Digit 8 - Heat Meter location Flow / Return. 6 - Digit 9 - Communications type. 7 - Digit 10 - Display option. 8 Digits 11,12,13 - Revision. To view a warning about the under sizing of Heat Meters, please click here. New serial communication modules are now available for Modbus RTU and BACnet MS/TP interfaces.

Issue The STR-250 will not respond to any input and the display is incorrect, typically flashing random characters or 00. During this behavior the Xenta 102-AX will remain offline and unresponsive, no longer controlling room temperature. Product Line TAC Vista Environment Xenta 102-AX STR-250 Cause A firmware error has been identified in the TAC Xenta 102-AX (and 102-AX-U8) version 2.14, when they are used together with STR-250, the LCD version of STAT. A certain sequence of key strokes will cause the Xenta 102-AX to lock up. A firmware upgrade is available. Until that has been downloaded a power cycle will in most cases recover the controller. See the full TPA-MALR-10-0004.00. Resolution The 102-AX Firmware error is fixed in version 2.16 and later. Instructions on how to properly upgrade the 102-AX are located here: Upgrading a Xenta 102-AX to version 2.16 or later

Issue Does the STR-250 work on Micro Regulators (MR)? Environment I/NET Seven STR-250, I/STAT, M/STAT I/SITE Controller and Micro Regulators (MR) Cause The STR-250 Wall Module is the replacement for the commonly referred to I/STAT sensor, still referenced in I/NET documentation.  The I/STAT is no longer available.  Resolution The STR-250 sensor is the replacement for the I/NET I/STAT, so installation and configuration for the STR-250 is as per this I/STAT. There are two documents that will provide assistance with this TCON126 and TCON299 (Chapter 21). The STR-250 full functionality must be installed on the I/STAT port of any I/NET device and configured as detailed in the above documents. Only one I/STAT port exists per MR. The M/STAT is still available and is used as the hardware tool for configuring the controller settings on all supported I/STAT devices, such as, all Micro Regulators (MR) variants, I/Site LAN Controller (Model 7728) and Xenta 102-AX. 

Issue How to change the STR-150 temperature display, setpoint adjustment range, etc. Product Line TAC Vista Environment STR-150 STR Sensor Cause The communication between the STR-150 and the TAC Xenta 121/122 device is one way, space temperature and setpoints are sent from the sensor to the controller. Therefore some STR-150 functions (for example, the setpoint adjustment) can not be configured though Zbuilder, but needs to be done manually in the STR 150 device. Resolution Buttons on the thermostat: Increase Button Decrease Button Bypass button Fan button Wrench symbol   Steps of changing the STR-150 configuration are listed below: Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0 In P0, hold down the bypass button and push the fan button three times to enter configuration mode. NOTE: the wrench symbol is lit when the STR-150 is in configuration mode.   In configuration mode: Press the fan button repeatedly until reaches desired parameters (refer to the configuration table below). NOTE: the two digits farthest to the left on the display show the parameters, while the two digits farthest to the right show the value Use increase button or decrease button to change the value.   Exit configuration mode: Push the fan and bypass button simultaneously for 2 seconds. Or, the timeout will exit configuration mode if idle.   Configuration Options: Parameter Function Value/Range Default value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 1=°C P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 22°C / 72°F P3 Setpoint or room temp. 1=Setpt, 2=Room 1=Setpt P4 Timeout 5-90 seconds 10 seconds P5 Fan Settings 0=No fan 1=On/Off fan 2=Two-speed fan 3=Three-speed fan 3=Three-speed fan P6 Room temperature and setpoint display resolution 0.1 or 0.5 °C 0.2 or 1.0 °F 0.5 °C or 0.2 °F P7 Max adjustable setpoint span above or below Reftemp (P2). +/- 0 - +/- 5°C +/- 0 - +/- 10°F +/- 3° or +/- 6°F P8 Bypass button and occupancy indication When = 2, no bypass command is sent  to the controller 1= Symbol on, off Or flashing 2=Symbol always off Default 1=on, off Or flashing P9 Setpoint as Absolute or Offset value 1=Absolute 2=Offset 1=Absolute   Click here to read STR-150 user's manual.

Issue Does Vista support virtualization? Will Vista run on a virtual PC, VMware, virtual environment? Product Line TAC Vista Environment TAC Vista all versions VMWare, Player, Workstation and Server Microsoft Virtual PC Cause For many companies, the largest benefit of server virtualization is in reducing the amount of hardware that is required to run all the software needed by the business. Consolidating servers using a virtualization process not only provides savings in terms of how many physical machines must be bought and maintained, but also potentially reduces the amount of physical space that a company needs for its servers or data centre. Resolution Virtualization is a term that allows software in emulating environments, such as VMware / Virtual PC. These software packages emulate a PC environment so that many computers appear to be running on one single machine, thus “virtualization”. The general impression is that the emulation packages work very well. The user must be familiar with the emulating product in order to be able to do the correct settings. No matter if it runs on PC hardware or in an emulating environment, the specific product is supported given the problems are related to the Software itself, but not for problems related to the environment it runs on. Particular note and understanding is required when dealing with multiple applications trying to access a single piece of hardware, such as serial ports, USB and the like. Please see the following TPA-MALI-09-0013.00 for additional information. Also note that Vista Licensing system is NOT supported when using Remote Desktop.  Refer to the following article for further details: Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system.

Issue A TAC Xenta programmable controller has issues, and more information is needed to analyze what is happening in the controller. Product Line EcoStruxure Building Operation Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 401 XentaErrorLogViewer Cause The TAC Xenta 280, 300 and 401 series has an internal Error Log, that in some cases could give more information about the way the device is acting, storing restart reasons etc. Resolution The XentaSystemErrorLogViewer is used to read out the internal error log file from a TAC Xenta 280, 300 or 401 device. The XentaSystemErrorLogViewer is a program that runs in your PC, and you have to connect to the TAC Xenta device by the use of a serial cable. You must have at least the same version number of the XentaErrorLogViewer as the device you want to read the information from. Please note that the XentaSystemErrorLogViewer program only works with released version of the TAC Xenta 280, 300 or 401 devices. 1. Download XentaSystemErrorLogViewer 2. Install the program 3. Connect the TAC Xenta to the PC using the TAC Xenta programming cable. Refer to the cable guide for further information. 4. In "Preferences", select the COM port to which you connected the serial cable 5. Check "Write System Error Log to file" 6. Click "Get new information" 7. The information is written to "C:\Windows\Temp\XentaSystemErrorLogg.txt"

Issue You need to replace a faulty Xenta 301 controller. However, the existing unit is running System Version 1, and the network comprises approximately 12 Xenta controllers on a Menta-only network using the .nwc and .ndb configuration tools. Product Line TAC Vista Environment TAC Xenta 300 Cause New Xenta 301 controllers are shipped with System Version 3 by default. System Versions 1 and 3 are incompatible on the same network. Resolution To ensure compatibility, downgrade the new Xenta 301 controller to System Version 1.17 before installation. Steps to Downgrade and Replace: Download TAC Xenta 300 system program version 1.17 Use the Download Wizard as usual. Important: When downgrading from Version 3 to Version 1, do NOT retain the old application in the Download Wizard. Select "Clear Application" during the process. Manually Download the Menta Application and Network Configuration Use a serial cable to perform the manual download. Apply the appropriate TAC Menta versions for your network setup. Additional Notes Mixing different system versions on the same network can lead to unpredictable behavior and communication issues. Always verify the version compatibility before deploying new hardware.

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel.   2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log.  Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue Receiving the following error when attempting to navigate to the Xenta web interface. "TAC C503Boot/x.x.x.x not configured". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 511, 527, 555 Xenta Server 701, 721, 731 Cause Device web interface has stopped working or flash drive / hard disk has been corrupted on the Xenta Server. Resolution Attempt the following steps to resolve this problem: Try restarting the device and see if the unit comes back online, remember to wait 1-2 minutes for the unit to restart.  Check the RUN LED on the panel, if the LED is a solid green this indicates the device is running normally, and your access should be restored. If the LED is RED, solid or flashing this would indicate a problem with the device. Attempt to restore or upgrade the device to the latest firmware.    You can download the latest firmware version from the Schneider Electric Exchange. If this fails then then reference Xenta Server "Run" light is solid red with no communication via Ethernet.

Issue Problems installing Vista Webstation 5.1.5 or newer Product Line TAC Vista Environment Vista Webapps (Webstation) 5.1.5 Windows 2008 Server 32-bit or 64-bit. Cause In order to install TAC Vista Webstation successfully on Windows Server 2008, there are a number of steps and prerequisites to be checked. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: PC Preparation – Only if you can not access the Run as administrator context-menu! Log in as an administrator and create a new administrator group (eg. VistaAdmin) and add a user to this group. By doing this you will be able to access the Run as administrator context menu later on (users added to the Windows administrator group do not always receive full administrator rights). Install IIS 7 and ASP.net Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click Next and then click Install. NOTE FOR WINDOWS 7 USERS! Whilst Windows 7 is not officially supported for running Webstation it may be used in a test environment. It's important to note that the IIS and ASP.net installation is slightly different - the user is not asked to add roles, the user is asked to add windows features (see screenshot below). Ensure .net framework 4.0 is installed Open Server Manager and select Features. Scroll down and ensure .net framework 4.0 is installed. If not: Open Internet Explorer. From the menu select Tools\Windows Update (Safety\Windows Update in IE8) Run windows update and install .net framework 4.0 Install TAC Vista Server and any hotfixes Install TAC Vista Webstation and any hotfixes As administrator, register ASP.Net version 4.0 Click on start and then All programs\Accessories. Right-click on Command Prompt and select Runs as administrator. If using 32-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis. If using 64-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis. Ensuring that the directory is set to C:\ copy the file path into command prompt and the add the following text : aspnet_regiis.exe -i -enable Press Enter Confirm the installation was successful Click on start and then type inetmgr in the search box. This will open IIS manager. Expand the hierarchical menu on the left and then expand the Sites folder. Expand Default Web Sites and select Webstation Right-click on webstation and select manage application > Advanced Settings. In the Application Pool field it should say SE ASP.NET v4.0 Classic All that is left now is ISAPI, CGI (see "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server") and DCOM settings (see TAC Vista Installation Manual or Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET). License problem: Webstation - No license Available