Upgrade to Office 365 64bit - Unhandled Exception
I recently update to Office 365 2016 64bit and I am now getting an unhandled exception when starting the v1.2 exe saying TYPE_E_CANTLOADLIBRARY. Prior to this upgrade I was using the same Office version just the 32bit instead and localimhistory worked fine. Is this a known limitation for 64bit and is there a way for me to overcome this issue or a plan to update the tool to work?
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Uc.UCOfficeIntegration'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6A222195-F65E-467F-8F77-EB180BD85288}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
at Microsoft.Lync.Model.LyncClient.EnsureOI()
at Microsoft.Lync.Model.LyncClient.GetClient(Boolean sideBySideLync)
at LyncIMLocalHistory.Program.
************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
LyncIMLocalHistory Assembly Version: 1.2.0.0 Win32 Version: 1.2.0.0 CodeBase: file:///C:/Users/rl91824/Tools/LyncIMLocalHistory/LyncIMLocalHistory.exe
System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3353.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.Lync.Model Assembly Version: 15.0.0.0 Win32 Version: 15.0.4603.1000 CodeBase: file:///C:/Users/rl91824/Tools/LyncIMLocalHistory/Microsoft.Lync.Model.DLL
System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.Office.Uc Assembly Version: 15.0.4603.1000 Win32 Version: 15.0.4603.1000 CodeBase: file:///C:/Users/rl91824/Tools/LyncIMLocalHistory/Microsoft.Office.Uc.DLL
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
I'm sorry but I'm not working on this project anymore. Try to contact someone who forked my project if they still use and develop the tool. Thanks
I'm sorry but I'm not working on this project anymore. Try to contact someone who forked my project if they still use and develop the tool. Thanks
Crap!
But on a side note, this has been a great app over the years!!
I must say I love this app also.
And i still left it run even though it didn't work as I was looking for other ways to fix or workaround this issue.
I'm on O365 monthly updates and for the past few weeks it was working, the another update and the same error. @bujocek how much would it cost to get this fixed? I would be extremely happy to pay a reasonable amount for your time to fix this issue, if you can?
Either way, thank you for a great app for the past few years.
@mande01 Thanks for the offer, but the main problem is that I changed my job and we don't use Lync/SkypeForBusiness here. So i can not even reproduce the problem, nor fix it. I'm sorry. And there is no point in buying SFB licence just for me and create a domain just to run it and fix this issue (and we don't know if it is even possible to fix it).
Thank you, I totally understand.
This has been a fantastic little piece of software, which I have used extensively.
I'll going fishing for a developer who may be able to get involved.