views:

83

answers:

3

I deployed an asp.net website to a shared server.....

I got the error

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.

Here is my page http://static3.nextgenits.com/Forms/Homepage.aspx

What am i missing ?... Any suggestion...

A: 

Set it to debug="true" and you will see the error. Or browse it from the local machine if thats possible. I would also recommend you use something like elmah to log errors in your application. Then you will always be able to see the error when you have your custom error pages set.

The reason you get the message is because you have some other error that asp.net doesn't want to display in release mode as it might contain sensitive information that you don't want the end use to see.

Mattias Jakobsson
A: 

Maybe a typo in your web.config preventing asp.net to eval. customErrors section.

EDIT: Bit more clear. If there is an error in the web.config (it's an XML File) then ASP.NET isn't able to parse that file. This is an error. As asp.net can't parse the web.config it ignores any settings.

Arthur
@Arthur can't get ur point? Plz explain a bit more..
Pandiya Chendur
A: 

Your application's web.config is not configured to show the error messages remotely. You will have to edit your web.config and un-comment the customErrors section. Also make sure you set it to RemoteOnly . Once you do this you will see the actual error on the screen and then you can correct it accordingly. Here is the web.config section to be used:

<customErrors mode="RemoteOnly"/>
Bootcamp