Category Archives: 6584

Update for TFS 2010 (RTM version) including all hot fixes

Get your TFS current: All hotfixes bundled in one updateMicrosoft released an update (KB 983578) for:

  • Team Foundation Server 2010
  • All Team Foundation Server 2010 clients (aka Team Explorer)

It’s the same update package that will update the client and server components.

What’s in that upgrade?

According to Brian Harry and the KB article:

Enables Visual Studio 2010 Lab Management functionality

  • Improves performance for Lab Management Workflow Wizard.
  • Improves performance for running automated test cases on Network Isolated Lab environments.
  • Fixes an issue in which a Test Controller service account that is the same as a Lab Service account causes issues with environment capabilities.
  • There is a new Expression Encoder 4.0 based Video Diagnostic data adapter to collect video recording when you perform tests. This diagnostic adapter replaces the Windows Media Encoder base video diagnostic adapter.
  • Labels created in TFS2008 do not contain items after migration to TFS 2010 under certain rename/delete conditions.
  • TFS Cannot be re-installed (ATOnly) targeting a database that was patched before.
  • Tfs2010Beta2ToRTM operation is not executed when RC database is upgraded by post RTM server (RTM + Patch1 or SP1).
TFS Build
  • VS2008 “smart device” projects pick up the 2010 MSTEST rather than the 2008 one.
  • Unavailable build agents are pinged indefinitely rather than giving up after an hour.
  • Duplicate changeset listings in build report.
  • Test results for VS2008 solution not published in case of a failed test.
  • Cannot delete build drops if a controller goes down
  • Open Process File Location” grayed out on menu- right click on a build definition when connected to a TFS 2008 server
Version Control
  • Branch from label has been removed in TFS 2010 – now it’s back.
  • Convert folder to branch on a hierarchy root folder with children and cycle renames crashes VS.
  • Unshelve reports bogus errors about a null DownloadUrl when dependent renames are shelved and child item names overlap.
  • Incorrect query plan on QueryPendingChanges when querying all users pending changes can lead to bad performance.
  • merge /discard in both directions causes unnecessary “empty” merges in future merge attempts.
  • Issue in merge causes a conflict not to be generated when there is a rename in the target and source.
  • Overly aggressive automatic detection of file encoding can result in inappropriate encoding mismatches during merges.
Work Item Tracking
  • Work item queries containing references to deleted fields can cause a red X on the work items node.
Team Web Access
  • Firefox Browser: "Link Selected Items to a New Work Item" and other dialogs don’t launch pages successfully
  • Chrome Browser: Adding an attachment doesn’t work
  • Chrome Browser: Select Query Dropdown doesn’t work in Choose Work Items window
  • Chrome Browser: Retain/Delete a build in Build Report page will get an exception “Unexpected callback response”
  • Query Picker Web Part Incorrectly Renders List Items (Rows) in List View (Overflow DIVs) within WebKit-based Browsers (including Safari, Chrome, etc)

Where should I apply the upgrade?

TFS component: Applies to:
TFS Application Tier Yes
TFS Data Tier (SQL Server) No
Team Explorer 2010 Yes
Visual Studio 2010 Yes
Visual Studio 2005/2008 No
Microsoft Test Manager (MTM) Yes
TFS Build Controller Yes
TFS Build Agent Yes
TFS Test Controller Yes
TFS Test Agent Yes
TFS Lab Agent Yes
System Center Virtual Machine Manager (SCVMM) No
SQL Server Reporting Services No
SQL Server Analysis Services No
SharePoint/WSS No

Download the update package now.

Frequently asked questions

  • Should I install the update although I do not use Lab Management?
    Yes, it contains all TFS fixes that have been made since TFS 2010.
  • Is this a Service Pack?
  • If I reinstall or add TFS components later, do I have to reapply this patch?
  • Should I stop TFS service prior to installing?
    No, this is not necessary and will be done automatically by the update.

TF30207: Can’t create team project on TFS itself / red X on documents and reports / insufficient SSRS or WSS permissions

Problem description

Team Project creation fails on the Team Foundation Server itself due to insufficient permissions although the user has all neccessary permissions in SQL Server Reporting Services (Content Manager role) as well as Windows SharePoint Services.


A red X is shown next to the Reports and Documents node when running Team Explorer on the Team Foundation Server itself.

Further obervations:

    • You can access http://<server>/reports without problems.
    • You can access the SharePoint Central Administration without problems.
    • Creating team projects with Team Explorer from other machines work fine.


Follow the steps outlined in the following KB article:

Unable to publish test results from Visual Studio to TFS

Error message similar to:

username@servername (mailto:username@servername) 2008-10-13 2:21:50          0.28 MB            10/13/2008 3:19:14 PM    Failed    Access to the path ‘\\DropFolder\Buildname_20080723.3\TestResults\fd8883e0-2153-44c6-8671-6d6db460c4a8\uesrname 2008-10-13 _02_21.trx’ is denied.

Cause: Permission issue

