This does not necessarily mean that the server is misconfigured; in fact, it usually means that a CGI script you have installed is not functioning correctly due to a scripting error, and the server is detecting this. Common causes are: the file is not executable, there is a malformed header, or it is has an incorrect path reference when using a server side include. If you're using a server side include, the path format is usually the cause. See the Apache and NCSA httpd home pages, the comp.

First, check the end of your error_log file which is present in your logs/ directory. If it shows a "Premature end of script headers" message for your CGI script, make sure that you have uploaded the script in ASCII mode from your FTP transfer program, and that if it is a perl script, the first line reads "#!/usr/bin/perl".

This (rather useless) error message generally means that your webserver tried to execute the program, but execution failed. This is most likely to be caused by the Perl program not being valid Perl. Perl tries to run your program, finds an error, and throws up warnings. The webserver interprets these warnings as output from the CGI which it can't understand, and throws out an Internal Server Error.

This error happens due to a bug in librsync that prevents it from handling files greater than 4 GB in some situations, such as when transferring between a 32-bit host and a 64-bit host. A patch is available from the librsync project page on Sourceforge. The CVS version of librsync also contains the patch. More information is also available in Debian bug report #355178.

quot;Could not login. The specified user name does not exist in the system." - This means that your Blackboard account has yet to be created. Often this is because you just enrolled in a class, and the process for creating your Blackboard account hasn't been completed, or you are enrolled in a class that is not using Blackboard. quot;Could not login.

Only one in ten thousand "Internal Server Errors" are actually caused by a server fault. Most likely, your script has a bad permission (a.k.a. CHMOD) setting, error statements and/or a wrong path to the PERL intepreter. Fix the problem and you'll soon realize that the error is actually not caused by the server in any sense.

First check here (in Student Web Server Upgrade to Apache 1.3 ) to see if your problem is because of Apache 1.3 slightly silly directory permission requirements. If not, you can get hints about what's really going wrong by looking in /software/wwwapache-1.3_server/logs/error_log /software/wwwapache-1.3_server/logs/access_log /software/wwwapache-1.3_server/logs/cgi.

Below is a list of the main error messages you will see while searching the Wayback Machine. If you see an error message that does not have the Internet Archive Wayback Machine logo in the upper left corner, you are most likely looking at an archived page or the live web. Failed Connection: The server that the particular piece of information lives on is down. Generally these clear up within two weeks. Robots.txt Query Exclusion: A robots.

Yes, every account comes with its own cgi-bin and you can install your own CGI scripts. Be sure that the scripts conform to the provisions in our Acceptable Use Policy and that you set the mode (chmod) on them to 0755 (rwxr-x-r-x) so that they will run.

First, make sure that the permissions on the file are set properly for execute permission. By default, the permissions are 644 (rw-r--r--) and do not allow execution. You need to change the permissions, or the mode, on your cgi script to 755 (rwxr-xr-x). Some FTP programs allow you to change file permissions, if yours doesn't, then you can use the File Manager in your Control Panel to change the permissions.

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.

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.

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.

This means that the script is failing before getting a chance to output any data. Look at the error log of your web server for any error output produced when the script is run, and see section 4.6 (above) for suggestions on what to do if your web server doesn't log meaningful error output.

Each server comes with it's own unique CGI bin directory. Access to the directory is through Telnet or FTP. We also have many other CGI that you may add by simply copying into your own cgi-bin directory.

Applications using a UNIX-style build process will typically require a shell environment and set of POSIX tools, for executing configure scripts and building the application. The Cygwin environment was once the only choice available to fill this role, although recently the MSYS environment was released to offer MinGW developers a more lightweight alternative. The use of both these environments with MinGW is described in more detail below.

There is an error somewhere in your ASP pages, but Internet Explorer is hiding the real error message from you. To turn this off, select Options from the Tools menu, select the Advanced Tab, and scroll down until you see "Show Friendly HTTP Error Messages". Uncheck the options and press OK. On refreshing your erroneous page, you will be able to see IIS' explanation of your problem.

This message indicates a serious problem. Please send a message to directory@mtu.edu if this message persists, or try again at a later time.

If you are using Microsoft® Internet Explorer, Click on the Tools menu of Internet Explorer and select Internet Options... The Internet Options dialog will be displayed. Click the Advanced tab at the top right of the Internet Options dialog. Uncheck the "Reuse windows for launching shortcuts" item. Click the OK button to save the setting and dismiss the Internet Options dialog.

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.

When sending signalling data, for instance in an MTP-2 monitoring application, some information about sockets going down is logged. This is intended for internal use, but they might be of some use when solving problems. The possible messages are: This happens if an attempt to write a socket failed with an error.

SMTP authentication is required In order to prevent spamemrs from accessing the outgoing mail server and using your account to send spam. Run through the mail settings of the e-mail client you are using and make sure the Account Name is set to your username (all lowercase) and password is correct by deleting it and retyping it in

Under normal circumstances, the Apache access control modules will pass unrecognized user IDs on to the next access control module in line. Only if the user ID is recognized and the password is validated (or not) will it give the usual success or "authentication failed" messages.

CGI (Common Gateway Interface) is a process used by the server to pass information between the user and an application on the server. With CGI access, you can install Perl scripts on your website for such things as feedback forms, guestbook, counters, and so on.