DCOM config for Isolated websites (was "IIS crash (IISAdmi..

The reason why I'm posting this in a new thread is because probably I got a
clue about which error could lead to IISAdmin to crash / hang.

As I replied to Pat, examining IIS Dump / IIS Crash Agent logs, we have 2
types of reports:

1) generating Process_Shut_Down_Exception, which (I guess) stops IISAdmin
and then other services. Please note that we don't issue any stop command to
IISAdmin, nor I know any software on our server which could do that.
IISAdmin, in my opinion, simply crashes. I wasn't able to figure it out why;

2) generating exception (first_chance) 800706d5 or 80070005 or both.

I did a little researching on those and they are related to security
permissions to access COM objects. I found a bulletin from MS explaining how
to setup DCOM permissions to let isolated websites to use COM components. I
did it (adding IUSR_machine, INTERACTIVE users to default security, launch
permissions lists and so on). It didn't solve the problem, but since we're
experiencing both exceptions quite often and since same websites were hosted
on another machine which used same confiuguration, except for the
high-isolated mode (was medium-pooled on old server), I'm starting to think
it might be a permission/security/access problem to common COM components.

I might solve this moving all websites back to medium-pooled mode (and I
will do that if I can't solve this quickly), but I'd like to have websites
running in isolated mode.

My question is: could that crash IIS / IISAdmin? If so, what are minimum
permissions / settings to allow websites to run in high-isolated mode and
access common components (and third-party objects)?

Thank you very much.

Guglielmo Mengora

Those are non-fatal exceptions, typically meaning that an error occurred
during the DCOM call at the remote object.

Pat

"Guglielmo Mengora" <mengora.TakeThisOut@netcore-online.com> wrote in message
news:eIxeYVhdDHA.2436@TK2MSFTNGP09.phx.gbl...
 > The reason why I'm posting this in a new thread is because probably I got
a
 > clue about which error could lead to IISAdmin to crash / hang.
 >
 > As I replied to Pat, examining IIS Dump / IIS Crash Agent logs, we have 2
 > types of reports:
 >
 > 1) generating Process_Shut_Down_Exception, which (I guess) stops IISAdmin
 > and then other services. Please note that we don't issue any stop command
to
 > IISAdmin, nor I know any software on our server which could do that.
 > IISAdmin, in my opinion, simply crashes. I wasn't able to figure it out
why;
 >
 > 2) generating exception (first_chance) 800706d5 or 80070005 or both.
 >
 > I did a little researching on those and they are related to security
 > permissions to access COM objects. I found a bulletin from MS explaining
how
 > to setup DCOM permissions to let isolated websites to use COM components.
I
 > did it (adding IUSR_machine, INTERACTIVE users to default security, launch
 > permissions lists and so on). It didn't solve the problem, but since we're
 > experiencing both exceptions quite often and since same websites were
hosted
 > on another machine which used same confiuguration, except for the
 > high-isolated mode (was medium-pooled on old server), I'm starting to
think
 > it might be a permission/security/access problem to common COM components.
 >
 > I might solve this moving all websites back to medium-pooled mode (and I
 > will do that if I can't solve this quickly), but I'd like to have websites
 > running in isolated mode.
 >
 > My question is: could that crash IIS / IISAdmin? If so, what are minimum
 > permissions / settings to allow websites to run in high-isolated mode and
 > access common components (and third-party objects)?
 >
 > Thank you very much.
 >
 > Guglielmo Mengora
 >
 ><!-- ~MESSAGE_AFTER~ -->