Logos 5 Won't Open
Worked fine last week. Now it gets to the "Signing In" and crashes.
I've renamed the /Users/sgtthee/Library/Application Support/Logos4/Data/3sn1805l.y56/ResourceManager/ResourceManager.db that someone suggested in another post, but no help.
Please help!!!!
in Him,
Jeff
Comments
-
That's an error that I've not seen before, and there are no useful entries in the logs. Could you have a look in Windows Event Viewer to see what is recorded there?
- Go to the Start Menu and type Event Viewer in the search box. When you see the link for event viewer appear in the search results, click it.
- When the event viewer opens, expand the Windows Logs folder, and then click on Application.
- Scroll through the list until you come to the time and date when Logos crashed (2013-10-16 09:03:47).
- Click once on the row to display the error details in the lower part of the window.
- Copy and paste that error message here (there may be two entries, both would be useful).
You're looking for something like this:
Some crashes similar to this have been caused by buggy AMD video drivers. Have you updated the driver recently?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I haven't updated any AMD drivers lately...that I'm aware of:
First error log from Event viewer
Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
Stack:
at <Module>.TextShaperFactory.Create(WinUtil.DWriteCustomFontCollectionProvider*)
at Libronix.DigitalLibrary.Logos.LogosResourceDriver.SetFontCachePath(System.String)
at LDLS4.OurApp.CacheFonts()
at LDLS4.OurApp.<InitializeAndRun>b__2e(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()SECOND ERROR LOG
Windows cannot access the file C:\Users\Jeff\AppData\Local\Logos4\Shared\Cache\Fonts\5.1.2.0083-5.dat for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Logos Bible Software 5 because of this error.
Program: Logos Bible Software 5
File: C:\Users\Jeff\AppData\Local\Logos4\Shared\Cache\Fonts\5.1.2.0083-5.datThe error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.Additional Data
Error value: C0000185
Disk type: 3THIRD ERROR LOG- all within seconds of each other.
Faulting application name: Logos.exe, version: 5.1.2.83, time stamp: 0x525330a4
Faulting module name: dwrite.dll, version: 6.2.9200.16571, time stamp: 0x5154c177
Exception code: 0xc0000006
Fault offset: 0x00074db3
Faulting process id: 0x2018
Faulting application start time: 0x01ceca785ab0b822
Faulting application path: C:\Users\Jeff\AppData\Local\Logos4\System\Logos.exe
Faulting module path: C:\Windows\system32\dwrite.dll
Report Id: ad9bb6bd-366b-11e3-9311-b8ac6fb523fdThanks,
Jeff
0 -
Sounds like a font cache refresh might sort things out: https://www.logos.com/support/logos5/windows/font-cache (solution 2)
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks! I'll give it a try. I have an appointment right now, but will check when over.
THanks again,
Jeff
0 -
Okay, I followed Step 2 and Logos went to load and then crashed before gettng to the sign in stage...Recommendations???
0 -
Does this file exist: C:\Users\Jeff\AppData\Local\Logos4\Shared\Cache\Fonts\5.1.2.0083-5.dat
If it does, it might be worth trying to rename it. (I'm guessing a little bit here, because I've never seen this error before. If renaming it doesn't work, you'll probably need help from Logos).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Nope, doesn't exist. I'll call them. Thanks for all your help.
Jeff
0
