Incorrect Application Path IIS 7, Win 7

"Invalid application path" error. Here are the steps I took.

  • Right-click the root folder of the website. Click Add Virtual Directory.

  • In the window that opens, set an alias to the name of the subfolder. WS

  • Use the browse button to navigate and set the path to the physical folder on the disk. Click OK

  • Click "Test Settings ...". Authentication passes through the pass. But get a warning that the path cannot be verified. It looks ok.

    Click OK. And the "WS" folder is now installed as a virtual directory. (If I click "Basic Settings ..." and the test parameters, you will still get the results.

  • Right-click the folder. Select Convert to Application. Leave all the defaults as they are. Click "Test Settings" and I get an error message. (This is with pass-through authentication.)

  • Connect as a "Specific User", and this time, "Test Settings ..." do not report any errors. In addition, the path is indicated as “accessible”.

So the question is, why does “Pass Through” authentication fail?

Now note that if I continue and click OK to convert the virtual folder to the application, an error does not occur. And I can start the web service (this is using the pass-through authentication option for the application).

So what a problem. Well, when I add a website to VS 2008 solution and try to create a website (I need to debug the web service). I get this error:

An error occurred while using a section registered as allowDefinition = 'MachineToApplication' that exceeded the application level. This error can be caused by the fact that the virtual directory is not configured as an application in IIS.

But a folder is an application. I just converted it. And the web service is working fine on the local host.

What details am I missing?

(Studying these problems, I found that several web.config files can lead to a site build error. I do not have multiple web.config files.)

+8
web-applications iis-7
Oct 29 '11 at 15:05
source share
3 answers

I was asked that IIS be / be corrupted. But after listening to this message on a new computer with a new 64-bit version of Win 7, installing IIS and creating one new website, I came to the conclusion that the message itself is an error and that it is sound. That is, the application and website will work as expected. This opinion did not contradict the MS IIS forum since I posted it a few months ago.

See this topic: http://forums.iis.net/p/1182820/2000936.aspx

+17
Jan 11 2018-12-12T00:
source share

Found a solution for my error:

in the folder c: \ inetpub \ wwwroot I had a folder with the same name, I wanted the application to have

something like: C: \ Inetpub \ Wwwroot \ TestWebsite

in IIS it was not an application, but it showed up as a folder

when I tried to create an application in IIS using the Alias ​​TestWebsite, it gave me this error, even if it was on a completely different physical path

check if there is a folder with the same name as the alias for the application that you create in the wwwroot folder

was not right in my case

hope this helps someone

I also recommend removing the alias from IIS using the appcmd command located in C: \ Windows \ System32 \ inetsrv , see this link for an explanation of how

+5
Feb 07 2018-12-14T00:
source share

I just ran into this problem and it was caused when I canceled iisreset before restarting the web server.

Make sure your IIS server pools and application pools are running. iisreset

+2
Feb 22 '12 at 22:45
source share



All Articles