This <customErrors> tag should then have its "mode" attribute set to "Off".

I am not sure how to get past this error I'm getting after copying a website from my windows XP machine to our new dev server and then trying to run it's default.aspx page:
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>
 

For the CustomErrors section in this app, we currently have:
----------------------------------------------------------------------

<customErrors mode="RemoteOnly">
      <error statusCode="404" redirect="~/temp/readme.txt" />
</customErrors>

we were all running this locally on XP Pro before we got this dev server now.  We need to be able to keep the CustomErrors section as is I would assume so that it redirects them to our readme.txt once we go to production with this.
LVL 1
dba123Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nauman_ahmedCommented:
Please read the following post for a detailed explanation:

Title: Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
http://www.experts-exchange.com/Programming/Programming_Languages/Dot_Net/ASP_DOT_NET/Q_21964669.html

RemoteOnly will display the error when you run the web site by logging in to dev machine windows.

--Nauman.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DBAduck - Ben MillerPrincipal ConsultantCommented:
If you want to get the error, then you will need to set it to mode="Off" while testing, and then set it back to RemoteOnly when you go into production.

The only other way, is to be logged into the dev server and run it from there using Localhost, and it will show you the error, but outside users will not see the error.

Ben.
crisco96Commented:
My guess is that you don't have the folder set as an application, double check that.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.