Problem Analysis and Troubleshooting

Module Overview
Types of problems that affect IIS How to identify them

What can cause them

How to troubleshoot them Lots of hands on!

Section 1: Common IIS-Related Problems

Application Crash 100% CPU Hang

0% CPU Hang
Performance Issues Memory Leaks

Startup Problems
Access Issues

Application Crash - How to Identify

Browser errors The connection with the server was reset The remote procedure call failed The RPC server is unavailable ASP 0115 / HTTP 500 Event logs

IIS logs

Application Crash - Possible Causes

Stack overflow Stack corruption

Heap corruption
Divide by Zero Null pointer dereference

Any other unhandled exception

Application Crash - How to Troubleshoot

Review event logs Review IIS logs for HTTP 500/ASP 0115 errors

Switch off all proactive recycling

Run ADPlus or DebugDiag in crash mode Analyze memory dump in WinDBG

100% CPU Hang - How to Identify

Browser shows only blank page or times out Pages take a long time to load on browser

Check CPU usage in Task Manager or Performance Monitor

100% CPU Hang - Possible Causes

Long loops Infinite loops

Memory leaks
String manipulation Garbage collection

Insufficient hardware

100% CPU Hang - How to Troubleshoot

Switch off all proactive recycling Wait for problem to occur again

Gather Perfmon data

Run ADPlus or DebugDiag in hang mode Analyze Perfmon data

Analyze memory dump in WinDBG

Perform live debug to identify the root cause, if required

0% CPU Hang - How to Identify

Browser shows only blank page or times out Create simple .htm, .asp, .aspx pages

Attempt to browse to each test page

Does process recover if load is removed? Easy to confuse with performance issues

0% CPU Hang - Possible Causes

Serialization Deadlocks

Orphaned critical sections or monitors

Microsoft Visual Basic (VB) RIM/UE issues Failing COM/database/remoting calls

0% CPU Hang - How to Troubleshoot

Switch off all proactive recycling Enable process orphaning

Run DebugDiag or ADPlus in hang mode

Analyze memory dump in WinDBG !locks

!critsec
!syncblk

Performance Issues - How to Identify

Users report application is running slowly Application appears to hang

Performance Issues - Possible Causes

Too many to mention! Serialization

Long COM/database/remoting calls

Insufficient hardware Network congestion

Poor quality application code

Performance Issues - How to Troubleshoot

Performance Monitor Perfmon baseline logs

Stress testing tools

Application Center Test WCAT

Log Parser

Memory Leaks - How to Identify

Popup message stating "System out of virtual memory Random problems associated with a lack of virtual memory Degrading system performance and excessive swapping Failed memory allocations

Memory Leaks - Possible Causes

Application failing to free private memory or resource allocations Includes memory, user and gdi objects, handles, threads, etc. Abnormal code paths which bypass free logic Logic errors

Memory Leaks - How to Troubleshoot

Performance Monitor PMON.EXE

DebugDiag (LeakTrack)
UMDH.exe LeakDiag (Microsoft PSS Tool)

Startup Problems - How to Identify

IIS fails to start IIS starts very slowly

Startup Problems - Possible Causes

Large metabase files Permissions

Corrupt/missing Machine Keys

Startup Problems - How to Troubleshoot

Event logs ETW Event Tracing

Access Issues - How to Identify

Users receive unexpected authentication prompts Users get Access Denied messages

Access Issues - Possible Causes

Incorrect authentication schemes configured DC comms issues

Incorrect user or process identity permissions

Access Issues - How to Troubleshoot

Network Monitor (NetMon) WFetch

AuthDiag
Log Parser ASPNET_regiis

Permissions Verifier

Section 2: Labs - Troubleshooting Scenarios

Action Planning Exercise

Think about how youll apply the concepts and/or practices youve learned when you return to your workplace. 1.Summarize your action items 2.Questions for your trainer? 3.Class discussion