RE: TFS 2008 Team Build: Error connecting to remote build agent

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I got it resolved by

- Disable Firewall if the operating system is windows server 2003
- If the operating system is Windows server 2008, try following steps
1. Open Server Manager -> Configuration -> Windows Firewall with Advanced
Security -> InBound Rules.
2. Right Click InBound Rules and select New Rule.
3. Click on "Port" radio button and press Next button.
4. Enter 9191 in Specific local ports text box.
5. Click Next until you finish.

"Dan Sloan" wrote:

Hi everyone,

I am trying to get a remote build agent to work in a TFS 2008 environment
and I'm having some difficulty. If anyone has any guidance for
troubleshooting this, I'd really appreciate it.

Issue:

* When I queue builds from Team Explorer, I get the following error:

TF215085: An error occurred while connecting to agent
\[MyTeamProjectName]\BUILD_AGENT_BOX: TF215076: Team Foundation Build on
computer BUILD_AGENT_BOX (port 9191) is not responding. (Detail Message: HTTP
code 403: Forbidden)

Here's the situation:

******* Build Agent Machine *******

TFSBuildService.exe is running - and I've run it both under
NTAUTHORITY\Network Service, as well as a domain account that has
administrative rights on the box. For the latter configuration, I added that
domain account to the team project's [Build Services] TFS group. Neither
configuration seems to resolve the issue.

I have reviewed TFSBuildService.exe.config for all of the normal
configuration settings and everything looks good, including:

<add key="port" value="9191" />
...
<add key="AuthenticationScheme" value="Ntlm" />
...
<add key="AllowedTeamServer" value="http://TFS_APP_TIER_BOX:8080"; />
...

******* TFS App Tier Machine *********

To try and troubleshoot the issue, I remoted to the app tier box and was
able to perform the "telnet test" to port 9191 successfully, so I know that
this box can talk to the build agent box and it recognizes that port 9191 is
in use. I am not aware of any firewalls between the two machines.


******* Common Stuff **************

-- Both the app tier box and build agent box are on the same domain.
-- There are no errors in the build agent's event log.
-- I have started a build agent on the app tier box and can queue builds up
to that machine successfully. This only appears to be a problem when the
build agent is running remotely.


Any insight would be greatly appreciated!

Dan
.



Relevant Pages

  • RFCAS - The San Data Flow and Messaging Engine
    ... RFCAS - The San Data Flow and Messaging Engine ... think of an agent as being a mini-process. ... shorthand for port 0. ... A port can be connected to more than one pipe by using ...
    (comp.programming)
  • Re: minimum install & pickling
    ...  If you're running foreign ... There is support for imposing limits on processes in the Python ... the solutions ultimately come from the operating system: ... then anything with access to the agent can. ...
    (comp.lang.python)
  • SNMP version in agent response message
    ... I devellop a SNMP agent with Win SNMP API 2.0. ... SnmpSetTranslateMode ... User Datagram Protocol, Src Port: 1371, Dst Port: snmp ...
    (comp.protocols.snmp)
  • Re: RFCAS - The San Data Flow and Messaging Engine
    ... I'd just allow each agent to ... to leave a port exposed for some other entity to set up the connection. ... > (strings), ... Is there significant value in adding mailing lists? ...
    (comp.programming)
  • Re: SQL Server Agent
    ... nur der Agent kann keine Operatoren benachrichtigen. ... keine Fehlermeldungen. ... Ich habe einen SQL Server 2008 von einem Windows Server 2003 auf einen Windows Server 2003 migriert. ... Ich habe das nun auf Datenbank E-Mail umgestellt. ...
    (microsoft.public.de.sqlserver)