earthboundmisfit has asked for the wisdom of the Perl Monks concerning the following question:

Brothers and Sisters...... HELP. I just upgraded to ActiveState Perl build 628. Everything went without a hitch (as close as you can get to that with Windoze) with the exception of this one quirk:

I cannot get a module to load but only when it's run through IIS. Running the script on the command line, it loads just fine. When I hit the same exact script in a web browser it complains that it can't find the .pm 

#! Perl -w
use strict;
use CGI::Carp 'fatalsToBrowser';
use CGI;
use DBI;
use CCMckLib3_2;
my $q = CGI->new;
print $q->header;
print "we're good";

[download]
Again, on the command line, it prints a mime header and the text "we're good," in the browser the error is
"Can't locate CCMckLib3_2.pm in @INC (@INC contains: ....."

I checked the directories of @INC. CCMckLib3_2.pm is right where it ought to be.

I've checked the settings in IIS, re-installed the whole thing, and dumped every caching device I can think of. I'm out of ideas.

Is there anything special I need to do to install a module under this latest build?

Replies are listed 'Best First'.
Re: Odd behavior after upgrade of AS Perl
by LD2 (Curate) on Aug 11, 2001 at 04:35 UTC
    I'm not sure if this is the problem, but you may want to check the directories of where the web server thinks the files are located. It's possible you may need to add these lines: 
    # The following 4 lines are here only because the current directory fo
+r
# Microsoft IIS when running script on browser is always the root
# directory of the web server.
# You need to replace the path of the mck-shared and mck-cgi direct if
+ they
#are at different location. 

BEGIN {
push(@INC, 'C:\\inetpub\\wwwroot\\mck-shared\\'); #or wherever the scr
+ipts are located.
push(@INC, 'C:\\inetpub\\wwwroot\\test-mck\\mck-cgi\\'); #ditto here.
}

    [download]
[reply]
[d/l]
      Yes. Thanks. I have it pointing at a web shared directory and that's my temporary fix for it. This strikes me as a bit megabit on the insecure side and was hoping to find the right way of doing it. Google has been a goose egg for me thus far.

      I'm also wondering why the upgrade hosed me. I did a complete uninstall, but I may have some vagrant registry keys (??) to clean from the previous version. I really expected this to be a simple matter of copying the pm over to the new /Perl/lib directory..... Silly me.

      update: Checked the environment PATH var and even tried a bonafied #!shebang in the script itself. I did find some mention of a PERLIB var. Looking into it.

[reply]

Back to Seekers of Perl Wisdom