Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Core.IRibbonUI.'
Hello everybody. I have a user on Windows 7 and Office 2010. He receives the following error when using OnePlaceMail:
Error: Unable to cast COM object of type 'System._ComObject' to interface type 'Microsoft.Office.Core.IRibbonUI'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{000C03A7-0000-0000-C000-000000000046}' failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPEE_LIBNOTREGISTERED)).
I found this post (https://feedback.oneplacesolutions.com/forums/589411-oneplacemail-desktop/suggestions/18223252-com-error-in-ops-lite-when-moving-emails-to-folder) and it says that this bug is resolved. But I cannot find the solution anywhere in this post.
A support engineer has already run an Office repair and has also re-installed OnePlaceMail, but the error keeps coming back. Is it necessary to completely un-install Office and OnePlaceMail and re-install them again? Or is this an issue with Office 2010? Or is there another solution? Thanks in advance for all your help.
With kind regards, Richy
-
Hi Kat
I will email you these instructions
Kind regards
Elissa
-
Kat commented
Hi there,
I also have this issue, would you be able to email me the solution?
Thank you
Kat
-
Benoit Leguillier commented
Hello,
I'm facing the same issues for some users with Outlook 2013 (works fine with Outlook 365).
Would it be possible to know what the registry keys to update ?Many thanks in advance and kind regards,
Benoit
-
Stephen Carrier commented
Hello,
I am having the same issue. Is there a solution available?
Thanks very much.
Steve
-
Hi Mark,
Thank you for your inquiry.
I will email you the resolution.
Regards,
Zeeshan -
Mark commented
Hi Elissa,
I have a user getting the same issue, would you be able to send me through the resolution steps too please?
Many thanks
Mark -
Hi Richy
Thanks for your comment.
The root issue of this error is that the version reference for a key in the registry is pointing to an incorrect value.
For simplicity, I will email you these steps to resolve this issue.
kind regards
Elissa