Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi
Solved Eza archivé

Getting an error when snoozing calendar reminders

Ybother

I have several reminders popping up. When I snooze them, or if I just close the window, I get an error window saying "An error occurred while writing to the calendar Home!" If I click the Details button, I get a message Error code: MODIFICATION_FAILED. That's all there is. It seems to be focused around one entry, as all the others get cleared from the notification window after I click "OK" on the error window, but one notification stays.

I have several reminders popping up. When I snooze them, or if I just close the window, I get an error window saying "An error occurred while writing to the calendar Home!" If I click the Details button, I get a message Error code: MODIFICATION_FAILED. That's all there is. It seems to be focused around one entry, as all the others get cleared from the notification window after I click "OK" on the error window, but one notification stays.
Tanga eyano oyo ndenge esengeli

Solution eye oponami

Restarting Thunderbird seems to have fixed this.

All Replies (5)

If you right click the Home calendar folder in the Calendar Pane on the left and select Properties, is the box for Read Only checked? If so uncheck it and see if it works better.

No, the calendar is not set to read-only. As I said, this is happening with only 1 entry out of several - all from the same calendar. The other entries are fine.

I forgot to mention that these are all tasks, not events, which are set to repeat once a year.

I am not sure what else would cause it. Hopefully someone else will have an idea. Sorry.

Solution eye oponami

Restarting Thunderbird seems to have fixed this.

Thanks for the update. Glad you figured it out.