Upgrade to TB 24 and lightning 2.6 breaks exchange plugin

[Stuart Brown]

Getting this error when starting thunderbird after automatic update to TB 24 and lightning 2.6:

An error was encountered preparing the calendar located at https://auto/272d5f27-ea3d-4384-846d-1cb88ce7427e for use. It will not be available.

[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:///home/aqil/.thunderbird/k0f73wtm.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]

Am guessing this is the exchange plugin because it was not included in the upgrade and the exchange calendar is the one not appearing.

Setup debug config and this is output :
[calBackendLoader] Using libical backend at /home/aqil/.thunderbird/k0f73wtm.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical.manifest
Error: [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:///home/aqil/.thunderbird/k0f73wtm.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]
Error: [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:///home/aqil/.thunderbird/k0f73wtm.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]

[Stuart Brown (sabrown-9)]

Sorry this may not be a bug with the exchange provider. I seem to be using Exchange EWS Provider Add-on for Lightning not this plugin.

Don't know how to take back this bug report.