Archive

Posts Tagged ‘The type must derive from System.Web.Services.Protocols.SoapHttpClientProtocol.’

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