Microsoft Developer Network > Forums Home > BizTalk Server Forums > BizTalk Server General > Typed Faults from Orchestrations published as WCF Services
Ask a questionAsk a question
 

AnswerTyped Faults from Orchestrations published as WCF Services

  • Wednesday, November 04, 2009 1:54 PMRaci Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi

    I want to throw typed faults from the orchestration which is published as wcf service. I followed the steps in the link http://blogs.msdn.com/paolos/archive/2009/05/22/how-to-throw-typed-fault-exceptions-from-orchestrations-published-as-wcf-services.aspx?CommentPosted=true#commentmessage.

    With wshttp binding, it works when the Security is set to None. When the Security is set to Message (with Windows) it throws the following error


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

    Inner exception:

    Digest verification failed for Reference '#_0'.

    On further analysis, a Custom Message Inspector is used. In the Custom Message Inspector, a custom "MessageFault" object is created (which is derived from MessageFault class).
    If we remove the creation of Custom Message Fault object, we do not get the above error(But we dont get the typed fault either).

    I tried searching for samples of classes derived from MessageFault. But did not find any.
    Do you know why creation of object derived from MessageFault can cause the above error?

    Is there any other way to throw typed faults from Orchestrations published as wcf service.

    Thanks and Regards
    Raci

Answers

All Replies