The message with Action '' cannot be processed at the receiver,

Question

I have WSDl provided by the Client based on which i need to create a WCF service

it is does not provide any soap action as its under soap 1.2 which i tried to implement in WCF using following config

when i try to submit and app using soap UI i get the error below

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
   <s:Body>
      <s:Fault>
         <s:Code>
            <s:Value>s:Sender</s:Value>
            <s:Subcode>
               <s:Value xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</s:Value>
            </s:Subcode>
         </s:Code>
         <s:Reason>
            <s:Text xml:lang="en-US">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</s:Text>
         </s:Reason>
         <s:Detail>
            <z:anyType i:nil="true" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/>
         </s:Detail>
      </s:Fault>
   </s:Body>
</s:Envelope>

<services>
  <service name="Myservice" behaviorConfiguration="MyServiceTypeBehaviors">
    <endpoint name="MyserviceEndpoint" address="soap12" 
              binding="customBinding" bindingNamespace="http://Myservice.namespace"
              bindingConfiguration="httpSoap12" contract="IMyService"/>

  </service>
</services>
<behaviors>
  <serviceBehaviors>
    <behavior name="MyServiceTypeBehaviors" >
      <serviceMetadata httpGetEnabled="true" />
    </behavior>
  </serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

Answer 1

There are various interpretations whether what to do if soapAction is not specified (e.g. there might be a default soapaction). I suggest to set up wcf client and server and see what soapAction the client sends. This is the soapAction all clients should send.