Q: What’s the most common cause for Team Foundation Server application tier setup failures?

A: The most common cause of Team Foundation Server application tier setup failures (36%) in Beta 2 is SQL Server services (in particular, Reporting Services) not running prior to installing the application tier. Before installing the Team Foundation Server database and application tiers, check that SQL Server services are running: On the data tier computer, verify…


KNOWN ISSUE: Some Antivirus Applications Interfere with Setup

Problem:Some antivirus applications delete the contents of the Temporary Files folder (%temp%) as part of a reboot. Setup programs, such as Team Foundation Server and Visual Studio, may require restarting your computer during installation to complete part of the installation. In many cases, state information is written to the temp folder to support the continuation of the installation after the computer…


KNOWN ISSUE: AD/AM Installation Failure

Problem:We have tracked down a problem during the installation of the middle-tier that impacts the ability to install AD/AM correctly, which is installed by Team Foundation Server setup. The issue is that under certain configurations, path names are resolved to long filenames, which in this particular case resolves to a path with spaces in it. The…


Q: Where can I find documentation for Team System, including walkthroughs?

A: Product documentation, including walkthroughs, is available by installing the MSDN Library that ships with Team System. In addition, during the Beta 2 timeframe the Visual Studio 2005 Beta Documentation should be updated with the content that ships with Visual Studio 2005 Beta 2. For more information, see the Visual Studio Team System dev center….


KNOWN ISSUE: CQConverter Analyze Command Does Not Work

Problem: Running the IBM Rational ClearQuest to Visual Studio Team Foundation work item tracking system converter (CQConverter.exe) with the analyze command (/c:analyze) throws an exception. Workaround: You will not be able to use the CQConverter to analyze and generate a schema of your IBM Rational ClearQuest database. Neither will you be able to use the analyze command…


KNOWN ISSUE: Various Issues Cause Error 32000 During Team Foundation Server Application Tier Installation

Problem: During the Application Tier setup, Error 32000 occurs when performing quiet execution (QuietExec) of certain Windows Installer custom actions (CAs). This may happen for the following executables: Bisregedit.exe SetupWarehouse.exe templateuploader2.exe tfsadaminst.exe Workaround: Troubleshoot causes for this error by: Verifying connectivity exists between the application and data tiers. Ensuring data tier installation is complete, the data tier computer has…


KNOWN ISSUE: DSL Tools December 2004 CTP Release

Known issues for the December 2004 CTP release of the Microsoft Tools for Domain-Specific Languages (DSL Tools) are available online. For more information, see: http://blogs.msdn.com/jochens/articles/360261.aspx Applicability: Microsoft Tools for Domain-Specific Languages December 2004 CTP


KNOWN ISSUE: Cannot type certain characters in the work item query builder

Problem: You cannot type a lowercase ‘q’  or a period ‘.’ in the work item query builder. Workaround: Use an uppercase ‘Q’. There is no workaround for typing periods. Applicability: Visual Studio 2005 Team System December 2004 CTP


KNOWN ISSUE: Team Foundation version control history window does not display file history

Problem: The checkin/out history of a file does not display in the history window even if it has been modified multiple times. Workaround: To view file history, run the history command from a command prompt in the local workspace:           h history [/server:serverName] Applicability: Visual Studio 2005 Team System December 2004 CTP


KNOWN ISSUE: Could not load file or assembly CleanBuildPolicy when creating a new checkin policy

Problem: When trying to create a new checkin policy, you receive the following error: Could not load file or assembly ‘CleanBuildPolicy, Version=8.0.1200.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. HRESULT 0x8013141A Strong name validation failed. Workaround: Delete the following value from the Registry: WARNING: If you use Registry Editor incorrectly, you may cause serious problems…