jeremyll
asked on
cannot debug or load up web page ASP.NET (Visual web developer 2010 express)
I've installed visual web developer 2010 express and just typed up my first asp.net page
Each time I click on 'Debug'
I get this ERROR message:
Error 1 It is an error to use a section registered as allowDefinition='MachineTo Applicatio n' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. C:\inetpub\wwwroot\Lynda ASP.Net Exercise\Ch01GettingStarte d\HelloWor ld\Web.con fig 12
and output message:
Validating Web Site
Building directory '/Exercise/Account/'.
C:\inetpub\wwwroot\Exercis e\Ch01Hell oWorld\Web .config(12 ): Build (web): It is an error to use a section registered as allowDefinition='MachineTo Applicatio n' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Any clues?
Each time I click on 'Debug'
I get this ERROR message:
Error 1 It is an error to use a section registered as allowDefinition='MachineTo
and output message:
Validating Web Site
Building directory '/Exercise/Account/'.
C:\inetpub\wwwroot\Exercis
Any clues?
Set the folder "Ch01HelloWorld" in C:\inetpub\wwwroot\Exercis e\ as virtual directory.
ASKER
@karthitron
I did do that through IIS, but im still getting the same error message.
I did do that through IIS, but im still getting the same error message.
What version of IIIS you are using.
1. Confirm whether any web.config is there in any other sub folder, if so, create virutal directory for each sub folder, haing the web.config.
2. Confirm whether the website opened in visual studio is the root directory of the website having web.config file.
For more causes:
http://dotnet-magic.blogspot.com/2008/11/it-is-error-to-use-section-registered.html?showComment=1255557256812#c1453036979266449646
http://forums.iis.net/t/1148147.aspx
http://social.msdn.microsoft.com/Forums/en/windowsazure/thread/1164186d-e1dc-440b-b745-02a00eb66909
1. Confirm whether any web.config is there in any other sub folder, if so, create virutal directory for each sub folder, haing the web.config.
2. Confirm whether the website opened in visual studio is the root directory of the website having web.config file.
For more causes:
http://dotnet-magic.blogspot.com/2008/11/it-is-error-to-use-section-registered.html?showComment=1255557256812#c1453036979266449646
http://forums.iis.net/t/1148147.aspx
http://social.msdn.microsoft.com/Forums/en/windowsazure/thread/1164186d-e1dc-440b-b745-02a00eb66909
I would remove the part in your web.config that says "allowDefinition='MachineT oApplicati on' ".
I have no idea why a tutorial set would have that in there in the first place. It's something that restricts configuration settings on higher level config files (like in a hosting environment, where the host wants to restrict clients).
I have no idea why a tutorial set would have that in there in the first place. It's something that restricts configuration settings on higher level config files (like in a hosting environment, where the host wants to restrict clients).
ASKER
I've deleted all instance of the web.config file in the directory.
I'm not sure if I'm setting up the virtual directory correctly. I just go into windows 7 IIS Manager then right click on the website folder and select 'add virtual directory'.
I'm still having the same problem.
I'm not sure if I'm setting up the virtual directory correctly. I just go into windows 7 IIS Manager then right click on the website folder and select 'add virtual directory'.
I'm still having the same problem.
ASKER
@b_levitt i tried removing 'allowDefinition='MachineT
<?xml version="1.0"?>
<!--
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
-->
<configuration>
<connectionStrings>
<add name="ApplicationServices"
connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<compilation debug="false" targetFramework="4.0" />
<authentication mode="Forms">
<forms loginUrl="~/Account/Login.aspx" timeout="2880" />
</authentication>
<membership>
<providers>
<clear/>
<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices"
enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10"
applicationName="/" />
</providers>
</membership>
<profile>
<providers>
<clear/>
<add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/"/>
</providers>
</profile>
<roleManager enabled="false">
<providers>
<clear/>
<add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/" />
<add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/" />
</providers>
</roleManager>
</system.web>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
</configuration>
Please define "didn't work." Was there an error message?
I think, there is problem in creation of virutal directory in windows 7. Please go through the steps for creating and testing the site as mentioned in below URL:
http://technet.microsoft.com/en-us/library/cc771804(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc771804(WS.10).aspx
ASKER
I still have the same problem at the moment.
When i tried to create the virtual directory through IIS manager and clicked 'Test Settings...' I get an exclaimation mark next to Authorization: cannot verify access to path c:\inetpub\wwwroot\folder
The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
When i tried to create the virtual directory through IIS manager and clicked 'Test Settings...' I get an exclaimation mark next to Authorization: cannot verify access to path c:\inetpub\wwwroot\folder
The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
ASKER
I have a feeling i need to fix something else first before this problem gets fixed. So i created another question here: https://www.experts-exchange.com/questions/26817910/Error-Summary-HTTP-Error-401-3-Unauthorized-You-do-not-have-permission-to-view-this-directory-or-page-because-of-the-access-control-list-ACL-configuration-or-encryption-settings-for-this-resource.html
It's this error:
Error Summary HTTP Error 401.3 - Unauthorized You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource
It's this error:
Error Summary HTTP Error 401.3 - Unauthorized You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource
ASKER
I think the problem above is related to this one.
I"m still waiting on clarification of "didn't work". I will review your other question.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.