Recently, because of the relationship between a project, use it back to ASP. The code of this project is very chaotic, often 500 errors, return an error page, and there is no specific prompt to make mistakes, people are very headache. After a few days, I also have some grasp of the law of 500 errors, and organized as follows.
1. Error INCLUDE. If INCLUDE is in the page, this page does not exist or path errors, often 500 errors
2, do not match the loop or process control statement, this often appears, in a more complex page, there will be more than one NEXT or LOOP, and will be 500
3, <% and%> do not match, I have encountered several in these two days.
4, some unfill statements, such as DIM SQL, SQL2, if there is more comma, will be 500
5. Execute some actions that will produce an exception. If you delete a no file, because the ASP basically does not support the abnormal processing, this is generally 500 in this case.
Add ...
