Page 1 of 1

Problem with CUBS and MLS?

Posted: Mon Oct 25, 2010 4:19 pm
by edwardlalone
Here is the situation:

Prior to receiving CUBS our computer's date was changed to the future. We did not notice this problem for some time and were processing transactions during this time. We did not have this problem corrected by the time that CUBS was downloaded on our computer so we will need to change the system clock back.

Doing so would lock us out of MLS unless we restore from a backup. Prior to CUBS installation it was acceptable to restore from a backup and to reenter information from prior dates.

After thinking about it I feel this may or may not pose a problem but if we were to restore to a backup prior to CUBS being installed would it uninstall CUBS? If so, how would we reinstall cubs without using a backup that isn't correct.

We were planning on trying to correct this problem Wednesday.

Can someone please provide a clear list of instructions on how to correct the date and have MLS and CUBS reflect accurate transaction information.

Posted: Mon Oct 25, 2010 4:25 pm
by aebrown
Edward Lalone wrote:Can someone please provide a clear list of instructions on how to correct the time and have MLS and CUBS reflect accurate transaction information.
The first question is: how far in the future was the clock set? If it's not too far in the future, then the easiest way is to stop using MLS, wait until the real time catches up with the computer time, set the clock back to the real time, and then you can use MLS again.

But if that's impractical, you'll have to restore a backup from before the time was set back. Detailed instructions are on the wiki under Changing the system date. But because the system date was advanced prior to the CUBS conversion, you'll have to contact Local Unit Support to ask them to trigger the resending of the CUBS update file.

Posted: Mon Oct 25, 2010 4:45 pm
by edwardlalone
Alan_Brown wrote:The first question is: how far in the future was the clock set? If it's not too far in the future, then the easiest way is to stop using MLS, wait until the real time catches up with the computer time, set the clock back to the real time, and then you can use MLS again.
It was November 17th.
But if that's impractical, you'll have to restore a backup from before the time was set back. Detailed instructions are on the wiki under Changing the system date. But because the system date was advanced prior to the CUBS conversion, you'll have to contact Local Unit Support to ask them to trigger the resending of the CUBS update file.
We already have those instructions and would be able to use them but we would like to avoid confusion and mistakes as we correct this problem. Here are a few questions:

1. With the computer clock still in the future so MLS will run, print a copy of recent deposits and other changes that may have been made.

Which reports would we need to print to be most efficient? Would we need to print a copy of membership transactions or just financial transactions?

2. Find the most recent backup that is dated before the present

Does this have to be the most recent backup that was correct or the most recent backup? For example, this Sunday we entered donations and printed checks even though the date was incorrect? Would this be the backup we need to restore to or should we restore to the most recent backup where we have the correct date.

3. Turn the computer clock to the present
4. Restore your MLS data from the backup
5. Re-enter all deposit and other information.

Another question our Stake Clerk had was if we would need to change the time back to each donation/expense date when re-entering all deposits and other information (other information isn't quite clear) or if reverting it back to the last date that was correct would be sufficient.

One final question would be. If we need to re-enter check information. How would we re-enter it without reprinting the check. Should we change the check # to the correct check # and then print it on a blank piece of paper?

Any clarification would be useful.

Thanks for being so helpful. While the information you gave us is what we already knew we had to do it does validate what we already knew it's good to have it validated by someone with your experience.

What we didn't know was that we would need to re-send CUBS. That's good to know.

Posted: Mon Oct 25, 2010 7:16 pm
by crislapi
Edward Lalone wrote:Which reports would we need to print to be most efficient? Would we need to print a copy of membership transactions or just financial transactions?
I would think view/update expenses (detail), view/update donations (default), members moved in & members moved out. Yes, the restore will affect membership as well as financial
Edward Lalone wrote:Does this have to be the most recent backup that was correct or the most recent backup? For example, this Sunday we entered donations and printed checks even though the date was incorrect? Would this be the backup we need to restore to or should we restore to the most recent backup where we have the correct date.
I gather the only issue was system time, correct? No other issues? I would think you shouldn't have to go back to when the date was correct then.

MLS does not let you log in with a system time/date prior to the last login time stamp. The last login information is included in the backup. If on Sunday while entering donations your system clock said November 17th, then if you restore w/ that backup, it will not let you log in again until the system time is later than Nov 17th (time included as well obviously, not just date).

I would say pick a time you will next be using MLS and find the backup closest to this date (just slightly prior). Set the system clock to that date/time and restore. Log out, correct the system date and time, and don't log in until that date/time arrives.
Edward Lalone wrote:3. Turn the computer clock to the present
4. Restore your MLS data from the backup
5. Re-enter all deposit and other information.
You can not restore from a "future" backup. System time must be at or beyond the date of the backup you are restoring from. Therefore, if you are going to restore to current date, the backup you use must be dated on or before current date/time.

If you want to use a future back-up (minimize the data you'll have to re-enter), set your clock to just beyond the date/time of the back up you want to use. I'd suggest next Saturday, perhaps (if that gains you anything). Restore, log off, correct the time and then wait until that date/time arrives before logging in to re-enter the lost data.
Edward Lalone wrote:Another question our Stake Clerk had was if we would need to change the time back to each donation/expense date when re-entering all deposits and other information (other information isn't quite clear) or if reverting it back to the last date that was correct would be sufficient.
Do NOT mess with the clock again!!! Assuming you transmitted the expenses already, there is no need to re-transmit. I would suggest using the "Not an check" option when entering them to get the date correct. Because they are not checks, they won't transmit again and you won't have to re-print either.
Edward Lalone wrote:One final question would be. If we need to re-enter check information. How would we re-enter it without reprinting the check. Should we change the check # to the correct check # and then print it on a blank piece of paper?
See above. If you do decide to re-enter them as checks, yes, you would need to print them on blank paper (not checks). You may have to print them one at a time to get the check number correct for each one, too. Again, I see no need to do this if you already transmitted the checks.

Posted: Tue Oct 26, 2010 8:17 am
by jonesrk
Edward Lalone wrote:It was November 17th.
Another option would be to set the date back some each time before MLS is run. It would take some time to get it back to the correct date but might be preferable to trying to restore and cleanup. Just another option.

Posted: Wed Oct 27, 2010 10:54 pm
by waynecooke
We had a similar problem a couple of years ago with the computer date, and moving it back a little each transmission work great. Took some time, and you had to be on top of it, and everyone involved had to know what was happening, but it worked. Good luck.:o