Tech Forum

Earlier this week we discovered that Send/Receive is giving us the following Error:

An error occurred while transmitting. Contact your stake clerk if you are unable to transmit after multiple multiple attempts. The stake clerk should contact support if he needs assistance to resolve transmission problems. Error 2 "Unauthorized"

Our Stake Clerk has contacted the stake technology specialist, and he is contacting MLS support, but I thought I'd see if the community had an answer. In a few hours we'll be doing donations, and would love to resolve this issue quickly.

That is the standard transmission security error. It typically occurs when MLS has been installed on a new machine, but you have not yet contacted Local Unit Support to request a "security reset." Since LUS is not open on Sunday, your simplest option will be to wait until Monday and make that call, then transmit.

There are other possibilities if your previous computer is still available, but they require careful technical steps.

And if you aren't using a new MLS installation, then this is a bit more mysterious and it would be helpful if you could shed any light on why MLS might think it is now running on a different machine from the last time a successful transmission was made.

Thanks so much for your quick response . . . It looks like the plot thickens, we are using an existing machine and installation of MLS. As far as I can tell, nothing has changed on our network, the internet connection is still the same and currently functioning.

This past wednesday evening the Bishop was closing out tithing settlement, He said it started acting weird and was not positive that it completed the send receive. For some reason he was concerned we might need to restore from a backup, however we are not sure exactly what the messages were that he was getting.

Since that incident, we are unable to send/receive --- The Clerk say as he browses MLS, everything looks in order, it just gives us that error each time.

"There are other possibilities if your previous computer is still available, but they require careful technical steps."

can you shed any more details on this process?

It would be nice if we could sign in like we can on TM with the routers to reset our own security. It is very frustrating to have driven an hour to a unit on MY Saturday and not be able to get any support.

miken2av wrote:"There are other possibilities if your previous computer is still available, but they require careful technical steps."

can you shed any more details on this process?

The process involves copying certain folders from the old computer to the new computer. At this Wiki page, the beginning of the Clean Installation procedures show which folders and files are involved. See step 2 under Preparation.

Note that these instructions are old, that on newer installations of MLS the file paths may have changed, and that even this procedure is not always reliable in avoiding the need for a reset.

Need help with the following . An error occurred while transmitting. Contact your stake clerk if you are unable to transmit after multiple attempts. The stake clerk should contact support if he needs assistance to resolve transmission problems. Error 2 "Unauthorized" Please help. Can't get Stake Clerks number or contact.

AundreHSaunders wrote:Error 2 "Unauthorized"

You'll probably have to contact church support. That usually happens when changing computers, or doing something to the MLS software.

We just had this happen to us today in our stake (Layton South Stake). I contacted the Global Support Center and was told that it is a known issue system wide. I was told today to just have the ward make the deposit and to try to submit the batch at a later date. They should make a back-up like they normally should each week as well.

jendeano_12 wrote:We just had this happen to us today in our stake (Layton South Stake). I contacted the Global Support Center and was told that it is a known issue system wide. I was told today to just have the ward make the deposit and to try to submit the batch at a later date. They should make a back-up like they normally should each week as well.

This is the correct and current response, especially considering how many times this post has been viewed so far today (over 1,500+)

ashtonhsmith wrote:This is the correct and current response, especially considering how many times this post has been viewed so far today (over 1,500+)

That's not today's count. This thread is 5 years old.