More on running multiple TFS build controllers on a single VM
I have been having a on-going project to run multiple build controllers on a single VM. Today I needed to reconfigure a on of the controllers to point at a different TPC. You have to do this the correct way to avoid problems.
My error log was full of
Http communication failure:
Exception Message: Cannot listen on pipe name 'net.pipe://build/ServiceHost/1' because another pipe endpoint is already listening on that name. (type AddressAlreadyInUseException)
It all boiled down to the fact I ended up with two controllers trying to use the same URI, in my case
The number at the end of this URI is assigned when the controller is registered with a TPC. If, as I did, you just stop a controller and edit its properties to point at another TPC and restart it, it is possible to end up with two controllers on the same box trying to use the same ID.
The simple fix is to unregister the build controller and the register it with the new TPC as needed. This will cause the machine to be scanned and new, empty ID chosen for the URI. As as detailed in Jim Lamb’s original post.
As a side effect I also saw errors in the log saying custom activity assemblies could not be loaded due to permission errors. This all turned out to be that the custom activities are stored in
C:\Users\[tfs build account]\AppData\Local\Temp\BuildAgent\[agent ID]
So if two agents have on the ID, even if one’s parent controller is failing to load fully, it will tend to lock the files for the other controller. Again this was fixed by registering the controller and agents in the correct manner
Read the complete post at http://blogs.blackmarble.co.uk/blogs/rfennell/archive/2011/07/25/more-on-running-multiple-tfs-build-controllers-on-a-single-vm.aspx