Acutally, when you lack symbols, because most COM objects will export only 4
functions, one of which is DllCanUnloadNow(), which is why you see it often.
But that's not why I selected it.
The reason was that when you see a lot of threads w/OLE32 (owns most of the
COM control interfaces) calling RPCRT4 (helps with marshalling) from an ASP
page (evidenced by VBScript also being on the stack) you have a strong
indication that cross apartment (or process) marshalling is going on. I
don't know that the VB object in question (it is VB b/c the call directly
above it is MSVBVM60) is a problem in and of itself, I just think that it is
related to the problem b/c it is inducing the marshalling.
So basically, the problem in this log is that a bunch of ASP pages called a
COM object which then, for reasons unknown, is trying to marshal a call to a
destination unknown.
Pat
"Scott Souza" <scotsouza.DeleteThis@hotmail.com> wrote in message
news:u7THYi$7DHA.2472@TK2MSFTNGP10.phx.gbl...
> Perhaps he just searched for DllCanUnloadNow and saw all the references to
> ebRICBT???????
>
>
> "Scott Souza" <scotsouza.DeleteThis@hotmail.com> wrote in message
> news:u$5klW$7DHA.1428@TK2MSFTNGP12.phx.gbl...
> > After looking at the entire output file how were you able to determine
it
> > was the ebRICBT.dll??
> >
> > Scott
> >
> >
> >
> > "Pat [MSFT]" <patfilot.DeleteThis@online.microsoft.com> wrote in message
> > news:OoUs8L$7DHA.1948@TK2MSFTNGP12.phx.gbl...
> > > ebRICBT.dll is trying to create an object in another
apartment/process,
> > but
> > > I can't tell where or what because the symbols were not downloaded,
but
> > that
> > > may give you a place to start.
> > >
> > > Suggestions:
> > > 1) Allow the machine that you are using to run IISState access to the
> > > internet while IISState is running. This will allow the symbols to be
> > > downloaded from microsoft.com. This will allow IISState to grab
better
> > > information and make analysis easier.
> > >
> > > 2) If possible, get the symbols for ebRICBT.dll and place them in the
> > > directory w/the dll. IISState will detect them and can tell us what
> > > class/function is trying to create the object and that may give us a
> clue
> > as
> > > well.
> > >
> > >
> > > Pat
> > >
> > >
> >
> >
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: iisstate analysis please 
FAQ
Profile
Private Messages
Log in
