Pat
Tue Jun 21 12:28:19 CDT 2005
This is an insidious error and is not trivial to troubleshoot, and means
that you have a COM object that has a threading problem (actually it is
usually a problem with an ISAPI filter or Extension that uses COM).
Basically the error maps to a COM HRESULT that means RPC_E_WRONG_THREAD. A
typical way to 'make' this happen is to have a CoInit call without a
corresponding CoUninit call. The reason it is intermittent is that the
problem actually corrupts at the thread level, so only the thread in
question will respond with the error. Over time, more and mroe threads are
affected so the problem appears to get worse until all the threads are
affected and things more or less stop working. One other way to do it is
with VB where references are passed as part of an array (which bypasses
apartment marshalling and is a very bad thing to do).
Check your ISAPI's (extensions & filters) and see if you can isolate any of
them. You should also try to isolate any COM objects that you are calling
from ASP that create their own threads or that you store in Application or
Session scope.
Pat
"Jane" <nospam@developmentnow.com> wrote in message
news:b891d035-5061-4160-b589-77fb6d3826c3@msnews.microsoft.com...
> Hi All
>
> Can anyone please tell me what this error means? Our website is
> experiencing difficulties serving up ASP pages (IIS5 and IE5). The pages
> are definitley there, and if you refresh they will often display. We've
> restarted the service several times but over the period of a few hours the
> web pages start to 'break' more regularly.
>
> The web pages use .asp code and xml. Any suggestions?
>
> From
http://www.developmentnow.com/g/59_2003_7_0_2_0/inetserver-iis.htm
>
> Posted via DevelopmentNow.com Groups
>
http://www.developmentnow.com