Crash, 4.0c SR1: Crash whilst searching

Mark Barnes
Mark Barnes Member Posts: 15,432 ✭✭✭

Sorry, I lost the full log. Here's the crash log. It's reproducible for me - whenever I do a particular search.

Program Version: 4.0c SR-1 (4.03.3.9838)
Windows Version: 6.1.7600.0
Time: 2010-05-21 11:39:00
Installed memory: 2,046 MB
Install path: C:\Users\Mark Barnes.EMW\AppData\Local\Logos4\System\Logos4.exe
Data path: C:\Users\Mark Barnes.EMW\AppData\Local\Logos4\Data\vqzpi4x1.qsx
Free disk space: 169,081 MB
Temp path: C:\Users\Mark Barnes.EMW\AppData\Local\Temp\
Free temp space: 169,081 MB

Error ID: 6545
Error detail: InvalidOperationException: Sequence contains no matching element

System.InvalidOperationException: Sequence contains no matching element
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate)
   at LDLS4.SearchResultPreviewUtility.GetSearchResultPreviewInfo(ResourceArticlePreviewSearchResult result, LibraryCatalog libraryCatalog, ResourceManager resourceManager, IWorkState workState)
   at LDLS4.Panels.SearchPanel.ArticlePreviewSearchResultViewModel.<LoadPreviewWork>d__0.MoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution()
   at Libronix.Utility.Threading.AsyncAction.Continue()
   at Libronix.Utility.Threading.ThreadPoolAsyncAction.<Start>b__0(Object )
   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)

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!

Comments

This discussion has been closed.