Build Configuration - Build Controller unavailable

Question

It shows the controller is unavailable. I checked the proxy settings, but they were correct. It has been this way since we upgraded to TFS2010.

Log viewer info below:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="TFSBuildServiceHost"
/>

<EventID
Qualifiers="0">0</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-11-07T15:16:12.000Z" />

<EventRecordID>110938</EventRecordID>

<Channel>Application</Channel>

<Computer>txrv.BBB.com</Computer>

<Security />

</System>

- <EventData>

<Data>Service 'fakeController' had an exception: Exception Message: There was
no endpoint listening at http://noservice:8888/Controller/3 that could accept
the message. This is often caused by an incorrect address or SOAP action. See
InnerException, if present, for more details. (type EndpointNotFoundException)
Exception Stack Trace: Server stack trace: at
System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout) at
System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message
message, TimeSpan timeout) at
System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan
timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action,
Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs,
TimeSpan timeout) at
System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
methodCall, ProxyOperationRuntime operation) at
System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: at
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg,
IMessage retMsg) at
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type) at
Microsoft.TeamFoundation.Build.Machine.IBuildControllerService.TestConnectionFromController(String
agentUri) at
Microsoft.TeamFoundation.Build.Machine.ServiceProxies.ServiceProxy`1.<>c__DisplayClass3.<Do>b__2(T
channel) at
Microsoft.TeamFoundation.Build.Machine.ServiceProxies.ServiceProxy`1.Do[TResult](Func`2
action) at
Microsoft.TeamFoundation.Build.Machine.BuildAgentService.<>c__DisplayClass12.<TestConnection>b__11(Object
) Inner Exception Details: Exception Message: The remote name could not be
resolved: 'noservice' (type WebException) Exception Stack Trace: at
System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at
System.Net.HttpWebRequest.GetRequestStream() at
System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()</Data>

</EventData>

</Event>

Answer 1

Hi,

Thanks for your post.

According to your description, you are using TFS Proxy, correct?

And do you mean the "fakeController" is unavailable after upgrade? I notice there is another build controller, is it working well? Is the Team Foundation Build Service configured to Use Team Foundation Server Proxy?

Could you please share us your upgrade steps?

Also, please try to clear client cache restored in C:\Users\username\AppData\Local\Microsoft\Team Foundation\3.0\Cache, and refer to the article below to check the configuration:

http://msdn.microsoft.com/en-us/library/cc716770(v=vs.100).aspx

Best regards.

 

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 2

The other two controllers appear to be working fine. The fakebuild controller is the only one that does not work. It is what is used to help update the 'build included' fields of work items during builds, which manually gets completed now. Otherwise, our builds have been running with no issues.

Our upgrade was completed using the Microsoft instructions for an upgrade. We run the builds from two builds machines, not the server that TFS is installed on.

Answer 3

The location of the cache in that directory shows 3.0 not 4.0...is that a problem?

Answer 4

Hi,

The location of the cache in that directory shows 3.0 not 4.0...is that a problem?

Sorry my typo, it should be 3.0 since you are using TFS 2010.

After updating the 'build included' fields of work items manually, does the fakeController still can't work?

Have you clear the cache in folder 3.0? How is the result?

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 5

No, didn't delete the cache because I wasn't sure if that was correct.

For clarification, build included had been getting updated manually because the fakecontroller wasn't working.

I'll delete the cache.

However, I am reluctant to mess with the registry settings suggested in: http://msdn.microsoft.com/en-us/library/cc716770(v=vs.100).aspx

because the other parts of the build works correctly.

Answer 6

Hi,

Sorry for my misleading.

The link above explains the steps that when you want to configure Team Foundation Build Service to retrieve files from Team Foundation Server Proxy. Maybe not appropriate for your scenario.

Besides clearing the cache C:\Users\username\AppData\Local\Microsoft\Team Foundation\3.0\Cache, please also clear the cache C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v10.0.

Let us know if cleaning the caches can fix your issue.

Best regards.

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 7

Made the change and the controller status has not changed...ran a build over the weekend, and it had issues. Not sure if it is related to the removal of the cache or not yet.

Answer 8

Hi,

Clearing cache shouldn't effect your builds result. I'm going to report your issue to our senior engineer, maybe some time delay, appreciate your patience.

Best regard.

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 9

Issue was caused by something else. But, the original issue is still unresolved.

Thanks for contacting the senior engineer.