See <limits> in doc. By default there's a limit on number of tokens in a
message. To override this change config. Example from doc:
<microsoft.web.services2>
<security>
<limits
maxSignedItems="10"
maxEncryptedItems="4"
maxTokens="2" />
</security>
</microsoft.web.services2>
> Anyone know whats causing this, and how to fix it?
>
[quoted text clipped - 10 lines]
> stack trace --- at
> Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element) at
Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnve
lope
> envelope) at
> Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
> envelope) at
Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer
verMessage
> message)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
schneider - 26 Jul 2004 23:42 GMT
> See <limits> in doc. By default there's a limit on number of tokens in a
> message. To override this change config. Example from doc:
[quoted text clipped - 37 lines]
>>current web request. Please review the stack trace for more information
>>about the error and where it originated in the code.
Ok, I can set this to -1 and it's ignored.
But if this does happen I must restart IIS, what good is that? Shouldn't
it just ignore the IP request?
I tried to acess the site from another machine and the site would Not
work....
Also the docs speak as if you set how many tokens can bi in the message,
yet I only have one. I am however loging in with the same user/pass
several time quickly while I develope.
Any clarification would help.....
Schneider
Lucien - 27 Jul 2004 18:02 GMT
Is the exception on the server side? You don't need to recycle IIS when you
change web.config. But I didn't quite get the 'restart' issue that happens
(after the exception?).
Also are you sure you only have 1 security token? Can you capture the
message and look at the number of tokens you have?
Last by default detailedErrors is turned off for security reasons. So you
may not get a nice detailed error by default for obvious reasons.
> > See <limits> in doc. By default there's a limit on number of tokens in a
> > message. To override this change config. Example from doc:
[quoted text clipped - 22 lines]
> >>stack trace --- at
> >>Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element) at
Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnve
> > lope
> >
> >>envelope) at
> >>Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
> >>envelope) at
Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer
> > verMessage
> >
[quoted text clipped - 18 lines]
>
> Schneider