Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can not open interface - [0x8002802B] (TYPE_E_ELEMENTNOTFOUND) #999

Closed
john270 opened this issue Jun 3, 2020 · 34 comments
Closed

Can not open interface - [0x8002802B] (TYPE_E_ELEMENTNOTFOUND) #999

john270 opened this issue Jun 3, 2020 · 34 comments
Labels
bug Something's not working right dll hell Office libraries and/or registry broken dormant Issue has not been responded to over 30 days

Comments

@john270
Copy link

john270 commented Jun 3, 2020 •
edited by phw198
Loading

Checklist:-

  • Upgrade to the latest release latest release
  • Reproduce the issue
  • Complete the information below
  • Provide your OGcalsync.log file (see how-to)

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

  1. Launch OGCS

Any other information
OGcalsync.log is attached
@john270 john270 added the bug Something's not working right label Jun 3, 2020
@Olgrov
Copy link

Olgrov commented Jun 4, 2020

Same issue for me. Outlook repair as well as reinstall did not work.
OGcalsync.log

@phw198 phw198 changed the title Can not open interface - error 8002802B (unknown) Can not open interface - [0x8002802B] (TYPE_E_ELEMENTNOTFOUND) Jun 10, 2020
@phw198 phw198 added the dll hell Office libraries and/or registry broken label Jun 10, 2020
@phw198
Copy link
Owner

phw198 commented Jun 10, 2020

This definitely looks like a strange one - never seen that error code before and there's almost nothing found by Google either.

I'm wondering if it might be worth you checking for dependencies and whether any missing dependencies are found:

  1. Download Dependencies from GitHub
  2. Extract the ZIP, and execute DependenciesGui.exe.
    1. If SmartScreen blocks it, right click the file > Properties > Unblock
  3. Locate your OGCS executable: %LOCALAPPDATA%\OutlookGoogleCalendarSync\app-2.8.3-alpha\OutlookGoogleCalendarSync.exe and open in Dependencies.
  4. Provide a screen shot of what it reports.

@phw198 phw198 mentioned this issue Jun 10, 2020
Closed
Repository owner deleted a comment from PackElend Jun 10, 2020
@john270
Copy link
Author

john270 commented Jun 11, 2020

Thanks for the feedback. I've not used the dependencies tool before so not sure what is important to focus on - please let me know if you need me to expand any of the information.
image

@phw198
Copy link
Owner

phw198 commented Jun 13, 2020

TBH, I'm not entirely sure what to look for either - was hoping it might obviously flag something missing, but it doesn't look like it.

I also posted here about trying Microsoft's SysInternals Process Monitor to see if that shows anything either too...

@ond198
Copy link

ond198 commented Jun 15, 2020

Checklist:

  • Upgraded to the latest release latest alpha release
  • Reproduced the issue several times
  • Reported the issue
  • Provided the OGcalsync.log file (see below)

OGCS Version: v2.8.3 / v2.8.0 / v2.5.3
Edition: Install & Portable
Sync Direction: Not applicable

Bug Description
I'm experiencing a very similar issue where OGCS crashes upon launching. This started happening after I went through a complete re-installation of Outlook last weekend. I've tried re-installing v2.8.3, v2.8.0, and even 2.5.3 which I used earlier. I've also tried using the portable edition of v2.8.3. All crash the exact same way. I've tested the above before starting Outlook as well as after starting Outlook. I've tested it while the machine had been running for a while as well as right upon rebooting. All approaches result in the same error 0x80040155.

Steps to Reproduce the Issue
Launch OGCS

Any other information
OGcalsync.log

@phw198 phw198 mentioned this issue Jun 15, 2020
Closed
@phw198
Copy link
Owner

phw198 commented Jun 15, 2020

@ond198 Your issue is different so I have now created issue #1012 to track it under. Meanwhile, the error should have taken you to the wiki.

@Olgrov
Copy link

Olgrov commented Jul 24, 2020

Upgrading to v. 2.8.4.0 does not help.
OGcalsync.log

@phw198
Copy link
Owner

phw198 commented Aug 4, 2020

As per this link, can you confirm if you have "Microsoft Visual C++ 2008 Redistributable Package" installed?

If you do, could try uninstalling it and reinstalling?

Microsoft downloads: 64-bit or 32-bit

@Olgrov
Copy link

Olgrov commented Aug 5, 2020

The Package was installed. I uninstalled and reinstalled both packages and restarted the system but it still did not help unfortunately.

