Cannot access Outlook profile recipient.Name [0x80004004]
See original GitHub issueOGCS Version: v2.8.2.0 (Alpha)
Edition: Installed
Sync Direction: G->O / O->G / O<->G
Bug Description
OGCS crashes and the process thread closes by itself
Steps to Reproduce the Issue
- Launch OGCS
Any additional information that may help troubleshoot the issue. Version of outlook: 15.0.5172.1000 MSO 32-bit Machine: Surface Pro Windows version: Windows 10 Enterprise 1809 version
OGcalsync.log
📎 Attach your OGcalsync.log
file.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Unable to access appointment recipients [0x80004004 ...
I used OGCS successfully for quite some time and it stopped working when my Office installation was upgraded to Office 365. Are there...
Read more >Can't open Outlook after changing Windows 10 profile name
Can't open Outlook after changing Windows 10 profile name · 1. Open Control Panel · 2. Change Control Panel view to small icons...
Read more >MS Outlook VBO - Error in get mail stage | Blue Prism Product
Im looking for the Email in Inbox folder and have only 1 outlook profile configured and I'm still getting this error. 10.
Read more >Get Outlook Mail Message not working - Help
According to a few of the Microsoft sites (e.g. Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) - outlook appointment ) this is ...
Read more >Can't set up a new profile by using Exchange Autodiscover ...
Describes an issue that blocks Outlook from setting up a new profile by using Exchange Autodiscover for an Exchange Online mailbox in ...
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
Works well. It raised an AV exception, but once I allowed it - it went through.
I have a corporate exchange account and AV is managed by the IT. I couldnt disable the AV but I was able to allow exceptions and exclude OGCS to .
Hope you will incorporate the fix in the main build. I have been using OGCS for a while now, just moved to a new laptop and the issues started.
Sync just finished and worked flawlessly as before. Thanks for the help
📦 OK, please try again with v2.8.2.23.zip (see instructions for applying).
For my info, can you describe the environment you’re running in? Looks like a corporate Exchange account - is the AV also managed by your IT? Can you temporarily disable the AV?