![MSBUILD : error MSB4015: The build stopped unexpectedly because the "WorkflowCentralLogger" logger failed unexpectedly during shutdown. System.ArgumentException: '.', hexadecimal value 0x00, is an invalid character. at System.Xml.XmlConvert.VerifyCharData(String data, ExceptionType invCharExceptionType, ExceptionType invSurrogateExceptionType) at System.Xml.XmlCharCheckingWriter.WriteString(String text) at System.Xml.XmlWriter.WriteAttributeString(String localName, String value) at Microsoft.TeamFoundation.Build.Client.InformationField.ToXml(XmlWriter writer, String element) at Microsoft.TeamFoundation.Build.Client.Helper.ToXml(XmlWriter writer, String element, InformationField[] array) at Microsoft.TeamFoundation.Build.Client.InformationAddRequest.ToXml(XmlWriter writer, String element) at Microsoft.TeamFoundation.Build.Client.Helper.ToXml(XmlWriter writer, String element, InformationChangeRequest[] array) at Microsoft.TeamFoundation.Build.Client.BuildWebService.UpdateBuildInformation(InformationChangeRequest[] changes)](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgp6irzzOHi-o7aPeNYZQD5REE6huRd3hM_YbQdHpHa00ZrziXwGZ9_ZObETRvvR9XnVNsFvn-8NYenC1o0kh9bAxnOe-qBrC32BBuZwzgI7p-oGHigHTmuug8KPEIttn2HUAtASciwnPo/s1600/msbuilderror.png)
Based on the stack trace, it looks like there was a problem converting the build output to XML, so it was just a matter of finding the culprit. A quick search through the build output using PowerShell located the offending \0 character (which it is not possible to represent in XML), so I loaded the build log into NotePad++ to confirm:
Hopefully this will help anyone else who may run into this issue in TFS.
0 comments:
Post a Comment