Network Drive Storage for Library

Is there a way to have my Logos Library books stored on a network drive rather than my local hard drive? I tried to do an install to a custom path on a network drive, but then every time Logos started I received a message that the indexer crashed. I do not have that problem when I go the 'Typical' installation route.

Thanks in advance.

Find more posts tagged with

Comments

Mark Smith

Ryan,

You cannot store the books separate from your total Logos installation. If you chose the custom install route everything is on that network drive. Unless there are access problems or interruptions over that network, Logos should be able to run that way.

It would have been good to have been generating log files during your attempts. There should be an error log under My Documents\Logos Log Files at least. If so you could attach it to a follow-up message. To enable permanent diagnostic logging see: http://wiki.logos.com/Diagnostic_Logging

Ryan Hutchinson

https://community.logos.com/discussion/comment/342313#Comment_342313

Mark:

Attached are the log files. I tried an installation to a network drive where I did not choose to automatically download updates. With that Logos 4 launched fine off of the network drive. However, within the app when I enabled automatic download the indexer crashed.

Thanks for the assistance.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/342484#Comment_342484

However, within the app when I enabled automatic download the indexer crashed.

Looks like UNC (Universal Naming Convention) was used for network path. Wonder about mapping UNC to a drive letter, then custom install using drive letter path (instead of \\file03....) ?

Keep Smiling [:)]

Mark Smith

https://community.logos.com/discussion/comment/342484#Comment_342484

Ryan,

I have not seen these before (not surprising since yours is a pretty rare setup). They all indicate a failure to be able to gain permission to set something called 'defaultProxy'.

Googling the error led me to this page which might be a fix for you: http://www.codeguru.com/forum/showthread.php?t=516691

Ryan Hutchinson

https://community.logos.com/discussion/comment/342500#Comment_342500

Thanks. Does look like it is probably the issue highlighted from the other forum where my network drive isn't trusted by the .NET framework. Lots of switches w/ that CasPol.exe command so it might take me a while to figure out the right combination to get it to work.

Ryan Hutchinson

https://community.logos.com/discussion/comment/342517#Comment_342517

Looks like the problem is not resolved w/ adding the network drive as a trusted location for the .NET framework. Here is the format I had to use for the command to make it work: C:\Windows\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -m -pp off -ag 1.2 -url file://///server/share/* FullTrust (replacing the server and share path w/ my location.)

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/342530#Comment_342530

Looks like the problem is not resolved w/ adding the network drive as a trusted location for the .NET framework.

Years ago encountered some Windows programs that always needed a drive letter; they would not work with UNC path. Hence wonder about mapping network drive to a drive letter, then custom install Logos 4 using that drive letter.

Keep Smiling [:)]

Ryan Hutchinson

https://community.logos.com/discussion/comment/342555#Comment_342555

Just realized I mistyped on my earlier post. The problem was "resolved" by adding the network path as a trusted location. Not sure why I typed that it was not resolved. Since I can't edit the post at this point, here is it again w/ the right verbiage:

Problem resolved: Looks like the problem IS resolved w/ adding the network drive as a
trusted location for the .NET framework. Here is the format I had to use
for the command to make it work:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -m -pp off -ag
1.2 -url file://///server/share/* FullTrust (replacing the server and
share path w/ my location.)