BUG:Logos 6.1 Beta 1 (6.1.0.0004) at startup

"2015-01-20 16:41:07.2877 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is preparing your library (Stage 1 of 3)
2015-01-20 16:41:07.3647 7 Error IndexerProgram Unhandled exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Libronix.DigitalLibrary.ResourceManager.GetResourceListsForAllDrivers(IWorkState state)
at Libronix.DigitalLibrary.ResourceManager.DiscoverResourcesThread(IPausableWorkState state, DiscoveryData data)
at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
2015-01-20 16:41:07.3877 7 Info LogosApplication DoRegisterShutdown(True) for Indexer.
2015-01-20 16:41:07.4537 7 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\Errors\Indexer\ErrorReportManager.db
2015-01-20 16:41:18.3543 7 Error RaygunErrorReporter Error Logging Exception to Raygun.io Error building request. Request: POST https://api.raygun.io/entries"

Comments

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,120

    Can you post the full log files?

  • Martin Grainger Dean
    Martin Grainger Dean Member Posts: 571 ✭✭
    This is LogosIndexer.log: "2015-01-21 00:31:14.9981 1 Info IndexerProgram Starting application with module name LogosIndexer, branded name Logos (6.1 Beta 1, version 6.1.0.0004 x64 on Microsoft Windows NT 6.1.7601 Service Pack 1). Pid: 3784
    2015-01-21 00:31:15.2961 1 Info LogosApplication Checking application compatibility mode for 'LogosIndexer.exe'.
    2015-01-21 00:31:17.2623 1 Info UserManager Opening UserManager in D:\Logos\Users.
    2015-01-21 00:31:18.8213 1 Info LocalFileDatabase Found existing database at D:\Logos\Users\UserManager.db
    2015-01-21 00:31:20.1114 1 Info IndexerProgram Using language en-US
    2015-01-21 00:31:20.6805 1 Info IndexerProgram Setting status to Initializing
    2015-01-21 00:31:20.7085 1 Info IndexerProgram Setting storage status to Normal
    2015-01-21 00:31:20.7125 1 Info IndexerProgram Processing existing commands.
    2015-01-21 00:31:20.7225 1 Info IndexerProgram Setting status to PreparingLibrary
    2015-01-21 00:31:20.7255 1 Info IndexerProgram Creating digital library services.
    2015-01-21 00:31:20.7685 1 Info DigitalLibraryServices Initializing DigitalLibraryServices. (Shared Folder= D:\Logos\Shared, Data Folder = D:\Logos\Data\jjurzlpu.v3k, Documents Folder = D:\Logos\Documents\jjurzlpu.v3k)
    2015-01-21 00:31:20.8035 6 Info DigitalLibraryServices (Timed) Creating update manager.
    2015-01-21 00:31:21.0885 6 Info DigitalLibraryServices (Timed) Creating license manager.
    2015-01-21 00:31:21.1235 6 Info LicenseManager Opening LicenseManager in D:\Logos\Data\jjurzlpu.v3k\LicenseManager; products folder is D:\Logos\Shared\Products
    2015-01-21 00:31:21.1725 6 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\LicenseManager\Products.db
    2015-01-21 00:31:21.5045 6 Info DigitalLibraryServices (412ms) Creating license manager.
    2015-01-21 00:31:21.5075 6 Info DigitalLibraryServices (Timed) Creating resource manager.
    2015-01-21 00:31:21.5095 6 Info DigitalLibraryServices (Timed) Creating data type options.
    2015-01-21 00:31:21.5105 6 Info DigitalLibraryServices (0ms) Creating data type options.
    2015-01-21 00:31:21.6255 6 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\WebCache\CacheData.db
    2015-01-21 00:31:21.6935 6 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\ResourceManager\ResourceManager.db
    2015-01-21 00:31:22.0375 6 Info LocalFileDatabase Found existing database at D:\Logos\Documents\jjurzlpu.v3k\ResourceManager\ResourceSyncManager.db
    2015-01-21 00:31:22.3756 6 Info DigitalLibraryServices (867ms) Creating resource manager.
    2015-01-21 00:31:22.3886 6 Info UpdateManager Initializing update manager.
    2015-01-21 00:31:22.9236 6 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\UpdateManager\Updates.db
    2015-01-21 00:31:22.9686 6 Info DigitalLibraryServices (1892ms) Creating update manager.
    2015-01-21 00:31:23.0616 6 Info DigitalLibraryServices (Timed) Creating download manager.
    2015-01-21 00:31:23.7696 6 Info DownloadManager Opening Download Manager in D:\Logos\Data\jjurzlpu.v3k\DownloadManager.
    2015-01-21 00:31:25.3357 6 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\DownloadManager\DownloadManager.db
    2015-01-21 00:31:25.3377 6 Info DigitalLibraryServices (1598ms) Creating download manager.
    2015-01-21 00:31:25.4087 1 Info IndexerProgram Resource discovery started.
    2015-01-21 00:31:25.7437 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is preparing your library (Stage 1 of 3)
    2015-01-21 00:31:26.1818 7 Error IndexerProgram Unhandled exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
    at Libronix.DigitalLibrary.ResourceManager.GetResourceListsForAllDrivers(IWorkState state)
    at Libronix.DigitalLibrary.ResourceManager.DiscoverResourcesThread(IPausableWorkState state, DiscoveryData data)
    at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)
    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ThreadHelper.ThreadStart(Object obj)
    2015-01-21 00:31:26.3358 7 Info LogosApplication DoRegisterShutdown(True) for Indexer.
    2015-01-21 00:31:26.5578 7 Info LocalFileDatabase Found existing database at D:\Logos\Data\jjurzlpu.v3k\Errors\Indexer\ErrorReportManager.db
    2015-01-21 00:34:45.9972 7 Error RaygunErrorReporter Error Logging Exception to Raygun.io Error building request. Request: POST https://api.raygun.io/entries"
  • MJ. Smith
    MJ. Smith MVP Posts: 54,952

    Martin, there should be up to 5 log files that were created. They are usually attached via the paper clip icon both to keep the forums readable and to allow people trying to help to view them in customized text editors. As I recall, in a previous thread there was difficulty getting a complete set of logging information uploaded into the forums. Is there a specific problem with doing so that we can help with?

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭

    Yes, Martin, it's incredibly difficult to read log files when the text is copied/pasted into a forum post, because there are no proper line breaks. Could you please use the paper-clip icon to upload your logs. If there are multiple files, you can zip them together using the instructions here.

    Which files to include? In your Logos Log Files folder, you will find any or all of: Logos.log, LogosError.log, LogosCrash.txt, LogosIndexer.log, LogosIndexerError.log, LogosIndexerCrash.txt. The latter three only matter if the problem involves indexing, and the ones with "Crash" in their names are only relevant if it's a crashing bug you're reporting (and they'll be generated regardless of whether you have diagnostic logging enabled) but actually they are redundant if you do have diagnostic logging enabled (which you appear to) because their contents are entirely included within Logos.log and LogosIndexer.log respectively.

    If it's an installation related problem, then logossetup.log and DigitalLibraryInstall.log (and sometimes PrerequisitesInstall.log) might also be called for, but this time that doesn't appear to be the case.