How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services | Microsoft Share Point

Fri, 22 May 2009 20:07:57 GMT

PingBack from http://microsoft-sharepoint.simplynetdev.com/how-to-throw-typed-fault-exceptions-from-orchestrations-published-as-wcf-services/

How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services - Paolo Salvatori

DotNetShoutout — Sat, 23 May 2009 06:14:14 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

re: How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

Yogesh Mulye — Wed, 03 Jun 2009 07:18:18 GMT

Excellent article and enough details there. Just what I had in my mind.

Thank you.

re: How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

Vinoth — Thu, 20 Aug 2009 16:50:00 GMT

Your sample code works fine with basicHttpBinding. But getting below error if I use the wsHttpBinding.Please advise

The signature verification failed. Please see inner exception for fault details.

Inner exception:

Digest verification failed for Reference '#_0'.

re: How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

Paolo — Fri, 21 Aug 2009 07:38:23 GMT

Hi Vinoth,

could you please send me a repro of your test to better scope the problem? My demo works fine and it makes use of a WCF-CustomIsolated Receive Location to expose the orchestration as a WCF service and this Receive Location is configured to use the WsHttpBinding binding.

re: How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

efung — Thu, 19 Nov 2009 08:00:01 GMT

Hi,

I have tried to deployed the solution for testing, but I get the following error when I called SayHello using the driver.

"The message could not be processed. This is most likely because the action 'SayHello' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding."

I think I have missing something on configuration. Do you have any idea on that?

Thanks,

Efung

re: How to Throw Typed Fault Exceptions from Orchestrations Published as WCF Services

leprino — Thu, 19 Nov 2009 08:36:40 GMT

Hi Efung,

I doubt that the problem is due to the Action, as the operation exposed by the WCF Receive Location accepts any Action as shown in te code snippet below (Action="*"):

[OperationContract(AsyncPattern = true, IsOneWay = false, Action = "*", ReplyAction = "*")]

IAsyncResult BeginTwoWayMethod(Message message, AsyncCallback callback, object state);

The next check is to verify that the binding used on the client side and server side (WCF Receive Location). Since you downloaded my code (that works fine on my machine, and several other people were able to successfully install and use the demo) I'm inclined to think that bindings are ok.

So the next question is: are you hosting the WCF Receive Location within IIS 6.0 or 7.0? What kind of Application Pool (Integrated/Classic) are you using to host the WCF Receive Location? What kind of security did you set on the web application hosting the WCF Receive Location? Take into account that since the WCF Receive Location is using the wsHttpBinding with no security (no authentication), you have to enable Anonymous Authentication on the web application hosting the WCF Receive Location.

Ciao,

Paolo