K
kevingangsun
I created an ASP.NET application for our company and it worked great
on more than 4 windows 2003 servers. However, when we deployed it to
another 2003 server (IIS6), we got the following error message:
It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level.
Source Error:
Line 47: by Microsoft that offers a single logon and core
profile services for member sites.
Line 48: -->
Line 49: <authentication mode="Windows" />
Line 50: <!-- AUTHORIZATION
Line 51: This section sets the authorization policies of the
application. You can allow or deny access
I read almost all the posts on the web and the solution is either to
set it as an IIS application or remove the nested web.config file.
However, neither of them works for my case. We have the virtual
directory set as an application and we do not have nested web.config
file inside the subfolders.
As I said, the same procedure and same piece of code worked fine on
all other machines but this one. I even recreated the virtual
directory and used the aspnet_regiis to remove/install the ASP.NET on
the IIS server, but none of them work. I am beginning to think that
one of the other software packages loaded on this server has changed a
IIS setting somewhere that is causing this issue. However, I just do
not know where to start to look...
Any suggestion is greatly appreciated.
on more than 4 windows 2003 servers. However, when we deployed it to
another 2003 server (IIS6), we got the following error message:
It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level.
Source Error:
Line 47: by Microsoft that offers a single logon and core
profile services for member sites.
Line 48: -->
Line 49: <authentication mode="Windows" />
Line 50: <!-- AUTHORIZATION
Line 51: This section sets the authorization policies of the
application. You can allow or deny access
I read almost all the posts on the web and the solution is either to
set it as an IIS application or remove the nested web.config file.
However, neither of them works for my case. We have the virtual
directory set as an application and we do not have nested web.config
file inside the subfolders.
As I said, the same procedure and same piece of code worked fine on
all other machines but this one. I even recreated the virtual
directory and used the aspnet_regiis to remove/install the ASP.NET on
the IIS server, but none of them work. I am beginning to think that
one of the other software packages loaded on this server has changed a
IIS setting somewhere that is causing this issue. However, I just do
not know where to start to look...
Any suggestion is greatly appreciated.