Logos Crashes on Startup; HELP

Try deleting the contents of this folder C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\HomePage

The AppData folder is hidden so you will need enable viewing of hidden files and folders.

I am in the same boat - if I use the cntr key when I start I get the blank layout. Load other layouts but the when I click the Home Icon it crashes. This is what Melissa at Logos said in an email:

Something on the home page is crashing the program, but it’s not clear what’s causing it. Since Beta 11 was just released, check it again after the update has been downloaded and installed. If it still crashes, try again tomorrow to see if the problem is related to a specific feed from today.

https://community.logos.com/discussion/comment/93699#Comment_93699

Kevin and Joe: Thank you for your quick responses. 1) I am not running a beta addition; 2) I deleted the Homepage folder contents Kevin suggested and it still crashes on startup. A couple more items that might be helpful in trouble shooting this:

1) When I started Logos this time after deleting the homepage folder contents, when it crashed, it also brought up the window “indexing your files” at the same time. I remember this morning before crashing the first time, that when I started windows, I received the note that Logos was indexing my resources. I thought this a bit strange as I do not remember downloading anything recently that would have necessitated an indexing. I have attached a screen shot of this latest crash, FYI.

2) I have also attached the latest log file. I note in reading through this (I am not that technically competent; just nosing around) that the “Floating window is activated”:

2010-02-19 07:24:28.5965 1 Info FloatingWindow Floating window activated: LDLS4.FloatingWindow

Is it possible that this is somehow related to an earlier problem as noted in my first post?

5861.2010 02 19 Logos Crash PrtSc.docx

8311.Logos4.log

https://community.logos.com/discussion/comment/93712#Comment_93712

Bruce,

I find your most recent log file curious. There are no errors. While I'm not totally versed in what everything in logs mean, it almost looks to me like the application was shut down properly... which is inconsistent with the crash message (that and the application shutting down 3 seconds after launched)!

I will have to defer to one of the developers who roam the forum (or someone who's come across this error before) to suggest another course of action.

https://community.logos.com/discussion/comment/93739#Comment_93739

Kevin, check out my logs. I start Logos4 with Cntr to get blank screen - then go to layouts and load several of my layouts all working ok. But I click on the Home icon in the top left and crash.

Attached is my log.0878.Logos4.log

https://community.logos.com/discussion/comment/93746#Comment_93746

Kevin: Thank you for taking a look at the log file. I checked the time stamp on that file and I think I may have sent the wrong log file. I have attempted to restart Logos again, and this time I think I have a good log file; it crashed and immediately brought up the “indexing your resources” notification. If you look at the end of the file, it appears problematic. Thx for your help!5504.Logos4.log

https://community.logos.com/discussion/comment/93746#Comment_93746

Kevin, check out my logs. I start Logos4 with Cntr to get blank screen - then go to layouts and load several of my layouts all working ok. But I click on the Home icon in the top left and crash.

Interesting. Your logs are full of WpfDataBinding Errors. However, they (according to Logos) are rarely fatal and they don't seem to be directly related to the crash. The log just ends. I don't know what to suggest. Try deleting the contents of the folder I recommended above. It might not do anything but it can't hurt and it has fixed bugs w/ corrupted homepage contents in the past, perhaps we'll get lucky [:)].

https://community.logos.com/discussion/comment/93748#Comment_93748

Kevin: Thank you for taking a look at the log file. I checked the time stamp on that file and I think I may have sent the wrong log file. I have attempted to restart Logos again, and this time I think I have a good log file; it crashed and immediately brought up the “indexing your resources” notification. If you look at the end of the file, it appears problematic. Thx for your help!5504.Logos4.log

Okay that's a real crash. Was there an indexer log that was saved too? That might be helpful in diagnosing this problem.

Normally, with problems with the index, I would recommend the command "rebuild index" to see if that would correct the problem. But if Logos in crashing we'll have to trigger a new index by deleting the contents of the index folder C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\LibraryIndex

