MacBook Pro Mavericks SSD
This morning I am unable to start Logos 5 - starts to load and then crashes -- sent numerous reports and would really appreciate help - have followed instructions on "Support" page to no avail.
4456.LogosLogs.graemeleslierobertson.20131120-104653.zip
Many thanks,
Graeme Robertson
sent numerous reports and would really appreciate help
Sending reports doesn't provide you with help directly... It is still good to do.
This morning I am unable to start Logos 5 - starts to load and then crashes
I think the problem is a corrupted database file. Try deleting your ErrorReportManager.db file and restarting Logos. The path is:
Users/graemeleslierobertson/Library/Application Support/Logos4/Data/n7rj3fko.k3g/Errors/Application/ErrorReportManager.db
NOTE: Your user library is hidden by default in OSX. Google: "Show user library OSX" to discover different ways to reveal it.
Thank you for your amazingly quick response! I have followed your instructions and deleted the error file - however it has not resolved the problem - and of course produces another error file each time, however I know how to delete that now.
Any other suggestions would still be appreciated -- I have sent an email to support as well.
Just for anyone else -- to find library folder in Mavericks - in the GO menu of Finder - pressing the option key and holding it down reveals the Library folder in the drop down menu.
Thanks,
Graeme,
Another user's error log shows the same errors yours does for today. I told him all I know here: http://community.logos.com/forums/t/77855.aspx
Afraid that isn't much help. The cause of your problem seems to be the same as his. Hopefully this can get sorted out soon.
I have followed your instructions and deleted the error file - however it has not resolved the problem - and of course produces another error file each time, however I know how to delete that now.
I am a "half techie," and may have misread the log. For clarification, however, you don't need to delete that .db file over and over. If it was corrupted, a new one should have been rebuilt, which you will want to leave in place.
There appear to be several users with a similar issue, which I have not been able to help resolve. Hopefully someone more knowledgable will be by soon.
