When the application crashes, it will write a short crash report to My Documents\Logos Log Files\*Crash.txt; this will occur whether or not logging is enabled.

All beta users should enable logging again: http://downloads.logos.com/LBS4/Installer/EnableLogging.js.

(http://community.logos.com/forums/t/21128.aspx) Startup “Proxy settings” link on the Sign in window will now appear after a failed log in attempt (e.g., blocked by proxy server), so the proxy details can be entered.

Startup Hidden resources are now documented in the Logos4.log.

Android Reader 4.6.4 Improved Improved crash logging and reporting

Android Reader 5.12.4 Build 117 Fixed Added back crash logging

- Fixed Biblia Text Comparison crash when user is not logged in.

- Fixed Biblia Text Comparison crash when user is not logged in.

Android Reader 8.12.2.0031 Fixed - Fixed potential Notes sync issue - Prevent attempted use of Notes when not logged in

Android Reader 8.8.0.0021 Improved - Potential crash log improvement Fixed - Various bug fixes

These documents were compiled as personal books, and a further script examined the warning logs generated by Logos to determine which verses are unsupported by each datatype.

If possible please follow the directions for Diagnostic Logging and Uploading Logs to include a diagnostic log with your post.

Log file attached on forum thread.

See this other thread, too, for more info and logs (concerning the near grinding to a halt when closing a certain BWS panel): http://community.logos.com/forums/t/9407.aspx Software version: 4.0.

I enabled the logs and all the logs contain this line: System.Data.SQLite.SQLiteException: The database disk image is malformed database disk image is malformed I’ll try to upload the logs as well.

Bug: Cannot update SR-2 to SR-3 Whether from the web or automatic download, logs show that the downloaded msi is SR-2 and there is nothing to update.

A log file and screen shot are attached in the forum thread.

Log attached in forum.

If the program continues to crash, please enable logging and post logs on the Logos 4 forum, or contact customer support at 800-875-6467

Here’s what I did to cause Logos to abnormally terminate and capture log file: a.

In the attached zip file, I have the log files and a few screenshots showing the crash dialogs.

Forum link: http://community.logos.com/forums/t/7418.aspx Status: invalid – Bradley Grainger can’t reproduce this problem, but has added some more diagnostic code in case it does ever happen again.

Hopefully log file will help you troubleshoot it.

Forum link: http://community.logos.com/forums/ Status: invalid – Log files or crash dump are needed (post on forum or with tech support staff).

With log file attached... =========== Thanks guys.

Forum link: http://community.logos.com/forums/ Status: invalid If indexer crash has not been resolved, please provide logs or contact Customer Support.

Forum link: http://community.logos.com/forums/ Status: invalid If problem is not resolved, please provide logs, or contact Technical Support at tech@logos.com.

Bug: Logos 4 Perpetually indexing when Windows 7 starts The Logos 4 indexer starts every time I log into Windows or re-start Windows; however, it appear that the indexing is not actually working because my search function does not work properly.

My log fileshttp://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2451.Logos-Log-Files.zip Running on Vista-32bit Acer Aspire 5100 Turion AMD X2 Mobile technology TL-52 1.60 Ghz with 2gig of ram.

Bug: Logos crashes before display log-in screen See title and post.

Forum link: http://community.logos.com/forums/t/18203.aspx Status: confirmed Called support; logs provided to development.

Forum link: http://community.logos.com/forums/ Status: invalid – need more information and logs

SEE lastest post for the lates log file (only produces one file) and screen shots.

Another user reported this error and a third reports 2 errors – one of which is similar and one different, if I read the logs right.

I’ll find the logging info and investigate further.

Bug: Problem with Merge Index whether user requested or automatic Typical log entry is: Error Program Unhandled exception: System.ArgumentOutOfRangeException: document id 2527 is outside valid range of [1, 2527) Software version: 4.0a.

Comments Log files (attached) indicate that the cause of the crash was Error Program Unhandled exception: Libronix.DigitalLibrary.Logos.IndexingException: No translation word for specified document position —> System.ArgumentException: No translation word for specified document position    at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResourceCore.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)    at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResource.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)    at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.ProcessReverseInterlinearIndexData(NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)    at Libronix.DigitalLibrary.Logos.Callback.ProcessReverseInterlinearIndexData(Callback* , NativeLogosResourceIndexer* pNativeIndexer

Here is the crash log: Program Version: 4.0d (4.04.4.1385) Windows Version: 6.1.7600.0 Time: 2010-07-11 08:14:07 Installed memory: 3,839 MB Install path: C:\Logos4\System\Logos4.exe Data path: C:\Logos4\Data\xvkpktor.1vn Free disk space: 538,607 MB Temp path: C:\Users\Michael\AppData\Local\Temp\ Free temp space: 538,607 MB Error ID: 2638 Error detail: SEHException: External component has thrown an exception.

setup programs not running, taking a long time or crash on startup (no logs); corrupt indexes or continual indexing.

It appears that resource id’s are case sensitive as the logs state:-        ‘LLS:gs_jbmw_10’ is out of date        ‘LLS:GS_JBMW_10’ is up to date Software version: 4.0a.

Note that the expiration of your certificates might have been caused by you changing the date/time on your machine. 3) Proxy server problems This is one more possible obscure cause (Windows): Check the log file for an error like this: “The remote server returned an error: (514) Web Acceleration Client Error (514) – Proxied HTTPS Request Not Supported.”

