TFS Build Agent On x64 Machine

We recently moved our build agents over to x64 machines and bumped into a few issues.  Here are the issue and solutions to hopefully help you out:

Error:  TF215097: An error occurred while initializing a build for build definition \…: Cannot create unknown type ‘{clr-namespace: …}’

This one doesn’t have to do with x64.  We use custom tasks in our build process and with setting up a new build controller you  have to specify where the assemblies for the custom tasks live.

To fix:

  1. Go To Manage Build Controllers (Team Explorer –> Right click on Builds)
  2. Select Properties for your Controller
  3. Specify “Version control path to custom assemblies”

Building .NET Application

Building Visual C++ Application

Error: Could not load the Visual C++ component “VCBuild.exe”. To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere.

One of our applications is a C++ app build in Visual Studio 2005 and MSBuild would throw this error.

To fix:

  1. Ensure that you have VCBuild.exe on your machine in the paths below.  On my machine it was at the two paths below.  I already had .NET 2.0 and Visual Studio 2005 installed and it still did not work.
  2. Add these to system path variable
    C:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcpackages
    C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages
  3. Reboot (It didn’t work until I rebooted.  It might be possible that just restarting the TFS Build service would work.)

Error: Component ‘mscomctl.ocx or one of its dependencies not correctly registered: a file is missing or invalid

To fix:

  1. Find mscomctl.ocx on another machine or download from web
  2. Copy file into c:\Windows\SysWOW64

I didn’t need to register it but others say to register it.

Error: Component ‘comdlg32.ocx’ or one of its dependencies not correctly registered: a file is missing or invalid

To fix:

  1. Find comdlg32.ocx on another machine or download from web
  2. Copy file into c:\Windows\SysWOW64

I didn’t need to register it.

Performance

  1. Virus Scan: Be sure to exclude the directory on the build server where the files get dropped from Virus Scan software.  We saw a two minute gain from 8 minutes to 6 minutes doing this.
Explore posts in the same categories: TFS

Tags:

You can comment below, or link to this permanent URL from your own site.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: