Identifying the version of a reference dll with which a dll was built.

May 28, 2011 2 comments

As a part of BizTalk development, we use many Common DLLs as references in our projects. One frequent issue we face is in knowing the reference DLL details(mainly the version) with which a DLL was built with.

Assume we have a map project “MapProj” which refers to a common DLL “SharedSchemas.dll” which is of version and also there are many versions of “SharedSchemas.dll” that coexists.

After deploying the”MapProj” to a server where it executes, you identify that the maps output was not as expected and you want to ensure if the maps project was built with the expected version of the referenced dll, of “SharedSchemas.dll” in our case. We can use ILDASM.exe, a built-in .NET framework tool which will identify the version details of a referenced assembly.

Step1 : Go to your VisualStudio Command Prompt and type “ILDASM.exe”.

c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>ildasm.exe

Step2 : Open the “MapProj.dll” for which we have to check the references.


Step 3: Double-click on “Manifest”.



The popup gives you the list of referenced assemblies and their versions.

View AssemblyDetails

View AssemblyDetails

Please provide your feedback and comments.

Failed to load “” type. Please verify the fully-qualified type name is valid.Details: “”.

March 25, 2011 1 comment


Failed to load “” type. Please verify the fully-qualified type name is valid.Details: “”.
The type must derive from System.Web.Services.Protocols.SoapHttpClientProtocol.
The type must have the attribute System.Web.Services.WebServiceBindingAttribute.


When a webreference is used in an orchestration, a logical port created for this webreference does not have a portype referred from webporttype.


When a webreference is used in an orchestration, a message passed to this webreference’s logical port is not a web messagetype.


 Configure the existing logical port(used to pass the webreference message) to have its porttype pointing to a webportytype as shown in the following image. Pick the exact webreference which you want to use in this port.


If this does not resolve the issue, check if the message passed to this logical port is of a webmessage type.

A message passed to a logical port that is of a WebPortType should be of type WebMessage.Select the message in an Orchestration View and make sure its messagetype is selected from “WebMessageTypes” as shown below.

Select WebMessageType

This should resolve the issue. Please post your questions or comments.

Cannot locate document specification because multiple schemas matched the message type

March 24, 2011 2 comments


Cannot locate document specification because multiple schemas matched the message type “RootName#Namespace”.


This happens when multiple schemas of the messagetype deployed.

MessageType is an important property that is used for evaluating subscriptions by BizTalk to identify where an incoming message has to be routed to.A MessageType(RootName#NameSpace) is a combination of a schema’s rootname and namespace.

If 2 schemas with the same MessageType(RootName#NameSpace) has been deployed, the XMLDisassembler will not understand which schematype the received message is of.So the exception “Cannot locate document specification because multiple schemas matched the message type “RootName#NameSpace” will be thrown.

Run the following Query against the BizTalkManagement Database. If it returns more than 1 row, then that should be the problem.

SELECT  msgtype
FROM bt_DocumentSpec
Where msgtype = ‘’

Note:Replace “” by “YourSchemasNameSpace#YourSchemasRootName”.


1.If you are using the same schema in different projects seperately, then

Move this schema to a common project and deploy it. Refer this common project in all other projects that you want this schema to be used in.This will resolve the issue.

2.If both the schemas are different and the namespace can be modified, then

Modify the namespace for any one of the schemas and deploy it.This will resolve the issue.

3.If both the schemas are different and the namespace cannot be changed, then

  • Create a custom receive pipeline and add an XmlDisassembler to it.
  • Set the “Document schemas” property of the XMLDisassembler by picking the schema(one among the 2 schemas with the same messagetype deployed) which you want to receive on this receive pipeline.
  • Use this receivepipeline on the receive location. This way we are forcing the XMLDisassembler to use the schema we have provided rather then it trying to match one in the DocumentSpec table.

Please post your comments or questions.


The POP3 adapter could not establish a connection with the POP3 server

March 23, 2011 Leave a comment

Exception :

The adapter “POP3” raised an error message. Details “The POP3 adapter could not establish a connection with the POP3 server. This could be due to the following reasons:
1) The POP3 server host and port information is incorrect.
2) The POP3 server is not running or is not reachable due to network issues.
URL: POP3://<server name>#<user name>
Error: No connection could be made because the target machine actively refused it “.

Cause :

This exception occurs when your firewall blocks the ports used by BizTalk Server to connect to the POP3 server.

Resolution :

There are certain ports that has to be opened on the firewall to allow BizTalk to communicate with the POP3 server.The list of ports to be opened on the firewall  for each adapter can be found at the following link:

Remember to mention the port number as 995 if a Secure connection is used.

To know more about other POP3 Adapter Configurations check

Please post any of your comments or questions.

InBound/OutBound Maps with same MessageType- Order of Execution

February 10, 2011 Leave a comment

Few days ago, there was a question in Biztalk forum which has triggered this post of mine.It was about the sequence in which BizTalk will execute the inbound maps configured in a receive port .

As we know, when two maps “Map A”  and “Map B”  that takes different input schema types  “Schema1” and “Schema2”  respectively will behave as follows.

When “Schema 1″ is received,” Map A” executes and for “Schema 2” it will be “Map B”.All is well till this.

What happens when multiple maps with the same schema type are input configured as inbound maps. Say the maps are taking the inputs as follows.

Schema 1           Map A               Schema 1
Schema 1           Map B               Schema 2
Schema 1           Map C               Schema 1

