Hi Brandon,
Could you please describe your scenario in a little more detail? For
example, what version of WSE2.0 are you using? SP1, SP2 or SP3?
Does your message just contain a username token or is the message signed
with that username token? Is it a plain text password? if it is, then
whenever WSE
(at the service side) receives a request with a username token with plain
text password, it does a LogonUser with those credentials. If this is the
case then perhaps
the user does not exist on the Win2K box.
Have you tried turning on detailed errors on the server's web.config to
see if you get a better exception?
Thanks,
Sidd [MSFT]
[quoted text, click to view] "Brandon" <Brandon@discussions.microsoft.com> wrote in message
news:A1992652-0378-4C1F-AD3E-F2CF9FE5F620@microsoft.com...
> Tim,
>
> Have you solved this problem yet? I am having a similar problem and I
> cannot seem to find any type of documentation regarding this problem. At
> this point, I am narrowing my search to a timeout issue. I will attempt
> to
> fix and let you know if this worked out. If you had another workaround,
> would appreciate it. Thanks.
>
> Brandon
>
> "Tim Heuer" wrote:
>
>> Hi. I've got a program that uses wse 2.0 to consume a web service (that
>> I
>> wrote). It exchanges an username token.
>> If I run the program on Windows XP, it works beautifully. If I run on
>> Windows 2000 server I get the error:
>>
>> an error was discovered processing the <security> header.
>>
>>
>> same code, same everything but the operating system. Any ideas would be
>> GREATLY appreciated.
>>
>> --
>> Tim Heuer
>> heuert at Comcast dot net