v3.0.0.1: Unable to start

[phw198]

See #1888 for latest release updates.

Having extracted the development build v3.0.0.1, when running it from the command line as per the instructions (with a blank settings file), it fails with Object reference not set to an instance of an object.

[TheJacksonian]

Where is the best place for feedback?
I'll reply here, but happy to move if required. I get an Application unexpectedly terminated on start, 'Object reference not set to an instance of an object'.
Log attached.
OGcalsync.log

[phw198]

I was wondering about this, and I think it's a good opportunity to test out GitHub Discussions - so I've converted this issue over to see how it goes 🙂

So I think you missed out the keyword call at the start of the line invoking the OGCS executable? Also, try wrapping the /t parameter value in speech marks: "Development Build".

[TheJacksonian]

I thought it might be due to spaces in the path, so I moved it exactly as described by you, and I was copy/pasting the call command.

Same issue.
OGcalsync.log

[TheJacksonian]

Yes, I got the screen (only once yesterday, cannot reproduce) that asked for permission to automatically report the errors, and then it crashed. Now I'm getting the splash screen and the crash. Log is attached.

OGcalsync.log

[phw198]

Did you extract the updated zip file into the same directory as before? If so, I think you have a corrupted settings.xml file in there from your first attempt, which is causing this - the file should be around 7kb in size, not 3kb or so.

Delete that file and run OGCS again and I think it should work?

[TheJacksonian]

Success!! Deleted the settings.xml! Working through setting it up with my dummy calendar now.

[TheJacksonian]

However, upon login, here endeth where I can assist you. There's no way I'll be getting this Admin permission. I'll discuss with some people when I'm back in the office next week, but I don't like my chances.

[phw198]

Interestingly, the consent screen for my corporate account looks slightly different - I guess it depend on the organisation and/or their security config...

[phw198]

Hi @TheJacksonian, @Zikoat, did either of you get a chance to discuss approving OGCS access with your IT department?

[caesay]

I use OGCS to mirror my work Outlook calendar onto a personal Google one so I can see it on my personal devices. I'm going to run into this same issue with ITOps. The "Write user and shared calendars" will likely be a blocker, since most global calendars in my company are shared in good faith, but could cause chaos if someone started mucking with them. I actually only need "Read user calendar" since I'm only syncing my personal calendar O->G. Do you think there'd be any chances we could reduce the permissions required to support this use-case?

[Zikoat]

@phw198 Response was denied from IT:
"It is not desirable to synchronize company information from a work account to a private Google account."

[faultoverload]

I think the only way to avoid the requirement to setup an app would be to use a built in browser that lets you log into OWA and then grab the auth token from that to use. You will run into issues with the refresh timers on those tokens though, not to mention having to reverse engineer the internal API used inside of OWA.

[jeme81]

Since the "new" client version may no longer require the outlook app to be installed does this open up the possibility of a linux version of this sync client?

[phw198]

Requests for MacOS version are much more common, but I've not the time to do that either, so no, very unlikely...

[mickey58github]

I have installed v3.0.0.1 successfully on a Windows 10 notebook for testing, and got it working.

Now I'm trying to install it on my Windows 11 laptop. Same as on my Win 10 machine, I unpacked the zip file to C:\OCGS-dev. Then I open a command window, change directory to this directory, and execute the command C:\OCGS-dev>call OutlookGoogleCalendarSync /t:"Development Build" /s:.\settings.xml /l:.\OGcalsync.log. But it get the above error Object reference not set to an instance of an object. I deleted the setup file after this error occured and retried, but still this strange error...

My log file: OGcalsync.log

What is wrong?

[phw198]

What are the two pages with the different links? But why are you running the original v3.0.0.1? There are several releases more recent than that...

[mickey58github]

The page from which I downloaded the first 3.0.0.1 zip file is #1881

After the error, I downloaded another 3.0.0.1 zip file from the link on #1888.

Will try with the latest hotfix next.

[mickey58github]

I replaced the original .exe with the one that comes with the 3.0.0.6 hotfix, but both with the 3.0.0.1 exe that comes from the link on #1888, and with the one that comes with the 3.0.0.6 hotfix, I get this error after startup:: 0x8002802B - TYPE_E_ELEMENTNOTFOUND

[mickey58github]

Next I did an Office repair as advised on https://github.com/phw198/OutlookGoogleCalendarSync/wiki/FAQs---COM-Errors#0x8002802b---type_e_elementnotfound, but the 0x8002802B error persists (running 3.0.0.6)...

Log file: OGcalsync.log

[phw198]

#1915 talks of reverting to a restore point to when Outlook wasn't broken by an upgrade.

But if you are wanting to use OGCS v3 which doesn't need the classic Outlook client, is that even installed at all? If the classic Outlook is not meant to be installed, then I think the problem is you still have remnants of COM configured on your system:

2024-09-11 01:06:04,148 INFO  1 OutlookGoogleCalendarSync.Outlook.Factory [233] -  Assembly details: Microsoft.Office.Interop.Outlook, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
2024-09-11 01:06:04,149 DEBUG  1 OutlookGoogleCalendarSync.Outlook.Factory [235] -  Assembly location: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.Office.Interop.Outlook\15.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Outlook.dll
2024-09-11 01:06:04,156 INFO  1 OutlookGoogleCalendarSync.Outlook.Calendar [1128] -  Attaching to the already running Outlook process.

Can you fully uninstall the classic Outlook? I guess the Outlook OGCS has detected running is the New Outlook?