Crash on opening Logos 6

Page 1 of 1 (6 items)
This post has 5 Replies | 1 Follower

Posts 317
Paul Meathrel | Forum Activity | Posted: Thu, Mar 5 2015 4:15 AM

Hi all,

When I opened Logos 6 this morning on my Windows PC it crashes quickly after launching. It opened fine yesterday but today it won't open without immediately crashing again. Can anyone offer any help please?

Looking in the event log I get very similar errors to the OP here: https://community.logos.com/forums/p/101684/703295.aspx#703295

My exact errors are:

Faulting application name: Logos.exe, version: 6.1.0.24, time stamp: 0x54ee7b7a
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process ID: 0x4c0c
Faulting application start time: 0x01d05738ca939261
Faulting application path: C:\Users\Paul\AppData\Local\Logos5\System\Logos.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report ID: 6577d4ab-c32c-11e4-bee1-d43d7e4bb7cf
Faulting package full name:
Faulting package-relative application ID:

Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.Path.InternalGetTempFileName(Boolean)
at Libronix.SearchEngine.DocumentMetadataManager..ctor(Libronix.SearchEngine.IndexParameters)
at Libronix.SearchEngine.Indexer..ctor(Libronix.SearchEngine.IndexInfo, Libronix.SearchEngine.IIndexerProgress, Libronix.SearchEngine.IndexFileFormat)
at Libronix.DigitalLibrary.Documents.DocumentManager.DoBuildIndex(Libronix.Utility.Threading.IPausableWorkState, DocumentManagerIndexData)
at Libronix.DigitalLibrary.Documents.DocumentManager.BuildIndexThread(Libronix.Utility.Threading.IPausableWorkState, DocumentManagerIndexData)
at Libronix.Utility.Threading.WorkStateThreadOwner`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ThreadProc(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)

Faulting application name: LogosCEF.exe, version: 1.2.1.4, time stamp: 0x5457f831
Faulting module name: libcef.dll, version: 3.2062.1898.1, time stamp: 0x5450b6a7
Exception code: 0xc0000005
Fault offset: 0x0000000000a97ed2
Faulting process ID: 0x39b8
Faulting application start time: 0x01d05738055217d4
Faulting application path: C:\Users\Paul\AppData\Local\Logos5\System\LogosCEF.exe
Faulting module path: C:\Users\Paul\AppData\Local\Logos5\System\libcef.dll
Report ID: a002825d-c32b-11e4-bee1-d43d7e4bb7cf
Faulting package full name:
Faulting package-relative application ID:

Posts 29618
Forum MVP
JT (alabama24) | Forum Activity | Replied: Thu, Mar 5 2015 4:32 AM

Please enable and post logs. 

macOS, iOS & iPadOS | Logs |  Install

Posts 317
Posts 29618
Forum MVP
JT (alabama24) | Forum Activity | Replied: Thu, Mar 5 2015 7:53 AM

I see one or two "unhandled exceptions" in your logs, but I am not sure what they mean. Until someone with more knowledge comes along:

  1. Have you tried opening to a blank layout? I believe on windows you press and hold the control key immediately upon startup.
  2. If that doesn't work, you could try moving the ErrorReportManager.db file to the desktop. I am not sure if that file is corrupted or not. 

C:\Users\Paul\AppData\Local\Logos5\Data\rnbdysu5.ntd\Errors\Application\ErrorReportManager.db


 

macOS, iOS & iPadOS | Logs |  Install

Posts 95
LogosEmployee
Lawrence Rafferty | Forum Activity | Replied: Thu, Mar 5 2015 9:36 AM

I'm sorry for the frustration we added to your morning! From the logs it looks like the root cause is that the application is unable to write to a temporary file, because all the available temporary file names are in use. Can you try running the Disk Cleanup utility included with Windows, check the box next to "Temporary Files", and click okay. Please let me know if the app still crashes after deleting the temporary files.

Posts 317
Paul Meathrel | Forum Activity | Replied: Fri, Mar 6 2015 5:20 AM

Thanks for the reply Lawrence, that resolved the issue!

Page 1 of 1 (6 items) | RSS