teenzbutler said:
I want to thank you all for your positive feedback LOL...
Let me explain:
1. The President of my company wanted the abiilty to view
his month-end reports while away from the office (8
reports in total). The files are company-sensitive Excel
spreadsheet that were converted to HTML.
2. To protect the material, I created a secure logon
using ASP. To secure the files, I had to convert them to
ASP
3. 7 of the 8 reports are working perfectly. The large
one (10mb), however, is giving me problems.
The true HTTP error is:
HTTP/1.1 500 Server Error
No it isn't. You did not read the page whose link I posted. Do you not have
internet access? Here, I'll post the text:
Why do I get a 500 Internal Server error for all ASP errors?
http://www.aspfaq.com/2109 created: before August 2000
last updated: 2003-12-24 20:09 this article is printer friendly
You might be finding it difficult to debug ASP errors in a
browser. This is because IE5 has a ridiculous default 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."
After you've disabled this default setting, refresh the page in
question. There are four possible outcomes: (1) the page will magically work
again; (2) the page will give you a more detailed error (e.g. Stack Overflow
or Syntax Error), including a line number; (3) you will get "Server
Application Error" - which means that at some point IIS got confused about
the current application; or (4) you will still see non-descript error
messages.
If (3) is what happens, you can remedy this simply by going into
Internet Services Manager. Right-click the application in question (or
Default Web Site, if an application is not relevant), select properties, hit
the "Home Directory" tab, click the "Remove" button, and then click the
"Create" button. Follow with Apply/OK etc and get out of Internet Services
Manager. Refresh your page, and all should be well again.
If (4) is what happens, open Internet Services Manager, go to
the home directory tab of your default web site or application, click on
configuration, go to the Debugging tab, and make sure "Send detailed error
messages to the client" is selected. Click Apply/OK/OK etc. to get out of
there and try your page again.
If you are still getting errors like 'page not found' then go
into Internet Services Manager, right-click Default Web Site, choose
Properties, and on the Home Directory tab, click the Configuration button.
On the App Debugging tab, make sure "Send detailed ASP error messages to
client" is selected.
Page not found errors can also be cause by the IIS Lockdown
wizard. Or, in Windows Server 2003 / IIS 6.0, a misconfigured Application
Server (see Article #2147 for information on configuring your application
server to allow the server to process ASP files).
Finally, check the event log, as occasionally there is more
information there than you will see in the browser. Of course this is even
more likely if you can't change the IIS or browser configurations.
See KB #261200 and KB #311766 for more information.
Bob Barrows