@Olgrov
Copy link

Olgrov commented Sep 15, 2020

Yesterday I uninstalled my office, then reinstalled it to version 1908. And OGCS worked again properly. Then I updated my office to updatebranch = Current (i.e. version 2008) and the crash during start of OGCS happens again.
OGCS error

@MarcoUmpierrez
Copy link

MarcoUmpierrez commented Nov 11, 2020 •
edited
Loading

Hello, looking for this error I ended up here and today one of my colleagues already found the solution so, as a good internet citizen I'm going to share it here too:

The problem seems to be related to upgrading or uninstalling office. It leaves old registry entries that conflict with the current version.

The solution is to remove the key of the registry that doesn't match the installed version.

Link

@phw198
Copy link
Owner

phw198 commented Nov 22, 2020

@MarcoUmpierrez Thanks, though the fix you have linked to is related to TYPE_E_CANTLOADLIBRARY, which is 0x80029C4A and already well documented.

Are you saying 0x8002802B is also fixed with the same registry changes?

@phw198
Copy link
Owner

phw198 commented Nov 22, 2020 •
edited
Loading

@Olgrov Current channel looks to be v2010 now - did upgrading to v2009 or v2010 help at all?

@phw198 phw198 added the dormant Issue has not been responded to over 30 days label Jan 24, 2021
@phw198 phw198 closed this as completed Jan 24, 2021
@phw198 phw198 mentioned this issue Mar 13, 2021
Closed
@ajburke3
Copy link

I also ran into this problem. Unfortunately it wasn't solved by the steps for 0x80029C4A TYPE_E_CANTLOADLIBRARY.

As it stands now, I'm unable to use OGCS, which bums me out because it's GREAT and has been so helpful to me over the years. Please update this bug if any solution found. Thank you.

Details:

  • Most recently I've been using OGCS with:

    • Windows 10 Enterprise version 21H1 OS build 19043.1706 experience pack 120.2212.4170.0
    • Microsoft® Outlook® for Microsoft 365 MSO (Version 2202 Build 16.0.14931.20272) 64-bit

  • My company has instructed me to transition from the above Dell desktop to a new Dell laptop that's running:

    • Windows 10 Enterprise version 21H1 OS build 19044.1766 experience pack 120.2212.4180.0
    • Microsoft® Outlook® for Microsoft 365 MSO (Version 2204 Build 16.0.15128.20278) 64-bit

  • On this clean laptop I installed OGCS v2.9.0-beta.

  • But when I tried to run OGCS, it gave this bug's error about 0x8002802B TYPE_E_ELEMENTNOTFOUND.

  • I tried and checked all of the steps for 0x80029C4A TYPE_E_CANTLOADLIBRARY. The only finding was from the very bottom of that article, where my MSOUTL.LIB was in path ...\root\... but the registry setting said ...\Root\.... Everything else from the article was as-expected, I registered MSOUTL.LIB using regtlibv12.exe, rebooted the laptop, tried OGCS again, same error. I uninstalled and reinstalled OGCS, still same error.

  • Then I tried OGCS v2.9.5-alpha. When I ran it, I got the same error.

OGcalsync.log attached.

Hopefully some solution soon. Thanks.

OGcalsync.log

@HB9GAA
Copy link

HB9GAA commented Jul 11, 2022

I have the same problem, since about 2 weeks. Outlook 2019 and Windows 11.
Attempts to solve the problem according to the instructions for 0x80029C4A I have not managed.
The program OGCS breaks after the start.

Need urgent help, thank you.

@DN1967HB
Copy link

I have the same problem, since 2 days. Outlook 2019 and Windows 11.
The program OGCS breaks after the start.
Need urgent help too, thank you!!!

@phw198
Copy link
Owner

phw198 commented Jul 23, 2022

Last time this occurred, it seems to be an Outlook build issue on v2008, that fixed on v2010.

@ajburke3 Your broken laptop is v2204 and I see v2205 was released on 12-July if you're on the Monthly Enterprise Channel - have you been able to upgrade Office and does OGCS work now?

@HB9GAA What version of Outlook are you running?

@ajburke3
Copy link

Thanks @phw198 . I'll check with our IT dept to see if I can upgrade Office.

@phw198
Copy link
Owner

phw198 commented Sep 5, 2022

Hi @ajburke3 - were you able to update Office to v2205 and did it help?

@ajburke3
Copy link

ajburke3 commented Sep 5, 2022 via email

@risobalaz
Copy link

