If you encounter a generic error such as HTTP 500 - Internal Server Error when accessing an ASP page, this is almost always caused by an issue within your ASP code rather than a problem with the hosting server. By default, Internet Explorer hides detailed error information, making it difficult to diagnose the root cause.
To properly debug ASP errors, you must disable Internet Explorer’s friendly HTTP error messages. This allows the browser to display the full server-generated error output.
Why ASP Error Messages Are Hidden
Internet Explorer replaces detailed ASP error messages with simplified pages to improve the browsing experience. While helpful for end users, this feature prevents developers from seeing:
- The exact ASP error description
- The file path where the error occurred
- The specific line number causing the issue
How to Show Detailed ASP Error Messages
- Open Internet Explorer
- Click Tools then select Internet Options
- Open the Advanced tab
- Scroll to the Browsing section
- Untick Show friendly HTTP error messages
- Click Apply and then OK
Once this setting is applied, reload the ASP page. The browser will now display the full ASP error output, including the exact line number and code reference that caused the failure.
Common ASP Errors You May See
- Microsoft VBScript runtime error
- Object required
- Type mismatch
- Permission denied
- Invalid procedure call or argument
These errors typically indicate missing objects, incorrect variable usage, file permission issues, or syntax errors within the ASP script.
Additional Troubleshooting Tips
- Verify file and folder permissions are set correctly
- Ensure required components and DLLs are installed
- Check database connection strings
- Confirm all included ASP files exist and are accessible
Security note: Friendly error messages should be re-enabled after troubleshooting to avoid exposing sensitive error details to visitors.