The event at 2pm is the key. The unit is still running 3.1.5 at that moment, and due to a bug in 3.1.5 it is filling up the mlslog.txt file. When you later attempt to do another transmission, the log file is so large that it cannot be effectively transmitted and so the transmission fails.
Deleting or renaming the mlslog.txt file will solve the problem. With potentially limited space on hard drives, deleting the file may be the better option.
MLS 3.2.0 (the version being downloaded to the units), is immune to the problem. Unfortunately, the problem is in MLS 3.1.5 and appears to be happening as people continue to use MLS after receiving MLS 3.2 but before completing the upgrade process.
Best suggestion for anyone who hasn't yet upgraded to MLS 3.2: Reboot immediately after receiving the update. Don't wait, don't do other MLS work. Just take care of the reboot and things should be fine after that.
One complicating factor: MLS 3.1.x had reliability issues with showing the reboot dialog. So you may not realize you have received MLS 3.2 unless you were watching the status bar.
We're having the same problem... Here's the history of what happened:
- 10:30 am - Membership clerk transmits membership updates, MLS 3.2 starts downloading
- 10:55 am - download finishes
- 11:00 am - 12 noon - various people use the computer for reports and other duties, the computer is never rebooted (I'm guessing that someone saw the message to reboot the computer to apply the update, but they must have forgotten to reboot)
- 12:20 pm - we start doing a donation batch
- 1:20 pm - we transmit the donation batch, finance transmission report prints
- 1:30 pm - I start entering in expenses to write some checks
- 2:00 pm - when I click the "Print Checks" button, javaw.exe pegs processor 100% for 3 + minutes, I do a "force quit" on the .exe file via task manager and reboot the machine
- 2:05 pm - I start MLS after a reboot and it finishes applying the update
- 2:06 pm - 3:00 pm - I'm able to print the checks (23 of them), but I can't successfully transmit... when I click send/receive, it dials the number (we are on dial-up) and then it never gives me a progress bar or anything letting me know it is transmitting...
- 3:00 pm - I lock the office and put a note on the computer: "Please let the computer finish transmitting" and I go home.
- 7:00 pm - I return to the church to see if it finished transmitting... the modem had disconnected but the expenses were still "Not Sent" on the "View/Update Expenses" screen. I try transmitting again and it doesn't work (it dials, connects, and then sits).
Anyhow, I'm about to call CHQ to let them know about these 23 checks that we wrote yesterday. I'm sure enough of us will be manually calling in new expenses that they'll realize something isn't right.