As we don't patch on Fridays as a rule, we are not going to post this patch until next week, but I wanted to make sure our users knew that a new version of Builder is coming very soon that solves a bunch of problems that have been reported so far.
To see the patch notes, please visit this page:
Having some problems with the new builder. First of all, I was under the impression that it would basically replace the old version. Instead, it ignored it.
But more importantly, the new version will not let me save my work. It asks me to (continually) upgrade to an activated congregational version. I have (supposedly) successfully activated our version a couple of dozen times, and it still does the same thing.
Am wondering if the presence of the old one is causing the problem. If I had my druthers, I would rather leave the old one in place for a few weeks while we learn (and get the bugs out of) this new version.
Builder 2.0 is intended to install alongside Builder 1 instead of replace it, to provide an easier upgrade path. We knew not everyone would have the time to dedicate to learning the changes in Builder 2 going into Advent, and we also wanted to make sure that if anything was working incorrectly, users would have a "fallback" option available to them.
The presence of Builder 1 is not affecting your Builder 2 installation. They are completely independent of each other.
What version of Windows is installed on that computer?
XP Home
OK; let's do this:
Search your system for a file labeled "lsb.ini." You will find two of them. (To find the second one, you may have to search hidden files and folders.)
One of them will be in this folder:
C:\Documents and Settings\All Users\Application Data\Concordia Publishing House\Lutheran Service Builder 2\
We'd like to rename that file to something else.
The next time you start Builder, it will recreate that file from scratch. You will have to re-point Builder in the direction of your SQL databases for Builder (if you need help with this, just let me know). You will then have to activate Builder one more time.
After this activation, you should not see the activation prompt again. If you do, please let me know and we'll take some additional steps to solve the problem.
Ryan - Your advice seemed complicated, so I called support to have them help me walk through it. They had a different suggestion, and their advice worked.
Evidently, there were some incorrect unlock codes in the activation (and 'N' instead of an 'M'). Once we got that straightened out, everything now works fine.
Except for one thing. I had put people on this before, as Builder 1 did the same thing. I save the document as a Word document. But after I go to Microsoft Word and open the document up, it recognizes it and wants to save it as an RTF extension, not a DOC. It is an easy enough thing to fix, but it is an annoying extra step, that sadly has made its way also into version 2.
But thanx for your help. New version looks QUITE good.
You must log in to post.
