Team Builds error when connecting to the build machine.
Hi!
I'm currently trying to configure a build machine into my team foundation server environment, but I cant get it to work!
When I'm from a client is trying to trigger a build of my project I get the following errormessage:
TF42046: The build service used in the build process is not reachable. This error occurs when either the build machine is off-line, the required service is not running, Team Build is not installed on the build machine, Team Build is configured for a different Team Foundation Server or the network is not available. Contact your Team Foundation Server administrator to confirm that Team Build is correctly installed and running, or contact your network administrator to confirm the build machine is available.
I have checked everything and I cant figure out what's wrong, so I hope someone here can help me.
My environment is the following:
- A server where TFS is running
- Developer workstations with VS2005 with Team Explorer installed
- Team Build Computer where I want the build service to run
- I have on this computer installed Team Foundation Build from the TFS CD (bb folder)
- All computers in the network is a workgroup environment
- All users is created on the server that is on the developer stations
- The build user on the build computer is also on the server
- All access to TFS is verified OK for the user running the build service and other users in the environment
Does anyone know what may be wrong?
--Rune
Hello Rune,Would you please check the following:
1. Log on to the build server machine and check if "Team Build" service is up and running
2. Try pinging the build machine from the client with build service account credentials
Also, is your build server SKU installed on the TFS machine itself or a separate machine?
A quick addition...If you are using B3 bits in a workgroup env, your setup must be configured as App Tier, Data Tier and Build server all on the same machine.
Please let me know if that is not the case in your setup. Hi!
Yes, it's B3 in a workgroup environment... And the app and data tier is on the same server, but the build tier is on a another...
So if you are running a workgroup environment everything has to be on the same machine? Why's that? Shouldn't it be enough to have the same user with the same credentials on both computers?
Sry for this late answer, I am away on a business trip, and just got some time to reply!
--Rune
In a workgroup environment, the build server has to be on the app tier in Beta3.
The build machine used a secure remoting channel from the app tier for connections - this does not work in a Workgroup scenario.
This issue has been fixed post beta3 - the protocol between the build machine and the AT has changed to use a non secure remoting channel.
For now, you will have to install the build server on the same box.
Thanks,
Kishore.
Ahh!
Thank you for the answer!
I am getting the same error. Have all TFS applications installed on the same machine, a brand new windows 2003 server with no other applications on it.
Looking at the logfiles of IIS, buildcontroller.asmx is causing a 500 error, strange becuase there are also some OK 200 responses for BuildStore.asmx
2005-11-04 01:40:21 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:32 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:32 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:32 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:32 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:32 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:44 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:40:44 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:12 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:12 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:12 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:12 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:16 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:28 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:28 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 - 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 401 2 2148074254
2005-11-04 01:41:28 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 - 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 401 1 0
2005-11-04 01:41:29 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
2005-11-04 01:41:29 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
2005-11-04 01:41:29 W3SVC3 192.168.16.10 POST /Build/v1.0/BuildStore.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:34 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:34 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
2005-11-04 01:41:34 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
2005-11-04 01:41:34 W3SVC3 192.168.16.10 POST /Build/v1.0/BuildStore.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:41 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:41 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:41 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:41 W3SVC3 192.168.16.10 POST /VersionControl/v1.0/repository.asmx - 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:41 W3SVC3 192.168.16.10 GET /VersionControl/v1.0/item.asmx sfid=1036,0,0,0,0,0,0,0,0,0&ts=632667517012500000&s=bhvPr%2FRHmRX4jQ%2FYv4WmgakU5jtPTP6BPyJMZrlhOIjNN2Ga%2BdWnJKuUjl7nBhm7YVbEOKSog3A2eLi34JvKcHol%2FsZoGOJ8p%2FZgvHgSNZuGt%2F%2BBx9zkkidzKLoyZmrgrp3Di%2F6BPjUlvUFpH0LRfu59EJXy%2Fsu3gc1nDZ0O%2FaI%3D&fid=1036 8080 SAVITAS\jgill 192.168.16.41 Team+Foundation+(devenv.exe,+8.0.50727.43) 200 0 0
2005-11-04 01:41:43 W3SVC3 192.168.16.10 POST /Services/v1.0/GroupSecurityService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
2005-11-04 01:41:43 W3SVC3 192.168.16.10 POST /Services/v1.0/AuthorizationService.asmx - 8080 SAVITAS\tfsService 192.168.16.10 Team+Foundation+(w3wp.exe[Team+Build],+8.0.50727.43) 200 0 0
the build service is running, and i can ping the build server, i should be able to since i am able to connect with team explorer.
Any thoughts?
Is this issue solved? I saw your post on another
thread saying you got the build working.
If not, Please provide answers to below.
1. Are you getting the same error mentioned in the first post? Is your setup a workgroup setup( ie. machine belongs to a workgroup and not a domain).
2. Is the account running the build service a member of the "Build services" group for that team project?
Thanks
Kishore.
Hi!
We are experience the same problem described above.
When we turned on the system.diagnostics in the web.config file in the WebServices directory we could see this error message about a "illegal characters in path".
What is that? We have no clue what path it's complaining about.
- The Team System Machine host all the services and the application tier.
- It's a member of the domain.
- The TFSServices account is running the TeamBuild service and is a member of the build service group.
- The team project is a very simple Hello World program with NO FOREIGN characters or spaces in the project.
The log....
[TB] [Error, PID 2080, TID 1100, 08:34:19.296] {
[TB] [Error, PID 2080, TID 1100, 08:34:19.405] Exception: {
Exception Message: Exception has been thrown by the target of an invocation. (type TargetInvocationException)
Exception Stack Trace:
Server stack trace:
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Runtime.Remoting.RemotingConfigHandler.RemotingConfigInfo.StartupWellKnownObject(String asmName, String svrTypeName, String URI, WellKnownObjectMode mode, Boolean fReplace)
at System.Runtime.Remoting.RemotingConfigHandler.RemotingConfigInfo.StartupWellKnownObject(String URI)
at System.Runtime.Remoting.RemotingConfigHandler.CreateWellKnownObject(String uri)
at System.Runtime.Remoting.IdentityHolder.CasualResolveIdentity(String uri)
at System.Runtime.Remoting.Messaging.MethodCall.ResolveType()
at System.Runtime.Remoting.Messaging.MethodCall.ResolveMethod(Boolean bThrowIfNotResolved)
at System.Runtime.Remoting.Messaging.MethodCall..ctor(Object handlerObject, BinaryMethodCallMessage smuggledMsg)
at System.Runtime.Serialization.Formatters.Binary.BinaryMethodCall.ReadArray(Object[] callA, Object handlerObject)
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryRequestMessage(String objectUri, Stream inputStream, Boolean bStrictBinding, TypeFilterLevel securityLevel)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
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.Common.IBuildAgent.IsBuildInProgress(String teamProject)
at Microsoft.TeamFoundation.Build.Server.BuildController.StartBuildInternal(BuildParameters buildParams)
Inner Exception Details:
Exception Message: Illegal characters in path. (type ArgumentException)
Exception Stack Trace: at System.IO.Path.CheckInvalidPathChars(String path)
at System.IO.Path.Combine(String path1, String path2)
at Microsoft.TeamFoundation.Build.Client.BuildAgent.GetMSBuildLaunchEnvironmentPath()
at Microsoft.TeamFoundation.Build.Client.BuildAgent..ctor()
}
[TB] [Error, PID 2080, TID 1100, 08:34:19.405] }
[TB] [Error, PID 2080, TID 1100, 08:34:19.421] {
[TB] [Error, PID 2080, TID 1100, 08:34:19.421] Exception: {
Exception Message: TF42046: The build service used in the build process is not reachable. This error occurs when either the build machine is off-line, the required service is not running, Team Build is not installed on the build machine, Team Build is configured for a different Team Foundation Server or the network is not available. Contact your Team Foundation Server administrator to confirm that Team Build is correctly installed and running, or contact your network administrator to confirm the build machine is available. (type BuildException)
Exception Stack Trace: at Microsoft.TeamFoundation.Build.Server.BuildController.StartBuildInternal(BuildParameters buildParams)
}
Does the PATH environment variable on your machine have quotes in it like d:\temp;"d:\program files\MyApp";...
If so, remove the quotes from the Path (using My Computer-> properties ->Advanced ->Environment Variables) , stop and start the Team Build Service.
This issue has been fixed post Beta3.
If the above is not the issue, can you send me the value of PATH variable.
That solved the problem!
It was Norton Ghost who messed up the path string...
Cheers m8! :D
