iis7开发系列课程4iis7.0故障解决

Level

200收听本次课程需必备的条件了解.NET了解IIS了解Windows

ServerIIS7

的和故障排除能力可以轻松的看到All站点的state，AppPools,Worker

Processes,

and

App

s实时处理中看到实时请求情况从开始到结束中

在同一个操作界面一个请求操作ASP.NET

和IIS设置自动

错误请求Runtime

Status

an可以获得运行状况

AppPoolsWorkerProcessesWebSitessApp

目标直接操作展示运行状态Control

RSCARSCDemo内容Runtime

Status

and

Control

Data——改进当前请求List详细的信息管道及时状态、运行模块进程请求App

List通过WMI和代码展示oRuntime

Status

and

Control

Data——

APIApplicationPool：提供

状态状况ServerManager.Applicati nPools

:

givesallpoolsStatus

Data:ApplicationPool.NameApplicationPool.StateApplicationPool.WorkerProcessesActions/Controls:ApplicationPool.Start()ApplicationP

.

top()ApplicationPool.Recycle()WorkerProcess：Status

Data:IDSite.StateActions/Controls:Site.Start()Site.Stop()：象cRuntime

Status

and

Control

Data——操作数据和对ApplicationStatus

Data:AppID.Unload()Virtual

and

Physical

PathsSite

IDI

lControls:Unload

app :

Appli

ationSite：Status

Data:PID/GUID/AppPool

NameState

–

can

be

starting/running/stop/unknownCurrently

Executing

Requests

–

WorkerProcess.GetRequests(0)Currently

loaded

App s

–

WorkerProcess.ApplicationsDemo内容Tracing——灵活性独立

：ETW：Event

Tracingfor

WindowsAutomatic

Failure

Req

Tracing

(FREB)…insert

your

own

format

here…灵活性：

添加Tracing——如何工作登记模板通过trace

configuration管道模块readconfiguration管道模块提交trace

event返回处理事件所有的IIS类似300

eventsin

core

IIS7You

can

create

your

ownTraceeventourceTraceeventproviders/consumerw3coreAnypipelinemoduleTRACE_EVENTConsumermodule(etw,

frebetc)TraceconfigReadtraceconfigMy

traceoutputformatAutomatic

Failure eq

Tracing失败requestsList打开tracing

不仅仅是“fail d

requests”Automatic

Failure

Req

Tracing

(FREB)对每一个失败的URL的自定义多条目状态/子状态代码事件冗长（登陆失败etc.每个URL

trace

configuration允许自定义URL例如：“*.aspx”——如何使用ApplicationHost.configAutomatic

Failure

Req

TracingAutomatic

Failure

Req

Tracing——如何使用Configure

failure

definitions

in

web.configDefine

URLDefine

failure

definitionsDefine

what

areas

to

trace

per

URLASPX

Page

Eventracing——如何使用How

to

enable

it:Turn

page

tracing

on

(nothing

new

here)<%Page

Trace=“True”%>Configure

FREB

to

look

for

ASPN T

provider,

Page

flag<traceFailedRequests><add

path=“login.aspx”

><tr

ceAreas><add

provider=“ASPNET”

area=“Page”

verbosity=“verbose”

/></traceAreas><failureDefinitions

statusCodes=“401”

/

></add><traceFailedRequests>Events

come

out

with:Data:

connection

ID,

Activity

ID

(for

correlation),

Uri,

and

the

messagelogged

in

the

or

allSeparate

event

types

for

Trace.Warn()

and

Trace.Write()Write()

events

:

verbosity=“verbose”Warn()

events

:

verbosity=“warning”的

latform

Tracing在IIS7

Tracing

Infrastructure

中定义路径：

ASP.NET

Page

Trace.W

ite()and

Trace.Warn()callsSystem.Diagnostics.TraceSource

callsWebEvents

raised

on

co text

of

requestIISTraceListener<atype=“Mi</shatrace

source:加入Trace

Events

模板System.Diagnostics.TraceSourceIIS7

adds

a

new

Trace

Listener

forTraceSource

calls

–<system.Diagnostics><sharedListeners>dd

name=“IISTraceListener”crosoft.IIS.IIS7Tra…”/>redListeners>Create

new

trace

source

in

config

for

your

module

–example:

myModuleSourceAdd

the

IISTraceListener

as

a

listener

for

your

module<sources><source

name=“myModuleSource”><!--

now

IaddtheIIS7TraceListener

asalistener

--><listeners><add

name=“IISTraceListener”

/></listeners></source></sources>Demo内容：On-demand

runtime

state

and

control

of

objectsExtensible

tracing

subs

stemSubsystem

publishing

and

consumption

APIs

areexposed

publiclyYou

can

roll

your

own

trace

output

moduleIIS

modules

are

built

on

these

publicAPI’sNo-re ro

Tracin viaF

EBAdd

your

own

trace

event