Skip to main content

Troubleshooting IIS

I recently had the pleasure if misdiagnosing a problem and spending 2 days in the deep weeds of IIS.  Figured I'd share my learnings and increase google fodder.

Update: Another finding, '500 0 0' entries that don't work with Failed Request Tracing should be dropping stuff in the Application log.

  1. Figure out how to reproduce the error, maybe write a test? :)
  2. Gather the specific error code:  "500" is the request status code, you also have subStatus codes and win32-status codes.  e.g. 500.1.1, 403.1.2
    1. If you have server access, set the hosts file on the server to point to, then load a browser on the server itself and re-create the error - moar info
      1. This also usually yields actual error messages (which are generally also dumped into the Application event log)
    2. You can change a web.config setting for show remote errors (I've had so-so luck with it in the past)
  3. Check the event log
    1. Usually in the Application log you'll see ASP.NET errors/warnings
    2. You can filter System for: Source: HttpEvent
    3. AppPool recycles are logged
    4. IISRESETs are logged
  4. Check the IIS logs
    1. C:\inetpub\logs\LogFiles\W3SVC1 (corresponds to IIS site id #)
    2. Each line should have 500 0 1 or something matching the actual error code
      1. 2016-08-18 00:00:08 GET /keepalive.aspx - 443 - ELB-HealthChecker/1.0 - 200 0 0 0
        1. See the end?  200 is the status code, 0 is substatus, 0 is win32-status, 0 is bytes
        2. Win32 codes:
  5. Check the appPool status ( crashes can leave it in a stopped state, or Rapid Fail Protection could be kicking in, perhaps the default 30hour recycle is going on?)
    1. Bad code is usually the cause of legit crashes.  Ensure the code has logging on crashes.
  6. White screen of death.  (user only sees a white screen, nothing else, fast load time)
    1. Test locally on the server.  Does it work?
    2. Are you running a load balancer?
    3. Are any instances in the pool?
    4. No?
    5. Because you didn't account for a change that broke the health check?
    6. Fix the health check!
  7. You are deep in the weeds now.  Here there be dragons.
  8. Check HTTPERR logs: C:\Windows\System32\LogFiles\HTTPERR
  9. You might see something like: 2016-08-17 02:50:07 14728 80 HTTP/1.1 GET /keepalive.aspx 503 1 N/A DNN
    1. 80 HTTP/1.1 GET /keepalive.aspx 503 1 N/A DNN
      1. port, protocol, request type, request path, status code, sub-status code, REASON, appPool
        1. N/A - A service unavailable error occurred (an HTTP error 503). The service is not available because an internal error (such as a memory allocation failure or URL Reservation List conflict) occurred.
  10. If you are seeing 503 errors, you are really in the weeds.  http.sys is the thing that handles basic request routing for the appPools, and 503 means "the down...the system...", i.e. the appPool isn't even seeing the reqs.
  11. Check here for a list of 503 REASONS:
    1. Boiled down:
      1. Bad configuration file XML
        1. web.config
        2. C:\Windows\System32\inetsrv\config
        3. C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CONFIG\machine.config
      2. Overloading of the server
      3. Identity/permissions (appPool identity, file perms, combo of both)
      4. URL reservation issues or IP inclusion list
      5. appPool issues
  12. Failed Request Tracing
    1. If you rely on IIS, you probably should use's not too bad once you get over the gotchas
  13. If URL reservation/IP inclusion list issues:
    1. netsh http show servicestate
    2. netsh http show urlacl
  14. Other random stuff to try if you're this desperate.  These were pulled as common comments 'solutions'.
    1. Commenting out the IPv6 entry in hosts (wat)
    2. Enable 32-bit on the appPool (you coded something wrong/badly)
    3. aspnet_regiis.exe /i  (this is a horrible solution)
    4. Starting the stopped appPool (you would be amazed how often this came up)

Code Snippet to test web.config (PowerShell)

#I did not write this, one of those links' authors did.
Import-Module WebAdministration
$site = "DNN" #or whatever
 Get-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST' -location "$site" -filter "system.webServer" -name . | Out-Null
 Write-Output "All is Well"
catch [System.Exception]
 Write-Output $_ 

Some reading


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…