In this case, BizTalk will execute only one of the maps when an XML instance of “Schema 1” is received even though all the three Maps should have.But this is not the issue on focus..Things were well until this question raised. Which of the maps will execute?

Will they execute in the order they are configured in the port – NO.

Or in the order of their names- NO.  So how it works. Here are my findings on this.

I tested this scenario by configuring 3 maps A, B and C and all taking  the same “Schema 1” as their input. I added a C# script in all the maps to write the map’s name in the event log when it executes. This way we would know which map got executed.

This is how my port was configured.


Map Configuration in the Port

When Schema 1 was posted to the receive location, the event viewer log confirmed that “Map C” was executed.But,Why Map C?

After a few hours of search in the management database, I found that “admsvr_GetRecvPortTransformAssemblyName” is the SP responsible for selecting the map to execute.



Stored Procedure Code

  1. BizTalk picks the “MessageType” of the received msg(Promoted by XMLReceive pipeline ).It will be “http://MapTests.Schema1#Root&#8221; in our test scenario.
  2. Checks for this MessageType in “bt_DocSpec” table and picks the corresponding “docspec_name” column’s value.It will be “MapTests.Schema1” in our case.
  3. Picks the receive port’s GUID from “bts_receiveport” table.
  4. Inner Joins the results from points 2 and 3 and  gets the list of map IDs matching these conditions.

The result contains the GUIDs of  all maps that takes “http://MapTests.Schema1#Root&#8221; as input and configured for this receive port.

There were 3 GUIDs returned(one for each map A,B&C) when I executed the  first highlighted part of the SP with our test case inputs.

SELECT @nMapID = FROM bt_MapSpec ms

INNER JOIN bt_DocumentSpec ds ON ds.docspec_name = ms.indoc_docspec_name

INNER JOIN bts_receiveport_transform rpt ON rpt.uidTransformGUID =

INNER JOIN bts_receiveport rp ON rp.nID = rpt.nReceivePortID

WHERE ds.msgtype =http://MapTests.Schema1#Root&#8221;

AND rp.uidGUID = “4c160275-98c6-4f60-a0bf-9c9b5ccd958b”

AND rpt.bTransmit = “False”

The result was as follows.


MapIDs returned

Since “SELECT @nMapID =” in the query will always hold the last value of the result returned, @nMapID will be equal to ”68bfd6c1-eb61-40e4-9dec-a183a4f189fd” in our test scenario.

I customized the second part of our SP “admsvr_GetRecvPortTransformAssemblyName a little to take in all the GUIDs returned(for our understanding and analysis) that we just obtained as result.(Remember our @nMapID is actually having only ’68bfd6c1-eb61-40e4-9dec-a183a4f189fd”) .

SELECT ba.nvcFullName, bi.FullName FROM bts_assembly AS ba

INNER JOIN bt_MapSpec AS ms ON ba.nID = ms.assemblyid

INNER JOIN bts_item AS bi ON ms.itemid =

WHERE ( IN (‘6abc55b3-24b1-4c9a-9919-84e6ca81cf25’, ‘761be6b1-f7e8-4bc7-b855-8d99203df47c’, ’68bfd6c1-eb61-40e4-9dec-a183a4f189fd’))

The result of this query resolves half the mystery.

Query Results

Query Results

So, the MapName for the GUID that @nMapID holds will be “Map C” which will be the one that executes.


  • This order of the result IS NOT THE SAME  and changes if anything gets deployed. I tried deploying another set of maps that are not related to our sample project and our test scenario executed “Map A” instead of “Map C” this time but our query returned “Map A” as the final row.
  • BUT the last row of the result from the following query will be the map that executes. SELECT ms.idFROM bt_MapSpec ms INNER JOIN bt_DocumentSpec ds ON ds.docspec_name = ms.indoc_docspec_name INNER JOIN bts_receiveport_transform rpt ON rpt.uidTransformGUID =                                                                                         INNER JOIN bts_receiveport rp ON rp.nID = rpt.nReceivePortID                                                                                                                WHERE ds.msgtype = <MessageType> AND rp.uidGUID = <ReceivePortGUID> AND rpt.bTransmit = <PortTransmitType>
  • Maps that have multiple Inputs cannot be configured  EXACTLY as InBound maps. Eventhough they can be configured, the first input schema that was used while developing the map will be used as input.                                                                                              REASON: BizTalk runtime’s decision of the map to execute also depends on the “MessageType” property(as we saw in the SP).Thisgets proved at “WHERE ds.msgtype =” of the SP “admsvr_GetRecvPortTransformAssemblyName” . Here it takes only one messagetype and hence thus one input.
  • MessageType MUST be promoted to have the InBound Maps work. Passthru will not help.
  • These applies to the OutBound Maps as well.( the SP names and tables are different but follows the same naming conventions as the ones related to InBound maps).


Even though we can find how the map selection happens during execution, in an environment where multiple deployments happen, the order in which the SP returns the result will keep varying thus leaving the Map that will be executed unpredictable. So, Watch On!

Katradhu Kaialavu, Kalladhadhu Ulagalavu!(Means?)

February 8, 2011 1 comment

This is my first blog post ever.Excited and feeling responsible.

The tagline is a Tamil language quote meaning, “What you know is as big as the size of sand in your palm, what you do not know is as big as the size of the universe”(wikiquotes).

Trusting this, would appreciate any comment/advise/ideas on my posts which would help me in understanding BizTalk further.

Thanks And Here it goes….

Categories: Others