Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Displaying error messages

Status
Not open for further replies.

jdgonzalez

Programmer
May 11, 2004
72
US
I not new to web development, but I'm new to ASP and I've run into an odd problem (at least for me). It seems that sometimes when the page errors out I get a 'page cannot be displayed' instead of seeing the actual error message. It's almost as if I'm trying to load the wrong page. But if I go into the code and write an obvious error like delete a 'then' in an if block and refresh the screen it starts to provide error messages.

As you can imagine this makes troubleshooting error message a real pain. Has anyone else run into this and can provide a possible solution?

Thanks
 
Did you uncheck "show friendly http error msg" & "disable script debugging" box in IE tool/internet options?
 
It would be my luck for it to be something this easy. I'll give it a shot to see what happens. The 'show friendly error messages' box was checked.

Thanks!!!
 
If it's a syntax error, you will get the error mesg no matter what. If it's logic error, you need to turn off the "show friendly http err msg" in order to the err msg.
 
If the page is timing outthen the error is likely something like an endless loop. The error being sen onthe browser is because it timed out while waiting for its page request to be filled. So according to the browser there isn't necessarally an error on the website, it's just that the server never delivered anything to it.
One way to get th portions of your page up to the error portion tht is causingthe timeout is to turn off theResponse buffer (or make liberal use of Response.Flush statements). This forces the server to send portions ofthe HTML as they are created by the ASP page raher than buffering them. The downside of this isthat it causes the script to take longer to execute and send to the end user because instead of sending a big chunk of data all at once you are sending little squirts of data, causing more overhead during the data transmission (ie, many less than full packets being sent to the client) and more overhead frthe browser as it tries to render the incoming data in small chunks.

-T

01000111 01101111 01110100 00100000 01000011 01101111 01100110 01100110 01100101 01100101 00111111
The never-completed website:
 
Tarwn,

I was thinking the same thing with respect to the endless loop thing, but the error would just be a simple syntax error. Since disabling the friendly error messages, I haven't seen it give me a 'page cannot be displayed' message. I hope that's what it was.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top