But it works on my PC!

The random thoughts of Richard Fennell on technology and software development

TF21508 Error, cannot see build server after moving a Hyper-V image

We have been consolidating our Hyper-V system of late, moving various older systems onto a new SAN based cluster. This has meant we have just moved our virtual TFS2008 build machines. After the move I started seeing the following error on all the builds using that server, re-enabling the build machine had no effect.


I restarted the build VM but this did not fix the problem; I had to also restart the TFS2008 AT, once this was done all was fine. I guess that there was a cached IP/ARP table somewhere routing packets the wrong way.

Technical Tip: if you can’t see the build server don’t just assume it is always the build server at fault, it might be the other calling machine i.e. the TFS AT

Interestingly our TFS2010 build machines did not suffer this problem.

TF250020 error creating new Team Projects

Whilst working on our TFS2010 Beta 1 test server today I got the following error when I tried to create a new team project

TF250020: The following SharePoint Web application is not valid: http://vs2010.mydomain.com. Verify that you have the correct URL.

I thought this strange, as I was doing nothing I had not done before, creating a MSF Agile team project with default settings. What I did notice was that in the new project wizard I had the server URL as http://vs2010 but the error message said http://vs2010.mydomain.com. So I checked the alternate access mappings in the WSS central admin, only vs2010 was listed, so I added vs2010.mydomain.com as the Internet alias and it all leapt into life when I tried the wizard again.

Question remains how did this work before, operating system service packs maybe?

Expression Suite Version 3 and Source Control

It is good to see that at last Expression Web and Blend have got source control integrated into their IDEs. This is a vital feature if developers and designers are to work together effectively on the same code. It is a shame that the integration is just for TFS, it would be nice to support other source repositories to get an even wider reach, but TFS is enough for me now.

Just remember that to get this integration to work you need to do a bit more than install Expression Suite

All seems to work though.

Visual Studio 2008 connecting to TFS 2010

You can connect a Visual Studio 2008 IDE instance to a TFS 2010 server, as detailed in Martin Hinshelwood’s blog, but I cannot stress enough you have to have VS2008 SP1 installed. If you don’t, you get an error dialog when you enter the URL for the TFS server saying the URL contains invalid characters.

This seems a simple rule, but as I found today it is easy to not realise your PC is not patched. You look in the about dialog for Visual Studio and it says SP1 installed, but the Team Foundation Client has not been. This was because the following installation order was followed:

  1. Install VS2008
  2. Patch with SP1
  3. Install Team Foundation Client

The SP1 needed to be run again to patch the client then all was OK

Video recording gotta for VS2010 Test Runner

VS2010 has excellent new features to assist the tester in general, and specifically in the area of manual testing. One of these is the ability to video a manual test run; to get this to work you have to have the Windows Media Encoder 9 installed as well as the VS2010 Test Runner . If you don’t have it installed and try to use the video feature you get a dialog that warns you this component is missing and would you like to either download it or disable video recording feature for this test run.

The problem is the warning dialog has a link that takes to you the Windows Media Encoder 9 homepage. This gives you the option to install either the 32bit or 64bit version. I mistakenly assumed that I needed the version for operating system I have i.e. 64bit as I run 64bit Windows 7. THIS IS WRONG.

VS2010 Test Runner only seems to work if you have to install the 32bit and the hotfix the Test Runner dialog mentions. Once I installed the 32bit video recording of the test worked perfectly.

And eScrum is no more

I have posted in the past about the TFS 2005 and 2008 Process Template eScrum from Microsoft; a template we use internally for a number of Agile projects. Well today it has been removed from the Microsoft download sites.

It was decided a while ago that it would not be updated to support TFS2010 and has been removed to avoid any confusion over whether it is support or not by Microsoft (FYI it was never officially supported anyway as it did not originate inside the TFS team)

So are we at Black Marble going to miss it? Well the main reason we had used it in the past was the web interface that gave a single point for updating the status of work items without the need to enter Visual Studio, it was our project wallboard. With the much enhanced Office integration with TFS2010 I think we are not going to miss eScrum. We can now provide an easy way with Excel or Project for any team member (developer or not) to update their work status and also Excel Services to provide a information radiator showing the overall project status.

If you do need a strict Scrum implementation template for TFS then have a look at Conchango’s Scrum for Team System which is going to be updated to make use of all the new features of TFS2010

Remember the new URL format for the TFS2010 web services have changed

To have a good look at TFS2010 I have migrated some existing VS2008 projects to VS2010. This has meant they are now being built using a new TFS 2010 build server. Now I wanted to make sure everyone still knew what was building and what was not, so I updated the configuration on our build wallboard to get the status from both the older 2008 and the new 2010 server – and it did not work. I fiddled around, upgraded the build wallboard to use the TFS2010 assemblies, all to no avail, the application just exited when I tried to get a reference to the build service.

Then I had another think, the Url of the TFS server has changed format in 2010. It used to be http://my2008server:8080 it is now http://my2010server:8080/tfs. I had been leaving off the trailing /tfs, an easy mistake to make. Once this was corrected my old build wallboard worked without a problem, there was no need to use the TFS2010 assemblies in the project.