Page 1 of 2

MLS unable to send/receive

Posted: Tue Jul 09, 2013 1:54 pm
by ajthomas
Our MLS developed a database error and we were unable to login. After searching the forum, the solution seemed to be to remove MLS, reinstall, and restore from a backup. That I did, and it worked fine. MLS is up and running again. Well, almost. The problem is that the finance functionality is locked until we do a send/receive, and that doesn't work. We get the "Error 2 Unauthorized" message indicating a need to have some security setting reset. The problem I have is that our stake clerk, who functions as the technology specialist, and who as I understand is the only one who can request that, seems to be on vacation and I can't reach him. We have a huge pile of donations from Sunday waiting to be processed. Is there any way I can get this to work without waiting for the stake clerk to come back?

Re: MLS unable to send/receive

Posted: Tue Jul 09, 2013 1:58 pm
by russellhltn
Call Local Unit Support and explain the situation.

Re: MLS unable to send/receive

Posted: Wed Jul 10, 2013 5:09 pm
by sbradshaw
Yes, you will need to call Local Unit Support and tell them you need them to reset the security token. Have your ward unit number handy (the 5 or 6 digit identifier for your ward – it's next to the ward name on most things printed from MLS and can also be found on CDOL).

The system is set up to make sure MLS isn't installed on more than one computer at a time, similar to the registration/licensing process for other software. Every time MLS is installed, reinstalled, or transferred to a new computer the security token needs to be reset.

One thing to note is that Local Unit Support is not open on Sundays – you'll need to call them during the week. You don't need to be at your computer for them to reset the token, you just need to call and have your unit number handy to give them, and the next time you're at your computer Send and Receive Changes should work as expected.

Re: MLS unable to send/receive

Posted: Wed Jul 10, 2013 6:41 pm
by ajthomas
I hesitated to call LUS because the website where I found the phone number makes it pretty clear that only technology specialists, facilities, and a few others are allowed to contact them, and I was left with the impression they wouldn't talk to me as a clerk. Well, they did; problem solved.

Re: MLS unable to send/receive

Posted: Wed Jul 10, 2013 7:24 pm
by lajackson
ajthomas wrote:I was left with the impression they wouldn't talk to me as a clerk. Well, they did; problem solved.
This was a case where the stake clerk or technology specialist was not available, and it was perfectly appropriate for you, as a ward clerk, to make the call, explain the situation, and have LUS help you.

All unit numbers are not 5 or 6 digits, by the way. Some very old wards and branches have 3- or 4-digit numbers, and the newest units have 7. sbradshaw has probably not run into that, yet. [grin]

Re: MLS unable to send/receive

Posted: Wed Jul 10, 2013 9:02 pm
by sbradshaw
Nope, I haven't seen that yet :)
So is unit "1" the first ward created?

I looked for the page about Local Unit Support to read the wording (ajthomas said it sounded like not everyone should call) and found this:
https://www.lds.org/callings/melchizede ... t?lang=eng

It has the same phone number and email as Local Unit Support – but with a different name: "Member, Leader, and Unit (MLU) Support." It seems like they're redefining their scope. Is "Local Unit Support" still the proper name? Anybody know about the reason behind the change?

Re: MLS unable to send/receive

Posted: Thu Jul 11, 2013 9:02 am
by lajackson
sbradshaw wrote:Nope, I haven't seen that yet :)
So is unit "1" the first ward created?
I don't know. I lived in unit 469 for a long time (it had a different name back then). I now live in a 7-digit stake and a 5-digit ward. We share the meetinghouse with a 7-digit ward and a 6-digit ward. You used to be able to tell from the unit number if a unit was a ward/branch or a stake. With the growth of the Church, new units now have 7-digit numbers, and I cannot tell if there is a pattern.

Re: MLS unable to send/receive

Posted: Thu Jul 11, 2013 9:19 am
by jonesrk
There are a few 2-digit unit numbers also (very old units). Now all new units have 7-digits. They are now generated from the same source and the unit type doesn't affect it anymore. Instead the numbers are now somewhat sequential.

Re: MLS unable to send/receive

Posted: Thu Jul 11, 2013 2:11 pm
by ajthomas
sbradshaw wrote:Nope, I haven't seen that yet :)
So is unit "1" the first ward created?

I looked for the page about Local Unit Support to read the wording (ajthomas said it sounded like not everyone should call) and found this:
https://www.lds.org/callings/melchizede ... t?lang=eng

It has the same phone number and email as Local Unit Support – but with a different name: "Member, Leader, and Unit (MLU) Support." It seems like they're redefining their scope. Is "Local Unit Support" still the proper name? Anybody know about the reason behind the change?
Actually, the page I found was this one, which says:
Only technology specialists, physical facilities representatives, facilities management groups, and area offices are authorized to contact IT Support. All other individuals should contact their stake or district technology specialist for assistance with meetinghouse technology.
Regarding unit numbers, my unit is actually one of the old ones with a 4-digit number. It was established in the late 1800's if I recall correctly (not that I was around at the time, of course).

Re: MLS unable to send/receive

Posted: Thu Jul 11, 2013 2:32 pm
by russellhltn
ajthomas wrote:Actually, the page I found was this one, which says:
Only technology specialists, physical facilities representatives, facilities management groups, and area offices are authorized to contact IT Support. All other individuals should contact their stake or district technology specialist for assistance with meetinghouse technology.
I'd agree with that for an initial contact about a problem. But there have been cases where a ward contacted me (as a STS) and I've told them that for that particular problem (data corruption), there wasn't anything I could do and to contact IT Support and let me know the outcome. I also said to tell them that they had called me first.

I've never had a problem with that arrangement.