Exchange EWS Provider stopped reading from and writing to Outlook calendar

[infobroker]

I'm posting this issue because Thunderbird/Lightning used to play very well with my Outlook calendar until early in December 2015. Since then only some of the items in my Outlook calendar display in my Thunderbird/Lightning calendar and I no longer seem to be able to add events to the Outlook calendar through Thunderbird/Lightning. I believe that the Exchange server URL should still be what it has always been (https://pod51011.outlook.com/ews/exchange.asmx). I am using Thunderbird 38.5, Lightning 4.0.5, and Exchange EWS Provider 3.5. I am experiencing similar issues in both Windows and Mac environments. Does anybody think that I should try reverting to an earlier version of anything to try to get the calendars to communicate better again? I'm just really frustrated because it used to work perfectly and have no idea what might have changed to eliminate the functionality.

Please help if you can,

Bruce

[infobroker]

OK. I think that I can clarify what the problem is to some degree. There was nothing wrong with the Exchange server URL. In fact, there was nothing wrong with my Exchange server username. The problem is that Thunderbird or Lightning or Exchange EWS Provider used to automatically prompt me for the Microsoft Exchange EWS server password. Now, I have to change the username and change it back again to "manually" get Exchange EWS Provider to connect to my calendar information. Does anybody have any idea how to get the application to do this upon the launch of Thunderbird (again)?

Thanks in advance for any help that can be provided in this area,

Bruce

[bavincen]

Can you clean cache then try. You can find it in EWS settings

[infobroker]

That sounded like something that would work. However, it does not appear that it did. EWS Exchange Provider just doesn't want to do a password request upon the launch of Thunderbird. I can only get it to do it by going into the settings and doing a double change of the Username (a change and then back to what it should be). I can work with this annoyance, but wish I knew why it will no longer do a password request automatically at the launch of Thunderbird. It does it automatically both for incoming and outgoing emails, but not for the calendar information. :-(

[bavincen]

Your environment details?

On Tue, Jan 5, 2016, 13:32 infobroker notifications@github.com wrote:

That sounded like something that would work. However, it does not appear that it did. EWS Exchange Provider just doesn't want to do a password request upon the launch of Thunderbird. I can only get it to do it by going into the settings and doing a double change of the Username (a change and then back to what it should be). I can work with this annoyance, but wish I knew why it will no longer do a password request automatically at the launch of Thunderbird. It does it automatically both for incoming and outgoing emails, but not for the calendar information. :-(

— Reply to this email directly or view it on GitHub https://github.com/Ericsson/exchangecalendar/issues/393#issuecomment-168929726 .

[infobroker]

I have the same issue with both Windows 7 Service Pack 1 and Mac OS 10.6.8. Thus, I don't think that it has much to do with the OS. To be clear, all I really want is a way to get something to automatically prompt me for the Microsoft Exchange EWS server password every time that I launch Thunderbird. Prior to December it did so. Some application upgrade (Thunderbird, Lightning, or Exchange EWS Provider) might have broken that feature. I found a "manual" workaround, but I'm hoping someone can tell me how I might get the password request to pop up automatically upon launch again (unless this is a bug of some current version).

[andyrozman]

I use password manager "Startup Master", for handling my passwords... When my password changes I get request to enter new password. Would something like that be good enough for you?

[infobroker]

Well, it hasn't been an issue in Windows 7 recently (even though a separate password request no longer pops up). It can still be an issue in Mac OS 10.6.8, but the "manual" workaround is still working.