cgibbs
Wed Jul 09 16:26:59 CDT 2003
I've just spent half a day working the same problem on a new 2003
production server in which we moved sites from a 2000 server. Since
your 2003 installation is from an MSDN I would suspect that you have
the same issue we did. Which is that our web apps were written for
.Net Framework v1.0 and 2003 comes installed with .Net Framework v1.1.
The neat thing is that both frameworks can co-reside on the same
server, but the set-up for us was most tricky.
The first thing to determine is whether you upgraded to 2003 from 2000
or did a fresh install. If you did a fresh install, you will need to
download and install the 1.0 framework or install it from a prior
visual studio disk.
Don't be fooled by finding a folder at
%winroot%\Microsoft.Net\Framwork\v1.0.3705\ either, there needs to be
more than 4 or 5 files in that folder to be sure that version 1.0 is
installed.
Once you know you have both frameworks installed, you will need to add
and allow the 1.0 framework to the Web Service Extensions in IIS6.
You can then use the method decribed here to re-register just the web
apps built on the 1.0 framework.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;816782
Once this is done you will need to create a new Application Pool in
IIS for sites that are running the old framework since sites
referencing different framework versions cannot run in the same
Application Pool.
Now go to the web site properties of the sites that need the 1.0
framework to run and on the Home Directory tab select the new
Application Pool that was just created.
There is one last thing to do, and this is the part we did not like,
but it seems to be the only way to get our older .Net sites to run.
Go into the Properties of the Application Pool that was just created
and select the Identity Tab. In the drop down select "Local System".
Now when you hit OK you will get a nasty security warning that is very
valid, but it was the only way we got our sites to work properly. If
anyone could follow up with a better way to manage this hurtle that is
less of a security risk, I would sure like to know.
Hope this helps.
Chris
"Francesco Stiffoni" <francesco@teknoscurl.it> wrote in message news:<O9uaSZiRDHA.1920@TK2MSFTNGP11.phx.gbl>...
> I have just installed the Windows Server 2003 Standard that I received with
> MSDN subscription. Almost everything works well but aspx support.
> All the service and applications server seems OK, but every file with .aspx
> suffix, also a file not present in the directory, return this error:
>
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
>
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
>
>
>
> I open the event viewer application section and no error is reported.
>
> Thanks in advance
>
> Francecesco