kc4rzw wrote:We had quite a scare last Sunday, our Stake Technology specialist came by and told us not to transmit, the 2.9 download had caused every MLS in the stake to crash. Fortunately we did not have our computer setup so that the downloads can be updated by windows, we have to have admin login to update so we go through OK but the stake tech spec admin had a list of comptuers to fix that was lengthy. So what is the problem with downloading the 2.9? Didn't seem like we got any warning to be prepared to download it. I'm holding off until I get a clear go ahead to update to 2.9.
MLS 2.9 should only have been downloaded to stakes that participate in the MLS beta testing program. Is your stake a participant? We have had some other reports where people initially were surprised that MLS 2.9 was downloaded, but then they found out that their stake was indeed a beta site.
Our stake does participate in the beta program, and all the wards, as well as the stake computer, updated to MLS 2.9 with no problem on Sunday. Other participants on this forum have reported that they upgraded to MLS 2.9 as well. Yours is the first report of any problem.
I'm having some difficulty understanding what you mean by "Fortunately we did not have our computer setup so that the downloads can be updated by windows, we have to have admin login to update so we go through OK..." All ward/stake administrative computers are required to use the clerk login, which has Windows administrator privileges. Are you saying that you do not
use that login? If so, that could be a source of the problem.
If your stake has failed to follow the clear instructions for configuring administrative computers, then it's not surprising that a software update would cause problems. Although we've heard many concerns about the requirement to run MLS under an administrator account (and I share some of those concerns), it is still a fact that we are presently required to run MLS using the specified account. Many people have inferred (and it makes sense to me) that one of the major reasons for this requirement is to facilitate software updates, which is precisely what happened on Sunday. If I have misunderstood your statement, and you are running MLS using the required Windows user account, then please help us understand more details as to what your configuration is like, what the sequence of events was, and what you mean by "crash."
As for the lack of warning, I do feel your pain. I do not understand why the Church would fail to give any notification to the beta sites that this update was coming. Yesterday I sent a strongly worded message to Clerk Support requesting that the MLS product team would start running a more professional beta program.