Reputation: 54127
I am troubleshooting a failing TFS 2015 build that I have inherited, which has the following error:
This error is almost certainly a character encoding issue in a batch file (as 
is how a UTF-8 BOM can be interpreted.
Source control contains a number of batch files which I and converted to UTF-8 (without BOM) using Notepad++.
This has not resolved the issue.
I hoped that TFS would contain logs that would tell me which file caused this issue, but the only log file I could find (ActivityLog.xml) this doesn't contain any information about this error.
Is there anywhere in TFS that contains additional logging information about build issues?
Upvotes: 1
Views: 283
Reputation: 31083
If you are using TFS 2012 XAML build, you can change the logging verbosity to Diagnostic
in Build Definition directly to get more build log.
If you are using TFS 2013 XAML build, you can pass the parameter:
/flp:verbosity="Diagnostic"
in the MSBuild arguments section, of the Process tab, in the build definition.
Additional, you can check event log in Event Viewer on your build agent machine to see whether there is more information there.
Upvotes: 1