Logos 5 won't start after using Rebuild Index Tool

It would seem that your system is not compatible with L5. Being a dedicated Mac user, I could be wrong. but you logs indicate that you are on Windows NT which is not compatible with Logos 5.

[quote]2013-09-08 13:09:05.9024 1 Info OurApp Starting application (5.1a SR-1, version 5.1.1.0600 on Microsoft Windows NT 6.1.7601 Service Pack 1) at 0.342 seconds.

Minimum Windows OS would be Vista.

Michael - Great job of creating a new thread and posting logs. Your logos.log file is strange to me… that may be from the issue you are having. When the logos.log file is as short as yours, it is often because logging wasn't enabled… but I think yours was.

When I minimized this status notification, the circular exclamation mark changed from grey to yellow and the indexing status never progressed from 0%.

For clarification: I assume that you restarted Logos and your computer too at some point before trying to rebuild your index files, right?

Normally it isn't good to "take someone else's medicine." Your symptoms may be the same as someone else's, but have an entirely different problem. I was inclined to suggest that you might need to delete your BibleIndex and LibraryIndex folders… I followed the link you provided to the other thread after reading your logs and not finding anything (that I understood) and see that this is what Dave recommended to the other user. Since you were going to rebuild your index, the net result of this suggestion should be about the same… the rebuilding of your index files. The biggest problem I have right now, however, is finding the right path for you. I see some paths in your log files, but they are not explicitly to the index folders. If you can't find these, you will need to wait for a techie to come along with more help.

https://community.logos.com/discussion/comment/523771#Comment_523771

I could be wrong

You are. [:P]

you logs indicate that you are on Windows NT

I hate reading windows logs. MSFT has to make everything so difficult. All of the more recent releases of Windows are descendant from / a form of "windows NT." The logs should be in plain english. Sheesh. You know it's bad when a BAMA boy is complaining about using "plain english."

In this case, he is running windows 7, service pack 1.

https://community.logos.com/discussion/comment/523771#Comment_523771

Thank you for your reply. I am using Windows 7 SP1

https://community.logos.com/discussion/comment/523772#Comment_523772

Thanks for the suggestions. Yes, I did a reboot and a restart of Logos 5 and logging was enabled. Now Logos crashes straight away so I am not even sure if deleting those folders will help.

https://community.logos.com/discussion/comment/523786#Comment_523786

