Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Different event log entries that are generated by ASP.NET

Different event log entries that are generated by ASP.NET

View products that this article applies to.

Introduction

This article describes the event log entries that you can find when you use Microsoft ASP.NET.

↑ Back to the top

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
    Couldn't 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.

↑ Back to the top

References

For more information about event log entries in ASP.NET, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/dhacse28(vs.71).aspx

↑ Back to the top

Keywords: KB835387, kbinfo, kbaspobj, kbeventlog

↑ Back to the top

Article Info
Article ID : 835387
Revision : 6
Created on : 12/3/2007
Published on : 12/3/2007
Exists online : False
Views : 453