[thelist] Interesting maybe IIS/ASP maybe authentication erro r SOLVED, BUT WAIT.....

[Jay Blanchard]

[snip]
In Internet Explorer, please do:
Tools -> Internet options -> advanced -> uncheck "Show Friendly HTTP Errors"
Reload the page.
What error message do you see now?
[/snip]

Ya ain't gonna' belee dis!

Either Ken knows some weird Internet Exploder magic (more precisely voodoo)
but the error that appears after unchecking "Show Friendly HTTP Errors" is
no error at all, it is the expected web page. 

I would have expected that turning this off would have provided a more
verbose reason as to what the error was, and I should have expected it
according to;

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807 

However, clearing the checkbox fixes this particular user's problem. I did
confirm that you get a more verbose message when this option is cleared and
a proper error is introduced.

I should be satisfied that the issue has been resolved, but I am a little
uneasy. This particular action should not have corrected the issue at all,
just given me more information. Is this a known work around? After Googling
the phrase I found nothing that hints that this might be a solution for this
kind of issue, except for one small entry in;

http://www.aspfaq.com/show.asp?id=2109

[quote]
You might be finding it difficult to debug ASP errors in a browser. This is
because IE, versions 5.0 and up, defaults to a ridiculous option that
suppresses errors to a more "friendly" error (which, IMHO, is a lot more
cryptic than what they'd get otherwise). This comes back to the user as a
500.100 Internal Server Error (ASP 0147), and in certain scenarios a 404
Page cannot be found error, and doesn't leave the user much information to
pass on to the webmaster, except to tell them that "The page cannot be
displayed." 
 
To circumvent this silliness and get real ASP errors, go to IE's
Tools/Internet Options menu, and on the advanced tab, uncheck "Show friendly
HTTP error messages." 
  
Hit Apply, OK, and refresh the page in question. There are five possible
outcomes; the page will either:
still yield cryptic and unhelpful error messages (e.g. Page Not Found); 

stop processing where the error occurs, and leave the rest of the page
blank; 

return "Server Application Error";  

give you a more detailed error; or, 

magically work again.
[/quote]

Thanks Ken...and Happy Holidays!