hehehe, maar als je er 1 maal in bent dan is er niemand
nou ja, bijna..
msn wederom gefaald..
-
- Lid
- Berichten: 2488
- Lid geworden op: 02 jul 2004, 01:24
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>
Dit krijg ik nu
--------------------------------------------------------------------------------
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>
Dit krijg ik nu
- Martijn
- Lid
- Berichten: 2268
- Lid geworden op: 28 jan 2002, 21:14
- Locatie: Eindhoven
- Contacteer:
Re: msn wederom gefaald..
Het antwoord op je vragen is: Nee. Ze worden zo vaak dichtgegooid, omdat dit soort topics werkelijk nergens over gaan. Een verdere toelichting hoef ik denk ik niet te geven. Op zich is het niet erg dat er gewoon geslowchat wordt op dit forum. Vooral in de babbelbox is dit wel mogelijk. Het is makkelijk als dit allemaal in één topic gebeurd. Een slowchattopic. Weet je wat, ik sluit deze en open meteen zo'n topic.Guido schreef:Msn doet het wederom niet, waarom gooien mods. deze topics altijd zo snel dicht? houden jullie een score bij in staffroom.. en wie de meeste topics kan verplaatsen/dichtgooien ?:D zoja, wie staat er voor?
"Wie leest die onderschriften eigenlijk?"