Software Development Technology

TFS 11 Express Beta Error TF400030

The other day I received this error when attempting to open a Team Project from Team Foundation Server 11 Express:

TF400030: The local metadata table could not be loaded because exclusive access could not be acquired.

So I fired my Concordance of Microsoft Error Messages (Google) and was ready for a quick resolution:

Your search - TF400030: The local metadata table could not be loaded because exclusive access could ... - did not match any documents.


I knew I hadn't changed anything on the server, nor had anyone else accessed the project since I was last working on it so I quickly ruled my server as the culprit. Then I remembered that my hosting provider (Softsys Hosting - a great hosting provider, by the way) was having hardware issues with the box that housed my VM and had migrated all the VMs on that box to some newer hardware the previous night.

A quick disconnect and reconnect to the project collection and TFS was back running hot, straight, and normal. I'm guessing that this is related to the new Local Workspaces feature in TFS 11.

If you're reading this, I'm guessing you may be seeing this error message right now; I hope this saves you a few minutes (and now I can close the browser tab with the search for the error message that I've been keeping open to remind me to blog about this).

Software Development Technology

TFSBuild Queued Build Stalled and Can’t Be Deleted

I was playing with the TFS Community Build Extensions ( with the new TFS11 Express Beta and ran into a situation where I had a build that was stalled and wouldn't complete and couldn't be stopped. I figured I would use my go-to solution and rebooted my workstation. I opened Visual Studio after my box came back up and was surprised to see that TFSBuild had dutifully restarted the build.

The solution was quick and fairly painless (found here: - in short: delete the queued build definition from the Build Queue table in the project collection's database (tbl_BuildQueue) and then restart the build agent (TFS Administration Console).

Software Development Technology

Visual Studio 11 Team Foundation Explorer Express Beta Error

I am test driving the new (awesome) Visual Studio 11 Team Foundation Explorer Express Beta; my initial review is that it is awesome (more to follow on this). However, I ran into an issue when installing it on a Windows Server 2008 R2 box (it installed just fine on a workstation). The install went smoothly but once I tried to perform certain configuration tasks I started receiving errors; attempting to open the TFS Web Access portal also returned a 500 (internal server error). After much, much tinkering, I finally discovered the solution:

- solution after the jump -

when TFS is installed, it configures the TFS application pools in IIS to allow 32-bit applications, changing this to false corrects the issue and allows the application to function. To do this: in IIS > Application Pools > [Select the app pool] > Advanced Settings > Enable 32-Bit Applications = False.

I checked on the workstation installation and it was already set to false, so it seems that the issue is more with the installation package than with the actual TFS product (which is awesome, by the way). I'm not certain what actually causes the installer to do this, but I'm guessing it's related to the installer's detection of the CPU capabilities and  the fact that the server is a virtual.

As a side note, if you want the details of this bug, you can find them on the Microsoft Connect website: I was working with Chandru, a Senior Dev with Microsoft who was also great to work with - if you read this, thanks for all your help Chandru!

If this helped you, please let me know in the comments!