As I read through this post and based on the experience our Stake is having, here are some common points.
The issue cropped up between Sept. 20th and Sept. 22nd.
The issue most often affects the "Stake" calendar.
Many users have posted that the issue affects the months Oct., Nov., Dec.
This is the body of an email I sent to our SES.
This is the testing I have performed with Internet Explorer 8. (I will have to test other browsers later.) I am attaching the error that I get.
I subscribed to the "Stake" calendar. I recieved an error on the following months.
January 2011
February 2011
April 2011
May 2011
October 2011
November 2011
December 2011
I changed my view from "Month" to "Week." I received an error on the following weeks and most of them would not load.
Jan 2 - 8 (one error, but it loaded anyway)
Jan 16 - 22 (one error)
Jan 23 - 29 (one error)
Jan 30 - Feb 5 (one error)
Feb 6 - 12 (one error, but it loaded anyway)
Apr 3 - 9 (two errors)
Apr 10-16 (one error)
Apr 24 - 30 (one error)
May 1 - 7 (two errors)
May 8 - 14 (one error)
Oct 2 - 11 (one error, but it loaded anyway)
Oct 23 - 29 (one error)
Oct 30 - Nov 5 (one error)
Nov 6 - 12 (two errors)
Nov 20 - 26 (one error)
Nov 27 - Dec 3 (one error)
Dec 4 - 10 (two errors)
Dec 11 - 17 (one error)
Dec 18 - 24 (one error)
Dec 25 - 31 (one error)
I un-subscribed from the "Stake" calendar and re-checked the above weeks. Here are the weeks that still posted errors.
Dec 4 - 10 (one error, but it loaded anyway)
Dec 25 - 31 (one error)
I un-subcribed from the ward calendar named "Primary" and the former two weeks no longer presented an error.
I re-subscribed to the "Stake" calendar and re-tested the former two weeks and got errors.
Dec 4 - 10 (two errors)
Dec 25 - 31 (one error)
With that information, I am lead to believe that there is an event on the "Stake" calendar during each of the weeks listed first that have something triggering the error. The weeks that pop the error, but still load seem to be the first week selected in a month that has errors. The weeks that pop two errors seem to be the weeks that have errors and be the first week selected in a month that has errors.
Now, that we know what weeks are erroring out. The next step is to figure out which events are generating the error, that may prove to be tricky since we can't get to them. Then find out why. Then apply changes to resolve the error.
I am curious if the results would be the similar if the same tests were performed from a different ward or user.
I will report my findings to the forum and see if anyone has other ideas.
I will keep you posted.
The error also appears when I check the subscribed location "Events without Locations."
I subscribed to the two calendars that are presenting the error, and tried to download the .csv to see if the issue was related to the presentation of the data on the webpage, but I got the 500 error, that has been previously reported. My thought was that there may be some unique character that is triggering the issue, like a single quote/apostraphe ('), or double quote("), etc... so we can give the development team something specific to look for.
The only way for me to get by the error is to not subscribed to the "Stake" calendar, or the "Primary" calendar. This isn't really a workaround, as there is no way for me to get that data electronically. Yes, I know there was life before electronics and we will survive.
I hope the development team is able to find the issue soon and resolve it quickly.