为什么是“本地启动”允许默认情况下的out-proc服务器，但是“本地激活”不是？ [英] Why is "local launch" allowed for out-proc servers by default but "local activation" is not?

问题描述

我目前需要创建一个COM对象，该对象由ASP.NET处理程序内部的外部COM服务器提供。因此，每次我部署COM服务器，我必须启动DCOM配置和更改安全设置。具体来说，我需要确保本地用户ASPNET允许本地启动和本地激活。

I currently need to create a COM object that is served by an out-proc COM server from inside an ASP.NET handler. So every time I deploy the COM server I have to fire up DCOM Config and change the security settings. Specifically I need to ensure that both "local launch" and "local activation" is allowed fro the local user ASPNET.

令我惊讶的是，当我打开相关设置页面本地启动已经被允许，但本地激活是不允许的。

What surprises me is that when I open the relevant settings page "local launch" is already allowed but "local activation" is not allowed.

这没有意义 - 为什么我需要这样的权限组合？ p>

That doesn't make sense - why would I need such combination of permissions?

推荐答案

我会猜测，因为这是你的默认设置。

I'm going to guess it's because that's what your default is set to. It's not normal as far as I'm concerned so I don't know how it got messed up.

您可以通过查看dcomcnfg的属性来设置dcomcnfg中的默认权限COM安全选项卡下的我的计算机。我想你会发现你的COM服务器的用户的默认权限下的编辑默认值启动和激活权限没有本地激活检查。

You can set the default permissions in dcomcnfg by looking at the properties of "my computer" under the COM Security tab. I think you'll find your COM server's user's default permissions under "Edit Defaults" for Launch and Activation Permissions doesn't have local activation checked.

这篇关于为什么是“本地启动”允许默认情况下的out-proc服务器，但是“本地激活”不是？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！