This project is read-only.
1
Vote

Does not generate the report

description

i've tried this app, all the way to the generate report part... but no matter what changesets i choose and click the generate release notes, a small windows quickly pops up and disappears, and nothing else happens... no html. Any ideas? can't see what is mentioned in that windows since it appears soo quickly.

file attachments

comments

Dharmesh_Shah wrote Nov 23, 2012 at 9:32 AM

Hi,

We know that we are missing some good logging and exception handling features in this version of the application and we will try to prioritize the same for upcoming versions.

In the mean time, it will help if you run this application from command prompt via "TFSChangeLogCL.exe" file that is present in the default installation location of TFS ChangeLog Appplicaiton.

Best Regards,
  • TFS ChangeLog Team.

wrote Feb 14, 2013 at 8:54 PM

guzzam wrote May 27, 2013 at 1:37 PM

Very useful tool but have some issues. Sometimes the GUI creates the html page and sometimes not. Seems to depend on the selected changeset range? Tried the command line version TFSChangeLogCL.exe but this one can not resolve the branch path correctly. Branch path is set to $/MyProject/Dev in the TFSChangeLogConfig.xml file. Produces this kind of output:

Generating Branch List from TFS ... Please Wait ... ... ...
Generating ChangeSet information from TFS ... Please Wait ... ... ...
Generating Change Log / Release Notes from TFS ... Please Wait ... ... ...
ERROR : Exception is : System.ArgumentException: Invalid name character in '_Project/WebSite'. The '/' character, hexadecimal value 0x2F, cannot be included in a name.
at System.Xml.XmlWellFormedWriter.CheckNCName(String ncname)
at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWriter.WriteElementString(String localName, String ns, String value)
at TFSChangeLog.Operations.Services.GenerateReleaseNotesService.GenerateRelaseNotes(MainWindowViewModel m_ViewModel)
ERROR : Exception is : System.InvalidOperationException: The Writer is closed or in error state.
at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)
at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWriter.WriteElementString(String localName, String ns, String value)
at TFSChangeLog.Operations.Services.GenerateReleaseNotesService.GenerateRelaseNotes(MainWindowViewModel m_ViewModel)
ERROR : Exception is : System.InvalidOperationException: The Writer is closed or in error state.
at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)

Dharmesh_Shah wrote May 30, 2013 at 3:47 PM

Hi,

I don't think this issue is related to Branch Path that you are using in your Configuration file. If your branch path was wrong then it should throw an error just immediately after processing all the branches in your project. See following example where I deliberately used a wrong Branch Path for generating report.
Quote
Generating Branch List from TFS ... Please Wait ... ... ...
ERROR : "$/TFS Demo/Development/tureA_Br" Branch is not found.
<<<< Unquote.

I think problem here is to do with some invalid XML characters getting in there while either saving your XML file or generating HTML file from newly created XML file via XSLT transformation. Based on your reported error, I'm assuming that one of your XML element name or XML element content has "Project/WebSite" value. Now XML is very sensitive to reserved characters like "/" and because it's getting in your XML output, it's just throwing this as error.

I suggest you to check if raw XML file is generated successfully. So each time when you run this application, it generates XML file containing all reportable data and saves it under your user profile at "C:\Users[USER_ID]\AppData\Local\TFSChangeLog". This XML file has "YYYYMMDD_HHmmss_TFSChangeLog.XML" naming convention. Check if this file is present for each run that you executed. If it does then it means that the problem is encountered when this XML file is transformed into HTML. In this case, you can open this file in notepad and look for "Project/WebSite" in it. I would also suggest for you to send this file to us by attaching it to this forum and we can have further look into it.

guzzam wrote May 31, 2013 at 3:27 PM

