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.

Uploading Logs Wiki: TOC, VTOC, Home Forum: Home, General When you’ve completed your Bug Report in the Forums, you need to attach a copy of the Logs that were indicated by the wiki article Diagnostic Logging.

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

Uploading Logs)

Diagnostic Logs Logs record the activity of the software in a way that assists identification of the feature or module that is causing a problem.

Mac and PC User Interface Differences Wiki: TOC, VTOC, Home Forum: Home, General See also  Keyboard Shortcuts For Mac  Keyboard Shortcuts For Windows  Logos 4 Mac  Mac Release Notes and History Page Contents Common Experience Default File Path Easter Egg – Mac only Feature Parity – Mac needs some improvements Floating Window Indexer Icon Keyboard Shortcuts Logging Microsoft Word Hyperlinks Morphology Pop-up Notes Spell Check Printing & Export Program Icon Program Scaling Resource Update Right Click Search – Handouts Screen layout File Guides Layouts Tools Common Experience Logos for Mac and Logos for PC share code base – most items function identically on both platforms (including right and left mouse click options in File, Guides, and Layouts menus).

Logos Windows Profiler Utility Important Note This is not a “general purpose” diagnostic tool.

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

Option: can open diagnostic log to verify scan path added: Logos Application Diagnostic Log Logos /Users/username/Library/Application Support/Logos4/Logging/Logos.log Verbum /Users/username/Library/Application Support/Verbum/Logging/Verbum.log After scan path command is entered, scanning begins immediately.

Diagnostic logging was enabled until Logos 4.3 Beta 5 (version 4.30.0.0586), when default was changed to improve performance, Logos Logging application can show then optionally change diagnostic logging, refer to Mac Diagnostic Logging for details Enable Mac Diagnostic Logging (always includes indexer logging) Repeat buggy issue OR crash (unexpected disappearance) in Logos 4 Mac Immediately after Logos 4 Mac issue repeats OR crashes (and before relaunching), open a Finder window, press Command-Shift-G, and enter “~/Library/Application Support/Logos4” (without the quotation marks) in sheet that pops up, then press OK.

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

Logos Help Center (LHC) includes What to do if Logos crashes & How-to-Enable-and-Submit-Log-Files with macOS Logging selection box.

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

Logos Help Center (LHC) includes What to do if Logos crashes & How-to-Enable-and-Submit-Log-Files with macOS Logging selection box.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

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

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.

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

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.

library.logosBug: Login Required Twice When first logging into library.logos.com (or after clearing cookies), I am forced to login twice.

Faithlife Status – Check server issue(s), or follow @FaithlifeDevOps Using the Forums for friendly discussions about Faithlife stuff LBS Platform Feature Comparison: Desktop, Mobile, Web Blogs & News – General Interest & Products by Faithlife Corporation Contact – Faithlife email addresses & phone numbers FAQ : Faithlife, Ebooks, Logos, Verbum, Notes, Connect, Privacy Policy, Faithlife Study Bible, Faithlife TV, Lexham Press, Terms of Service Faithlife Feedback – Help Prioritize Development : Announcement Desktop App Issues Logos Support (LS) + Verbum Support (VS) LS Desktop + VS Desktop LS Support FAQ + VS Support FAQ LS Free Support + VS Free Support LS Optimizing + VS Optimizing LS Remote Assistance LS Report a Problem – PC & Mac VS Report a Problem – Mac VS Report a Problem – PC LS Installing + VS Installing Installing & Indexing Questions – PC & Mac Diagnostic Logging – PC & Mac Screenshot – PC & Mac Windows Screen Reader – PC Windows Troubleshooting

Logging Added new logging to track when resources are removed, this is cumulative rather than for each session.

Additional logging to help with future issue reports

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.)

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

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.

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

iOS Reader 4.6.4 New Improved logging for “Report a Problem” Smarter loading of text range note attachments Fixed Opening Note Documents should no longer crash the app Deleting History items should no longer crash the app

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

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.

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.)

Android Reader 4.6.4 Improved Improved crash logging and reporting

Android Reader 5.12.4 Build 117 Fixed Added back crash logging

Include your Logos.log and LogosError.log files.

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

New Features for Windows Logging Moved the default logging folder location to: %LocalAppData%\Faithlife\Logs\Logos\ %LocalAppData%\Faithlife\Logs\Verbum\ Changes Search Removed the “Search (while typing)” option from Bible Search.

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

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

Logos 9.3 RC 1 Version: 9.3.0.0039 Released: February 23, 2021 New Features My Library Added some additional logging.

And note that it will sync settings, documents, history, etc. between those two accounts (assuming that you log in with the same logos.com account on both Windows accounts).

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

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

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

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.

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

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.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

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

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

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

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

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

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

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

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

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

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.

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

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

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

How do I enable diagnostic logging?

I’ll find the logging info and investigate further.

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

Hopefully log file will help you troubleshoot it.

Log attached in forum.

Fixed The Verse of the Day is now properly localized (in the Biblia app) Internal crash log report fixes

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

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Logging Moved the default logging folder location to: %LocalAppData%\Faithlife\Logs\Logos\ %LocalAppData%\Faithlife\Logs\Verbum\ Bug Fixes Canvas Fixed a bug that prevented Word Info Cards from showing up.

Creating a Hang Dump The instructions are the same as above, except in step 2, run Logos4: procdump -h -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp Logos5: procdump -h -x "%LOCALAPPDATA%\Logos5\System\Logos.exe" Logos5.dmp Collecting Diagnostics for the Indexer If the Logos 4 Indexer is hanging or crashing, use the same instructions as above, but change Logos4.exe in the commands to Logos4Indexer.exe

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

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

SQLite errors are logged to the application error log.

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

Logging Added new logging to track when resources are removed.

Log file attached on forum thread.

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

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.

Page Contents Where do I find the Warning/Error log?

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.

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.

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

You should also provide log files from your attempt to start Logos.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

SQLite errors are logged to the application error log.

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.

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?

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

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

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

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

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.”

How do I upload log files to the Logos Forums?  

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

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

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

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.”