blank files hitting runtime error.

[Eric Layman]

Hi,

We have a remote webhost here that runs dotnet.

Interestingly, it is not able to parse any aspx files

It will show a run time error even if the aspx file is blank or doesnt even
exist. I played around with web.config but nothing happens.

RUNTIME ERROR

Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrorstag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrorstag should then have its "mode" attribute
set to "Off".

My web.config:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<system.web>

<customErrors mode="Off"/>

<globalization requestEncoding="utf-8" responseEncoding="utf-8"

culture="en-GB" />

</system.web>

</configuration>

Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com

[Latish Sehgal]

Change to
<customErrors mode="On" />
Post back the error info.

[Damien]

On Apr 3, 6:08 am, "Eric Layman" <namyalcire[at no spam]gmail.com>
wrote:

Hi,

We have a remote webhost here that runs dotnet.

Interestingly, it is not able to parse any aspx files

It will show a run time error even if the aspx file is blank or doesnt even
exist. I played around with web.config but nothing happens.

RUNTIME ERROR

Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrorstag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrorstag should then have its "mode" attribute
set to "Off".

My web.config:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<system.web>

<customErrors mode="Off"/>

<globalization requestEncoding="utf-8" responseEncoding="utf-8"

culture="en-GB" />

</system.web>

</configuration>

Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com

Frequently, if you've followed the advice of the generic error page
(to set customErrors to off), but you're still receiving the generic
error page, it tends to indicate that your web.config isn't the one
that's being applied. This can be caused if your application is
sitting in a (virtual) directory below another site, but it's
(virtual) directory hasn't been marked as an application in IIS.

Damien