TF42057: build request is not from the configured team foundation server

TF42057: build request is not from the configured team foundation server

• Wim 2005

  Yes same fix for me too. The way I found it was simply to look at the event log on the Team Server. It logged a "file cannot be accessed because already locked by another process" error, which prompted me to check for more than one thread in the TFS IIS app pool which was the case, and as you found setting it to one ("turning off web garden feature") fixed the problem.

  TFS is aparently not certified for multi-threaded operation. Could hinder scalability Or MS need to fix it. I wonder what guidelines are there for app pools with Team System. It's a bit odd to have bottlenecks on file locks on the server-side. Surely all the stuff it works with will be in the database, especially for Team Build (just source). If it were my code I'd be concerned about that design/implementation.

  
  

• chris22ka

  TFS does not currently support web gardens, though we are looking into numerous approaches to improving scalability for future releases. This should be documented somewhere, though I couldn't tell you exactly where to look. Incidentally, web gardens involve multiple processes, as opposed to multiple threads.

  Do you have any more information available on the file lock issue you mentioned What file was being accessed Was it really a Team Server issue, or was the access by multiple processes on the build machine

  -Aaron

  
  
  

• Sergey Dubinets

  Chris,

  Can you provide me details of your setup of your TF Server Is it a single server setup

  Are the TF Server and the Build server of the same version

  Are you able to run builds for other build types / teamprojects

  Thanks

  
  
  

• Electronic Screw

  This is beyond frustrating.
  
  IF the CORRECT server name is entered in the AllowedTeamServer field, then I get the message "TF42057: The build request is not from the configured Team Foundation Server"
  
  IF the INCORRECT server name (could be anything) is in the AllowedTeamServer field, then I get the message "TF42053: The build machine is not configured to build for server http://foundation:8080/'...
  
  
  
  
  

• v-lijieh

  For future reference,
  Kishore solved this problem. My IIS server running the application tier had a Web Garden setting of 10. When this value was reset to 1, team foundation build started functioning properly.
  
  Thanks Kishore!
  
  
  Chris Lively
  
  
  
  

• JanT [MVP]

  The TF42057 message is only used when the build service calls back to the app tier to verify the request.  It passes back to the server the information that was passed to it.  For that to fail is really odd because it means that the build service called the server successfully but the server returned false.

  Have you moved your server   Changed the name of the machine   Anything like that

  Try clearing the cache directory for the service account used to run the build service on the build machine.  Delete the directory C:\Documents and Settings\<<ACCOUNT>>\Local Settings\Application Data\Microsoft\Team Foundation.  Then restart the build service on the build machine.

  Buck

  
  
  

• Carver42

  I just set up a brand new machine (from OS install on up) and I am still receiving this same error.
  
  So far, I have modified the AllowedTeamServer key in the tfsbuildservice.exe.config file to point to http://foundation:8080/ (foundation is the name of my application tier).
  
  I have also modified the reg key for AllowedTeamServer to point to http://foundation:8080
  
  Also, I restarted the entire server after each change. 
  
  What else is there
  
  Thanks
  
  
  

• Samer Selo

  Hi Buck / Kishore,
  I have not moved or renamed any of my Team Foundation servers (application, data, etc).
  
  The Build machine is a brand new install with only 2003 Server Standard SP1, Team Foundation Client, and Team Build on it.  The application tier is running 2003 Server Standard R2 with SP1.
  
  I deleted that directory from the build machine, rebooted the machine, and am still getting the same message. I have tried kicking off the build process directly from the build machine (command line) and my VS2005 environment on my main desktop.
  
  The overall setup is 1 application tier, 1 data tier (sql 2005 standard), and 1 build machine. These are all on physically separate machines, I am not running any sort of virtual server software.
  
  It has never built a project before. This particular project is a small assembly.
  
  I'm in the process of setting up another brand new build box, this should take another 30 minutes. I won't put Team Foundation Client on this one.
  
  
  

• thanks

  Well, I just finished creating a brand new build box. I installed Windows 2003 Server Standard w/SP1, applied all of the available updates, and installed only Team Build.
  
  It gave the exact same error message.
  
  To me, this means the problem is either on the application or data tiers.
  
  Thoughts
  
  
  

• Mister_Vee

  Chris,

  Please enable tracing on the application tier and send me the logs. On the application tier,

  - enable tracing by setting the “tracewriter” value to true in the web.config, and setting the switches values to 4.

  Run the build, this will generate logs under %windows%\temp\tflogfiles. send the one with the teambuild exception message to kishormn at microsoft dot com.

  Do you also see the same error in the Event log on the Build machine

  
  
  

• Lars Breiter

  Each build machine is only allowed to "talk" to one TFS - an attempt to start a build on a build machine from a different TFS give the error you are encountering. So - on your build machine (which I gather is the same machine as your TFS AT) you will need to locate TFSBuildService.exe.config (typically this is in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies) and add/modify the AllowedTeamServer value. Make sure to restart the service after modifying this value.

  -Aaron

  
  
  

• Lourdes

  This is as good a spot as any, I think! I'll investigate this case - please let us know if you run into other cases where you think the error messages are bogus.

  -Aaron

  
  
  

• SpencerInLa

  Okay, I just added a c:\logs directory to my build machine. It wasn't there before and suddenly this message is gone, albeit there are others.
  
  Is there someplace we can post to microsoft about invalid error messages
  
  
  

• Mark Levison

  I take it back. I'm at the same place I was to begin with, with the same error. I have no idea why it worked once. The only thing in the build machine log is:
  
  [Info, PID 1780, TID 1952, 19:43:19.750] Params: tfsServer = http://foundation:8080/
  [Info, PID 1780, TID 1952, 19:43:19.859] Params: teamProject = Panther
  [Info, PID 1780, TID 1952, 19:43:19.859] Params: buildType = E3Access3
  [Info, PID 1780, TID 1952, 19:43:19.859] Params: buildDirectory = C:\Builds\E3Access
  
  
  
  Which is accurate...There is nothing in the event logs of either machines to indicate a problem.
  
  Is there some place else that I can look for logging
  
  
  
• TF42057: build request is not from the configured team foundation server