I did try deleting those folders because I do have a backup, but Logos still crashes. Even when I hold down the Ctrl key it still crashes... :-(

I don't like not having Logos to do my studies...

https://community.logos.com/discussion/comment/523786#Comment_523786

Now Logos crashes straight away so I am not even sure if deleting those folders will help.

Why? It may be those exact files which are causing the app to crash!

Make sure you try loading to a blank layout (press and hold control key immediately upon startup, check the right box)
If you want to, you can try downloading the engine again. This is a pretty unlikely fix. The issue is probably NOT the software, but the datafiles. Redownloading the engine, however, is a fairly simple thing (5 minutes) to do over doing a reindex (many hours).
If those things don't work, the issue is likely in the data files... which may or may not be the ones we discussed.

I can't be of any more help than that. [:S] I still have my techie training wheels on. [8-|]

Graham Criddle

https://community.logos.com/discussion/comment/523786#Comment_523786

Michael

Now Logos crashes straight away so I am not even sure if deleting those folders will help.

Are you able to post new logs after a failed start attempt?

Graham

https://community.logos.com/discussion/comment/523789#Comment_523789

Last two suggestions:

You could try posting new logs to see if anything additional is added. As a last resort (other than waiting for someone else - perhaps not a bad idea) would be to grab the book files, delete all else, and reinstall. This would save on redownloading the resources.

http://wiki.logos.com/Quick_Installation_onto_multiple_computers

https://community.logos.com/discussion/comment/523789#Comment_523789

Now Logos crashes straight away so I am not even sure if deleting those folders will help.

Why? It may be those exact files which are causing the app to crash!

Make sure you try loading to a blank layout (press and hold control key immediately upon startup, check the right box)

If you want to, you can try downloading the engine again. This is a pretty unlikely fix. The issue is probably NOT the software, but the datafiles. Redownloading the engine, however, is a fairly simple thing (5 minutes) to do over doing a reindex (many hours).

If those things don't work, the issue is likely in the data files... which may or may not be the ones we discussed.

I can't be of any more help than that. I still have my techie training wheels on.

Thanks for trying to help! As I said, even when I hold down the Ctrl key, Logos still crashes and I did already try deleting those index folders, but no change. Is there a Tech Support line I can call? On the Logos website, I can only see one available in Spanish, which is a bit strange.

https://community.logos.com/discussion/comment/523797#Comment_523797

Here are the latest log files...

2337.Logos (2).zip

https://community.logos.com/discussion/comment/523790#Comment_523790

Michael

Are you able to post new logs after a failed start attempt?

Graham

Hi Graham, I have just uploaded new logs...

Many thanks for trying to help!!

https://community.logos.com/discussion/comment/523801#Comment_523801

Hi Graham, I have just uploaded new logs...

I think this might be a long shot... but it wouldn't hurt to try... Try moving your ErrorReportManager.db file to the desktop and restarting Logos. Here is the path:

C:\Users\Michael\AppData\Local\Logos5\Shared\Errors\Application\ErrorReportManager.db

If that doesn't work, we need to put out an APB for a Logos techie.

Is there a Tech Support line I can call? On the Logos website, I can only see one available in Spanish, which is a bit strange.

The Contact info can be found HERE. Looking it over, it is perhaps a bit strange that they say "Tech Support, Spanish Language Only." The "customer service" line is what you would call for tech support, unless you are in the U.K.

https://community.logos.com/discussion/comment/523840#Comment_523840

I think this might be a long shot... but it wouldn't hurt to try... Try moving your ErrorReportManager.db file to the desktop and restarting Logos. Here is the path:

C:\Users\Michael\AppData\Local\Logos5\Shared\Errors\Application\ErrorReportManager.db

If that doesn't work, we need to put out an APB for a Logos techie.

Halleluyah!! Success!! Logos is back, thank you very much indeed!

As to whether it has also resolved the initial problem of the continuous & non-progressive indexing, I will let you know in a few hours. Meanwhile at least I can read and study!

Thanks again,

Michael

https://community.logos.com/discussion/comment/523856#Comment_523856

Glad to help... I think. [:)] Let us know how it goes.

https://community.logos.com/discussion/comment/523773#Comment_523773

you logs indicate that you are on Windows NT

I hate reading windows logs. MSFT has to make everything so difficult. All of the more recent releases of Windows are descendant from / a form of "windows NT." The logs should be in plain english. Sheesh. You know it's bad when a BAMA boy is complaining about using "plain english."

Knew MS was strange, just did not realize how very strange they were [^o)]

https://community.logos.com/discussion/comment/523862#Comment_523862

Knew MS was strange, just did not realize how very strange they were

when I read windows logs now, if I think the OS might be an issue, I immediately google the release number to figure out what it actually is. Much easier just to read 10.8.4. [:D]

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/523856#Comment_523856

If it does crash again, we should be able to work around the issue by editing the registry. (Just post a reply back to this thread.)

Dave Hooton

https://community.logos.com/discussion/comment/523773#Comment_523773

I hate reading windows logs. MSFT has to make everything so difficult. All of the more recent releases of Windows are descendant from / a form of "windows NT." The logs should be in plain english.

It's the same English as a Mac log. What's the difference between OT 10.8.4 and NT 6.1.7601 [:D]

Logos 5 is compatible with NT 6.x whereas Logos 4 is compatible with NT 5.x, 6.x i.e. Logos 5 won't run on NT 5.x.

(I can do this because I'm not trying to think at 4 in the morning; unlike you guys).

https://community.logos.com/discussion/comment/523971#Comment_523971

It's the same English as a Mac log. What's the difference between OT 10.8.4 and NT 6.1.7601

The difference is significant! Who in their right mind refers to "NT 6.1.7601"? Even better, shouldn't windows 7 be "NT 7.X.XXXX"? On the other hand, I would guess that most Mac users refer to their OS as "10.X.X." At least all Mac users I come into contact with do so.

Dave Hooton

https://community.logos.com/discussion/comment/523974#Comment_523974

The difference is significant! Who in their right mind...

You missed the point of the smiley!

I get lost when people refer to Mountain Lion or Snow Leopard.

https://community.logos.com/discussion/comment/523982#Comment_523982

You missed the point of the smiley!

[:D]

I get lost when people refer to Mountain Lion or Snow Leopard.

I can understand. [:)]