risobalaz commented Sep 18, 2022 •
edited
Loading

Hello, struggling with starting sync after latest Office update (company stuff). Attaching OGcalsync.log. Trying to use 0x80029C4A fix, but there are not Win32 references. Really missing this great tool!
OGCS Version: v2.9.5-alpha (but tried 2.9.0-beta with same result)
Edition: Install Setup.exe
OGcalsync.log

@HB9GAA
Copy link

HB9GAA commented Oct 11, 2022 via email

@doktornotor
Copy link

Hello, struggling with starting sync after latest Office update (company stuff). Attaching OGcalsync.log. Trying to use 0x80029C4A fix, but there are not Win32 references. Really missing this great tool! OGCS Version: v2.9.5-alpha (but tried 2.9.0-beta with same result) Edition: Install Setup.exe OGcalsync.log

Seems to have fixed itself after latest Office 2021 updates. Using LTSC though, (16.0.14332.20378)

@HB9GAA
Copy link

HB9GAA commented Oct 13, 2022 via email

@risobalaz
Copy link

Repair seems to make things working again. Thanks for support!!

@ajburke3
Copy link

@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!

@HB9GAA
Copy link

HB9GAA commented Oct 14, 2022

This problem occurs if the Microsoft Office part (Ole32.dll file that is located in the %WINDIR%\System32 folder) is not registered correctly in the Microsoft Windows registry.

@meberli
Copy link

meberli commented Oct 17, 2022

I also have this issue. Office repair solves it. But same error seems to come again after every Office update..

@NTV-Biker
Copy link

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 phw198 mentioned this issue Dec 18, 2022
Closed
@EthanFord888
Copy link

Hi I had the same problem. After I did the Office Repair ( App -> Installed App -> Change -> Quick Repair) everything was OK again. Best regards Roland
…
_____ HB9GAA Brunnhaldenstrasse 8 3510 Konolfingen Switzerland Tel: 41 (0)31 792 04 60 Mail: @.> @. Von: doktornotor @.> Gesendet: Mittwoch, 12. Oktober 2022 09:19 An: phw198/OutlookGoogleCalendarSync @.> Cc: Roland @.>; Mention @.> Betreff: Re: [phw198/OutlookGoogleCalendarSync] Can not open interface - [0x8002802B] (TYPE_E_ELEMENTNOTFOUND) (#999) Hello, struggling with starting sync after latest Office update (company stuff). Attaching OGcalsync.log. Trying to use 0x80029C4A fix, but there are not Win32 references. Really missing this great tool! OGCS Version: v2.9.5-alpha (but tried 2.9.0-beta with same result) Edition: Install Setup.exe OGcalsync.log https://github.com/phw198/OutlookGoogleCalendarSync/files/9594955/OGcalsync.log Seems to have fixed itself after latest Office 2021 updates. Using LTSC though, (16.0.14332.20378) — Reply to this email directly, view it on GitHub <#999 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6PPEDO3E6NA22TISUTK2DWCZQ6DANCNFSM4NRN7E5A . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AC6PPEFPYPFSHT5KAHE4U53WCZQ6DA5CNFSM4NRN7E5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJQE22KI.gif Message ID: @.*** @.***> >

Good day Roland,

Please could you explain how to do this repair ?

I have gone through apps and features but the problem still persists.

Regards

@sanojn sanojn mentioned this issue Oct 18, 2023
Closed
@jstarj010101
Copy link

A repair worked for me. I'm on Win11 and followed this: https://thegeekpage.com/repair-microsoft-office/

@JonathanBasys
Copy link

JonathanBasys commented Jul 10, 2024 •
edited
Loading

An office update did the trick for me as well 👍 Thanks for the pointing in the right direction with the wiki opening on the exact error code I was experiencing - awesome work!

... and the next day, I'm here again! 😨

@r10thamus r10thamus mentioned this issue Aug 13, 2024
Closed
@aisbergde
Copy link

image

or sorted by Module
image

@phw198
Copy link
Owner

phw198 commented Oct 27, 2024

@aisbergde Looks like you're running v3.0.0.1, which shouldn't need the client at all - however, I don't think the development releases have fully removed the reliance on the client. But anyway, if you've not got the classic Outlook client installed any longer, I'd not expect the COM interface to work.

Make sure you're getting the latest development releases - v3.0.0.6 is available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something's not working right dll hell Office libraries and/or registry broken dormant Issue has not been responded to over 30 days
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests