Another 'Server Not Available' Thread...

Thanks for being curious enough to look in here.

Particulars:
IIS 6.0
Windows 2003
SqlServer 2000
.Net 2.0 & 1.1
Port 8080

My problem is that I get the 'Server Not Available' error message after
installing my web site with an installer. But I can copy the files that
were placed into the original virtual directory into another virtual
directory and the web site will be active. I can't see any difference
between the old or new directories (physical or virtual). What could be
going on here?

So, my steps: After the web site successfully installs and I change
the ASP.NET property for the web site from .Net 2.0 to .Net 1.1, I
restart IIS. I get the 'Server Not Available' error message.

So, I rename the original directory to 'siteold' under wwwroot, create
a new directory called 'site', copy all content (folders and files)
from 'siteold' to 'site', and in IIS, I create a new virtual directory
for 'site'. I also change the ASP.NET version from .Net 2.0 to .Net
1.1. The web site is seen when I browse to it and it works like a
charm.

I don't create the installer scripts so I can't tell what is going on
there. When I create the virtual directory, I do check the read and
execute checkboxes (actually the first three checkboxes) when display.
This installer will be checked on a Win2000 box shortly so I don't know
if it works there but I will repost if I see the error there too.

Any suggestions?

Juan
Thu Apr 06 22:50:30 CDT 2006

re:
> After the web site successfully installs and I change the ASP.NET
> property for the web site from .Net 2.0 to .Net 1.1, I restart IIS.
> I get the 'Server Not Available' error message.
> I also change the ASP.NET version from .Net 2.0 to .Net 1.1.
> Any suggestions?

Yes.

Make sure that the application isn't in the same Application Pool
as applications running under ASP.NET 2.0.

If you're running IIS 6.0 in worker process isolation mode (the default),
you cannot run ASP.NET 1.1 and ASP.NET 2.0 apps in
the same Application Pool.



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/
===================================
<spearenb@mantech-wva.com> wrote in message
news:1144374393.004257.318020@i39g2000cwa.googlegroups.com...
> Thanks for being curious enough to look in here.
>
> Particulars:
> IIS 6.0
> Windows 2003
> SqlServer 2000
> .Net 2.0 & 1.1
> Port 8080
>
> My problem is that I get the 'Server Not Available' error message after
> installing my web site with an installer. But I can copy the files that
> were placed into the original virtual directory into another virtual
> directory and the web site will be active. I can't see any difference
> between the old or new directories (physical or virtual). What could be
> going on here?
>
> So, my steps: After the web site successfully installs and I change
> the ASP.NET property for the web site from .Net 2.0 to .Net 1.1, I
> restart IIS. I get the 'Server Not Available' error message.
>
> So, I rename the original directory to 'siteold' under wwwroot, create
> a new directory called 'site', copy all content (folders and files)
> from 'siteold' to 'site', and in IIS, I create a new virtual directory
> for 'site'. I also change the ASP.NET version from .Net 2.0 to .Net
> 1.1. The web site is seen when I browse to it and it works like a
> charm.
>
> I don't create the installer scripts so I can't tell what is going on
> there. When I create the virtual directory, I do check the read and
> execute checkboxes (actually the first three checkboxes) when display.
> This installer will be checked on a Win2000 box shortly so I don't know
> if it works there but I will repost if I see the error there too.
>
> Any suggestions?
>

spearenb
Fri Apr 07 10:18:49 CDT 2006

I will go and check to make sure that I am not doing that. But, I have
refined these steps a little bit. After installation I go and rename
the source folder from 'temp' to 'tempold', create a new folder 'temp',
and copy all content from 'tempold' to 'temp'. I then go into IIS and
change (not create) the virtual directory setting for the 'temp' from
ASP.NET .NET 2.0 to 1.1. That's it. The site works. I don't have to
reboot or bounce the IIS service.

These steps work for both Win 2000 and Win 2003.

Any suggestions?