However, I'm not convinced yet that this is the right course of action. If you can afford the re-indexing time, go for it. But first see if you can upload indexer logs, they might hold some extra clues about what's gone wrong.

https://community.logos.com/discussion/comment/93755#Comment_93755

Kevin: Each time I start Logos I get the “indexing your resources” notification. Right now the indexer is running. I have attached the Logos4Indexer.log, but it might only reflect what is going on right now.

I have the platinum edition, plus a lot of other books I have added over the years (about 2,700). Yes, I can afford the indexing time, but obviously if this is not the fix would like to forgo that for now. Thx for the help!

1057.Logos4Indexer.log

https://community.logos.com/discussion/comment/93759#Comment_93759

From your indexer log it is clear that it is attempting a merge of indexes. 4.0a has had problems with merging indexes. Also there is an error in the indexing log, I don't know if it's from a problem with the merge or if something is corrupted, causing problems.

If I were in your shoes I would delete my index before I went to bed and let it run overnight and see what it looks like in the morning.

I can't guarantee that a new index will fix the problem, but it shouldn't hurt.

EDIT: as I look at the indexer log again, it looks like there might be a problem with your metadata db (it'd be nice if Logos would release a key to reading the logs, make it easier on us to figure things out). The metadata is stored here: C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\Updates\metadata.db I might try deleting it too [:)] I apologize for guessing so much. I won't be offended in the slightest if you decide to wait for someone who knows more than I do.

https://community.logos.com/discussion/comment/93751#Comment_93751

I did delete the homepage folder as you suggested it still would not load homepage without crashing. I can load my layouts but would like to get my home page back again!

I am attaching index log maybe you can make something out of that!0763.Logos4Indexer.log

Thanks

https://community.logos.com/discussion/comment/93766#Comment_93766

Joe, thanks for your indexer log. No errors, so it appears to be running just fine. I think that your problem is different than Bruce's, but I don't know for sure.

https://community.logos.com/discussion/comment/93764#Comment_93764

Thx Kevin. I'll let 'er rip and we'll see what happens. Perhaps we have a couple of issues going on here.

https://community.logos.com/discussion/comment/93775#Comment_93775

Kevin: What do you think about first deleting the metadata.db file, then if I get another crash, deleting the indexing file and try re-indexing?

I understand you may not have the total answer, but you have more than I have right now! The worst that can happen is that I have to do a total install! Right? Not-to-worry; I appreciate your help. [:)]

https://community.logos.com/discussion/comment/93781#Comment_93781

Kevin: What do you think about first deleting the metadata.db file, then if I get another crash, deleting the indexing file and try re-indexing?

I understand you may not have the total answer, but you have more than I have right now! The worst that can happen is that I have to do a total install! Right? Not-to-worry; I appreciate your help.

I guess that's the best idea and gives you a chance of avoiding a total re-index, although with 4.0a's track record of merges that might be in your future no matter what.

