dotnet web services enhancements: I have a problem running 2 webservices next to each other.

The first web service runs the technology preview version of WSE2.0
The second web service runs the WSE2.0 sp1.

Both WebServices authenticate SOAP-calls using a custom UsernameTokenManager

Somehow after a while all SOAP-calls that have to go to the second Webservice will bounce. I then get the following error message:

"WSE542: The UsernameToken security token does not have sufficient information to generate a key to sign messages with."

When I then go in the ISS 6.0 management tool and I recycle the DefaultAppPool where both WebServices run under, the problem dissapears, but after a while it will pop up again.

I can not find any documentation on how this error occurs. Any help on this one?



--------------------------------
From: Robbert van Geldrop

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

Hi Robbert,

Does this error happen right away or does it take some time? I.e. is it
dependent on the number of requests you send, or not. Secondly, I would like
to understand your scenario a little more. You are having these 2 web
services in (I presume) 2 separate virtual directories?

Are these two web services being hit by the same client? What are the
sequence of operations? If you let me know the clients interact with the
same web services, that would be great. For example,
- client 1 sends signed message with username token to WSE TP
- client 1 sends signed message with username token to WSE 2.0 SP1

What version of WSE are the clients built with (assuming that there are
more than 1). Is there ever a situation when a client built with WSE 2.0 TP
is hitting a webservice with WSE 2.0 SP1?

I would love to investigate, however, I would need a little more detail
from you to understand your scenario a bit more.

Thanks,

Sidd [MSFT]

"Robbert van Geldrop via .NET 247" <anonymous@dotnet247.com> wrote in
message news:eAVAhGXAFHA.4044@TK2MSFTNGP11.phx.gbl...
[quoted text, click to view]
DefaultAppPool where both WebServices run under, the problem dissapears, but
after a while it will pop up again.
[quoted text, click to view]