Access denied attempting to launch a DCOM Server

[c.verma]

I have a web based (forms based authentication) asp.net application
that uses .NET remoting. It has web.config.remoting with all the
required settings in it. As soon as it tries to access the website, it
threw an error:
Access denied attempting to launch a DCOM Server. The server is:
{000C101C-0000-0000-C000-00000­0000046} The user is ASPNET/ServerName,

SID=S-1-5-21-1606980848-602162­358-1801674531-1007.


I tried to find the answer on the groups and the problem as Microsoft
site states is that DCOM server is failing to launch Machine Debug
Manager. They give the possible solution also on the following link:
http://support.microsoft.com/k­b/290398. BUT this solution DOESN'T
seem
to be working too!


To let the site work, I had to change the following in machine.config:
<processmodel username="machine">
TO
<processmodel username="system">
The web application works just fine.


HOWEVER, this solution exposes the server. Which means this is NOT the
right solution. At the same time, no where I have been able to find the

answer to my problem. And also why is the very idea of using
username="system" being used even though it is not safe??


Chanda.

 

[Bruce Barker]

your kb article tells you why.

the dcom server asp.net is accessing, can only be started by the system
account. you need to reconfigure your dcom server to be started by other
accounts (say the asp.net machine account).

-- bruce (sqlwork.com)



I have a web based (forms based authentication) asp.net application
that uses .NET remoting. It has web.config.remoting with all the
required settings in it. As soon as it tries to access the website, it
threw an error:
Access denied attempting to launch a DCOM Server. The server is:
{000C101C-0000-0000-C000-00000­0000046} The user is ASPNET/ServerName,

SID=S-1-5-21-1606980848-602162­358-1801674531-1007.


I tried to find the answer on the groups and the problem as Microsoft
site states is that DCOM server is failing to launch Machine Debug
Manager. They give the possible solution also on the following link:
http://support.microsoft.com/k­b/290398. BUT this solution DOESN'T
seem
to be working too!


To let the site work, I had to change the following in machine.config:
<processmodel username="machine">
TO
<processmodel username="system">
The web application works just fine.


HOWEVER, this solution exposes the server. Which means this is NOT the
right solution. At the same time, no where I have been able to find the

answer to my problem. And also why is the very idea of using
username="system" being used even though it is not safe??


Chanda.

 

[c.verma]

Thanks Bruce!
But my question remains same. If you change username="system", then you
are exposing your server. Which is not a good idea.
So why should we at all set this property when it is playing with the
security of the server?