We're using Visual Studio Online, but we have local Build Controller and Build agent. This has been running fine for the past 6 months or so, but just this week the builds have consistently failed.
The software itself appears to build successfully, and the tests also seem to pass, but it fails due to an error during the publication of the log files (see error below).
The build uses an unmodified Default Template, and is setup so that it "does not copy output files to a drop folder" (in the Build Defaults of the build definition).
After a few hours of head-banging this feels like some sort of permissions thing, but I have no idea how to go about debugging, or verifying this assumption.
One thing to note is that this error is consistent across all builds that are executed through the same build controller. I've tried removing and re-registering the controller, restarting the build service and the build server itself.
Can anyone offer any suggestions, or better yet, a solution! :-)
One other thing to note is that we have been mucking about with our users in Visual Studio Online to change some accounts from Basic to Stakeholder accounts in order to reduce costs. I'm wondering if we've also managed to remove a critical account or permission that has caused this...?
An error occurred while copying diagnostic activity logs to the drop location. Details: TF270002: An error occurred copying files from 'C:\Users\tfs\AppData\Local\Temp\BuildAgent\5498\Logs\2853\LogsToCopy\ActivityLog.AgentScope.5498.xml' to 'ActivityLog.AgentScope.5498.xml'. Details: BadRequest: Bad Request An error occurred while copying diagnostic activity logs to the drop location. Details: TF270002: An error occurred copying files from 'C:\Users\tfs\AppData\Local\Temp\BuildController\4592\Logs\2853\LogsToCopy\ActivityLog.xml' to 'ActivityLog.xml'. Details: BadRequest: Bad Request
Thanks for your post.
I'd like to confirm with you did you try on another client machine? Could you reproduce this issue on another client machine?
Please try to clean the cache files in C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache. And you may also try with another Visual Studio Online account to login in. If the issue persists, you may try to set up a new build service to check whether the issue is due to build service.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
Thanks for the reply. Two things I've noticed since posting:
- The build machine was using v11 (TFS 2012) controller software
- Visual Studio Online was updated on 14th October
I've hastily built another build server with v12 (TFS 2013) controller software and this doesn't appear to suffer from the same issues (at least with the build of a simple project). I'm just in the process of testing a full build of our main project to see if this resolves the issue.