Last post Dec 12, 2012 10:14 PM by Angie xu - MSFT
Dec 06, 2012 05:20 PM|uldis|LINK
I want to change my asp.net hosting ,but our country hosting services can't configurate my site ( web configuration) on new server. If no-one can help me on this problem,maybe I can resolve it on with hosting on another EU country .Prices on Latvia is aprox.
30 EUR / 10 GB disk space and I'm ready booking on long term.
Dec 06, 2012 09:55 PM|carl.steinhart|LINK
Could you please advise here the problem that you got? Please explain it clearly. :) For asp hosting, I would recommend you to find it on microsoft.com/web/hosting, you can try
Dec 07, 2012 03:55 AM|uldis|LINK
Problem is typcal and old as an asp...
“This error can be caused by a virtual directory not being configured as an application in IIS.“ Screen is here
Sure, I know ,that this is not a new in forums ,but I can't find progrmmist in Latvia ,who could resolve this problem in practice ,i.e., change a code on system . I'm just a owner of 4 years old site .
Hosting problem is in fact ,that I need 24/7 service ,therefore change hosting from private ( not my own ) Windows Server to companie ( they have 10 years practice on hosting business ) service on Windows Server too.
Dec 12, 2012 10:14 PM|Angie xu - MSFT|LINK
We have discussed this error before,
This error occurs primarily out of 2 scenarios:
1. When you create an new web application using visual studio.net, it automatically creates the virtual directory and configures it as an application. However, if you manually create the virtual directory and it is not configured as an application, then
you will not be able to browse the application and may get the above error. The debug information you get as mentioned above, is applicable to this scenario. To resolve it, Right Click on the virtual directory - select properties and then click on "Create"
next to the "Application" Label and the textbox. It will automatically create the "application" using the virtual directory's name. Now the application can be accessed.
2. When you have sub-directories in your application, you can have web.config file for the sub-directory. However, there are certain properties which cannot be set in the web.config of the sub-directory such as authentication, session state (you may see
that the error message shows the line number where the authentication or sessionstate is declared in the web.config of the sub-directory). The reason is, these settings cannot be overridden at the sub-directory level unless the sub-directory is also configured
as an application (as mentioned in the above point). Mostly we have the practice of adding web.config in the sub-directory if we want to protect access to the sub-directory files (say, the directory is admin and we wish to protect the admin pages from unathorized
Moreover, you could post this in IIS Forums for better solution(http://forums.iis.net/).
Note: you could learn detailed discussion information here(http://forums.asp.net/t/769696.aspx/1/10).
hope it helps you.