Hi,

i am delevoping an ASP.NET website which worked well on my old web host and
now working on localhost but now it doesnt works on my new host. i have new
registered and ftp the files that work on previous host. now it shows the
classic runtime eror page which explains how to enable customerrors tag.
the problem is my website is configured to show my custom error page. what
is the problem? why the customerors tag doesnt work?


my Web.Config file is:

<?xml version="1.0"?>
<configuration>
<appSettings>
</appSettings>
<connectionStrings>
<add name=..../>
</connectionStrings>
<system.web>
<authentication mode="Forms">
<forms name..../>
</authentication>
<authorization>
<allow users="*"/>
</authorization>
<customErrors mode="RemoteOnly" defaultRedirect="YapimAsamasinda.htm">
<error statusCode="403" redirect="YapimAsamasinda.htm"/>
<error statusCode="404" redirect="YapimAsamasinda.htm"/>
</customErrors>
<compilation debug="true">
<assemblies>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A"/>
</assemblies>
</compilation>
</system.web>
</configuration>



the site is shown as:

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>

Tahir wrote:
> Hi,
>
> i am delevoping an ASP.NET website which worked well on my old web host
> and now working on localhost but now it doesnt works on my new host. i
> have new registered and ftp the files that work on previous host. now
> it shows the classic runtime eror page which explains how to enable
> customerrors tag. the problem is my website is configured to show my
> custom error page. what is the problem? why the customerors tag doesnt
> work?
>
>
> my Web.Config file is:
>
> <?xml version="1.0"?>
> <configuration>
> <appSettings>
> </appSettings>
> <connectionStrings>
> <add name=..../>
> </connectionStrings>
> <system.web>
> <authentication mode="Forms">
> <forms name..../>
> </authentication>
> <authorization>
> <allow users="*"/>
> </authorization>
> <customErrors mode="RemoteOnly" defaultRedirect="YapimAsamasinda.htm">

Try with mode="Off" so that you see the actual error message. That may
help to find out what the main problem is.


Use an url relative to the root instead of an url relative to the
current folder:

~/YapimAsamasinda.htm

That way you get redirected to the same page even if the error occurs in
a page in a subfolder.

> <error statusCode="403" redirect="YapimAsamasinda.htm"/>
> <error statusCode="404" redirect="YapimAsamasinda.htm"/>
> </customErrors>
> <compilation debug="true">
> <assemblies>
> <add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=B03F5F7F11D50A3A"/>
> </assemblies>
> </compilation>
> </system.web>
> </configuration>
>
>
>
> the site is shown as:
>
> 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>
>
>


--
Göran Andersson
_____
http://www.guffa.com

ok, i found that the error was my site isnot configured as .NET 2.0
application >
thanks for replies.


"Tahir" <(E-Mail Removed)>, iletisinde þunu yazdý,
news:973D49F3-4096-4A3F-B98C-(E-Mail Removed)...
> Hi,
>
> i am delevoping an ASP.NET website which worked well on my old web host
> and now working on localhost but now it doesnt works on my new host. i
> have new registered and ftp the files that work on previous host. now it
> shows the classic runtime eror page which explains how to enable
> customerrors tag. the problem is my website is configured to show my
> custom error page. what is the problem? why the customerors tag doesnt
> work?
>
>
> my Web.Config file is:
>
> <?xml version="1.0"?>
> <configuration>
> <appSettings>
> </appSettings>
> <connectionStrings>
> <add name=..../>
> </connectionStrings>
> <system.web>
> <authentication mode="Forms">
> <forms name..../>
> </authentication>
> <authorization>
> <allow users="*"/>
> </authorization>
> <customErrors mode="RemoteOnly" defaultRedirect="YapimAsamasinda.htm">
> <error statusCode="403" redirect="YapimAsamasinda.htm"/>
> <error statusCode="404" redirect="YapimAsamasinda.htm"/>
> </customErrors>
> <compilation debug="true">
> <assemblies>
> <add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=B03F5F7F11D50A3A"/>
> </assemblies>
> </compilation>
> </system.web>
> </configuration>
>
>
>
> the site is shown as:
>
> 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>
>
>