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

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

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
  1. Ram
    September 15, 2011 at 6:22 PM

    Thanks Sriram, this post helped me a lot.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: