"Service Unavailable" - when changing a site from asp 1.1 to 2.0

Hi,

We host multiple sites on IIS6, when a client wants a site to run in
ASP.NET 2.0 I go into IIS Manager, move the site into a new application
pool, then click on the ASPNET Tab, and i change it from 1.1 to 2.0

The problem is that when I do this, ALL websites on this machine get a
"Service Unavailable" for about 15/20 seconds which it switches over.

Is there anyway around this, because if we are changing sites over
continually throughout the day, then people's sites are going to be
down more than they are going to be up.

Dave

LeonMayne
Wed Jun 28 10:56:02 CDT 2006

> We host multiple sites on IIS6, when a client wants a site to run in
> ASP.NET 2.0 I go into IIS Manager, move the site into a new application
> pool, then click on the ASPNET Tab, and i change it from 1.1 to 2.0
>
> The problem is that when I do this, ALL websites on this machine get a
> "Service Unavailable" for about 15/20 seconds which it switches over.

Do the other websites use the same application pool as the one you are
switching?

Dave
Wed Jun 28 12:34:05 CDT 2006

HI Leon,

All sites, in all application pools get the this error, thats whats so
wierd.

Even if i take the site it put it into it's own application pool, and
then change over the ASP versions, all other sites on the server get
that Service Unavailable error.

Dave

Leon Mayne wrote:
> > We host multiple sites on IIS6, when a client wants a site to run in
> > ASP.NET 2.0 I go into IIS Manager, move the site into a new application
> > pool, then click on the ASPNET Tab, and i change it from 1.1 to 2.0
> >
> > The problem is that when I do this, ALL websites on this machine get a
> > "Service Unavailable" for about 15/20 seconds which it switches over.
>
> Do the other websites use the same application pool as the one you are
> switching?