in reply to Inconsistent failure to find module

Assumptions:

Is it possible that apache does not have access to Z:? Unless Apache is running as you and not as a service, it is quite possible that Z: is not available to it.

--MidLifeXis

  • Comment on Re: Inconsistent failure to find module

Replies are listed 'Best First'.
Re^2: Inconsistent failure to find module
by afoken (Chancellor) on Feb 16, 2012 at 18:59 UTC
    Is it possible that apache does not have access to Z:?

    Most likely. Services usually run as "Local System", and even if not, they run in different sessions than normal users. Since about Windows XP / Server 2003, drive letters are no longer global, but per user (or session, dunno). Microsoft recommends using UNC paths (i.e. \\server\share\some\path instead of x:\some\path), another way that still works (but who knows for how long?) is to install and use the AutoExNT tool. This tool installs as a service and runs a batch file whenever its service is started. From that batch file, one can map drive letters using net use x: \\server\share /user:foo topsecretpassword.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]
[select]
Re^2: Inconsistent failure to find module
by davies (Monsignor) on Feb 16, 2012 at 18:57 UTC

    Z is a network share. I don't know about Apache (it's running according to its defaults), but I thought everything had access to everything else. I'll try to investigate further & see if it's a non-Perl issue.

    Thanks & regards,

    John Davies

[reply]

In Section Seekers of Perl Wisdom