I just recently had a problem with a website where I received the generic 'server error... runtime' message.

I contacted my host who advised me to change the customErrors liine in the web.config file from 'RemoteOnly" to "Off."

I did this.  While this brought the site back for public viewing, changing this line appears to only turn off any error messages and doesn't address the cause for why the error message was generated in the first place.

This site has been running fine for several months.  In fact it was working at 8:00am (local time) and then suddenly this error message appeared around 9:30am.  None of my other DNN installations at this host have had this problem.

Understandably, I'm concerned that whatever the problem was that generated the error message still exists and it's only a matter of time before this happens again with possibly more dire consequences.

Of course, I could be misinterpreting the rationale for changing the customErrors line.

Any insight would be greatly appreciated.