IIS 7.5 debugging errors in ASP, PHP pages...

Hello everyone,

I recently upgraded from IIS 6/Win 2003 to IIS 7.5/Win 2008.

Im getting a bit annoyed because even very basic errors such as a wrong DB connection or parent paths disabled, with both ASP and PHP, show an unclear Internal 500 error (or 4xx). I have to do procure with "Failed Request tracing rule" on the site to get the details.

Ive tried things such as, in the case of ASP, asking to show errors on client and server... Or when accesing site via IE disable the friendly errors. But nothing helps.

Please, how can the customers get clearer errors so its lower our workload and they can find out about specific errors themselves? Can someone pls advise on exact procedures?

Thank you!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brad HoweDevOps ManagerCommented:
It is odd that you are not getting ANY errors.

Confirm you have set the following.

1. Disable IE "Friendly HTTP Error Messages" on the client side
Go to “Tools > Internet Options”, choose the Advanced tab, and clear the “Show friendly HTTP error messages” checkbox.  Then, close the browser, open it again, and re-request the page.

2. Detailed error logging on the website Server Side

Try the following. From IIS Management, selecting your website/application/virtual directory in the left-hand tree view, clicking on the “Error Pages” icon, clicking “Edit Feature Settings” action, and then selecting “Detailed Errors”.

IIS> Sites > Website > Error Pages > Edit Feature Settings > "Detailed errors"
IIS> Sites > Website > ASP > Debugging Properties > Send Error to Browser = True

viperman67Author Commented:

It helped once, but now for example I have a situation where its not helping. What exactly makes PHP for example errors show clearly?

Also, how can I make it by default be set to show clear errors for everyone? There doesnt seem to be a master site like IIS6. Is it in application host config file?

Here's an example

internal error - http://screencast.com/t/oOTrY99VT3

trace logs indicate double php mapping - http://screencast.com/t/vJemDR4OSstU

I did all procedures you mentioned, but it remains showing an unclear Internal error. I had to use TRACE logs to find the site has a double PHP mapping causing the issue.

viperman67Author Commented:

We had success, basically, in the master site:

- HTTP features/ERROR pages, on right side click on Edit feature settings and choose "Detailed errors".

- Application development/ASP icon. Debugging properties, send error to browser TRUE.

Thanks to Rafael Cresci. The other day a bunch of sites were down with the nasty internal error, we did the above and the error changed to  "could not connect to DB", making it much easier to troubleshoot.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.