Logos 5 crashed following updates

Greetings! I was working in Logos 5 (Gold) on the evening of 10/27/2014 and loaded the available Logos updates. After that Logos would open but not respond. I received an error message saying that Logos 5 had stopped working and Windows was looking for a solution. I did manage to open the Logos program by bypassing the latest layout. My log files are attached.4786.LogosCrash20141028.zip

Find more posts tagged with

Comments

TCBlack

I did manage to open the Logos program by bypassing the latest layout.

It may have been a corruption in that layout then. Is it working normally now?

JT (alabama24)

Is the app still crashing? Have you tried rebuilding the layout?

Mark Smith

The error is most unusual (having to do with EzekielsTemple.xps) and I don't have an explanation for it or how to correct it. If you recognize where you had that image or graphic open in your Layout and rebuild the layout without it. I am glad you can at least work in Logos for now.

I notice you are still using Logos 5.2. I'd suggest you upgrade to Logos 5.3 which is the latest release (not that that has anything to do with your problem). Type Update Now in the Command Bar, hit Enter and Logos should discover the update and download it for you.

Someone from Logos may look in and be able to tell you how to handle that errant file.

Graham Criddle

https://community.logos.com/discussion/comment/645587#Comment_645587

I notice you are still using Logos 5.2. I'd suggest you upgrade to Logos 5.3 which is the latest release (not that that has anything to do with your problem). Type Update Now in the Command Bar, hit Enter and Logos should discover the update and download it for you.

Mark - 5.3 is still in beta testing (with no current plans for it to come out) so 5.2b SR7 is the latest stable release before Logos 6.

Victor Engbrecht

https://community.logos.com/discussion/comment/645576#Comment_645576

It seems to be working now since I deleted the the layout that seemed to creating the problem.

Victor Engbrecht

https://community.logos.com/discussion/comment/645579#Comment_645579

Not crashing yet and I haven't attempted to rebuild the layout. I need to have the program working for a day before I risk another crash.

Victor Engbrecht

https://community.logos.com/discussion/comment/645587#Comment_645587

Thanks Mark!

Victor Engbrecht

https://community.logos.com/discussion/comment/645594#Comment_645594

I am running 5.2b SR-7 (5.2.2.1584), so thank you for affirming that it is a stable version. The layout could have been the problem because it included several open windows. Perhaps there was a conflict with some of the open programs. If it crashes again we may find out.

JT (alabama24)

https://community.logos.com/discussion/comment/645701#Comment_645701

Sometimes a layout gets corrupted, and just needs to be deleted. Sometimes a resource (book) gets corrupted and needs to be deleted and redownloaded. We don't know without 1) logs and 2) trial and error. It could also be something completely different.

In your case, you reported that you had a crash... but that it was up and running again. It was confusing why you posted (Were you asking for help, or just reporting something?) It might be good to make sure that logging is "permanently" enabled. If it crashes again, upload the logs and tell us what you were doing so we (or someone smarter!) can help. [:)]

Mark Smith

https://community.logos.com/discussion/comment/645594#Comment_645594

Mark - 5.3 is still in beta testing (with no current plans for it to come out) so 5.2b SR7 is the latest stable release before Logos 6.

HMM. Shows how much attention I've been paying to L5 the last couple of months.

Victor Engbrecht

https://community.logos.com/discussion/comment/645732#Comment_645732

Thanks alabama, much appreciated.

Victor Engbrecht

https://community.logos.com/discussion/comment/645740#Comment_645740

You're probably not alone on that one, but I sure appreciate your willingness to help.

Chris Robbers

https://community.logos.com/discussion/comment/645753#Comment_645753

Please see this thread for a workaround: https://community.logos.com/forums/p/93159/647414.aspx