为什么是“本地启动”？默认情况下允许进程外服务器，但需要“本地激活”不是吗？
我当前需要创建一个 COM 对象，该对象由 ASP.NET 处理程序内部的进程外 COM 服务器提供服务。因此，每次部署 COM 服务器时，我都必须启动 DCOM Config 并更改安全设置。具体来说，我需要确保本地用户 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.
That doesn't make sense - why would I need such combination of permissions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我猜这是因为这就是你的默认设置。就我而言，这不正常，所以我不知道它是如何搞砸的。
您可以通过查看“COM 安全”选项卡下“我的电脑”的属性来设置 dcomcnfg 中的默认权限。我想您会在启动和激活权限的“编辑默认值”下找到 COM 服务器用户的默认权限，但没有检查本地激活。
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.
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.