here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://stackoverflow.com/questions/16161525/iis-7-error-500-internal-server-error-in-asp and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/1453791/classic-asp-on-iis7-refusing-to-send-errors-to-browser-on-500-internal-server-e the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it internal server only takes a minute: Sign up IIS 7 error 500 internal server error in asp up vote 1 down vote favorite I am having a asp web application running through IIS...If i insert data in a form from my system..The application connects to SQL Server 2008 and insert data.. i am able to insert...if i do the same process through internal server error my network systems ..i am getting error as "500 - internal server error. there is a problem with the resource you are looking for, and it cannot be displayed"..How to overcome this ? iis-7 asp-classic share|improve this question asked Apr 23 '13 at 5:19 Affan 1392214 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote First, you will have to activate Detailed Server Errors (see Classic ASP on IIS7: refusing to send errors to browser on 500 Internal Server Error for instance), to see what causes the error. It may be a DB error, but it could also be a script syntax error or something else. Classic ASP is not compiled, so even simple syntax errors show up only when the code is executed. share|improve this answer answered Apr 24 '13 at 6:36 gpinkas 1,28721329 add a comment| up vote 1 down vote First check you could connect to SQl2008 successfully with the credentials you gave in your asp application. Then check if the user has got permissions to insert data into the da
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Classic ASP on IIS7: refusing to send errors to browser on 500 Internal Server Error up vote 48 down vote favorite 4 I have classic ASP running on IIS 7. Even though I configured the ASP "Debugging Properties" to "Send Errors to Browser = True", the web app REFUSES to send errors to the browser and continues to send a 500 internal server error. My browser has "Show Friendly HTTP Error Messages" unchecked. Failed Request Tracing is installed (not sure if that's related) Happens both on web pages loaded locally on the server and remotely The App Pool is integrated (not sure if that matters) Any ideas? iis-7 asp-classic iis-7.5 share|improve this question edited Oct 18 '12 at 18:57 lsalamon 5,38043048 asked Sep 21 '09 at 10:17 Matias Nino 2,010103958 add a comment| 6 Answers 6 active oldest votes up vote 79 down vote accepted Try : Internet Information Services (IIS) Manager --> Default Web Site --> Click Error Pages properties and select Detail errors share|improve this answer edited Dec 2 '11 at 15:53 answered Sep 21 '09 at 15:16 lsalamon 5,38043048 I also had to convert my virtual directory into an Application –Matthew Lock May 5 '13 at 3:47 add a comment| up vote 6 down vote I had this occuring on a Classic ASP application running in a subfolder of a site. The solution was: IIS > Click into your Site > Click into your Application folder > Error Pages > Edit Feature Settings > set to: Detailed Errors share|improve this answer edited Jan 28 '15 at 11:40 answered Jan 20 '14 at 12:49 James McCormack 6,58133450 add a comment| up vote 3 down vote I was having the same issue with a Classic ASP app running in a subfolder of a site. I had enabled detailed errors and the 500 was still showing. My resolution was to enable parent paths in the ASP section in IIS for the site as the application was referencing the parent folder using "../": share|improve this answ