Logos4 stops working on startup

My Logos4 has been working great for 2 mos since I installed it. Now it stops working on startup. Attached are the log files I copied out of the documents folder and the popup message telling me the program has stopped working. Sometimes I can see my current layout just before it stops working and sometimes the layout doesn't appear. I am running windows 7 home pro on a new asus W75 gaming laptop.

Dead in the water,

Richard Durkopp

Find more posts tagged with

Comments

Lynden O. Williams

Welcome to the forums Richard. Have you tried holding down the Ctrl key when starting and opening to a blank layout?

Richard Durkopp

https://community.logos.com/discussion/comment/396102#Comment_396102

Thank you very much! I fixed it by opening logos4 with a blank layout. Found the last layout used would crash logos4 when selected. I deleted that layout and created a new one which works fine.

How often does this happen?

Also I noticed logos4 doesn't sync layouts with my other computer. Is that normal?

Thanks again,

Richard Durkopp

Rich DeRuiter

https://community.logos.com/discussion/comment/396134#Comment_396134

Thank you very much! I fixed it by opening logos4 with a blank layout. Found the last layout used would crash logos4 when selected. I deleted that layout and created a new one which works fine.

How often does this happen?

It has happened more frequently lately, which has me somewhat concerned. Hopefully the techs are watching these issues and are figuring it out.

Also I noticed logos4 doesn't sync layouts with my other computer. Is that normal?

Logos only syncs saved layouts. If those aren't syncing then you'd need to look at your sync settings and internet connection on both computers.

DMB

https://community.logos.com/discussion/comment/396139#Comment_396139

I don't understand why the software can't seem to figure out 'what went wrong'. But I have a strong opinion (the one related to trying make the software as un-intuitive to use as possible).

Earlier this morning a user's Logos4 figured out the database version didn't match the software version (though that's sort of up in the air-ish). But none the less, the program's next decision point was to simply crash.