BizTalkDocumenter Work Item Rss Feed

Created Issue: Item has already been added. Key in dictionary: '...' Key being added: '...'

willbrown — Thu, 04 Jun 2009 23:32:17 GMT

i am seeing this when 2 artifacts have the same name (in my particular situation pipelines) despite the fact that they reside in 2 different BizTalk assemblies... i can't seem to find any sort of dictionary object in the source code where i can modify the determination of unique keys...

any pointers (or a fixed version :) ) would be much appreciated
-Will

Commented Issue: When specific applications are selected for documenting in the UI, only the first one is included in the resulting CHM file

ajade101 — Tue, 31 Mar 2009 14:33:14 GMT

If you select multiple applications to document in the UI, only one (the first one) will be documented.
Comments: ** Comment from web user: ajade101 **

It is not working. Produce output just for default.

Commented Issue: Error when port tracking is enabled

dmierlo — Thu, 09 Oct 2008 08:35:40 GMT

The documenter throws an error whenever it encounters a port with tracking enabled.
Comments: ** Comment from web user: dmierlo **

The work-around to disable all tracking works.

Thnx,

Dennis

Created Issue: "Group not configured" error when generating against remote biztalk server

Chandalar — Fri, 01 Aug 2008 20:59:56 GMT

I get the following error when trying to generate documentation against a remote BizTalk server. The tool works fine when run from the remote server directly.

Microsoft.Services.Tools.BizTalkDocumenter.Core.Documenter.GenerateDocumentation: System.Runtime.InteropServices.COMException (0xC0C024BF): The server has not been configured.
To configure the server, run the BizTalk Server Configuration wizard and configure the Group feature.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Microsoft.Services.Tools.BizTalkOM.Host.GetInstance(String className)
at Microsoft.Services.Tools.BizTalkOM.Host.Load(BtsCatalogExplorer explorer, Host host)
at Microsoft.Services.Tools.BizTalkOM.BizTalkInstallation.DocumentHosts()
at Microsoft.Services.Tools.BizTalkOM.BizTalkInstallation.LoadConfigInternal(LoadOption loadOption)
at Microsoft.Services.Tools.BizTalkOM.BizTalkInstallation.LoadConfig()
at Microsoft.Services.Tools.BizTalkDocumenter.Core.Documenter.GenerateDocumentation()

Any ideas?

COMMENTED ISSUE: Dictionary key problem

ricardotorre — Fri, 30 May 2008 07:01:32 GMT

I think it's the RoleLinks...

---------------------------
Error Generating Documentation
---------------------------
Item has already been added. Key in dictionary: 'Provider' Key being added: 'Provider'
---------------------------
OK
---------------------------
Comments: ** Comment from web user: ricardotorre **

i got this error when there was 2 version numbers of the same orchestration deployed

COMMENTED ISSUE: Only 10 variables are documented for an orchestration

yap — Thu, 15 May 2008 08:39:57 GMT

The documentation ends after 10 variables.
Comments: ** Comment from web user: yap **

Sorry it's not the number but the fact is, that the documentation of the variables suddenly stops and not all variables are documened. Unfortunately the source code is not up to date and does not match the lates relase version.

CREATED ISSUE: Only 10 variables are documented for an orchestration

yap — Thu, 15 May 2008 07:19:57 GMT

The documentation ends after 10 variables.

CREATED ISSUE: Error "Could not contact the SSO server 'xxx'"

Chandalar — Thu, 24 Apr 2008 22:18:26 GMT

When trying to run BizTalk documenter remotely against the BizTalk server, I get the above error. The server name in quotes is the name of the workstation I am running the BizTalk documenter on, not the management server name I entered into the UI.

The tool runs fine when used directly from the BizTalk server.

COMMENTED ISSUE: Running App against Remote Biztalk Server

scox_nz — Tue, 12 Feb 2008 09:40:20 GMT

When I run the Documenter application against a configuration on a remote Biztalk Server, I get an object reference not set to an instance of an object error. When I run it on my development server, it runs fine.
Comments: ** Comment from web user: scox_nz **

Note this is a bug with Microsoft.Services.Tools.BizTalkOM (previously Microsoft..SDC.BizTalkOM) - delivered from the Codeplex BiztalkOM project.

COMMENTED ISSUE: Running App against Remote Biztalk Server

scox_nz — Tue, 12 Feb 2008 09:35:04 GMT

I have reproduced it using the latet version of BizTalkOM. The issue is in Host.GetInstance - this function returns null if it doesn't find the Host Instance Name ON THE LOCAL MACHINE. So you have to have at least the same hosts set up on your dev box as your remote box - other wise you get null from this function, then Host.Load will throw the object reference exception on
int hostType = Convert.ToInt32(wmiHost.Properties["HostType"].Value.ToString());
as wmiHost is null from the earlier call to this.GetInstance returned nul...

