Help! :)

Hi all. I have much experience with running embperl on linux/apache
but I currently need to set it up under CGI on IIS (win 2000, IIS 5)
by tomorrow!

I have:

1. compiled HTML::Embperl 1.3.4 myself without mod_perl support. All
   the tests pass fine.
2. have associated .pl files with the Activestate perlis.dll (changing
   this to perl.exe doesn't make any difference so I may as well
   generate errors faster, right? :)
3. Have installed embcgi.pl in the default /scripts/
   subdirectory. It's being run within perl as sticking some short
   example code at the top does the right thing. Other perl scripts
   here work fine.
4. I have added a BEGIN {} block to set some environment variables in
   this cgi script. Currently logging isn't working but this may be a
   symptom of the problem described below.
5. I have also associated .epl files with the
   /Inetpub/scripts/embpcgi.pl executable as suggested in this list
   somewhere. 
6. In desperation I have also set the AllowPathInfoForScriptMappings
   property (as also discussed in the archives)


(my embpcgi.pl available from:
http://stage.switchsuper.com.au/emb/embpcgi.pl)

If I request /scripts/embpcgi.pl/admin/default.epl I get:

  'c:\inetpub\wwwroot\admin\default.epl' script produced no output

... even when I insert a printenv-type thing that shortcuts all the
Embperl calls.


If I request /admin/default.epl I get:

  Error 403.1 Forbidden: Execute Access Forbidden
  Internet Information Services blah blah blah
  
.. ie I haven't set some sort of execute permission somewhere. Looking
at the properties of that folder in the Management Console, Execute
Permissions are set to "Scripts and Executables".

Help!

-- 
 Andrew O'Brien
 Senior Engineer                       email: [EMAIL PROTECTED]
 Switch Online Group Pty Limited       phone: +61 2 9299 1133
 ABN 89 092 286 327                    fax:   +61 2 9299 1134

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to