Cannot start L4 after issue opening NIV Logs available – see thread.

How do I enable diagnostic logging?

Crash on opening L4 under VMWare Logs available – see thread.

Crash: Animation Exception on Home Page Logs available – see thread Software version: 4.0d B4.

Crash: SQLite Exception: The database disk image is malformed Logs available – see thread.

The deleted files will be listed in the Logos.log if Diagnostic Logging is active.

Diagnostic Logging Wiki: TOC, VTOC, Home Forum: Home, General See also  Uploading Logs  Bug Report  Screenshot  Logos Help Center  Report a Problem A diagnostic log is a detailed report of what the Logos program is doing and it is used to diagnose problems.

If they are authorized to connect to the document (either because it’s shared to “All Users” and they’re logged in, or because it’s shared to a Faithlife group that they are connected to) they will see a blue “Actions” button in the upper right, where they can choose to connect to the document.

Faithlife Assistant Commands Calendar Based Tasks General Navigation Help Bible Navigation Resource Navigation Narration Search Definition & Lookup Documents Guides Tools Bible Browser Trivia Settings Account & Orders Diagnostic & Maintenance He is risen!

How do I upload log files to the Logos Forums?  

.), then we usually want to see some logs from the desktop and mobile applications before we can help.

Include your Logos.log and LogosError.log files.

If a reference cell cannot be parsed, the software will skip that field, and leave a warning message in the log.

Thus, while it remains possible to install and run Libronix on a Windows desktop, this installation can no longer connect to Libronix servers to sychronize your licenses) Associate License Online Log into Logos.com OR forums OR Faithlife with your Faithlife account Use https://www.logos.com/Redeem Enter your product key (OR serial #) Call Customer Service You call 1 (800) 875-6467 (US), 0871-218-1700 (UK) Sample Conversation ring, ring Receptionist: Logos Bible Software, how may I direct your call?

Logos 28.0 RC 1 Version: 28.0.32 Release Date: September 5, 2023 Bug Fixes Reporting Improved logging for crash reports.

The application is not ready until after the user has logged in successfully, the main window has appeared, and any startup operations have completed.

The application will write a Logos4Crash.txt crash report to Documents\Logos Log Files if it crashes, regardless of whether logging is enabled.

Logos 4.0b Crashes The following crashes have been logged from Logos 4.0b.

Program Settings Hidden resources are now documented in the Logos4.log.

