Thanks Byron!  When I set <detailedErrors enabled="true" />, I get more
useful error message and it turns out a bug of this WSE 2.0 which can not be
used when the server machine time is faster than my client machine. It cause
a "System.Exception: Creation time in the timestamp can not be in the
future".

So I have to adjust my server machine time to be a little be late, say 5
minutes than normal. Is there any other way to figure out this problem?
Thanks!

Jim, Y

Set detailed error at your server side configuration

<microsoft.web.services2>
   <diagnostics>
     <detailedErrors enabled="true" />
   </diagnostics>
 </microsoft.web.services2>

and try to get full detailed error would be easier to troubleshoot.

thanks
Byron KIM

I use WSE2.0 with a custom UsernameTokenManager (inherited from the default)
for webservice authentication. The username and password are retrieved from
a database in my overrided AuthenticateToken function as shown in Handon Lab
A (PasswordOption is SendHashed). My project is running perfect on my local
machine where I referenced my webservice on localhost. But the error is
occurred whenever I move my webservice to my remote web server which is also
running the WSE2.0. The error is "
Exception Type: System.Web.Services.Protocols.SoapHeaderException
Code:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d:InvalidSecurity
Detail: NULL
Message: An error was discovered processing the <Security> header
TargetSite: System.Object[]
ReadResponse(System.Web.Services.Protocols.SoapClientMessage,
System.Net.WebResponse, System.IO.Stream, Boolean)
HelpLink: NULL
Source: System.Web.Services"
Somebody know what is the problem of that? and How to figure it?

Thanks!