Title: General Help: "Internal Server Error" or "Error 500"
I am getting this error when running the script.

Internal server error (Error 500) is usually due to one of these:

• The script is not chmoded properly
If the script is not chmoded properly, it is not executable.

• The script is corrupted
Maybe the original codes were messed accidentally when you tried to edit the variables in the script. For example, you accidentally deleted a quote mark or semicolon around the values (variables) you were asked to provide.

- If you have telnet access to your server, please see the "How to troubleshoot the configuration errors" section.
- See also the "12 most commonly-made CGI mistakes" section.

• The server does not allow CGI scripts to be executed
Some hosting ISPs do not allow you to run CGI scripts and some require special (non-standard) procedures. In this case, please contact your hosting ISP.

• The server does not allow CGI scripts to be executed outside cgi bin (or its subfolder)
In this case, you have to install the scripts in the cgi bin.

• The server in general is not properly configured
If you are so unlucky, please contact your hosting ISP.

• Bad Perl location
The command interpreter (the first line of the script that specifies the location of Perl, usually looks like #!/usr/bin/perl or #!/usr/local/bin/perl) is wrong or not located at the very top line of your script. If it is even one line down, it won't work. It must begin with #!/

• Broken long lines
You edited the script in a text editor that broke long lines when the script was saved. Your text editor must never break lines with hard returns.

• Missing backslash (\) before the @
For example, an email address should be "mail\@domain.com" and NOT "mail@domain.com"

• Wrongly uploaded in BINARY mode
You must upload scripts and its data files (if any) in ASCII mode. Do not use MS-FrontPage or any other HTML editor to upload Perl or data files to your server. Always use an FTP client such as WS_FTP or CuteFTP.

• Missing # sign
Missing # sign in front of a comment line.

  Powered by Document Publisher