Startup Sign in dialog now says “Sign in to Logos.com” instead of “Log in to Logos.com.”

Startup Sign in dialog now says “Sign in to Logos.com” instead of “Log in to Logos.com.”

Diagnostic Logging Full Logging has been disabled to improve performance in the program.

Diagnostic Logging Full Logging has been disabled to improve performance in the program.

Entering this command will download all of the sync items on the server and compare them to the sync items on the client, reporting any mismatches to the Logos4.log (if logging is enabled) as well as to a new “Logos4Error.log.”

Added a ‘View log file...’ link to panel post-compilation for easy access to Personal Book log files.

New Features for Mac Logging Implemented creation of Logos4Error.log file when errors occur, even if logging isn’t enabled (this matches an existing Windows feature.)

New Features for Mac Logging Implemented creation of Logos4Error.log file when errors occur, even if logging isn’t enabled (this matches an existing Windows feature.)

SQLite errors are logged to the application error log.

SQLite errors are logged to the application error log.

Social Sharing Clicking the Faithlife icon in the info pane for Bibles will display a web page with a runtime error if Faithlife.com is not already logged into a user account.

Known Issues Synchronization Some users may see a yellow “sync error” icon and have the following text logged in Logos4Error.log (see this thread): Request: GET https://librarycatalogapi.logos.com/collections/v1/sync (status InternalServerError

Log In Screen Fixed bug which prevented the “Why?”

Log In Screen Fixed bug which prevented the “Why?”

Bug Fixes for Windows Setup Fixed bug which prevented installing Logos without being logged into Windows as the administrative user.

If you crash on startup, hold down ‘control’ when you startup the program and make offline selection in order to run the program in diagnostic mode and then remove NRSV bible from the Preferred Bible list on the Homepage.

Startup Fixed bug which could occur when logging in with incorrect credentials.

Personal Book Builder Fixed bug which caused error in log file when input text box was created.

Startup Fixed crash which could occur when logging in with incorrect credentials.

Logging    “Unparsed reference: popup.pos” errors are no longer appearing in the Logos.log file.

Synchronization    Attempting to sync after changing password while logged in will provide a message prompting a restart and re-login.

LLS Resources    “Unparsed reference: popup.pos” errors are no longer appearing in the Logos.log file.

Fixed crash when building books caused by the Logos\Logging\PBB\Logs folder becoming unwriteable.

Fixed crash when building books caused by the Logos\Logging\PBB\Logs folder becoming unwriteable.

Personal Book Builder Fixed crash when building Personal Book if the Logging folder didn’t have read/write/execute permissions correctly set.

Logos Fixed numerous crashes in various areas in the application that had been reported by our automatic crash logging.

Logos Fixed numerous crashes in various areas in the application that had been reported by our automatic crash logging.

Please post your Logos.log file on the Thread and then run Repair in Programs and Features.

Updater Fixed a patching error when downloading new resources and updating existing resources resulting in “Catastrophic failure” in the log.

Updater Fixed a patching error when downloading new resources and updating existing resources resulting in “Catastrophic failure” in the log.

If Controlled Folder Access is turned on Logos Logs will now be saved in %LOCALAPPDATA%\Logos\Logos Log Files and %LOCALAPPDATA%\Logos Log Files.

Thread Startup Fixed bug where Work Offline option was missing when logging in.

If Controlled Folder Access is turned on Logos Logs will now be saved in %LOCALAPPDATA%\Logos\Logos Log Files and %LOCALAPPDATA%\Logos Log Files.

Sign-In Updated the log-in screen brand icons.

Improvements Sign-In Updated the log-in screen brand icons.

Additional logging to help with future issue reports

If you have any unexpected behavior with startup or indexing, please inform us on the forums and post logs if available.

If you experience any issues, please post your logs and any reproduction steps in the Logos Desktop Beta Forum.

Improvements Performance Modified ngen to hide the process log and launch Logos.

Logging Added new logging to track when resources are removed.