Classic ASP Sending errors to browser does not work on IIS7 for remote connections

Question

I can’t get detailed error reporting for IIS7 for ASP pages on a remote browser connection. However, when I run the page locally on the server I do see a detailed error message.

I have enabled Send Errors To Browser but IIS keeps sending an internal server error.

I have unchecked show friendly HTTP error messages on IE.

Does anyone know how to enable error messages to be sent to a remote browser?

score 28 · Answer 1 · edited Oct 08 '12 at 08:28

28

If "Send Errors To Browser" is not working set also this:

Error Pages -> 500 -> Edit Feature Settings -> "Detailed Errors"

edited Oct 08 '12 at 08:28

Andrew

12,991
15
55
85

answered Mar 29 '11 at 15:23

Casper

281
3
3

You do not need to select "500" or anything other. "Edit Feature Settings" is independent of the selected status code. – Uwe Keim Apr 28 '23 at 15:35

score 12 · Answer 2 · answered Oct 14 '10 at 10:05

There is an ASP setting you need to change in IIS 7

Under the IIS heading, open the ASP properties, and under Compilation, expand the Debugging Properties, there you'll find:

Send Errors To Browser

Set it to True

As you've already done, you need to disable the show friendly HTTP error messages in IE.

score 9 · Answer 3 · edited Nov 26 '15 at 11:15

9

IIS
  - Error Pages
      - Edit Feature Settings
        - Check: Detailed errors

IIS
  - ASP
    - Compilation
      - Debugging Properties
        - Set: Enable Server-side Debugging = False
        - Set: Send Errors To Browser = True

In my case Server-side Debugging was on and it was not displaying error details on remote side. It started showing error details as soon I set Enable Server-side Debugging = False.

edited Nov 26 '15 at 11:15

krlzlx

5,752
14
47
55

answered Sep 16 '13 at 22:05

user1720604

91
1
1

`Enable Server-side Debugging = False` was the solution for me too. – krlzlx Nov 24 '15 at 15:51
this is the only one that works for me -> IIS - Error Pages - Edit Feature Settings - Check: Detailed errors – Dinesh Rajan Jun 15 '16 at 22:22

score 5 · Answer 4 · answered Jun 27 '13 at 09:04

5

By default IIS7 intercepts HTTP status codes such as 4xx and 5xx generated by applications further up the pipeline.

In web.config replace the line

<httpErrors errorMode="Detailed">

with

<httpErrors existingResponse="PassThrough" errorMode="Detailed">

answered Jun 27 '13 at 09:04

Gustavo

71
1
1

This was the solution for my case, too, after I did [both steps outlined here](https://stackoverflow.com/a/18838090/107625). – Uwe Keim Apr 28 '23 at 16:04

score 3 · Answer 5 · edited Nov 29 '12 at 18:20

3

under prompt

go to %windir%\system32\inetsrv
execute inetmgr
in the IIS MMC select "web sites" from the three on the left
open the menu action\properties.
in the home directory tab select "configuration..."
in the tab "debug" enable the send error to the client and flag both the checkboxes.
confirm all
restart IIS.

I had the same error and I solved following the above steps.

edited Nov 29 '12 at 18:20

mbinette

5,094
3
24
32

answered Feb 13 '11 at 21:21

Diego La Monica

31
1

score 1 · Answer 6 · edited Jul 27 '11 at 09:53

1

Simply Add following line under this

<?xml version="1.0" encoding="UTF-8"?>
  <configuration>
    <system.webServer>
      <httpErrors errorMode="Detailed" />
    </system.webServer>
</configuration>

And You are done..

edited Jul 27 '11 at 09:53

Andrew

12,991
15
55
85

answered Jul 14 '11 at 15:30

Hetal

11
1

– Hetal Jul 14 '11 at 15:31

Classic ASP Sending errors to browser does not work on IIS7 for remote connections

6 Answers6

Linked