Outlook access

Dec 18, 2014 at 5:06 PM
I set the program to run in the system tray (doesn't appear but its running - maybe I should use the Beta version?) and sync once a week (Google to Outlook). The next day and every day since a popup from Outlook asks if I want to grant something permission to access my Outlook email.

Is that this program (Outlook doesn't say, which is not helpful)?

Is Outlook's popup poorly drafted - meaning it says "email" but it means "calendar"?

If I'm syncing Google to Outlook once per week why is the program trying to run every day?

Concerning behavior - thanks for explaining.
Coordinator
Jan 24, 2015 at 12:12 PM
The permissions pop-up is indeed this program requesting programmatic access to Outlook (there is no distinction between email and calendar).

See here for more detail: https://outlookgooglecalendarsync.codeplex.com/wikipage?title=FAQs%20%2f%20Known%20Issues&referringTitle=Documentation#security

Regarding syncing once per week, the option is intervals of minutes or hours - not days. However, v1.2.3.1 has had a bit more refinement around the automatic scheduling, so you may like to see if this handles syncing once per week as you are wanting.

Thanks
Coordinator
Jan 24, 2015 at 4:22 PM
I've just found a tool called Advanced Security for Outlook and tested this on 2003 - seems to do the job of suppressing the security popup nicely. It does require installation however. I've updated the documentation accordingly.
Marked as answer by phw198 on 2/15/2015 at 5:34 AM
Jan 7, 2016 at 9:54 PM
I have a similar symptom where I have set a sync interval of 3 hours, but Outlook seems to pop up a security window for a sync attempt every hour. It doesn't seem to honour the interval I have set?

I'll also try the Advanced Security for Outlook tool to try and suppress this popup...
Jan 14, 2016 at 4:40 AM
The Advanced Security for Outlook tool did suppress the popup, however it caused other problems (Outlook would spike to 100% CPU every time I copied something to the clipboard... strange!), so I had to stop using it.
Coordinator
Jan 14, 2016 at 7:20 AM
Hi Annihilannic,
Thanks for the feedback on that security tool.
For the hourly pop-up, when you change the sync interval on the Settings tab to e.g. 3 hours, what is the"next sync" reported as on the Sync tab? If it's correctly 3 hours after the last successful sync, then what does the OGcalsync.log file say it's doing when you get the premature security pop-up?
Jan 15, 2016 at 12:06 AM
Edited Jan 15, 2016 at 1:04 AM
It does correctly calculate when the next scheduled sync should occur, displayed both in the log file and where you described on the Sync tab (previous successful sync was 09:57).

2016-01-15 11:33:12,095 INFO 1 OutlookGoogleCalendarSync.MainForm [0] - Next sync scheduled for Friday, 15 January 2016 - 12:57: 56

However it seems to trigger an hour earlier than it should:

2016-01-15 11:57:12,144 DEBUG 1 OutlookGoogleCalendarSync.MainForm [0] - Scheduled sync triggered.
2016-01-15 11:57:12,160 DEBUG 1 OutlookGoogleCalendarSync.MainForm [0] - Scheduled sync started.

Some daylight savings time confusion perhaps?

Hmm... no, I don't think it's that, the following sync:

2016-01-15 12:03:27,490 INFO 1 OutlookGoogleCalendarSync.MainForm [0] - Next sync scheduled for Friday, 15 January 2016 - 15:03:19
2016-01-15 13:02:27,571 DEBUG 1 OutlookGoogleCalendarSync.MainForm [0] - Scheduled sync triggered.
2016-01-15 13:02:27,576 DEBUG 1 OutlookGoogleCalendarSync.MainForm [0] - Scheduled sync started.
Jan 18, 2016 at 10:20 PM
I opened a support query with MAPILab about the high CPU usage and they recommended other tools for this purpose, pointing me to this discussion on the MYOB forums.

Rather than installing ClickYes as suggested there, I'm already running AutoHotKey so I wrote this script to detect and answer the Outlook dialogue:
#Persistent
SetTimer, OutlookAllowAccess, 500

OutlookAllowAccess:
If WinExist("Microsoft Outlook ahk_class #32770", "A program is trying to access")
{
    WinActivate
    Send !a{Tab}{Tab}{Space}
}
Return
That does the trick. Any more thoughts on the scheduling issue though?
Feb 23, 2016 at 5:18 AM
Using this registry key method now to avoid the warnings, a much better way:

http://www.slipstick.com/developer/change-programmatic-access-options/