检索CLSID为{XXXX}的组件的COM类工厂失败,原因如下:80080005 [英] Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80080005

查看:2144
本文介绍了检索CLSID为{XXXX}的组件的COM类工厂失败,原因如下:80080005的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

检索CLSID为{XXXX}的组件的COM类工厂失败,由于以下错误:80080005.Net中的错误,故障排除过程是什么?澄清:我得到这在运行时,在我的XP机器上,客户端是.net代码在管理帐户下运行。 {XXXX}是指我们的一个内部COM组件。

What is the troubleshooting process for the "Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80080005" errors in .Net? To clarify: I am getting this at runtime, on my XP machine, with client being .net code running under admin account. {XXXX} refers to one of our in-house COM components.

从我的理解,0x80080005是指权限被拒绝,但我在哪里去检查/更改权限?或者我在这里完全错了,错误是来自组件本身,而不是从Windows COM子系统?

From what I understand, 0x80080005 refers to "permission denied", but where do I go to check/change the permissions? Or am I completely wrong here, and the error is coming from the component itself, and not out of Windows COM subsystem?

推荐答案

似乎是一个相当普通的错误,与启动COM服务器有关。可能的问题包括超时登录失败(检查问题 CO_E_SERVER_EXEC_FAILURE )或安全权限,或(显然) VS2008 ATL错误。在CreateInstance中碰到一个错误也会起到作用。我认为。

Seems to be a rather generic error relating to starting up the COM server. Possible issues include timeouts, logon failures (check the Q about CO_E_SERVER_EXEC_FAILURE), or security permissions, or (evidently) a VS2008 ATL bug. Hitting an error in CreateInstance would do the trick as well, I think.

我会先检查事件日志,找到有趣的东西。

I'd start by checking Event Log for anything interesting.

这篇关于检索CLSID为{XXXX}的组件的COM类工厂失败,原因如下:80080005的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