Visual Studio Team System

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

MSDNArchive — Wed, 04 May 2005 22:00:00 GMT

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 SQL Server is running. In Control Panel, open Administrative Tools and then open Services. Verify that the following services (each of which is configured to start automatically at system startup) are running on the data tier computer:

·         Analysis Server (MSSQLSERVER)

·         Report Server (MSSQLSERVER)

·         SQL Server (MSSQLSERVER)

·         SQL Server Agent (MSSQLSERVER)

If any of these services are not running, start them before proceeding.

Next, check that the Report Server site is working:

Verify Report Server is running by opening a Web browser and navigating to the Report Server URL (for example, http://localhost/reports).

If the page does not display properly, or if an error message appears, refer to the SQL Server 2005 product documentation to troubleshoot the problem.

You can also use the new SQL Server Surface Area Configuration tools to control SQL Server services and features.

Applicability: Visual Studio 2005 Team System Beta 2

KNOWN ISSUE: Some Antivirus Applications Interfere with Setup

MSDNArchive — Fri, 22 Apr 2005 03:45:00 GMT

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 restarts. When antivirus software is configured to delete items in the Temporary Files folder on reboot the setup program is unable to maintain state and therefore the installation process cannot continue.

Solution:
Disable your antivirus program during setup, or at least disable the feature to delete the contents of the Temporary Files folder. In addition, disabling your antivirus program may reduce the time necessary for setup to complete.

Applicability: Visual Studio 2005 Team Foundation Server, Beta 2

KNOWN ISSUE: AD/AM Installation Failure

MSDNArchive — Fri, 22 Apr 2005 01:45:00 GMT

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 space is causing the command to fail when installing AD/AM.

The user will notice several attempts to install AD/AM ultimately leading to a failed installation of the Team Foundation Server application tier. Reviewing the AD/AM installation log in %systemdrive%\windows\debug will indicate that the Answer File could not be located.

Solution:
Install AD/AM manually prior to installing the Team Foundation Server application tier. We use defaults for most settings, with the following exceptions:

InstallType=Unique
InstanceName=BISGSS
LocalLDAPPortToListenOn=2420

Applicability: Visual Studio 2005 Team Foundation Server, Beta 2

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

MSDNArchive — Thu, 03 Mar 2005 12:49:00 GMT

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.

Applicability: Visual Studio 2005 Team System

KNOWN ISSUE: CQConverter Analyze Command Does Not Work

MSDNArchive — Fri, 28 Jan 2005 01:59:00 GMT

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 (/c:analyze) to generate the required field mapping and user mapping file. To migrate the work items from IBM Rational ClearQuest to Visual Studio Team Foundation, you will need to manually create a schema in the Team Foundation work item tracking system, and then manually create the schemamap file, field mapping files & user map file. See the converter walkthrough in the product documentation for examples of these files. After creating the schema and the required files, you can then use the converter to migrate the work items to VSTS using the migrate command (/c:migrate).

Applicability: Visual Studio 2005 Team System December 2004 CTP

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

MSDNArchive — Fri, 28 Jan 2005 01:51:00 GMT

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 restarted, and all SQL Server 2005 services are running as per the Team Foundation Installation Guide.
Restoring the data tier computer to pre-application tier installation condition if the application tier setup failed previously.
Uninstalling Active Directory Application Mode (Adam Instance BISGSS) and rebooting the application tier computer before starting a new installation.

Applicability: Visual Studio 2005 Team System December 2004 CTP

KNOWN ISSUE: DSL Tools December 2004 CTP Release

MSDNArchive — Tue, 25 Jan 2005 18:17:00 GMT

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

MSDNArchive — Mon, 24 Jan 2005 22:10:00 GMT

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

MSDNArchive — Mon, 24 Jan 2005 14:43:00 GMT

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

MSDNArchive — Mon, 24 Jan 2005 06:25:00 GMT

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 that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Hatteras\Checkin Policies
Value Name: CleanBuildPolicy
Type: REG_SZ
Data: C:\Program Files\Microsoft Visual Studio 8\Team Tools\Static Analysis Tools\CleanBuildPolicy.dll

Applicability: Visual Studio 2005 Team System December 2004 CTP