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
Running Microsoft IIS?
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.
What it is
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.
The honest version
No technology is all upside. This is where Microsoft IIS earns its place and where it tends to cause trouble.
Sound familiar?
The Microsoft IIS problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
Call us for one broken site, or hand over the whole Windows estate.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: