Tried fresh install, indexer keeps crashing, no resources discovered.

Hi.

In the hope of being able to shift my resources from the VMware disk to a directory on my VMware host (P:\ to the Vista Guest), I uninstalled Beta 5 and then reinstalled it. That didn't work - I've forgotten the exact error message now - so I tried shifting them back. I'm now in a state where Beta 5 is installed (I reinstalled it again, pointing it at C:\ again), but the indexer keeps crashing. What can I do?

NCunningham-IndexerStopsResponding.zip

Find more posts tagged with

Performance

Comments

Melissa Snyder

Thanks for the log file Nigel. I'll report error.

Melissa

Nigel Cunningham

https://community.logos.com/discussion/comment/18027#Comment_18027

Thanks Melissa.

I'll wait for possible fixes before nuking everything and trying again.

Melissa Snyder

https://community.logos.com/discussion/comment/18112#Comment_18112

Try this: move (not delete) the LCV.lbslcv file out of the Resources folder in path below.

C:\Users\Nigel\AppData\Local\Logos4\Data\v5p1leg0.gq4\ResourceManager\ResourceManager\Resources

Let us know whether that resolves the indexer crash.

Thanks,
Melissa

Nigel Cunningham

https://community.logos.com/discussion/comment/18235#Comment_18235

It doesn't, sorry.

The error message looks the same to me, but I'll post it if you want.

Nigel Cunningham

https://community.logos.com/discussion/comment/18564#Comment_18564

Still no success with Beta 6 and that file moved, sorry.

Logos4Indexer.log

Melissa Snyder

https://community.logos.com/discussion/comment/18694#Comment_18694

Thanks Nigel. I'll pass the log on to Development. ~ Melissa

Update: The log file shows you still have Beta 5 installed. Can you provide an updated indexer log for Beta 6? Perhaps delete the old one first?

Nigel Cunningham

https://community.logos.com/discussion/comment/18758#Comment_18758

Done. Still crashes. Would you like a newer log?

Melissa Snyder

https://community.logos.com/discussion/comment/19115#Comment_19115

Done. Still crashes. Would you like a newer log?

Yes, please.

Nigel Cunningham

https://community.logos.com/discussion/comment/19185#Comment_19185

Here you go!

Logos4Indexer.log

Nigel Cunningham

https://community.logos.com/discussion/comment/19770#Comment_19770

Hi again.
I've just installed Beta 7, and still have the crash (the About box shows version 1525) and exactly the same backtrace in the Indexer log.

Would you mind if, once I've finished downloadings updates, I follow the purging instructions that were given elsewhere, and try for a fresh start?

Melissa Snyder

https://community.logos.com/discussion/comment/19986#Comment_19986

Of course, we don't mind at all. ) ~ Melissa

Nigel Cunningham

https://community.logos.com/discussion/comment/19987#Comment_19987

I thought you might because in my software development (I maintain a hibernation patch for the Linux kernel), if someone has a problem, I like them to be able to confirm the fix.

Ok. Will try the purge once the download is done!

Nigel

Melissa Snyder

https://community.logos.com/discussion/comment/19989#Comment_19989

I thought you might because in my software development (I maintain a hibernation patch for the Linux kernel), if someone has a problem, I like them to be able to confirm the fix.

Ok. Will try the purge once the download is done!

Nigel

Appreciate that. If the problem reoccurs after uninstalling and reinstalling, please zip and attach all the log files found in the Libronix Log Files folder.

Thanks,
Melissa

Nigel Cunningham

https://community.logos.com/discussion/comment/19994#Comment_19994

A fresh install and deleting the user's Logos4 directory did the trick, and I was able to reproduce the issue again by asking the software to scan a network drive. After doing this (scan P:\Resources), the indexer failed every time it was restarted.

Regards,

Nigel

Melissa Snyder

https://community.logos.com/discussion/comment/20152#Comment_20152

Thanks, I've passed on this information to dev.

Update: This is most likely due to a 'non-standard' system configuration, accessing the resources over the network from VMWare on Linux. Since no other beta testers are having a crash in KERNEL32.dll when accessing the beta resources, we suspect that it is due to your specific setup.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/20234#Comment_20234

More specifically, from the limited information we have available, it looks like a driver/OS issue. Does it still crash if you remove all files from P:\ and start the app? What if you put just one file there, and scan, or ten, or twenty? Is there a particular file that it always crashes on, or does just any file at all cause the crash?

Nigel Cunningham

https://community.logos.com/discussion/comment/20312#Comment_20312

Hi Bradley.

Thanks for the reply. Before I go reproducing the bug again, is there a simple way of undoing the scan command afterwards? I'm not afraid to delete a registry entry if that's what's necessary. I'd just really rather not reinstall unnecessarily.