When an application pool stops, the Windows Process Activation Service (WAS) shuts down totally every single worker processes that are running and which serves that particular application pool. When this happens, all those shutdown worker processes cannot be started again by the Windows Process Activation Service.
Therefore, it has to be an administrator who will start these application pools that have stopped. Errors bearing the tag “503 Service Unavailable†is sent to every single application routed to an application pool which stopped.
You should also note that this applies only to the Windows 7 platform, the 2008 Windows Server, the 2008 R2 Windows Server and finally the Windows Vista platform.
Application Pools Feature Requirements (IIS 7)
Here, you will find all the requirements you need to configure application pools.
Requirement 1: Levels.
You can perform the steps used to configure application pools in IIS at the web server level.
Requirement 2: Handlers and modules.
On a Web Server, there are some necessary handlers and modules which are to be installed and also enabled at that particular level, where you perform this procedure.
Requirement 3: Permissions
In this particular section, it a necessity for you to be an administrator of the server in order to use the IIS manager to carry out procedures. If you run WMI scripts, edit files for configurations or make use of the Appcmd.exe to carry out procedures, then it is a necessity for you to write a passage to either the configuration files or file which have been targeted as the case may be.
How To Start Or Stop An Application Pool
You can perform this procedure by using the user interface (UI), by running Appcmd.exe commands in a command-line window, by editing configuration files directly, or by writing WMI scripts.
How To Start Or Stop An Application Pool with User Interface
To use the UI
This particular procedure can be performed by either making use of the User Interface popularly known in the IT World as UI, by directly editing the files for configuration, by the writing of scripts for WMI or by the running of commands of the Appcmd.exe in a window for the command line.
In order to make a change of the Application Pool, the following steps would be of a very good assistance if followed correctly.
Step 1: Open IIS Manager
Opening of the IIS Manager is the very first thing to do when you want to use the UI.
Step 2: Choose Application Pool
This entails you navigating into the pane for “Connections†and then access the server node, where you would see a list of options and you select the “Application Pools†option.
Step 3: Choose Application Pool Type
When you have accessed the page for the “Applications Poolsâ€, then select the type of application pool which you would like to either stop or start.
Step 4: Click Start or Stop Applications
Navigate to the pane tagged “Action†and tap on either the Stop or the Start procedure in order to end or begin the application pool. This action stops or starts the application pool as the case may be.
Command Line
Make use of the syntax below if you wish to start an application pool. The syntax is thus:
"**appcmd start apppool /apppool.name:**string"
What the application you wish to start is called is "app.namestring" which is a variable. An example is when you wish to begin an application pool known as “Businessâ€, then this is the format you should use in typing at the prompt of the command after which you then tap on the “Enter buttonâ€.
"appcmd start apppool /apppool.name:Business"
Make use of the syntax below if you wish to start an application pool. The syntax is thus:
"**appcmd stop apppool /apppool.name:**string"
What the application you wish to stop is called is "app.namestring" which is a variable. An example is when you wish to end an application pool known as “Businessâ€, then this is the format you should use in typing at the prompt of the command after which you then tap on the “Enter buttonâ€.
"appcmd stop apppool /apppool.name:Business"
ppcmd.exe (IIS 7)
There is a new tool for the command-line provided by IIS 7 known as Appcmd.exe which is used in configuring and querying objects within your web server and also in returning the output in either the XML or text.
You can use the Appcmd.exe to create sites and at the same time configure them, create and also to configure virtual directories, application pools and applications. It can also be used to either stop or start sites, stop, start and also recycle different application pools, and finally to see information pertaining to worker processes and those Web server requests, running.
The Appcmd.exe also provides commands consistently for queries which are common and tasks for configurations and this helps to reduce the syntax learning complexity. An example is when you want to get information concerning a certain element like an application, you can make use of the command tagged “list†and when creating a specific element like a site, then the command tagged “add†would serve.
IIS Settings Schema in IIS 7.0
The settings schema of the IIS makes the provision for the basis for configuring the IIS 7.0. Now, majority of the properties for the meta-base you utilized in the versions of the IIS which are now outdated, have finally been transformed into attributes or elements in the schema.
Starting or Stopping an Application Pool with WMI
You can make use of the ApplicationPool.Stop WMI method and also the ApplicationPool.Start
method to adequately complete this particular procedure.
Check out these top 3 Windows hosting services:
- Your search to the best windows hosting can end by clicking here.
