Reputation: 29769
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.
But I need to be able to see where the problem is. Could anyone suggest any method I can see what is the problem logging or something. I think that web.config may be wrong or something. I dont have access to iis so I need other solution. Thanks for help
Upvotes: 0
Views: 3263
Reputation: 1481
From your error message it sound like turning off the custome error will give you more information See this MSDN page for more information on the custom error setting in web.config
Upvotes: 0
Reputation: 4951
Check your customErrors element in web.config. It's likely set to 'RemoteOnly' or 'On'--setting it to 'Off' will allow you to view the error page. As a longer term strategy you may want to consider a logging mechanism, like ELMAH.
Upvotes: 2
Reputation: 2839
Is there any way you can get access to the server to run the application from there?
If you can get to the app.config / web.config file you'll be able to change the error settings to allow errors to be viewed remotely, the full error screen you get in your browser should tell you what changes need to be made.
Upvotes: 0
Reputation: 499232
Update the web.config
customErrors
element and set the mode
attribute to off
.
This will allow you to see the yellow screen of death.
Don't forget to set it back when finished.
A long term solution is to add logging to your application so you can have a log of issues at hand.
Upvotes: 1