The whole point of this message is to tell you how to enable viewing error
details. Your current configuration disables that. Follow the instruction
and you will know what is the reason for the error.
Eliyahu
[quoted text, click to view] "Hines" <Hines@discussions.microsoft.com> wrote in message
news:04AC014B-6526-4FF3-B190-7C58BDCDF6BC@microsoft.com...
> Hi,
>
> Can someone tell me what's the cause of this error.
>
> 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>
>
>
> Sometimes this error occur and sometimes not.
>
> Thanks.
>