Thanks! You are right, it is not the "/" character that bothers. I found out that the command-line and the GUI versions act identically. It has to do with the range of changesets I select. The XML file is always generated but is corrupt in failure cases (meaning the file is not complete).
We have the SDL-template installed and probably its only the SDL-tasks that are not handled correctly? Attached an excerpt from the XML-file. The beginning of file is OK. The content is modified to protect co-workers but all XML tags are original and the XML-file ends exactly where this sample ends:
    <ChangeSet>
      <ID>414</ID>
      <Date>29.4.2013 11:37:59</Date>
      <Comment>Corrections made</Comment>
      <User>Company\User_A</User>
      <WorkItems>
        <WorkItem>
          <_Title>Title for this Work Item</_Title>
          <_State>Closed</_State>
          <_Rev>19</_Rev>
          <_ChangedBy>Mister X</_ChangedBy>
          <_Reason>Completed</_Reason>
          <_AssignedTo>Mister Y</_AssignedTo>
          <_WorkItemType>SDL Task</_WorkItemType>
          <_CreatedDate>10.12.2012 14:42:35</_CreatedDate>
          <_CreatedBy>Mister X</_CreatedBy>
          <_Description>Sample for TFSChangeLog

Modules included:
Lines of text
Lines of text
Lines of text
More lines of text
More lines of text
More lines of text
End even more...
End even more...
End even more...
End even more...
End even more...
End even more...
          <_History />
          <_RelatedLinkCount>15</_RelatedLinkCount>
          <_IterationPath>Test\2013\03</_IterationPath>
          <_IterationID>55</_IterationID>
          <_StateChangeDate>22.4.2013 17:27:09</_StateChangeDate>
          <_ActivatedDate>10.12.2012 14:42:35</_ActivatedDate>
          <_ActivatedBy>Mister X</_ActivatedBy>
          <_ClosedDate>22.4.2013 17:27:09</_ClosedDate>
          <_ClosedBy>Mister Y</_ClosedBy>
          <_StackRank />
          <_IntegrationBuild>BuildNumber_v01.00.20130430.1</_IntegrationBuild>
          <_Activity>Development</_Activity>
          <_RemainingWork>21</_RemainingWork>
          <_OriginalEstimate>21</_OriginalEstimate>
          <_CompletedWork>21</_CompletedWork>
          <_StartDate />
          <_FinishDate />
          <_ExternalLinkCount>4</_ExternalLinkCount>
          <_TeamProject>Test</_TeamProject>
          <_HyperlinkCount>0</_HyperlinkCount>
          <_AttachedFileCount>0</_AttachedFileCount>
          <_ExceptionJustification />
          <_ExceptionResolutionPlan />
          <_ExceptionResolutionTimeframe />
          <_TaskType>Requirement</_TaskType>
          

Dharmesh_Shah wrote Jun 11, 2013 at 9:22 AM

Hi,

So this problem must be due to one of the custom field that is introduced in your Process Template within "SDL Task" type of WorkItem. Can you please export your WorkItem definition and provide me with the XML file that it generates. I can then have a look at it and see if this can be fixed.

Best Regards,
TFSChangelog Team.

wrote Jun 12, 2013 at 8:01 AM

guzzam wrote Jun 12, 2013 at 8:01 AM

OK, thanks. Here it is attached, without the Global List definition.

Dharmesh_Shah wrote Jun 12, 2013 at 8:39 AM

Hi,

I think the issue here is to do with the fact that your field name is “Project/Web Site” which contains this “/” (slash) character. I would suggest that you rename your field from “Project/Web Site” to “Project OR Web Site” and import your SDL Task template back on the project. Like you exported it via witadmin tool, you can import it back using the same tool.

I also noticed that you have another field called “SDL-Agile Category”. I also suggest that you can rename your field to “SDL_Agile Category” (replacing dash with underscore) just in case if you still encounter problem.

I hope this fixes your issue.

Best Regards,
TFSChangeLog Team.

vjenkins wrote Dec 11, 2013 at 6:14 PM

I am having a similar issue in regards to it not generating a report. some changeset and changeset ranges will generate a report fine but others do nothing and if these changesets are included in the range of changesets no report will generate. is there anything I can look into in regards to the changesets that will not generate a report?
Thanks