Re: WSE 3.0 errors in event log (may be MTOM related): The value may not be accessed in message stage 0.

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Mar 12, 3:56 am, "Zencat" <lawre...@xxxxxxxxxxxxxxxxxxx> wrote:
On Feb 22, 2:59 pm, Don Rixtown <real.email.addr...@xxxxxxxxxxxx>
wrote:

Hi,

We've noticed some strange errors on our production servers running WSE
3.0. From the stack trace it seems itmaybe MTOM related. The following
two errors occur at the same time:

1. System.InvalidOperationException: Thevaluemaynotbeaccessedinmessagestage0.
2.ServercannotclearheadersafterHTTPheadershavebeensent.

I'm guessing the first error is causing the secondmessage. Does anyone
haveany suggestions for trying to solve this?

I'll include the full event log details below.

Hey Don,

We are receiving the same errors on our production servers. We also
can't replicate the issue in our support and UAT environments. Did you
manage to fix it?

Thanks,
L

Hi L,

Did you ever get a response on how to fix this? We are running into
this same problem in a live production environment and have not been
able to reproduce it internally. It's very frustrating to keep telling
our customers to reset IIS when it happens.

Thanks,
Natalie

.

Relevant Pages

  • Error message translation
    ... Can anyone translate the following error into english for me and advise me ... on what I need to do in order to fix it? ... Please review the stack trace for more information ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Object reference not set to an instance of an object error
    ... Sadly the stack trace wasn't of any help. ... but when i try to debug, ... >> i try to recreate it with the same data, the program works fine, i'm out of ... >> ideas to fix the problem. ...
    (microsoft.public.dotnet.general)