Running Microsoft IIS?

IIS site down or stuck on old Windows? We take it on.

Most IIS servers that reach us are quietly holding up a line-of-business app that was written years ago by somebody who has long since moved on. We get the Application Pool healthy again, sort out the web.config, and plan what happens next before the Windows version itself falls out of support.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

Application event log

still failing

What it is

Microsoft IIS at a glance

Internet Information Services, known as IIS, is Microsoft's web server. It has shipped with Windows Server since 1995 and the current release is version 10, bundled with Windows Server 2016, 2019, 2022 and 2025 as well as the client editions of Windows.

IIS hosts classic ASP, ASP.NET Framework in-process through System.Web, ASP.NET Core either out-of-process or in-process via the ASP.NET Core Module, PHP through FastCGI, and ordinary static sites. It is managed with the inetmgr console, with the WebAdministration PowerShell module, or with appcmd.exe. In most shops it sits next to Active Directory and SQL Server.

Type
Web server for Windows Server
First released
1995
License
Proprietary, bundled with Windows Server
Maintained by
Microsoft Corporation
Typically used for
ASP.NET apps, intranet apps, SharePoint, Exchange, legacy classic ASP, line-of-business web services

The honest version

Microsoft IIS pros and cons

No technology is all upside. This is where Microsoft IIS earns its place and where it tends to cause trouble.

Where Microsoft IIS is strong

  • At home on WindowsIntegrated Windows Authentication against Active Directory and the kernel-mode output cache are first-class features here, not add-ons. For an intranet app that honours domain logins, nothing else is as straightforward.
  • Hosts both flavours of .NETASP.NET Framework apps run in-process through System.Web, and ASP.NET Core apps run behind the ASP.NET Core Module. The same server keeps a 2008 WebForms app and a .NET 8 API alongside each other.
  • URL Rewrite and ARRThe URL Rewrite module handles redirects and canonical hostnames at the server level. Application Request Routing turns IIS into a capable reverse proxy for internal services, with no second product to license.
  • The admin console people already knowWindows administrators have clicked through inetmgr for twenty years. Handing an IIS server to a Windows team rarely needs training, which matters when the on-call rotation is already stretched.
  • Strong performance on its home platformOn Windows Server with a sensible AppPool configuration and the kernel cache enabled, IIS serves static and cached content very quickly indeed.

Where Microsoft IIS bites

  • You pay for the Windows licenceUnlike Linux web servers, every IIS box carries a Windows Server licence cost, plus CALs where they apply. On a fleet this is not trivial, and it rules IIS out for many small-scale public sites.
  • Certificates and bindings are clickyRenewing a TLS certificate means a trip through certlm.msc to import it and inetmgr to rebind it. Scripting the whole dance with PowerShell is possible but seldom what the previous admin left behind.
  • web.config complexityThe <system.webServer> section accumulates handlers, modules, rewrite rules and request filtering settings. One stray XML element returns HTTP Error 500.19 and the whole site is down until somebody reads the config carefully.
  • AppPool recycles bite in-memory cachesDefault recycles at 1740 minutes or on a memory threshold quietly discard everything a worker process held. Apps that assumed a long-lived cache or an open database handle behave oddly after each recycle until that assumption is removed.
  • Legacy services keep you pinnedProduction .asmx web services and WCF endpoints are everywhere inside Windows shops. They only run on the full Framework on IIS, which keeps the server tied to this platform long after the rest of the stack has moved on.
  • Windows updates reboot the serverPatch Tuesday schedules reboots that take the whole site offline for a few minutes unless there is a second node to fail over to. Planning around this is a job on its own.
  • Runtime and module versions confuse peopleCore 3.1, 5, 6, 7 and 8 each want a matching ASP.NET Core Module and hosting bundle. Framework apps need the right CLR version set on the AppPool. Mixing these up gives you the ANCM In-Process Start Failure page and no clue why.

Sound familiar?

Common Microsoft IIS problems we fix

The Microsoft IIS problems that bring people to us, and what you have once each one is fixed.

