Strange WSE error when trying to connect to web service

•

What is DaniWeb IT Discussion Community?

You're currently browsing the RSS, Web Services and SOAP section within the Web Development category of DaniWeb, a massive community of 423,139 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 4,214 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our RSS, Web Services and SOAP advertiser: Programming Forums

Thread Tools Display Modes

Views: 2977 | Replies: 5

Previous Post in Thread

Next Post in Thread

•

Join Date: Oct 2005

Posts: 27

Reputation: edmicman is an unknown quantity at this point

Rep Power: 3

Solved Threads: 0

edmicman

Offline

Light Poster

Strange WSE error when trying to connect to web service

Feb 5th, 2007

I'm working on an ASP.NET 2.0 app with WSE 3.0, that is trying to connect to a web service that was written with ASP.NET 1.1 and WSE 2. It's close, but when I try to actually retrieve data, I'm getting this error:

•

System.Web.Services.Protocols.SoapHeaderException: System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.Configuration.ConfigurationException: WSE535: The following SecurityToken QName is unsupported: http://schemas.xmlsoap.org/ws/2005/0...erivedKeyToken.

I'm not finding hardly anything when searching for any of the phrases in the error - WSE535, qname, anything. Any ideas or pointers? Any more info that I can give that would help? Thanks!