You need to enable error messages in your browser. In IE, go to TOOLS , INTERNET PROPERTIES, ADVANCED tab, UNCHECK "show friendly HTTP error messages" This will allow your browser to show error lines and descriptions instead of the 500 Internal server error.

The HTTP error 400, bad request, means that the Web server received a request that it could not process, because it is not configured to do so, or because it expects certain headers or parameters in the request that are not present.

This is the most general CGI error message you will come across and has a number of causes. Please check the following points: Ensure that your script was ftp'ed to the webserver in ascii mode. If not, your script will be transfered with control characters added to it. You may have specified a mail program that does not exist or resides in a different directory to the one specified in your CGI script. Edit your CGI script and make sure that the mail program is specified correctly.

Internal Server Error 500 is a generic error that covers a multitude of issues. To see the real error message, you need to disable friendly errors in your browser options. To disable friendly error messages, in your browser (assumes IE), select Tools > Internet Options and click Advanced. This error means 'Permission Denied' and is typically caused by incorrect permissions being given on your server. To prevent this occuring, you MUST ensure your server account (e.g.

This is a general error Internet Explorer shows when something is wrong. To find out exactly what the real problem is you need to turn off Show friendly HTTP errors in Internet Explorer's settings to see detailed information about the error. Do this by going to Tools -> Internet Options -> Advanced -> and scroll down to Show friendly HTTP errors and uncheck it. Click OK to apply the changes. Close out your browser and start it up again to make sure the change takes effect.

EZProxy delivers error pages to users for certain common problems. These will usually have the libraries' header and information relevant to explaining the problem and solution. There are a variety of common errors that occur during general surfing of the Internet. When they occur, the web server (or web browser) sends an error page for you to view - usually without a lot of explanation. These may or may not be related to EZProxy.

I keep getting "THE REQUESTED URL COULD NOT BE RETRIEVED..." when I try to run any software script from CGI Connection

This probably means that your picture is taking too long to upload. Your file might be too big. You should make your file smaller.

This usually means that the server your picture is hosted on is too slow. In this case, we recommend you find another place to host your photo. The only reason your picture would be rejected is if you tried to upload something that is unappropriate.

This probably means that your picture is taking too long to upload. Your file is bigger than the maximum allowed size of 10MB. You should make your file smaller.

When there is a glitch in the server you will receive this error. The server checks itself every minute and if it finds a problem it restarts. If you'll wait a few minutes and try your access again, the problem should clear itself up.

There are many different possibilities. If you have a problem, misconfiguration, or syntax error in you script, you will probably be able to find it by checking your error logs which can be found in your your control panel under "Statistics -> Show Error Logs". Although this is generally caused by a problem within the script, many times it is caused by incorrect file permissions either on the script itself, or another file or directory used by the script.

A Web server (external website) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. a Web browser or web server's CheckUpDown robot) for access to the requested URL. This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. It is up to the operators of the Web server site to locate and analyse these logs.

The Path to Perl or CHMOD of your file or directory may be wrong. Try CHMOD all the files and directory again. Your server may not like the CHMOD setting ask you host what you should be using. Check you did not open the script with anything other than notepad. Check your log to find out more. Also try putting the code below directly after your Path to Perl this will stop and report the script error in more detail.

The Unlocking Generator checks 3 things. Your IMEI; which is run through a genuine check (more info below). Your Country; which displays the service providers in your country. And Finally to check if you have agreed with the terms and conditions (check the box). Try: Looking under your phone's battery for your IMEI, if it differs from the one returned by *#06#, please contact your place of purchase. And/Or using another Browser.

Make sure you are going to http://courses.sxu.edu/. If you type "http://www.courses.sxu.edu/", you will get the "Page cannot be displayed" error. You are not currently connected to the Internet. If you use a modem (not a cable modem) to connect to the Internet, you might try reconnecting. If you cannot login with your username and password, please contact Nubi Achebo at ext. 3884 or via e-mail at achebo@sxu.edu

When trying scripts this is usually because the script has failed to run normally because of an error in the configuration file. Check your configuration files and if possible the server log files. These should point you in the right direction. The spreadsheets may be used or copied freely the password is to protect the sheets from accidental damage by users not to keep people from changing or seeing the formulas and code.

All scripts are limited in the amount of CPU they can use. If your script is too CPU intensive, or runs for longer than 20 seconds, it will be shut down, giving a 500 error.

A common reason for a script file being invalid is that it was produced on another operating system, and then uploaded to the web server. If the operating system uses the sqeuence of carriage-return (hex 0D) followed by linefeed (hex 0A) then a UNIX web server will typically not like the first line of the file which is supposed to cause the appropriate processing program to be invoked.

Answer: 500 errors are typically something wrong in the syntax of your script. Most often times you should check to make sure you have the path to PERL correct. Currently we are running Perl5 on our servers. The correct path to PERL is: #!/usr/bin/perl

If you have just recently set up your hosting account with us, your site DNS records may not have fully propagated yet. It generally takes 24-72 hours for all the root servers around the world to update any changes in your DNS records. If you have a name based hosting account, try pointing to http://yourIP/~username using the IP and username provided in your Activation Email. If you have an IP based hosting account, try pointing to http://yourIP.

You are getting this error because all PHP and Perl files must have permission set to 755. You can change the permissions of the files through the File Manager inside the Control panel or through FTP. Once you set file permissions to 755 PHP/Perl will be working fine. To change file permissions through FTP select the file and use the commands: "chmod 755". Or you can use the File Manager for the purpose.