HTTP Error 500.19

The site returns 500.19 and nobody knows why

An invalid element in web.config, almost always from a recent deploy or a missing module such as URL Rewrite or the ASP.NET Core Hosting Bundle.

Config repaired, site back up

503 Service Unavailable

The Application Pool keeps stopping

Rapid-fail protection has tripped after repeated crashes in the worker process. The underlying cause is usually an unhandled exception at startup or a bad AppPool identity.

Pool stable, cause fixed

ANCM In-Process Start Failure

An ASP.NET Core app refuses to start

The hosting bundle version on the server does not match the framework the app was built against, or the AppPool is not set to No Managed Code.

Runtime aligned with the app

Windows Server 2012 R2

The Windows version is out of support

The server hosts a legacy app and nobody has scheduled the move to a supported Windows release. Every month the risk grows.

Migrated to a supported host

handler mapping missing

A legacy classic ASP or WCF app stopped responding

A role or feature was removed during a tidy-up, or a web.config inherits a handler that is no longer installed on the box.

Handlers restored and documented

SSL binding: certificate not found

The TLS certificate did not renew cleanly

A new certificate is in the store but the binding still points at the old thumbprint, or the private key is not marked exportable.

Renewal scripted end to end

last admin: unknown

The developer who built it has gone

An IIS server with hand-edited web.config files, scheduled tasks and no written-down logins. The business still needs the app it is running.

Ownership and access returned to you

What we do

IIS help, from rescue to replatform

Call us for one broken site, or hand over the whole Windows estate.

Rescue
AppPool crash loops, 500.19 after a deploy, certificate renewals that broke the binding. We get the site serving again, then find out what caused it.
Legacy takeover
A Windows web app nobody at your company wants to touch. We document it, back it up properly, and either keep it running or plan its replacement.
Upgrades
Moving from Windows Server 2012 R2 or 2016 onto a supported release, and from Framework 4.x to a modern .NET where it makes sense.
Hardening
Request filtering, TLS configuration, AppPool identity reviews, and getting Windows Update on a rhythm that does not surprise anyone.
Migrations
Off IIS to Kestrel on Linux where that fits, or between Windows hosts where it does not. Decided on evidence, not fashion.
Managed Tech
Monitoring, patching windows, backups and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Microsoft IIS alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Microsoft IIS questions

Something else? Call+1 737 727 7327

Can you fix our IIS site returning 500.19?

Yes. HTTP Error 500.19 almost always points at web.config, usually a missing module such as the URL Rewrite extension or the ASP.NET Core Hosting Bundle, or an element that is locked at the server level. We read the detailed error, fix the real cause, and leave notes behind so the next person understands what changed.

Why does our Application Pool keep crashing?

A 503 with the pool stopped usually means rapid-fail protection has tripped after repeated worker process crashes. The underlying reason is an unhandled startup exception, a wrong AppPool identity that cannot read its own files, a bad connection string, or a runtime mismatch. We attach a dump, read the actual exception, and fix that rather than just restarting the pool.

Can you take over a legacy IIS Windows web app?

Yes, and this is a lot of what we do. We take inventory of the sites, pools, bindings, scheduled tasks and dependencies, get backups you can actually restore from, and give you a written picture of what the server does before we change anything on it.

Should we move from IIS to Kestrel on Linux?

Sometimes. For a modern ASP.NET Core app that does not need Windows Authentication or Windows-only libraries, Kestrel behind nginx on Linux is cheaper to run and simpler to patch. For a WebForms or WCF estate tied to Active Directory, staying on IIS is usually the honest answer.

Why are our web.config URL Rewrite rules not firing?

Either the URL Rewrite module is not installed on the server, the rule syntax has an error that silently disables it, or a parent web.config higher up the tree is overriding your rule. We check the failed request trace, confirm which rule is actually matched, and correct the one that is wrong.

How much does IIS help cost?

Estimates are free. Share the IIS version, the web.config and the recent event log entries, and we quote a scope before anyone remotes in.

Free estimate

IIS giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.