IDC资讯中心
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).
messageid= 1018
severity=error
failed while registering asp.net (version %1) in iis. error code: %2.
messageid= 1019
severity=informational
finish registering asp.net (version %1). detailed registration logs can be found in %2.
messageid= 1020
severity=warning
updates to the iis metabase were aborted because iis is either not installed or is disabled on this machine. to configure asp.net to run in iis, please install or enable iis and re-register asp.net using aspnet_regiis.exe /i.
messageid=1021
severity=informational
starting %1.
messageid=1022
severity=informational
stopping %1.
messageid=1023
severity=informational
restarting w3svc.
messageid=1024
severity=error
failed while restarting w3svc. error code: %1.
messageid=1025
severity=informational
finish restarting w3svc.
messageid=1026
severity=warning
during unregistration (version %1), a clean uninstall was done because the process failed to get the next highest version. error code: %2.
messageid=1027
severity=informational
start unregistering asp.net (version %1).
messageid=1028
severity=error
failed while unregistering asp.net (version %1) in iis. error code: %2.
messageid=1029
severity=informational
finish unregistering asp.net (version %1). detailed unregistration logs can be found in %2.
messageid=1030
severity=warning
updates to the iis metabase were aborted because iis is either not installed or is disabled on this machine. to completely uninstall asp.net from iis, please re-enable iis and unregister asp.net using aspnet_regiis.exe /u.
messageid=1031
severity=informational
the current version at the iis root is %1.
messageid=1032
severity=warning
registration (version %1) will not register the dll in the scriptmap properties of any iis website because the version is not high enough to replace the existing one at the root. see help for the explanation of version comparison during installation.
note the words "web site" are capitalized incorrectly in the message.
messageid=1033
severity=error
registration failed when trying to find the highest version installed on the machine. error code: %1.
messageid=1034
severity=warning
failed reading registry key %1 for value %2. error code: %3.
messageid=1035
severity=warning
failed while verifying that the asp.net dll (path:%1) (version:%2) exists. error code: %3.
messageid=1036
severity=warning
failed while verifying that the asp.net dll (version:%1) exists. error code: %2.
messageid=1037
severity=warning
the asp.net dll (path: %1) (version:%2) is missing.
messageid=1038
severity=warning
failed while getting the version of %1, which is found in a scriptmap in iis. the file could be missing. error code: %2.
messageid=1039
severity=warning
registration failed to find the highest installed version from the registry. as a result, registration will use the iis default document, mimemap settings and isapi filter dll path from the current version. error code: %1.
messageid=1040
couldnt create app domain.
messageid=1041
unhandled exception in managed code.
messageid=1041
failed to assign request using process model.
messageid=1042
cannot queue the request.
messageid=1043
aspnet_isapi.dll can not run in dllhost.exe. please, re-register aspnet_isapi.dll.
messageid=1044
managed code failure while executing this request.
messageid=1045
worker process stopped unexpectedly.
messageid=1046
server unavailable.
messageid=1048
server application unavailable.
messageid=1049
the web application you are attempting to access on this web server is currently unavailable. please hit the "refresh" button in your web browser to retry your request.
note the word "web" is capitalized incorrectly two times in the message.
messageid=1050
administrator note:
messageid=1051
an error message detailing the cause of this specific request failure can be found in the application event log of the web server. please review this log entry to discover what caused this error to occur.
note the word "web" is capitalized incorrectly in the message.
messageid=1052
worker process was recycled.
messageid=1053
username and/or password supplied in the processmodel section of the config file are invalid.
messageid=1054
worker process was recycled because it exceeded the configured time limit.
messageid=1055
worker process was recycled because it exceeded the configured idle time limit.
messageid=1056
worker process was recycled because it exceeded the configured requests limit.
messageid=1057
worker process was recycled because its request queue exceeded the configured limit.
messageid=1058
worker process was recycled because its memory consumption exceeded the configured limit.
messageid=1059
worker process was recycled because it failed to respond to ping message.
messageid=1060
<html><body><h1>server is too busy</h1></body></html>.
messageid=1061
asp.net does not support /3gb memory mode.
messageid=1062
severity=error
it is not possible to run two different versions of asp.net in the same iis process. please use the iis administration tool to reconfigure your server to run the application in a separate process.
messageid=1063
severity=warning
failed while reading the asp.net client side script files to be copied to each website. error code: %1.
note the words "web site" are capitalized incorrectly in the message.
messageid=1064
severity=warning
failed while creating the asp.net client side script files directories under %1. error code: %2.
messageid=1065
severity=warning
failed while listing the asp.net client side script files directories under %1. error code: %2.
messageid=1066
severity=warning
failed while copying the asp.net client side script files (source: %1) (destination: %2). error code: %3.
messageid=1067
severity=warning
failed while copying the asp.net client side script files (file: %1). error code: %2.
messageid=1068
severity=warning
failed while copying the asp.net client side script files to directories under %1. error code: %2.
messageid=1069
severity=warning
failed while removing the asp.net client side script files to directories under %1. error code: %2.
messageid=1070
severity=warning
failed while removing the asp.net client side script files directory (%1). error code: %2.
messageid=1071
severity=warning
failed while setting the access for the asp.net client side script files directory (iis application path: %1) in iis. error code: %2.
messageid=1072
severity=warning
failed while removing the access for the asp.net client side script files directory (iis application path: %1) in iis. error code: %2.
messageid=1073
%1.
messageid=1074
severity=error
an error occurred in while processing a request in state server. major callstack: %1. error code: %2.
messageid=1075
severity=error
state server socket timeout thread exits because of repeating error. error code: %1.
messageid=1076
severity=informational
state server starts listening with %1 listeners.
messageid=1077
severity=informational
state server stops listening.
messageid=1078
severity=error
the state server has closed an expired tcp/ip connection. the ip address of the client is %1.%2.%3.%4. the expired %5 operation began at %6/%7/%8 %9:%10:%11.
messageid=1079
severity=error
(for debugging) state server expiry thread is closing a socket. the ip address of the client is %1.%2.%3.%4. the expired %5 operation began at %6/%7/%8 %9:%10:%11.
messageid=1080
"provides support for out-of-process session states for asp.net. if this service is stopped, out-of-process requests will not be processed. if this service is disabled, any services that explicitly depend on it will fail to start."
messageid=1081
"asp.net state service" .
messageid=1082
severity=error
installation failed because the user does not have administrative rights on this machine.
messageid=1083
severity=error
uninstallation failed because the user does not have administrative rights on this machine.
messageid=1084
severity=error
aspnet_wp.exe could not be started. the error code for the failure is %1. this error can be caused when the worker process account has insufficient rights to read the .net framework files. please ensure that the .net framework is correctly installed and that the acls on the installation directory allow access to the configured account.
messageid=1085
asp.net machine account.
messageid=1086
account used for running the asp.net worker process (aspnet_wp.exe).
messageid=1087
failed to execute request due to internal failure. error: %1.
messageid=1088
failed to execute request because the app-domain could not be created. error: %1.
messageid=1089
failed to execute the request because the asp.net process identity does not have read permissions to the global assembly cache. error: %1.
messageid=1090
failed to execute request because queryinterface for asp.net runtime failed. error: %1.
messageid=1091
failed to execute request due to unknown error. error: %1.
messageid=1092
deadlock detected.
messageid=1093
unable to get the private bytes memory limit for the w3wp process. the asp.net cache will be unable to limit its memory use, which may lead to a process restart. error: %1.
references
for more information about event log entries in asp.net, visit the following microsoft developer network (msdn) web site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbconintroductiontoeventlogcomponents.asp
