A
Arthur Dent
Hello all.... i am having a very frustrating problem, because it has KILLED
my website, and i cant seem to get it working again.
I have an ASP.NET 2.0 site, which worked without any problems a few days
ago. The past few days i have been working on a different project, and have
not touched this project. I have checked in Windows Update, and no updates
were installed in the past couple days and no work has been done on the
server.
In my web app, i am using Forms Authentication, and consequently have both
an AUTHENTICATION element and an AUTHORIZATION element.When i try to go to
the site, ... well, the first problem is it is not recognizing my
customErrors mode=Off setting. So i have to go to the server to find out
what's really wrong (this is probably related to my main problem).
But when i go to the site now on the server, i get the following error:
===== BEGIN ERROR =====
Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS.
Source Error:
Line 68: <authentication mode="Forms"> <----- this line is
highlighted.
Line 69: <forms defaultUrl="index.aspx" loginUrl="login.aspx"
name="bnlpcasAUTHX" protection="All" slidingExpiration="true" timeout="90"/>
Line 70: </authentication>
===== END ERROR =====
I checked the directory in IIS and it is set up as an application. I tried
removing the application and recreating it. Nojoy. I tried switching the
site to .NET 1.1, Nojoy, switched it back to 2.0, Nojoy. IIS seems to have
lost the fact that this is an application and no matter what i do, i can't
seem to get it recognized as an application again, even though the IIS gui
does show it as an application. This has happened to both our 2.0 sites and
our 1.1 sites. One or two sites ive been able to get back up by removing the
application and recreating it, but not most of them.
As part of the same problem, it also doesnt recognize other settings in the
web config... such as the customErrors and connectionStrings keys.
Any help is GREATLY appreciated as this currently has our development system
essentially down and development stopped.
Thanks in advance!!!!!
- Arthur Dent
my website, and i cant seem to get it working again.
I have an ASP.NET 2.0 site, which worked without any problems a few days
ago. The past few days i have been working on a different project, and have
not touched this project. I have checked in Windows Update, and no updates
were installed in the past couple days and no work has been done on the
server.
In my web app, i am using Forms Authentication, and consequently have both
an AUTHENTICATION element and an AUTHORIZATION element.When i try to go to
the site, ... well, the first problem is it is not recognizing my
customErrors mode=Off setting. So i have to go to the server to find out
what's really wrong (this is probably related to my main problem).
But when i go to the site now on the server, i get the following error:
===== BEGIN ERROR =====
Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS.
Source Error:
Line 68: <authentication mode="Forms"> <----- this line is
highlighted.
Line 69: <forms defaultUrl="index.aspx" loginUrl="login.aspx"
name="bnlpcasAUTHX" protection="All" slidingExpiration="true" timeout="90"/>
Line 70: </authentication>
===== END ERROR =====
I checked the directory in IIS and it is set up as an application. I tried
removing the application and recreating it. Nojoy. I tried switching the
site to .NET 1.1, Nojoy, switched it back to 2.0, Nojoy. IIS seems to have
lost the fact that this is an application and no matter what i do, i can't
seem to get it recognized as an application again, even though the IIS gui
does show it as an application. This has happened to both our 2.0 sites and
our 1.1 sites. One or two sites ive been able to get back up by removing the
application and recreating it, but not most of them.
As part of the same problem, it also doesnt recognize other settings in the
web config... such as the customErrors and connectionStrings keys.
Any help is GREATLY appreciated as this currently has our development system
essentially down and development stopped.
Thanks in advance!!!!!
- Arthur Dent