I was going through the hands on lab with WSE 3.0 security doc. I found out
that there were few important steps were missing. But I was able figure that
out with the help of the user group. Now I am facing a road block. When I
update my ref for the web service for my client. It suppose to add a proxy
class named SecureInvoiceServiceWse, but It doesn't and also it fails and I
get the following error int he event viewer. Any ideas/suggestion. Thanks a
lot.
Event Type: Error
Event Source: Microsoft WSE 3.0
Event Category: None
Event ID: 0
Date: 7/18/2006
Time: 11:13:13 AM
User: N/A
Computer: Z86277HLXP
Description:
An error occured processing an outgoing fault response.
Details of the error causing the processing failure:
System.InvalidOperationException: Send security filter on the server could
not retrieve the operation protection requirements from the operation state.
at
Microsoft.Web.Services3.Security.SecureConversationServiceSendSecurityFilter.SecureMessage(SoapEnvelope envelope, Security security)
at
Microsoft.Web.Services3.Security.SendSecurityFilter.ProcessMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope
envelope)
at
Microsoft.Web.Services3.WseProtocol.GetFilteredResponseEnvelope(SoapEnvelope
outputEnvelope)
The SOAP fault that was being processed follows:
<soap:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
<wsa:MessageID>urn:uuid:ef0a71f6-d0b9-4757-9481-5295d529d0d7</wsa:MessageID>
<wsa:RelatesTo>urn:uuid:a89ea038-8484-48f4-965e-dc7b88b31ac8</wsa:RelatesTo>
<wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode
xmlns:prefix0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d">prefix0:Security</faultcode>
<faultstring>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&
abortProcessing)</faultstring>
<faultactor>http://localhost/SecureInvoiceService/Basic/Part1/Before/SecureInvoiceService.asmx</faultactor>
</soap:Fault>
</soap:Body>
</soap:Envelope>
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
MHoque - 18 Jul 2006 18:41 GMT
After getting a reply from Chris , I went back and reinstalled my SDK, and
now I can see WSE 3.0 from IDE and after I used that to fix the
configuration, it fixed the SecureInvoiceClientWse proxy class problem.
> I was going through the hands on lab with WSE 3.0 security doc. I found out
> that there were few important steps were missing. But I was able figure that
[quoted text clipped - 69 lines]
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.