c# - Lync: VideoWindows of AVModality.VideoChannel are null after successfully calling BeginStart (COMException HRESULT: 0x80029C4A TYPE_E_CANTLOADLIBRARY) -
we trying incorporate lync communication (lync sdk 2010) our application , have run issue videowindows (capturevideowindow, rendervideowindow) of avmodality's videochannel: null, after calling beginstart. connection established. can talk. our own video shown in remote lync client. avmodalitystate connected. videochannelstate goes connecting receive send.
it not matter when , how try access them: directly after beginstart, in asynccallback of beginstart, in response various state changes or in response external trigger (user click event); in main/ui thread or in event/callback thread. 2 video windows null.
in example application "%programfiles%\microsoft lync\sdk\samples\audiovideoconversation", works intended: beginstart has finished, can access non-null video windows. in our little stand-alone prototype project, works, too. in our real application, not.
we have double checked , have run out of ideas of might cause problem.
any ideas, hints? should aware of?
(link corresponding msdn forum thread)
update (4th july 2012, 15:46 cet):
when take @ members of videochannel find internally comexception occured in "microsoft.office.uc": error loading dll, hresult: 0x80029c4a (type_e_cantloadlibrary). more details in attached screenshot.

we did research on error, found nothing worked us. ideas causes exception?
update (9th july 2012, 16:43 cet):
we did further testing...
our software consists of 1 main application , many plugin-like "apps" loaded via mef. created minimal test app makes video call: video windows did not work (as expected). when took identical code , created separate solution outside of our architecture, did work. so, issue environment, not code.
at first, suspected mef might problem. so, hacked lync code our main application - circumventing whole app architecture. still not working.
then sliced off our whole system, bit bit, until reached point did work. after following wrong tracks several times, found culprit... quartz.net!
for strange reason mere presence of assembly reference quartz.dll v.1.0.3.3, without single line of quartz code, causes video windows not work. unbelievable, it's 100% reproducible: if take mentioned test solution , nothing add reference, stops working.
any idea how such thing possible?
we solved it! kind of. reference quartz.net dll somehow caused issue. more details in updated question.
for now, have removed component used quartz. not need it.
but i'm still interested in further input how mere reference can cause such issue.
Comments
Post a Comment