I've recently upgraded to TFS - RC and all is going well, except for Team Build.
All the solutions build successfully when they are on their own (i.e., in their own individual build), however when I combine them up into a single Team Build, it crashes part way through with the following Error in the Application Log. (Below)
I can't see any errors in the build log, it just stops !
I have tried several orderings of solutions, and it seems to die around the same point, which is in the the 5th solution, regardless of which solution the 5th one actually is !.
Any thoughts
Regards
Mark.
Application log Error:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 6/03/2006 6:27:56 AM
Machine: VISDEV05
Application Domain: msbuild.exe
Assembly: Microsoft.TeamFoundation.Build.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: MSBuild
Process Id: 4920
Thread Id: 4928
Account name: CORP\tfsservice
Detailed Message: A database error occurred (SQL error 512)
Exception Message: A database error occurred (SQL error 512) (type SoapException)
Exception Stack Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.Build.Proxy.BuildStore.AddProjectDetailsForBuild(String buildUri, ProjectData project)
at Microsoft.TeamFoundation.Build.BuildLogger.AddProjectDetails(String projectFile, String parentProjectFile, String platform, String flavor, Int32 compileErrors, Int32 compileWarnings, Int32 staticAnalysisErrors, Int32 staticAnalysisWarnings)
at Microsoft.TeamFoundation.Build.BuildLogger.LogProjectFinishedEvent(Object sender, ProjectFinishedEventArgs projFinishedEventArg)

Errors in Team Build - TFS RC
Tatakau
Hi Manish,
I just checked MSDN and don't see a 'post RC build' for the TeamBuild. Where is this available from please
Regards
ksalter
Can you give the project hierarchy of your combined build type This looks like same issue as http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=244702&SiteID=1&mode=1 that we have fixed post RC.
Thanks,
Gautam
Desperate Jaap
Hi Manish,
I am not sure exactly what you mean by 'mapped to workspace'. Where is this mapping done / checked (Outside of the database)
I have checed the dbo.tbl_workspace and Workspace ID 96 has a WorkSpace name of "VISDEV05_Wisdom_BuildAll" and a Computer of "VISDEV05" which is correct.
Checking the dbo.tbl_WorkngFolder table for Workspaceid= 96, it has
ServerItem = "$\Wisdom\"
LocalItem = c:\viseandev\teambuild\Wisdom\BuildAll\Sources\
MappingType=true
This appears correct to me, as $\Wisdom\ is the root of the Project, so I assume covers ALL sources/sln's under it.
This is the only pair of entries for the build server.
Regards
VinnieThaMadeMan
Mark - I checked with Chaitanya and it looks like you need to instal from the post RC build.
Regards
pfdeveloper
Hi Marlyn,
Yes, there is no post RC build that is official released. Sorry for the confusion.
We have fixed the bug and it will be available in next official release that should be happening soon though I do not have the dates.
Is it possible for you to wait for the official build Else, I have to check back on how best we can get the workaround available in your hands. The change is in our SQL script on the DT.
Thanks,
Gautam
mcclgn
Mark,
Can you make sure that all the sources/sln's present under the "sources" folder are mapped to workspace which is created by the build process (i.e. createworkspace task)
nbl
Thanks a lot.
Gautam
Tran Van Thang
Hi Gautam,
I've worked around it now with multiple build projects, so yes, happy to wait until the release version to fix the issue.
Thanks
Mark.
danillo ciafrei
Marlyn,
Your workspace and folder hierarch is fine.
As gautam pointed out, this is a known issue (bug) and we have fixed it post RC. Please refer the post for details- http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=244702&SiteID=1&mode=1
Thanks,
Tim McDaniel
Thanks for the quick response.
Is there a patch or a workaround available This issue is currently stopping our build server from running our automated build&deploy system on the RC.
Thanks
Mark
David
Hi Gautam.
Is there an Easy way to generate this project Heirarchy
I have attached the contents of the Build File, and the Build Log, and what appear to be other related files below.
Regards.
Mark