Recovering from a "crash on startup"

Greetings!

I had been working fine since my initial upgrade to L4 and over the last week I had a root kit issue I had to resolve; in doing so I did a system restore point to an earlier version (windows XP pro SP3). Coincidentally or not …. I was not able to start L4 after the restore.

By following various hints and suggestions in the forums I was able to get my L4 to restart and forced an upgrade…

I was getting the “database schema is new than the latest schema recognized by this code” type error in the log. I would go one by one an rename the offending database (e.g., .db to .dbo ) and restart with the CTL key until I was able to clear the issue (ultimately I was able to get the program to “update” after I moved the contents of the …\data\LibraryCatalog directory to a temp location).

After download and install of the upgrade L4 would startup … I had lost some personal settings (collections, reading plans etc…) Not a big deal.

The only remaining issue for me is I can’t seem to find my “notes” … the notes.db file seems OK ? (it's about a 1.1 MB big)… all my old L3 annotation files from the import seem to be there and OK … is there something obvious I’m not seeing about my notes file/database?

BTW ... notes.db was "not" one of the databases I had to rename

Thanks in advance for any help pointers.

Dave-

Find more posts tagged with

Comments

David V. Barragan

BTW ... found on a post by DominicM (ref http://community.logos.com/forums/p/16769/126972.aspx#126972) that notes have a master/detail format and the master is on the "Documentinfo.db" when I restored that database from my earier "renames" ... I was able to see my notes again.

I think I'm all good now! (or at least back to working in my normal context! )

Thanks to all who have posted before!

Dave-

Dave Hooton

I was getting the “database schema is new than the latest schema recognized by this code” type error in the log. I would go one by one an rename the offending database (e.g., .db to .dbo ) and restart with the CTL key until I was able to clear the issue (ultimately I was able to get the program to “update” after I moved the contents of the …\data\LibraryCatalog directory to a temp location).

As a cautionary note this is NOT the way to recover from this issue as either a software update or re-install will fix it without side effects! And there are ways to re-install without re-downloading resources.

SteveF

https://community.logos.com/discussion/comment/153348#Comment_153348

I was getting the “database schema is new than the latest schema recognized by this code” type error in the log. I would go one by one an rename the offending database (e.g., .db to .dbo ) and restart with the CTL key until I was able to clear the issue (ultimately I was able to get the program to “update” after I moved the contents of the …\data\LibraryCatalog directory to a temp location).

As a cautionary note this is NOT the way to recover from this issue as either a software update or re-install will fix it without side effects! And there are ways to re-install without re-downloading resources.

To Dave Hooten: I had this exact same problem last month when installing to a new lap top

(I was using one of the Wiki methods} I had re-installed (from backups) many other times on other machines yet had never gotten that error.

I ended up doing a total re-install by down load.

Dave Hooton

https://community.logos.com/discussion/comment/153698#Comment_153698

To Dave Hooten: I had this exact same problem last month when installing to a new lap top

(I was using one of the Wiki methods} I had re-installed (from backups) many other times on other machines yet had never gotten that error.

Steve, that "database schema" error can happen if you use/copy from different versions of the software eg. install 4.0c but copy Data/Documents from 4.0d Beta.

SteveF

https://community.logos.com/discussion/comment/153710#Comment_153710

that "database schema" error can happen if you use/copy from different versions

That is probably what happened. I had done multiple backups to an external hard drive.

Sorry, DavidVBarragan for high-jacking your post. Hope your issues are soon all solved.

Regards,

Steve