Re: How do I configure IIS for the following?



You spotted my error (working too late..). It should say login.aspx. This is
ASP.NET v1.1.

Regards,

Andrew
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:%23nTGF7J4GHA.4764@xxxxxxxxxxxxxxxxxxxxxxx
You will run into problems if you nest ASP.NET 1.1 and ASP.NET 2.0 apps.
Other than that what you say is fine if you configure each directory as an
IIS Application.

I wouldn't even think of using the .Net Framework 1.0 at this point in
time, however.

I'm curious. When you wrote :
Each Ver... directory has my complete ASP project in it. I want the URL
to a specific version to be, for example,
http://localhost/Ver1.0/login.asp.

...did you mean ASP or ASP.NET ?

I ask because your URL is login.asp, but the error message refers to
login.aspx.

I remind people, all the time, to make sure they don't refer to ASP.NET as
ASP.
ASP is a different technology and saying ASP when you mean ASP.NET is
confusing.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Andrew Chalk" <achalk@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e2kzE9H4GHA.1588@xxxxxxxxxxxxxxxxxxxxxxx
How do I configure IIS for the following.

I have a directory called base and then several directories at the next
level down corresponding to versions of my ASP app.

I.e.
BASE
Ver1.0
Ver1.1
...
Ver1.n

Each Ver... directory has my complete ASP project in it. I want the URL
to a specific version to be, for example,
http://localhost/Ver1.0/login.asp. Currently, I have WEBshared BASE and
given it an alias. However, invoking this URL gives me the error below.
Any idea how to get this to work? I'm trying to order various project
versions without having them as a long list in IIS.

Many thanks.
Configuration Error
Description: An error occurred during the processing of a configuration
file required to service this request. Please review the specific error
details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error can be caused by a virtual directory not being configured as an
application in IIS.

Source Error:

Line 59: <authentication mode="Windows" />
Line 60: -->
Line 61: <authentication mode="Forms" >
Line 62: <forms name=".ASPXUSERDEMO" loginUrl="login.aspx"
protection="All" timeout="60" />
Line 63: </authentication>

Source File: D:\Web Sites\CallRecording\20060426\web.config Line: 61







.



Relevant Pages

  • Re: dllhost
    ... It's just about 100% pure ASP with com objects. ... DLLHOST goes to 95-100% utilization and stays there indefinitely unless IIS ... > a simple HTML page serve or do they also hung? ...
    (microsoft.public.inetserver.iis)
  • Re: Accessing 32 bit COM components in 64 bit IIS
    ... CGIs, and ASP scripts onto a 64bit machine, and it just works after they ... The most confusing aspect of running 32bit app on a 64bit OS is that you ... System32 access is redirected, etc). ... we will be introducing the ability to configure IIS to run ...
    (microsoft.public.inetserver.iis)
  • Re: ASP Authentication on IIS 6.0 Windows 2003 Server 32bit help please
    ... when an ASP page is executed in IIS? ... site that requires a user to enter their domain account to access the ... the ASP script code ... I find that the .exe runs ...
    (microsoft.public.inetserver.iis.security)
  • Re: Serious problem in using COM in IIS
    ... introduces a "thread affinity" for your ASP session. ... and that's unlikely to be the thread you're on at the time (IIS ... otherwise i will set it to private and persistable ... >> variables defined in my ABC COM ...
    (microsoft.public.vb.general.discussion)
  • Re: Accessing 32 bit COM components in 64 bit IIS
    ... we will be introducing the ability to configure IIS to run under ... and under the 32bit command line no error is thrown. ... the problem must be to do with how the dll is registered. ... > You should be able to reproduce your situation outside of ASP by creating ...
    (microsoft.public.inetserver.iis)

Loading