Server Error in '/postlogon' 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

flintmich wrote:
own choosing. You may not want to display reason for error on the
server "BUT" you may want to pass an error code or other explanation to
the user based on what caused the error. You can have multiple server
application errors pages by modifying the customerrors configuration tag
within your application. Is this what you are asking about?

Winged