Lutjens
Member
OK - I'm sure its somewhere, I just can't find it.
Is there an official or actual release date for a non-beta Builder 2.x? Will our old builder automatically update a patch, or will we need to install a separate program and transfer notes back and forth?
I'm eager to use it, and find all sorts of new bugs to point out! :)
Right now, Builder 2.0 is tentatively scheduled for November 10 as a final download release (the official release date is "late this year" or "when it's ready").
This is of course contingent on testing being a-OK and that bugs have been caught and squished to our satisfaction.
Builder 2 isn't an automatic update to Builder 1; you'll have to come to the Builder Web site and download it of your own accord. It will not overwrite your Builder 1 installation, but will instead install alongside it as a separate program. It *will* initiate a one-time transfer of your saved information from Builder 1 to Builder 2 when you install it.
I'm planning on editing the FAQ today to include some of this information as well.
pastorjoel
Member
After installing 2.0 ver .....20 when I click start icon it loads about 80% of files and quits. I've tried installing it twice as a clean install. Still does the same thing. It won't load up. Here is the lsb.log file. Any help?
=============================================
Executed: Lutheran Service Builder 2 2.0.20.27239
Date: 10/23/2008 5:01:01 PM (Pacific Daylight Time)
Platform: Microsoft Windows NT 5.1.2600 Service Pack 3 .NET 2.0.50727.3053
Licenses: Congregation
=============================================
Content TypesCreate: creating "ContentTypes"...
Content Types.AssertSchema: Invalid object name 'ContentTypes'.
CommandText: SELECT [id], [created3], [createdBy], [modified3], [modifiedBy], [name], [supportedFormats] FROM [ContentTypes]
LSB.App.OnStartup: Invalid object name 'ContentTypes'.
at System.Data.SqlClient.SqlConnection.OnError
at System.Data.SqlClient.SqlInternalConnection.OnError
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning
at System.Data.SqlClient.TdsParser.Run
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData
at System.Data.SqlClient.SqlDataReader.get_MetaData
at System.Data.SqlClient.SqlCommand.FinishExecuteReader
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds
at System.Data.SqlClient.SqlCommand.RunExecuteReader
at System.Data.SqlClient.SqlCommand.ExecuteReader
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader
at CPH.Data.DataConnection`1.ExecuteReader
at CPH.Data.TableBase.ExecuteReader
at CPH.Data.TableBase.AssertSchema
at CPH.Data.TableBase.Open
at CPH.Data.RecordsetBase`2.Open
at CPH.Data.Database.OpenTable
at CPH.Data.Database.Open
at LSB.App.OpenDatabases
at LSB.App.Initialize
at LSB.App.OnStartup
Are you able to submit that error through the built-in reporting service? We'd like to make sure it's cataloged correctly.
pastorjoel
Member
Ryan,
The program installs but won't load after installation. How can I report it through the built-in reporting service? It quits after it's loading "categories" or the item right after it. It's hard to tell exactly because the script moves so fast.
The service should appear when you have an error and ask you if you want to submit it to CPH. It's possible you're not seeing it because of where you are in the initialization process, and that's OK.
We're taking a look at what you pasted above and working through finding a solution today; I will post back when we have either a solution you can try or a patch that solves the issue.
You must log in to post.
