Team Build unable to Run Auto Builds now

Team Build unable to Run Auto Builds now

• chinimimita

  I'm afraid it sounds like your best bet is to go to RTM. Based on the timeline you mentioned above you should be about there by now

  Brian

  
  

• Absolute_Zero

  This weekend we upgrade to RTM.

  Everything looked good, but then problem happened again intermittently.

  I dont know if this is the culprit. I added this at the very end of the TFSBuild.proj, right before </Project>

  My goal is to get the autobuild to package the code after it is built.

  Is this also the correct way to include the build packages

  Added code:

  --------------------

  <Target Name="AfterCompile">

  <Exec Command="&quot;$(VS80COMNTOOLS)\..\IDE\devenv&quot;&#xD;&#xA;&quot;$(SolutionRoot)\WCF-Prototype\SetupMarsServer\SetupMarsServer.vdproj /Build &quot;Release|Any CPU&quot;" />

  <Copy SourceFiles="$(SolutionRoot)\WCF-Prototype\SetupMarsServer\Release\SetupMarsServer.msi" DestinationFolder="$(OutDir)" />

  <Exec Command="&quot;$(VS80COMNTOOLS)\..\IDE\devenv&quot;&#xD;&#xA;&quot;$(SolutionRoot)\MARS_UI\MARS_UI_WebSetup\MARS_UI_WebSetup.vdproj /Build &quot;Release|Any CPU&quot;" />

  <Copy SourceFiles="$(SolutionRoot)\MARS_UI\MARS_UI_WebSetup\Release\MARS_UI_WebSetup.msi" DestinationFolder="$(OutDir)" />

  <Exec Command="&quot;$(VS80COMNTOOLS)\..\IDE\devenv&quot;&#xD;&#xA;&quot;$(SolutionRoot)\MARS_ASP_Website\MARS_ASP_WebSetup\MARS_ASP_WebSetup.vdproj /Build &quot;Release|Any CPU&quot;" />

  <Copy SourceFiles="$(SolutionRoot)\MARS_ASP_Website\MARS_ASP_WebSetup\Release\MARS_ASP_WebSetup.msi" DestinationFolder="$(OutDir)" />

  </Target>

  
  

• Jerry-liu

  Any chance the proxy settings in IE are incorrect for the account that's used to do the build   Did the password expire

  Buck

  
  
  

• dude4453169

  You might be able to build from the IDE since the solutions are locally present on your machine. Can you try pinging the server from the client to make sure it is accessible
  
  

• richard_deeming

  Maybe Anu has a guess as to what's going on, but at this point the best thing would be to upgrade to RTM. Beta 3 is now not supported since v1 shipped two months ago, and beta 3 itself is based on code that's about 8 months old. There were a lot of fixes made after beta 3.

  Buck

  
  
  

• tomas77777

  Thanks.   We are planning on upgrading in 3-4 weeks.  I cant wait.  I think most of my headaches would be fixed by using the finally product.

  I think I have narrowed down the problem.  It seems to hang now for some reason on the last project of the solution in the corecompile section.   Eventually, Ill get the error message in the original post.

  Still puzzled on why it worked since yesterday at 10:30AM till 10:00AM this morning.   I asked around if anything changed.  The answer was no.   The event logs dont appear to have anything that points to what the problem might be.

   

  Any suggestions would be appreciated.

   

  Thanks,
  staffan

  
  

• Jacquemin

  Thanks for the suggestion. I checked the settings and they havent changed. The password hasnt changed either.

  We bounced our Team Foundation Server on Friday in the hope that memory would be cleared and the problem fixed. Unfortunately, it didnt help. :-(

  It checks out and starts to build, but gets hung up on the last project of the last solution.

  Maybe it is just the VSTS Beta 3 version that has issues. I wish I knew the work around.

  Any other suggestions

  Thanks,
  Staffan

  
  

• Dave J

  FYI We are using Beta 3 version of the Team Foundation.
  

• nehajampala

  Thanks for your response :-)

  I pinged the machine and it comes back with replies.

  Extra note: Im able to check the code out manually. Im more puzzled now.

  Any other suggestions or ideas

  
  

• xp

  The exception you reported in your original post is a "Request timed out" httpexception. These are caused when a request takes longer than the specified executionTimeout in the config file chain... Is this the same exception you are seeing now

  If so, I believe that the executionTimeout value is set to 3600 seconds (one hour) in the default TFS install, but you should verify that the value is not something smallish that might realistically cause a timeout to occur. You would want to look first in the web.config file in the build web services directory - something like "C:\Program Files\Microsoft Team Foundation 2005\Web Services\Build". Probably the relevant value will not be set there - you should then check the team foundation directory, which is just one directory up. If it is not set there either, the value will be coming from your machine.config, and is probably the default value of 90 seconds, which may be small enough that it gets exceeded when your network is not behaving well.

  In any case, the relevant setting will look something like this:

  <httpRuntime executionTimeout="3600" maxRequestLength="2000000" />

  Can you report back on the value you find for executionTimeout

  -Aaron

  
  
  

• Dan Prudhoe

  Problem occurred again. I dont know why. It has been working fine for a few months. For some reason, this morning it just wont allow to be built on the machine.

  Is there a bug fix for this It is like something is flagged as not being connected.

  Please help since this is getting very frustrating. I dont want to have to different machines to build on.

  Thanks,

  staffan

  
  
• Team Build unable to Run Auto Builds now