Calendar has stopped displaying in Lightning
This morning I switched to my calendar in Thunderbird to see today's meetings, and lo and behold, none of my Exchange calendar meetings are shown in Lightning anymore.
Fedora 14 32 bit
Thunderbird 3.1.11
Lightning 1.0b2
I had not installed or updated anything (to my knowledge) to cause the change (in fact Thunderbird was still open from the day before), but I uninstalled Provider for MS Exchange 0.15 and installed 0.16 anyway, to no avail.
Tried reloading the remote calendars. That didn't work although it did make my Google calendar disappear. Restarted Thunderbird and the Google calendar was back but the Exchange calendar was still missing.
Tried deleting the Exchange calendar and re-adding. This also did not work.
Have tried both methods of Calendar location:
https://<ADdomain>
https://<ADdomain>
Interesting to note that the second method asks for my password but the first does not. Both say they have successfully created the calendar but nothing is ever populated.
If I create an event in that calendar in Lightning and then switch over to my Windows box, I can see the event has been added to my Outlook calendar. I'm able to see any new events that I create after connecting to the Exchange server, but cannot retrieve anything from the server itself. No meeting invites that I accept are added to my Lightning calendar, but they are accepted and display in Outlook on my Windows box.
Any help would be greatly appreciated. It was awesome to be able to see all my meetings from within Thunderbird and not have to switch from my Linux box to my Windows box several times a day just to keep up to date with meetings, or worse yet, rely on the dreaded webmail version of Outlook.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Related bugs
Related FAQ:
None Link to a FAQ
Revision history for this message
|
#1 |
Just did a little more digging, and found something even stranger. There seems to be a 2 week gap where I'm not seeing any Exchange calendar data. If i go to the week of August 7-13, I am able to see Exchange calendar data. If I go back to July 17-23, I am also able to see Exchange calendar data.
However, there is no Exchange calendar data for July 24-30 and July 31 - Aug 6, but there ARE meetings on the server during those two weeks. When I switch over to Outlook I can see them in there.
I don't know if this helps or makes it more confusing. I am now thoroughly confused.
Revision history for this message
|
#2 |
Hi Kate,
I love a good puzzle. I suspect that there are some calendar entries that make the plugin fall on its face.
Could you please capture the debug output as described in the wiki and post it here? Make sure to obscure all data you don't want to have publicly on the internet. Please capture the debug output when the calendar doesn't show anything.
Revision history for this message
|
#3 |
Holy cow, there's a lot of information in there. I'm not sure how much you want/need, so I'll start with this. I have the entire output saved in a text file so let me know if you need more.
This occurs right underneath the debug output for the autodiscovery and login to the Exchange server. There's more after this if you need it. I wasn't sure how much you needed.
Oh and a side note - I don't know if this helps or not - recurring appointments that started before the two week gap and end after the two week gap are displaying before and after the gap, but not inside. There's one every Thursday, so it displays for July 21, NOT for July 28 or Aug 4, but displays again for Aug 11.
Here is some of the output (let me know if this is not sufficient):
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
getInterfaces called
9c686af6-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
making prompt: true
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
9c686af6-
<s:Header>
<h:
</s:Header>
<s:Body xmlns:xsi="http://
<m:
<
<
</m:
</s:Body>
</s:Envelope>
Revision history for this message
|
#4 |
I'll need the big bulk of data that follows. You can also mail it to me at 2@0x2c.org. Please follow up on the newly created bug report, because this is clearly a bug.
Revision history for this message
|
#5 |
I emailed you the full debug output to the address you provided. Let me know if you need me to resend it. Thanks!
Can you help with this problem?
Provide an answer of your own, or ask Kate Sowa for more information if necessary.