My calendar is asking for Google password but not accepting it
It just happened now, out of the blue. My email accounts work well but my calendars keep popping up asking me for my Google password but they don't accept it. I use Thunderbird version 31.2.0, Lightning 3.3.1 and Provider for Google Calendar 0.32 (the latest version doesn't work at all)
Избрано решение
I have the same problem. Last month i did the fix (desinstalled provider and lightening and relinked agenda to google calendar and disabled the autoupdate)
Since then everything worked and i did not touch anything. Nevertheless all of a sudden, agenda started to ask for my password but don't accept it and then says that an error has occured while preparing the agenda which won't be available.
[Exception... "[xpconnect wrapped nsIURI]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/C%C3%A9cile/AppData/Roaming/Thunderbird/Profiles/k9ktyvla.default/extensions/%7Ba62ef8ec-5fdc-40c2-873c-223b8a6925cc%7D/js/calGoogleCalendar.js ::
And indeed, its impossible to check the agendas boxes
Всички отговори (2)
Избрано решение
I have the same problem. Last month i did the fix (desinstalled provider and lightening and relinked agenda to google calendar and disabled the autoupdate)
Since then everything worked and i did not touch anything. Nevertheless all of a sudden, agenda started to ask for my password but don't accept it and then says that an error has occured while preparing the agenda which won't be available.
[Exception... "[xpconnect wrapped nsIURI]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/C%C3%A9cile/AppData/Roaming/Thunderbird/Profiles/k9ktyvla.default/extensions/%7Ba62ef8ec-5fdc-40c2-873c-223b8a6925cc%7D/js/calGoogleCalendar.js ::
And indeed, its impossible to check the agendas boxes
I just saw that there is a new version (1.0.2) of Provider for Google Calendar. I installed it and the problem was gone. Prior to that, with version 1.0.1, I was having also issues so I rolled back to the one before. I suppose that every time there is a new version it affects my existing working platform, even though my auto update is set to "off"