Different event log entries that are generated by ASP.NET
INTRODUCTION
This article describes the event log entries that you can find when you use Microsoft ASP.NET.
MORE INFORMATION
The following list describes the different types of event log entries that you may experience when you use ASP.NET:
MessageId=1000
Severity=Error
aspnet_wp.exe (PID: %1) stopped unexpectedly.
MessageId= 1001
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because memory consumption exceeded the %2 MB (%3 percent of available RAM).
MessageId= 1002
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because the number of queued requests exceeded %2.
MessageId= 1003
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last %2 seconds. This timeout may be adjusted using the <processModel responseDeadlockInterval> setting in machine.config.
MessageId= 1004
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after %2 seconds.
MessageId= 1005
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after being idle for %2 seconds.
MessageId= 1006
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after serving %2 requests.
MessageId= 1007
Severity=Error Symbolic
aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.
MessageId= 1008
Severity=ERROR
aspnet_wp.exe (PID: %1) was recycled because it failed to respond to ping message.
MessageId= 1009
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the synchronization event could not be initialized. Error code: %2.
MessageId= 1010
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the synchronous pipes could not be initialized. Error code: %2.
MessageId= 1011
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the asynchronous pipe could not be initialized. Error code: %2.
MessageId= 1012
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the .NET Runtime could not be initialized. Error code: %2.
MessageId= 1013
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because CoInitializeEx failed. Error code: %2.
MessageId= 1014
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because CoInitializeSecurity failed. Error code: %2.
MessageId= 1015
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the aspnet_isapi.dll could not be initialized. Error code: %2.
MessageId= 1016
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because of failure to create the thread for answering ping messages. Error code: %2.
MessageId= 1017
Severity=Informational
Start registering ASP.NET (version %1).
Messa
This article describes the event log entries that you can find when you use Microsoft ASP.NET.
MORE INFORMATION
The following list describes the different types of event log entries that you may experience when you use ASP.NET:
MessageId=1000
Severity=Error
aspnet_wp.exe (PID: %1) stopped unexpectedly.
MessageId= 1001
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because memory consumption exceeded the %2 MB (%3 percent of available RAM).
MessageId= 1002
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because the number of queued requests exceeded %2.
MessageId= 1003
Severity=Error
aspnet_wp.exe (PID: %1) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last %2 seconds. This timeout may be adjusted using the <processModel responseDeadlockInterval> setting in machine.config.
MessageId= 1004
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after %2 seconds.
MessageId= 1005
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after being idle for %2 seconds.
MessageId= 1006
Severity=Informational
aspnet_wp.exe (PID: %1) was recycled after serving %2 requests.
MessageId= 1007
Severity=Error Symbolic
aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.
MessageId= 1008
Severity=ERROR
aspnet_wp.exe (PID: %1) was recycled because it failed to respond to ping message.
MessageId= 1009
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the synchronization event could not be initialized. Error code: %2.
MessageId= 1010
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the synchronous pipes could not be initialized. Error code: %2.
MessageId= 1011
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the asynchronous pipe could not be initialized. Error code: %2.
MessageId= 1012
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the .NET Runtime could not be initialized. Error code: %2.
MessageId= 1013
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because CoInitializeEx failed. Error code: %2.
MessageId= 1014
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because CoInitializeSecurity failed. Error code: %2.
MessageId= 1015
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because the aspnet_isapi.dll could not be initialized. Error code: %2.
MessageId= 1016
Severity=Error
aspnet_wp.exe (PID: %1) failed to startup because of failure to create the thread for answering ping messages. Error code: %2.
MessageId= 1017
Severity=Informational
Start registering ASP.NET (version %1).
Messa
相关文章
 我来说两句 |
对此文章发表了评论 |
评论列表 （最新 评论仅限网友观点！）
推荐文章
