L4 Crashed while away from my desk

Page 1 of 1 (10 items)
This post has 9 Replies | 0 Followers

Posts 8601
TCBlack | Forum Activity | Posted: Fri, Sep 28 2012 11:06 AM

Having done nothing more than walk away from my desk while L4 was loading (after upgrading to the latest 4.6aβ3).

Logos crashed:

 

Description:

  Stopped working

 

Problem signature:

  Problem Event Name: CLR20r3

  Problem Signature 01: logos4.exe

  Problem Signature 02: 4.61.0.3239

  Problem Signature 03: 5064b161

  Problem Signature 04: Libronix.Utility

  Problem Signature 05: 4.61.0.3239

  Problem Signature 06: 5064afd1

  Problem Signature 07: c74

  Problem Signature 08: 19

  Problem Signature 09: A4DH5WWIWWW1YJTMP0C0KV4ZWCALU4IN

  OS Version: 6.1.7601.2.1.0.256.48

  Locale ID: 1033

3884.Logos-Log-Files.zip

 

Truth Is Still Truth Even if You Don't Believe It

Check the Wiki

Warning: Sarcasm is my love language. I may inadvertently express my love to you.

Posts 2061
Forum MVP
Randy W. Sims | Forum Activity | Replied: Fri, Sep 28 2012 11:14 AM

This looks like the same problem others have had. For a possible solution, see here: http://community.logos.com/forums/p/55341/400661.aspx#400661

Posts 1639
SteveF | Forum Activity | Replied: Fri, Sep 28 2012 11:18 AM

[My error code was identical]

Logos has replied on the other thread.

With their suggestion:

STEPS TAKEN:

1. I deleted the whole Handout folder.

2. Loaded L4 Beta 3 & 

 3. immediately found and deleted this "phantom" handout from my file menu. [For now anyways] that has solved the issue.

 

Regards, SteveF

Posts 8601
TCBlack | Forum Activity | Replied: Fri, Sep 28 2012 12:32 PM

SteveF:
I deleted the whole Handout folder.
HORROR.

Truth Is Still Truth Even if You Don't Believe It

Check the Wiki

Warning: Sarcasm is my love language. I may inadvertently express my love to you.

Posts 8601
TCBlack | Forum Activity | Replied: Fri, Sep 28 2012 12:35 PM

I didn't want to risk that just yet Steve.

I opened L4 and quick deleted a few spurious looking handouts and clicked sync.

I hope it works.

Truth Is Still Truth Even if You Don't Believe It

Check the Wiki

Warning: Sarcasm is my love language. I may inadvertently express my love to you.

Posts 1639
SteveF | Forum Activity | Replied: Fri, Sep 28 2012 12:46 PM

TCBlack:
HORROR.

It was no loss. My (un-happy) experience with handouts going back to their earliest inception has pretty much put them at the bottom of my "like" list Super Angry

Regards, SteveF

Posts 2061
Forum MVP
Randy W. Sims | Forum Activity | Replied: Fri, Sep 28 2012 12:50 PM

I would just copy them elsewhere. I'm wondering if they don't sync back when you start Logos??? Surely, you don't have to permanently destroy any work you've done.

Posts 4590
Forum MVP
Fred Chapman | Forum Activity | Replied: Fri, Sep 28 2012 1:42 PM

This may be a good thread for someone to ask Thomas how he feels about handoutsWink

Posts 8601
TCBlack | Forum Activity | Replied: Sat, Sep 29 2012 8:55 PM

Fredc:

This may be a good thread for someone to ask Thomas how he feels about handoutsWink

Oh. No. You. Didn't!

Truth Is Still Truth Even if You Don't Believe It

Check the Wiki

Warning: Sarcasm is my love language. I may inadvertently express my love to you.

Posts 4885
DIsciple II | Forum Activity | Replied: Sun, Sep 30 2012 3:33 PM

Randy W. Sims (Shayne):

I would just copy them elsewhere. I'm wondering if they don't sync back when you start Logos??? Surely, you don't have to permanently destroy any work you've done.

I had an issue with Visual Filters Randy,  They do sync back but just cause the same problems and the system to crash because the problem document whether it be a handout, visual filter etc resides on the server, so yes you do have to destroy these document - if you want to get back into using L4 before the weekend is over and someone at Logos might be able to remove the problem document from the server.

 

 If you have time you can go through them deleting one by one to find the problem document if you have the time but that can be very time consuming.  What Logos needs to do is improve their error message output so that it tells you the name of the document causing the problem.

Page 1 of 1 (10 items) | RSS