400 cannot resolve this request.
401.1 Unauthorized: Access denied due to invalid credentials.
401.2 Unauthorized: Access was rejected because the server configuration tended to use alternate authentication methods.
401.3 Unauthorized: Access because the ACL's settings for the requested resource are denied.
401.4 Unauthorized: The filter authority installed on the WEB server failed.
401.5 Unauthorized: ISAPI/CGI application authorization failed.
401.7 Unauthorized: Access is denied because of a URL authorization policy on the Web server.
403 Prohibit access: Access is denied.
403.1 Prohibit access: execution access is denied.
403.2 Prohibit access: Read access is denied.
403.3 Prohibit access: Write access is denied.
403.4 No access: You need to view the resource using SSL.
403.5 No access: You need to view the resource using SSL 128.
403.6 Prohibit access: The IP address of the client is denied.
403.7 No access: SSL client certificate required.
403.8 Prohibit access: The DNS name of the client is denied.
403.9 No access: Too many clients are trying to connect to the Web server.
403.10 Prohibit access: The WEB server is configured to deny execution of access.
403.11 No access: password has changed.
403.12 Prohibit access: The server certificate mapper has denied client certificate access.
403.13 Prohibit access: The client certificate has been revoked on the Web server.
403.14 No access: The directory list has been rejected on the Web server.
403.15 No access: The WEB server has exceeded the Client Access License limit.
403.16 No access: The client certificate is malformed or not trusted by the Web server.
403.17 No access: The client certificate has expired or has not yet taken effect.
403.18 Prohibit access: The requested URL cannot be executed in the current application pool.
403.19 No access: CGI cannot be performed for clients in this application pool.
403.20 No access: Passport Login failed.
404 the file or directory could not be found.
404.1 the file or directory was not found: The Web site cannot be accessed on the requested port.
Note that the 404.1 error will only appear on computers with multiple IP addresses. If a client request is received on a specific IP address/port combination and the IP address is not configured to listen on that particular port, IIS returns a 404.1 HTTP error. For example, if a computer has two IP addresses and only one of the IP addresses is configured to listen on port 80, any requests received from port 80 by another IP address will cause IIS to return 404.1 errors. This error should only be set at this service level because it is returned to the client only when multiple IP addresses are used on the server.
404.2 file or directory cannot be found: The lockdown policy prohibits the request.
404.3 file or directory cannot be found: The MIME mapping policy prohibits the request.
405 The HTTP action used to access the page is not licensed.
406 The client browser does not accept the MIME type of the requested page.
The 407 WEB server requires initial proxy authentication.
410 The file has been deleted.
412 The prerequisites for client setup failed when evaluated on the WEB server.
414 The request URL is too large, so the URL is not accepted on the WEB server.
500 Server Internal error.
500.11 Server Error: The application on the WEB server is shutting down.
500.12 Server Error: The application on the WEB server is rebooting.
500.13 Server Error: The WEB server is too busy.
500.14 Server Error: Invalid application configuration on the server.
500.15 Server error: Direct request GLOBAL is not allowed. Asa.
500.16 Server Error: UNC authorization credentials are incorrect.
500.17 Server Error: URL authorization store could not be found.
500.18 Server Error: The URL authorization store could not be opened.
500.19 Server Error: The data for this file is not configured correctly in the metabase.
500.20 Server error: URL authorization domain could not be found.
500 100 Internal Server error: ASP error.
501 The specified configuration for the header value was not executed.
The 502 Web server received an invalid response while acting as a gateway or proxy server.
WIN2003 SERVER IIS6.0 ASP Error Resolution
Event ID Description
0100 Not enough memory. Unable to allocate the required memory.
0101 unexpected error. function to return |.
0102 requires string input. function requires string input.
0103 requires digital input. The function requires numeric input.
0104 does not allow operation.
0105 The index is out of range. Array index is out of range.
0106 types do not match. The unhandled data type was encountered.
0107 The data size is too large. The size of the data sent in the request exceeds the allowable limit.
0108 failed to create object. An error occurred while creating the object '%s '.
0109 members were not found.
0110 unknown name.
0111 unknown interface.
0112 parameter is missing.
0113 the script timed out. Exceeded the maximum time that the script was run. You can change this limit by specifying a new value for the Server.ScriptTimeout property or modifying the value in the IIS administration tool.
0114 objects are not available for free threads. The Application object only accepts the free thread object, and the object '%s ' is not available for free threading.
0115 unexpected error. A catch error (%x) occurred in the external object. The script cannot continue to run.
0116 the script delimiter end tag is missing. Script block missing script end tag (%>).
0117 script end tag is missing. Script block missing script end tag (</SCRIPT>) or tag end symbol (>).
The end tag of the 0118 object is missing. Object block missing object end tag (</OBJECT>) or tag end symbol (>).
0119 Classid or Progid property is missing. Object instance ' | ' requires a valid CLASSID or Progid in the object tag.
The 0120 Runat property is invalid. The Runat property of a script tag or object tag can only have a ' Server ' value.
The range in the 0121 object tag is invalid. Object instance ' | ' cannot be scoped to application or session. To create an instance of an object that has a session or application scope, you will include the OBJECT tag in the Global.asa file.
The range in the 0122 object tag is invalid. Object instance ' | ' must have application or session scope. This applies to all objects created within the Global.asa file.
0123 missing Id attribute. The Id attribute required for the Object token is missing.
0124 Language property is missing. The Language property required for the Object token is missing.
0125 property end tag is missing. The value of ' | ' property has no end separator.
0126 The Include file was not found. The Include file ' | ' was not found.
The end tag of the 0127 HTML annotation is missing. The HTML annotation or the include file on the server side lacks a closing tag (-->).
0128 File or Virtual property is missing. The Include file name must be specified with the file or Virtual attribute.
0129 unknown scripting language. scripting language ' | ' cannot be found on the server.
The 0130 File property is not valid. The File property ' | ' cannot start with a slash or backslash.
0131 the parent path is not allowed. The Include file ' | ' cannot contain '.. ' to represent the parent directory.
0132 compilation error. Unable to process Active Server Page ' | '.
The 0133 ClassID property is invalid. The OBJECT tag has an invalid ClassID ' | '.
The 0134 ProgID property is invalid. Object has an invalid ProgID ' | '.
0135 loops contain. The file ' | ' contains itself (which may be not directly contained). Please check the other include statements in the include file.
0136 object instance name is invalid. Object instance ' | ' attempted to use a reserved name. This name is used by internal objects in Active Server Pages.
0137 Global script is not valid. The script block must be one of the allowed Global.asa procedures. Scripting instructions are not allowed in the Global.asa file in <%.%>. The allowed procedure name is Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd.
0138 script block nesting. The script block cannot be placed inside another script block.
0139 nested objects. Object tags cannot be placed inside another object tag.
0140 Page command order is incorrect. The @ command must be the first command in the Active Server Page.
0141 Page command repeat. The @ command can only be used once in Active Server Page.