Repeated system clock failures while inputting tithing batch

Discussions around using and interfacing with the Church MLS program.
mfunk179
New Member
Posts: 1
Joined: Sun Jul 06, 2014 3:53 pm

Repeated system clock failures while inputting tithing batch

Postby mfunk179 » Sun Jul 06, 2014 4:17 pm

I could sure use some help on a very frustrating problem. About three or four months ago our ward got a new desktop computer; at or about the same time, we began to see error messages while entering tithing on Sunday afternoons.

What seems to happen is that at some point during batch entry, the system stops recording donations as they're being made. The user can't visually detect any problem until we try to print the reports and transmit the batch. Only then do we realize that the last 60 or 70 transactions are just...gone.

About then an MLS error message pops up that says that MLS has detected a change to the system clock, and MLS should be restarted....

Problem is, we haven't changed the system clock, and in fact the clock is displaying the correct date and time.

Ultimately, we have to re-enter the whole batch, which is extremely frustrating. After the error today, we had to sedate the finance clerk; I was afraid he was going to stroke out.


Anyway, I could really use a solution. Any help would be deeply appreciated.

russellhltn
Community Administrator
Posts: 23022
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: Repeated system clock failures while inputting tithing b

Postby russellhltn » Sun Jul 06, 2014 5:46 pm

Just a thought - you might want to make sure you re-start MLS before doing a batch. My thought is that if the computer goes to sleep while MLS is running, at some point MLS may see the clock "jump" and not like that. By restarting MLS before doing the batch, I think you'd avoid having a "sleep memory loss".
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

jirp
Member
Posts: 167
Joined: Thu Feb 21, 2013 8:02 pm
Location: Greybull WY

Re: Repeated system clock failures while inputting tithing b

Postby jirp » Sun Jul 06, 2014 7:21 pm

At some point you are leaving MLS running to long without doing anything. I have never gotten that message if I don't leave MLS running without taking any action. I had guessed it was a way for the programmers to protect against people leaving it open with no one attending it and that it actually had nothing to do with the system clock.(I might be wrong on this) Russel's suggestion of restarting MLS just before you actually begin entering the tithing should solve it.(don't do it until you are actually ready to enter the tithing.)

If that doesn't do it another possible that might help is open another tab in MLS temporarily while entering tithing and do something else in MLS like look up a name in the middle of what you are doing so the program knows you are present. You have to change the tabs for MLS to detect you are doing something and tithing entry might not be doing it so opening another tab should do it.

If he is right and it is computer sleep time you might try going to control panel --> system and security --> power options and change the screen saver and sleep times upward to longer than it takes you to do tithing. Depending on your systems admin security you may have to have your stake technology specialist make this change.

rontilby
Member
Posts: 135
Joined: Mon Apr 20, 2009 7:22 pm
Location: Salt Lake City, UT, USA

Re: Repeated system clock failures while inputting tithing b

Postby rontilby » Mon Jul 07, 2014 11:39 am

Windows is usually configured to automatically synchronize the pc clock to "internet time" on a scheduled basis. It may be that Windows is syncing the pc's clock to internet time every Sunday during the time you're entering donations. This would cause MLS to complain that the clock has "changed".
You could try this:
Exit MLS
Set the Windows system clock to the proper time zone and synchronize with an Internet time server and "Update Now".
Start MLS
Enter the donation batch.

User avatar
Biggles
Senior Member
Posts: 1066
Joined: Tue May 27, 2008 4:14 am
Location: Watford, England

Re: Repeated system clock failures while inputting tithing b

Postby Biggles » Mon Jul 07, 2014 11:56 am

rontilby wrote:Windows is usually configured to automatically synchronize the pc clock to "internet time" on a scheduled basis. It may be that Windows is syncing the pc's clock to internet time every Sunday during the time you're entering donations. This would cause MLS to complain that the clock has "changed".
You could try this:
Exit MLS
Set the Windows system clock to the proper time zone and synchronize with an Internet time server and "Update Now".
Start MLS
Enter the donation batch.

The procedure for setting the time as mentioned, unfortunately wont work on a Clerk computer that has the mandatory Church (TEM) management software installed. TEM locks out the date, time and zone settings. This, for none techy persons, requires the GSC to remotely adjust.

From my own experience, the MLS computers doesn't time sync via the internet.

brtwitchell
New Member
Posts: 1
Joined: Sun Dec 03, 2017 12:46 pm

Re: Repeated system clock failures while inputting tithing batch

Postby brtwitchell » Thu Dec 14, 2017 3:54 pm

I know this is an old thread but apparently this is still an issue. This has happened to me the last two weeks while I was doing tithing settlement (finance clerk). We have been keeping our batch open until tithing settlement is over, and the computer goes to sleep when you are away for a bit i.e. waiting for any more donations. At the end when I go to finish the batch I get the error saying "your system clock has changed", at this point the only thing I could do is restart MLS and open my "open batch" and then finish it. Some donations/expenses have to be redone and this is very frustrating, but at least I have been able to open the open batch and not redo the whole thing.

I would think a solution could be found to resolve this issue now that is has been happening for years. At least give us a recommendation about how to process long batches i.e. tithing settlement without the computer going to sleep.

PLEASE and thanks!

User avatar
Biggles
Senior Member
Posts: 1066
Joined: Tue May 27, 2008 4:14 am
Location: Watford, England

Re: Repeated system clock failures while inputting tithing batch

Postby Biggles » Thu Dec 14, 2017 4:42 pm

The simplest solution is to prevent the computer from going to sleep. With the help of your STS, set the power setting to never sleep, or perhaps 5 hours as a minimum!

russellhltn
Community Administrator
Posts: 23022
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: Repeated system clock failures while inputting tithing batch

Postby russellhltn » Thu Dec 14, 2017 4:44 pm

Biggles wrote:With the help of your STS, set the power setting to never sleep, or perhaps 5 hours as a minimum!

I'd avoid "never sleep" as someone may leave the machine running all week in a hot building. That's a good way to cook a machine. I'd suggest having it not go to sleep for several hours. Something short enough that it will sleep if everyone goes home, but not so short that it will be asleep after a short meeting.
Have you searched the Wiki?

Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.


Return to “MLS Support, Help, and Feedback”

Who is online

Users browsing this forum: No registered users and 1 guest