Microsoft Visual Studio Team Foundation Server (TFS) 2010 Service Pack 1 (SP1) cumulative update (CU) 2 is available. This CU resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
FIX: A "NullReferenceException" message is logged for agent jobs in Team Foundation Server 2010 after you install update 2570791
Additionally, this CU resolves the following issues.
When you check in some files to TFS 2010 source control, the files are not copied automatically to the custom assembly path for the build controller and its agents. Note If you restart the build service manually, the files are copied immediately.
You encounter one of the following performance issues in TFS 2010 after you install hotfix 2564498:
The Identity Management Service (IMS) of the TFS server is rolled back after the database is restored from a backup. When you try to synchronize work item tracking (WIT) from the server, a time-out error or an out-of-memory error may occur.
When you have many team projects in a single collection, and then you try to insert or update a work item, a time-out error occurs on the server. Or, the server responds much more slowly than usual.
It takes a long time to connect to a team project from Microsoft Excel or from Microsoft Project.
When you run an application that uses the WorkItemStore.BatchSave method to save a work item, you receive the following error message:
TF237079: Team Foundation could not update the work item because it was already updated by another user, it does not exist, or you do not have permission to update it.
Build agents do not run the builds that are in a build controller in TFS 2010 as expected, even though the build agents are still listed as available.
When a user's display name in a WIT work item contains a special character, a red X is displayed on the work item, and you receive an error message that resembles the following:
There is an error in XML document (22229, 11664256). ---> System.Xml.XmlException: '', hexadecimal value 0x1A, is an invalid character.
Note There is an known issue where the TFS and project server synchronization job will fail after you apply this update. You may receive the following exception that is thrown by the syncronization job:
Job extension had an unhandled error: System.TypeLoadException: Could not load type 'CREDENTIAL_ATTRIBUTE' from assembly 'Microsoft.TeamFoundation.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.; at Microsoft.TeamFoundation.Client.CredentialsCacheManager.GetCredentials(String targetName); at Microsoft.TeamFoundation.Client.CredentialsCacheManager.GetCredentials(Uri uri, Boolean requireExactUriMatch); at Microsoft.TeamFoundation.Client.CachedCredentialsProvider.DetermineProvider(Uri uri); at Microsoft.TeamFoundation.Client.CredentialsProviderFactory.GetCredentialsProvider(Uri uri, ICredentialsProvider fallbackProvider); at Microsoft.TeamFoundation.Client.TfsTeamProjectCollectionFactory.GetTeamProjectCollection(Uri uri, ICredentialsProvider fallbackCredentialsProvider); at Microsoft.TeamFoundation.Sync.JobExtension.JobServicePlugin.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime jobQueueTime, String& resultMessage); at Microsoft.TeamFoundation.Framework.Server.JobRunner.ExecuteJob
This issue can be resolved by cycling the tfsjobagent service. You can run the following commands after you install the update:
net stop tfsjobagent
net start tfsjobagent
To apply this cumulative update, you must have Team Foundation Server 2010 Service Pack 1 or Visual Studio 2010 SP1 installed.
Important You also need to apply this update on both the TFS servers and on all TFS clients.
You may have to restart the computer after you install this cumulative update if the affected files are being used.
We recommend that you close all instances of Microsoft Visual Studio before you install this cumulative update.
The English version of this cumulative update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.