TfsBuild fails because target file is wrong version - by Vicero

Status : 


Sign in
to vote
ID 542413 Comments
Status Active Workarounds
Type Bug Repros 11
Opened 3/16/2010 4:02:59 PM
Access Restriction Public


I cannot use team build.  I am trying to enable it for a project built in vs2008.  The build agent fails with the following log:

Upgrade Build Process

Get the Build

Update Build Number

Run On Agent


Get the Build Directory

If Not String.IsNullOrEmpty(ConfigurationFolderPath)

Run TfsBuild for Configuration Folder
 TF270000: The TFSBuild workflow activity cannot continue because it requires a build targets file that is version 3 or higher.  The version of the current build targets file is 2. The name of the file is C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets.

The build machine has tfs 2010 and visual studio 2008, with .net frameworks 2, 3, 3.5, 3.5 sp1 and 4.0.

A work around or a way to repair the targets file would be appreciated.
Sign in to post a comment.
Posted by Microsoft on 6/21/2010 at 1:04 PM
This issue should not occur if only RTM builds have been on the machine. It should be limited to cases where Beta releases were installed.
Posted by Ewald Hofman - MSFT on 4/27/2010 at 12:38 PM
I have created a blog post on this:
Posted by Ewald Hofman - MSFT on 4/26/2010 at 12:22 PM
I am using the RTM version, and I get the error also. I have repaired the TFS 2010 installation, but that did not fix the issue
Posted by Microsoft on 3/17/2010 at 8:26 AM
This type of error can happen if 2008 is installed after TFS 2010 on the build machine. Repairing TFS 2010 fixes this.

In your case, the correct .targets file appears to be from Program Files while the error is referencing the .targets file from Program Files (x86). Have you set the build definition to explicitly use the 32-bit version of msbuild? Can you confirm the install order of 2008 and 2010 products on that machine and whether or not the x86 version of the .targets is version 2.0 or 3.0
Posted by Microsoft on 3/16/2010 at 10:09 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you