When errors occur in the JScript program running on Bivouac, you are supposed to see the actual JScript error. But some browsers like Internet Explorer instead try to hide these JScript errors, and instead report a "friendly" message such as "Page cannot be displayed". These friendly messages are useless to you in trying to figure out the problem.
For example, a typical underlying error message that Microsoft hides is shown below:
Instead, they simply tell you the page can't be displayed.
"Microsoft Jet Database Engine Error: The field is too small
to accept the amount of data you attempted to add.
Try inserting less data."
Mtn.asp line 127
I constructed a deliberately broken page so you can test if you are getting proper error messages. To test the difference between the two error display modes, click the link below, once with "Friendly Messages" turned on, and once with it turned off. When you click on the following page, you should see a message that says there is an error. The message will look something like:
Microsoft JScript compilation error '800a03ec'
/TestErrorDisplay.asp, line 6
This is an error
Now test your browser to see if you get the above message:error test page. If not, keep reading.
As of 2015, fortunately most browsers seem to show proper error messages by default. However, you can search in Google for your particular browser if you don't think you are getting the full error message. For example, search Google for "Turning off friendly HTTP error messages" in Firefox"
Below are my notes on a few browsers that I have tested:
The option you want to change is called "Show Friendly HTTP Error Messages". Uncheck the box so you see the underlying error message. The option is under a subheading called "browsing".
Tools > Internet Options > Advanced
Now test it by clicking on the deliberately broken link error test page. You should see it reporting an error in line 3 of this page.
[ ] Show Friendly HTTP error messages
Netscape does not need this adjustment, by default it shows you the actual error message.
2014.12.18 Works same way in IE Version 11 (on 2012 server)