Question

I am trying to install TWiki using Indigoperl. But I am getting an error "Permission denied at ../tools/rewriteshbang.pl line 71" whenever I put interpretor path. I am sure that I have put Interpretor path correctly. Please look into this issue soon.

Environment

-- TWikiGuest - 05 Jan 2007

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Please tell us who you are. That always helps to motivate us to look into problems!

BTW the problem is that one or more files in the bin directory is set read-only for the user running rewriteshebang.pl

-- CrawfordCurrie - 05 Jan 2007

I am having the same problem. I verified that none of the files in the bin directory are read-only and I am putting the interpretor path in correctly. Is there anything else I could be doing?

-- DanielDowlin - 12 Dec 2007

Sorry, closing this question after more than 30 days of inactivity. Feel free to re-open if needed.

-- PeterThoeny - 02 Feb 2008

I have the same problem and I checked: both the folders twiki\bin and twiki\tools are "full control" permissions for me (Administrator), and I put the correct Perl interpreter path. I could not find an answer to this problem. So I re-open th question

-- RiccardoBianchi - 18 Apr 2008

Ok, I found the solution, it was my mistake :-P When I checked the permissions for the \bin and \tools directory I just saw the Security tab, in order to assign Full Control to my User. But then, when I tried to change the "configure" file by hand...I noticed it was set as "Read Only" in the Properties tab!! :-P

So the solution is: right-click on the \bin and \tools folders, than uncheck the "Read Only" field, choose "Apply this to the subfolders and files", then "Ok"....and now rewriteshebang.pl can do its work properly!! Bye!

-- RiccardoBianchi - 19 Apr 2008

I had the same problem. But some reason I was not able to uncheck the read-only box on the bin folder, so I added my windows username to the local admin group and that did all the magic !!!

-- RajeshN - 27 Jan 2009