asp.net on windows server 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When asp.net application is deployed and run in windows server 2003 it gives
a error as "SERVER APPLICATION UNAVAILABLE".How to solve this problem? and
the ASP.net framework is 2.0.
 
When I see this error I usually assume it is an identity crisis...
specifically, the NT user running the app-pool. Note that once an
app-pool bombs, it shuts down and must be *manually* restarted in IIS;
simply refreshing / rebuilding the app will not fix it.

Check what identity the app is running as; if it isn't the default,
then note that there are specific conditions for running aspnet under
a bespoke account. If you need I'll post the list...

But remember to check the app-pool is running (refreshing the display
as necessary)

Marc
 
Posted for completeness:

Configuring IIS Application Identity:

* Decide which identity you wish to use! (typically your own
credentials for debugging purposes, or a specific account for
test/production servers)
* Add the account to the "Log on as a service" policy-group (Local
Security Settings -> User Rights Assignment)
* Add the account to the "IIS_WPG" user-group (Computer Management ->
Local Users and Groups)
* Grant the account "Read & Execute", "List Folder Contents" and
"Read" permissions to the file structure (Explorer -> Properties)
* Either create a new application pool, or update the user account of
an existing pool (Internet Information Services -> Application Pools)
* Set the application pool for the site / application (Internet
Information Services -> Web Sites)

I have also seen references to the following, but I have never needed
them myself:

* Assign the account the right to start CGI processes: adjust memory
quotas for a process and replace a process level token
* Add the account to the "Logon local" policy-group
 
Also - "identity crisis" is my first bet (**every** time I have seen
this error, this has been the cause), but review the server event log
for more clues.

Marc
 
I solved the issue like this... I was running Enterprise edition SP1

- Expand Application Pools

- Create a new application pool 'NewPool'

- Right Click>Properties>Set the Identity to Predifined>Local Service

- Give permission for local service (Read, execute, list folders, ...) for
- Windows\Microsoft.NET\Framework\v2.0.50727
- Physical root directory of website

- Expand Websites and Select your web sites virtual folder

- Right Click>Properties>Set Properties>Home Directory>Application Pool to
'NewPool'

Hope it will help you...
 
All this in IIS Admin console

Faiz said:
I solved the issue like this... I was running Enterprise edition SP1

- Expand Application Pools

- Create a new application pool 'NewPool'

- Right Click>Properties>Set the Identity to Predifined>Local Service

- Give permission for local service (Read, execute, list folders, ...) for
- Windows\Microsoft.NET\Framework\v2.0.50727
- Physical root directory of website

- Expand Websites and Select your web sites virtual folder

- Right Click>Properties>Set Properties>Home Directory>Application Pool to
'NewPool'

Hope it will help you...
Click to expand...
 
Back
Top