next »

[bovis]

Searched forum for CGIWrap Error and found posts regarding this same issue. Tried posted solutions and then couldn't open calendar_admin.pl.

I am now back to original install. Debug says everything is cool.

I receive the same "CGI Wrap Error  Execution Script not permitted" when I try to continue beyond calendar_admin initial screen -- same thing happens from calendar.pl if I try to move to another month - same error message

Any help appreciated.

ISP Server OS = FREE BSD
My OS = W2K
Browser = Mozilla
Error Message:
CGIWrap Error: Execution of this script not permitted

Execution of (web) is not permitted for the following reason:

Script is not a regular file

Server Data:

   Server Administrator/Contact: lod@leagueofdecency.com
   Server Name: www.leagueofdecency.com  
   Server Port: 80
   Server Protocol: HTTP/1.1

Request Data:

   User Agent/Browser: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
   Request Method: POST
   Remote Address: 216.175.64.228
   Remote Port: 65166
   Extra Path Info: /calendar_admin.pl
   Referring Page: http://www.leagueofdecency.com/cgi-bin/calendar_admin.pl  

Followed instructions regarding CHMOD/777
webhost is HostBaby.com

[DanO]

What exactly are the URL(s) which generate the errors? Have you looked at them closely to see if anything's out of place??

Edit: This is what I found.

When at ww.leagueofdecency.com/cgi-bin/calendar_admin.pl, clicking the next button, I get taken to ww.leagueofdecency.com/calendar_admin.pl (note the lack of "cgi-bin") which of course generates the error (since no script is at that location).

Something similar occurs with the calendar.pl file but *may* be corrected once you get through the administrations set up screens.

It looks like your server is not reporting the $ENV{'SCRIPT_NAME'} value properly. In the calendar_admin.pl file find the line:

$Template::CGI_URL = $ENV{'SCRIPT_NAME'} | | $ENV{'REQUEST_URI'};

and try reversing the variables. Eg.

$Template::CGI_URL = $ENV{'REQUEST_URI'} | | $ENV{'SCRIPT_NAME'};

If that doesn't work, you may have to set those paths manually or check with your host to see what environment variables you can use the retrieve the proper paths.

JMO

Dan O.

[This message has been edited by DanO (edited February 09, 2005).]

[bovis]

DanO:

I tried your suggestion and it solved my problem. Had I paid closer attention to address info displayed in the address bar I might have eventually figured out what was wrong on my own.

Thanks for your help.

bovis

------------------

[DanO]

** your suggestion solved my problem. **

Glad to hear it, thanks for the follow up.

Dan O.

------------------