-
Notifications
You must be signed in to change notification settings - Fork 217
Known Issues
FAQs > Known Issues |
---|
- Why Won't OGCS Upgrade? I Know There's a Later Version Released!
- "Page cannot be displayed" After Authorising OGCS To Access My Calendar
- Usage Limits Exceeded
- Anti-Virus False Positives
- Windows Defender SmartScreen Protected Your PC
- Old Events Not Observing Daylight Saving
- Outlook Spam/Junk Mail Interference
If the later version has only just been released, it is usually rolled out gradually over the course of a week. If you wish to upgrade more quickly, the setup file can be downloaded manually - see the wiki Upgrading section for more details.
If you are running a version of OGCS prior to v2.7.4.0, unfortunately GitHub made a change that broke the upgrade mechanism. You will need to manually download at least v2.7.4 for the upgrade process to work again.
ℹ️ Also reported as directing to https://accounts.google.com/info/unknownerror and displaying "An error has occurred! Sorry, an error occurred. Please try again.".
This may happen if you have Google Chrome as your default browser and have previously accessed a website on https://localhost
- something web developers or people in IT may do. To resolve this, there are several options available:
- Change the start of the URL from
https://
tohttp://
- Perform a hard refresh by pressing
-
Ctrl+F5
, or -
F12
and then right-click the refresh button andHard Reload
orEmpty Cache and Hard Reload
-
- At the start of the authorisation process, copy the URL out to
- an Incognito Chrome window (
Ctrl+Shift+N
) - a different browser
- an Incognito Chrome window (
Although Google do impose usage limits, there appears to be a bug related to events with multiple recipients with different email address domains. Therefore, if you are continually hitting this problem, try unchecking the sync attendees option.
Unable to add new entries into the Google Calendar. The following error occurred:
Google.Apis.Requests.RequestError
Calendar usage limits exceeded. [403](403)
Errors [
Message[Calendar usage limits exceeded.](Calendar-usage-limits-exceeded.) Location[ - ](---)
Reason[quotaExceeded](quotaExceeded) Domain[usageLimits](usageLimits)
will help anti-virus software to trust it[1] 🌟
[1]However, a new certificate has to be purchased every year, which loses any reputation the previous certificate had built. This means there is a month or so each year of increased false positives whilst the reputation rebuilds on the new certificate. 😞
Some AV software may falsely report OGCS as a virus. This is likely due to OGCS accessing the Outlook address book to determine the email address of meeting attendees, which is required in order to sync them.
This being a spare-time project, there's no way I can submit every release of OGCS to every over-zealous AV vendor - support from the user community in doing so would be greatly appreciated 👍
False positive reporting links for some well known AV vendors:-
- AVG
- Avast
- Bitdefender
- F-Secure
- Kapersky
- McAfee
- Norton - then click "Incorrectly Detected by Norton"
- Symantec - then click "Incorrectly Detected by Symantec"
This is normally the Windows 10 Edge browser marking files that are downloaded from the internet (especially executable files) as blocked by default. To unblock your OGCS download:
- For
Setup.exe
right-click the file and selectProperties
- In the bottom right hand corner, click the
Unblock
button. - Execute
Setup.exe
If you are wanting to use the portable zip release, either double-click the Windows Defender SmartScreen Unblock.ps1
file or follow these steps manually:
-
Winkey+R
and typepowershell
- Change directory to the extracted files
cd C:\my\extracted\files\directory
Get-ChildItem | Unblock-File
- Now run OGCS by double clicking the executable.
As per issue 239, 1728, Outlook may not recalculate the new time properly. In this case, you need to re-open the problematic appointment(s), change the start time, change it back and then save it. This should force Microsoft to recalculate the time, accounting for DST, local to you.
As per Issue 1072, holding a programmatic connection open with Outlook appears to interfere with its spam mechanism and the notification messages that display above suspect messages. To workaround this, a hidden option is available with OGCS, forcing it to disconnect from Outlook inbetween syncs:
- Go to the
About
tab and double click on the path for "Config In" - this will open Windows Explorer - Close OGCS
- In the Explorer window, find your
settings.xml
file and open in an editor - Find the
DisconnectOutlookBetweenSync
line and change the value fromfalse
totrue
- Save and start OGCS