Can not open interface - [0x8002802B] (TYPE_E_ELEMENTNOTFOUND)
See original GitHub issueChecklist:-
OGCS Version: v2.8.3
Edition: Portable
Sync Direction: O->G (although fails before this stage)
Bug Description
Since recent MS outlook updates application no longer opens. Using v2.8.0 gives error 80004002, but unlike issue #991, my error with latest release (2.8.3) is 8002802B and this error is not listed in the wiki (or mentioned in other issues).
Steps to Reproduce the Issue
- Launch OGCS
Any other information
OGcalsync.log is attached
Issue Analytics
- State:
- Created 3 years ago
- Comments:30 (8 by maintainers)
Top Results From Across the Web
I have this error when automating excel actions: Unable to ...
I am trying to open an excel workbook with an automated action and I get this error: Unable to cast COM object of...
Read more >Unable to cast COM object of type 'Microsoft.Office.Interop. ...
failed due to the following error: Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND))." (see attachment). I tried ...
Read more >Unable to cast COM object of type 'Microsoft.Office.Interop. ...
Hello - has anyone seen and solved this error when opening/creating excel actions? Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.
Read more >This operation failed because the QueryInterface call on ...
ApplicationClass' to interface type 'Microsoft.Office.Interop.Word._Application'. This operation failed because the QueryInterface call on the ...
Read more >Make sure excel is installed error - Academy Feedback
Can anyone advise on next steps to fix this? Error opening workbook. Make sure Excel is installed. Unable to cast COM object of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Problem solved: I had serveral blue screen incidents on a Dell Latitude 5490 Laptop using Office 365 - 2022 (Build 14931.70764) and Win 10 (21H2 Build 19044.2132). After approx. 10 blue screen incidents I got the 0x8002802B message.
I used the repair feature of Office 365/ new Installation feature. Afterwards OGCS worked well as before. Obviously one or more Office files where corrupted caused by the system breakdown/ blue screen. No additional registry hacks (cleaning, deleting keys etc.) were necessary.
I’m happy that OGCS ist running again. I appreciate it very much.
@phw198, I’m now at my new company, and the latest version of Office, and yup hooray OGCS is once again working great. Thanks again for a great product which I’ll happily keep supporting!