The configuration error in the figure is as follows: "This configuration section cannot be used in this path." This can occur if the section is locked at the parent level. The lock is set by default (overridemodedefault= "Deny"), or explicitly set by a location tag containing overridemode= "Deny" or the old allowoverride= "false"
In the web.config did not find overridemodedefault this setting, obviously not my web.config problem (mine is not, can not explain none). After a search, it was said that because IIS7 adopted a more secure Web.config management mechanism, the configuration item was locked out by default. To change the command line%windir%\system32\inetsrv\appcmd unlock config-section:system.webserver/handlers must be run to unlock, if modules is also locked, can run%windir%\system32\inetsrv\appcmd unlock config-section:system.webserver/modules. (http://goo.gl/mW7Ub) According to this man, the reason is because Visual Studio installed in IIS will have this kind of problem.
I did not use the method he provided for the command line, I checked my IIS installation again, and I solved the problem by updating my asp.net on the hook. My IIS installation is as follows, if you are installing with asp.net+win7 remember to asp.net on the hook, if not you can use the command line method, I have not tried not to guarantee the success of.