RequestSoapContext.Current null at WS

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Keith - 30 Sep 2005 16:40 GMT

I have a WSE2 WS receiving X509-signed messages. I can't read the
RequestSoapContext.Current to get the cert token--the object is null. It
worked fine on my dev box. Now on a test server, it breaks whether I'm
coming from a different box or through localhost on the server box. Is this
a configuration issue?

Reply to this Message

Keith - 30 Sep 2005 18:00 GMT

For the benefit of those out there having the same problem:

I found the solution. It was simple enough: check the version number of
your Microsoft.Web.Services2.dll assembly, and make sure it matches the
Web.config of your WS, and the app.config of your client.

> I have a WSE2 WS receiving X509-signed messages. I can't read the
> RequestSoapContext.Current to get the cert token--the object is null. It
> worked fine on my dev box. Now on a test server, it breaks whether I'm
> coming from a different box or through localhost on the server box. Is this
> a configuration issue?

Reply to this Message

Rate this thread:

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...