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

Mycalendar is not working- Urgent

more options

I have upgraded from version 24.0 to 31.0 yesterday. My calendar is throwing some error.Need help on urgent basis

The calendar is available at the mentioned location. I have already checked it

Error message :

An error was encountered preparing the calendar located at https://stbeehive.oracle.com/caldav/st/home/arun.mangalath@ORACLE.COM/calendars/MyCalendar for use. It will not be available.

Error code : 0x80570015 [Exception... "Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]" nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)" location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/amangala/AppData/Roaming/Thunderbird/Profiles/yfvf5r0u.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]

I have upgraded from version 24.0 to 31.0 yesterday. My calendar is throwing some error.Need help on urgent basis The calendar is available at the mentioned location. I have already checked it Error message : An error was encountered preparing the calendar located at https://stbeehive.oracle.com/caldav/st/home/arun.mangalath@ORACLE.COM/calendars/MyCalendar for use. It will not be available. Error code : 0x80570015 [Exception... "Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]" nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)" location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/amangala/AppData/Roaming/Thunderbird/Profiles/yfvf5r0u.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]

All Replies (1)

more options

Issue has been fixed after upgrading Lightning to 3.3 . Thank you