See if you can load Logos with a blank layout after you delete the Metadata to give it time to download a fresh copy from the servers (may need an "update now' in the command line).

Just hope I don't peeve tech support with my advice [:)]. Let me know how it turns out, I'm going to bed right now.

Peter Junor

My problem is pretty much the same as Bruce's, and my system is almost identical.

No luck on the "delete Home Page" hint, nor on the wiki site referred to.

I have had no trouble until todayt

I did notice that there was a 460+Mb automatic download last night, and I have my suspicions that this might be the source of the drama

Peter

https://community.logos.com/discussion/comment/93815#Comment_93815

Still crashed; here is what I did:

Deleted metadata.db

Closed all programs and rebooted

On reboot, Logos indexer auto started and again started indexing resources

When indexing completed, started Logos using CNTRL key and checking the box to start in open window

Logos started and shortly thereafter, so did indexing.

Forced an update with "Update now" in command line

"No updates available"; "No updates were found"

Loaded layout; no problem

Attempted to open home page; crashed. Note that indexer is also still running through all this

Waiting until indexer stopped; it finally did: crashed

Attached are log file and indexer files

04548.Logos4.log

7651.Logos4Indexer.log

Next steps; I will:

Delete library index contents at: C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\LibraryIndex

Restart Logos with CNTRL key

Let logos re-index or try the "rebuild index" command (See this post about Journals: http://community.logos.com/forums/t/11911.aspx. I have most of these so am wondering .... )

I will post when done and let us see what we have. If anyone can find anything from the attached logs and post, that might also be helpful. Thx for everyone's help.

Jonathan Burke

https://community.logos.com/discussion/comment/93843#Comment_93843

I have the same problem, and I am sure it has to do with the latest update. I didn't have any issues until today.

https://community.logos.com/discussion/comment/93854#Comment_93854

Success! To close this post so others might learn:

Deleted library index contents at: C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\LibraryIndex

Restarted Logos with CNTRL key

Let logos re-index; left Logos with empty screen and minimized. Indexing took about 6 hours for about 2700 books.

Closed Logos

Opened Logos with CNTRL key (to start logging)

Forced update with “update now” command

Opened home page … YES! It worked!

I’m not sure if forcing the update at the end was needed, but just wanted to make sure. Hopefully, this will be the end of the issue. Thx to all for hanging with me on this and seeing it through! [:D]

https://community.logos.com/discussion/comment/93680#Comment_93680

I did three things and I now get the home page.

Started with blank layout and keyed in "Rebuild Index"
Deleted HomePage folder
After it had been "Re indexing for about 1:40 minutes" a message came up like it hadn't reindexing and it was going to reindex. It did that for better than 2 hours, I don't know how long I went to bed. When I got up I got out of Logos4 "clicked the 'x' in top right corner.
Then I clicked on Logos4 Icon on laptop, it started it went to the screen asking if I wanted to work offline? Note: There was not an option to start with blank screen." I clicked "Work online" It went to home page.
I don't know what that all means but it is working again.

Thanks Kevin for listening. I hope Bruce has success when he starts this morning.

https://community.logos.com/discussion/comment/93889#Comment_93889

Bruce and Joe,

I am thrilled that you are back up and running.

Melissa (or some other Logos person) what was the problem here? Which steps were good and which ones were unnecessary? Did Bruce and Joe have the same issue or separate ones?

https://community.logos.com/discussion/comment/93898#Comment_93898

Kevin: Good questions; I'd like to know too. I hope someone from Logos Tech support can take the time to sort through this and give us some input. Have a great day y'all! [:)]

Jeffrey S Gordon

https://community.logos.com/discussion/comment/93924#Comment_93924

Had a similar experience on machine at work (crashes only when trying to load the home page, which I have defaulting to blank). A couple times, this left no clue in the log. The last time though I got the output below at the end of the Logos4.log. I'm going to re-index completely over the weekend (it might take a while), since that seemed to fix the problem for others, and it's overdue anyway. Maybe the log output is a clue (the actual "crash" results in the "send to Microsoft" screen, running on XP).

2010-02-19 13:02:29.2187 19 Error OurApp Unhandled exception: System.InvalidOperationException: Error reading postings. Document id out of range.
   at Libronix.SearchEngine.PostingsFileSearchResultReader.ReadNextDocumentHeader()
   at Libronix.SearchEngine.PostingsFileSearchResultReader.MoveToResult(SearchResultPosition posDesired, IWorkState workState)
   at Libronix.SearchEngine.PostingsFileSearchResultReader.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToResult(SearchResultPosition posDesired, IWorkState workState)
   at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.TermQueryNodeSearchResultReader.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToResult(SearchResultPosition posDesired, IWorkState workState)
   at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.OperatorAndSearchResultReaderBase.MoveToResult(SearchResultPosition posCandidate, IWorkState workState)
   at Libronix.SearchEngine.OperatorAndSearchResultReaderBase.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.OperatorAndSearchResultReaderBase.MoveToResult(SearchResultPosition posCandidate, IWorkState workState)
   at Libronix.SearchEngine.OperatorAndSearchResultReaderBase.MoveToNextResult(IWorkState workState)
   at Libronix.SearchEngine.QueryProcessor.GetResult()
   at Libronix.SearchEngine.QueryProcessor.ExecuteQuery(IWorkState state, IDocumentMetadataManager documentManager, FieldManager fieldManager, Lexicon lexicon, PostingsFileReader postingsReader, QueryNode nodeQueryRoot, QueryOptions options, IMarkupManager markupManager)
   at Libronix.SearchEngine.Searcher.<>c__DisplayClass2.<ExecuteQuery>b__0()
   at Libronix.SearchEngine.Searcher.LockIndexAndExecute[TResult](Func`1 fnLocked, Func`1 fnNotLocked)
   at Libronix.SearchEngine.Searcher.ExecuteQuery(IWorkState state, QueryNode nodeQueryRoot, QueryOptions options, IMarkupManager markupManager)
   at Libronix.DigitalLibrary.Searching.LibraryRelevanceSearcher.GetSearchResults(IWorkState state, Func`1 fnCreateSearcher, IList`1 listResourceIds, QueryOptions options, QueryNode termNode, IMarkupManager markupManager)
   at Libronix.DigitalLibrary.Searching.LibraryRelevanceSearcher.GetSearchResults(IWorkState state, LibraryIndex libraryIndex, IList`1 listResourceIds, QueryNode node, Int32 nMaxResults, IMarkupManager markupManager)
   at LDLS4.HomePage.Items.MediaHomePageItemProvider.<GetRandomMediaFromResource>d__1b.MoveNext()
   at LDLS4.HomePage.Items.MediaHomePageItemProvider.FindMedia(Query query, Double fInclusiveMinRank, Double fExclusiveMaxRank, IWorkState state)
   at LDLS4.HomePage.Items.MediaHomePageItemProvider.GetItem(IEnumerable`1 seqResourceIds, Double fInclusiveMinRank, Double fExclusiveMaxRank, Double fNoReferencesInclusiveMinRank, Double fNoReferencesExclusiveMaxRank, IWorkState state, MediaTagKind[] aTags)
   at LDLS4.HomePage.Items.MediaHomePageItemProvider.GenerateItemsCore(IWorkState state)
   at LDLS4.HomePage.Items.HomePageItemProvider.GenerateItems(IWorkState state)
   at LDLS4.HomePage.HomePageViewModel.<>c__DisplayClass64.<GenerateItemsWork>b__4a(Object prov)
   at Libronix.Utility.Threading.DelegateAsyncWorkItem.<ExecuteCore>b__0(Object o)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at Libronix.Utility.Threading.DelegateAsyncWorkItem.ExecuteCore()
   at Libronix.Utility.Threading.AsyncWorkItem.Execute()
   at Libronix.Utility.Threading.ThreadPoolAsyncWorkItem.<StartCore>b__0(Object o)
   at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

Michael Scoggins

https://community.logos.com/discussion/comment/93889#Comment_93889

I too had the problem of Logos crashing on start-up after the update. I followed Bruce's guide with 2 small exceptions--- I closed Logos after the re-indexing started

(19 hours Yikes!) and I did not do a force update after indexing. It all worked and the home page is running!

Thanks Bruce!

https://community.logos.com/discussion/comment/94617#Comment_94617

Michael: Glad it was helpful. We also need to thank Kevin for his initial guidance on this. I am still hoping the folks in tech support will weigh in and let us know what were the correct steps in resolving this issue. I am sure there are some good trouble shooting things we could have done to minimize the stumbling around. But ... it worked! That is the important thing! [:D]