DiscusWare, LLC.
Download Purchase Contact Us
Home
Support Home Documentation Knowledge Base Support Forums Support Request Advanced Services
"500 Internal Server Error" message

General procedures for diagnosing a 500 (Internal Server Error) message.
Support Site Search
 

We have developed some specific documents to help you diagnose this error message. Please look carefully at the following list and see if your situation is one of those we have specifically documented. If not, please continue reading for general pointers.

If none of the above documents helped you, it is likely that the internal server error is occurring only when you access specific functions of your board. The following is the general procedure for diagnosing this problem:

  1. Access your diagnostic script to make sure all files are properly uploaded and that there are no problems with your setup or permissions. Click here to learn how.

  2. If you have Discus 4.1 or higher, Discus itself will create and maintain its own error log on most servers. When such an error occurs, it is presented as a "Software Error" and a reference number is provided. If you see this error, please read about the Software Error message.

  3. If your diagnostics do not shed any light on the problem (or diagnostics itself comes back with a server error message), you may have discovered a problem with the Discus program. Contact our support division with the URL to your board, version number, whether it is freeware or pro, the exact description of what you were doing when you got the error, and any relevant entries from your server's error log.

  4. If your server does not offer you an error log, you may be able to use the "CGI" perl module to generate one for yourself, if you have Discus 4.0 or higher. We have instructions on modifying scripts to produce an error log.


Download Purchase Contact Us
Privacy Policy
Copyright © 2005, DiscusWare, LLC, All Rights Reserved