IIS application pool keeps stopping

When an IIS application pool keeps stopping, resetting all of IIS brings the site back for a while, but it takes every other site on the server down with it and leaves the cause in place. 2501 finds out why the pool stops, fixes what it safely can and restarts only that pool, within limits you set.

The cause may be a configuration error, a missing file, a permission, or the account the pool runs under, with an expired password or a locked account.

What 2501 does

The Services Manager Windows specialty investigates before it changes anything, from the pool's settings and account to the event logs, and names the cause with the Windows events that show it. It corrects an obvious configuration error, restarts only that pool or site and confirms the site is healthy; if the pool stops again, it looks further rather than restarting it again. An account problem that needs work in Active Directory, or a full disk, can be handed to the agent that covers it. The report says what it found and did.

You stay in control

• You choose the level: investigate only, act after a person confirms, or act on its own within your rules. The level is set per specialty, not per ticket.
• One pool, not the whole server: it never resets all of IIS at once, never restarts the server and never switches off security tools such as Windows Defender.
• Account and security changes wait for a person: resetting a service account's password, changing Active Directory permissions, configuration beyond a simple fix, and anything that looks like a security incident.
• Your rules apply: which servers, sites and pools may be restarted unattended, and which change windows apply.

Frequently asked

Why does the pool keep stopping by itself? IIS stops a pool on purpose when its worker process crashes several times in a short period. Starting it again without fixing the cause starts the cycle over.

Can it diagnose without restarting anything? Yes. In investigate-only mode it reports the cause and the fix it would make, and changes nothing.

Related

• Services Manager Windows
• Windows Server automation
• Windows server running slowly
• Guardrails: what an agent may never touch