Team Build failure

Using beta3, I have a team project (solution) containing 3 projects. When I do the team build on this solution I get the following errors:

Build FAILED.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(2797,9): error MSB3491: Could not write lines to file "obj\CadetCommandBase.vbproj.FileList.txt". Access to the path 'd:\builds\CadetCommand\CadetCommandTest\Sources\CadetCommandBase\obj\CadetCommandBase.vbproj.FileList.txt' is denied.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(3021,9): error MSB3491: Could not write lines to file "obj\CadetCommandBase.vbproj.FileList.txt". Access to the path 'd:\builds\CadetCommand\CadetCommandTest\Sources\CadetCommandBase\obj\CadetCommandBase.vbproj.FileList.txt' is denied.

The reason access is denied is because the file is marked read-only. I have tried removing the read-only property, but on the next build effort the file is marked read-only again by the team build process. Is this a bug If not how do I get around this problem

Answer this question

Team Build failure

BillTodd
This is not a bug. These files seem to have been checked into Source Code Control. These are intermediate files generated by the build, so should not be checked in. Please remove them from SCC and try again.
muga
I tried building another project and now I get this error.

Target InitializeWorkspace:
    Workspace ACMONAPDB20P_CadetCommand_CadetCommandTest does not exist.
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error : The path d:\builds\CadetCommand\CadetCommandTest\Sources is already mapped in workspace ACMONAPDB20P_CadetCommand_CadetCommandTest.
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018: The "CreateWorkspaceTask" task failed unexpectedly.
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018: Microsoft.TeamFoundation.VersionControl.Client.MappingConflictException: The path d:\builds\CadetCommand\CadetCommandTest\Sources is already mapped in workspace ACMONAPDB20P_CadetCommand_CadetCommandTest.
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.TeamFoundation.VersionControl.Client.InternalCache.CheckForMappingConflicts(WorkspaceInfo workspace)
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.TeamFoundation.VersionControl.Client.InternalCache.CheckForMappingConflicts(Workspace workspace)
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.TeamFoundation.VersionControl.Client.Client.CreateWorkspace(Workspace workspace)
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer.CreateWorkspace(String name, String owner, String comment, WorkingFolder[] mappings)
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.TeamFoundation.Build.Tasks.CreateWorkspaceTask.Execute()
    C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets(275,5): error MSB4018:    at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)
Done building target "InitializeWorkspace" in project "TFSBuild.proj" -- FAILED.

This process appears to be very finicky and too complicated for normal use. We've never had these types of problems doing local builds in Visual Studio and we're not going to be able to use team build if we have to hold our breath every time wondering what is going to fail this time. The "administrative" problems in making this work are intolerable.
musichenryviolin

Sorry for the inconvenience rdulpo. But this error is arising because the build directory you are trying to build into(d:\builds) is already mapped by another user in another workspace. This might have happened due to changing the build service account after setup. < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Would you please try building in a separate build directory (preferably one that is not yet existent on the file system)

You might also want to look at this post for an alternate solution to your problem.

Re your previous problem of FileList.txt, this problem has risen because you have not added the solution to source control from within VS. VS will automatically filter out these files for you and hence evade the problem.

Please let me know if you have more queries.
Team Build failure

Answer this question