4.0b Beta 11 (4.02.3.6685) available
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
For Release Notes, see http://wiki.logos.com/4.0b_Beta_11.
To upgrade from a previous beta, enter "update now" to begin downloading it. To install Beta 11 from scratch, see the notes and download link at http://community.logos.com/forums/t/8883.aspx
For 4.0b Beta 10 release notes, see http://community.logos.com/forums/t/11913.aspx.
Comments
-
Sounds like this is just about to launch...[:D]
0 -
Pat Flanakin said:
Sounds like this is just about to launch...
I would guess RC 1 is just around the corner... [:)]
0 -
soon and very soon I think, for me its 95% there, all I really miss are my sentence diagrams...
I say 95% 'cos I dont expect my notes gripes ever to be fixed... otherwise its about 90%
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
DominicM said:
soon and very soon I think, for me its 95% there, all I really miss are my sentence diagrams...
I say 95% 'cos I dont expect my notes gripes ever to be fixed... otherwise its about 90%
I think sentence diagrams are probably going to be in 4.0c, which has already been under development for a while as a few developers remain on 4.0b fixing bugs. Bradley hints we might getting the first beta of 4.0c before March 16.
0 -
Come on verse lists! I miss those a lot. Beta 11 installed fine and seems to be working well.
0 -
Ok, loaded and runs fine. I have bounced through my layouts and back again, run PG, BWS and EG one right after another and searched again and again. BTW, Handouts are better since dealing with the memory issue. The results:
1. No crashes
2. The response is fast.
Time for RC1 IMHO (not that it maters [;)])
0 -
-
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
Dewayne Davis said:
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
I bet your logs would tell. [;)] http://wiki.logos.com/Diagnostic_Logging
MacBook Pro (2019), ThinkPad E540
0 -
Dewayne Davis said:
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
Did it produce a crash.txt file in your Logos Log Files folder? That is a new feature they added in Beta 10, so that regardless of whether you have diagnostic logging enabled, you can get some sort of report to give them to help track down what's causing the crash. Also of course it's good to try generating a log file as there might be more info in that which would help them. See http://wiki.logos.com/Diagnostic_Logging for how to generate the log files, and http://wiki.logos.com/Uploading_Logs for how to upload those log files (and crash.txt) as attachments here on a forum post.
0 -
Dewayne Davis said:
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
Crash Log
Program Version: 4.0b Beta 11 (4.02.3.6685)
Windows Version: 6.1.7600.0
Time: 2010-02-18 15:51:24
Installed memory: 1,535 MB
Install path: C:\Users\Dewayne\AppData\Local\Logos4\System\Logos4.exe
Free disk space: 44,252 MB
Temp path: C:\Users\Dewayne\AppData\Local\Temp\
Free temp space: 44,252 MB
Error ID: 3746
Error detail: InvalidOperationException: Error reading postings. Document id out of range.
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.TemporaryFileSearchResultReader.Load(IWorkState state, SearchResultReader readerSource)
at Libronix.SearchEngine.QueryProcessor.CreateReaderForProcessedTerm(ExpandedTermListProcessedTerm termProcessed)
at Libronix.SearchEngine.ExpandedTermListProcessedTerm.CreateReader()
at Libronix.SearchEngine.QueryTreeConverter.Libronix.SearchEngine.IQueryNodeVisitor.Visit(TermQueryNode node)
at Libronix.SearchEngine.TermQueryNode.Accept(IQueryNodeVisitor visitor)
at Libronix.SearchEngine.QueryTreeConverter..ctor(QueryProcessor processor, QueryNode nodeRoot)
at Libronix.SearchEngine.QueryTreeConverter.ConvertQueryTreeToProcessorTree(QueryProcessor processor, QueryNode nodeRoot)
at Libronix.SearchEngine.QueryProcessor..ctor(IWorkState workState, IDocumentMetadataManager documentManager, FieldManager fieldManager, Lexicon lexicon, PostingsFileReader postingsReader, QueryNode nodeQueryRoot, QueryOptions options)
at Libronix.SearchEngine.QueryProcessor.ExecuteQuery(IWorkState state, IDocumentMetadataManager documentManager, FieldManager fieldManager, Lexicon lexicon, PostingsFileReader postingsReader, QueryNode nodeQueryRoot, QueryOptions options)
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)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.GetSearchResults(IWorkState state, Func`1 fnCreateSearcher, QueryOptions options, IList`1 listResourceIds, Int32& nArticleCount, Int32& nHitCount, Int32& nResultCount)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.DoRunSearch(IWorkState state, QueryOptions options, IList`1& listMainResults, IList`1& listSupplementalResults)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.SearchAndMergeResults(IWorkState state, QueryOptions options, IComparer`1 comparer, SearchResultSummary& summary)
at Libronix.DigitalLibrary.Searching.HitsByResourceLibrarySearcher.GetResults(IWorkState state, Int32 startIndex, Int32 resultCount, SearchResultSummary& summary)
at LDLS4.Panels.VisualFilterPanel.VisualFilterDocumentUserVisualFilterManager.FilterCache.<RefreshWork>d__b.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)“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
Dewayne Davis said:
Error detail: InvalidOperationException: Error reading postings. Document id out of range.
This indicates that corruption was introduced at some time from merging indexes, and the 'rebuild index' command should fix this crash.
Melissa
0 -
Melissa Snyder said:Dewayne Davis said:
Error detail: InvalidOperationException: Error reading postings. Document id out of range.
This indicates that corruption was introduced at some time from merging indexes, and the 'rebuild index' command should fix this crash.
Melissa
Melissa, there seem to be a lot of users on the forum with corrupted indexes. Is the next release going to handle the corruption appropriately? Or will we still be getting users with crashing indexers?
MacBook Pro (2019), ThinkPad E540
0 -
Pat Flanakin said:
Sounds like this is just about to launch...
Sure would love to see the file menu organized before it does. All those note files sure gum things up.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Todd Phillips said:
Is the next release going to handle the corruption appropriately? Or will we still be getting users with crashing indexers?
There was a thread devoted to this question a while back and AFAIK no one from Logos responded to it. Inquiring minds want to know.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Todd Phillips said:
Melissa, there seem to be a lot of users on the forum with corrupted indexes. Is the next release going to handle the corruption appropriately? Or will we still be getting users with crashing indexers?
There have been fixes included in previous betas to prevent the corruption, however, if an index was merged in an earlier build that introduced the corruption, a newer build could still trigger the exception. Once the index is rebuilt, the problem shouldn't reoccur, unless another bug is introduced at some point.
Development has not closed this case yet, and we will continue to provide new logs and reports to them as necessary.
0 -
downloaded, started most the way, crashed, restarted, and works fine. It's curious, I don't have lots of issues, but have had 4 (I think) crashes in last 2 weeks or so, but restart always works fine. The crashes have been on the 2 desktops, I don't think the laptop has crashed.
0 -
Pat Flanakin said:
Sounds like this is just about to launch...
I hope not. Still waiting on the text to speech bug to be fixed. Pressing the down arrow key stops the speech
0 -
Melissa Snyder said:
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
Installed and working without problems.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Melissa Snyder said:Dewayne Davis said:
Error detail: InvalidOperationException: Error reading postings. Document id out of range.
This indicates that corruption was introduced at some time from merging indexes, and the 'rebuild index' command should fix this crash.
Melissa
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
Melissa Snyder said:
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
Downloaded, installed and is running fine.
Lenovo P72: Intel 8th Gen i7-8750H 6-core, 32GB RAM, 2TB HDD + 1TB Sata SSD, 17.3" FHD 1920x1080, NVIDIA Quadro P600 4GB, Win 10 Pro
0 -
0
-
After upgrading to Beta 11, on every start of the beta I get an additional update available downloading message. It comes and goes very quickly, so I am not sure the size of this download. It doesn't appear to do anything. It is very small... Looks like 25.6K. This also appears with update now command.
Does anyone else see this?
0 -
No, but if you post your logs, we could see what the resource was.
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 -
Dewayne Davis said:
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
It is working great now. Thanks.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
I wonder how often reindexing should be performed. I guess it is best when you have purchased additional resources.
Thoughts?
0 -
I hope not, indexing is the most annoying part of L4 for me. I really hope that reindexing will not be a solution in the future. I dont know how much more my computer can take.
0 -
Dewayne Davis said:Dewayne Davis said:
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
It is working great now. Thanks.
I saw another thread about B11 index corruption when merging. This got me to thinking. When I finished the 850+ meg Journal update and index, I did a Merge Index command. Maybe this is what introduced the corrupted index? I have had not problems before and am pretty sure that I did the reindex earlier in the beta when the corruption was first discussed.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
Dewayne Davis said:Dewayne Davis said:Dewayne Davis said:
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
It is working great now. Thanks.
I saw another thread about B11 index corruption when merging. This got me to thinking. When I finished the 850+ meg Journal update and index, I did a Merge Index command. Maybe this is what introduced the corrupted index? I have had not problems before and am pretty sure that I did the reindex earlier in the beta when the corruption was first discussed.
Yes that thread you saw mentions a workaround (until the bug is fixed) - using rebuild index should work.
0 -
Part of the log file is below with the log file for the session attached, now I see the resource but don't know who to resolve this.
2010-02-19 16:50:58.0638 5 Info UpdateManager No more resource file info objects retrieved; checking unknown resource status.
2010-02-19 16:50:58.0798 12 Info UpdateManager Re-attempting download of 1 resources marked as failed: LLS:LEXSGGLOSSARY
2010-02-19 16:50:58.0938 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.0938 12 Info UpdateManager Resource 'LLS:LEXSGGLOSSARY' is out of date.
2010-02-19 16:50:58.1198 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.1408 12 Info UpdateManager There are existing New or Postponed updates; raising event.
2010-02-19 16:50:58.1408 12 Info UpdateManager Starting Update Manager processing in 06:00:00.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are available.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are set to download automatically; starting download.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Starting download of 1 updates.0 -
Bob Soule said:
Part of the log file is below with the log file for the session attached, now I see the resource but don't know who to resolve this.
2010-02-19 16:50:58.0638 5 Info UpdateManager No more resource file info objects retrieved; checking unknown resource status.
2010-02-19 16:50:58.0798 12 Info UpdateManager Re-attempting download of 1 resources marked as failed: LLS:LEXSGGLOSSARY
2010-02-19 16:50:58.0938 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.0938 12 Info UpdateManager Resource 'LLS:LEXSGGLOSSARY' is out of date.
2010-02-19 16:50:58.1198 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.1408 12 Info UpdateManager There are existing New or Postponed updates; raising event.
2010-02-19 16:50:58.1408 12 Info UpdateManager Starting Update Manager processing in 06:00:00.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are available.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are set to download automatically; starting download.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Starting download of 1 updates.It sounds like the same issue a user was getting in this thread http://community.logos.com/forums/p/8136/64605.aspx#64605
0 -
George, I deleted LEXSGGLOSSARY.LOGOS4 to see if that would help, but same error. Any more ideas how to resolve?
0 -
George Allakhverdyan said:
Yes that thread you saw mentions a workaround (until the bug is fixed) - using rebuild index should work.
I had already been instructed to do the rebuild index. I just wanted to add the information for reference. Thanks.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”0 -
Bob Soule said:
George, I deleted LEXSGGLOSSARY.LOGOS4 to see if that would help, but same error. Any more ideas how to resolve?
Delete LEXSGGLOSSARY.LOGOS4 if necessary
Delete C:\Users\Bob\AppData\Local\Logos4\Data\egtfnf1i.ca4\UpdateManager\Updates.db
and C:\Users\Bob\AppData\Local\Logos4\Data\egtfnf1i.ca4\DownloadManager\DownloadManager.db + everything therein.
Ensure logging is ON and start L4. Return both log files if it doesn't work.
Dave
===Windows 11 & Android 13
0 -
Bob Soule said:
George, I deleted LEXSGGLOSSARY.LOGOS4 to see if that would help, but same error. Any more ideas how to resolve?
Sorry I should have been more clear in that link I posted is another thread describing the same symptoms you had - there is a utility you can use to clear out the list of download jobs from windows BITS service since that is what seems to be causing the repeating download - the post (specifically this one http://community.logos.com/forums/p/8136/66083.aspx#66083) talks about the utility, it says you may download the bitsadmin.exe utility here http://downloads.logos.com/LBS4/InstallerBeta/bitsadmin.exe right-click and save target to your desktop. After launching Logos, once the logos blue indexer icon says downloading (0%), we will run the bitsadmin.exe, first Since it is command line tool go to start-->cmd and type in 'cd desktop' (if you are in xp you might have to navigate to use 'cd c:\documents and settings\<user>\desktop'). type in 'bitsadmin /list' - you should see a job with possibly an error next to it - if so you may clear the job by typing 'bitsadmin /reset' - then restart Logos it should try to create a new job. Let me know how it goes.
0 -
Dave, that resolved the issue. Thanks
0 -
George Allakhverdyan said:Bob Soule said:
George, I deleted LEXSGGLOSSARY.LOGOS4 to see if that would help, but same error. Any more ideas how to resolve?
Sorry I should have been more clear in that link I posted is another thread describing the same symptoms you had - there is a utility you can use to clear out the list of download jobs from windows BITS service since that is what seems to be causing the repeating download - the post (specifically this one http://community.logos.com/forums/p/8136/66083.aspx#66083) talks about the utility, it says you may download the bitsadmin.exe utility here http://downloads.logos.com/LBS4/InstallerBeta/bitsadmin.exe right-click and save target to your desktop. After launching Logos, once the logos blue indexer icon says downloading (0%), we will run the bitsadmin.exe, first Since it is command line tool go to start-->cmd and type in 'cd desktop' (if you are in xp you might have to navigate to use 'cd c:\documents and settings\<user>\desktop'). type in 'bitsadmin /list' - you should see a job with possibly an error next to it - if so you may clear the job by typing 'bitsadmin /reset' - then restart Logos it should try to create a new job. Let me know how it goes.
George, thanks for the help.. Dave's method took care of it.
0 -
I am getting a crash. Microsoft C++ runtime Error. the installation downloads fine to my desktop, but when I try to run it a popup announces the program must close L4. I can't install the beta. when I try to open L4 BETA9, I get the option of installing an update - this crashes every time. If I click on the button to bypass the update, I can use the version of LOGOS I have.
I had BETA9 successfully installed and suddenly BETA11 is here. Do I need to go back somewhere and install BETA10? Is this a "rebuild index" problem too?
0 -
This is unlikely to be an indexing problem, and you shouldn't need to install beta 10. You may find it best to exit Logos completely, then download the beta again from this forum. If it still crashes, post a log for us to look at.
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 -
Having trouble generating a log report: I press CTRL and double-click on L4 icon but after holding down the key for a minute and a half, nothing happens but a splash screen for L4 that does not appear on the desktop but only on the task bar. I will re-boot and try a few other options.
0 -
You'll need to turn logging on permanently, then download and install Logos.
http://wiki.logos.com/Diagnostic_Logging
http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe
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 Mark,
I did a cold boot, did an "end task" on indexing which began running at once and then I double-clicked on the L4 icon which ran a successful install of BETA11. Now I am indexing.
I APPRECIATE YOUR HELP
0
