Posted: Sun Sep 28, 2008 3:36 pm
Thanks goes to the HQ staff for at least giving us an updated recording acknowledging the problem this week. But I would also like to see emails go out to the STS notifying them of the problems.
Technology Discussion forum - Technology used by members of The Church of Jesus Christ of Latter-day Saints
Yes. When the calls started coming in this afternoon, the recording was the first thing I checked. The e-mail would not really help me, since I am at Church in the afternoon.gpetersen wrote:Thanks goes to the HQ staff for at least giving us an updated recording acknowledging the problem this week. But I would also like to see emails go out to the STS notifying them of the problems.
I agree with this. I live 20 minutes each way from my meeting house, so it's not a quick trip either. It seems like these reoccurring Sunday availability problems should be a high priority for Salt Lake. Is this an issue of scaling to meet the traffic needs?lajackson wrote:Our clerks are not expected to make a special trip the meetinghouse on Mondays under any circumstances. They are to be with their families. We allow exceptions only if the meetinghouse is directly on the way to or from work for someone with S/R privileges.
I had to restart a couple of the wards' computers before the transmission finally went through (do they get locked into a particular socket?), but finally got all my wards transmitted. We're a student stake, so almost all the computers are in the same building. I do have one lingering worry - half the computers never printed out a financial transmission report after the successful transmission. I'm pretty sure this isn't the end of the world, but that means there is no confirmation or record of the batch/checks being transmitted. I did check under expenses and all the checks said "Sent", so I guess that means it transmitted successfully but I'll always wonder until the September statements come out...DJC wrote:The system is back up and functional. You should be able to transmit data as of right now. No guarantees for the future.
My personal opinion is that I'm sure this got ICS's attention when it happened two Sundays in a row now. I imagine there are putting every resource available on keeping it from happening again. Remember, that's 2 weeks in a row that Church employees probably had to travel to the office on the Sabbath to fix the problem for us.
I seriously doubt it is a scaling or any other architectural issue. I don't have any really good reasons, but it just wouldn't make sense. They've been using and monitoring these systems for years, with every Sunday being jam packed with traffic. Think of how many Sundays have gone by without a hitch (granted the actual communication may or may not have been slower, but always functional). I just imagine this being some configurational problem that is more temporal in nature than many of you are suggesting. It's probably just necessary to get to the root of the cause, which may not have been blatantly apparent last Sunday.