Logos 5 not opening bug

5355.logging.zipI click on the application and get a few seconds of seeing the spin wheel go round while receiving the logging on message then it just quits. Have restarted the mac, have unistalled and reinstalled the software but to no avail. log file attached re reporting a problem.

Find more posts tagged with

Comments

Graham Criddle

HI Richard

The latest entry in that log file is from 19 January.

Please enable full logging and post logs after a failed start attempt as per https://www.logos.com/support/logos5/mac/problem

Thanks Graham

Dave Scholes

https://community.logos.com/discussion/comment/572313#Comment_572313

the log is already attached to my post i believe

Dave Scholes

https://community.logos.com/discussion/comment/572315#Comment_572315

What do i attach? The zip file won't and if i unzip it i get several files but can't attach them all?

Dave Scholes

https://community.logos.com/discussion/comment/572315#Comment_572315

this is what was generated by last attempt to open, not sure if whats you need though?4010.logging.zip

Dave Scholes

https://community.logos.com/discussion/comment/572318#Comment_572318

3733.LogosLogs.richardscholes.20140301-233435.zip

Dave Scholes

https://community.logos.com/discussion/comment/572319#Comment_572319

7242.LogosError-2.log

JT (alabama24)

https://community.logos.com/discussion/comment/572315#Comment_572315

the log is already attached to my post i believe

For clarification: you did a great job of posting logs the first time... But they were old files. Logging is disabled by default and must be turned on. There are several ways to do this, some are temporary, some are permanent. The link already provided, or the one in my signature line, will provide instructions. I see you have made new attempts... I'm not near my computer to read the logs. If no one else sees them, I'll try to check later.

Dave Scholes

https://community.logos.com/discussion/comment/572322#Comment_572322

Thanks, have not done this before. Downloaded and used the log tool for first time and this is what was generated. Don't know why old files might be there for this reason. I activated the tool. Attempted to open the software and dsent the results as best as I could. As I say the original zip file didn't want to attach soni opened and attached what seemed relevant.

Dave Scholes

https://community.logos.com/discussion/comment/572322#Comment_572322

Have tried app removal and instal again. why should this not work?

JT (alabama24)

https://community.logos.com/discussion/comment/572327#Comment_572327

Have tried app removal and instal again. why should this not work?

Reinstalling the software is rarely a fix for issues with Logos. The data files are not deleted when you delete the engine... so its kind of like putting a new coat of paint over a car that has been totaled... In this case, you have a corrupted database file... but I am not fully sure which one. I do have a guess.

With Logos turned off, try moving your ErrorReportManager.db file (path listed below) to the desktop and restarting Logos. The file will rebuild. Hopefully this will fix things. If not, hopefully someone else will be able to direct you to the right file to delete.

Here is the path: /Users/richardscholes/Library/Application Support/Logos4/Data/ad3nqa0w.o3x/Errors/Application/ErrorReportManager.db

NOTE: your user library is hidden by default in OSX. If you do not know how to find it, google "show user library in OSX" to learn how.

Dave Scholes

https://community.logos.com/discussion/comment/572322#Comment_572322

might have done better this time. (pressed the sample button before trying to open). will try again. early hours in the am here in the UK so off to bed after this one. hope you can get me running soon!3264.LogosLogs.richardscholes.20140302-012537.zip

Dave Scholes

https://community.logos.com/discussion/comment/572337#Comment_572337

found and moved the errorreportmanager.db file to desktop and tried to restart but no difference I'm afraid.

JT (alabama24)

https://community.logos.com/discussion/comment/572347#Comment_572347

found and moved the errorreportmanager.db file to desktop and tried to restart but no difference I'm afraid.

Ugh. Sorry! [:S]

I know that the issue IS a corrupted .db file (the logs tell me so), but I don't know which one. I guessed on that one because it was the in the line right above the error message. Hopefully one of the full fledged techies will be of more help in the morning.