|
Home > Archive > IIS Server Security > November 2004 > Server Application Unavailable
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Server Application Unavailable
|
|
|
| This one has us stumped. On our production Windows Server 2003
Enterprise Edition running IIS 6.0 and .NET Framework 1.1. We are
attempting to deploy an ASP.NET application, the first ASP.NET
application on that box. Every request of every .aspx file results in
a "Server Application Unavailable" message in the browser. No errors
are recorded in the Event viewer. IIS log shows a 500 error with 0
sub-error.
The app runs fine on our development, test and staging servers -- all
were build about the same time and were nearly identical. We've tried
running aspnet_regiis -i to reinstall ASP.NET script maps, changed the
procesModel user in machine.config from "machine" to "system", and
numerous other things.
Interestingly, even requests for non-existant .apsx files result in
the same error -- we would have expected a 404 page not found.
However, requests for other files like .asp, .htm, .gif, etc. all work
fine. Filemon.exe shows no sign of an attempted read of the .aspx
file. Apparently, IIS issues the error before even attempting to read
the file.
We suspect a permissions problem, but have run out of things to try.
Any help would be appreciated!
Gary
| |
| Leon Mayne [MVP] 2004-11-12, 7:50 am |
| Gary wrote:
> "Server Application Unavailable" message in the browser.
Hmm, have you checked to see if IIS has put it into an application pool or
created one for it? Load the IIS snap in, right click on the virtual
directory corresponding to the application and select properties. Look under
'Application settings' and make sure it has an entry under 'Application
pool'. If 'application name' and 'application pool' are greyed out then
click the 'create' button and place it in the DefaultAppPool.
Also make sure IUSR_machine and IWAM_machine have read and execute
permissions on the folder where the app physically sits.
| |
| Gary Rainbow 2004-11-12, 8:46 pm |
| Hello Leon,
It's a new web site that's running in an application pool that was created
for the web site. There are several other web sites on the same box, each
with their own application pool. They all serve up .htm and .asp files with
no problem, and all fail to serve up .aspx pages.
This is an intranet with anonymous access disabled. We use integrated
Windows authentication. The account I connect with has full access to the
folder where the app sits.
Interestingly, if we switch to IIS 5.0 isolation mode the .aspx pages work
fine. But we consider that a poor workaround because we loose the advantages
of application isolation that IIS 6.0 offers. Besides, the app works fine on
our development, test, and staging servers which all use IIS 6.0 isolation.
Gary
"Leon Mayne [MVP]" <l.rmv.mayne@uea.ac.uk> wrote in message
news:%23zNgi7KyEHA.2568@TK2MSFTNGP11.phx.gbl...
> Gary wrote:
>
> Hmm, have you checked to see if IIS has put it into an application pool or
> created one for it? Load the IIS snap in, right click on the virtual
> directory corresponding to the application and select properties. Look
under
> 'Application settings' and make sure it has an entry under 'Application
> pool'. If 'application name' and 'application pool' are greyed out then
> click the 'create' button and place it in the DefaultAppPool.
>
> Also make sure IUSR_machine and IWAM_machine have read and execute
> permissions on the folder where the app physically sits.
>
>
| |
|
|
| Gary Rainbow 2004-11-15, 8:47 pm |
| Installing .NET Framework 1.1 solved the problem. Go figure. Thanks for the
help!
"Leon Mayne [MVP]" <l.rmv.mayne@uea.ac.uk> wrote in message
news:O8Do48xyEHA.2876@TK2MSFTNGP12.phx.gbl...
> Gary Rainbow wrote:
> <snip>
> Do any of these help?
> http://tinyurl.com/4z5zp
>
>
| |
| Leon Mayne [MVP] 2004-11-16, 2:47 am |
| Gary Rainbow wrote:
> Installing .NET Framework 1.1 solved the problem.
:-)
> Thanks
> for the help!
No prob.
|
|
|
|
|