A Workaround can be found in the KB article 958726.

Hotfix for Team Build 2008 SP1: Reducing project-to-project references in build log (KB958845)

From Aaron Hallberg blog:VS08-TeamSys-TFS_v_rgb_2

[…] change in TFS Build SP1 which reduced build log noise by cutting out the build steps for project-to-project references […] the fix in SP1 didn’t actually fix the problem, at least not completely.

[…] As such, if a project was referenced by 10 other projects the fix in SP1 would reduce the number of spurious build steps from 10*3 to 9*3 rather than removing them altogether.

A hotfix is finally available that will address the remaining parts of the problem […]

VSTS MVP colleague Mathias Olausson reports:

“before SP1 the build time was about 2h 30 min, with SP1 build time in average 65 minutes and with the build hotfix we’re now down to less than 40 minutes. The build log has changed from 5500 lines down to 550.”

Download hotfix: TFSBuild TargetsNotLogged property fails to cut down noisy builds

Additional Info: KB article 958845

Security Update for TSWA 2008 SP1

protected_83f8084f-8b20-45d5-8b17-67b0b449e38cFrom Hakan Eskici’s blog:

A security issue has been identified with Team System Web Access 2008 SP1 and we have recently published an update that fixes it.

Installation Notice

Please note that this is a full release, so you will need to uninstall any existing versions of Web Access before installing this update.

Update: Instructions to patching your installation without the need to uninstall/reinstall TSWA)

Update #2: KB article 961267 is now available.

Determining if the update is installed

Take a look at the About page (Help > About) in Web Access.
The version number will be 9.0.3275 for TSWA 2008 SP1 Update.

Download: Visual Studio Team System Web Access 2008 SP1 Power Tool

Update Warning: Security Update for SQL Server 2005 Service Pack 2 (KB948109) might break Reporting Services

Name des Updates und Nummer:

  • Security Update for SQL Server 2005 Service Pack 2 (KB948109)
    version 9.00.3068.00 released on 7/8/2008

Applies to:

  • SQL Server 2005 Service Pack 2 with Reporting Services installed

Symptoms & Result:

  • After installation the SQL Server 2005 Reporting Services service might not start. Therefore the Reporting Services cannot be used anymore.


  • The Update is distributed via Windows Update.


  • Uninstall the update (requires a restart).

My recommendation:
(for your internal SQL server you use for TFS)

  • Do not install the update and wait for the next service pack release.

Related Links:

Visual Studio 2008, .NET 3.5 and TFS 2008 Service Pack 1 released

Service Packs for VSTS/TFS do not only contain bug fixes, but quite a few nice new features as you can read here (more general) and here (TFS-specific).

Download links:

If you have trouble installing SP1 look here and here.


Tip #1: Uninstall Visual Studio Hotfixes first

If you previously installed a Visual Studio 2008 Hotfix, you must run the Hotfix Cleanup Utility before installing Visual Studio 2008 SP1. For more information, see Visual Studio 2008 Hotfix Cleanup Utility for Installing Visual Studio 2008 SP1.



Tip #2: Have enough disk space available on your primary hard drive:


You can read here why.


Tip #3: If you have Team Explorer or TSWA on your TFS you need to install… (Thanks to Hakan Eskici)

… Visual Studio 2008 Service Pack 1 and  TFS 2008 Service Pack 1 (in that order!).


Tip #4: Integrate installation of TFS and SP1 (“Slipstream”)

The steps to produce a so-called “slipstream” installation package are documented in the TFS Installation Guide in the chapter “How to: Integrate the Installation of Team Foundation Server and Service Pack 1“.

There are a few reasons why you must do that (e.g. upgrading to SQL Server 2008) you can read in Brian Harry’s blog post.

Slipstream_Step2 Slipstream_Step3 Slipstream_Step4 Slipstream_Step5


Tip #5: Ignore Windows Update reboot prompt (Thanks to Brian Harry)

If you get a Windows Update prompt to reboot during SP1 installation, ignore it (don’t reboot).  Wait until after the SP1 installation completes and then reboot.


Tip #6: Uninstall and reinstall Team System for Database Development GDR (Thanks to Brian Harry)

If you have a prerelease of the Team System for Database Development GDR (that supports SQL 2008) installed, you will need to reinstall it after upgrading to SP1.


Screenshots from applying TFS 2008 SP1:

TFS2008SP1_Step1 TFS2008SP1_Step2 TFS2008SP1_Step3 


Screenshots from applying VS 2008 SP1 (online installer) on at TFS with only Team Explorer installed:

VS2008SP1_Step1 VS2008SP1_Step2 VS2008SP1_Step3 VS2008SP1_Step4

Users can see all team projects after upgrading from TFS 2005 to 2008

  1. Make sure all team project members are added to the appropriate groups (Project Administrators, Contributors and Readers).
  2. For every team project remove the “[Server]\Team Foundation Valid Users” group from the team project settings (Team Project Settings » Securty).

  3. Done. Regular members now should only see team projects where they have permissions.