kotarokun wrote:The three wards with problems all recently got new computers. Our stake technology specialist set up the computers with the ward clerk logins not having administrator rights, which according to him was per the directions given him from the Church. (I didn't see the instructions myself, but I assume he's correct.) It appears that the lack of admin rights blocked MLS from updating to the 3.8 release; I had to log in with the stake administrator password and do the update manually.
So, my best guess is that the failure mechanism was that as part of the upgrade process, some script or something was supposed to grab a snapshot of the MLS information and transfer that to LCR, but when the upgrade failed, the transfer to LCR also failed. And the later manual upgrade apparently didn't kick off the "transfer to LCR" script.
That is correct. The functionality that transferred HT/VT data from MLS to headquarters required MLS 3.8. If MLS was still on 3.7.4, your data never got sent. If MLS wasn't running with admin rights, that would also have caused problems because of the way the export module was transferred to the clerk computers.
kotarokun wrote:Anyway, the data all still exists in MLS, and clearly a mechanism of transferring the data from MLS to LCR exists, but it's not clear whether the triggering of that mechanism was a one-time "if it doesn't work now it will be broken for time and all eternity" thing, or whether there is some way to kick off the script (or whatever it is) again manually, and I just have yet to find the person who knows the magic to make that happen.
It wasn't a one-time "if it doesn't work now" thing, but the update function disabled itself on July 15. There would be quite a bit of manual intervention involved at this point to run a data transfer.
I see three wards in your stake that only have data going back the last two months. I'm assuming those were the three affected. If the data was transferred to headquarters, we would have to purge the data they have entered so that we could run the import script. At this point, it's probably better for them to just plow forward.