Team Foundation Build Service 2010 Controller / Agents and FQDNs

by GaryG 20. July 2010 05:33

I know I usually write about Project Management related topics so I ask my regular readers to please bear with me.  This one was a real pain to solve so I wanted to share it since TFS 2010 is fairly new and and error its giving out doesn’t really help.  Recently while working with an enterprise client in a TFS2008 to TFS2010 migration (a real pain in itself) we came across an error in setting up the Team Build Service.  The topology here put the TFS application tier on one server and the Team Build Service on its own machine (a Windows 2008 Server), and both the Controller and Agents were on this machine. 

The problem we saw was that the the controller and agents couldn't connect (and of course all the team builds failed).  The error was:

"There was no endpoint listening at http://somemachine.company.com/Build/v3.0/Services/Contoller3 that could accept the message.  This is often caused by an incorrect address or SOAP action.  See InnerException, if present, for more details."

The error was displayed in the properties dialog for both the Controller and Agent as in the below screenshot:

image

 

After a lot of head banging, setting up traces, and a reinstall I realized that for some reason the configuration wizard put the FDQN (Fully Qualified Domain Name) rather than the machine name.  Having debugged an issue on another products Web Service I decided to change it to use just the Machine Name and it instantly connected both the Controller and Agents.

This fix is simple thankfully.  Change the local build service endpoint to NOT use a FQDN but just the machine name, restart the Build Controller and Agents.

To do this just get into the TFS Administration Console on the Build Server and click the Build Configuration node. From here click the Properties on the Build Service and you will get the following window:

image

The “Local Build Service Endpoint (incoming)” will be grayed out until you click the “stop to make changes” link.  Click the link to stop the service then click the Change button to change just the FQDN to the machine name.  From here just click the Start button and your Controller and Agents should be talking fine.  It may take a minute once you restart the Build Service for everything to reestablish communication.  I hope this helps someone on another TFS 2010 deployment.

Comments (6) -

garyg
garyg
9/9/2010 11:09:08 AM #

test

Reply

garyg
garyg
9/9/2010 11:17:07 AM #

test 2

Reply

Robert Adamczyk
Robert Adamczyk
11/5/2010 10:14:33 PM #

THANK YOU!!!  I was having this exact problem and this was the fix.  You saved me a lot of time.

Reply

lu
lu
12/25/2010 12:11:29 PM #

Hi, I am just wondering why you covered (or censored) your computer's name? who can do anything with that?

Reply

garyg
garyg
1/2/2011 9:13:44 AM #

Good question.  I blocked the name more for client privacy than anything else.  It wouldn't have added anything to the content by using actual system names

Reply

best domain hosting
best domain hosting
2/28/2012 4:59:24 PM #

Hi, I am just wondering why you covered (or censored) your computer's name? who can do anything with that?
http://www.webhostingmasters.com

Reply

Add comment




  Country flag
biuquote
  • Comment
  • Preview
Loading


About the author

   
Gary Gauvin is a 20+ year Information Technologies industry leader, currently working as the Director of Application Lifecycle Management for CD-Adapco, a leading developer of CFD/CAE solutions. Working in both enterprise environments and small businesses, Gary enjoys bringing ROI to the organizations he works with through strategic management and getting hands-on wherever practical. Among other qualifications, Gary holds a Bachelor of Science in Information Technologies, an MBA, a PMP (Project Management Professional) certification, and PSM (Professional Scrum Master) certification.  Gary has also been recognized as a Microsoft Most Valuable Professional.

LinkedIn Profile: http://www.linkedin.com/in/garypgauvin

(Note: Comments on this blog are moderated for content and relevancy)


 

Month List

Page List