Very Urgent!!!!....Production Problem -Server Error in '/' Applica

[Guest]

I've got the following error from ASP.Net Web Application from production
server. It was working fine till yesterday. Suddenly we were unable to open
any of the .aspx pages. But we can open .asp pages. Please help us
immediately.

The Error message is: (from ****START*** to ****END****)

*********** START *************

Server Error in '/' Application.
---------------------------------------
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 <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>


**************END**************


But actually I do have ' <customErrors mode="Off"/>' in my web.config.
Which means that ASP.NET is not picking up settings from my Web.config, but
probably from web.config in some parent directory, over which I have no
control(being in a hosted enviro.).

The wierdest thing is that, I get this error for any request with ASPX
extension. Even if the file doesn't exist!

Help needed immediately. thanks.

-Chitra-

 

[John Saunders]

I've got the following error from ASP.Net Web Application from production
server. It was working fine till yesterday. Suddenly we were unable to
open
any of the .aspx pages. But we can open .asp pages. Please help us
immediately.

The Error message is: (from ****START*** to ****END****)

*********** START *************

Server Error in '/' Application.
---------------------------------------
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 <customErrors> tag within a
"web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the
application's
<customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>


**************END**************


But actually I do have ' <customErrors mode="Off"/>' in my web.config.
Which means that ASP.NET is not picking up settings from my Web.config,
but
probably from web.config in some parent directory, over which I have no
control(being in a hosted enviro.).

The wierdest thing is that, I get this error for any request with ASPX
extension. Even if the file doesn't exist!

Help needed immediately. thanks.

This sounds like your IIS settings have changed. Check to make sure that the
virtual directory is defined as an application in IIS, and run
%windir%\Microsoft.Net\Framework\v1.1.4322\aspnet_regiis -i (or whatever
Framework version you're using).

John Saunders

 

[Guest]

just try to define a new virtual directory. copy your app into it.