The "cat" names, and now California "beach" names, are really just for marketing. It makes for a better television or print ad to say "O.S. Ten Mavericks" rather than "O.S. Ten Point Nine."

FYI - OSX 10.9 "Mavericks" will be released sometime in the next couple of months.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/523974#Comment_523974

Even better, shouldn't windows 7 be "NT 7.X.XXXX"?

If you want to read some really tortured reasoning behind the choice of "6.1" as the version number for Windows 7 (and why it was called "Windows 7" in the first place), take a look at http://blogs.windows.com/windows/archive/b/windowsvista/archive/2008/10/14/why-7.aspx.

https://community.logos.com/discussion/comment/523971#Comment_523971

It's the same English as a Mac log. What's the difference between OT 10.8.4 and NT 6.1.7601

Ah, but Apple markets the OS as 10.8.4 while MicroSoft markets Windows NT 6.1.7601 as Windows 7.

some really tortured reasoning

After reading that very-enlightening blog, I now understand that logic has nothing to do with it [8-|]

https://community.logos.com/discussion/comment/523858#Comment_523858

Glad to help... I think. Let us know how it goes.

Logos has finished indexing. Deleting those folders forced Logos to rebuild a new index which help as as well I think...

Many thanks again,

Michael

https://community.logos.com/discussion/comment/523912#Comment_523912

If it does crash again, we should be able to work around the issue by editing the registry. (Just post a reply back to this thread.)

Thanks Bradley for your advice. Logos seems to have settled down now... it is horrible when something that you use a lot suddenly stops working and especially on a Sunday when there is no one to phone!! Thank God for this forum and those people who take the time to keep their eyes on it and send replies!!

https://community.logos.com/discussion/comment/524012#Comment_524012

That's just funny, I don't care who you are. [:P]

https://community.logos.com/discussion/comment/524012#Comment_524012

After reading that very-enlightening blog, I now understand that logic has nothing to do with it

LOL [:D] I had no idea I was going to cause such an enlightening conversation!!

https://community.logos.com/discussion/comment/524019#Comment_524019

Sorry to have (Hi JACK!)ed your thread. (See what I did there?) [:)]

To bring things back for at least a moment... Is all still well?

fgh

https://community.logos.com/discussion/comment/524000#Comment_524000

If you want to read some really tortured reasoning behind the choice of "6.1" as the version number for Windows 7 (and why it was called "Windows 7" in the first place), take a look at http://blogs.windows.com/windows/archive/b/windowsvista/archive/2008/10/14/why-7.aspx.

Now I know why I'm on Mac.[:D]

Dave Hooton

https://community.logos.com/discussion/comment/524012#Comment_524012

some really tortured reasoning

Hey, Bradley is the author of that quote!

https://community.logos.com/discussion/comment/524037#Comment_524037

Sorry to have (Hi JACK!)ed your thread. (See what I did there?)

To bring things back for at least a moment... Is all still well?

Yes, you made me laugh!! [:)]

Yes, thank you very much for your help, it was and is very much appreciated!!

Blessings,

Michael

https://community.logos.com/discussion/comment/524054#Comment_524054

some really tortured reasoning

Hey, Bradley is the author of that quote!

Oops [:$]. A bit sloppy with the reply button there.

Sorry to have (Hi JACK!)ed your thread. (See what I did there?)

That's not nice. You realize that yelling "Hi Jack" in the airport terminal can get you in trouble. After you board the plane, the side effects are much worse [:D]

https://community.logos.com/discussion/comment/524246#Comment_524246

I'd better stick to your last name. [;)]

Dylan Rondeau

https://community.logos.com/discussion/comment/523912#Comment_523912

If it does crash again, we should be able to work around the issue by editing the registry. (Just post a reply back to this thread.)

This will be fixed in 5.1a SR 2.