BizTalk 2006 Documenter Available


I hadn't realized we released this publicly yet, but noticed this morning that the BizTalk Server 2006 Documenter is now
available for you to download. See Paul's blog
for the link.

I love this tool. To be able to generate a CHM file containing summaries of all your BizTalk artifacts (and relationships), plus business
rules, plus port configurations, plus orchestration image snapshots is freakin' great. Essential way to quickly document your
entire BizTalk application without writing a single line in a boring Word doc!

Technorati Tags:

Comments (9)
  1. http://weblogs.asp.net/scottgu/Only the second post in August!

    The world of work has been impinging…

  2. Kathy McKinney says:

    I have the 2006 Biztalk Documenter…It worked beautifully once, and now when I try to generate the documetation for my expanded Biztalk application, I consistently get an error "There was an error generating the XML document".  Is there any way to identify the offending component?  Thanks.

    Kathy

  3. Good question.  Do you get anything else in the Event Log?  Or is that all we’ve got to work with?

  4. Kathy McKinney says:

    Sorry it took so long to respond…but no, there are no entries in the event log at all.  I removed and then reinstalled the documenter, insured that I have all rights to the machine (I have a development biztalk server with Visual Studio, SQL Server 2005 and Biztalk 2006 installed on it  and log on as the biztalk administrator).  But still no go.  I am wondering if it is having difficulties scripting out a pipeline.  Or if I have an invalid XML character lurking in the application.

  5. Good point on some potentially tough to read artifact (like a pipeline).  I’d create a very simple app, and then just try documenting that.  See if we can isolate the culprit.

  6. mbenage says:

    I’m having the same problem (getting the "There was an error generating the XML document" error).  I turned on the logging for the documenter application and got the following detail:

    2006-11-07 01:24:28Z : VPC0602230237Administrator : TraceErr : Microsoft.Sdc.BiztalkDocumenter.Documenter.GenerateDocumentation: System.InvalidOperationException: There was an error generating the XML document. —> System.InvalidOperationException: Instance validation error: ‘255’ is not a valid value for Microsoft.Sdc.BizTalkOM.TrackingType.

      at System.Xml.Serialization.XmlCustomFormatter.FromEnum(Int64 val, String[] vals, Int64[] ids, String typeName)

      at System.Xml.Serialization.XmlSerializationWriter.FromEnum(Int64 value, String[] values, Int64[] ids, String typeName)

      at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write16_TrackingType(TrackingType v)

      at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write21_SendPort(String n, String ns, SendPort o, Boolean isNullable, Boolean needType)

      at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write37_BizTalkApplication(String n, String ns, BizTalkApplication o, Boolean isNullable, Boolean needType)

      at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write41_BizTalkBaseObject(String n, String ns, BizTalkBaseObject o, Boolean isNullable, Boolean needType)

      at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write42_BizTalkBaseObject(Object o)

      — End of inner exception stack trace —

      at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)

      at System.Xml.Serialization.XmlSerializer.Serialize(Stream stream, Object o)

      at Microsoft.Sdc.BizTalkOM.BizTalkBaseObject.GetXml()

      at Microsoft.Sdc.BiztalkDocumenter.Publishers.CompiledHelpPublisher.Publish(BizTalkInstallation bi, PublishType publishType, String resourceFolder, String publishFolder, String reportTitle, Boolean publishRules)

      at Microsoft.Sdc.BiztalkDocumenter.Documenter.GenerateDocumentation()

    You’ll notice the additional error message of: "System.InvalidOperationException: Instance validation error: ‘255’ is not a valid value for Microsoft.Sdc.BizTalkOM.TrackingType."

    This only happens on SOME of our BizTalk applications.  The only applications that the documenter doesn’t seem to work for are the applications where an orchestration calls a third-party WebService.  I’m not sure if that’s really the cause of the issue, but that’s the only major difference between the ones that do work and the ones that don’t.  I REALLY like the documenter application, I think it generates some VERY nice documentation, but I would like to get it working for all of our applications.  Please help!

  7. swedevx says:

    I got the same problem.. Any update in the near future..?

  8. Wow, the error looks tool-specific and from the error I can’t see exactly what is going wrong.  It doesn’t appear that the GotDotNet workspace is public, but Jason’s contact page is here: http://www.gotdotnet.com/Community/User/viewprofile.aspx?UserGuid=F04E101E-7010-44B0-A7F5-7A97EAA81381.

  9. dspading says:

    I’ve just installed and am getting basically the same error:

    TraceErr : Microsoft.Sdc.BiztalkDocumenter.Documenter.GenerateDocumentation: System.InvalidOperationException: There was an error generating the XML document. —> System.InvalidOperationException: Instance validation error: ‘204’ is not a valid value for Microsoft.Sdc.BizTalkOM.TrackingType.

    Has anyone who has experienced this error found the root cause?

    Thanks!

Comments are closed.

Skip to main content