.net web.config file

[Steve Spicer]

I can easily run a little test .net page in a Win2003 Server, but as soon as
I create a web.config file in FP the test page, nor any other .aspx file,
will not run. Even if there is nothing in the file. I've got a database app
that runs fine that I want to move over to the Win2003 server and I need the
web.config file. The error I get is about custom errors. I'm using FP2000 at
home to connect to the 2003 server at work. The error page is a 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>
<<

 

[Chris Leeds, MVP-FrontPage]

last time I messed with .net stuff I remember having to get the server
admins to set the particular folder as a .net web application.

it seems to have the web.config and or .dll files running on the site it
needs to be marked "server side" to allow it to run.

HTH

--
Chris Leeds,
Microsoft MVP-FrontPage

Make More Money with Less Work
Let Your Clients Control Their Content With Just A Browser!
http://contentseed.com/
--

 

[clintonG]

Add <customErrors mode="Off"/> to the web.config and try to load the
application again. You want to be able to read the descriptive error
messages. The advice regarding the root directory configured as a virtual
application was correct. Use IIS to configure locally and note the same has
to be done on the hosting server.

In this instance, the web.config file goes into the same directory of the
root of the application. When all is operating as desired change the
customErrors mode back to "On" and consider using the other web.config file
settings that you must use Google and MSDN to learn about as the web.config
file plays a critical role in ASP.NET applications.

-
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/

 

[Steve Spicer]

No, maybe this is the wrong place to ask this. The aspx file runs. It is a
net application as defined in IIS6. I've changed the machine.config file on
the server to customErrors mode = "Off" and added that line in the web's
web.config file. It will not run with a web.config file in the folder. The
page will run with it not in the folder.

 

[Chris Leeds, MVP-FrontPage]

since you turned custom errors on, what did they say?

--
Chris Leeds,
Microsoft MVP-FrontPage

Make More Money with Less Work
Let Your Clients Control Their Content With Just A Browser!
http://contentseed.com/
--

 

[Steve Spicer]

No change. I set the customError mode = "on" in the machine.config file
....but as long as I have a web.config file in the directory I get the same
error as I originally posted. Like I said, if I rename the web.config file in
the directory to something like OLDweb.config, my little aspx test file works
fine. Change it back and I get the runtime error. It's got to be something
else in the machine.config file is my guess, but I'm at a loss. The error
occurs if a web.config file is "alive" in the root of the application.

 

[Steve Spicer]

Thanks, I've got it working now with both the machine.config and the
web.config file set to customErrors mode ="Off". I'll change that back once
I'm satisfied stuff is working correctly. Thanks.

 

[Chris Leeds, MVP-FrontPage]

congrats! I've always struggled, and still do with the .net stuff. I've
got to get a better handle on it too!

--
Chris Leeds,
Microsoft MVP-FrontPage

Make More Money with Less Work
Let Your Clients Control Their Content With Just A Browser!
http://contentseed.com/
--