Turn detailed errors on in web.config on service side and run again. I have
no idea but maybe that gives a clue.
To exactly determine the issue also check the captures response message by
turning on trace.
> Hello there,
>
[quoted text clipped - 29 lines]
> methodname, SoapEnvelope envelope)
> at
Microsoft.Web.Services2.Security.SecurityTokenServiceClient.RequestSecurityT
> oken(SecurityTokenMessage request, String methodName)
> at
Microsoft.Web.Services2.Security.SecurityContextTokenServiceClient.RequestSe
> curityContextToken(SecurityToken baseToken, SecurityToken issuerToken,
> AppliesTo appliesTo)
> at
Microsoft.Web.Services2.Security.SecurityContextTokenServiceClient.IssueSecu
> rityContextTokenAuthenticated(SecurityToken baseToken, SecurityToken
> issuerToken)
> at SecureConvClient.SecureConvClient.Run() in c:\program files\microsoft
wse\v2.0\samples\cs\quickstart\secureconversation\code\secureconvcodeclient\
> secureconvclient.cs:line 91
> at SecureConvClient.SecureConvClient.Main(String[] args) in c:\program
> files\microsoft
wse\v2.0\samples\cs\quickstart\secureconversation\code\secureconvcodeclient\
> secureconvclient.cs:line 55