clickonce winform在Windows Udates之后不从开始菜单打开,一台/多台计算机重新启动后再次工作
自从一段时间以来,我开发的VB.NET应用程序通常在Windows 10更新之后为某些用户开发了停止工作。它在一次或多次重新启动计算机后再次开始工作,有时需要几天才能开始。
当用户试图重新安装它时,它是安装的,但抛出以下错误:
通过以下错误检索CLSID {X}组件的COM类工厂失败:80080005服务器执行失败(Hresult:0x80080005(co_e_e_e_server_exec_failure))。
我假设这与项目中的Outlook Interop参考有关。
关闭Outlook并作为管理员运行此应用程序时,我可以启动它,当Outlook打开时,我将无法做到。
当Outlook和应用程序都使用Admin PrivilegesIt打开时,正常工作。
我知道Outlook和应用程序应该以相同的安全级别运行,但是我并没有像Admin一样跑步,所以我很困惑为什么需要将应用程序运行为Admin。
目标CPU设置为“任何CPU”,我是否应该尝试将其更改为“ x86”?
Office版本是Office365 Pro
Since some time the vb.net application I developed stops working for some users, usually after windows 10 updates. It starts working again after restarting computer one or more times, sometimes it takes few days for it to start.
When user tries to reinstall it, it is installed but throws following error:
Retrieving the COM class factory for component with CLSID {X} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)).
I'm assuming that it has something to do with a Outlook Interop reference in the project.
When outlook is closed and I run this application as admin I am able to start it, when outlook is open I am not able to do it.
When both outlook and the application are open with admin privilegesit works correctly.
I understand that Outlook and the application should run with the same security level, but I'm not running outlook as admin so I'm confused why I need to run the app as admin.
The target CPU is set to 'Any CPU', should I maybe try changing it to 'X86'?
Office version is Office365 Pro
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您需要在相同的安全环境下运行两个应用程序。如果两者都是在同一用户下运行的 - 一切都应该正常工作。
但是,以下错误可能表明Office应用程序是从服务中自动化的:
服务器端自动化的注意事项文章在此类错误中指出以下内容:
You need to run both applications under the same security context. If both are run under the same user - everything should work correctly.
However, the following error may indicate that Office applications are automated from a service:
The Considerations for server-side Automation of Office article states the following for such errors: