Re: error accessing remotely

From: Mike Walsh (englantilainen_at_hotmail.com)
Date: 09/17/04 

Date: Fri, 17 Sep 2004 09:27:46 +0300

One little word is missing.

> would explain why you are not getting the error message.

would explain why you are not getting the error message LOCALLY.

Mike Walsh, Helsinki, Finland

"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:eguheHHnEHA.3392@TK2MSFTNGP15.phx.gbl...
> When I have made these changes, they have bitten and the next time I
> received an error message telling me there was a time-out. This (time
out) -
> if it is the problem - would explain why you are not getting the error
> message.
>
> I would try again to make the change requested and make sure that you are
> applying it to the right copy of web.config on the server.
>
> A re-boot in the meantime wouldn't hurt if they still aren't being
applied.
>
> Mike Walsh, Helsinki, Finland
> WSS FAQ at http://wss.collutions.com
> Please post questions to the newsgroup only.
>
>
> "erics" <anonymous@discussions.microsoft.com> wrote in message
> news:020a01c49c29$a1d1cd10$a501280a@phx.gbl...
> > While trying to access my sharepoint team site from a
> > remote computer I get the following page that pulls up
> > with the a message as shown below. I have tried what they
> > say to do in the message about making the <customErrors>
> > tag to have its "mode" attribute set to "Off" but the
> > pages still remains the same. I can access the page if
> > I'm on the server itself. Any ideas??? Thanks!
> >
> >
> > 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>
> >
>
>

Relevant Pages