I have written a WSE 3.0 web service that uses certificate authentication and I am able to call it via another .NET client. However, when the Axis2 client tries to call the service I am getting the following error.

System.ApplicationException:
WSE841: An error occured processing an outgoing fault response.
---> System.Web.Services.Protocols.SoapHeaderException:
Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient
is required but not present in the message.

I can view the trace files and see the wsa:Action is coming across but the soap xml namespace is different then the one the .NET web service is looking for.

<soapenv:Envelope xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlnsoapenv="http://schemas.xmlsoap.org/soap/envelope/">

When I take the same SOAP request and update the xmlns:wsa="http://www.w3.org/2005/08/addressing" to

xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" the error goes away. Is there any way to update the .NET web service to allow the w3.org namespace for the Action or is there anyway to update the .NET web service to make the Action, MessageID, ReployTo, and To Soap Header properties not required?

Thanks,
Katie

Hi Katie -

I am having the same problem. Did you finda solution to this problem.

I am getting following error. I am using WSE 3.0/VS 2005/X509.

<faultstring>System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.ApplicationException: WSE841: An error occured processing an outgoing fault response. ---> System.Web.Services.Protocols.SoapHeaderException: Microsoft.Web.Services3.Security.SecurityFault: Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.

at Microsoft.Web.Services3.Design.RequireSoapHeaderAssertion.RequireSoapHeaderFilter.ProcessMessage(SoapEnvelope envelope)

at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)

at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope requestEnvelope)

at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage message)

at System.Web.Services.Protocols.SoapServerProtocol.Initialize()

at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean&amp; abortProcessing)

remove <requireActionHeader> Element from policy file of Server. This will make Action header to be optional at server end.
This <requireActionHeader> Element is used twice in the policy file , under <extensions> and <policy name="ServerPolicy"> , you will be required to remove it from both places. This solved by problem.

Amit Joshi

Please help,

We are still getting this message after removing that from out Policy File.

processingStep description="Entering SOAP filter Microsoft.Web.Services3.Design.RequireSoapHeaderAssertion+RequireSoapHeaderFilter" />

---

Z