Geek asks and answers

Custom Lync Client Fails at Startup

I am writing a custom lightweight I / O application (AKA Status, Presence application, etc.) using the Microsoft Lync 2010 API. It should start after starting / logging in, but I encountered a problem when logging in after starting / restarting cars. I get the following error from a methodLyncClient.GetClient

System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) in Microsoft.Office.Uc.IUCOfficeIntegration.GetInterface (String _version, OIInterface _interface) in Microsoft.Lync.Model.LyncClient.GetClient ()

My application is a ClickOnce application that runs from a network drive. It is available online only. The .application file is called from a batch file that runs from netlogon. It works fine if I run a batch file after the computer has been working for a while. It also works if I log out and then boot again. Therefore, I assume that a service is required that is not already running when the method is called LyncClient.GetClient.

+3
source share
1 answer

I would agree that this is the service you are expecting and would be dangerous for the Remote Procedure Call (RPC) service. This is a service that enables COM communications (for example, it processes COM activation requests, among other things).

, - , Windows COM.

, , Lync, .

+3

More articles:


All Articles