Archive

Archive for March, 2011

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

March 25, 2011 1 comment

Exception:

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.

Cause:

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

(or)

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

Resolution:

 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.

WebPortType

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.

Advertisements

Cannot locate document specification because multiple schemas matched the message type

March 24, 2011 2 comments

Exception:

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

Cause:

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 = ‘http://schemas.microsoft.com/Sql/2008/05/GenericTableOp/#ExecuteScalar’

Note:Replace “http://schemas.microsoft.com/Sql/2008/05/GenericTableOp/#ExecuteScalar” by “YourSchemasNameSpace#YourSchemasRootName”.

Resolution:

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:  http://msdn.microsoft.com/en-us/library/dd802759(v=bts.10).aspx

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

To know more about other POP3 Adapter Configurations check

http://msdn.microsoft.com/en-us/library/aa559245(v=bts.70).aspx

Please post any of your comments or questions.