IIS and ASP.Net

[Guest]

I'm a beginner and trying to learn. I have a half dozen websites that I first
configured in just html. Then I converted them to ASP.Net and it took help
from Microsoft to get IIS to recognize the applications.

Then I lost my server and had to rebuild. Now that I have, I continue to
have the following problem:

The website I have under the default website oon IIS works fine. However,
the others, which I defined, each as their own website, fail to run. I get a
configuration error that "It is an error to use a section registered as
allowDefiniteion='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS." Then it displays the authentication section, whether forms or none.

I have gone into IIS and reset the website applications several times. There
appear to be no real differences between the virtual directory I defined for
the default website and those I defined for other websites. And indeed, IIS
seems to have no trouble finding the correct webconfig files each time.

Can anyone help? I've spent a couple of days trying to puzzle through this
and am completely stumped. Thanks!

 

[Nick Malik [Microsoft]]

how is IIS differentiating these sites? Host header? port number?

Did you place the additional sites under the same directory tree as the
default web site, because if you did... move them to another directory tree
altogether and set that tree to be the base directory for the additional web
site.

HTH,

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.

 

[Guest]

My first guess is that neither of those is the problem since IIS has no
trouble finding the webconfig files. However, to answer your questions,
1. The IP address and ports are the same for each. I'm using the headers
to differentiate.
2. Each site uses a different folder under wwwroot (i.e.,
\Inetpub\wwwroot\website1, \Inetpub\wwwroot\website2, etc.)

I did notice an initial difference in how IIS pointed to the starting
directories, but played with that and saw no change to the problem.

Did I answer what you were asking? Suggestions?

Thanks!

 

[Nick Malik [Microsoft]]

normally the default web site is at c:/inetpub/wwwroot
Therefore, normally a subdirectory under wwwroot is an application, but not
a site.

In order to avoid confusion, create your additional sites under a seperate
tree, like
c:/inetpub/site1root
and
c:/inetpub/site2root

I've had that help before, but I can't say as I've had any difficulty
setting up a seperate site, as you appear to be having.
Perhaps this will help you.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.

 

[Guest]

It sure seemed worth a shot and so I tried it. However, I'm still getting the
same results. I can't help but feel that the problem must lie in something
IIS expects in the way the application is defined, but I'm lost as to where
else to look.

I really appreciate the help, though. Do you have any ideas what else I can
try?