Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Summary

This article describes information about Team Foundation Server (TFS) 2010 Service Pack 1 (SP1).

The largest component of the TFS 2010 SP1 is the set of core product changes that are needed to enable our Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack. This component enables portfolio management collaboration between formal project management and developer teams. For more information, visit the following website:

Visual Studio Team Foundation Server 2010 and Project Server Integration Feature PackAdditionally, this article lists issues that are fixed and new technology improvements in Team Foundation Server 2010 SP1. 

More Information

How to obtain Team Foundation Server 2010 SP1

To obtain Team Foundation Server 2010 SP1, visit the following Microsoft website:

Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1

Included in this service pack

Visual Studio 2010 SP1 includes an update to the Microsoft .NET Framework 4. For more information about the update, click the following article number to view the article in the Microsoft Knowledge Base:

2468871 Update for Microsoft .NET Framework 4

Supported languages and operating systems

Supported languages

Team Foundation Server 2010 SP1 provides updates for the following versions:

  • English

  • Chinese (Simplified)

  • Chinese (Traditional)

  • French

  • German

  • Italian

  • Japanese

  • Korean

  • Russian

  • Spanish

  • Portuguese (Brazil)

Supported operating systems

  • Windows Server 2008 R2 (x64) with Service Pack 1

  • Windows 7 (x86 and x64) with Service Pack 1

  • Windows 7 (x86 and x64)

  • Windows Server 2008 (x86 and x64) with Service Pack 2 - all editions

  • Windows Vista (x86 and x64) with Service Pack 2 - all editions except Starter Edition

  • Windows Server 2003 R2 (x86 and x64) - all editions

  • Windows Server 2003 (x86 and x64) with Service Pack 2 - all editions

  • Windows XP Service Pack 2 (SP2) or a later version of Windows XP

  • Windows XP (x86) with Service Pack 3 - all editions except Starter Edition

Installation requirements

  • A licensed copy of one of the supported Team Foundation Server 2010 products must be installed on the destination computer.

  • We recommend that the computer has 1,024 MB or more RAM.

How to troubleshoot the installation

You may encounter some problems that prevent you from installing TFS 2010 SP1 correctly. To resolve the problems, click the following article number to view the Microsoft Knowledge Base article:

2516423 How to troubleshoot installation problems for Team Foundation Server 2010 SP1 and for later updates

Team Foundation Server 2010 SP1 support

Formal support is available through Microsoft Support websites. For more information, visit the following Microsoft website:

http://support.microsoft.comInformal community support is available through the Microsoft Developer Network (MSDN) forums. For more information, visit the following Microsoft website:

http://social.msdn.microsoft.com/Forums/en-US/categories

New features and fixed issues in Team Foundation Server 2010 SP1

Admin, Ops, and Setup

New technology improvements:

  • Added an option, tfsconfig updates /reapply, that will start the service host if it has been left in a stopped state after patching.

Fixed issues:

  • Upgrade from Visual Studio 2008 fails if @@SERVERNAME is NULL.

  • Update could not be installed correctly if the configuration database is being mirrored.

  • Installing an update fails if one of the collections is not available.

Build automation

Fixed issues:

  • You could not delete build drops if a controller went down.

  • The first changeset in the list of "Associated Changesets" may occur two times.

  • Ancient changesets are associated with build.

  • Memory leaks and performance drops on TFS 2010 Build Service under heavy loads.

  • A Dr. Watson error occurs on the buildnotification.exe process together with a system.argumentnullexception exception.

  • A Dr. Watson error occurs on the tfsbuildservicehost.exe process together with a 0xC000001D exception.

  • Change the default in What to Delete, under Build Retention, from All to All - Test Result.

  • When you manually queue a gated check-in build, the What do you want to build drop-down list is intermittently disabled.

  • Build Definition Cache on the Application Tier can become corrupted when multiple definitions map or cloak the same paths in the workspace templates.

  • When you undo a gated check in, the undo does not remove unshelved adds from the disk. This creates a cluttered workspace that could let breaking check ins make it through.

  • You can unintentionally change the build quality of a project because of odd focus and scroll wheel interaction.

  • There was a performance issue with TFS 2010 Build Log Viewer.

Core services

