Registered: March 13, 2007 | Reputation: | Posts: 1,911 |
| Posted: | | | | Ken, just got this error a few minutes ago after I clicked on the fourms tab. Quote: 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> | | | Signature banned: Reason out of date... |
|
Registered: March 13, 2007 | Posts: 671 |
| Posted: | | | | So did I - but only after getting a few "Service unavailable", then I got these server errors for a few minutes. I then decided to do something else, and five minutes later, everything was back to normal... But, on the other hand, it is actually exciting getting errors like that at the moment. Who knows, maybe there is a new version of DVDP available when it comes back up? | | | The future is here. It's just not widely distributed yet. (William Gibson) |
|
Registered: March 13, 2007 | Reputation: | Posts: 20,111 |
| Posted: | | | | I get that error every so often too. I seem to remember Ken saying something once about restarting the server every now and then to remedy the problem. | | | Corey |
|