본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Exchange integration stopped working with v52.1.1

  • 4 답장
  • 1 이 문제를 만남
  • 5 보기
  • 최종 답변자: gth65

more options

I have Thunderbird with Lightning that I use for work. I have several calendars set up in Lightning (local, google, and Exchange) which each have a different purpose, and have all been working together happily for two and a half years.

Yesterday, Thunderbird upgraded to v52.1.1 and on boot upgraded my plugins as well, and now my Exchange calendar (via Exchange EWS Provider 3.8.0-beta2) will not synchronize at all. I deleted the Exchange calendar with the intention of re-creating it - but now there is no communication between Lightning and the company Exchange server so I can't recreate the link at all.

Thunderbird is still talking to the Exchange server perfectly (via ExQuilla) so e-mail communication is not affected. This also proves both the server, account and password are still intact and working. I CAN still use the company's web version of outlook to access both e-mail and the calendar, so I know that system is still working from the server side.

I don't know if the issue is with Thunderbird, Lightning or Exchange EWS Provider, but it is a royal pain only having two of my three calendars available in TB, and having to use a web version of Outlook to access the third. Company security policies prevent me using an alternative to the Exchange server for company events so I'm a bit tied to it...

I note several others are reporting the same issue on github.

Does anyone know of a solution to this?

Thanks in anticipation.

I have Thunderbird with Lightning that I use for work. I have several calendars set up in Lightning (local, google, and Exchange) which each have a different purpose, and have all been working together happily for two and a half years. Yesterday, Thunderbird upgraded to v52.1.1 and on boot upgraded my plugins as well, and now my Exchange calendar (via Exchange EWS Provider 3.8.0-beta2) will not synchronize at all. I deleted the Exchange calendar with the intention of re-creating it - but now there is no communication between Lightning and the company Exchange server so I can't recreate the link at all. Thunderbird is still talking to the Exchange server perfectly (via ExQuilla) so e-mail communication is not affected. This also proves both the server, account and password are still intact and working. I CAN still use the company's web version of outlook to access both e-mail and the calendar, so I know that system is still working from the server side. I don't know if the issue is with Thunderbird, Lightning or Exchange EWS Provider, but it is a royal pain only having two of my three calendars available in TB, and having to use a web version of Outlook to access the third. Company security policies prevent me using an alternative to the Exchange server for company events so I'm a bit tied to it... I note several others are reporting the same issue on github. Does anyone know of a solution to this? Thanks in anticipation.

모든 댓글 (4)

more options

This is an issue with ExQuilla, so request help from them: http://exquilla.zendesk.com/

more options

Thanks Bruce.

I have communicated with Kent from ExQuilla previously on an unrelated calendar issue and been told by him (in no uncertain terms) that Exquilla has nothing to do any calendar function.

Exquilla does e-mail and address lookup with Exchange, and both these features are working fine.

Who provides support for Exchange EWS Provider? I don't see any contact information on its Extensions page...

more options

There is a newer version, 3.9, available:

https://github.com/Ericsson/exchangecalendar/releases

but it looks like v. 4.0.1003 is working with TB 52.1.1:

https://github.com/Ericsson/exchangecalendar/issues/595

more options

Thanks sfhowes,

That has indeed got the connection back again :) A little tweaking still required, but crisis averted for now.

Thanks