ppm giving "Permission denied" error

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

Good Day I would like to ask if anybody here experienced Permission denied error upon the installation of perl module specifically the TemplatToolkit Module in ppm? I think the installation was successful however during the uninstallation of the temporary files the permission denied error occured Ive read some problems like this and the solution was write access was not permissible so the granting write access to the temporary directory by using chmod in Linux fixed it. However Im using Windows and the temporary directory was already given write access since Im logged in as Administrator. Does anybody here know the reason for this problem? and how can this be fixed? How come installation of other modules were successful? Thanks Chester

20040725 Edit by ysth: Change title from Perl Module Problem in Windows

Comment on ppm giving "Permission denied" error

Replies are listed 'Best First'.
Re: ppm giving "Permission denied" error by rinceWind (Monsignor) on Jul 23, 2004 at 10:00 UTC
Try using "ppm" from a Dos Cmd window, rather than PPM3, which is installed to the start menu by default. This has solved an issue for me which seems very similar to the one you have encountered. If this doesn't work, try posting to the ActiveState ppm list -- I'm Not Just Another Perl Hacker	[reply]
Re^2: ppm giving "Permission denied" error by Anonymous Monk on Jul 26, 2004 at 06:27 UTC
Actually I used ppm from the command line. Was the error message something like this? Can't remove directory C:\blahblah : Permission denied ar C:\Perl\site\lib\PPM\Repository.pm line 247 Error: (un)install script failed: 'C:\Perl\bin\perl.exe install_script	[reply]
Re: ppm giving "Permission denied" error by fizbin (Chaplain) on Jul 23, 2004 at 15:28 UTC
In addition to the advice to use a dos-based PPM, make certain that you don't have any processes which have open some file that needs to be removed - for example, check that notepad does not have any of those files open, that you do not have an explorer window open to that directory, that you aren't using IE to look at anything in that directory, etc. I have often found on windows that the key to fixing any kind of permission denied error is tracking down the application that has the file open and closing it. `-- @/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/; map{y/X_/\n /;print}map{pop@$_}@/for@/` [download]	[reply] [d/l]