Error: Logos 6 crashes within about 10 minutes after showing the message: updating library catalog l

Logos 6 crashes within about 10 minutes after booting the program, the program window shows the message: updating library catalog list may be incomplete. I tried many times to update the program manually using the UPDATE NOW command, I also rebuilt the index using the command line of the program. Nothing so far has helped. This message came up on the Logos window for about a week before it just started crashing. Before it would just say it was updating the catalog but not crash.

I tried to look into the forums for a problem and there seems to be a problem that exists form several years ago but was resolved. I then followed the instructions on what to do if Logos crashes many times. I downloaded the Logos setup program from the web site but it will not run on this computer even in Administrator mode. I have no idea at this point what is happening to cause this problem.

I have IT experience and am a Logos user since version 3, so I do have some experience with the program.

I am afraid to pursue the fresh install as I am on a bandwidth limited internet on the East coast of Africa that is not consistent enough to be sure it will download without a lot of tries. Our power goes off every day some times for hours. I am just explaining some of my limitations here.

I don't want to stop using the software as I am in an active preaching and teaching ministry and use Logos every day. I am also pursing a masters degree and need the software running all the time. I have made an investment of over $8,000 and right now the program will not work so I am in need of help. PLEASE

My system is an HP I5 4th generation laptop with 8GB, 500 GB drive, Windows 8.1 fully updated. I have had no problems until now with Logos. It as installed when I was in Portugal last year and had free internet.

At present I have no access to my books as the program will not run beyond 10 minutes.

Thanks for any help.

Alan Hart

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Logos is crashing when failing to create the "BITS" (Background Intelligent Transfer Service) component. This is a core component of Windows (required for Windows Updates) so it's unexpected that this would happen.

Make sure the service is enabled and running in the Windows Services list. It's probably also worthwhile running "sfc /scannow" to ensure that all Windows files are installed correctly. If that doesn't fix the problem, we may need to research other potential causes of this error.

Bradley Grainger (Logos)

You could also try the Microsoft Fixit on this page, which should reset BITS (and other components needed by Windows Update): https://support.microsoft.com/en-us/kb/971058

Alan Hart

https://community.logos.com/discussion/comment/737425#Comment_737425

Bradley,

Thank you for responding to my request for assistance. The following is the screen information from Command Line after running sfc/scannow. I am also attaching the log file mentioned in this screen capture. I also ran the Fixit from Microsoft.com and it was partially successful. I am going to reboot and see where I am but wanted to send this information before I did that. I will update further later on.

I did notice that Windows Update itself was no working properly and did not make the connection to this problem. My IT experience is more in the hardware and repair area than programming.

Sorry about the delay but I am 9 hours east of Pacific time. Thanks again.

Alan

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan. Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.

C:\Windows\system32>

Mark Barnes

https://community.logos.com/discussion/comment/737481#Comment_737481

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.

That's not necessarily going to be an easy problem to fix. We might be able to help if you post the log file — although as this isn't a Logos-specific problem, you may find more expertise on other forums.

That said, as some fixing has taken place, it might be worth checking to see whether Windows Update is now working. If it's not, and Logos keeps crashing, I suggest using Logos in offline mode until you've fixed BITS. To do this, open Logos, go to Program Settings, and set "Use Internet" to "No", and then restart Logos. That should stop the crashing until the problem's fixed. (If that loses you too much functionality, you could try setting "Use Internet" to "Yes", but automatic downloads to "No".)

Alan Hart

https://community.logos.com/discussion/comment/737495#Comment_737495

Mark,

Thank you for writing. I tried to upload the CBS-log but the page wasn't accepting it. I don't know why. However, it looks like enough was fixed for Logos to work. Windows update now works and I am trying one more program the HP Support Assistant that seemed to also have problems and maybe it involves BITS also, don't know.

I left Logos running all day as I was out on a church building project all day. It is 5:30 PM, very tired but very happy that Logos seems to be back up and running. Thanks for the help-

Alan Hart

https://community.logos.com/discussion/comment/737425#Comment_737425

Bradley,

Thanks for all your help. It was an uncertain result from the scan and the fixit as it says that it was not able to fix everything. However, Logos, windows update are running. I have had a long day painting a church building and now can relax and read on Logos. Thank you for your help. God bless.

Alan Hart

Mark Barnes

https://community.logos.com/discussion/comment/737555#Comment_737555

I'm glad you're back in action.