I have automatic updates, but it crashed after the update, the crashed log said that it is because of ArgumentOutOfRangeException , what should I do?1732.Logos4Crash.txt
the crash log text
Program Version: 4.6c (4.63.0.0357)Windows Version: 5.1.2600.196608Time: 2013-07-07 06:40:36 -05:00 (2013-07-07T11:40:36Z)Installed memory: 2,047 MBInstall path: C:\Documents and Settings\Dad4Gen\Local Settings\Application Data\Logos4\System\Logos4.exeFree install space: 100,829 MBData path: C:\Documents and Settings\Dad4Gen\Local Settings\Application Data\Logos4\Data\uy0anqfo.wofFree disk space: 100,829 MBTemp path: C:\Documents and Settings\Dad4Gen\Local Settings\Temp\Free temp space: 100,829 MBError ID: 6593Error detail: ArgumentOutOfRangeException: The TimeSpan must have a positive duration.參數名稱: tsSystem.ArgumentOutOfRangeException: The TimeSpan must have a positive duration.參數名稱: ts 於 Libronix.Utility.TimeSpanUtility.FormatForLogging(TimeSpan ts) 於 Logos.Sync.Client.SyncManager.<SyncManagerThread>b__9(KeyValuePair`2 x) 於 System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() 於 Libronix.Utility.EnumerableUtility.<IntersperseIterator>d__84`1.MoveNext() 於 System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func) 於 Libronix.Utility.StringUtility.Join(IEnumerable`1 seq, String strSeparator) 於 Logos.Sync.Client.SyncManager.SyncManagerThread() 於 System.Threading.ThreadHelper.ThreadStart_Context(Object state) 於 System.Threading.ExecutionContext.runTryCode(Object userData) 於 System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) 於 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) 於 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 於 System.Threading.ThreadHelper.ThreadStart()
Ho-Ngon Yung:I have automatic updates, but it crashed after the update,
Not looking good for a workaround as it occurs with a Logos Sync utility, but try a restart of the computer and Logos. Alternatively go to Add/Remove Programs, click Logos Bible Software 4 and choose Repair. If that fails start Logos with CTRL key held and upload Logos.log immediately after the crash.
Dave===
Windows 10 & Android 8
I try but not successful. Here is the logos4.log file5670.Logos4.log
We will have to wait for Logos to respond to this, or you can contact Technical Support.
Does the program crash every time you run it, with the same error each time? (If so, I'm surprised that this is consistently reproducible.)
We will fix this in the next Service Release.
Yes, thank you.
Ho-Ngon Yung: it crashed after the update, the crashed log said that it is because of ArgumentOutOfRangeException
This will be fixed in 5.1 SR-1. If it is not fixed please let us know.