People still use PERL?

hehe - sorry...

seriously...99% sure it's a permissions or pathing problem - that's the ONLY thing I can remember frommy days in PERL - it's very peculiar about permissions and paths.

Double, triple and quadruple check your paths within your scripts, to PERL and make sure that eveything is uploaded in ASCII and has the correct modify permissions assigned to it.

And when all else fails - upgrade to ASP.NET

Perl is NOT particular about permissions. Paths, somewhat, no more than anything else.

That being said your Web Server may refuse to run the perl script without the correct permissions.

Perhaps I shoud have said Linux is very particular about paths and permissions....

if your perl script doesn't run at all, then most like you have the wrong path to the perl executable. you mentioned it did run on another host, however it errored out midway through. if the code is known to be good, then most likely it's a permissions error. if you know what files, if any, your script is modifying, or what it is doing, then you can check the permissions on the respective files and get it up and running once again.