That is a generic and largely unhelpful error, similar to the 500 on Apache. What this most likely means is the script is either 500 erroring (an actual error) or it's just not outputting anything (just dieing.) On any request, a script must print a content-type header and output something to STDOUT (i.e., send a response back to the browser.) How you'd get to the root of it . . .
First, was it on Linux before? The windows environment is different for windows servers, especially in respect to permissions. Perl scripts need to be set executable, and chmod is not a Linux command. So you'll have to log in to your hosting CP to set those executable. If there are any files that need to be written, they need to be in a directory that is writable.
Next, always know what the environment variables are or even if you can execute scripts "from where you are" (this is particularly fussy on windows servers.) Add this little script somewhere - but REMOVE it as soon as you have the info:
If this won't run - see comments about executable. Once you get the envars script running, one of the important ones to note is DOCUMENT_ROOT. This is the full path to your server's root, and may be incorrect in your script configuration - open any config files to verify.
Last, once you get the environment variable script running, without access to error logs or other tools, you can begin debugging like so. Add the following three lines somewhere near the top of the script after #!/usr/bin/perl
thank you rocknbil, i will try that code. this was hosted on a windows server for aboit 5 years without any issues. they forgot to renew it and the host canceled their account. now they set it up on netsolultions on a windows server.
they tell us that our scripts have issues but... how can that be if they ran for years. the old host no longer does windows on linux so they had to do netsol who claim they have no logs to show on a hosted account.