At my last job we had a local, in-house written program that ran on IIS. It was a typical n-tier web front-end with a database back-end. The guy that had the job before me wrote the app, but because he was more of a UNIX guy, he wrote the .asp in PerlScript (not vbScript) which was somewhat unusual, but worked fine.
The problem:
The guy that replaced me at this job called me up and said that a power surge blew the server, and he had to set much of it up again (and apparently did not have a back-up of the IIS config). I went over to give him a hand, and we got all of the virtual directories for everything else set-up (typical stuff- intranet, webmail, etc...), but we could not get this PerlScript app to run.
My gut feeling is that we need to link a Perl interpreter to the script files (which, while being written in PerlScript, are still .asp extension). We did get an error page from the virtual directory, but it was generic, and didn't really reveal too much.
Anyone have any ideas?
Thanks
"I would rather have a free bottle in front of me, than a pre-frontal lobotomy..."
-Shrubble
The problem:
The guy that replaced me at this job called me up and said that a power surge blew the server, and he had to set much of it up again (and apparently did not have a back-up of the IIS config). I went over to give him a hand, and we got all of the virtual directories for everything else set-up (typical stuff- intranet, webmail, etc...), but we could not get this PerlScript app to run.
My gut feeling is that we need to link a Perl interpreter to the script files (which, while being written in PerlScript, are still .asp extension). We did get an error page from the virtual directory, but it was generic, and didn't really reveal too much.
Anyone have any ideas?
Thanks
"I would rather have a free bottle in front of me, than a pre-frontal lobotomy..."
-Shrubble