Databases
StackOverflow2013
Postsdbo
POTFS Build errors TF224003, TF215085, TF215076
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTFS Build errors TF224003, TF215085, TF215076
    primarykey
    data
    text
    <p>I am using TFS2008 and VS2008. I run nightly builds for about 20 applications using one build agent and the builds are scheduled for either 1am or 2am. Most of the build succeed, however 6 of them fail regularly with similar errors. The errors are either the first two below, or the third one by itself:</p> <ul> <li>TF215085: An error occurred while connecting to agent \xxxx\BUILDMACHINE: TF215076: Team Foundation Build on computer BUILDMACHINE (port 9191) is not responding. (Detail Message: The request was aborted: The operation has timed out.) 11/04/2010 2:10:10 AM </li> <li>TF224003: An exception occurred on the build computer BUILDMACHINE: The build (vstfs:///Build/Build/2632) has already completed and cannot be started again.. </li> <li>TF215085: An error occurred while connecting to agent \yyyyy\BA_WKSTFSBUILD: Team Foundation services are not available from server srvtfs. Technical information (for administrator): The operation has timed out</li> </ul> <p>It looks to me like some kind of communication error, maybe the port gets over loaded - can this happen? Should I spread the builds out a bit more? In the build definition it says "Queue the build on the default build agent at", so I figured if I scheduled them to start at the same time they would be queued and occur sequentially. </p> <p>Most of the suggestions I've found online for these errors are for all or nothing scenarios where <strong>no</strong> builds work at all whereas my problem is most build but some consistently do not. Note that if I schedule the builds via <em>Team Explorer -> BuildDefinition -> Rightclick - Queue new build</em> they run without error. Judging by the dates of the last successful builds of these 6 failing builds I believe it is the same 6 failing every night. (I'm editing the build definitions now to keep the failed builds so I can get some more info on the problem)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjessehouwing
    1. USJames Gardner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POTFS Build errors TF224003, TF215085, TF215076
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTFS Build errors TF224003, TF215085, TF215076
      1. USPabloC
      1. VTFavorite
    3. VO
      singulars
      1. POTFS Build errors TF224003, TF215085, TF215076
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou say they are kicked off at 1 am or 2 am. Are the ones that are failing all triggered at the same time? I have the same problem and I suspect it's because the port is already in use by another concurrent build.
      singulars
      1. POTFS Build errors TF224003, TF215085, TF215076
      1. USPabloC
    2. CO@PabloC these errors occur intermittently, but yes I have the start times the same for about 5 projects. I think TFS should do some queuing to stop what you are suggesting from happening, but who knows.
      singulars
      1. POTFS Build errors TF224003, TF215085, TF215076
      1. USJames Gardner
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload