Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When upgrading to version 2.10.5.0 error received. #1861

Open
Veggie352 opened this issue May 19, 2024 · 5 comments
Open

When upgrading to version 2.10.5.0 error received. #1861

Veggie352 opened this issue May 19, 2024 · 5 comments
Assignees
Labels
bug Something's not working right resolved Working hotfix available
Milestone

Comments

@Veggie352
Copy link

Checklist:-

  • Upgrade to the latest release (alpha if available) latest release
  • Reproduce the issue
  • Complete the information below
  • Provide your OGcalsync.log file (see how-to)

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

  1. Go to...
  2. Click on...

Any other information
Any additional information that may help troubleshoot the issue.
📎 Attach your OGcalsync.log file.
OGCS error

@Veggie352 Veggie352 added the bug Something's not working right label May 19, 2024
@phw198
Copy link
Owner

phw198 commented May 19, 2024

🗒️ If you can provide your OGcalsync.log file (see instructions), I'll take a look.

@phw198
Copy link
Owner

phw198 commented May 19, 2024

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.

@phw198 phw198 self-assigned this May 19, 2024
@phw198 phw198 added the resolved Working hotfix available label May 19, 2024
@phw198 phw198 added this to the v2.10.6 milestone May 19, 2024
@Veggie352
Copy link
Author

Veggie352 commented May 20, 2024 via email

@phw198
Copy link
Owner

phw198 commented May 20, 2024

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.

@Veggie352
Copy link
Author

Veggie352 commented May 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's not working right resolved Working hotfix available
Projects
None yet
Development

No branches or pull requests

2 participants