Fixed issues:

  • QueryActiveRequests shows requests that do not contain the associated threads.

  • QueryActiveRequests occasionally stops, becomes unresponsive, and never returns.

  • The server plug-in architecture disables plug-ins when an exception is thrown.

  • A transport-level error occurs when Core Services received results from the server.

  • A Dr. Watson error occurs together with a SqlException exception and the message, "Failed to load Msxmlsql.dll."

  • The Security service crashes when you have two paths that are different only by the letter "I" on a Turkish database.

  • The Attach action fails when custom instance groups are members of collection groups.

  • A Dr. Watson error occurs on the tfsjobagent.exe process together with an exception in SYSTEM.DATA.SQLCLIENT.SQL.

  • You cannot stop the configuration service host if there is a running job that will take a long time to finish.

  • A process that calls ApplicationServiceHost.BeginRequest may prevent the service host from stopping until the request context that was passed to that method is disposed of.

  • You cannot detach an Offline Collection.

Office integration 

Fixed issues:

  • Add the Work Item ID and the Title to the subject line of the email message when you export a single work item.

  • Non-TFS project plan displays the error TF80070 when you change work in Task Usage view to the side-by-side view, and a bound project plan is open.

  • You cannot undo a sort in Excel Trees, and then you clear Sort and Filter. In this case, unexpected results might occur when you try to publish a workbook.

  • A disconnected client displays the error message "Server not available" for every table in a workbook.

  • Error TF208021 occurs when you convert to a tree query that only contains one WI by Configure list.

  • You receive an Access Violation when you create an instance of CLSID {23A20EA8-2DF0-40a6-A1FA-8143EDB7B172}.

  • If a filter is set on the Gantt View, a work item can be parented incorrectly when the work item is brought into the project plan through an update on the Team Planner view.

  • Adding additional resources to a summary task does not reset all assignment units to 0 percent.

  • A "An item with the same key has already been added" error occurs when you try to publish a TFS work item link from Microsoft Project.

Reporting

Fixed issues:

  • TFSOlapProcessComponent's class ICancelable implementation has to call server.Disconnect(false) in addition to CancelCommand().

  • Microsoft SQL Server deadlocks during the prc_Dimension_DimFile_AddUpdate SQL exception procedure.

  • You cannot insert a duplicate key row in object 'dbo.DimFile' that has a unique index 'DimFile_FileBK'.

  • Jobs are not deleted when reporting is disabled. This results in inaccurate data that is displayed on reports.

  • The WIT Warehouse adapter relies on the WorkItemsAre and WorkItemsLatest tables that have the same [Changed Order] values. In this case, Warehouse processing fails, and you receive the following error: 

    The trust relationship between the primary domain and the trusted domain failed.

Team Web Access

Fixed issues:

  • The Web Access UI does not react to locked links.

  • The View Log command cannot show content when you use a Firefox 3.5 browser.

  • When you build a web part, the build queries more data than is necessary. This can lead to a performance issue when lots of builds are processed.

  • A localized web access site points to ENU MSDN pages for help content.

Version control

New technology improvements:

  • Adds support for QueryMergesExtended to query merge targets for a given item

  • Adds changes to baseless merge for deleted items and cherry picks

  • Adds changes to make the comparison for Get and Remap commands case-sensitive

Fixed issues:

  • Branch mappings obtain the wrong mapping.

  • Blocking problems occur on check in and remove access control list actions.

  • Product changes to remove redundant content are added.

  • Merge and Unshelve bad query plans and the rename merge issue are addressed.

  • Query plan fix for check in and fix for infinite merge loop are addressed.

  • Syncing to a label that has a duplicate name but different scope in the system produces unpredictable results.

  • After you open a solution, the database node in Server Explorer becomes fully expanded, and you are prompted to add a database diagram.

  • Comparing a file after renaming its parent does not work.

  • You cannot determine one branch from another branch when they have the same name.

  • A lock on a file is orphaned on check in when the parent is renamed and checked in in another workspace.

  • You receive an InvalidOperationException exception on a message pump callback from PendingChangesFileList. This causes Visual Studio to crash when you try to resolve multiple conflicts.

  • The autoproxy contacts LDAP every time that TFS 2010 processes GetOperations when there are interactions with Team Foundation Server 2005 or with Team Foundation Server 2008.

  • An upgrade from Team Foundation Server 2005 or Team Foundation Server 2008 adds ACEs for shelvesets and for workspaces. This incorrectly keeps identities alive.

  • Issues occur with the Turkish letter "I" on large check ins.

  • A candidate delete is lost when you perform a merge in a folder rename.

  • When you try to merge a rename and a delete on a file, the results cause inconsistencies in the version control database.

  • Merge does not conflict in some cases after a merge or discard in same direction.

  • You receive the error "System.IO.IOException: Unable to read data from the transport connection: The connection was closed." when you try to download a source.

