When we built sites in NT with ASP pages, if something was wrong, we would 

get back a useful detailed error message from the server.  Now we just get 

http 500 errors.  It now takes me 3-4 times as long to do anything.  

Something as simple as not terminating a string properly will cause a 500 

error.  On a page with 1500 lines of code, this can cause brief moments of 

insanity followed by rage.  My hair line has receeded 2 full inches since 

migrating to Win 2000.



Please tell me there is a way to get detailed error messages again.

> When we built sites in NT with ASP pages, if something was wrong, we 

would 

> get back a useful detailed error message from the server.  Now we just 

get 

> http 500 errors.  It now takes me 3-4 times as long to do anything.  

> Something as simple as not terminating a string properly will cause a 

500 

> error.  On a page with 1500 lines of code, this can cause brief moments 

of 

> insanity followed by rage.  My hair line has receeded 2 full inches 

since 

> migrating to Win 2000.

> 

> Please tell me there is a way to get detailed error messages again.





I found the answer to my own question.  The "Show friendly http errors" 

checkbox in the advanced tab under tools->Internet Options must be 

unchecked.



What had happened was that since before when we developed web 

applications, the server was NT and my machine was/is windows 2000 

professional, the client didn't recognize what was coming from the NT 

server as an error and displayed the full message.  Once we updated the 

server, the client could better understand the error message and would 

replace it with the "friendly" http 500 error.  Whoever decided that IE 

needed this feature is a jackass.  The browser should display what the 

server sends it and not try to make my life better by protecting me from 

scary error messages.



Someone please tell Bill Gates he owes me 2 inches of hair plus lost wages 

for time spent