自定义 Lync 客户端启动失败
我正在使用 Microsoft Lync 2010 API 编写自定义轻量级输入/输出板（又名状态、状态等）应用程序。它需要在启动/登录后运行，但在启动/重新启动机器后登录时我遇到了问题。我从 LyncClient.GetClient 方法收到以下错误
System.Runtime.InteropServices.COMException (0x800706BE)：远程过程调用失败。 （HRESULT 异常：0x800706BE） 在 Microsoft.Office.Uc.IUCOfficeIntegration.GetInterface(String _version, OIInterface _interface) 在 Microsoft.Lync.Model.LyncClient.GetClient()
我的应用程序是从网络驱动器运行的 ClickOnce 应用程序。它仅在在线模式下可用。 .application 文件是从 netlogon 运行的批处理文件中调用的。如果我在计算机运行一段时间后运行批处理文件，效果很好。如果我注销然后重新登录，它也可以工作。因此，我假设调用 LyncClient.GetClient 方法时需要一项尚未启动的服务。
I'm writing a custom light-weight in/out board (AKA Status, Presence, etc.) application using the Microsoft Lync 2010 API. It needs to run after startup/login but I've ran into a problem when I login after I start/restart the machine. I get the following error from the LyncClient.GetClient method
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed.
(Exception from HRESULT: 0x800706BE)
at Microsoft.Office.Uc.IUCOfficeIntegration.GetInterface(String _version, OIInterface _interface)
at Microsoft.Lync.Model.LyncClient.GetClient()
My application is a ClickOnce application that runs from a network drive. It's available only in Online mode. The .application file is called from a batch file that is run from netlogon. It works fine if I run the batch file after my computer has been running for a while. It also works if I log out and then log back in. Therefore I'm assuming that there is a service required that has not yet started when the LyncClient.GetClient method is called.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我同意这是您正在等待的服务，并且会冒险猜测“远程过程调用（RPC）”服务。这是启用 COM 通信的服务（即，它处理 COM 激活请求等）。
测试这一点很尴尬，因为服务控制管理器不允许您关闭该服务 - 它是一项关键服务，因为大量 Windows 都依赖 COM。
为了进行测试，您可以在代码中检查该服务的启动状态，然后仅在该服务启动时初始化 Lync。
I would agree that it's a service that you're waiting for, and would hazard a guess at the "Remote Procedure Call (RPC)" service. This is the service that enables COM communication (i.e. it handles COM activation requests, among other things).
It's awkward to test this, as Service Control Manager doesn't let you shut the service down - it's a critical service as large swathes of Windows rely on COM.
To test, you could check the startup status of the service in code, and then only initialise Lync when that service is started.