Work item tracking

Fixed issues:

  • Backward compatible verbatim error message was missing.

  • An HTML server truncates stack traces that contain hyperlinks that use quotation marks.

  • An error on a Work Item form occurs in TFS when an object reference is not set to an instance of an object.

  • When you change the reporting type of a field, work item operations can be blocked for up to seven minutes.

  • WorkItem.aspx treats the default description field differently than other longtext fields.

  • Team project creation fails in Pseudo-Location (PLOC) because of a global workflow issue.

  • The Bypass rule attribute does not work with batch update.

  • String fields should accept the new line and tab characters.

  • The System.History field is not displayed in query results view.

  • The work item Object Model (OM) cannot be loaded.

  • Usage incorrectly identifies flags for the WitAdmin ExportGlobalWorkflow command.

  • WitAdmin commands cannot be run on a release version client against a TFS SP1 server.

  • The WitAdmin deletefield method causes an error "TF237159: The query contains columns that are not valid."

  • SERVERDEFAULT from currentuser does not work when the fields are marked with the SyncNameChanges field, and this field is set to True.

  • After an upgrade, the allowed values in fields that are marked with the syncnamechanges field when this field is set to True may block the WIT import.

  • Bypassing workflow rules is broken if you delete a field that existed before the last servicing operation.

  • An index exists on the title field.

  • When you use a Visual Studio 2005 or a Visual Studio 2008 client, you encounter a red "X" on the reporting node of the team explorer.

  • The process template is not uploaded if a work item type definition references project level groups.


Previous issues

These are the previous issues that are included in TFS SP1.

TFS build

Fixed issues:

  • Visual Studio 2008 "smart device" projects obtain the 2010 MSTEST instead of the 2008 MSTEST.

  • Unavailable build agents are pinged indefinitely instead of stopping after an hour.

  • Duplicate changesets are listed in the build report.

  • Test results for Visual Studio 2008 solution are not published if there is a failed test.

  • You cannot delete build drops if a controller goes down.

  • When you are connected to Team Foundation Server 2008, when you right-click a build definition, you see that Open Process File Location is dimmed on the shortcut menu.

Version control

Fixed issues:

  • Labels that are created in TFS 2008 do not contain items after you migrate to TFS 2010.

  • Branch from label was removed in TFS 2010.

  • When you convert a folder that has subfolders to a branch folder on a hierarchy root folder, and then you rename the folder and its subfolders, Visual Studio crashes.

  • Unshelve reports bogus errors about a null DownloadUrl when dependent renames are shelved, and child item names overlap.

  • When you have an incorrect query plan on QueryPendingChanges, and you run a query, all users' pending changes could result in bad performance.

  • Merge or discard in both directions cause unnecessary "empty" merges in future merge attempts.

  • An issue in merge causes a conflict not to be generated when there is a rename in the target and source.

  • Very aggressive automatic detection of file encoding can result in unsuitable encoding mismatches during merges.

Work item tracking

Fixed issue:

  • Work item queries that contain references to deleted fields can cause a red "X" to be displayed on the work items node.

Team Web Access

Fixed issues:

  • Link Selected Items to a New Work Item and other dialog boxes do not open pages successfully in the Firefox browser.

  • Adding an attachment does not work in the Chrome browser.

  • The Select Query drop-down list does not work in the Choose Work Items dialog box in the Chrome browser.

  • When you try to use the Retain/Delete a build option on the build report page, an exception occurs in the Chrome browser: "Unexpected callback response."

  • The Query Picker Web Part incorrectly displays list items or rows in the list view (Overflow DIVs) within WebKit-based browsers such as Safari, Chrome, and other browsers.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×