Tech Forum

When we do a send/receive we can see the major processes it goes through during the connection. The last is often Updating Membership and quite often this runs an awkwardly long time. I have started a send.receive before meetings and checked back after church to find it still Updating Membership (over 3 hours). A couple times I have even had to cancel the action so I could use the computer for something else. I am just wondering first if this is a common problem, and second if there is a solution?

This happens to me every once in a while. I always show the Send/Receive status (you can just hit F9 to show it) and watch the progress. Each file is processed pretty quickly. But on occasion, the dialog box that says membership data is being updated doesn't get dismissed properly. If I check the status and see that nothing is still being processed, I simply close that dialog box.

I'd say this happens to me about once every couple of months, so I see it as a mildly annoying quirk. I've never seen any problems come from closing that dialog box.

This is the first I've heard of it being that long.

I'd suggest calling Local Unit Support tomorrow. I'm concerned that the data may have corruption that could get worse if the wrong thing is done.

wrigjef wrote:When we do a send/receive we can see the major processes it goes through during the connection. The last is often Updating Membership and quite often this runs an awkwardly long time. . . .
I am just wondering first if this is a common problem, and second if there is a solution?

This happens almost every time on our stake MLS computer. Once the status line says that the Send/Receive is complete, and files are no longer being processed, we close the window. We have not had any trouble with this workaround so far.

Another workaround is to minimize the MLS window to the task bar and then expand it again. This will sometimes, but not always, clear the Updating Membership window.

We had a similar but different problem last night that I will call on later today. This time it was "Updating Callings" that seemed to be on the screen forever. I did the F9 thing and while it showed "completed" for most files, it showed "queued" for certain others. But it did not show anything as processing or give any indicator that something was happening. The files that had red indicators next to them were /cubstomls/amr and /cubstomls/luba the file that had MARCH25Error in it's name read as queued.

This is still an issue for our Stake Computer (and has been for several years). Happens every week especially if responding to the update prompt when first logged in. It has only occurred on the Updating Membership. I finally found this thread but was hopping that it would list a fix. Has there been anything done to fix this or something I need to do as Stake Technology Specialist and Stake Assistant Finance Clerk to fix it?

dongreen wrote:This is still an issue for our Stake Computer (and has been for several years). Happens every week especially if responding to the update prompt when first logged in. It has only occurred on the Updating Membership.

It still happens to us regularly, and there is no fix of which I am aware. We just use the F9 key and do not shut down until all of the files have processed.

We submitted a bug report a while ago and never got any response. Perhaps it is time to submit another one.

lajackson wrote:

dongreen wrote:This is still an issue for our Stake Computer (and has been for several years). Happens every week especially if responding to the update prompt when first logged in. It has only occurred on the Updating Membership.

It still happens to us regularly, and there is no fix of which I am aware. We just use the F9 key and do not shut down until all of the files have processed.

We submitted a bug report a while ago and never got any response. Perhaps it is time to submit another one.

If you can reproduce it consistently, I would submit another one.

scgallafent wrote:If you can reproduce it consistently, I would submit another one.

Well, we cannot reproduce it consistently. It just happens a lot, and we have not figured out a sequence of events that will cause it to happen.

And since we have such a good workaround, and there are other things higher on our wish list to be fixed in MLS, we have not worried about it much.