You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
A clear and concise description of what the bug is.
After I upgraded to v2.10.5.0 I received a pop up error box entitled Calendar Folders. The message read: A problem was encountered when searching for Outlook calenda folders. Cannot access a disposed object. Object name: 'TabPage'. On clicking OK, the window reappeared. All I could do was to kill OGCS in task manager. Can you assist please? Steps to Reproduce the Issue
Go to...
Click on...
Any other information
Any additional information that may help troubleshoot the issue.
📎 Attach your OGcalsync.log file.
The text was updated successfully, but these errors were encountered:
Thanks for the logfile. Yes, it was pretty niche - basically v2.10.4 was still initialising (and having trouble connecting to the Outlook client for some reason) and at the same time the upgrade ran and then started shutting down the application.
I've now made that shutdown much more forceful, so the initialisation doesn't attempt to continue. However, this won't be available until v2.10.6 and upgrading from there.
The issue is only related to completing the end of the upgrade, otherwise what you have installed is working fine - I'd suggest you just stay with what you have.
OGCS Version: v2.10.5.0
Edition: Installed
Sync Direction: O<->G
Bug Description
A clear and concise description of what the bug is.
After I upgraded to v2.10.5.0 I received a pop up error box entitled Calendar Folders. The message read: A problem was encountered when searching for Outlook calenda folders. Cannot access a disposed object. Object name: 'TabPage'. On clicking OK, the window reappeared. All I could do was to kill OGCS in task manager. Can you assist please?
Steps to Reproduce the Issue
Any other information
Any additional information that may help troubleshoot the issue.
📎 Attach your
OGcalsync.log
file.The text was updated successfully, but these errors were encountered: