ODBC errors not showing in IIS7

hi all,
i've recently set up a server running IIS7... all error messages are set to send to browser and VBScript errors are displayed the same as in iis6 etc...
my problem is that whenever there is a error which is database related (creating a recordset or displaying field contents) then no error is given, the page simply stops loading...
this means that if the problem is in creating a recordset then you just get a blank page... if the problem is in the midst of html markup at least then a 'view source' shows you where the error occured...

i'm currently using "on error resume" to get past the error and

If Err.Number <> 0 Then  
response.write Err.Number &""& Err.Description
End if

to find the error, but when you have several recordets or lots of code it still makes debugging a very slow process...

so, does anyone know how to get back ODBC debugging?

btw, i'm using classic asp...
Who is Participating?
Praveen DMConnect With a Mentor Infra Team LeadCommented:
1) Turn Windows futures on or off under Control Panel\Programs\

Under Internet Information Services > Web Management Tools
  Switch on IIS Management Console/Management Scripts and Tools/Management Service

Under Internet Information Services > World Wide Web Services > Application Developement Features
  Switch on all features

Under Internet Information Services > World Wide Web Services > Common Http features
  Switch on Default Document and Static content (can now see image in iistart.htm welcome page)

Under Internet Information Services > World Wide Web Services > Security
  Switch on Basic Authentication, Request Filtering, and Windows Auhentication

2) Run Internet Information Services (IIS) Manager under Control Panel\System and Maintenance\Administrative Tools
Double click on the ASP icon

Under Behaviour
  Set Enable Parent Paths to True (so as not to change existing ASP code)

Under Debugging Properties
  Set Errors To Browser to True
dog_starAuthor Commented:
sorry for the delay in replying...

couldn't find some of the options you mention in 1)

2) already set "errors to browser" but it still doesn't display them... the only way i've found is to use ASP script to display the error, which isn't very efficient...
dog_starAuthor Commented:
as a follow up i eventually found this fix :

run the following at the CMD prompt :

%windir%\system32\inetsrv\appcmd set config -section:asp -scriptErrorSentToBrowser:true

this seems to do the trick...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.