Problems with MLS export

natet · #11

Well, I've downloaded the 2.9.1 installer and ran it twice with no change. I'm downloading it again, because I'm that stubborn.

EDIT: Nope, no go.

aebrown · #12

natet wrote:Well, I've downloaded the 2.9.1 installer and ran it twice with no change. I'm downloading it again, because I'm that stubborn.

EDIT: Nope, no go.

In my case, I simply installed 2.9.1 on top of the previous installation and it worked. Have you tried doing an uninstall before the reinstall? I suppose that could make a difference.

If that doesn't work, you could work with your Stake Technology Specialist and hope he has some ideas; the next option is to call Clerk Support, but they won't be open again until Monday morning because of the Thanksgiving holiday.

#13

mkmurray wrote:STC? What is that? Or did you mean STS (stake technology specialist)?

I did mean STS. Sorry. The other term is one I use daily at work and means something entirely different. I will volunteer to be the turkey today. [grin]

As for the problem, I do recommend the Alan reinstall approach. After that, we once had a printing problem with MLS that was unique to our specific box. No number of wipes or installs would solve the problem. At their request, we finally shipped the box to SL. They sent us a replacement box.

The developers at CHQ soon found the problem, but it took a change to MLS to solve it. That change also had the benefit of largely solving the printing problems that plagued the early years of MLS in 2004, 2005, and 2006.

#14

lajackson wrote:I will volunteer to be the turkey today. [grin]

Yikes! Thanksgiving Day is not the day I would want to be a turkey.

russellhltn · #15

lajackson wrote:The developers at CHQ soon found the problem, but it took a change to MLS to solve it. That change also had the benefit of largely solving the printing problems that plagued the early years of MLS in 2004, 2005, and 2006.

OK, now I'm curious. What problem was it and what did they have to do to fix it?

#16

RussellHltn wrote:OK, now I'm curious. What problem was it and what did they have to do to fix it?

It was the printing problem, the one where print jobs would skip large sections of documents, or even worse, just quit printing.

In my particular case, if you clicked on any print button in MLS (and I do mean ANY print button), the computer would immediately display the desktop and there would be absolutely no evidence at all that MLS had ever been running. Zip, scratch, nada. Nothing. Over and over and over. MLS simply disappeared as if it never existed.

The crash could be duplicated repeatedly. It happened as tithing settlement was beginning in one of our units, so I wound up moving the unit data to another computer and overnighting the tithing settlement forms and reports to the branch president so he could conduct tithing settlement.

After the requisite number of help desk calls required to convince them that I was not making it up, they had me box up the computer CPU and overnight it to CHQ. They duplicated the problem (repeatedly), traced what was happening, dug into the code, and wrote a fix (as best they could) in MLS to help solve the problem.

I never got the details, but there was a time when the underlying version of Java had a problem handling print commands. It was a known Java bug that SL was having a difficult time patching around. It seems that whatever was happening with the box I sent gave them enough insight to create a mostly successful patch for the problem.

And eventually, I think, the Java bug also was fixed.

#17

Mikerowaved wrote:Yikes! Thanksgiving Day is not the day I would want to be a turkey.

I am banking on a pardon. Besides, at least in our home, I am the one holding the knife being used to carve the turkey. As long as I hold the knife, I figure I am safe. [grin]

Happy Thanksgiving everyone. And yes, I know those of you in Canada (and some places elsewhere) have already celebrated. I, for one, have been very blessed this year.