COMMENTED ISSUE: Dictionary key problem

crestall — Fri, 21 Dec 2007 20:24:05 GMT

I got the same problem. For me it was in Parties.... I have a Custom name for a unique qualifier/value pair that I use on multiple parties. I changed the name, which as far as I can tell is not used anyway, to get it to work

CREATED ISSUE: Multiserver Issue?

neemic — Fri, 21 Dec 2007 14:47:10 GMT

Hi all,
Anybody out there know running the documenter successfully in a multi-server Biztalk 2006 environment?
I have tried it remotely from my desktop, local on the Biztalk server and local on the SQL Server machine. All without success.

No problems running it on a single server hosting Biztalk and SQL together...

COMMENTED ISSUE: Error Generating XML Documents

eliasen — Tue, 18 Dec 2007 13:48:15 GMT

Running the tool on R2 RTM
during documentation creation, a dialog box appears saying "There was an error generating XML Documents"
Comments: ** Comment from web user: eliasen **

I had the same error. The solution ended up being the solution someone else has described in the issue "Error when port tracking is enabled" - so try that?

COMMENTED ISSUE: Error when port tracking is enabled

michaelstephenso — Mon, 19 Nov 2007 13:15:43 GMT

The documenter throws an error whenever it encounters a port with tracking enabled.
Comments: ** Comment from web user: michaelstephenso **

I had the same issue, i was able to resolve this by downloading the source code and building the code. The defect is caused because the TrackingType class does not have the full and correct list of Enum elements to be able to serialize correctly. The current list is:

AfterReceivePipeline = 2,
AfterSendPipeline = 8,
BeforeReceivePipeline = 1,
BeforeSendPipeline = 4,
TrackPropertiesForIncomingMessages = 0x10,
TrackPropertiesForOutgoingMessages = 0x20,

I used reflector on the Microsoft.BizTalk.ExplorerOM assembly as this tracking types should be the same as the equivelent class there. If you replace the above elements with the following it seems to work fine.

AfterReceivePipeline = 2,
AfterSendPipeline = 8,
BeforeReceivePipeline = 1,
BeforeSendPipeline = 4,
TrackPropertiesAfterReceivePipeline = 0x20,
TrackPropertiesAfterSendPipeline = 0x80,
TrackPropertiesBeforeReceivePipeline = 0x10,
TrackPropertiesBeforeSendPipeline = 0x40

Hope this helps

Mike

COMMENTED ISSUE: Error Generating XML Documents

renea — Thu, 11 Oct 2007 17:04:36 GMT

Running the tool on R2 RTM
during documentation creation, a dialog box appears saying "There was an error generating XML Documents"
Comments: ** Comment from web user: renea **

We ain´t got any \ in port names, but I also get this error with BTS 2006 R1

COMMENTED ISSUE: Applications that reference other applications cannot be documented

mbrimble — Sun, 16 Sep 2007 23:35:47 GMT

Found with change set 3441 and 4081.( except with 4081 you can select multiple applications in "specific documentation type" option).

The error is ;
---------------------------

System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: Instance validation error: '192' 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.Write4_TrackingType(TrackingType v)

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

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

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

at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterBizTalkBaseObject.Write45_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()

at Microsoft.Sdc.BiztalkDocumenter.Form1.GenerateDocumentation()
---------------------------
Comments: ** Comment from web user: mbrimble **

The structure of the applications can be seen in the attached chm. If you look at the shared invoice application, you can see it back references PMK.APS. This application cannot be documented.

CREATED ISSUE: Applications that reference other applications cannot be documented

mbrimble — Sun, 16 Sep 2007 23:23:05 GMT

CREATED ISSUE: Running App against Remote Biztalk Server

TMcCarthy — Wed, 12 Sep 2007 19:58:04 GMT

CREATED ISSUE: Dictionary key problem

obiwanjacobi — Mon, 20 Aug 2007 11:06:45 GMT

CREATED ISSUE: SQL Connection Error on remote server

plditallo — Wed, 15 Aug 2007 18:54:28 GMT

Hi,

I can run this utility on my laptop instance without any heartburn, but connecting over to another server is a different story. When I type in:

Microsoft.Sdc.BiztalkDocumenter.exe /s:BZTALKSrvr\BIZTALKInst\ /r:schema /p:chm /o:C:\Docs\BTS

I get the error message:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 -Error Locating Server/Instance Specified)

I created an ODBC connection using the same server and instance. I was able to connect remotely without any glitches. I then tried using the odbc reference in the GUI with the same error.

Any advice?

Thanks,
Paula