iisres.dll.mui IIS Resource DLL 63d140cdb4790a3abc20cb8964e7abfc

File name:	iisres.dll.mui
Size:	502784 byte
MD5:	63d140cdb4790a3abc20cb8964e7abfc
SHA1:	f1eccfc9d069958e9c1d7181abee10e4babe3389
SHA256:	f45cf973894fe92f4939df0a2166924efd7d08fe76e317f05773d7bd6116c711
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	English (U.S.)	English
100	007~ASP 0100~Out of memory~Unable to allocate required memory.	007~ASP 0100~Out of memory~Unable to allocate required memory.
101	007~ASP 0101~Unexpected error~The function returned |.	007~ASP 0101~Unexpected error~The function returned |.
102	007~ASP 0102~Expecting string input~The function expects a string as input.	007~ASP 0102~Expecting string input~The function expects a string as input.
103	007~ASP 0103~Expecting numeric input~The function expects a number as input.	007~ASP 0103~Expecting numeric input~The function expects a number as input.
104	007~ASP 0104~Operation not Allowed~	007~ASP 0104~Operation not Allowed~
105	007~ASP 0105~Index out of range~An array index is out of range.	007~ASP 0105~Index out of range~An array index is out of range.
106	007~ASP 0106~Type Mismatch~An unhandled data type was encountered.	007~ASP 0106~Type Mismatch~An unhandled data type was encountered.
107	007~ASP 0107~Data size too large~Size of data being sent in the request is over the allowed limit.	007~ASP 0107~Data size too large~Size of data being sent in the request is over the allowed limit.
108	An active server control or component performed an illegal OLE CoUninitialize call. Components used by Active Server Pages must not do this. Attempting to recover.	An active server control or component performed an illegal OLE CoUninitialize call. Components used by Active Server Pages must not do this. Attempting to recover.
109	True	True
110	False	False
111	006~ASP 0211~Object out of scope~A built-in ASP object has been referenced, which is no longer valid.	006~ASP 0211~Object out of scope~A built-in ASP object has been referenced, which is no longer valid.
112	006~ASP 0226~Cannot modify StaticObjects~StaticObjects collection cannot be modified at run time.	006~ASP 0226~Cannot modify StaticObjects~StaticObjects collection cannot be modified at run time.
113	No further information is available. (Error description is too long; please check for missing end delimiters, such as '%'.)	No further information is available. (Error description is too long; please check for missing end delimiters, such as '%'.)
114	The Template Persistent Cache initialization failed for Application Pool '%s' because of the following error: %s. The data may have additional error codes.	The Template Persistent Cache initialization failed for Application Pool '%s' because of the following error: %s. The data may have additional error codes.
115	ASP unhealthy because %d%% of executing requests are hung and %d%% of the request queue is full.	ASP unhealthy because %d%% of executing requests are hung and %d%% of the request queue is full.
116	ASP will not serve requests because it could not perform the first request initialization.	ASP will not serve requests because it could not perform the first request initialization.
117	ASP unhealthy due to an out of memory condition.	ASP unhealthy due to an out of memory condition.
118	006~ASP 0251~Response Buffer Limit Exceeded~Execution of the ASP page caused the Response Buffer to exceed its configured limit.	006~ASP 0251~Response Buffer Limit Exceeded~Execution of the ASP page caused the Response Buffer to exceed its configured limit.
119	The Disk Cache Directory Name is too long	The Disk Cache Directory Name is too long
120	Could not create a Disk Cache Sub-directory for the Application Pool	Could not create a Disk Cache Sub-directory for the Application Pool
121	The Disk Cache Sub-directory for the Application Pool is missing or cannot be accessed	The Disk Cache Sub-directory for the Application Pool is missing or cannot be accessed
122	The generated name for the Disk Cache Cleanup Event is too long	The generated name for the Disk Cache Cleanup Event is too long
123	The Event for the Disk Cache Directory Cleanup could not be created	The Event for the Disk Cache Directory Cleanup could not be created
201	Error: Access is Denied.	Error: Access is Denied.
202	An error occurred on the server when processing the URL. Please contact the system administrator.	An error occurred on the server when processing the URL. Please contact the system administrator.
203	The server is under heavy load, please try again later.	The server is under heavy load, please try again later.
204	VBScript	VBScript
205	Internet Information Services is not installed, Active Server Pages requires IIS installed first.	Internet Information Services is not installed, Active Server Pages requires IIS installed first.
206	%SystemDrive%\inetpub\temp\ASP Compiled Templates	%SystemDrive%\inetpub\temp\ASP Compiled Templates
300	301	301
302
303	error '	error '
304	'	'
305
309	, line	, line
311
315	401 Microsoft Active Server Pages	401 Microsoft Active Server Pages
402	IIS log failed to write entry,	IIS log failed to write entry,
403	Active Server Pages Compiler	Active Server Pages Compiler
404	Active Server Pages	Active Server Pages
405	File	File
406	Line	Line
407	Metabase key %d is out of range. Using %d as default.	Metabase key %d is out of range. Using %d as default.
408	|ASP	|ASP
409	Error while reading default settings. please do regsvr32 asp.dll.	Error while reading default settings. please do regsvr32 asp.dll.
410	ASP Script Error	ASP Script Error
413	- Application Debugging is Disabled	- Application Debugging is Disabled
501	204 No Content	204 No Content
502	403 Forbidden	403 Forbidden
503	404 Not Found	404 Not Found
504	500 Server Error	500 Server Error
505	401 Access Denied	401 Access Denied
601	*** Encrypted ASP File ***	*** Encrypted ASP File ***
1000	006~ASP 0108~Create object failed~An error occurred while creating object '%s'.	006~ASP 0108~Create object failed~An error occurred while creating object '%s'.
1004	006~ASP 0109~Member not found~	006~ASP 0109~Member not found~
1005	006~ASP 0110~Unknown name~	006~ASP 0110~Unknown name~
1006	006~ASP 0111~Unknown interface~	006~ASP 0111~Unknown interface~
1007	006~ASP 0112~Missing parameter~	006~ASP 0112~Missing parameter~
1008	006~ASP 0113~Script timed out~The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.	006~ASP 0113~Script timed out~The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
1009	006~ASP 0114~Object not free threaded~The application object accepts only free threaded objects; object '%s' is not free threaded.	006~ASP 0114~Object not free threaded~The application object accepts only free threaded objects; object '%s' is not free threaded.
1010	007~ASP 0115~Unexpected error~A trappable error (%X) occurred in an external object. The script cannot continue running.	007~ASP 0115~Unexpected error~A trappable error (%X) occurred in an external object. The script cannot continue running.
1011	An external object raised an error. No Error Description Available.	An external object raised an error. No Error Description Available.
1012	007~ASP 0240~Script Engine Exception~A ScriptEngine threw exception '%X' in '%s' from '%s'.	007~ASP 0240~Script Engine Exception~A ScriptEngine threw exception '%X' in '%s' from '%s'.
1013	007~ASP 0241~CreateObject Exception~The CreateObject of '%s' caused exception %X.	007~ASP 0241~CreateObject Exception~The CreateObject of '%s' caused exception %X.
1014	007~ASP 0242~Query OnStartPage Interface Exception~Querying Object '%s''s OnStartPage or OnEndPage methods caused exception %X.	007~ASP 0242~Query OnStartPage Interface Exception~Querying Object '%s''s OnStartPage or OnEndPage methods caused exception %X.
2000	ASP Preprocessor Error	ASP Preprocessor Error
2001	Error in script file '|' on line |:	Error in script file '|' on line |:
2002	006~ASP 0116~Missing close of script delimiter~The Script block lacks the close of script tag (%).	006~ASP 0116~Missing close of script delimiter~The Script block lacks the close of script tag (%).
2003	006~ASP 0117~Missing close of script tag~The Script block lacks the close of script tag () or close of tag symbol ().	006~ASP 0117~Missing close of script tag~The Script block lacks the close of script tag () or close of tag symbol ().
2004	006~ASP 0118~Missing close of object tag~The Object block lacks the close of object tag () or close of tag symbol ().	006~ASP 0118~Missing close of object tag~The Object block lacks the close of object tag () or close of tag symbol ().
2005	006~ASP 0119~Missing Classid or Progid attribute~The object instance '|' requires a valid Classid or Progid in the object tag.	006~ASP 0119~Missing Classid or Progid attribute~The object instance '|' requires a valid Classid or Progid in the object tag.
2006	006~ASP 0120~Invalid Runat attribute~The Runat attribute of the Script tag or Object tag can only have the value 'Server'.	006~ASP 0120~Invalid Runat attribute~The Runat attribute of the Script tag or Object tag can only have the value 'Server'.
2007	006~ASP 0121~Invalid Scope in object tag~The object instance '|' cannot have Application or Session scope. To create the object instance with Session or Application scope, place the Object tag in the Global.asa file.	006~ASP 0121~Invalid Scope in object tag~The object instance '|' cannot have Application or Session scope. To create the object instance with Session or Application scope, place the Object tag in the Global.asa file.
2008	006~ASP 0122~Invalid Scope in object tag~The object instance '|' must have Application or Session scope. This applies to all objects created in a Global.asa file.	006~ASP 0122~Invalid Scope in object tag~The object instance '|' must have Application or Session scope. This applies to all objects created in a Global.asa file.
2009	006~ASP 0123~Missing Id attribute~The required Id attribute of the Object tag is missing.	006~ASP 0123~Missing Id attribute~The required Id attribute of the Object tag is missing.
2010	006~ASP 0124~Missing Language attribute~The required Language attribute of the Script tag is missing.	006~ASP 0124~Missing Language attribute~The required Language attribute of the Script tag is missing.
2011	006~ASP 0125~Missing close of attribute~The value of the '|' attribute has no closing delimiter.	006~ASP 0125~Missing close of attribute~The value of the '|' attribute has no closing delimiter.
2012	006~ASP 0126~Include file not found~The include file '|' was not found.	006~ASP 0126~Include file not found~The include file '|' was not found.
2013	006~ASP 0127~Missing close of HTML comment~The HTML comment or server-side include lacks the close tag (--).	006~ASP 0127~Missing close of HTML comment~The HTML comment or server-side include lacks the close tag (--).
2014	006~ASP 0128~Missing File or Virtual attribute~The Include file name must be specified using either the File or Virtual attribute.	006~ASP 0128~Missing File or Virtual attribute~The Include file name must be specified using either the File or Virtual attribute.
2015	006~ASP 0129~Unknown scripting language~The scripting language '|' is not found on the server.	006~ASP 0129~Unknown scripting language~The scripting language '|' is not found on the server.
2016	006~ASP 0130~Invalid File attribute~File attribute '|' cannot start with forward slash or back slash.	006~ASP 0130~Invalid File attribute~File attribute '|' cannot start with forward slash or back slash.
2017	006~ASP 0131~Disallowed Parent Path~The Include file '|' cannot contain '..' to indicate the parent directory.	006~ASP 0131~Disallowed Parent Path~The Include file '|' cannot contain '..' to indicate the parent directory.
2018	006~ASP 0132~Compilation Error~The Active Server Page '|' could not be processed.	006~ASP 0132~Compilation Error~The Active Server Page '|' could not be processed.
2019	006~ASP 0133~Invalid ClassID attribute~The object tag has an invalid ClassID of '|'.	006~ASP 0133~Invalid ClassID attribute~The object tag has an invalid ClassID of '|'.
2020	006~ASP 0134~Invalid ProgID attribute~The object has an invalid ProgID of '|'.	006~ASP 0134~Invalid ProgID attribute~The object has an invalid ProgID of '|'.
2021	006~ASP 0135~Cyclic Include~The file '|' is included by itself (perhaps indirectly). Please check include files for other Include statements.	006~ASP 0135~Cyclic Include~The file '|' is included by itself (perhaps indirectly). Please check include files for other Include statements.
2022	006~ASP 0136~Invalid object instance name~The object instance '|' is attempting to use a reserved name. This name is used by Active Server Pages intrinsic objects.	006~ASP 0136~Invalid object instance name~The object instance '|' is attempting to use a reserved name. This name is used by Active Server Pages intrinsic objects.
2023	006~ASP 0137~Invalid Global Script~Script blocks must be one of the allowed Global.asa procedures. Script directives within are not allowed within the Global.asa file. The allowed procedure names are Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd.	006~ASP 0137~Invalid Global Script~Script blocks must be one of the allowed Global.asa procedures. Script directives within are not allowed within the Global.asa file. The allowed procedure names are Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd.
2024	006~ASP 0138~Nested Script Block~A script block cannot be placed inside another script block.	006~ASP 0138~Nested Script Block~A script block cannot be placed inside another script block.
2025	006~ASP 0139~Nested Object~An object tag cannot be placed inside another object tag.	006~ASP 0139~Nested Object~An object tag cannot be placed inside another object tag.
2026	006~ASP 0140~Page Command Out Of Order~The @ command must be the first command within the Active Server Page.	006~ASP 0140~Page Command Out Of Order~The @ command must be the first command within the Active Server Page.
2027	006~ASP 0141~Page Command Repeated~The @ command can only be used once within the Active Server Page.	006~ASP 0141~Page Command Repeated~The @ command can only be used once within the Active Server Page.
2028	006~ASP 0201~Invalid Default Script Language~The default script language specified for this application is invalid.	006~ASP 0201~Invalid Default Script Language~The default script language specified for this application is invalid.
2029	006~ASP 0202~Missing Code Page~The code page attribute is missing.	006~ASP 0202~Missing Code Page~The code page attribute is missing.
2030	006~ASP 0203~Invalid Code Page~The specified code page attribute is invalid.	006~ASP 0203~Invalid Code Page~The specified code page attribute is invalid.
2031	006~ASP 0209~Illegal value for TRANSACTION property~The TRANSACTION property can only be REQUIRED, REQUIRES_NEW, SUPPORTED or NOT_SUPPORTED.	006~ASP 0209~Illegal value for TRANSACTION property~The TRANSACTION property can only be REQUIRED, REQUIRES_NEW, SUPPORTED or NOT_SUPPORTED.
2032	006~ASP 0215~Illegal value for ENABLESESSIONSTATE property~The ENABLESESSIONSTATE property can only be TRUE or FALSE.	006~ASP 0215~Illegal value for ENABLESESSIONSTATE property~The ENABLESESSIONSTATE property can only be TRUE or FALSE.
2033	006~ASP 0217~Invalid Scope in object tag~Object scope must be Page, Session or Application.	006~ASP 0217~Invalid Scope in object tag~Object scope must be Page, Session or Application.
2034	006~ASP 0218~Missing LCID~The LCID attribute is missing.	006~ASP 0218~Missing LCID~The LCID attribute is missing.
2035	006~ASP 0219~Invalid LCID~The specified LCID is not available.	006~ASP 0219~Invalid LCID~The specified LCID is not available.
2036	006~ASP 0221~Invalid @ Command directive~The specified '|' option is unknown or invalid.	006~ASP 0221~Invalid @ Command directive~The specified '|' option is unknown or invalid.
2037	006~ASP 0222~Invalid TypeLib Specification~METADATA tag contains an invalid Type Library specification.	006~ASP 0222~Invalid TypeLib Specification~METADATA tag contains an invalid Type Library specification.
2038	006~ASP 0223~TypeLib Not Found~METADATA tag contains a Type Library specification that does not match any Registry entry.	006~ASP 0223~TypeLib Not Found~METADATA tag contains a Type Library specification that does not match any Registry entry.
2039	006~ASP 0224~Cannot load TypeLib~Cannot load Type Library specified in the METADATA tag.	006~ASP 0224~Cannot load TypeLib~Cannot load Type Library specified in the METADATA tag.
2040	006~ASP 0225~Cannot wrap TypeLibs~Cannot create a Type Library Wrapper object from the Type Libraries specified in METADATA tags.	006~ASP 0225~Cannot wrap TypeLibs~Cannot create a Type Library Wrapper object from the Type Libraries specified in METADATA tags.
2041	006~ASP 0232~Invalid Cookie Specification~METADATA tag contains an invalid cookie specification.	006~ASP 0232~Invalid Cookie Specification~METADATA tag contains an invalid cookie specification.
2042	006~ASP 0233~Cannot load cookie script source~Cannot load cookie script source file specified in the METADATA tag.	006~ASP 0233~Cannot load cookie script source~Cannot load cookie script source file specified in the METADATA tag.
2043	006~ASP 0234~Invalid include directive~Server side include directives may not be present in script blocks. Please use the SRC= attribute of the tag.	006~ASP 0234~Invalid include directive~Server side include directives may not be present in script blocks. Please use the SRC= attribute of the tag.
2044	006~ASP 0236~Invalid Cookie Specification~METADATA tag contains an invalid or missing SRC parameter.	006~ASP 0236~Invalid Cookie Specification~METADATA tag contains an invalid or missing SRC parameter.
2045	006~ASP 0237~Invalid Cookie Specification~METADATA tag contains an invalid or missing NAME parameter.	006~ASP 0237~Invalid Cookie Specification~METADATA tag contains an invalid or missing NAME parameter.
2046	006~ASP 0238~Missing attribute value~No value was specified for the '|' attribute.	006~ASP 0238~Missing attribute value~No value was specified for the '|' attribute.
2047	006~ASP 0239~Cannot process file~UNICODE ASP files are not supported.	006~ASP 0239~Cannot process file~UNICODE ASP files are not supported.
2048	006~ASP 0243~Invalid METADATA tag in Global.asa~Only METADATA TYPE="TypeLib" may be used in Global.asa.	006~ASP 0243~Invalid METADATA tag in Global.asa~Only METADATA TYPE="TypeLib" may be used in Global.asa.
2049	006~ASP 0244~Cannot Enable Session State~Session state cannot be enabled when it has been disabled in the application.	006~ASP 0244~Cannot Enable Session State~Session state cannot be enabled when it has been disabled in the application.
2050	006~ASP 0245~Mixed usage of Code Page values~The @CODEPAGE value specified differs from that of the including file's CODEPAGE or the file's saved format.	006~ASP 0245~Mixed usage of Code Page values~The @CODEPAGE value specified differs from that of the including file's CODEPAGE or the file's saved format.
3001	518~0~204 No Content~	518~0~204 No Content~
3002	518~0~404 Not Found~	518~0~404 Not Found~
3003	006~ASP 0216~MSDTC Service not running~Transactional web pages cannot be run if the MSDTC service is not running.	006~ASP 0216~MSDTC Service not running~Transactional web pages cannot be run if the MSDTC service is not running.
3004	518~0~401 Error: Access is Denied.~	518~0~401 Error: Access is Denied.~
4000	Object Not Found	Object Not Found
4001	Error, Script file '%s' was not found on the server.	Error, Script file '%s' was not found on the server.
4002	Error, Script file '%s' is empty.	Error, Script file '%s' is empty.
4003	006~ASP 0142~Thread token error~A thread token failed to open.	006~ASP 0142~Thread token error~A thread token failed to open.
4004	006~ASP 0143~Invalid Application Name~A valid application name was not found.	006~ASP 0143~Invalid Application Name~A valid application name was not found.
4005	006~ASP 0144~Initialization Error~The page level objects list failed during initialization.	006~ASP 0144~Initialization Error~The page level objects list failed during initialization.
4006	006~ASP 0145~New Application Failed~The new Application could not be added.	006~ASP 0145~New Application Failed~The new Application could not be added.
4007	006~ASP 0146~New Session Failed~The new Session could not be added	006~ASP 0146~New Session Failed~The new Session could not be added
4008	006~ASP 0150~Application Directory Error~The Application directory could not be opened.	006~ASP 0150~Application Directory Error~The Application directory could not be opened.
4009	006~ASP 0151~Change Notification Error~The change notification event could not be created.	006~ASP 0151~Change Notification Error~The change notification event could not be created.
4010	006~ASP 0152~Security Error~An error occurred while processing a user's security credentials.	006~ASP 0152~Security Error~An error occurred while processing a user's security credentials.
4011	006~ASP 0147~500 Server Error~	006~ASP 0147~500 Server Error~
4012	006~ASP 0148~Server Too Busy~	006~ASP 0148~Server Too Busy~
4013	006~ASP 0198~Server shutting down~Cannot process request	006~ASP 0198~Server shutting down~Cannot process request
4014	006~ASP 0149~Application Restarting~The request cannot be processed while the application is being restarted.	006~ASP 0149~Application Restarting~The request cannot be processed while the application is being restarted.
4015	006~ASP 0220~Requests for GLOBAL.ASA Not Allowed~Requests with the URL pointing to GLOBAL.ASA are not allowed.	006~ASP 0220~Requests for GLOBAL.ASA Not Allowed~Requests with the URL pointing to GLOBAL.ASA are not allowed.
4016	006~ASP 0246~Too many concurrent users. Please try again later.~	006~ASP 0246~Too many concurrent users. Please try again later.~
4017	006~ASP 0250~Invalid Default Code Page~The default code page specified for this application is invalid.	006~ASP 0250~Invalid Default Code Page~The default code page specified for this application is invalid.
5000	006~ASP 0153~Thread Error~A new thread request failed.	006~ASP 0153~Thread Error~A new thread request failed.
6000	Response object	Response object
6001	006~ASP 0154~Write HTTP Header Error~The HTTP headers could not be written to the client browser.	006~ASP 0154~Write HTTP Header Error~The HTTP headers could not be written to the client browser.
6002	006~ASP 0155~Write Page Content Error~The page content could not be written to the client browser.	006~ASP 0155~Write Page Content Error~The page content could not be written to the client browser.
6003	006~ASP 0156~Header Error~The HTTP headers are already written to the client browser. Any HTTP header modifications must be made before writing page content.	006~ASP 0156~Header Error~The HTTP headers are already written to the client browser. Any HTTP header modifications must be made before writing page content.
6004	006~ASP 0157~Buffering On~Buffering cannot be turned off once it is already turned on.	006~ASP 0157~Buffering On~Buffering cannot be turned off once it is already turned on.
6005	006~ASP 0158~Missing URL~A URL is required.	006~ASP 0158~Missing URL~A URL is required.
6006	006~ASP 0159~Buffering Off~Buffering must be on.	006~ASP 0159~Buffering Off~Buffering must be on.
6007	006~ASP 0160~Logging Failure~Failure to write entry to log.	006~ASP 0160~Logging Failure~Failure to write entry to log.
6008	Object moved Object MovedThis object may be found	Object moved Object MovedThis object may be found
6009	"here.	"here.
6010	006~ASP 0161~Data Type Error~The conversion of a Variant to a String variable failed.	006~ASP 0161~Data Type Error~The conversion of a Variant to a String variable failed.
6011	006~ASP 0162~Cannot Modify Cookie~The cookie 'ASPSessionID' cannot be modified. It is a reserved cookie name.	006~ASP 0162~Cannot Modify Cookie~The cookie 'ASPSessionID' cannot be modified. It is a reserved cookie name.
6012	006~ASP 0163~Invalid Comma Use~Commas cannot be used within a log entry. Please select another delimiter.	006~ASP 0163~Invalid Comma Use~Commas cannot be used within a log entry. Please select another delimiter.
6013	006~ASP 0212~Cannot Clear Buffer~Response.Clear is not allowed after a Response.Flush while Client Debugging is Enabled.	006~ASP 0212~Cannot Clear Buffer~Response.Clear is not allowed after a Response.Flush while Client Debugging is Enabled.
6014	006~ASP 0210~Method not implemented~This method has not yet been implemented.	006~ASP 0210~Method not implemented~This method has not yet been implemented.
6100	Session object	Session object
6101	SessionID	SessionID
6102	006~ASP 0164~Invalid TimeOut Value~An invalid TimeOut value was specified.	006~ASP 0164~Invalid TimeOut Value~An invalid TimeOut value was specified.
6103	006~ASP 0165~SessionID Error~A SessionID string cannot be created.	006~ASP 0165~SessionID Error~A SessionID string cannot be created.
6104	006~ASP 0166~Uninitialized Object~An attempt was made to access an uninitialized object.	006~ASP 0166~Uninitialized Object~An attempt was made to access an uninitialized object.
6105	006~ASP 0167~Session Initialization Error~An error occurred while initializing the Session object.	006~ASP 0167~Session Initialization Error~An error occurred while initializing the Session object.
6107	006~ASP 0168~Disallowed object use~An intrinsic object cannot be stored within the Session object.	006~ASP 0168~Disallowed object use~An intrinsic object cannot be stored within the Session object.
6108	006~ASP 0169~Missing object information~An object with missing information cannot be stored in the Session object. The threading model information for an object is required.	006~ASP 0169~Missing object information~An object with missing information cannot be stored in the Session object. The threading model information for an object is required.
6109	006~ASP 0170~Delete Session Error~The Session did not delete properly.	006~ASP 0170~Delete Session Error~The Session did not delete properly.
6110	006~ASP 0188~Disallowed object use~Cannot add objects created using object tags to the session intrinsic.	006~ASP 0188~Disallowed object use~Cannot add objects created using object tags to the session intrinsic.
6111	006~ASP 0199~Disallowed object use~Cannot add JScript objects to the session.	006~ASP 0199~Disallowed object use~Cannot add JScript objects to the session.
6112	006~ASP 0204~Invalid CodePage Value~An invalid CodePage value was specified.	006~ASP 0204~Invalid CodePage Value~An invalid CodePage value was specified.
6200	Server object	Server object
6201	Server.MapPath()	Server.MapPath()
6202	006~ASP 0171~Missing Path~The Path parameter must be specified for the MapPath method.	006~ASP 0171~Missing Path~The Path parameter must be specified for the MapPath method.
6203	006~ASP 0172~Invalid Path~The Path parameter for the MapPath method must be a virtual path. A physical path was used.	006~ASP 0172~Invalid Path~The Path parameter for the MapPath method must be a virtual path. A physical path was used.
6204	006~ASP 0173~Invalid Path Character~An invalid character was specified in the Path parameter for the MapPath method.	006~ASP 0173~Invalid Path Character~An invalid character was specified in the Path parameter for the MapPath method.
6205	006~ASP 0174~Invalid Path Character(s)~An invalid '/' or '\' was found in the Path parameter for the MapPath method.	006~ASP 0174~Invalid Path Character(s)~An invalid '/' or '\' was found in the Path parameter for the MapPath method.
6206	006~ASP 0175~Disallowed Path Characters~The '..' characters are not allowed in the Path parameter for the MapPath method.	006~ASP 0175~Disallowed Path Characters~The '..' characters are not allowed in the Path parameter for the MapPath method.
6207	006~ASP 0176~Path Not Found~The Path parameter for the MapPath method did not correspond to a known path.	006~ASP 0176~Path Not Found~The Path parameter for the MapPath method did not correspond to a known path.
6208	006~ASP 0195~Invalid Server Method Call~This method of the Server object cannot be called during Session_OnEnd and Application_OnEnd.	006~ASP 0195~Invalid Server Method Call~This method of the Server object cannot be called during Session_OnEnd and Application_OnEnd.
6209	006~ASP 0177~Server.CreateObject Failed~%s	006~ASP 0177~Server.CreateObject Failed~%s
6210	006~ASP 0178~Server.CreateObject Access Error~The call to Server.CreateObject failed while checking permissions. Access is denied to this object.	006~ASP 0178~Server.CreateObject Access Error~The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
6211	006~ASP 0196~Cannot launch out of process component~Only InProc server components should be used. If you want to use LocalServer components, you must set the AspAllowOutOfProcComponents metabase setting. Please consult the help file for important considerations.	006~ASP 0196~Cannot launch out of process component~Only InProc server components should be used. If you want to use LocalServer components, you must set the AspAllowOutOfProcComponents metabase setting. Please consult the help file for important considerations.
6213	006~ASP 0214~Invalid Path parameter~The Path parameter excedes the maximum length allowed.	006~ASP 0214~Invalid Path parameter~The Path parameter excedes the maximum length allowed.
6214	006~ASP 0227~Server.Execute Failed~The call to Server.Execute failed	006~ASP 0227~Server.Execute Failed~The call to Server.Execute failed
6215	006~ASP 0228~Server.Execute Error~The call to Server.Execute failed while loading the page.	006~ASP 0228~Server.Execute Error~The call to Server.Execute failed while loading the page.
6216	006~ASP 0231~Server.Execute Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.	006~ASP 0231~Server.Execute Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.
6217	006~ASP 0229~Server.Transfer Failed~The call to Server.Transfer failed	006~ASP 0229~Server.Transfer Failed~The call to Server.Transfer failed
6218	006~ASP 0230~Server.Transfer Error~The call to Server.Transfer failed while loading the page.	006~ASP 0230~Server.Transfer Error~The call to Server.Transfer failed while loading the page.
6219	006~ASP 0235~Server.Transfer Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.	006~ASP 0235~Server.Transfer Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.
6300	Application object	Application object
6301	006~ASP 0179~Application Initialization Error~An error occurred while initializing the Application object.	006~ASP 0179~Application Initialization Error~An error occurred while initializing the Application object.
6302	006~ASP 0180~Disallowed object use~An intrinsic object cannot be stored within the Application object.	006~ASP 0180~Disallowed object use~An intrinsic object cannot be stored within the Application object.
6303	006~ASP 0181~Invalid threading model~An object using the apartment threading model cannot be stored within the Application object.	006~ASP 0181~Invalid threading model~An object using the apartment threading model cannot be stored within the Application object.
6304	006~ASP 0182~Missing object information~An object with missing information cannot be stored in the Application object. The threading model information for the object is required.	006~ASP 0182~Missing object information~An object with missing information cannot be stored in the Application object. The threading model information for the object is required.
6305	006~ASP 0189~Disallowed object use~Cannot add objects created using object tags to the application intrinsic.	006~ASP 0189~Disallowed object use~Cannot add objects created using object tags to the application intrinsic.
6307	006~ASP 0187~Object addition conflict~Could not add object to application. Application was locked down by another request for adding an object.	006~ASP 0187~Object addition conflict~Could not add object to application. Application was locked down by another request for adding an object.
6308	006~ASP 0197~Disallowed object use~Cannot add object with apartment model behavior to the application intrinsic object.	006~ASP 0197~Disallowed object use~Cannot add object with apartment model behavior to the application intrinsic object.
6309	006~ASP 0205~Change Notification~Failed to create event for change notification.	006~ASP 0205~Change Notification~Failed to create event for change notification.
6400	Cookies object	Cookies object
6401	006~ASP 0183~Empty Cookie Key~A cookie with an empty key cannot be stored.	006~ASP 0183~Empty Cookie Key~A cookie with an empty key cannot be stored.
6402	006~ASP 0184~Missing Cookie Name~A name must be specified for a cookie.	006~ASP 0184~Missing Cookie Name~A name must be specified for a cookie.
6403	006~ASP 0200~Out of Range 'Expires' attribute~The date and time given for 'Expires' precedes Jan 1, 1980 or excedes Jan 19, 2038, 3:14:07 GMT.	006~ASP 0200~Out of Range 'Expires' attribute~The date and time given for 'Expires' precedes Jan 1, 1980 or excedes Jan 19, 2038, 3:14:07 GMT.
6500	Request object	Request object
6501	006~ASP 0206~Cannot call BinaryRead~Cannot call BinaryRead after using Request.Form collection.	006~ASP 0206~Cannot call BinaryRead~Cannot call BinaryRead after using Request.Form collection.
6502	006~ASP 0207~Cannot use Request.Form~Cannot use Request.Form collection after calling BinaryRead.	006~ASP 0207~Cannot use Request.Form~Cannot use Request.Form collection after calling BinaryRead.
6503	006~ASP 0208~Cannot use generic Request collection~Cannot use the generic Request collection after calling BinaryRead.	006~ASP 0208~Cannot use generic Request collection~Cannot use the generic Request collection after calling BinaryRead.
6504	006~ASP 0249~Cannot use IStream on Request~Cannot use IStream on Request object after using Request.Form collection or Request.BinaryRead.	006~ASP 0249~Cannot use IStream on Request~Cannot use IStream on Request object after using Request.Form collection or Request.BinaryRead.
6505	006~ASP 0247~Bad Argument to BinaryRead~The argument to BinaryRead must be non-negative.	006~ASP 0247~Bad Argument to BinaryRead~The argument to BinaryRead must be non-negative.
6701	007~ASP 0190~Unexpected error~A trappable error occurred while releasing an external object.	007~ASP 0190~Unexpected error~A trappable error occurred while releasing an external object.
6702	007~ASP 0191~Unexpected error~A trappable error occurred in the OnStartPage method of an external object.	007~ASP 0191~Unexpected error~A trappable error occurred in the OnStartPage method of an external object.
6703	007~ASP 0192~Unexpected error~A trappable error occurred in the OnEndPage method of an external object.	007~ASP 0192~Unexpected error~A trappable error occurred in the OnEndPage method of an external object.
6704	007~ASP 0193~OnStartPage Failed~An error occurred in the OnStartPage method of an external object.	007~ASP 0193~OnStartPage Failed~An error occurred in the OnStartPage method of an external object.
6705	007~ASP 0194~OnEndPage Failed~An error occurred in the OnEndPage method of an external object.	007~ASP 0194~OnEndPage Failed~An error occurred in the OnEndPage method of an external object.
6800	Certificate object	Certificate object
6801	006~ASP 0186~Error parsing certificate	006~ASP 0186~Error parsing certificate
6850	ObjectContext object	ObjectContext object
6851	006~ASP 0248~Script isn't transacted~This ASP file must be transacted in order to use the ObjectContext object.	006~ASP 0248~Script isn't transacted~This ASP file must be transacted in order to use the ObjectContext object.
9000	006~ASP 0185~Missing Default Property~A default property was not found for the object.	006~ASP 0185~Missing Default Property~A default property was not found for the object.
12000	[To Parent Directory]	[To Parent Directory]
12001	dir	dir
12100	Document Moved Object MovedThis document may be found here	Document Moved Object MovedThis document may be found here
12101	Site Access Denied Access DeniedYour site has been denied access to this server.	Site Access Denied Access DeniedYour site has been denied access to this server.
12122	Too Many UsersThere are too many connected users. Please try again later.	Too Many UsersThere are too many connected users. Please try again later.
12123	All of the available licenses are in use. Talk to the system administrator to increase the number of available licenses on this server.	All of the available licenses are in use. Talk to the system administrator to increase the number of available licenses on this server.
12124	This Virtual Directory does not allow objects to be read.	This Virtual Directory does not allow objects to be read.
12125	This Virtual Directory does not allow objects to be executed.	This Virtual Directory does not allow objects to be executed.
12126	This Virtual Directory requires a browser that supports the configured encryption options.	This Virtual Directory requires a browser that supports the configured encryption options.
12127	This Virtual Directory does not allow objects to be written.	This Virtual Directory does not allow objects to be written.
12130	Access to this server is forbidden from your client	Access to this server is forbidden from your client
12132	The server configuration is invalid	The server configuration is invalid
12134	Access denied using this Client Certificate	Access denied using this Client Certificate
12135	Error: Unable to read footer file.	Error: Unable to read footer file.
12138	Unsupported Content-Type The Content-Type of the request is not supported by this server.	Unsupported Content-Type The Content-Type of the request is not supported by this server.
12139	No license available to access this computer	No license available to access this computer
12141	The specified method is not supported	The specified method is not supported
12142	The client certificate has been revoked	The client certificate has been revoked
12143	The client certificate is untrusted or corrupt.	The client certificate is untrusted or corrupt.
12144	The client certificate has expired or is not yet valid.	The client certificate has expired or is not yet valid.
12145	This Virtual Directory does not allow contents to be listed.	This Virtual Directory does not allow contents to be listed.
12146	Server Application Error Server Application ErrorThe server has reached the maximum recovery limit for the application during the processing of your request. Please contact the server administrator for assistance.	Server Application Error Server Application ErrorThe server has reached the maximum recovery limit for the application during the processing of your request. Please contact the server administrator for assistance.
12147	Server Application Error Server Application ErrorThe server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.	Server Application Error Server Application ErrorThe server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.
12148	The specified request cannot be executed from current Application Pool	The specified request cannot be executed from current Application Pool
12149	The configured user for the current Application Pool does not have enough privileges to run CGIs	The configured user for the current Application Pool does not have enough privileges to run CGIs
12150	Authentication credentials received by the server are bad or incomplete	Authentication credentials received by the server are bad or incomplete
12151	This Virtual Directory does not allow the specified authentication method	This Virtual Directory does not allow the specified authentication method
12152	The ACL on this resource denied access to the authenticated user	The ACL on this resource denied access to the authenticated user
12153	An ISAPI filter serving this request denied it	An ISAPI filter serving this request denied it
12154	The application serving this request denied it	The application serving this request denied it
12155	The ISAPI/CGI configured for this request is not allowed to execute	The ISAPI/CGI configured for this request is not allowed to execute
12156	The file-extension for this static request is not present in the mime-map list	The file-extension for this static request is not present in the mime-map list
12157	No handler could be found for this request	No handler could be found for this request
12158	The specified URL sequence is denied	The specified URL sequence is denied
12159	The specified verb is denied	The specified verb is denied
12160	The specified file extension is denied	The specified file extension is denied
12161	The namespace for this URL is hidden by configuration	The namespace for this URL is hidden by configuration
12162	This file has a hidden attribute which prevents it from being served	This file has a hidden attribute which prevents it from being served
12163	One of the request header is longer than the specified limit	One of the request header is longer than the specified limit
12164	This URL is denied because it is susceptible to double-escaping attacks	This URL is denied because it is susceptible to double-escaping attacks
12165	This URL is denied because it has high-bit characters	This URL is denied because it has high-bit characters
12166	The Content-Length is longer than allowed by configuration	The Content-Length is longer than allowed by configuration
12167	The URL is longer than allowed by configuration	The URL is longer than allowed by configuration
12168	The QueryString is longer than allowed by configuration	The QueryString is longer than allowed by configuration
12169	IIS 10.0 Detailed Error - %u.%u - %S %s HTTP Error %u.%u - %S %s %s Detailed Error Information: Module   %s Notification   %s Handler   %s Error Code   0x%08x %s Requested URL   %s Physical Path   %s Logon Method   %s Logon User   %s %s %s More Information: %s View more information » %s	IIS 10.0 Detailed Error - %u.%u - %S %s HTTP Error %u.%u - %S %s %s Detailed Error Information: Module   %s Notification   %s Handler   %s Error Code   0x%08x %s Requested URL   %s Physical Path   %s Logon Method   %s Logon User   %s %s %s More Information: %s View more information » %s
12170	Config Error   %s Config File   %s	Config Error   %s Config File   %s
12171	%s	%s
12172	Anonymous	Anonymous
12173	Not yet determined	Not yet determined
12174	Microsoft Knowledge Base Articles: %s	Microsoft Knowledge Base Articles: %s
12175	Most likely causes: %s Things you can try: %s	Most likely causes: %s Things you can try: %s
12176	Request Tracing Directory   %s	Request Tracing Directory   %s
12177	Server Error	Server Error
12178	Server Error in Application "%s"	Server Error in Application "%s"
12179	Unknown	Unknown
12180
12181	Config Source: %s	Config Source: %s
12182	Unavailable (Config Isolation)	Unavailable (Config Isolation)
12183	Request started: "%s" %s	Request started: "%s" %s
12184	Request ended: %s with HTTP status %d.%d	Request ended: %s with HTTP status %d.%d
12185	Child request started: "%s"	Child request started: "%s"
12186	Child request ended: "%s" for site "%s" application "%s"	Child request ended: "%s" for site "%s" application "%s"
12187	Successfully registered URL "%s" for site "%s" application "%s"	Successfully registered URL "%s" for site "%s" application "%s"
12188	Failed to register URL "%s" for site "%s"	Failed to register URL "%s" for site "%s"
12196	The custom error module does not recognize this error.	The custom error module does not recognize this error.
12197	A module set an infrequently used status code.	A module set an infrequently used status code.
12198	Investigate why the module set the status code.	Investigate why the module set the status code.
12199	Any module can call SetStatus with the status, substatus or HRESULT. The custom error module only displays status specific error messages for well known errors.	Any module can call SetStatus with the status, substatus or HRESULT. The custom error module only displays status specific error messages for well known errors.
12200	12202 You do not have permission to view this directory or page.	12202 You do not have permission to view this directory or page.
12203	The authenticated user does not have access to a resource needed to process the request.	The authenticated user does not have access to a resource needed to process the request.
12204	Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12205	This is the generic Access Denied error returned by IIS. Typically, there is a substatus code associated with this error that describes why the server denied the request. Check the IIS Log file to determine whether a substatus code is associated with this failure.	This is the generic Access Denied error returned by IIS. Typically, there is a substatus code associated with this error that describes why the server denied the request. Check the IIS Log file to determine whether a substatus code is associated with this failure.
12206	907273	907273
12208	You do not have permission to view this directory or page using the credentials that you supplied.	You do not have permission to view this directory or page using the credentials that you supplied.
12209	The username supplied to IIS is invalid. The password supplied to IIS was not typed correctly. Incorrect credentials were cached by the browser. IIS could not verify the identity of the username and password provided. The resource is configured for Anonymous authentication, but the configured anonymous account either has an invalid password or was disabled. The server is configured to deny login privileges to the authenticating user or the group in which the user is a member. Invalid Kerberos configuration may be the cause if all of the following are true: Integrated authentication was used. the application pool identity is a custom account. the server is a member of a domain.	The username supplied to IIS is invalid. The password supplied to IIS was not typed correctly. Incorrect credentials were cached by the browser. IIS could not verify the identity of the username and password provided. The resource is configured for Anonymous authentication, but the configured anonymous account either has an invalid password or was disabled. The server is configured to deny login privileges to the authenticating user or the group in which the user is a member. Invalid Kerberos configuration may be the cause if all of the following are true: Integrated authentication was used. the application pool identity is a custom account. the server is a member of a domain.
12210	Verify that the username and password are correct, and are not cached by the browser. Use a different username and password. If you are using a custom anonymous account, verify that the password has not expired. Verify that the authenticating user or the user's group, has not been denied login access to the server. Verify that the account was not locked out due to numerous failed login attempts. If you are using authentication and the server is a member of a domain, verify that you have configured the application pool identity using the utility SETSPN.exe, or changed the configuration so that NTLM is the favored authentication type. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify that the username and password are correct, and are not cached by the browser. Use a different username and password. If you are using a custom anonymous account, verify that the password has not expired. Verify that the authenticating user or the user's group, has not been denied login access to the server. Verify that the account was not locked out due to numerous failed login attempts. If you are using authentication and the server is a member of a domain, verify that you have configured the application pool identity using the utility SETSPN.exe, or changed the configuration so that NTLM is the favored authentication type. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12211	This error occurs when either the username or password supplied to IIS is invalid, or when IIS cannot use the username and password to authenticate the user.	This error occurs when either the username or password supplied to IIS is invalid, or when IIS cannot use the username and password to authenticate the user.
12212	907273871179896861	907273871179896861
12214	You are not authorized to view this page due to invalid authentication headers.	You are not authorized to view this page due to invalid authentication headers.
12215	No authentication protocol (including anonymous) is selected in IIS. Only integrated authentication is enabled, and a client browser was used that does not support integrated authentication. Integrated authentication is enabled and the request was sent through a proxy that changed the authentication headers before they reach the Web server. The Web server is not configured for anonymous access and a required authorization header was not received. The "configuration/system.webServer/authorization" configuration section may be explicitly denying the user access.	No authentication protocol (including anonymous) is selected in IIS. Only integrated authentication is enabled, and a client browser was used that does not support integrated authentication. Integrated authentication is enabled and the request was sent through a proxy that changed the authentication headers before they reach the Web server. The Web server is not configured for anonymous access and a required authorization header was not received. The "configuration/system.webServer/authorization" configuration section may be explicitly denying the user access.
12216	Verify the authentication setting for the resource and then try requesting the resource using that authentication method. Verify that the client browser supports Integrated authentication. Verify that the request is not going through a proxy when Integrated authentication is used. Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify the authentication setting for the resource and then try requesting the resource using that authentication method. Verify that the client browser supports Integrated authentication. Verify that the request is not going through a proxy when Integrated authentication is used. Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12217	This error occurs when the WWW-Authenticate header sent to the Web server is not supported by the server configuration. Check the authentication method for the resource, and verify which authentication method the client used. The error occurs when the authentication methods are different. To determine which type of authentication the client is using, check the authentication settings for the client.	This error occurs when the WWW-Authenticate header sent to the Web server is not supported by the server configuration. Check the authentication method for the resource, and verify which authentication method the client used. The error occurs when the authentication methods are different. To determine which type of authentication the client is using, check the authentication settings for the client.
12218	907273253667	907273253667
12220	You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.	You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.
12221	The user authenticated by the Web server does not have permission to open the file on the file system. If the resource is located on a Universal Naming Convention (UNC) share, the authenticated user may not have sufficient share and NTFS permissions, or the permissions on the share may not match the permissions on the physical path. The file is encrypted.	The user authenticated by the Web server does not have permission to open the file on the file system. If the resource is located on a Universal Naming Convention (UNC) share, the authenticated user may not have sufficient share and NTFS permissions, or the permissions on the share may not match the permissions on the physical path. The file is encrypted.
12222	Open File Explorer and check the ACLs for the file that is being requested. Make sure that the user accessing the Web site is not being explicitly denied access, and that they do have permission to open the file. Open File Explorer and check the ACLs for the share and the physical path. Ensure that both ACLs allow the user to access the resource. Open File Explorer and check the encryption properties for the file that is being requested. (This setting is located in the Advanced attribute properties dialog.) Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Open File Explorer and check the ACLs for the file that is being requested. Make sure that the user accessing the Web site is not being explicitly denied access, and that they do have permission to open the file. Open File Explorer and check the ACLs for the share and the physical path. Ensure that both ACLs allow the user to access the resource. Open File Explorer and check the encryption properties for the file that is being requested. (This setting is located in the Advanced attribute properties dialog.) Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12223	The user trying to access the page was successfully logged on, but the user does not have permission to access the resource. This means the access control list (ACL) for the resource either does not include the user or explicitly denies the user. Check the ACL for the resource and add the user to the ACL. If the content is located on a share, ensure both NTFS and share permissions allow the user access. It is also possible that the user is part of a group that is denied access.	The user trying to access the page was successfully logged on, but the user does not have permission to access the resource. This means the access control list (ACL) for the resource either does not include the user or explicitly denies the user. Check the ACL for the resource and add the user to the ACL. If the content is located on a share, ensure both NTFS and share permissions allow the user access. It is also possible that the user is part of a group that is denied access.
12224	907273332142	907273332142
12226	You might not have permission to view this directory or page using the credentials that you supplied. The Web server has a filter installed to verify users connecting to the server and it failed to authenticate your credentials.	You might not have permission to view this directory or page using the credentials that you supplied. The Web server has a filter installed to verify users connecting to the server and it failed to authenticate your credentials.
12227	An ISAPI filter running on the Web server has failed the authentication process or denied the request.	An ISAPI filter running on the Web server has failed the authentication process or denied the request.
12228	To test this error, remove any filters that are installed for the Web site where access was requested. If the error does not occur after the filters are removed, one of the filters was returning the error. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	To test this error, remove any filters that are installed for the Web site where access was requested. If the error does not occur after the filters are removed, one of the filters was returning the error. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12229	This error occurs when an ISAPI filter running on the Web server fails the authentication process. IIS does not ship with any ISAPI filters that would return this error, so the error is caused by a third-party filter installed on the server.	This error occurs when an ISAPI filter running on the Web server fails the authentication process. IIS does not ship with any ISAPI filters that would return this error, so the error is caused by a third-party filter installed on the server.
12232	The URL you tried to reach has an ISAPI or CGI application installed that verifies user credentials before proceeding. This application cannot verify your credentials.	The URL you tried to reach has an ISAPI or CGI application installed that verifies user credentials before proceeding. This application cannot verify your credentials.
12233	A custom ISAPI extension, CGI application, ASP page, or handler failed the request with an Access Denied error.	A custom ISAPI extension, CGI application, ASP page, or handler failed the request with an Access Denied error.
12234	Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12235	The URL you tried to reach is an ASP page or is mapped to an ISAPI extension, CGI application, or custom handler. The ISAPI extension, CGI application, ASP page, or handler refused the request by returning an "Access Denied" error.	The URL you tried to reach is an ASP page or is mapped to an ISAPI extension, CGI application, or custom handler. The ISAPI extension, CGI application, ASP page, or handler refused the request by returning an "Access Denied" error.
12238	You do not have permission to view this directory or page.	You do not have permission to view this directory or page.
12239	This is a generic 403 error and means the authenticated user is not authorized to view the page.	This is a generic 403 error and means the authenticated user is not authorized to view the page.
12241	This generic 403 error means that the authenticated user is not authorized to use the requested resource. A substatus code in the IIS log files should indicate the reason for the 403 error. If a substatus code does not exist, use the steps above to gather more information about the source of the error.	This generic 403 error means that the authenticated user is not authorized to use the requested resource. A substatus code in the IIS log files should indicate the reason for the 403 error. If a substatus code does not exist, use the steps above to gather more information about the source of the error.
12242	12244 You have attempted to run a CGI, ISAPI, or other executable program from a directory that does not allow executables to run.	12244 You have attempted to run a CGI, ISAPI, or other executable program from a directory that does not allow executables to run.
12245	The "Scripts" or "Scripts and Executables" flag is not configured in Rights and Permissions at the server, site, application, or page level. The configuration/system.webServer/handlers@accessPolicy attribute does not have Script or Execute configured. Execute access is denied when you try to run a CGI file or other executable. Script access is denied when you try to access an ASP, ASP.NET or other dynamic scripting file. The script mapping for the file you are trying to run is not configured to recognize the HTTP verb you are using (such as GET or POST). The HTTP verb for the script mapping is case sensitive, and use upper case. The HTTP verb "POST" is correct, while "post" is incorrect and execution is denied.	The "Scripts" or "Scripts and Executables" flag is not configured in Rights and Permissions at the server, site, application, or page level. The configuration/system.webServer/handlers@accessPolicy attribute does not have Script or Execute configured. Execute access is denied when you try to run a CGI file or other executable. Script access is denied when you try to access an ASP, ASP.NET or other dynamic scripting file. The script mapping for the file you are trying to run is not configured to recognize the HTTP verb you are using (such as GET or POST). The HTTP verb for the script mapping is case sensitive, and use upper case. The HTTP verb "POST" is correct, while "post" is incorrect and execution is denied.
12246	Enable scripts to run for the requested resource. Open IIS Manager and navigate to the level you want to manage. On the Features page, double-click the Handler Mappings feature. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions. In the Edit Handler Mappings dialog box, select Scripts to enable handlers that require script rights. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Enable scripts to run for the requested resource. Open IIS Manager and navigate to the level you want to manage. On the Features page, double-click the Handler Mappings feature. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions. In the Edit Handler Mappings dialog box, select Scripts to enable handlers that require script rights. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12247	This error occurs when the Execute Rights setting for the requested resource does not allow scripts to run. Set the Execute Rights property for the resource at the server, site, application, and file level. To resolve this problem, verify the Execute Rights setting at each of these levels, and set the appropriate Execute Right at the desired level.	This error occurs when the Execute Rights setting for the requested resource does not allow scripts to run. Set the Execute Rights property for the resource at the server, site, application, and file level. To resolve this problem, verify the Execute Rights setting at each of these levels, and set the appropriate Execute Right at the desired level.
12248	318380	318380
12250	You have attempted to view a resource that does not have Read access.	You have attempted to view a resource that does not have Read access.
12251	The Rights and Permissions setting for the requested resource does not allow Read access. The default document specified for the Web site does not exist. For example, you specified Default.htm but this file does not exist. Directory browsing is not enabled. The configuration/system.webServer/handlers@accessPolicy attribute does not have "Read" configured for the requested resource at the server, site, application, or page level.	The Rights and Permissions setting for the requested resource does not allow Read access. The default document specified for the Web site does not exist. For example, you specified Default.htm but this file does not exist. Directory browsing is not enabled. The configuration/system.webServer/handlers@accessPolicy attribute does not have "Read" configured for the requested resource at the server, site, application, or page level.
12252	Enable Read access for the requested resource. Open IIS Manager and navigate to the level you want to manage. On the Features page, double-click the Handler Mappings feature. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions. In the Edit Handler Mappings dialog box, select Read to enable handlers that require read access. Verify the default document does exist and matches what is specified in the Web site properties. Verify that directory browsing is enabled. Directory browsing needs to be enabled if you want a Web site to show a directory listing (all files in the folder you are accessing). Verify the configuration/system.webServer/handlers/accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Read" is listed as one of the flags. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Enable Read access for the requested resource. Open IIS Manager and navigate to the level you want to manage. On the Features page, double-click the Handler Mappings feature. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions. In the Edit Handler Mappings dialog box, select Read to enable handlers that require read access. Verify the default document does exist and matches what is specified in the Web site properties. Verify that directory browsing is enabled. Directory browsing needs to be enabled if you want a Web site to show a directory listing (all files in the folder you are accessing). Verify the configuration/system.webServer/handlers/accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Read" is listed as one of the flags. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12253	This problem occurs when the access permission for the requested resource does not have Read access enabled. Change this setting at the server, site, application, or file level. To resolve this problem, verify the Read access permissions setting at each of these levels, and set the appropriate access permissions at the desired level.	This problem occurs when the access permission for the requested resource does not have Read access enabled. Change this setting at the server, site, application, or file level. To resolve this problem, verify the Read access permissions setting at each of these levels, and set the appropriate access permissions at the desired level.
12254	247677838790	247677838790
12256	You have attempted to write to a folder that does not have Write access.	You have attempted to write to a folder that does not have Write access.
12257	The Rights and Permissions setting for the requested resource does not allow Write access. The configuration/system.webServer/handlers@accessPolicy attribute does not have "Write" configured for the requested resource at the server, site, application, or page level.	The Rights and Permissions setting for the requested resource does not allow Write access. The configuration/system.webServer/handlers@accessPolicy attribute does not have "Write" configured for the requested resource at the server, site, application, or page level.
12258	Enable Write access for the requested resource. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Write" is listed as one of the flags. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Enable Write access for the requested resource. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Write" is listed as one of the flags. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12259	This problem occurs when the access permissions setting for the requested resource does not have Write access enabled. Change this setting at the server, site, application, or file level. To resolve this problem, verify the Write access permissions setting at each of these levels, and set the appropriate access permissions at the desired level.	This problem occurs when the access permissions setting for the requested resource does not have Write access enabled. Change this setting at the server, site, application, or file level. To resolve this problem, verify the Write access permissions setting at each of these levels, and set the appropriate access permissions at the desired level.
12260	248072	248072
12262	The page you are trying to access is secured with Secure Sockets Layer (SSL).	The page you are trying to access is secured with Secure Sockets Layer (SSL).
12263	Secure Sockets Layer (SSL) is enabled for the URL requested. The page request was made over HTTP, but the server requires the request from a secure channel that uses HTTPS.	Secure Sockets Layer (SSL) is enabled for the URL requested. The page request was made over HTTP, but the server requires the request from a secure channel that uses HTTPS.
12264	Browse to the URL over a secure channel by using the "https:" prefix instead of "http:". If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting. Verify the SSL Settings in IIS Manager by connecting to the server, site, application or page and opening the SSL Settings feature. Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.	Browse to the URL over a secure channel by using the "https:" prefix instead of "http:". If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting. Verify the SSL Settings in IIS Manager by connecting to the server, site, application or page and opening the SSL Settings feature. Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.
12265	This error means that the requested Web page requires SSL. Try to browse to the same URL, but use "https:" instead of "http:".	This error means that the requested Web page requires SSL. Try to browse to the same URL, but use "https:" instead of "http:".
12266	12268 The resource you are trying to access is secured with a 128-bit version of Secure Sockets Layer (SSL). To view this resource, you need a Web browser that supports this version of SSL.	12268 The resource you are trying to access is secured with a 128-bit version of Secure Sockets Layer (SSL). To view this resource, you need a Web browser that supports this version of SSL.
12269	The Web server requires a 128-bit SSL connection for the requested resource, but the browser is using something less than 128-bit encryption.	The Web server requires a 128-bit SSL connection for the requested resource, but the browser is using something less than 128-bit encryption.
12270	Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions. Verify the SSL Settings in IIS Manager by connecting to the server, site, application, or page and opening the SSL Settings feature. Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.	Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions. Verify the SSL Settings in IIS Manager by connecting to the server, site, application, or page and opening the SSL Settings feature. Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.
12271	This error means that the Web server requires 128-bit SSL encryption, but the browser specified something less than 128-bit SSL encryption during the request. Make sure the browser both supports 128-bit encryption and is configured to use it.	This error means that the Web server requires 128-bit SSL encryption, but the browser specified something less than 128-bit SSL encryption during the request. Make sure the browser both supports 128-bit encryption and is configured to use it.
12272	12274 The IP address from which you are browsing is not permitted to access the requested Web site.	12274 The IP address from which you are browsing is not permitted to access the requested Web site.
12275	The server, site, application, or page requested has explicitly denied the IP address of the client computer.	The server, site, application, or page requested has explicitly denied the IP address of the client computer.
12276	Verify the IP and domain restrictions in IIS Manager. Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.	Verify the IP and domain restrictions in IIS Manager. Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.
12277	Set IP restrictions at the server, site, application, or file level. Verify or change the IP restrictions at the site level.	Set IP restrictions at the server, site, application, or file level. Verify or change the IP restrictions at the site level.
12278	12280 The page you are attempting to access requires your browser to have a Secure Sockets Layer (SSL) client certificate that the Web server recognizes.	12280 The page you are attempting to access requires your browser to have a Secure Sockets Layer (SSL) client certificate that the Web server recognizes.
12281	The page you are attempting to access requires an SSL client certificate. You are browsing to the page using HTTP. The client certificate has expired or the effective time has not been reached. The root certificate (the Certificate Authority certificate) of the client certificate issuing server is not installed on the Web server.	The page you are attempting to access requires an SSL client certificate. You are browsing to the page using HTTP. The client certificate has expired or the effective time has not been reached. The root certificate (the Certificate Authority certificate) of the client certificate issuing server is not installed on the Web server.
12282	Contact the site administrator to obtain a valid client certificate for the Web site. Try browsing to the page using HTTPS. If you have a client certificate installed, check if it has expired or if the effective time has not been reached. Verify that the root certificate is installed on the Web server.	Contact the site administrator to obtain a valid client certificate for the Web site. Try browsing to the page using HTTPS. If you have a client certificate installed, check if it has expired or if the effective time has not been reached. Verify that the root certificate is installed on the Web server.
12283	This error means that the requested URL requires client certificates. The client certificate is used for identifying you as a valid user of the resource. Contact the site administrator for information about how to acquire the correct certificate to use for the Web site.	This error means that the requested URL requires client certificates. The client certificate is used for identifying you as a valid user of the resource. Contact the site administrator for information about how to acquire the correct certificate to use for the Web site.
12284	12286 The DNS name of the computer from which you are browsing is not permitted to access the Web site you requested.	12286 The DNS name of the computer from which you are browsing is not permitted to access the Web site you requested.
12287	The server, site, application, or page requested has explicitly denied the DNS name of the client machine.	The server, site, application, or page requested has explicitly denied the DNS name of the client machine.
12288	Verify or change the DNS restrictions for the requested resource. Remove the DNS restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the applicable server, site, application or page.	Verify or change the DNS restrictions for the requested resource. Remove the DNS restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the applicable server, site, application or page.
12289	This error occurs when a DNS restriction is set for the requested resource. Set DNS restrictions at the server, site, application, or file level.	This error occurs when a DNS restriction is set for the requested resource. Set DNS restrictions at the server, site, application, or file level.
12290	248032	248032
12292	The account to which your client certificate is mapped on the Web server has been denied access to this Web site.	The account to which your client certificate is mapped on the Web server has been denied access to this Web site.
12293	The requested file or directory does not allow the user to whom the client certificate is mapped to access to the resource.	The requested file or directory does not allow the user to whom the client certificate is mapped to access to the resource.
12294	Verify the access control lists (ACLs) on the requested file or directory and make sure that the user to whom the client certificate is mapped has access. Check the effective date on the client certificate and ensure that the certificate is valid. Check the expiration date and ensure that the certificate has not expired. Check with the Certificate Authority that provided the certificate to see if your certificate has expired. Verify that the certificate was not explicitly denied access. Ensure that the client certificate is installed properly in the browser. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify the access control lists (ACLs) on the requested file or directory and make sure that the user to whom the client certificate is mapped has access. Check the effective date on the client certificate and ensure that the certificate is valid. Check the expiration date and ensure that the certificate has not expired. Check with the Certificate Authority that provided the certificate to see if your certificate has expired. Verify that the certificate was not explicitly denied access. Ensure that the client certificate is installed properly in the browser. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12295	The user account that the client certificate used to access the Web site was denied access to the resource.	The user account that the client certificate used to access the Web site was denied access to the resource.
12296	248075	248075
12298	Your client certificate was revoked, or the revocation status could not be determined.	Your client certificate was revoked, or the revocation status could not be determined.
12299	The client certificate was revoked or the revocation server could not be contacted.	The client certificate was revoked or the revocation server could not be contacted.
12300	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify the client certificate's validity by contacting the issuer of the client certificate. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify the client certificate's validity by contacting the issuer of the client certificate. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12301	This error is returned when a resource that the user is attempting to access requires a valid client Secure Sockets Layer (SSL) certificate. A client certificate is used for identifying you as a valid user of the resource and must be installed in the Web browser. The error message can also occur if IIS is unable to contact the server that stores the Certificate Revocation List (CRL) to check for revoked certificates. If a CRL server is unreachable, the certificates are presumed to be revoked.	This error is returned when a resource that the user is attempting to access requires a valid client Secure Sockets Layer (SSL) certificate. A client certificate is used for identifying you as a valid user of the resource and must be installed in the Web browser. The error message can also occur if IIS is unable to contact the server that stores the Certificate Revocation List (CRL) to check for revoked certificates. If a CRL server is unreachable, the certificates are presumed to be revoked.
12302	248058294305	248058294305
12304	The Web server is configured to not list the contents of this directory.	The Web server is configured to not list the contents of this directory.
12305	A default document is not configured for the requested URL, and directory browsing is not enabled on the server.	A default document is not configured for the requested URL, and directory browsing is not enabled on the server.
12306	If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. Enable directory browsing using IIS Manager. Open IIS Manager. In the Features view, double-click Directory Browsing. On the Directory Browsing page, in the Actions pane, click Enable. Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.	If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. Enable directory browsing using IIS Manager. Open IIS Manager. In the Features view, double-click Directory Browsing. On the Directory Browsing page, in the Actions pane, click Enable. Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.
12307	This error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server.	This error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server.
12308	12310 Your client certificate is either not trusted or is invalid.	12310 Your client certificate is either not trusted or is invalid.
12311	The client certificate used for this request is not trusted by the Web server.	The client certificate used for this request is not trusted by the Web server.
12312	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify that the client certificate is trusted by the Web server. Verify that the root certificate is properly installed and trusted on the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify that the client certificate is trusted by the Web server. Verify that the root certificate is properly installed and trusted on the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12313	A Secure Sockets Layer (SSL) client certificate identifies you as a valid user of the resource. This error can occur if you choose a client certificate created by a Certificate Authority (CA) that is not trusted by the Web server.	A Secure Sockets Layer (SSL) client certificate identifies you as a valid user of the resource. This error can occur if you choose a client certificate created by a Certificate Authority (CA) that is not trusted by the Web server.
12314	12316 Your client certificate has expired or is not yet valid.	12316 Your client certificate has expired or is not yet valid.
12317	The client certificate used to access the Web server has expired or is not yet valid.	The client certificate used to access the Web server has expired or is not yet valid.
12318	Verify that the client certificate has not expired. Verify that the client machine's date is set correctly. Obtain a new client certificate. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify that the client certificate has not expired. Verify that the client machine's date is set correctly. Obtain a new client certificate. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12319	A Secure Sockets Layer (SSL) client certificate identifies you as a valid user of the resource. The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication.	A Secure Sockets Layer (SSL) client certificate identifies you as a valid user of the resource. The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication.
12320	12322 The specified request cannot be processed in the application pool that is configured for this resource on the Web server.	12322 The specified request cannot be processed in the application pool that is configured for this resource on the Web server.
12323	An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL. An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL. You have a custom error page that is located in one application pool but is referenced by a Web site in another application pool. When the URL is processed, it is determined by IIS that that it should have been processed in the first application pool, not the other pool. The Web site has multiple applications configured. The application this request is configured to run in is set to run in an application pool that does not exist.	An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL. An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL. You have a custom error page that is located in one application pool but is referenced by a Web site in another application pool. When the URL is processed, it is determined by IIS that that it should have been processed in the first application pool, not the other pool. The Web site has multiple applications configured. The application this request is configured to run in is set to run in an application pool that does not exist.
12324	If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate. If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature. Verify that the application pool for the application exists. Create a tracing rule to track failed requests for this HTTP status code and see if ExecuteURL is being called. For more information about creating a tracing rule for failed requests, click here.	If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate. If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature. Verify that the application pool for the application exists. Create a tracing rule to track failed requests for this HTTP status code and see if ExecuteURL is being called. For more information about creating a tracing rule for failed requests, click here.
12325	This error occurs if the application pool for the request does not exist, or if an ISAPI filter, ISAPI extension or HTTP module calls the ExecuteURL server support function (or ExecuteRequest) with a URL that is configured in a different application pool. Due to security reasons, a Web site in one application pool cannot make ExecuteURL requests against a URL in another application pool. If you have an application that is trying to process a URL in another application pool, ensure that they both run in the same application pool if appropriate.	This error occurs if the application pool for the request does not exist, or if an ISAPI filter, ISAPI extension or HTTP module calls the ExecuteURL server support function (or ExecuteRequest) with a URL that is configured in a different application pool. Due to security reasons, a Web site in one application pool cannot make ExecuteURL requests against a URL in another application pool. If you have an application that is trying to process a URL in another application pool, ensure that they both run in the same application pool if appropriate.
12326	12328 The configured user for this application pool does not have sufficient privileges to run CGI applications.	12328 The configured user for this application pool does not have sufficient privileges to run CGI applications.
12329	CGI applications are launched as the authenticated user, if the site has anonymous authentication configured, the application may be launched as the anonymous user account. If CreateProcessAsUser is true, then CGI applications are launched as the authenticated user. If CreateProcessAsUser is false, then CGI applications are launched as the process identity. The user account under which the application pool is configured to run does not have the following privileges: Replace a process level token - SE_ASSIGNPRIMARYTOKEN_NAME. Adjust memory quotas for a process - SE_INCREASE_QUOTA_NAME.	CGI applications are launched as the authenticated user, if the site has anonymous authentication configured, the application may be launched as the anonymous user account. If CreateProcessAsUser is true, then CGI applications are launched as the authenticated user. If CreateProcessAsUser is false, then CGI applications are launched as the process identity. The user account under which the application pool is configured to run does not have the following privileges: Replace a process level token - SE_ASSIGNPRIMARYTOKEN_NAME. Adjust memory quotas for a process - SE_INCREASE_QUOTA_NAME.
12330	If the CGI application is launched as the anonymous user, you can set the IIS configuration property, called CreateProcessAsUser, to False. This setting launches the CGI application as the application pool identity. Add the necessary privileges to the user account the application pool is running as by completing the following: Open the Local Security Policy settings MMC. Start %windir%\System32\Secpol.msc. Expand the Local Policies node and then click User Rights Assignment. In the right-hand pane, double-click Adjust memory quotas for a process. Add the application pool identity to this user right and then click OK. In the-right hand pane, double-click Replace a process token. Add the application pool identity to this user right and then click OK. Restart IIS for the changes to take effect.	If the CGI application is launched as the anonymous user, you can set the IIS configuration property, called CreateProcessAsUser, to False. This setting launches the CGI application as the application pool identity. Add the necessary privileges to the user account the application pool is running as by completing the following: Open the Local Security Policy settings MMC. Start %windir%\System32\Secpol.msc. Expand the Local Policies node and then click User Rights Assignment. In the right-hand pane, double-click Adjust memory quotas for a process. Add the application pool identity to this user right and then click OK. In the-right hand pane, double-click Replace a process token. Add the application pool identity to this user right and then click OK. Restart IIS for the changes to take effect.
12331	This error means that the process identity for the application pool does not have sufficient privileges to create the CGI Application. This can occur if the application pool identity does not have sufficient privileges, or when the CGI application is launched as the anonymous user.	This error means that the process identity for the application pool does not have sufficient privileges to create the CGI Application. This can occur if the application pool identity does not have sufficient privileges, or when the CGI application is launched as the anonymous user.
12332	12334 The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.	12334 The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
12335	The directory or file specified does not exist on the Web server. The URL contains a typographical error. A custom filter or module, such as URLScan, restricts access to the file.	The directory or file specified does not exist on the Web server. The URL contains a typographical error. A custom filter or module, such as URLScan, restricts access to the file.
12336	Create the content on the Web server. Review the browser URL. Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.	Create the content on the Web server. Review the browser URL. Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.
12337	This error means that the file or directory does not exist on the server. Create the file or directory and try the request again.	This error means that the file or directory does not exist on the server. Create the file or directory and try the request again.
12338	12340 The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server.	12340 The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server.
12341	No handler mapping for this request was found. A feature may have to be installed. The Web service extension for the requested resource is not enabled on the server. The mapping for the extension points to the incorrect location. The extension was misspelled in the browser or the Web server.	No handler mapping for this request was found. A feature may have to be installed. The Web service extension for the requested resource is not enabled on the server. The mapping for the extension points to the incorrect location. The extension was misspelled in the browser or the Web server.
12342	Install the feature that handles this request. For example, if you get this error for an .ASPX page, you may have to install ASP.NET via IIS setup. Verify that the Web service extension requested is enabled on the server. Open the IIS Manager and navigate to the server level. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed. If the extension is not in the list, click Add in the Actions pane. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file. In the Description box, type a brief description of the restriction. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane. Click OK. NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list. Verify that the location of the extension is correct. Verify that the URL for the extension is spelled correctly both in the browser and the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Install the feature that handles this request. For example, if you get this error for an .ASPX page, you may have to install ASP.NET via IIS setup. Verify that the Web service extension requested is enabled on the server. Open the IIS Manager and navigate to the server level. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed. If the extension is not in the list, click Add in the Actions pane. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file. In the Description box, type a brief description of the restriction. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane. Click OK. NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list. Verify that the location of the extension is correct. Verify that the URL for the extension is spelled correctly both in the browser and the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12343	This error occurs when the necessary Web service extension is not enabled, the location or the name of the extension are misspelled or incorrectly entered.	This error occurs when the necessary Web service extension is not enabled, the location or the name of the extension are misspelled or incorrectly entered.
12344	12346 The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.	12346 The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
12347	It is possible that a handler mapping is missing. By default, the static file handler processes all content. The feature you are trying to use may not be installed. The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.) If ASP.NET is not installed.	It is possible that a handler mapping is missing. By default, the static file handler processes all content. The feature you are trying to use may not be installed. The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.) If ASP.NET is not installed.
12348	In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Install ASP.NET. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Install ASP.NET. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12349	This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.	This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.
12350	12352 The resource you are looking for does not have a handler associated with it.	12352 The resource you are looking for does not have a handler associated with it.
12353	The file extension for the requested URL does not have a handler configured to process the request on the Web server.	The file extension for the requested URL does not have a handler configured to process the request on the Web server.
12354	If the file extension does not have a handler associated with it, add a handler mapping for the extension. Verify that the handler associated with the file extension is properly installed and configured. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	If the file extension does not have a handler associated with it, add a handler mapping for the extension. Verify that the handler associated with the file extension is properly installed and configured. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12355	This error means that the Web server does not recognize the file extension of the requested resource. A module handler is not configured on the Web server for this extension. If the file extension being denied is required by the Web server, add the appropriate handler for the file extension.	This error means that the Web server does not recognize the file extension of the requested resource. A module handler is not configured on the Web server for this extension. If the file extension being denied is required by the Web server, add the appropriate handler for the file extension.
12356	12358 The request filtering module is configured to deny the URL sequence.	12358 The request filtering module is configured to deny the URL sequence.
12359	Request filtering is configured for the Web server and the URL sequence is being denied.	Request filtering is configured for the Web server and the URL sequence is being denied.
12360	Verify the configuration/system.webServer/security/requestFiltering/denyUrlSequences settings in the applicationHost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering/denyUrlSequences settings in the applicationHost.config or web.config file.
12361	This is a security feature. Do not change this feature unless the scope of the change is fully understood. To allow the URL sequence for the request, remove the denied URL from configuration/system.webServer/security/requestFiltering/denyUrlSequences.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. To allow the URL sequence for the request, remove the denied URL from configuration/system.webServer/security/requestFiltering/denyUrlSequences.
12362	12364 The request filtering module is configured to deny the HTTP verb.	12364 The request filtering module is configured to deny the HTTP verb.
12365	Request filtering is configured for the Web server and the HTTP verb for this request is explicitly denied.	Request filtering is configured for the Web server and the HTTP verb for this request is explicitly denied.
12366	Verify the configuration/system.webServer/security/requestFiltering/verbs settings in applicationHost.config and web.config.	Verify the configuration/system.webServer/security/requestFiltering/verbs settings in applicationHost.config and web.config.
12367	The request filtering section of the applicationhost.config file or a web.config file contains an entry to deny the HTTP verb used for the request. This is a security feature and should not be changed unless the scope of the change is fully understood. If the HTTP Verb should be allowed then remove the HTTP verb being denied from configuration/system.webServer/security/requestFiltering/verbs.	The request filtering section of the applicationhost.config file or a web.config file contains an entry to deny the HTTP verb used for the request. This is a security feature and should not be changed unless the scope of the change is fully understood. If the HTTP Verb should be allowed then remove the HTTP verb being denied from configuration/system.webServer/security/requestFiltering/verbs.
12368	12370 The request filtering module is configured to deny the file extension.	12370 The request filtering module is configured to deny the file extension.
12371	Request filtering is configured for the Web server and the file extension for this request is explicitly denied.	Request filtering is configured for the Web server and the file extension for this request is explicitly denied.
12372	Verify the configuration/system.webServer/security/requestFiltering/fileExtensions settings in applicationhost.config and web.config.	Verify the configuration/system.webServer/security/requestFiltering/fileExtensions settings in applicationhost.config and web.config.
12373	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If the file extension for the request should be allowed, remove the denied file extension from configuration/system.webServer/security/requestFiltering/fileExtensions.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If the file extension for the request should be allowed, remove the denied file extension from configuration/system.webServer/security/requestFiltering/fileExtensions.
12374	12376 The request filtering module is configured to deny a path in the URL that contains a hiddenSegment section.	12376 The request filtering module is configured to deny a path in the URL that contains a hiddenSegment section.
12377	Request filtering is configured for the Web server and it contains a hiddenSegments section that allows the server administrator to deny access to specific directories.	Request filtering is configured for the Web server and it contains a hiddenSegments section that allows the server administrator to deny access to specific directories.
12378	Verify configuration/system.webServer/security/requestFiltering/hiddenSegments settings in the applicationhost.config or the web.config file.	Verify configuration/system.webServer/security/requestFiltering/hiddenSegments settings in the applicationhost.config or the web.config file.
12379	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If content should be served from a specific directory being denied by this setting, remove the denied directory from configuration/system.webServer/security/requestFiltering/hiddenSegments.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If content should be served from a specific directory being denied by this setting, remove the denied directory from configuration/system.webServer/security/requestFiltering/hiddenSegments.
12380	12382 This error occurs when the requested file is marked as hidden on the file system.	12382 This error occurs when the requested file is marked as hidden on the file system.
12383	The requested file is marked as hidden on the file system.	The requested file is marked as hidden on the file system.
12384	If IIS should serve the file, remove the hidden file attribute.	If IIS should serve the file, remove the hidden file attribute.
12385	This is a security feature that prevents displaying hidden files. Make sure the file should be served before removing the hidden file attribute.	This is a security feature that prevents displaying hidden files. Make sure the file should be served before removing the hidden file attribute.
12386	12388 The request filtering module is configured to deny a request header that is too large.	12388 The request filtering module is configured to deny a request header that is too large.
12389	Request filtering is configured for the Web server and it is denying the request because the request header was too large.	Request filtering is configured for the Web server and it is denying the request because the request header was too large.
12390	Verify the configuration/system.webServer/security/requestFiltering/requestLimits/headerLimits settings in the applicationhost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering/requestLimits/headerLimits settings in the applicationhost.config or web.config file.
12391	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If the request header size is legitimate, increase the size limit for the header in the configuration/system.webServer/security/requestFiltering/requestLimits/headerLimits section.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. If the request header size is legitimate, increase the size limit for the header in the configuration/system.webServer/security/requestFiltering/requestLimits/headerLimits section.
12392	12394 The request filtering module is configured to deny a request that contains a double escape sequence.	12394 The request filtering module is configured to deny a request that contains a double escape sequence.
12395	The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.	The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.
12396	Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.	Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.
12397	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You should take a network trace before changing this value to confirm that the request is not malicious. If double escape sequences are allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting. This could be caused by a malformed URL sent to the server by a malicious user.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You should take a network trace before changing this value to confirm that the request is not malicious. If double escape sequences are allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting. This could be caused by a malformed URL sent to the server by a malicious user.
12398	12400 The request filtering module is configured to deny a request URL that contains high-bit characters.	12400 The request filtering module is configured to deny a request URL that contains high-bit characters.
12401	The request contained high-bit characters and request filtering is configured on the Web server to deny high-bit characters.	The request contained high-bit characters and request filtering is configured on the Web server to deny high-bit characters.
12402	Verify the configuration/system.webServer/security/requestFiltering@allowHighBitCharacters setting in the applicationhost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering@allowHighBitCharacters setting in the applicationhost.config or web.config file.
12403	This is a security feature. Do not change this feature unless the scope of the change is fully understood. When allowHighBitCharacters is set to false (the value is true if not present), IIS rejects a request if it contains high-bit characters. If high-bit characters should be allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowHighBitCharacters setting.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. When allowHighBitCharacters is set to false (the value is true if not present), IIS rejects a request if it contains high-bit characters. If high-bit characters should be allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowHighBitCharacters setting.
12404	12406 The request filtering module is configured to deny a request that exceeds the request content length.	12406 The request filtering module is configured to deny a request that exceeds the request content length.
12407	Request filtering is configured on the Web server to deny the request because the content length exceeds the configured value.	Request filtering is configured on the Web server to deny the request because the content length exceeds the configured value.
12408	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting in the applicationhost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting in the applicationhost.config or web.config file.
12409	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose content length is greater than a specified value. If the request's content length is greater than the configured length, this error is returned. If the content length requires an increase, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose content length is greater than a specified value. If the request's content length is greater than the configured length, this error is returned. If the content length requires an increase, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting.
12410	12412 The request filtering module is configured to deny a URL that is too long.	12412 The request filtering module is configured to deny a URL that is too long.
12413	Request filtering is configured on the Web server to deny the request when the URL is too long.	Request filtering is configured on the Web server to deny the request when the URL is too long.
12414	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxUrl setting in the applicationhost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxUrl setting in the applicationhost.config or web.config file.
12415	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose URL length is greater than a specified value. If the URL length is greater than the configured length, this error is returned. If the URL length requires an increase, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxUrl setting.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose URL length is greater than a specified value. If the URL length is greater than the configured length, this error is returned. If the URL length requires an increase, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxUrl setting.
12416	12418 The request filtering module is configured to deny a request where the query string is too long.	12418 The request filtering module is configured to deny a request where the query string is too long.
12419	Request filtering is configured on the Web server to deny the request because the query string is too long.	Request filtering is configured on the Web server to deny the request because the query string is too long.
12420	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxQueryString setting in the applicationhost.config or web.config file.	Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxQueryString setting in the applicationhost.config or web.config file.
12421	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose query string is greater than a specified value. If the request's query string is greater than the configured value, this error is returned. If the allowed length of the query string needs to be increased, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxQueryString setting.	This is a security feature. Do not change this feature unless the scope of the change is fully understood. You can configure the IIS server to reject requests whose query string is greater than a specified value. If the request's query string is greater than the configured value, this error is returned. If the allowed length of the query string needs to be increased, modify the configuration/system.webServer/security/requestFiltering/requestLimits@maxQueryString setting.
12422	12424 The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.	12424 The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.
12425	The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request. A request was sent to the server that contained an invalid HTTP verb. The request is for static content and contains an HTTP verb other than GET or HEAD. A request was sent to a virtual directory using the HTTP verb POST and the default document is a static file that does not support HTTP verbs other than GET or HEAD.	The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request. A request was sent to the server that contained an invalid HTTP verb. The request is for static content and contains an HTTP verb other than GET or HEAD. A request was sent to a virtual directory using the HTTP verb POST and the default document is a static file that does not support HTTP verbs other than GET or HEAD.
12426	Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site. Check the IIS log file to see which verb is not allowed for the request. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site. Check the IIS log file to see which verb is not allowed for the request. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12427	This error means that the request sent to the Web server contained an HTTP verb that is not allowed by the configured module handler for the request.	This error means that the request sent to the Web server contained an HTTP verb that is not allowed by the configured module handler for the request.
12428	12430 The resource cannot be displayed because the file extension is not being accepted by your browser.	12430 The resource cannot be displayed because the file extension is not being accepted by your browser.
12431	The request was rejected because it contained an Accept header for a MIME type that is not supported for the requested file extension.	The request was rejected because it contained an Accept header for a MIME type that is not supported for the requested file extension.
12432	Verify the MIME settings for the file extension that was requested to make sure this MIME type is acceptable.	Verify the MIME settings for the file extension that was requested to make sure this MIME type is acceptable.
12433	This error occurs when the client requests a file with a certain file extension and then specifies the Accept header with a MIME type that is different from the configuration of this file extension on the server. An example is requesting a file with the .doc extension and specifying an Accept header with text/xml instead of application/msword. Usually the client specifies */* for the Accept header, which allows the request to serve any MIME type.	This error occurs when the client requests a file with a certain file extension and then specifies the Accept header with a MIME type that is different from the configuration of this file extension on the server. An example is requesting a file with the .doc extension and specifying an Accept header with text/xml instead of application/msword. Usually the client specifies */* for the Accept header, which allows the request to serve any MIME type.
12434	12436 The request was not completed due to preconditions that are set in the request header.	12436 The request was not completed due to preconditions that are set in the request header.
12437	The request sent to the Web server contained the If-Match or If-Unmodified-Since header. IIS checked this header value and failed the request.	The request sent to the Web server contained the If-Match or If-Unmodified-Since header. IIS checked this header value and failed the request.
12438	Get a network trace and verify that these headers are correct when sending to the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Get a network trace and verify that these headers are correct when sending to the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12439	Preconditions prevent the requested method from applying to a resource other than the one intended. An example of a precondition is to test for expired content in the page cache of the client. When the If-Match or If-Unmodified-Since header is part of the request to the Web server, IIS verifies that the request can continue processing based on these header values. In the case of the If-Match header, IIS checks its value against the current list of E-Tags it has stored. In the case of the If-Unmodified-Since header IIS checks the value against the last modified time of the file.	Preconditions prevent the requested method from applying to a resource other than the one intended. An example of a precondition is to test for expired content in the page cache of the client. When the If-Match or If-Unmodified-Since header is part of the request to the Web server, IIS verifies that the request can continue processing based on these header values. In the case of the If-Match header, IIS checks its value against the current list of E-Tags it has stored. In the case of the If-Unmodified-Since header IIS checks the value against the last modified time of the file.
12440	12442 The page cannot be displayed because an internal server error has occurred.	12442 The page cannot be displayed because an internal server error has occurred.
12443	IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.	IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
12444	Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12445	This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.	This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
12446	294807	294807
12448	The request was not processed because the Web site is shutting down.	The request was not processed because the Web site is shutting down.
12449	A request was sent to the Web server while the worker process configured to host the Web site was shutting down. The worker process tried to shut down but experienced a hang during the shutdown process. The worker process is shutting down unexpectedly. The application pool is recycling too often.	A request was sent to the Web server while the worker process configured to host the Web site was shutting down. The worker process tried to shut down but experienced a hang during the shutdown process. The worker process is shutting down unexpectedly. The application pool is recycling too often.
12450	Wait for the worker process to finish shutting down and then try the request again. Verify the application pool settings to make sure the recycling options are not causing the application pool to restart frequently. Open IIS Manager. In the Connections pane, expand the server node and click Application Pools. On the Application Pools page, select the Application Pool that is recycling frequently. In the Actions pane, under Edit Application Pool, click Recycling. Review the recycling settings to ensure that the settings are not making the application pool recycle too often. Manually restart the worker process. Open IIS Manager. In the Connections pane, expand the server node and click Application Pools. On the Application Pools page, select the Application Pool that is recycling frequently. In the Actions pane, under Application Pool Tasks, click Stop. In the Actions pane, under Application Pool Tasks, click Start. Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.	Wait for the worker process to finish shutting down and then try the request again. Verify the application pool settings to make sure the recycling options are not causing the application pool to restart frequently. Open IIS Manager. In the Connections pane, expand the server node and click Application Pools. On the Application Pools page, select the Application Pool that is recycling frequently. In the Actions pane, under Edit Application Pool, click Recycling. Review the recycling settings to ensure that the settings are not making the application pool recycle too often. Manually restart the worker process. Open IIS Manager. In the Connections pane, expand the server node and click Application Pools. On the Application Pools page, select the Application Pool that is recycling frequently. In the Actions pane, under Application Pool Tasks, click Stop. In the Actions pane, under Application Pool Tasks, click Start. Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.
12451	This error occurs because the Web site is currently in the process of shutting down and therefore is not accepting any new requests. If this error persists, the Web site could experience problems shutting down gracefully or recycling too often. Consult the event logs for more information on the cause of the shutdown.	This error occurs because the Web site is currently in the process of shutting down and therefore is not accepting any new requests. If this error persists, the Web site could experience problems shutting down gracefully or recycling too often. Consult the event logs for more information on the cause of the shutdown.
12452	12454 The request cannot process while the Web site is restarting.	12454 The request cannot process while the Web site is restarting.
12455	The global.asa file for the ASP application requested was modified. This caused the application to restart. Antivirus software is configured to scan the global.asa file for the ASP application.	The global.asa file for the ASP application requested was modified. This caused the application to restart. Antivirus software is configured to scan the global.asa file for the ASP application.
12456	Prevent antivirus software from scanning the global.asa file. Wait until the Web application has restarted and try the request again. Look in the event logs for messages related to application restart.	Prevent antivirus software from scanning the global.asa file. Wait until the Web application has restarted and try the request again. Look in the event logs for messages related to application restart.
12457	This error occurs when the global.asa file for an application was modified and caused the Web application to restart.	This error occurs when the global.asa file for an application was modified and caused the Web application to restart.
12458	248013	248013
12460	The request cannot be processed because the amount of traffic exceeds the Web site's configured capacity.	The request cannot be processed because the amount of traffic exceeds the Web site's configured capacity.
12461	The Web server is running at capacity and cannot accept any more requests. The server has become unstable and the ASP application cannot allocate enough memory for a new request. The ASP queue is full (ASPRequestQueueMax was reached).	The Web server is running at capacity and cannot accept any more requests. The server has become unstable and the ASP application cannot allocate enough memory for a new request. The ASP queue is full (ASPRequestQueueMax was reached).
12462	Determine which requests are running for the application and whether they are running for an abnormal amount of time. Open IIS Manager. In the Connections pane, select the server node in the tree. In the Features view, double-click Worker Processes to view the currently running requests. Use the IIS Debugging Tools to troubleshoot the issue as a hang.	Determine which requests are running for the application and whether they are running for an abnormal amount of time. Open IIS Manager. In the Connections pane, select the server node in the tree. In the Features view, double-click Worker Processes to view the currently running requests. Use the IIS Debugging Tools to troubleshoot the issue as a hang.
12463	This error occurs when the ASP application cannot allocate enough memory for a new request, or the request was sitting in the request queue for too long.	This error occurs when the ASP application cannot allocate enough memory for a new request, or the request was sitting in the request queue for too long.
12464	12466 The global.asax is a special file that you cannot access directly from your browser.	12466 The global.asax is a special file that you cannot access directly from your browser.
12467	A request was made for the global.asax file directly.	A request was made for the global.asax file directly.
12468	This is not allowed by the server for security purposes.	This is not allowed by the server for security purposes.
12469	This error is returned when a URL contains a request for the global.asax file for a Web application. This error is returned only if a handler is set up for the .asax file; otherwise, a 404.3 error is returned.	This error is returned when a URL contains a request for the global.asax file for a Web application. This error is returned only if a handler is set up for the .asax file; otherwise, a 404.3 error is returned.
12470	12472 You cannot access the page you are requesting because the UNC authorization settings are configured incorrectly on the Web server.	12472 You cannot access the page you are requesting because the UNC authorization settings are configured incorrectly on the Web server.
12473	The content for the request is located on a remote file server, and the UNC credentials specified to connect to the remote file share are incorrect. The content for the request is located on a remote file share, and the permissions on the file share do not allow the user configured in IIS to access the file share.	The content for the request is located on a remote file server, and the UNC credentials specified to connect to the remote file share are incorrect. The content for the request is located on a remote file share, and the permissions on the file share do not allow the user configured in IIS to access the file share.
12474	Verify the credentials set for accessing the remote file share. Open IIS Manager. In the Connections pane, click the site that is having the problem. In the Actions pane, under Edit Site, choose Advanced Settings. Verify that the username and password are correct. Check the security settings and sharing permissions for the remote UNC share hosting the content. If the account used to connect to the content is a local account. Verify that the password is synced on the Web server and the remote file server.	Verify the credentials set for accessing the remote file share. Open IIS Manager. In the Connections pane, click the site that is having the problem. In the Actions pane, under Edit Site, choose Advanced Settings. Verify that the username and password are correct. Check the security settings and sharing permissions for the remote UNC share hosting the content. If the account used to connect to the content is a local account. Verify that the password is synced on the Web server and the remote file server.
12475	This error occurs when the requested content is hosted on a remote file share and the credentials used to connect to the remote file share are invalid.	This error occurs when the requested content is hosted on a remote file share and the credentials used to connect to the remote file share are invalid.
12476	12478 The requested page cannot be accessed because the related configuration data for the page is invalid.	12478 The requested page cannot be accessed because the related configuration data for the page is invalid.
12479	The worker process is unable to read the applicationhost.config or web.config file. There is malformed XML in the applicationhost.config or web.config file. The server cannot access the applicationhost.config or web.config file because of incorrect NTFS permissions.	The worker process is unable to read the applicationhost.config or web.config file. There is malformed XML in the applicationhost.config or web.config file. The server cannot access the applicationhost.config or web.config file because of incorrect NTFS permissions.
12480	Look in the event logs for information about why the configuration files are not readable. Make sure the user identity specified for the application pool, or the authenticated user, has the required permissions to access the web.config file.	Look in the event logs for information about why the configuration files are not readable. Make sure the user identity specified for the application pool, or the authenticated user, has the required permissions to access the web.config file.
12481	This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.	This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
12482	12484 The page cannot be displayed due to an error with ASP.	12484 The page cannot be displayed due to an error with ASP.
12485	This is a generic ASP error that means there was a problem while processing the requested page. Turn off Show Friendly HTTP Errors in the browser to see more information about the failure.	This is a generic ASP error that means there was a problem while processing the requested page. Turn off Show Friendly HTTP Errors in the browser to see more information about the failure.
12486	Look in the IIS log file for additional information on the failure. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Look in the IIS log file for additional information on the failure. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12487	This error occurs when the URL requested is for an ASP application and a problem occurred on the server while processing the request.	This error occurs when the URL requested is for an ASP application and a problem occurred on the server while processing the request.
12488	12490 The page you are looking for cannot be displayed because a header value in the request does not match configuration settings.	12490 The page you are looking for cannot be displayed because a header value in the request does not match configuration settings.
12491	The request contains the HTTP verb "TRACE" and the registry value to enable this method is not configured on the server.	The request contains the HTTP verb "TRACE" and the registry value to enable this method is not configured on the server.
12492	If the server should allow the "TRACE" method, create a new DWORD registry parameter named "EnableTraceMethod" and set its value to 1 at the following location in the registry.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	If the server should allow the "TRACE" method, create a new DWORD registry parameter named "EnableTraceMethod" and set its value to 1 at the following location in the registry.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12493	This error is returned only when the HTTP verb is Trace and the EnableTraceMethod registry value is not set to 1. If this error is occurring for another reason, the registry value is probably set by a third-party application.	This error is returned only when the HTTP verb is Trace and the EnableTraceMethod registry value is not set to 1. If this error is occurring for another reason, the registry value is probably set by a third-party application.
12494	12496 The specified CGI application encountered an error and the server terminated the process.	12496 The specified CGI application encountered an error and the server terminated the process.
12497	The CGI application did not return a valid set of HTTP errors. A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.	The CGI application did not return a valid set of HTTP errors. A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.
12498	Use DebugDiag to troubleshoot the CGI application. Determine if a proxy or gateway is responsible for this error.	Use DebugDiag to troubleshoot the CGI application. Determine if a proxy or gateway is responsible for this error.
12499	This error occurs when a CGI application does not return a valid set of HTTP headers, or when a proxy or gateway was unable to send the request to a parent gateway. You may need to get a network trace or contact the proxy server administrator, if it is not a CGI problem.	This error occurs when a CGI application does not return a valid set of HTTP headers, or when a proxy or gateway was unable to send the request to a parent gateway. You may need to get a network trace or contact the proxy server administrator, if it is not a CGI problem.
12500	12502 The CGI application exceeded the time allowed for processing and the process was shut down.	12502 The CGI application exceeded the time allowed for processing and the process was shut down.
12503	The CGI application handling the request took longer than the configured CGI timeout to process the request. The CGI application is taking too long to process the request.	The CGI application handling the request took longer than the configured CGI timeout to process the request. The CGI application is taking too long to process the request.
12504	Verify the configured timeout for the CGI application. Open IIS Manager. In the Connections pane, click the site or application where the problem is occurring. In the Features pane, double-click CGI. In the CGI page, under Behavior, verify that a value is set for the Timeout property. Change the timeout value, if necessary, and then in the Actions pane click Apply. Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.	Verify the configured timeout for the CGI application. Open IIS Manager. In the Connections pane, click the site or application where the problem is occurring. In the Features pane, double-click CGI. In the CGI page, under Behavior, verify that a value is set for the Timeout property. Change the timeout value, if necessary, and then in the Actions pane click Apply. Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.
12505	This error occurs when the request is configured to handle by a CGI application and the CGI application takes longer than the configured timeout to handle the request. If the request usually takes longer than the configured timeout to run, increase the timeout value. Otherwise, troubleshoot the CGI application to determine the delay.	This error occurs when the request is configured to handle by a CGI application and the CGI application takes longer than the configured timeout to handle the request. If the request usually takes longer than the configured timeout to run, increase the timeout value. Otherwise, troubleshoot the CGI application to determine the delay.
12506	12508 The specified CGI application did not return a complete set of HTTP headers.	12508 The specified CGI application did not return a complete set of HTTP headers.
12509	The CGI process was shut down or terminated unexpectedly before it finished processing the request. The CGI process has a flaw and does not return a complete set of HTTP headers.	The CGI process was shut down or terminated unexpectedly before it finished processing the request. The CGI process has a flaw and does not return a complete set of HTTP headers.
12510	Check the event logs on the system to see whether the CGI process is shutting down unexpectedly. Troubleshoot the CGI application to determine why it is not sending a complete set of HTTP headers.	Check the event logs on the system to see whether the CGI process is shutting down unexpectedly. Troubleshoot the CGI application to determine why it is not sending a complete set of HTTP headers.
12511	This error occurs when the CGI process handling the request exits before it finishes sending the response to IIS.	This error occurs when the CGI process handling the request exits before it finishes sending the response to IIS.
12512	12514 You have attempted to run a CGI, ISAPI or other executable program from a directory that does not allow programs to be run.	12514 You have attempted to run a CGI, ISAPI or other executable program from a directory that does not allow programs to be run.
12515	The directory does not have Execute permission enabled.	The directory does not have Execute permission enabled.
12516	If appropriate, add Execute access to this directory.	If appropriate, add Execute access to this directory.
12517	Execute access is not enabled for the directory where you are attempting to launch an executable program. Before enabling Execute access, determined if this is appropriate.	Execute access is not enabled for the directory where you are attempting to launch an executable program. Before enabling Execute access, determined if this is appropriate.
12518	12520 You must be authenticated by a proxy before the Web server can process your request.	12520 You must be authenticated by a proxy before the Web server can process your request.
12521	A proxy between the client and the Web server requires some form of authentication.	A proxy between the client and the Web server requires some form of authentication.
12522	To troubleshoot this error depends on the proxy. You may need to get a network trace to resolve this problem.	To troubleshoot this error depends on the proxy. You may need to get a network trace to resolve this problem.
12523	This error occurs when a proxy between the client and the Web server requires authentication. You may need to get a network trace or contact the proxy server administrator.	This error occurs when a proxy between the client and the Web server requires authentication. You may need to get a network trace or contact the proxy server administrator.
12524	12526 The page cannot be displayed because the client took too long to complete its request and the server closed the connection.	12526 The page cannot be displayed because the client took too long to complete its request and the server closed the connection.
12527	The client took too long to complete its request and the connection was closed.	The client took too long to complete its request and the connection was closed.
12528	Troubleshooting this error requires the client. You may need a network trace to determine why the request was not completed by the client.	Troubleshooting this error requires the client. You may need a network trace to determine why the request was not completed by the client.
12529	This error occurs when a client takes too long to complete its request.	This error occurs when a client takes too long to complete its request.
12530	12532 The page was not displayed because there was a conflict.	12532 The page was not displayed because there was a conflict.
12533	The request could not be completed due to a conflict with the current state of the resource.	The request could not be completed due to a conflict with the current state of the resource.
12534	To troubleshoot this error depends upon the client.	To troubleshoot this error depends upon the client.
12535	This error occurs when there is a conflict with the current state of the resource.	This error occurs when there is a conflict with the current state of the resource.
12536	12538 The page you requested was removed.	12538 The page you requested was removed.
12539	The file has been removed.	The file has been removed.
12540	This status code occurs when a file or resource has been removed, or when the resource is permanently unavailable and has no forwarding address.	This status code occurs when a file or resource has been removed, or when the resource is permanently unavailable and has no forwarding address.
12541	This error occurs when a resource has been removed and the resource is not available or has no redirect address.	This error occurs when a resource has been removed and the resource is not available or has no redirect address.
12542	12544 The page cannot be displayed because the server requires a Content-Length header in the request.	12544 The page cannot be displayed because the server requires a Content-Length header in the request.
12545	The file was removed.	The file was removed.
12547	This error occurs when a resource has been removed and in many cases is used when the resource is not available or has no redirect address.	This error occurs when a resource has been removed and in many cases is used when the resource is not available or has no redirect address.
12548	12550 The page was not displayed because the Request URI is too long.	12550 The page was not displayed because the Request URI is too long.
12551	The server is refusing to service the request because the requested URL is too long. The client has encountered a redirection problem (for example, a redirected URL prefix that points to a suffix of itself). The client has improperly converted a POST request to a GET request with long query information. The Web server is under attack by the client.	The server is refusing to service the request because the requested URL is too long. The client has encountered a redirection problem (for example, a redirected URL prefix that points to a suffix of itself). The client has improperly converted a POST request to a GET request with long query information. The Web server is under attack by the client.
12552	Verify that the Request URI is not too long or try the request without it.	Verify that the Request URI is not too long or try the request without it.
12553	This error occurs when the Request URI is too long and the server is refusing to service the request. It could occur due to a client error or a client attack against the Web server.	This error occurs when the Request URI is too long and the server is refusing to service the request. It could occur due to a client error or a client attack against the Web server.
12554	12556 The server cannot service the request because the media type is unsupported.	12556 The server cannot service the request because the media type is unsupported.
12557	The requested file is in a format that the server is configured not to download.	The requested file is in a format that the server is configured not to download.
12558	Verify that the requested file is in a valid format.	Verify that the requested file is in a valid format.
12559	This error occurs when the server cannot service the request because the file type is unsupported.	This error occurs when the server cannot service the request because the file type is unsupported.
12560	12562 The page cannot be displayed because the request range was not satisfiable.	12562 The page cannot be displayed because the request range was not satisfiable.
12563	The requested range of a resource was invalid.	The requested range of a resource was invalid.
12564	Verify that the requested range is valid.	Verify that the requested range is valid.
12565	This error occurs when the requested range is invalid or could not be met by the server.	This error occurs when the requested range is invalid or could not be met by the server.
12566	12568 The page cannot be displayed because the expectation failed.	12568 The page cannot be displayed because the expectation failed.
12569	The client sent an Expect specifier in the HTTP header that the Web server or another server, such as a proxy server, could not process.	The client sent an Expect specifier in the HTTP header that the Web server or another server, such as a proxy server, could not process.
12570	Some proxy servers may not support the "100 continue" expectation. Remove this expectation or try the request without the proxy. Get a network trace and verify that the client is not sending an invalid expectation in the HTTP header when sending to the Web server.	Some proxy servers may not support the "100 continue" expectation. Remove this expectation or try the request without the proxy. Get a network trace and verify that the client is not sending an invalid expectation in the HTTP header when sending to the Web server.
12571	This status code occurs when a server could not meet the expectation specified in the client's request. Some proxy servers may not support the "100 continue" expectation or the client may specify an invalid expectation. You may need to get a network trace or contact the proxy server administrator.	This status code occurs when a server could not meet the expectation specified in the client's request. Some proxy servers may not support the "100 continue" expectation or the client may specify an invalid expectation. You may need to get a network trace or contact the proxy server administrator.
12572	12574 The service is unavailable.	12574 The service is unavailable.
12575	An invalid identity in the application pool could cause this error. The application pool is no longer running because of configuration or reaching application failure limits. The concurrent application request limit was reached.	An invalid identity in the application pool could cause this error. The application pool is no longer running because of configuration or reaching application failure limits. The concurrent application request limit was reached.
12576	Check the event logs and the HTTP error logs for more information.	Check the event logs and the HTTP error logs for more information.
12577	This error occurs when the worker process was unable to start. This could be due to an invalid identity or configuration, or because the concurrent request limit was reached.	This error occurs when the worker process was unable to start. This could be due to an invalid identity or configuration, or because the concurrent request limit was reached.
12578	12580 The page cannot be displayed due to a gateway timeout.	12580 The page cannot be displayed due to a gateway timeout.
12581	A proxy or gateway has timed out waiting for a response.	A proxy or gateway has timed out waiting for a response.
12582	Verify that a proxy or gateway is not responsible for this error. You may need to get a network trace.	Verify that a proxy or gateway is not responsible for this error. You may need to get a network trace.
12583	This error occurs when a proxy or gateway has timed out waiting for a response from another server. It may be necessary to get a network trace to troubleshoot this issue.	This error occurs when a proxy or gateway has timed out waiting for a response from another server. It may be necessary to get a network trace to troubleshoot this issue.
12584	12586 The page cannot be displayed because the HTTP version is not supported.	12586 The page cannot be displayed because the HTTP version is not supported.
12587	The server does not support the HTTP version requested by the client.	The server does not support the HTTP version requested by the client.
12588	Verify that the client is requesting an invalid or unsupported HTTP version.	Verify that the client is requesting an invalid or unsupported HTTP version.
12589	This error occurs when a client is requesting an invalid HTTP version. This can occur if the client is requesting an older, unsupported HTTP version. You can create a network trace to troubleshoot this issue.	This error occurs when a client is requesting an invalid HTTP version. This can occur if the client is requesting an older, unsupported HTTP version. You can create a network trace to troubleshoot this issue.
12590	12592 There is a problem with the resource you are looking for, so it cannot be displayed.	12592 There is a problem with the resource you are looking for, so it cannot be displayed.
12593	The path to the ISAPI Filter is incorrect. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.	The path to the ISAPI Filter is incorrect. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.
12594	Ensure that the path to the ISAPI DLL is correct. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Ensure that the path to the ISAPI DLL is correct. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12598	There is a problem with the resource you are looking for, so it cannot be displayed.	There is a problem with the resource you are looking for, so it cannot be displayed.
12599	The ISAPI Filter has dependencies that are not available on the Web server. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.	The ISAPI Filter has dependencies that are not available on the Web server. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.
12600	Try running Reskit tool "depends" on the ISAPI DLL. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Try running Reskit tool "depends" on the ISAPI DLL. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12604	The page was not displayed because the request entity is too large.	The page was not displayed because the request entity is too large.
12605	The Web server is refusing to service the request because the request entity is too large. The Web server cannot service the request because it is trying to negotiate a client certificate but the request entity is too large. The request URL or the physical mapping to the URL (i.e., the physical file system path to the URL's content) is too long.	The Web server is refusing to service the request because the request entity is too large. The Web server cannot service the request because it is trying to negotiate a client certificate but the request entity is too large. The request URL or the physical mapping to the URL (i.e., the physical file system path to the URL's content) is too long.
12606	Verify that the request is valid. If using client certificates, try: Increasing system.webServer/serverRuntime@uploadReadAheadSize Configure your SSL endpoint to negotiate client certificates as part of the initial SSL handshake. (netsh http add sslcert ... clientcertnegotiation=enable)	Verify that the request is valid. If using client certificates, try: Increasing system.webServer/serverRuntime@uploadReadAheadSize Configure your SSL endpoint to negotiate client certificates as part of the initial SSL handshake. (netsh http add sslcert ... clientcertnegotiation=enable)
12607	This error occurs when the Web server receives a large amount of data from the client. It also occurs if client certificate negotiation occurs while receiving a large request.	This error occurs when the Web server receives a large amount of data from the client. It also occurs if client certificate negotiation occurs while receiving a large request.
12608	12610 There is a problem with the resource you are looking for, so it cannot be displayed.	12610 There is a problem with the resource you are looking for, so it cannot be displayed.
12611	A module is referenced in configuration, but the module has not been installed or the name of the module is misspelled. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.	A module is referenced in configuration, but the module has not been installed or the name of the module is misspelled. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.
12612	Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error. If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error. If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12617	The module could not be found. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.	The module could not be found. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL.
12618	Verify that the module name is not misspelled in the configuration/system.webServer/globalModules config section. The error description may contain additional information to help you determine which module is causing the error. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.	Verify that the module name is not misspelled in the configuration/system.webServer/globalModules config section. The error description may contain additional information to help you determine which module is causing the error. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
12622	A DAV request went to the static file handler.	A DAV request went to the static file handler.
12623	DAV is installed and the <handler> entry is missing. A module set the DAV server-variable.	DAV is installed and the <handler> entry is missing. A module set the DAV server-variable.
12624	Re-install DAV. Try removing any recently installed modules.	Re-install DAV. Try removing any recently installed modules.
12625	DAV marks it's requests with a special server variable. If the static file handler sees the special server variable, it knows it received the request in error.	DAV marks it's requests with a special server variable. If the static file handler sees the special server variable, it knows it received the request in error.
12626	12628 The requested content appears to be script and will not be served by the static file handler.	12628 The requested content appears to be script and will not be served by the static file handler.
12629	The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different handler.	The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different handler.
12630	If you want to serve this content as a static file, add an explicit MIME map.	If you want to serve this content as a static file, add an explicit MIME map.
12631	Sometimes preconditions and a wildcard MIME map can unintentionally cause serving script source.	Sometimes preconditions and a wildcard MIME map can unintentionally cause serving script source.
12632	12634 The specified handler mapping is incorrect.	12634 The specified handler mapping is incorrect.
12635	Managed handler is used; however, ASP.NET is not installed or is not installed completely. There is a typographical error in the configuration for the handler module list. During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.	Managed handler is used; however, ASP.NET is not installed or is not installed completely. There is a typographical error in the configuration for the handler module list. During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.
12636	Install ASP.NET if you are using managed handler. Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule". Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.) As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)	Install ASP.NET if you are using managed handler. Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule". Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.) As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)
12637	IIS core does not recognize the module.	IIS core does not recognize the module.
12638	12640 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.	12640 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
12641	This application defines configuration in the system.web/httpModules section.	This application defines configuration in the system.web/httpModules section.
12642	Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)	Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)
12643	Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and above.	Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and above.
12644	12646 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.	12646 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
12647	This application defines configuration in the system.web/httpHandlers section.	This application defines configuration in the system.web/httpHandlers section.
12648	Migrate the configuration to the system.webServer/handlers section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using appcmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool - for example, appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)	Migrate the configuration to the system.webServer/handlers section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using appcmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool - for example, appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)
12650	12652 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.	12652 An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
12653	system.web/identity@impersonate is set to true.	system.web/identity@impersonate is set to true.
12654	If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Move this application to an application pool using Classic .NET mode - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool" (You can set "Classic .NET AppPool" to the name of another application pool running in Classic managed pipeline mode)	If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Move this application to an application pool using Classic .NET mode - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool" (You can set "Classic .NET AppPool" to the name of another application pool running in Classic managed pipeline mode)
12655	If you are not sure or unable to use the first two options, then it is preferred that you move this application to Classic mode.	If you are not sure or unable to use the first two options, then it is preferred that you move this application to Classic mode.
12656	12658 The serverRuntime@appConcurrentRequestLimit setting is being exceeded.	12658 The serverRuntime@appConcurrentRequestLimit setting is being exceeded.
12659	Setting is too low. The application is taking too long for the current load.	Setting is too low. The application is taking too long for the current load.
12660	Try increasing the value of the setting. Check that external resources (for example, disk, database, etc..) are performing at expected levels. Check that the application has not deadlocked.	Try increasing the value of the setting. Check that external resources (for example, disk, database, etc..) are performing at expected levels. Check that the application has not deadlocked.
12661	IIS will not allow more concurrent requests to an application than the serverRuntime@appConcurrentRequestLimit setting permits.	IIS will not allow more concurrent requests to an application than the serverRuntime@appConcurrentRequestLimit setting permits.
12662	12664 Bad Request	12664 Bad Request
12665
12667	The request could not be understood by the server due to malformed syntax.	The request could not be understood by the server due to malformed syntax.
12670	ASP.NET rejected this request because the queue limit was exceeded.	ASP.NET rejected this request because the queue limit was exceeded.
12671	The queue limit for ASP.NET has been exceeded. (machine.config system.web/processModel@requestQueueLimit)	The queue limit for ASP.NET has been exceeded. (machine.config system.web/processModel@requestQueueLimit)
12673	12674	12674
12676	The FastCGI queue has been exceeded	The FastCGI queue has been exceeded
12677	The system.webServer/fastCgi/application@queueLength setting has been exceeded	The system.webServer/fastCgi/application@queueLength setting has been exceeded
12679	12680	12680
12682	No default document.	No default document.
12683	A default document is not configured for the site. The URL contains a typographical error. Directory browsing is not enabled.	A default document is not configured for the site. The URL contains a typographical error. Directory browsing is not enabled.
12684	Configure a default document for this site. This is commonly default.aspx for ASP.NET and index.php for PHP. Review the browser URL. Enable directory browsing to allow listing the contents of the directory.	Configure a default document for this site. This is commonly default.aspx for ASP.NET and index.php for PHP. Review the browser URL. Enable directory browsing to allow listing the contents of the directory.
12685	A default document is not configured for the site.	A default document is not configured for the site.
12686	12688 The page could not be loaded.	12688 The page could not be loaded.
12689	PHP is not installed. PHP is not enabled for this web site.	PHP is not installed. PHP is not enabled for this web site.
12690	Install PHP and configure handlers correctly. Install and enable PHP for this web site. If you are using WebMatrix, follow these steps to enable PHP: Open the web site in WebMatrix. Select the Site workspace and click on Settings. Check the "Enable PHP" checkbox to install and enable PHP.	Install PHP and configure handlers correctly. Install and enable PHP for this web site. If you are using WebMatrix, follow these steps to enable PHP: Open the web site in WebMatrix. Select the Site workspace and click on Settings. Check the "Enable PHP" checkbox to install and enable PHP.
12691	This error occurs when there is no handler configured to serve the document specified in the URL.	This error occurs when there is no handler configured to serve the document specified in the URL.
12692	12694 The page could not be loaded.	12694 The page could not be loaded.
12695	ASP.NET is not installed. ASP.NET is not configured correctly.	ASP.NET is not installed. ASP.NET is not configured correctly.
12696	Install ASP.NET. If ASP.NET is already installed, make sure that handlers are configured correctly.	Install ASP.NET. If ASP.NET is already installed, make sure that handlers are configured correctly.
12698	12700 The page could not be loaded.	12700 The page could not be loaded.
12701	ASP.NET Web Pages is not installed. ASP.NET Web Pages is not configured correctly.	ASP.NET Web Pages is not installed. ASP.NET Web Pages is not configured correctly.
12702	Install ASP.NET Web Pages. If ASP.NET Web Pages is already installed, make sure that handlers are configured correctly.	Install ASP.NET Web Pages. If ASP.NET Web Pages is already installed, make sure that handlers are configured correctly.
12704	12795 Module "%s" could not be found	12795 Module "%s" could not be found
12796	Often, if SslRequireCert is set at configuration/system.webServer/access@sslFlags, then SslNegotiateCert is intended	Often, if SslRequireCert is set at configuration/system.webServer/access@sslFlags, then SslNegotiateCert is intended
12797	Module "%s" has a bad precondition "%s"	Module "%s" has a bad precondition "%s"
12798	Handler "%s" has a bad precondition "%s"	Handler "%s" has a bad precondition "%s"
12799	Handler "%s" has a bad module "%.*s" in its module list	Handler "%s" has a bad module "%.*s" in its module list
12810	Calling LoadLibraryEx on ISAPI filter "%s" failed	Calling LoadLibraryEx on ISAPI filter "%s" failed
12811	Calling GetProcAddress on ISAPI filter "%s" failed	Calling GetProcAddress on ISAPI filter "%s" failed
12812	Calling GetFilterVersion on ISAPI filter "%s" failed	Calling GetFilterVersion on ISAPI filter "%s" failed
12813	ISAPI filter "%s" tried to register for SF_NOTIFY_READ_RAW_DATA notification	ISAPI filter "%s" tried to register for SF_NOTIFY_READ_RAW_DATA notification
12814	The config for ISAPI filter "%s" has an unrecognized precondition	The config for ISAPI filter "%s" has an unrecognized precondition
12815	Error loading ISAPI filter "%s"	Error loading ISAPI filter "%s"
12834	Tracing area "%s" is not recognized	Tracing area "%s" is not recognized
12835	Tracing provider "%s" is not recognized	Tracing provider "%s" is not recognized
12836	Tracing status "%s" is not recognized	Tracing status "%s" is not recognized
12850	Hidden Segments may not contain a '/' or '\' character	Hidden Segments may not contain a '/' or '\' character
12851	The httpExpires value '%s' is not recognized as a valid date	The httpExpires value '%s' is not recognized as a valid date
12852	The CGI application exceeded the time allowed for processing and the process was terminated. The output from the CGI was "%S".	The CGI application exceeded the time allowed for processing and the process was terminated. The output from the CGI was "%S".
12853	The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "%S".	The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "%S".
12854	Absolute physical path "%s" is not allowed in system.webServer/httpErrors section in web.config file. Use relative path instead.	Absolute physical path "%s" is not allowed in system.webServer/httpErrors section in web.config file. Use relative path instead.
12902	Check the failed request tracing logs for additional information about this error. For more information, click here.	Check the failed request tracing logs for additional information about this error. For more information, click here.
12906	Verify that the username and password are correct, and are not cached by the browser. Use a different username and password. If you are using a custom anonymous account, verify that the password has not expired. Verify that the authenticating user or the user's group, has not been denied login access to the server. Verify that the account was not locked out due to numerous failed login attempts. If you are using authentication and the server is a member of a domain, verify that you have configured the application pool identity using the utility SETSPN.exe, or changed the configuration so that NTLM is the favored authentication type. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify that the username and password are correct, and are not cached by the browser. Use a different username and password. If you are using a custom anonymous account, verify that the password has not expired. Verify that the authenticating user or the user's group, has not been denied login access to the server. Verify that the account was not locked out due to numerous failed login attempts. If you are using authentication and the server is a member of a domain, verify that you have configured the application pool identity using the utility SETSPN.exe, or changed the configuration so that NTLM is the favored authentication type. Check the failed request tracing logs for additional information about this error. For more information, click here.
12908	Verify the authentication setting for the resource and then try requesting the resource using that authentication method. Verify that the client browser supports Integrated authentication. Verify that the request is not going through a proxy when Integrated authentication is used. Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify the authentication setting for the resource and then try requesting the resource using that authentication method. Verify that the client browser supports Integrated authentication. Verify that the request is not going through a proxy when Integrated authentication is used. Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section. Check the failed request tracing logs for additional information about this error. For more information, click here.
12910	Open File Explorer and check the ACLs for the file that is being requested. Make sure that the user accessing the Web site is not being explicitly denied access, and that they do have permission to open the file. Open File Explorer and check the ACLs for the share and the physical path. Ensure that both ACLs allow the user to access the resource. Open File Explorer and check the encryption properties for the file that is being requested. (This setting is located in the Advanced attribute properties dialog.) Check the failed request tracing logs for additional information about this error. For more information, click here.	Open File Explorer and check the ACLs for the file that is being requested. Make sure that the user accessing the Web site is not being explicitly denied access, and that they do have permission to open the file. Open File Explorer and check the ACLs for the share and the physical path. Ensure that both ACLs allow the user to access the resource. Open File Explorer and check the encryption properties for the file that is being requested. (This setting is located in the Advanced attribute properties dialog.) Check the failed request tracing logs for additional information about this error. For more information, click here.
12912	To test this error, remove any filters that are installed for the Web site where access was requested. If the error does not occur after the filters are removed, one of the filters was returning the error. Check the failed request tracing logs for additional information about this error. For more information, click here.	To test this error, remove any filters that are installed for the Web site where access was requested. If the error does not occur after the filters are removed, one of the filters was returning the error. Check the failed request tracing logs for additional information about this error. For more information, click here.
12914	Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request. Check the failed request tracing logs for additional information about this error. For more information, click here.	Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request. Check the failed request tracing logs for additional information about this error. For more information, click here.
12918	Enable scripts to run for the requested resource. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Script Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase. Check the failed request tracing logs for additional information about this error. For more information, click here.	Enable scripts to run for the requested resource. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Script Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase. Check the failed request tracing logs for additional information about this error. For more information, click here.
12920	Enable Read access for the requested resource. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Read Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly. Verify the default document does exist and matches what is specified in the Web site properties. Verify that directory browsing is enabled. Directory browsing needs to be enabled if you want a Web site to show a directory listing (all files in the folder you are accessing). Verify the configuration/system.webServer/handlers/accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Read" is listed as one of the flags. Check the failed request tracing logs for additional information about this error. For more information, click here.	Enable Read access for the requested resource. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Read Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly. Verify the default document does exist and matches what is specified in the Web site properties. Verify that directory browsing is enabled. Directory browsing needs to be enabled if you want a Web site to show a directory listing (all files in the folder you are accessing). Verify the configuration/system.webServer/handlers/accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Read" is listed as one of the flags. Check the failed request tracing logs for additional information about this error. For more information, click here.
12922	Enable Write access for the requested resource. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Write" is listed as one of the flags. Check the failed request tracing logs for additional information about this error. For more information, click here.	Enable Write access for the requested resource. Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Write" is listed as one of the flags. Check the failed request tracing logs for additional information about this error. For more information, click here.
12924	Browse to the URL over a secure channel by using the "https:" prefix instead of "http:". If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting. If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct. Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.	Browse to the URL over a secure channel by using the "https:" prefix instead of "http:". If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting. If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct. Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.
12926	Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions. If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct. Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.	Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions. If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct. Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.
12928	Verify the IP and domain restrictions are configured correctly in the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page. Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.	Verify the IP and domain restrictions are configured correctly in the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page. Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.
12933	Verify the access control lists (ACLs) on the requested file or directory and make sure that the user to whom the client certificate is mapped has access. Check the effective date on the client certificate and ensure that the certificate is valid. Check the expiration date and ensure that the certificate has not expired. Check with the Certificate Authority that provided the certificate to see if your certificate has expired. Verify that the certificate was not explicitly denied access. Ensure that the client certificate is installed properly in the browser. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify the access control lists (ACLs) on the requested file or directory and make sure that the user to whom the client certificate is mapped has access. Check the effective date on the client certificate and ensure that the certificate is valid. Check the expiration date and ensure that the certificate has not expired. Check with the Certificate Authority that provided the certificate to see if your certificate has expired. Verify that the certificate was not explicitly denied access. Ensure that the client certificate is installed properly in the browser. Check the failed request tracing logs for additional information about this error. For more information, click here.
12935	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify the client certificate's validity by contacting the issuer of the client certificate. Check the failed request tracing logs for additional information about this error. For more information, click here.	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify the client certificate's validity by contacting the issuer of the client certificate. Check the failed request tracing logs for additional information about this error. For more information, click here.
12937	If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. Enable directory browsing. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the server level. Run appcmd set config ["SITE_NAME"] /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the site level. Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.	If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. Enable directory browsing. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the server level. Run appcmd set config ["SITE_NAME"] /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the site level. Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.
12939	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify that the client certificate is trusted by the Web server. Verify that the root certificate is properly installed and trusted on the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.	The client may have an old certificate selected for client authentication to this Web site. Close all open client windows, open a new browser window, and then select a valid certificate for client authentication. Verify that the client certificate is trusted by the Web server. Verify that the root certificate is properly installed and trusted on the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.
12941	Verify that the client certificate has not expired. Verify that the client machine's date is set correctly. Obtain a new client certificate. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify that the client certificate has not expired. Verify that the client machine's date is set correctly. Obtain a new client certificate. Check the failed request tracing logs for additional information about this error. For more information, click here.
12943	If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate. If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature. Verify that the application pool for the application exists. Check the failed request tracing log and see if ExecuteURL is being called. For more information, click here.	If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate. If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature. Verify that the application pool for the application exists. Check the failed request tracing log and see if ExecuteURL is being called. For more information, click here.
12946	Create the content on the Web server. Review the browser URL. Check the failed request tracing log and see which module is calling SetStatus. For more information, click here.	Create the content on the Web server. Review the browser URL. Check the failed request tracing log and see which module is calling SetStatus. For more information, click here.
12948	Verify that the Web service extension requested is enabled on the server. To list handlers, go to the IIS Express install directory, and run appcmd list config /section:system.webServer/handlers. Ensure that the configuration for the desired handler is correct. Run appcmd set config /section:system.webServer/handlers /parameters to configure the handler. Check the ISAPI and CGI restriction list. In the IIS Express install directory, run appcmd list config /section:system.webServer/security/isapiCgiRestriction. To change the properties, run appcmd set config /section:system.webServer/security/isapiCgiRestriction /parameters. NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list. Verify that the location of the extension is correct. Verify that the URL for the extension is spelled correctly both in the browser and the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify that the Web service extension requested is enabled on the server. To list handlers, go to the IIS Express install directory, and run appcmd list config /section:system.webServer/handlers. Ensure that the configuration for the desired handler is correct. Run appcmd set config /section:system.webServer/handlers /parameters to configure the handler. Check the ISAPI and CGI restriction list. In the IIS Express install directory, run appcmd list config /section:system.webServer/security/isapiCgiRestriction. To change the properties, run appcmd set config /section:system.webServer/security/isapiCgiRestriction /parameters. NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list. Verify that the location of the extension is correct. Verify that the URL for the extension is spelled correctly both in the browser and the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.
12950	In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. To set a MIME type, run the following command in the IIS Express install directory: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Install ASP.NET. Check the failed request tracing logs for additional information about this error. For more information, click here.	In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. To set a MIME type, run the following command in the IIS Express install directory: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Install ASP.NET. Check the failed request tracing logs for additional information about this error. For more information, click here.
12952	If the file extension does not have a handler associated with it, add a handler mapping for the extension. Verify that the handler associated with the file extension is properly installed and configured. Check the failed request tracing logs for additional information about this error. For more information, click here.	If the file extension does not have a handler associated with it, add a handler mapping for the extension. Verify that the handler associated with the file extension is properly installed and configured. Check the failed request tracing logs for additional information about this error. For more information, click here.
12971	Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site. Check the IIS log file to see which verb is not allowed for the request. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify the list of verbs enabled for the module handler this request was sent to, and ensure that this verb should be allowed for the Web site. Check the IIS log file to see which verb is not allowed for the request. Check the failed request tracing logs for additional information about this error. For more information, click here.
12979	Get a network trace and verify that these headers are correct when sending to the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.	Get a network trace and verify that these headers are correct when sending to the Web server. Check the failed request tracing logs for additional information about this error. For more information, click here.
12986	Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Check the failed request tracing logs for additional information about this error. For more information, click here.	Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Check the failed request tracing logs for additional information about this error. For more information, click here.
12988	Ensure that the path to the ISAPI DLL is correct. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.	Ensure that the path to the ISAPI DLL is correct. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.
12990	Try running Reskit tool "depends" on the ISAPI DLL. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.	Try running Reskit tool "depends" on the ISAPI DLL. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.
12992	Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error. If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error. If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.
12994	Verify that the module name is not misspelled in the configuration/system.webServer/globalModules config section. The error description may contain additional information to help you determine which module is causing the error. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.	Verify that the module name is not misspelled in the configuration/system.webServer/globalModules config section. The error description may contain additional information to help you determine which module is causing the error. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Check the failed request tracing logs for additional information about this error. For more information, click here.
12996	Wait for the worker process to finish shutting down and then try the request again. Manually restart the worker process. If you are using WebMatrix, open the site, and in the ribbon, click "Start". Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.	Wait for the worker process to finish shutting down and then try the request again. Manually restart the worker process. If you are using WebMatrix, open the site, and in the ribbon, click "Start". Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.
12999	Determine which requests are running for the application and whether they are running for an abnormal amount of time. If you are using WebMatrix, open the site. Select the Site workspace, and in the ribbon, click "Requests". Use the IIS Debugging Tools to troubleshoot the issue as a hang.	Determine which requests are running for the application and whether they are running for an abnormal amount of time. If you are using WebMatrix, open the site. Select the Site workspace, and in the ribbon, click "Requests". Use the IIS Debugging Tools to troubleshoot the issue as a hang.
13002	Verify the credentials set for accessing the remote file share. Go to the IIS Express install directory. Run appcmd list config /section:system.applicationHost/sites. Verify that the username and password are correct for the application. Check the security settings and sharing permissions for the remote UNC share hosting the content. If the account used to connect to the content is a local account. Verify that the password is synced on the Web server and the remote file server.	Verify the credentials set for accessing the remote file share. Go to the IIS Express install directory. Run appcmd list config /section:system.applicationHost/sites. Verify that the username and password are correct for the application. Check the security settings and sharing permissions for the remote UNC share hosting the content. If the account used to connect to the content is a local account. Verify that the password is synced on the Web server and the remote file server.
13004	This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.If you see the text "There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined", this error is because you are running a .NET Framework 3.5-based application in .NET Framework 4. If you are running WebMatrix, to resolve this problem, go to the Settings node to set the .NET Framework version to ".NET 2". You can also remove the extra sections from the web.config file.	This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.If you see the text "There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined", this error is because you are running a .NET Framework 3.5-based application in .NET Framework 4. If you are running WebMatrix, to resolve this problem, go to the Settings node to set the .NET Framework version to ".NET 2". You can also remove the extra sections from the web.config file.
13007	Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line. For example, from the IIS Express install directory, run appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode. It will continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool". Only do this if you are unable to migrate your application.	Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line. For example, from the IIS Express install directory, run appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode. It will continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool". Only do this if you are unable to migrate your application.
13009	Migrate the configuration to the system.webServer/handlers section. You can do so manually or by using AppCmd from the command line. For example, from the IIS Express install directory, run appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode. It will continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool". Only do this if you are unable to migrate your application.	Migrate the configuration to the system.webServer/handlers section. You can do so manually or by using AppCmd from the command line. For example, from the IIS Express install directory, run appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode. It will continue to work in Classic mode and on previous versions of IIS. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool". Only do this if you are unable to migrate your application.
13011	If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.	If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
13013	Look in the IIS log file for additional information on the failure. Check the failed request tracing logs for additional information about this error. For more information, click here.	Look in the IIS log file for additional information on the failure. Check the failed request tracing logs for additional information about this error. For more information, click here.
13015	If the server should allow the "TRACE" method, create a new DWORD registry parameter named "EnableTraceMethod" and set its value to 1 at the following location in the registry.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters Check the failed request tracing logs for additional information about this error. For more information, click here.	If the server should allow the "TRACE" method, create a new DWORD registry parameter named "EnableTraceMethod" and set its value to 1 at the following location in the registry.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters Check the failed request tracing logs for additional information about this error. For more information, click here.
13018	Verify the configured timeout for the CGI application. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/cgi /timeout:time The 'time' property should be in the format hh:mm:ss. Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.	Verify the configured timeout for the CGI application. Go to the IIS Express install directory. Run appcmd set config /section:system.webServer/cgi /timeout:time The 'time' property should be in the format hh:mm:ss. Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.
20001	Web Management Service	Web Management Service
20002	The Web Management Service enables remote and delegated management capabilities for administrators to manage for the Web server, sites and applications present on this machine.	The Web Management Service enables remote and delegated management capabilities for administrators to manage for the Web server, sites and applications present on this machine.
20100	Internet Information Services (IIS) Manager	Internet Information Services (IIS) Manager
20101	The IIS Manager allows you to manage the Web Application Server.	The IIS Manager allows you to manage the Web Application Server.
20102	10.0.0.0	10.0.0.0
25001	Usage: %ws -s | -h [application host file] -w -in -%ws This option launches a worker process using the default application host config file. By default, it will use site id 1. -s Optional parameter to use a siteinformation from the provided site id. or -h [Application host config filename] Launches a worker process using the specified application host config file. -in Optional instance name to use. Defaults to 'HWC-' -w Optional root web config file to use.	Usage: %ws -s | -h [application host file] -w -in -%ws This option launches a worker process using the default application host config file. By default, it will use site id 1. -s Optional parameter to use a siteinformation from the provided site id. or -h [Application host config filename] Launches a worker process using the specified application host config file. -in Optional instance name to use. Defaults to 'HWC-' -w Optional root web config file to use.
25002	Press 'Q' to shutdown the process:	Press 'Q' to shutdown the process:
25003	Shutting down the process.	Shutting down the process.
25004	ERROR: The specified site has applications mapped to more than one application pool. Please configure all applications to a single application pool or delete those applications from this site.	ERROR: The specified site has applications mapped to more than one application pool. Please configure all applications to a single application pool or delete those applications from this site.
25005	ERROR: There was an error reading the configuration. Please check that the configuration file is exists, is accessible and contains valid configuration.	ERROR: There was an error reading the configuration. Please check that the configuration file is exists, is accessible and contains valid configuration.
25006	ERROR: The specified site could not be found or there are no sites configured. Please check that that configuration file contains at least one site and/or the specified site id is correct.	ERROR: The specified site could not be found or there are no sites configured. Please check that that configuration file contains at least one site and/or the specified site id is correct.
25007	ERROR: There are too many application pools defined in the given configuration file. Please ensure that the configuration file contains only one application pool configuration.	ERROR: There are too many application pools defined in the given configuration file. Please ensure that the configuration file contains only one application pool configuration.
25008	ERROR: There was an error processing one of the parameters. Please ensure that all parameters are correct and valid.	ERROR: There was an error processing one of the parameters. Please ensure that all parameters are correct and valid.
25009	ERROR: There has been an error during processing of this command. Please check the event log and see if any errors or warnings have been logged.	ERROR: There has been an error during processing of this command. Please check the event log and see if any errors or warnings have been logged.
30001	Windows Process Activation Service	Windows Process Activation Service
30002	The Windows Process Activation Service (WAS) provides process activation, resource management and health management services for message-activated applications.	The Windows Process Activation Service (WAS) provides process activation, resource management and health management services for message-activated applications.
30003	World Wide Web Publishing Service	World Wide Web Publishing Service
30004	Provides Web connectivity and administration through the Internet Information Services Manager	Provides Web connectivity and administration through the Internet Information Services Manager
30005	FTP Publishing Service	FTP Publishing Service
30006	Enables this server to be a File Transfer Protocol (FTP) server. If this service is stopped, the server cannot function as an FTP server. If this service is disabled, any services that explicitly depend on it will fail to start.	Enables this server to be a File Transfer Protocol (FTP) server. If this service is stopped, the server cannot function as an FTP server. If this service is disabled, any services that explicitly depend on it will fail to start.
30007	IIS Admin Service	IIS Admin Service
30008	Enables this server to administer the IIS metabase. The IIS metabase stores configuration for the SMTP and FTP services. If this service is stopped, the server will be unable to configure SMTP or FTP. If this service is disabled, any services that explicitly depend on it will fail to start.	Enables this server to administer the IIS metabase. The IIS metabase stores configuration for the SMTP and FTP services. If this service is stopped, the server will be unable to configure SMTP or FTP. If this service is disabled, any services that explicitly depend on it will fail to start.
30009	ASP.NET State Service	ASP.NET State Service
30010	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.	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.
30011	Application Host Helper Service	Application Host Helper Service
30012	Provides administrative services for IIS, for example configuration history and Application Pool account mapping. If this service is stopped, configuration history and locking down files or directories with Application Pool specific Access Control Entries will not work.	Provides administrative services for IIS, for example configuration history and Application Pool account mapping. If this service is stopped, configuration history and locking down files or directories with Application Pool specific Access Control Entries will not work.
30013	Web Hosting	Web Hosting
30014	W3C Logging Service	W3C Logging Service
30015	Provides W3C logging for Internet Information Services (IIS). If this service is stopped, W3C logging configured by IIS will not work.	Provides W3C logging for Internet Information Services (IIS). If this service is stopped, W3C logging configured by IIS will not work.
30500	World Wide Web Services (HTTP Traffic-In)	World Wide Web Services (HTTP Traffic-In)
30501	World Wide Web Services (HTTP)	World Wide Web Services (HTTP)
30502	World Wide Web Services (HTTPS Traffic-In)	World Wide Web Services (HTTPS Traffic-In)
30503	Secure World Wide Web Services (HTTPS)	Secure World Wide Web Services (HTTPS)
30504	FTP Server (FTP Traffic-In)	FTP Server (FTP Traffic-In)
30505	FTP Server	FTP Server
30506	Web Management Service (HTTP Traffic-In)	Web Management Service (HTTP Traffic-In)
30507	Web Management Service (HTTP)	Web Management Service (HTTP)
30510	An inbound rule to allow HTTP traffic for Internet Information Services (IIS) [TCP 80]	An inbound rule to allow HTTP traffic for Internet Information Services (IIS) [TCP 80]
30512	An inbound rule to allow HTTPS traffic for Internet Information Services (IIS) [TCP 443]	An inbound rule to allow HTTPS traffic for Internet Information Services (IIS) [TCP 443]
30514	An inbound rule to allow FTP traffic for Internet Information Services (IIS) [TCP 21]	An inbound rule to allow FTP traffic for Internet Information Services (IIS) [TCP 21]
30516	An inbound rule to allow Web Management Service traffic for Internet Information Services (IIS) [TCP 8172]	An inbound rule to allow Web Management Service traffic for Internet Information Services (IIS) [TCP 8172]
30517	FTP Server Secure (FTP SSL Traffic-In)	FTP Server Secure (FTP SSL Traffic-In)
30518	An inbound rule to allow FTP over SSL traffic for Internet Information Services (IIS) [TCP 990]	An inbound rule to allow FTP over SSL traffic for Internet Information Services (IIS) [TCP 990]
30519	FTP Server Secure (FTP SSL Traffic-Out)	FTP Server Secure (FTP SSL Traffic-Out)
30520	An outbound rule to allow FTP over SSL traffic for Internet Information Services (IIS) [TCP 989]	An outbound rule to allow FTP over SSL traffic for Internet Information Services (IIS) [TCP 989]
30521	FTP Server (FTP Traffic-Out)	FTP Server (FTP Traffic-Out)
30522	An outbound rule to allow FTP traffic for Internet Information Services (IIS) [TCP 20]	An outbound rule to allow FTP traffic for Internet Information Services (IIS) [TCP 20]
30523	FTP Server Passive (FTP Passive Traffic-In)	FTP Server Passive (FTP Passive Traffic-In)
30524	An inbound rule to allow Passive FTP traffic for Internet Information Services (IIS) [TCP 1023]	An inbound rule to allow Passive FTP traffic for Internet Information Services (IIS) [TCP 1023]
40001	Failed to initialize configuration system.	Failed to initialize configuration system.
40002	Failed to create configuration system.	Failed to create configuration system.
40003	Cannot find factory qualifier on class %s.	Cannot find factory qualifier on class %s.
40004	Cannot cocreate factory for class %s.	Cannot cocreate factory for class %s.
40005	Cannot get access to the process runtime data.	Cannot get access to the process runtime data.
40006	Failed to impersonate client.	Failed to impersonate client.
40007	Mandatory input parameter is missing: %s.	Mandatory input parameter is missing: %s.
40008	Cannot obtain mandatory input parameter: %s.	Cannot obtain mandatory input parameter: %s.
40009	Unsupported input parameter format: %s.	Unsupported input parameter format: %s.
40010	Object instance properties are not loaded: %s.	Object instance properties are not loaded: %s.
40011	%s: failed to load property %s.	%s: failed to load property %s.
40012	HTTP request runtime data is not available.	HTTP request runtime data is not available.
40013	Failed to enumerate appdomains.	Failed to enumerate appdomains.
40014	Failed to unload appdomain %s.	Failed to unload appdomain %s.
40016	Failed to enumerate server SSL certificate information.	Failed to enumerate server SSL certificate information.
40017	Failed to convert parameter %s.	Failed to convert parameter %s.
40018	Failed to store SSL certificate information.	Failed to store SSL certificate information.
40019	Failed to delete SSL certificate information.	Failed to delete SSL certificate information.
40020	Cannot find section path qualifier on class %s.	Cannot find section path qualifier on class %s.
40021	Failed to create configuration for path %s.	Failed to create configuration for path %s.
40022	Failed to get section %s for path %s.	Failed to get section %s for path %s.
40023	Cannot get default collection for section %s.	Cannot get default collection for section %s.
40024	Cannot get collection count.	Cannot get collection count.
40025	Cannot get collection element.	Cannot get collection element.
40026	Cannot get schema for configuration element %s.	Cannot get schema for configuration element %s.
40027	Cannot get property %s for configuration element %s.	Cannot get property %s for configuration element %s.
40028	Cannot get element name.	Cannot get element name.
40029	Object %s already exists.	Object %s already exists.
40030	Failed to create collection element.	Failed to create collection element.
40031	Cannot get default collection from element %s.	Cannot get default collection from element %s.
40032	Failed to add collection element.	Failed to add collection element.
40033	Object %s cannot be found.	Object %s cannot be found.
40034	Cannot get access to the site runtime data.	Cannot get access to the site runtime data.
40035	Failed to get site runtime status.	Failed to get site runtime status.
40036	Failed to start site.	Failed to start site.
40037	Failed to stop site.	Failed to stop site.
40038	Failed to delete %s.	Failed to delete %s.
40039	Cannot get access to the application pool runtime data.	Cannot get access to the application pool runtime data.
40040	Failed to get application pool runtime status.	Failed to get application pool runtime status.
40041	Failed to start application pool.	Failed to start application pool.
40042	Failed to stop application pool.	Failed to stop application pool.
40043	Failed to recycle application pool.	Failed to recycle application pool.
40044	Cannot call method on abstract CIM class.	Cannot call method on abstract CIM class.
40045	Cannot change configuration path between calls to BeginUpdateBatch and EndUpdateBatch.	Cannot change configuration path between calls to BeginUpdateBatch and EndUpdateBatch.
40501	This feature provides a web server that will handle HTTP traffic.	This feature provides a web server that will handle HTTP traffic.
40503	This feature provides a web server that will handle HTTPS traffic.	This feature provides a web server that will handle HTTPS traffic.
40505	This feature provides an FTP server for file transfers via the FTP protocol.	This feature provides an FTP server for file transfers via the FTP protocol.
40507	This feature provides a web management service that will handle HTTP traffic for remote Internet Information Services (IIS) management.	This feature provides a web management service that will handle HTTP traffic for remote Internet Information Services (IIS) management.
50000	WAS_W3WP	WAS_W3WP
50002	This counter set exposes Windows Process Activation Service (WAS) related counters for the worker process.	This counter set exposes Windows Process Activation Service (WAS) related counters for the worker process.
50004	Total Requests Served	Total Requests Served
50006	Total number of requests served by the worker process. This counter is only meaningful when request based recycling is enabled for the application pool.	Total number of requests served by the worker process. This counter is only meaningful when request based recycling is enabled for the application pool.
50008	Total Health Pings.	Total Health Pings.
50010	Total number of health pings received by the process.	Total number of health pings received by the process.
50012	Total Runtime Status Queries	Total Runtime Status Queries
50014	Total number of Runtime Status queries received by the process.	Total number of Runtime Status queries received by the process.
50016	Active Listener Channels	Active Listener Channels
50018	Number of currently active listener channels in the worker process.	Number of currently active listener channels in the worker process.
50020	Active Protocol Handlers	Active Protocol Handlers
50022	Number of currently active protocol handlers in the worker process.	Number of currently active protocol handlers in the worker process.
50024	Total WAS Messages Received	Total WAS Messages Received
50026	Total number of messages received by the worker process from Windows Process Activation Service (WAS).	Total number of messages received by the worker process from Windows Process Activation Service (WAS).
50028	Total Messages Sent to WAS	Total Messages Sent to WAS
50030	Total number of messages sent to Windows Process Activation Service (WAS) by the worker process.	Total number of messages sent to Windows Process Activation Service (WAS) by the worker process.
50032	Health Ping Reply Latency	Health Ping Reply Latency
50034	Time, in 100 nanosecond increments, taken by worker process to reply to last health ping.	Time, in 100 nanosecond increments, taken by worker process to reply to last health ping.
50500	W3SVC_W3WP	W3SVC_W3WP
50502	This counter set exposes HTTP request processing related counters for the worker process.	This counter set exposes HTTP request processing related counters for the worker process.
50504	Total HTTP Requests Served	Total HTTP Requests Served
50506	Total number of HTTP requests served by the worker process.	Total number of HTTP requests served by the worker process.
50508	Requests / Sec	Requests / Sec
50510	HTTP requests/sec being processed by the worker process.	HTTP requests/sec being processed by the worker process.
50512	Active Requests	Active Requests
50514	Current number of requests being processed by the worker process.	Current number of requests being processed by the worker process.
50516	Total Threads	Total Threads
50518	Total number of threads available to process requests in the worker process.	Total number of threads available to process requests in the worker process.
50520	Active Threads Count	Active Threads Count
50522	Number of threads actively processing requests in the worker process.	Number of threads actively processing requests in the worker process.
50524	Maximum Threads Count	Maximum Threads Count
50526	Maximum number of threads to which the thread pool can grow as needed.	Maximum number of threads to which the thread pool can grow as needed.
50528	Current File Cache Memory Usage	Current File Cache Memory Usage
50530	Current number of bytes used by user-mode file cache.	Current number of bytes used by user-mode file cache.
50532	Maximum File Cache Memory Usage	Maximum File Cache Memory Usage
50534	Maximum number of bytes used by user-mode file cache.	Maximum number of bytes used by user-mode file cache.
50536	Output Cache Current Memory Usage	Output Cache Current Memory Usage
50538	Current number of bytes used by output cache.	Current number of bytes used by output cache.
50540	Current Files Cached	Current Files Cached
50542	Current number of files whose contents are present in user-mode cache.	Current number of files whose contents are present in user-mode cache.
50544	Total Files Cached	Total Files Cached
50546	Total number of files whose contents were ever added to the user-mode cache (since service startup).	Total number of files whose contents were ever added to the user-mode cache (since service startup).
50548	File Cache Hits	File Cache Hits
50550	Total number of successful lookups in the user-mode file cache (since service startup).	Total number of successful lookups in the user-mode file cache (since service startup).
50552	File Cache Misses	File Cache Misses
50554	Total number of unsuccessful lookups in the user-mode file cache (since service startup).	Total number of unsuccessful lookups in the user-mode file cache (since service startup).
50556	File Cache Flushes	File Cache Flushes
50558	Total number of files removed from the user-mode cache (since service startup).	Total number of files removed from the user-mode cache (since service startup).
50560	Active Flushed Entries	Active Flushed Entries
50562	Number of file handles cached in user-mode that will be closed when all current transfers complete.	Number of file handles cached in user-mode that will be closed when all current transfers complete.
50564	Total Flushed Files	Total Flushed Files
50566	Total number of file handles that have been removed from the user-mode cache (since service startup).	Total number of file handles that have been removed from the user-mode cache (since service startup).
50568	Current URIs Cached	Current URIs Cached
50570	URI information blocks currently in the user-mode cache.	URI information blocks currently in the user-mode cache.
50572	Total URIs Cached	Total URIs Cached
50574	Total number of URI information blocks added to the user-mode cache (since service startup).	Total number of URI information blocks added to the user-mode cache (since service startup).
50576	URI Cache Hits	URI Cache Hits
50578	Total number of successful lookups in the user-mode URI cache (since service startup).	Total number of successful lookups in the user-mode URI cache (since service startup).
50580	URI Cache Misses	URI Cache Misses
50582	Total number of unsuccessful lookups in the user-mode URI cache (since service startup).	Total number of unsuccessful lookups in the user-mode URI cache (since service startup).
50584	URI Cache Flushes	URI Cache Flushes
50586	Total number of URI cache flushes (since service startup).	Total number of URI cache flushes (since service startup).
50588	Total Flushed URIs	Total Flushed URIs
50590	The number of URI information blocks that have been removed from the user-mode cache (since service startup).	The number of URI information blocks that have been removed from the user-mode cache (since service startup).
50592	Current Metadata Cached	Current Metadata Cached
50594	Number of metadata information blocks currently present in user-mode cache.	Number of metadata information blocks currently present in user-mode cache.
50596	Total Metadata Cached	Total Metadata Cached
50598	Total number of metadata information blocks added to the user-mode cache (since service startup).	Total number of metadata information blocks added to the user-mode cache (since service startup).
50600	Metadata Cache Hits	Metadata Cache Hits
50602	Total number of successful lookups in the user-mode metadata cache (since service startup).	Total number of successful lookups in the user-mode metadata cache (since service startup).
50604	Metadata Cache Misses	Metadata Cache Misses
50606	Total number of unsuccessful lookups in the user-mode metadata cache (since service startup).	Total number of unsuccessful lookups in the user-mode metadata cache (since service startup).
50608	Metadata Cache Flushes	Metadata Cache Flushes
50610	Total number of user-mode metadata cache flushes (since service startup).	Total number of user-mode metadata cache flushes (since service startup).
50612	Total Flushed Metadata	Total Flushed Metadata
50614	Total number of metadata information blocks removed from the user-mode cache (since service startup).	Total number of metadata information blocks removed from the user-mode cache (since service startup).
50616	Output Cache Current Items	Output Cache Current Items
50618	Number of items current present in output cache.	Number of items current present in output cache.
50620	Output Cache Total Hits	Output Cache Total Hits
50622	Total number of successful lookups in output cache (since service startup).	Total number of successful lookups in output cache (since service startup).
50624	Output Cache Total Misses	Output Cache Total Misses
50626	Total number of unsuccessful lookups in output cache (since service startup).	Total number of unsuccessful lookups in output cache (since service startup).
50628	Output Cache Total Flushes	Output Cache Total Flushes
50630	Total number of flushes of output cache (since service startup).	Total number of flushes of output cache (since service startup).
50632	Output Cache Current Flushed Items	Output Cache Current Flushed Items
50634	Number of items that have been flushed from output cache but are still being used by outgoing responses so are still taking up memory.	Number of items that have been flushed from output cache but are still being used by outgoing responses so are still taking up memory.
50636	Output Cache Total Flushed Items	Output Cache Total Flushed Items
50638	Total number of items flushed from output cache (since service startup).	Total number of items flushed from output cache (since service startup).
50640	File Cache Hits / sec	File Cache Hits / sec
50642	Rate of successful lookups in file cache during last sample interval.	Rate of successful lookups in file cache during last sample interval.
50644	Metadata Cache Hits / sec	Metadata Cache Hits / sec
50646	Rate of successful lookups in metadata cache during last sample interval.	Rate of successful lookups in metadata cache during last sample interval.
50648	Output Cache Hits / sec	Output Cache Hits / sec
50650	Rate of successful lookups in output cache during last sample interval.	Rate of successful lookups in output cache during last sample interval.
50652	Uri Cache Hits / sec	Uri Cache Hits / sec
50654	Rate of successful lookups in URI cache during last sample interval.	Rate of successful lookups in URI cache during last sample interval.
50656	File Cache Misses / sec	File Cache Misses / sec
50658	Rate of unsuccessful lookups in file cache during last sample interval.	Rate of unsuccessful lookups in file cache during last sample interval.
50660	Metadata Cache Misses / sec	Metadata Cache Misses / sec
50662	Rate of unsuccessful lookups in metadata cache during last sample interval.	Rate of unsuccessful lookups in metadata cache during last sample interval.
50664	Output Cache Misses / sec	Output Cache Misses / sec
50666	Rate of unsuccessful lookups in output cache during last sample interval.	Rate of unsuccessful lookups in output cache during last sample interval.
50668	Uri Cache Misses / sec	Uri Cache Misses / sec
50670	Rate of unsuccessful lookups in URI cache during last sample interval.	Rate of unsuccessful lookups in URI cache during last sample interval.
50672	% 401 HTTP Response Sent	% 401 HTTP Response Sent
50674	Percentage of 401 HTTP response sent by the worker process.	Percentage of 401 HTTP response sent by the worker process.
50676	% 403 HTTP Response Sent	% 403 HTTP Response Sent
50678	Percentage of 403 HTTP response sent by the worker process.	Percentage of 403 HTTP response sent by the worker process.
50680	% 404 HTTP Response Sent	% 404 HTTP Response Sent
50682	Percentage of 404 HTTP response sent by the worker process.	Percentage of 404 HTTP response sent by the worker process.
50684	% 500 HTTP Response Sent	% 500 HTTP Response Sent
50686	Percentage of 500 HTTP response sent by the worker process.	Percentage of 500 HTTP response sent by the worker process.
50688	WebSocket Active Requests	WebSocket Active Requests
50690	WebSocket requests currently being processed by the worker process.	WebSocket requests currently being processed by the worker process.
50692	WebSocket Connection Attempts / Sec	WebSocket Connection Attempts / Sec
50694	WebSocket connection attempts/sec being processed by the worker process.	WebSocket connection attempts/sec being processed by the worker process.
50696	WebSocket Connections Rejected / Sec	WebSocket Connections Rejected / Sec
50698	WebSocket connections rejected/sec by the worker process.	WebSocket connections rejected/sec by the worker process.
50700	WebSocket Connections Accepted / Sec	WebSocket Connections Accepted / Sec
50702	WebSocket connections accepted/sec by the worker process.	WebSocket connections accepted/sec by the worker process.
51000	APP_POOL_WAS	APP_POOL_WAS
51002	This counter set exposes WAS related counters for IIS Application Pools.	This counter set exposes WAS related counters for IIS Application Pools.
51004	Current Worker Processes	Current Worker Processes
51006	The current number of worker processes that are running in the application pool.	The current number of worker processes that are running in the application pool.
51008	Maximum Worker Processes	Maximum Worker Processes
51010	The maximum number of worker processes that have been created for the application pool since Windows Process Activation Service (WAS) started.	The maximum number of worker processes that have been created for the application pool since Windows Process Activation Service (WAS) started.
51012	Total Application Pool Recycles	Total Application Pool Recycles
51014	The number of times that the application pool has been recycled since Windows Process Activation Service (WAS) started.	The number of times that the application pool has been recycled since Windows Process Activation Service (WAS) started.
51016	Current Application Pool Uptime	Current Application Pool Uptime
51018	The length of time, in seconds, that the application pool has been running since it was started.	The length of time, in seconds, that the application pool has been running since it was started.
51020	Total Application Pool Uptime	Total Application Pool Uptime
51022	The length of time, in seconds, that the application pool has been running since Windows Process Activation Service (WAS) started.	The length of time, in seconds, that the application pool has been running since Windows Process Activation Service (WAS) started.
51024	Recent Worker Process Failures	Recent Worker Process Failures
51026	The number of times that worker processes for the application pool failed during the rapid-fail protection interval.	The number of times that worker processes for the application pool failed during the rapid-fail protection interval.
51028	Total Worker Process Failures	Total Worker Process Failures
51030	The number of times that worker processes have crashed since the application pool was started.	The number of times that worker processes have crashed since the application pool was started.
51032	Current Application Pool State	Current Application Pool State
51034	The current status of the application pool (1 - Uninitialized, 2 - Initialized, 3 - Running, 4 - Disabling, 5 - Disabled, 6 - Shutdown Pending, 7 - Delete Pending).	The current status of the application pool (1 - Uninitialized, 2 - Initialized, 3 - Running, 4 - Disabling, 5 - Disabled, 6 - Shutdown Pending, 7 - Delete Pending).
51036	Total Worker Process Startup Failures	Total Worker Process Startup Failures
51038	The number of times that Windows Process Activation Service (WAS) failed to start a worker process.	The number of times that Windows Process Activation Service (WAS) failed to start a worker process.
51040	Total Worker Process Shutdown Failures	Total Worker Process Shutdown Failures
51042	The number of times that Windows Process Activation Service (WAS) failed to shut down a worker process.	The number of times that Windows Process Activation Service (WAS) failed to shut down a worker process.
51044	Total Worker Process Ping Failures	Total Worker Process Ping Failures
51046	The number of times that Windows Process Activation Service (WAS) did not receive a response to ping messages sent to a worker process.	The number of times that Windows Process Activation Service (WAS) did not receive a response to ping messages sent to a worker process.
51048	Time Since Last Worker Process Failure	Time Since Last Worker Process Failure
51050	The length of time, in seconds, since the last worker process failure occurred for the application pool.	The length of time, in seconds, since the last worker process failure occurred for the application pool.
51052	Total Worker Processes Created	Total Worker Processes Created
51054	The number of worker processes created for the application pool since Windows Process Activation Service (WAS) started.	The number of worker processes created for the application pool since Windows Process Activation Service (WAS) started.
0xC1D	IISRESET.EXE (c) Microsoft Corp. 1998-2005%n%nUsage:%niisreset [computername]%n /RESTART Stop and then restart all Internet services. /START Start all Internet services. /STOP Stop all Internet services. /REBOOT Reboot the computer. /REBOOTONERROR Reboot the computer if an error occurs when starting, stopping, or restarting Internet services. /NOFORCE Do not forcefully terminate Internet services if attempting to stop them gracefully fails. /TIMEOUT:val Specify the timeout value ( in seconds ) to wait for a successful stop of Internet services. On expiration of this timeout the computer can be rebooted if the /REBOOTONERROR parameter is specified. The default value is 20s for restart, 60s for stop, and 0s for reboot. /STATUS Display the status of all Internet services. /ENABLE Enable restarting of Internet Services on the local system. /DISABLE Disable restarting of Internet Services on the local system.	IISRESET.EXE (c) Microsoft Corp. 1998-2005%n%nUsage:%niisreset [computername]%n /RESTART Stop and then restart all Internet services. /START Start all Internet services. /STOP Stop all Internet services. /REBOOT Reboot the computer. /REBOOTONERROR Reboot the computer if an error occurs when starting, stopping, or restarting Internet services. /NOFORCE Do not forcefully terminate Internet services if attempting to stop them gracefully fails. /TIMEOUT:val Specify the timeout value ( in seconds ) to wait for a successful stop of Internet services. On expiration of this timeout the computer can be rebooted if the /REBOOTONERROR parameter is specified. The default value is 20s for restart, 60s for stop, and 0s for reboot. /STATUS Display the status of all Internet services. /ENABLE Enable restarting of Internet Services on the local system. /DISABLE Disable restarting of Internet Services on the local system.
0xC1E	Status for %1 ( %2 ) : %3	Status for %1 ( %2 ) : %3
0xC1F	Stopped	Stopped
0xC20	Stop pending	Stop pending
0xC21	Running	Running
0xC22	Continue pending	Continue pending
0xC23	Pause pending	Pause pending
0xC24	Paused	Paused
0xC26	Start pending	Start pending
0xC27	Internet services successfully started	Internet services successfully started
0xC28	Internet services successfully stopped	Internet services successfully stopped
0xC29	Rebooting !	Rebooting !
0xC2A	Internet services successfully restarted	Internet services successfully restarted
0xC2B	Error processing command, attempting to reboot the server.	Error processing command, attempting to reboot the server.
0xC2C	Access to IIS restart API disabled to this computer	Access to IIS restart API disabled to this computer
0xC2D	Restarting of Internet Services has been enabled.	Restarting of Internet Services has been enabled.
0xC2E	Restarting of Internet Services has been disabled.	Restarting of Internet Services has been disabled.
0xC2F	Internet services successfully killed	Internet services successfully killed
0xC30	Attempting kill...	Attempting kill...
0xC31	Access denied, you must be an administrator of the remote computer to use thiscommand. Either have your account added to the administrator local group ofthe remote computer or to the domain administrator global group.	Access denied, you must be an administrator of the remote computer to use thiscommand. Either have your account added to the administrator local group ofthe remote computer or to the domain administrator global group.
0xC32	Start attempt failed.	Start attempt failed.
0xC33	Stop attempt failed.	Stop attempt failed.
0xC34	Restart attempt failed.	Restart attempt failed.
0xC35	Reboot attempt failed.	Reboot attempt failed.
0xC36	Kill attempt failed.	Kill attempt failed.
0xC37	Attempting start...	Attempting start...
0xC38	Attempting stop...	Attempting stop...
0xC39	Attempting reboot...	Attempting reboot...
0xC3A	The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.	The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.
0xFA0	General purpose IIS command line administration tool.APPCMD (command) (object-type) Supported object types:	General purpose IIS command line administration tool.APPCMD (command) (object-type) Supported object types:
0xFA1	(To list commands supported by each object use /?, e.g. 'appcmd.exe site /?')General parameters:/? Display context-sensitive help message./text Generate output in text format (default). /text:* shows all object properties in detail view. /text: shows the value of the specified attribute for each object./xml Generate output in XML format. Use this to produce output that can be sent to another command running in /in mode./in or - Read and operate on XML input from standard input. Use this to operate on input produced by another command running in /xml mode./config Show configuration for displayed objects. /config:* also includes inherited configuration./metadata Show configuration metadata when displaying configuration./commit Set config path where configuration changes are saved. Can specify either a specific configuration path, \"site\", \"app\", \"parent\", or \"url\" to save to the appropriate portion of the path being edited by the command, \"apphost\", \"webroot\", or \"machine\" for the corresponding configuration level./apphostconfig Specify an alternate applicationHost.config file to edit./debug Show debugging information for command execution.Use \"!\" to escape parameters that have same names as the general parameters,like \"/!debug:value\" to set a config property named \"debug\".	(To list commands supported by each object use /?, e.g. 'appcmd.exe site /?')General parameters:/? Display context-sensitive help message./text Generate output in text format (default). /text:* shows all object properties in detail view. /text: shows the value of the specified attribute for each object./xml Generate output in XML format. Use this to produce output that can be sent to another command running in /in mode./in or - Read and operate on XML input from standard input. Use this to operate on input produced by another command running in /xml mode./config Show configuration for displayed objects. /config:* also includes inherited configuration./metadata Show configuration metadata when displaying configuration./commit Set config path where configuration changes are saved. Can specify either a specific configuration path, \"site\", \"app\", \"parent\", or \"url\" to save to the appropriate portion of the path being edited by the command, \"apphost\", \"webroot\", or \"machine\" for the corresponding configuration level./apphostconfig Specify an alternate applicationHost.config file to edit./debug Show debugging information for command execution.Use \"!\" to escape parameters that have same names as the general parameters,like \"/!debug:value\" to set a config property named \"debug\".
0xFA2	%wsAPPCMD (command) %ws Supported commands:	%wsAPPCMD (command) %ws Supported commands:
0xFA3	(To get help for each command use /?, e.g. 'appcmd.exe add site /?'.)	(To get help for each command use /?, e.g. 'appcmd.exe add site /?'.)
0xFA4	APPCMD %ws %ws	APPCMD %ws %ws
0xFA5	Supported parameters:	Supported parameters:
0xFA6	Examples:	Examples:
0x1194	Metabase Add Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Add Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x1195	Metabase Delete Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Delete Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x1196	Metabase Delete Child Keys.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Delete Child Keys.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x1197	Metabase Copy Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n	Metabase Copy Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n
0x1198	Metabase Rename Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n New Key Name: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n	Metabase Rename Key.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n New Key Name: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n
0x1199	Metabase Set Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Property ID: %5%n Property Name: %6%n Old Value: %7%n New Value: %8%n Caller PID: %9%n Caller Image Path: %10%n Result: %11%n	Metabase Set Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Property ID: %5%n Property Name: %6%n Old Value: %7%n New Value: %8%n Caller PID: %9%n Caller Image Path: %10%n Result: %11%n
0x119A	Metabase Delete Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Property ID: %5%n Property Name: %6%n Old Value: %7%n Caller PID: %8%n Caller Image Path: %9%n Result: %10%n	Metabase Delete Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Property ID: %5%n Property Name: %6%n Old Value: %7%n Caller PID: %8%n Caller Image Path: %9%n Result: %10%n
0x119B	Metabase Delete All Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Delete All Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x119C	Metabase Copy Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n	Metabase Copy Data.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Caller PID: %6%n Caller Image Path: %7%n Result: %8%n
0x119D	Metabase Set Last Change Time.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Set Last Change Time.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Path: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x119E	Metabase Restore.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Name of Backup: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Restore.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Name of Backup: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x119F	Metabase Delete Backup.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Name of Backup: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n	Metabase Delete Backup.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Name of Backup: %4%n Caller PID: %5%n Caller Image Path: %6%n Result: %7%n
0x11A0	Metabase Import.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Filename: %6%n Caller PID: %7%n Caller Image Path: %8%n Result: %9%n	Metabase Import.%n %n Primary User Name: %1%n Primary User Domain: %2%n Primary Logon ID: %3%n Source Path: %4%n Destination Path: %5%n Filename: %6%n Caller PID: %7%n Caller Image Path: %8%n Result: %9%n
0x11000038	Classic	Classic
0x40000075	%1 Service started.	%1 Service started.
0x40000076	%1 Service stopped.	%1 Service stopped.
0x40000077	%1 Service paused.	%1 Service paused.
0x40000078	%1 Service resumed.	%1 Service resumed.
0x40000432	Not used.	Not used.
0x400008AF	For compatibility with previous versions of IIS, the filter '%1' was loaded as a global filter from the registry. To control the filter with the Internet Service Manager, remove the filter from the registry and add it as a global filter with Internet Service Manager. Filters in the registry are stored at \"HKLM\\System\\CurrentControlSet\\Services\\W3Svc\\Parameters\\Filter DLLs\".	For compatibility with previous versions of IIS, the filter '%1' was loaded as a global filter from the registry. To control the filter with the Internet Service Manager, remove the filter from the registry and add it as a global filter with Internet Service Manager. Filters in the registry are stored at \"HKLM\\System\\CurrentControlSet\\Services\\W3Svc\\Parameters\\Filter DLLs\".
0x40000906	A worker process with process id of '%1' serving application pool '%2' paged out due to inactivity. Application Pool timeout-action configuration was set to %3 minutes. A worker process will resume when needed.	A worker process with process id of '%1' serving application pool '%2' paged out due to inactivity. Application Pool timeout-action configuration was set to %3 minutes. A worker process will resume when needed.
0x40000C81	IIS start command received from user %1. The logged data is the status code.	IIS start command received from user %1. The logged data is the status code.
0x40000C82	IIS stop command received from user %1. The logged data is the status code.	IIS stop command received from user %1. The logged data is the status code.
0x40000C83	IIS reboot command received from user %1. The logged data is the status code.	IIS reboot command received from user %1. The logged data is the status code.
0x40000C84	IIS kill command received from user %1. The logged data is the status code.	IIS kill command received from user %1. The logged data is the status code.
0x40000C85	Your computer is being shut down by %1. Save any work that may be lost!	Your computer is being shut down by %1. Save any work that may be lost!
0x40000C86	IIS Reset encountered an error while stopping services, which was requested by %1. The logged data is the status code. Since the force option is on, IIS Reset will now terminate the services' processes. This may cause SCM to report errors about the services exiting.	IIS Reset encountered an error while stopping services, which was requested by %1. The logged data is the status code. Since the force option is on, IIS Reset will now terminate the services' processes. This may cause SCM to report errors about the services exiting.
0x40000FB2	Ignoring metadata tag.	Ignoring metadata tag.
0x40000FB3	The input contained an error element, which may indicate that the operationproducing the input has failed.	The input contained an error element, which may indicate that the operationproducing the input has failed.
0x40000FB4	Executed command.	Executed command.
0x400013D2	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because the worker process reached its allowed processing time limit.	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because the worker process reached its allowed processing time limit.
0x400013D3	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its allowed request limit.	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its allowed request limit.
0x400013D4	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its scheduled recycle time.	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its scheduled recycle time.
0x400013D5	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its virtual memory limit.	A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its virtual memory limit.
0x400013D6	An ISAPI reported an unhealthy condition to its worker process. Therefore, the worker process with process id of '%1' serving application pool '%2' has requested a recycle.	An ISAPI reported an unhealthy condition to its worker process. Therefore, the worker process with process id of '%1' serving application pool '%2' has requested a recycle.
0x400013D7	An administrator has requested a recycle of all worker processes in application pool '%1'.	An administrator has requested a recycle of all worker processes in application pool '%1'.
0x400013D8	The worker processes serving application pool '%1' are being recycled due to 1 or more configuration changes in the application pool properties which necessitate a restart of the processes.	The worker processes serving application pool '%1' are being recycled due to 1 or more configuration changes in the application pool properties which necessitate a restart of the processes.
0x400013D9	The worker processes serving application pool '%1' are being recycled due to detected problems with the IIS configuration store that may make current cached metadata invalid.	The worker processes serving application pool '%1' are being recycled due to detected problems with the IIS configuration store that may make current cached metadata invalid.
0x400013DA	A worker process with pid '%2' that serves application pool '%1' has been determined to be unhealthy (see previous event log message), but because a debugger is attached to it, the Windows Process Activation Service will ignore the error.	A worker process with pid '%2' that serves application pool '%1' has been determined to be unhealthy (see previous event log message), but because a debugger is attached to it, the Windows Process Activation Service will ignore the error.
0x400013FD	A worker process serving application pool '%1' has requested a recycle because it reached its private bytes memory limit.	A worker process serving application pool '%1' has requested a recycle because it reached its private bytes memory limit.
0x40001440	The Windows Process Activation Service recovered from a previous error creating app pool '%1'. See previously logged event(s).	The Windows Process Activation Service recovered from a previous error creating app pool '%1'. See previously logged event(s).
0x40001441	The Windows Process Activation Service recovered from a previous error creating site '%1'. See previously logged event(s).	The Windows Process Activation Service recovered from a previous error creating site '%1'. See previously logged event(s).
0x40001442	A worker process with process id of '%1' serving application pool '%2' was shutdown due to inactivity. Application Pool timeout configuration was set to %3 minutes. A new worker process will be started when needed.	A worker process with process id of '%1' serving application pool '%2' was shutdown due to inactivity. Application Pool timeout configuration was set to %3 minutes. A new worker process will be started when needed.
0x40001448	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will start to reduce worker process idle timeouts. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will start to reduce worker process idle timeouts. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.
0x4000144A	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will return worker process idle timeouts to their configured settings. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will return worker process idle timeouts to their configured settings. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.
0x4000144B	A worker process with process id of '%1' serving application pool '%2' was shutdown due to inactivity. The system is under high load and has decreased the idle timeout of this worker process to '%4' minutes from its original '%3' minutes. A new worker process will be started when needed.	A worker process with process id of '%1' serving application pool '%2' was shutdown due to inactivity. The system is under high load and has decreased the idle timeout of this worker process to '%4' minutes from its original '%3' minutes. A new worker process will be started when needed.
0x4000144D	The dynamic idle has been disabled in configuration. The Windows Process Activation Service (WAS) will return worker process idle timeouts to their configured settings.	The dynamic idle has been disabled in configuration. The Windows Process Activation Service (WAS) will return worker process idle timeouts to their configured settings.
0x40001455	The Windows Process Activation Service (WAS) was able to recover from the configuration read error condition and successfully read the configuration file.	The Windows Process Activation Service (WAS) was able to recover from the configuration read error condition and successfully read the configuration file.
0x4000145B	The Windows Process Activation Service (WAS) started with '%1' mode using '%2'	The Windows Process Activation Service (WAS) started with '%1' mode using '%2'
0x40001B5A	Listener Adapter protocol '%1' is waiting to connect to Windows Process Activation Service. This event will only be logged once. Cause: This could be caused by either Windows Process Activation Service not being started, the protocol not being configured in section, or another process already connected as Listener Adapter for that protocol. Fix: Ensure that Windows Process Activation Service is running, the protocol is configured in the section, and that another process has not already connected as the Listener Adapter for that protocol.	Listener Adapter protocol '%1' is waiting to connect to Windows Process Activation Service. This event will only be logged once. Cause: This could be caused by either Windows Process Activation Service not being started, the protocol not being configured in section, or another process already connected as Listener Adapter for that protocol. Fix: Ensure that Windows Process Activation Service is running, the protocol is configured in the section, and that another process has not already connected as the Listener Adapter for that protocol.
0x40001B5B	Listener Adapter protocol '%1' successfully connected to Windows Process Activation Service.	Listener Adapter protocol '%1' successfully connected to Windows Process Activation Service.
0x4004000B	Anonymous logon request received from %1 at host %2.	Anonymous logon request received from %1 at host %2.
0x4004000C	User logon request received from %1 at host %2.	User logon request received from %1 at host %2.
0x50000002	Error	Error
0x50000003	Warning	Warning
0x50000004	Information	Information
0x50000005	Verbose	Verbose
0x80000009	Warning: %1.	Warning: %1.
0x80000010	Warning: %1, %2.	Warning: %1, %2.
0x80000011	Warning: %1, %2, %3.	Warning: %1, %2, %3.
0x80000012	Warning: %1, %2, %3, %4.	Warning: %1, %2, %3, %4.
0x80000017	No Default Script Language specified for Application %s. Using default: %s.	No Default Script Language specified for Application %s. Using default: %s.
0x80000064	The server was unable to logon the Windows NT account '%1' due to the following error: %2 The data is the error code.	The server was unable to logon the Windows NT account '%1' due to the following error: %2 The data is the error code.
0x80000065	The server was unable to add the virtual root '%1' for the directory '%2' due to the following error: %3 The data is the error code.	The server was unable to add the virtual root '%1' for the directory '%2' due to the following error: %3 The data is the error code.
0x80000071	Instance %1 has invalid binding descriptor %2.	Instance %1 has invalid binding descriptor %2.
0x80000072	Instance %1 has invalid secure binding descriptor %2 (host name ignored).	Instance %1 has invalid secure binding descriptor %2 (host name ignored).
0x800003F8	The World Wide Web Publishing Service (WWW Service) did not configure logging for site %1. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not configure logging for site %1. The data field contains the error number.
0x800003FB	The World Wide Web Publishing Service (WWW Service) failed to intialize performance counters properly. The performance counters will run, but counter data may be inaccurate. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to intialize performance counters properly. The performance counters will run, but counter data may be inaccurate. The data field contains the error number.
0x80000411	The '%1' '%2' failed range validation for property '%3'. The configured value '%4' is outside of the range '%5' to '%6'. The value will default to '%7'.	The '%1' '%2' failed range validation for property '%3'. The configured value '%4' is outside of the range '%5' to '%6'. The value will default to '%7'.
0x80000412	The AppPoolCommand property set for application pool '%1' is not a valid value. The value is '%2'. It must be either MD_APPPOOL_COMMAND_START = 1 or MD_APPPOOL_COMMAND_STOP = 2.	The AppPoolCommand property set for application pool '%1' is not a valid value. The value is '%2'. It must be either MD_APPPOOL_COMMAND_START = 1 or MD_APPPOOL_COMMAND_STOP = 2.
0x80000413	The virtual site %1 is invalid because the World Wide Web Publishing Service (WWW Service) could not configure valid site bindings or no site bindings exist for the site.	The virtual site %1 is invalid because the World Wide Web Publishing Service (WWW Service) could not configure valid site bindings or no site bindings exist for the site.
0x80000414	The virtual site %1 is invalid because the application pool ID for the site is null.	The virtual site %1 is invalid because the application pool ID for the site is null.
0x80000415	Not Used.	Not Used.
0x8000042F	The World Wide Web Publishing Service (WWW Service) failed to enable global bandwidth throttling because QoS Packet Scheduler is not installed.	The World Wide Web Publishing Service (WWW Service) failed to enable global bandwidth throttling because QoS Packet Scheduler is not installed.
0x80000430	The World Wide Web Publishing Service failed to enable bandwidth throttling on site '%1'. The data field contains the error number.	The World Wide Web Publishing Service failed to enable bandwidth throttling on site '%1'. The data field contains the error number.
0x80000431	The World Wide Web Publishing Service failed to enable global bandwidth throttling because QoS Packet Scheduler is not installed or it's not running.	The World Wide Web Publishing Service failed to enable global bandwidth throttling because QoS Packet Scheduler is not installed or it's not running.
0x8000046D	The World Wide Web Publishing Service (WWW Service) has both centralized binary logging and centralized W3C logging enabled. Only one type of logging can be enabled at a time, so the system will default to central W3C logging.	The World Wide Web Publishing Service (WWW Service) has both centralized binary logging and centralized W3C logging enabled. Only one type of logging can be enabled at a time, so the system will default to central W3C logging.
0x80000494	The World Wide Web Publishing Service (WWW Service) did not construct valid URLs for virtual site %1. Therefore, the virtual site %1 will be stopped. This can be caused by invalid characters in the site bindings. The following characters are not allowed in a site binding: \"\\\"\" \"/\" \"\\\\\" \"[\" \"]\" \":\" \	The World Wide Web Publishing Service (WWW Service) did not construct valid URLs for virtual site %1. Therefore, the virtual site %1 will be stopped. This can be caused by invalid characters in the site bindings. The following characters are not allowed in a site binding: \"\\\"\" \"/\" \"\\\\\" \"[\" \"]\" \":\" \
0x800008B2	The server was unable to read the file %1 due to a lack of access permissions.	The server was unable to read the file %1 due to a lack of access permissions.
0x800008B4	The server stop serving requests for application '%1' because the number of Out of Process component crashes exceed a limit.	The server stop serving requests for application '%1' because the number of Out of Process component crashes exceed a limit.
0x800008B5	The server failed to shut down application '%1'. The error was '%2'.	The server failed to shut down application '%1'. The error was '%2'.
0x800008B6	The server was unable to read the file %1. The file does not exist.	The server was unable to read the file %1. The file does not exist.
0x800008B7	The server was unable to read the file %1. The Windows 32 error returned from the attempt is %2.	The server was unable to read the file %1. The Windows 32 error returned from the attempt is %2.
0x800008B8	The server was unable to read the file %1. The file exceeds the maximum allowable size of %2.	The server was unable to read the file %1. The file exceeds the maximum allowable size of %2.
0x800008B9	The server was unable to allocate a buffer to read the file %1.	The server was unable to allocate a buffer to read the file %1.
0x800008BC	The server failed to load application '%1'. The error was '%2'.	The server failed to load application '%1'. The error was '%2'.
0x800008BD	Out of process application '%1' terminated unexpectedly.	Out of process application '%1' terminated unexpectedly.
0x800008C1	Site '%1' hit its CPU Limit. No action was taken.	Site '%1' hit its CPU Limit. No action was taken.
0x800008C2	Site '%1' hit its CPU Limit. The priority of all process on that site has been lowered to idle class.	Site '%1' hit its CPU Limit. The priority of all process on that site has been lowered to idle class.
0x800008C3	Site '%1' hit its CPU Limit. All processes on that site have been terminated.	Site '%1' hit its CPU Limit. All processes on that site have been terminated.
0x800008C4	Site '%1' hit its CPU Limit. The site has been paused.	Site '%1' hit its CPU Limit. The site has been paused.
0x800008C5	The server certificate for instance '%1' has expired or is not yet valid.	The server certificate for instance '%1' has expired or is not yet valid.
0x800008C6	The server certificate for instance '%1' has been revoked.	The server certificate for instance '%1' has been revoked.
0x800008C7	The server certificate chain does not include a trusted root certificate.	The server certificate chain does not include a trusted root certificate.
0x800008C8	A certificate in the server certificate chain has an invalid signature.	A certificate in the server certificate chain has an invalid signature.
0x800008C9	CPU Limits/Accounting failed to queue work item. The data is the error.	CPU Limits/Accounting failed to queue work item. The data is the error.
0x800008CA	The World Wide Web Publishing Service (WWW Service) could not retrieve the server certificate for instance '%1' because the associated IIS configuration store data is invalid. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) could not retrieve the server certificate for instance '%1' because the associated IIS configuration store data is invalid. The error is '%2'.
0x800008CB	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of a CryptoAPI error. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of a CryptoAPI error. The error is '%2'.
0x800008CC	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because the certificate could not be found in a certificate store. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because the certificate could not be found in a certificate store. The error is '%2'.
0x800008CD	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of an internal error. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of an internal error. The error is '%2'.
0x800008CE	The server Certificate Trust List for instance '%1' had invalid IIS configuration store data associated with it and could not be retrieved; the error encountered was '%2'.	The server Certificate Trust List for instance '%1' had invalid IIS configuration store data associated with it and could not be retrieved; the error encountered was '%2'.
0x800008CF	The World Wide Web Publishing Service (WWW Service) failed to retrieve the server Certificate Trust List for instance '%1' because of a CryptoAPI error. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) failed to retrieve the server Certificate Trust List for instance '%1' because of a CryptoAPI error. The error is '%2'.
0x800008D0	The World Wide Web Publishing Service (WWW Service) did not retrieve the server Certificate Trust List for instance '%1' because it could not be found in the certificate store. The error is '%2'.	The World Wide Web Publishing Service (WWW Service) did not retrieve the server Certificate Trust List for instance '%1' because it could not be found in the certificate store. The error is '%2'.
0x800008D1	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of an internal error. The error is %2.	The World Wide Web Publishing Service (WWW Service) did not retrieve the server certificate for instance '%1' because of an internal error. The error is %2.
0x800008D2	The server failed to close client connections to the following URLs during shutdown: '%1'.	The server failed to close client connections to the following URLs during shutdown: '%1'.
0x800008D6	ISAPI '%1' reported itself as unhealthy for the following reason: '%2'.	ISAPI '%1' reported itself as unhealthy for the following reason: '%2'.
0x800008D7	ISAPI '%1' reported itself as unhealthy. No reason was given by the ISAPI.	ISAPI '%1' reported itself as unhealthy. No reason was given by the ISAPI.
0x800008D8	The directory specified for caching compressed content %1 is invalid. Static compression is being disabled.	The directory specified for caching compressed content %1 is invalid. Static compression is being disabled.
0x800008D9	The registry key for IIS subauthenticator is not configured correctly on local machine, the anonymous password sync feature is disabled.	The registry key for IIS subauthenticator is not configured correctly on local machine, the anonymous password sync feature is disabled.
0x800008DA	The account that the current worker process is running under does not have SeTcbPrivilege privilege, the anonymous password sync feature and the Digest authentication feature are disabled.	The account that the current worker process is running under does not have SeTcbPrivilege privilege, the anonymous password sync feature and the Digest authentication feature are disabled.
0x800008E0	The registry key for IIS subauthenticator is not configured correctly on domain controller, the Digest feature is disabled.	The registry key for IIS subauthenticator is not configured correctly on domain controller, the Digest feature is disabled.
0x800008E1	Worker process could not access IIS configuration store due to disconnection error. Marking process as unhealthy.	Worker process could not access IIS configuration store due to disconnection error. Marking process as unhealthy.
0x800008E3	ETW Tracing support failed to intialize. Execution of IIS will continue although ETW Tracing support (or parts of it) will not be available. The data is the error.	ETW Tracing support failed to intialize. Execution of IIS will continue although ETW Tracing support (or parts of it) will not be available. The data is the error.
0x800008EB	FailedRequestTracing module failed to create directory '%3'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module failed to create directory '%3'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008EC	FailedRequestTracing module failed to write buffered events to log file for the request that matched failure definition. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module failed to write buffered events to log file for the request that matched failure definition. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008ED	FailedRequestTracing module detected invalid configuration on path '%4'. Trace provider or tracing area name '%3' is not recognized. Check the section for currently supported list or providers and areas. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module detected invalid configuration on path '%4'. Trace provider or tracing area name '%3' is not recognized. Check the section for currently supported list or providers and areas. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008EE	FailedRequestTracing module detected invalid configuration on path '%4'. Attribute \"statusCode\" contains invalid value '%3'. Examples of valid status are '404' or '403.1'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module detected invalid configuration on path '%4'. Attribute \"statusCode\" contains invalid value '%3'. Examples of valid status are '404' or '403.1'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008EF	FailedRequestTracing module encountered problem while reading configuration. Configuration system returned exception '%3' in file %4 on line %5. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module encountered problem while reading configuration. Configuration system returned exception '%3' in file %4 on line %5. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008F0	FailedRequestTracing module encountered problem while reading configuration. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module encountered problem while reading configuration. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008F1	FailedRequestTracing Module failed to delete at least one log file from the directory '%3'. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing Module failed to delete at least one log file from the directory '%3'. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008F2	FailedRequestTracing module encountered runtime error. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module encountered runtime error. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008F3	FailedRequestTracing module detected invalid configuration on path '%4'. Attribute \"guid\" in section contains invalid value '%3'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module detected invalid configuration on path '%4'. Attribute \"guid\" in section contains invalid value '%3'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008F4	FailedRequestTracing module failed to create XSL file '%3. Friendly rendering of log files will not be available. The problem happened at least %1 times in the last %2 minutes. The data is the error.	FailedRequestTracing module failed to create XSL file '%3. Friendly rendering of log files will not be available. The problem happened at least %1 times in the last %2 minutes. The data is the error.
0x800008FA	The globalModules list is empty. No requests can be served successfully.	The globalModules list is empty. No requests can be served successfully.
0x800008FC	The worker process cannot access the CLR configuration file at '%1'. Verify that the file exists and that the worker process has read access to the file.	The worker process cannot access the CLR configuration file at '%1'. Verify that the file exists and that the worker process has read access to the file.
0x800008FD	There was an error during processing of the HTTP Application Preload event. Modules and/or applications relying upon this event may not have been initialized properly. The data field contains the error code.	There was an error during processing of the HTTP Application Preload event. Modules and/or applications relying upon this event may not have been initialized properly. The data field contains the error code.
0x800008FF	There was an error during processing of the managed application service auto-start for application pool: '%1'. Some application services may not have been processed correctly. Please check the configuration for application service auto-start for the application(s) assigned to this application pool. The data field contains the error code.	There was an error during processing of the managed application service auto-start for application pool: '%1'. Some application services may not have been processed correctly. Please check the configuration for application service auto-start for the application(s) assigned to this application pool. The data field contains the error code.
0x80000901	There was an error during processing of the managed application service auto-start for application pool: '%1'. The configured .Net Framework for this application pool doesn't support managed application services. As a result, no managed application service auto-start has been completed. To resolve this issue, please change the .Net Framework version configured for this application pool to one that supports managed application service. The data field contains the error code.	There was an error during processing of the managed application service auto-start for application pool: '%1'. The configured .Net Framework for this application pool doesn't support managed application services. As a result, no managed application service auto-start has been completed. To resolve this issue, please change the .Net Framework version configured for this application pool to one that supports managed application service. The data field contains the error code.
0x80000902	There was an error during processing of the managed application service auto-start for application pool: '%1'. The loading of application service provider objects is not supported if the pipeline mode is set to 'Classic' mode. As a result, no managed application service auto-start has been completed. To resolve this issue, please change the pipeline mode for this application pool to 'Integrated' mode. The data field contains the error code.	There was an error during processing of the managed application service auto-start for application pool: '%1'. The loading of application service provider objects is not supported if the pipeline mode is set to 'Classic' mode. As a result, no managed application service auto-start has been completed. To resolve this issue, please change the pipeline mode for this application pool to 'Integrated' mode. The data field contains the error code.
0x80001391	A process serving application pool '%1' terminated unexpectedly. The process id was '%2'. The process exit code was '0x%3'.	A process serving application pool '%1' terminated unexpectedly. The process id was '%2'. The process exit code was '0x%3'.
0x80001392	A process serving application pool '%1' failed to respond to a ping. The process id was '%2'.	A process serving application pool '%1' failed to respond to a ping. The process id was '%2'.
0x80001393	A process serving application pool '%1' suffered a fatal communication error with the Windows Process Activation Service. The process id was '%2'. The data field contains the error number.	A process serving application pool '%1' suffered a fatal communication error with the Windows Process Activation Service. The process id was '%2'. The data field contains the error number.
0x80001394	A process serving application pool '%1' exceeded time limits during start up. The process id was '%2'.	A process serving application pool '%1' exceeded time limits during start up. The process id was '%2'.
0x80001395	A process serving application pool '%1' exceeded time limits during shut down. The process id was '%2'.	A process serving application pool '%1' exceeded time limits during shut down. The process id was '%2'.
0x80001396	The Windows Process Activation Service encountered an internal error in its process management of worker process '%2' serving application pool '%1'. The data field contains the error number.	The Windows Process Activation Service encountered an internal error in its process management of worker process '%2' serving application pool '%1'. The data field contains the error number.
0x80001398	Event id used by World Wide Web Publishing Service.	Event id used by World Wide Web Publishing Service.
0x8000139D	The identity of application pool %1 is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.	The identity of application pool %1 is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
0x8000139E	The Windows Process Activation Service failed to create a worker process for the application pool '%1'. The data field contains the error number.	The Windows Process Activation Service failed to create a worker process for the application pool '%1'. The data field contains the error number.
0x800013A1	Application pool '%1' exceeded its job limit settings.	Application pool '%1' exceeded its job limit settings.
0x800013AF	A process serving application pool '%1' reported a failure. The process id was '%2'. The data field contains the error number.	A process serving application pool '%1' reported a failure. The process id was '%2'. The data field contains the error number.
0x800013B2	The AppPoolCommand property set on the application pool '%1' is not a valid value. It is '%2'. It must be either MD_APPPOOL_COMMAND_START = 1 or MD_APPPOOL_COMMAND_STOP = 2.	The AppPoolCommand property set on the application pool '%1' is not a valid value. It is '%2'. It must be either MD_APPPOOL_COMMAND_START = 1 or MD_APPPOOL_COMMAND_STOP = 2.
0x800013B3	The virtual site %1 is invalid because valid site bindings could not be configured or no site bindings exist for the site.	The virtual site %1 is invalid because valid site bindings could not be configured or no site bindings exist for the site.
0x800013B6	The server command property for virtual site '%1' is not a valid value. It is set to '%2'. It must be one of the following: MD_SERVER_COMMAND_START = 1 or MD_SERVER_COMMAND_STOP = 2 or MD_SERVER_COMMAND_PAUSE = 3 or MD_SERVER_COMMAND_CONTINUE = 4.	The server command property for virtual site '%1' is not a valid value. It is set to '%2'. It must be one of the following: MD_SERVER_COMMAND_START = 1 or MD_SERVER_COMMAND_STOP = 2 or MD_SERVER_COMMAND_PAUSE = 3 or MD_SERVER_COMMAND_CONTINUE = 4.
0x800013B7	The application '%2' belonging to site '%1' has an AppPoolId set, but the property is empty. Therefore, the application will be ignored.	The application '%2' belonging to site '%1' has an AppPoolId set, but the property is empty. Therefore, the application will be ignored.
0x800013B8	The application '%2' belonging to site '%1' has an invalid AppPoolId '%3' set. Therefore, the application will be ignored.	The application '%2' belonging to site '%1' has an invalid AppPoolId '%3' set. Therefore, the application will be ignored.
0x800013B9	This message has become deprecated in IIS 7.	This message has become deprecated in IIS 7.
0x800013BA	The application pool id '%1' exceeds length limits. It is '%2' characters and can not be more than '%3' characters. The application pool will therefore be ignored.	The application pool id '%1' exceeds length limits. It is '%2' characters and can not be more than '%3' characters. The application pool will therefore be ignored.
0x800013BB	An application pool id was defined as a zero length string. An application pool id must not be a zero length string. The application pool will therefore be ignored.	An application pool id was defined as a zero length string. An application pool id must not be a zero length string. The application pool will therefore be ignored.
0x800013BC	The application '%2' belongs to an invalid site '%1'. Therefore, the application will be ignored.	The application '%2' belongs to an invalid site '%1'. Therefore, the application will be ignored.
0x800013BF	Site %1 was disabled because the application pool defined for site %2 is not a valid application pool.	Site %1 was disabled because the application pool defined for site %2 is not a valid application pool.
0x800013C0	Site %1 was disabled because the root application defined for the site is invalid. See the previous event log message for information about why the root application is invalid.	Site %1 was disabled because the root application defined for the site is invalid. See the previous event log message for information about why the root application is invalid.
0x800013C1	Application pool %1 has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.	Application pool %1 has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.
0x800013C2	The Windows Process Activation Service encountered a failure while setting the affinity mask of application pool '%1'. Probable cause: The mask does not contain any processors available on this machine. The data field contains the error number.	The Windows Process Activation Service encountered a failure while setting the affinity mask of application pool '%1'. Probable cause: The mask does not contain any processors available on this machine. The data field contains the error number.
0x800013C9	Centralized logging is configured to truncate its log every '%1' bytes. Since this value must be at least 1048576 bytes ( 1 megabyte ), 1048576 bytes will be used.	Centralized logging is configured to truncate its log every '%1' bytes. Since this value must be at least 1048576 bytes ( 1 megabyte ), 1048576 bytes will be used.
0x800013CB	The World Wide Web Publishing Service property '%1' failed range validation. The configured value, '%2' is outside of the range '%3' to '%4'. The default value, '%5', will be used.	The World Wide Web Publishing Service property '%1' failed range validation. The configured value, '%2' is outside of the range '%3' to '%4'. The default value, '%5', will be used.
0x800013CE	The Windows Process Activation Service failed to issue recycle requests to all worker processes of application pool '%1'. The data field contains the error number.	The Windows Process Activation Service failed to issue recycle requests to all worker processes of application pool '%1'. The data field contains the error number.
0x80001407	A worker process '%2' serving application pool '%1' is no longer trusted by the Windows Process Activation Service, based on ill-formed data the worker process sent to the service. The data field contains the error number.	A worker process '%2' serving application pool '%1' is no longer trusted by the Windows Process Activation Service, based on ill-formed data the worker process sent to the service. The data field contains the error number.
0x8000140C	Enable32bitAppOnWin64 setting will be ignored because IIS is currently running in IIS5 Compatibility mode.	Enable32bitAppOnWin64 setting will be ignored because IIS is currently running in IIS5 Compatibility mode.
0x80001411	A worker process '%2' serving application pool '%1' failed to start a listener channel for protocol '%4' in the allotted time. The data field contains the error number.	A worker process '%2' serving application pool '%1' failed to start a listener channel for protocol '%4' in the allotted time. The data field contains the error number.
0x80001412	A worker process '%2' serving application pool '%1' failed to stop a listener channel for protocol '%4' in the allotted time. The data field contains the error number.	A worker process '%2' serving application pool '%1' failed to stop a listener channel for protocol '%4' in the allotted time. The data field contains the error number.
0x80001413	A listener channel for protocol '%4' in worker process '%2' serving application pool '%1' reported a listener channel failure. The data field contains the error number.	A listener channel for protocol '%4' in worker process '%2' serving application pool '%1' reported a listener channel failure. The data field contains the error number.
0x80001414	Windows Process Activation Service (WAS) disabled protocol %1 because WAS received bad data about the protocol. To re-enable the protocol, resolve the issue and recycle WAS.	Windows Process Activation Service (WAS) disabled protocol %1 because WAS received bad data about the protocol. To re-enable the protocol, resolve the issue and recycle WAS.
0x8000141C	Windows Process Activation Service (WAS) is disabling protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle the WAS.	Windows Process Activation Service (WAS) is disabling protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle the WAS.
0x8000141D	The World Wide Web Publishing Service property '%1' failed range validation. The configured value, '%2' is invalid. The default value, '%3', will be used.	The World Wide Web Publishing Service property '%1' failed range validation. The configured value, '%2' is invalid. The default value, '%3', will be used.
0x80001420	The application pool '%1' has an IdleTimeout '%2' equal to or greater than the PeriodicRestart time value of '%3'. This means that the worker process will never idle timeout, since it will restart before the idle timeout is reached. Please confirm that this is the desired behavior and if so, consider disabling the idle timeout by setting it to '0'.	The application pool '%1' has an IdleTimeout '%2' equal to or greater than the PeriodicRestart time value of '%3'. This means that the worker process will never idle timeout, since it will restart before the idle timeout is reached. Please confirm that this is the desired behavior and if so, consider disabling the idle timeout by setting it to '0'.
0x80001421	The Windows Process Activation Service (WAS) encountered an error attempting to look up the built in IIS_IUSRS group. There may be problems in viewing and setting security permissions with the IIS_IUSRS group. This happens if the machine has been joined and promoted to be a Domain Controller in a legacy domain. Please see the online help for more information and solutions to this problem. The data field contains the error number.	The Windows Process Activation Service (WAS) encountered an error attempting to look up the built in IIS_IUSRS group. There may be problems in viewing and setting security permissions with the IIS_IUSRS group. This happens if the machine has been joined and promoted to be a Domain Controller in a legacy domain. Please see the online help for more information and solutions to this problem. The data field contains the error number.
0x80001422	Available.	Available.
0x80001426	A listener adapter for protocol '%4' supporting a listener channel in worker process '%2' serving application pool '%1' failed. The data field contains the error number.	A listener adapter for protocol '%4' supporting a listener channel in worker process '%2' serving application pool '%1' failed. The data field contains the error number.
0x8000142A	The application '%2' belonging to site '%1' has an invalid AppRoot set. It should be '%4' but instead is '%3'. Therefore, the application will be ignored.	The application '%2' belonging to site '%1' has an invalid AppRoot set. It should be '%4' but instead is '%3'. Therefore, the application will be ignored.
0x80001449	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will start to aggressively reduce worker process idle timeouts. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.	The dynamic idle load is '%1' percent of the dynamic idle threshold. The Windows Process Activation Service (WAS) will start to aggressively reduce worker process idle timeouts. Current number of worker processes: '%2', current total commit: '%3' MB, total physical memory: '%4' MB, current physical memory free: '%5' MB.
0x8000144C	A request to create a new worker process has arrived. The '%1' setting has been reached. The Windows Process Activation Service (WAS) will not start any worker processes until this drops.	A request to create a new worker process has arrived. The '%1' setting has been reached. The Windows Process Activation Service (WAS) will not start any worker processes until this drops.
0x80001451	A process serving application pool '%1' reported a failure during application preloading or service loading. The process id was '%2'. Please ensure that all application preload or service settings in the application pool are configured properly. The data field contains the error number.	A process serving application pool '%1' reported a failure during application preloading or service loading. The process id was '%2'. Please ensure that all application preload or service settings in the application pool are configured properly. The data field contains the error number.
0x80001454	The Windows Process Activation Service (WAS) encountered an error condition attempting to read the configuration file. It will keep retrying to read the configuration. Until then, it will continue to run on the current configuration. The specific error was '%1' for configuration path '%2' for file '%3'. The data field contains the error number.	The Windows Process Activation Service (WAS) encountered an error condition attempting to read the configuration file. It will keep retrying to read the configuration. Until then, it will continue to run on the current configuration. The specific error was '%1' for configuration path '%2' for file '%3'. The data field contains the error number.
0x80001457	The job object associated with application pool '%1' encountered an error during qeurying information about job object. CPU monitoring may not function as expected. The data field contains the error number.	The job object associated with application pool '%1' encountered an error during qeurying information about job object. CPU monitoring may not function as expected. The data field contains the error number.
0x80001458	The Windows Process Activation Service failed to create a debugger process for the application pool '%1'. The data field contains the error number. Check registry 'Debugger' at HKLM\\SYSTEM\\CurrentControlSet\\Services\\WAS\\%1	The Windows Process Activation Service failed to create a debugger process for the application pool '%1'. The data field contains the error number. Check registry 'Debugger' at HKLM\\SYSTEM\\CurrentControlSet\\Services\\WAS\\%1
0x80001459	A process serving application pool '%1' exceeded time limits during start up. The process id was '%2'. The worker process was configured to start under debugger. Check registry 'Debugger' at HKLM\\SYSTEM\\CurrentControlSet\\Services\\WAS\\%1 to see whether debugger command arguments are set properly.	A process serving application pool '%1' exceeded time limits during start up. The process id was '%2'. The worker process was configured to start under debugger. Check registry 'Debugger' at HKLM\\SYSTEM\\CurrentControlSet\\Services\\WAS\\%1 to see whether debugger command arguments are set properly.
0x8000145A	CPU time for application pool '%1' has been throttled.	CPU time for application pool '%1' has been throttled.
0x8000145C	The Windows Process Activation Service (WAS) failed to insert data for registration site '%1'. The data field contains the error number.	The Windows Process Activation Service (WAS) failed to insert data for registration site '%1'. The data field contains the error number.
0x8000145D	Binding information '%1' is unsupported with dynamic mode. The Windows Process Activation Service (WAS) restart is required to register that binding.	Binding information '%1' is unsupported with dynamic mode. The Windows Process Activation Service (WAS) restart is required to register that binding.
0x80001B59	Listener Adapter protocol '%1' failed to connect to Windows Process Activation Service due to identity permissions mismatch. Cause: Configured Identity for protocol '%1' in applicationHost.config does not match identity of process '%2' hosting Listener Adapter. Fix: Ensure that the identity for protocol '%1' is configured correctly in applicationHost.config.	Listener Adapter protocol '%1' failed to connect to Windows Process Activation Service due to identity permissions mismatch. Cause: Configured Identity for protocol '%1' in applicationHost.config does not match identity of process '%2' hosting Listener Adapter. Fix: Ensure that the identity for protocol '%1' is configured correctly in applicationHost.config.
0x80001F41	The Web Management Service was stopped because it did not respond.	The Web Management Service was stopped because it did not respond.
0x80002331	The Application Host Helper Service encountered an error trying to delete the history directory '%1'. The directory will be skipped and ignored. Note that the directory may still get deleted in the future if the service restarts. The data field contains the error number.	The Application Host Helper Service encountered an error trying to delete the history directory '%1'. The directory will be skipped and ignored. Note that the directory may still get deleted in the future if the service restarts. The data field contains the error number.
0x8004000A	User %1 at host %2 has timed-out after %3 seconds of inactivity.	User %1 at host %2 has timed-out after %3 seconds of inactivity.
0x8004000D	User %1 failed to log on, could not access the home directory %2.	User %1 failed to log on, could not access the home directory %2.
0x8004000E	User %1 denied access to the current directory %2 due to a security change.	User %1 denied access to the current directory %2 due to a security change.
0x800401F3	Invalid ProgID.	Invalid ProgID.
0x80043841	The server failed to create a data channel connection to a client on local interface: %1. The FTP data port %2 may be in use by another service or application.	The server failed to create a data channel connection to a client on local interface: %1. The FTP data port %2 may be in use by another service or application.
0x90000001	Microsoft-Windows-IIS-Configuration	Microsoft-Windows-IIS-Configuration
0x90000002	Microsoft-Windows-IIS-Configuration/Administrative	Microsoft-Windows-IIS-Configuration/Administrative
0x90000003	Microsoft-Windows-IIS-Configuration/Operational	Microsoft-Windows-IIS-Configuration/Operational
0x90000004	Microsoft-Windows-IIS-Configuration/Analytic	Microsoft-Windows-IIS-Configuration/Analytic
0x90000005	Microsoft-Windows-IIS-Configuration/Debug	Microsoft-Windows-IIS-Configuration/Debug
0x91000001	Microsoft-Windows-IIS-FTP	Microsoft-Windows-IIS-FTP
0x92000001	Microsoft-Windows-IIS-IisMetabaseAudit	Microsoft-Windows-IIS-IisMetabaseAudit
0x93000001	Microsoft-Windows-IIS-IISReset	Microsoft-Windows-IIS-IISReset
0x94000001	Microsoft-Windows-IIS-W3SVC-WP	Microsoft-Windows-IIS-W3SVC-WP
0x95000001	Microsoft-Windows-IIS-W3SVC-PerfCounters	Microsoft-Windows-IIS-W3SVC-PerfCounters
0x96000001	Microsoft-Windows-WAS-ListenerAdapter	Microsoft-Windows-WAS-ListenerAdapter
0x97000001	Microsoft-Windows-WAS	Microsoft-Windows-WAS
0x98000001	Microsoft-Windows-IIS-W3SVC	Microsoft-Windows-IIS-W3SVC
0x99000001	Microsoft-Windows-IIS-WMSVC	Microsoft-Windows-IIS-WMSVC
0x9A000001	Microsoft-Windows-IIS-APPHOSTSVC	Microsoft-Windows-IIS-APPHOSTSVC
0x9B000001	Microsoft-Windows-IIS-W3LOGSVC	Microsoft-Windows-IIS-W3LOGSVC
0x9C000001	Microsoft-Windows-IIS-Logging	Microsoft-Windows-IIS-Logging
0x9C000002	Microsoft-Windows-IIS-Logging/Logs	Microsoft-Windows-IIS-Logging/Logs
0xB0000003	A cache node for '%3' has been added to cache.	A cache node for '%3' has been added to cache.
0xB0000007	Configuration cache is handling change notification for '%1'.	Configuration cache is handling change notification for '%1'.
0xB0000008	Configuration cache is polling for changes at '%1'.	Configuration cache is polling for changes at '%1'.
0xB0000009	Configuration cache is discarding all config files whose configuration path is equal to or a subpath of '%1'.	Configuration cache is discarding all config files whose configuration path is equal to or a subpath of '%1'.
0xB000000A	An error has occurred: %4	An error has occurred: %4
0xB000000C	Unable to find schema for config section '%4'. This section will be ignored.	Unable to find schema for config section '%4'. This section will be ignored.
0xB000000D	Parsing config file '%2'.	Parsing config file '%2'.
0xB000000E	MACHINE/WEBROOT/APPHOST configuration redirection has been enabled. The redirected physical path is '%1'.	MACHINE/WEBROOT/APPHOST configuration redirection has been enabled. The redirected physical path is '%1'.
0xB000000F	Attempting to open file or directory '%2'.	Attempting to open file or directory '%2'.
0xB0000010	An impersonation token with handle '%4' for the credentials of '%1\\%2' has been created.	An impersonation token with handle '%4' for the credentials of '%1\\%2' has been created.
0xB0000011	File change notification monitor that watches for changes in '%3' has been created.	File change notification monitor that watches for changes in '%3' has been created.
0xB0000012	File change notification monitor that watches for changes in '%3' has blocked waiting for file changes.	File change notification monitor that watches for changes in '%3' has blocked waiting for file changes.
0xB0000013	File change notification monitor that watches for changes in '%3' received a change notification.	File change notification monitor that watches for changes in '%3' received a change notification.
0xB0000014	File change notification monitor that watches for changes in '%3' is processing notified changes.	File change notification monitor that watches for changes in '%3' is processing notified changes.
0xB0000015	File change notification monitor that watches for changes in '%3' has been destroyed.	File change notification monitor that watches for changes in '%3' has been destroyed.
0xB0000017	A change listener of type '%2' is being informed about a configuration change at '%3'.	A change listener of type '%2' is being informed about a configuration change at '%3'.
0xB0000018	During schema file enumeration, the file '%1' was detected in the schema directory.	During schema file enumeration, the file '%1' was detected in the schema directory.
0xB0000019	The virtual path '%1' has been mapped to the physical path '%2'.	The virtual path '%1' has been mapped to the physical path '%2'.
0xB000001B	The '%6' metadata of a configuration system object was set to '%7'.	The '%6' metadata of a configuration system object was set to '%7'.
0xB000001C	Thread is impersonating an access token belonging to handle '%2'.	Thread is impersonating an access token belonging to handle '%2'.
0xB000001D	Changes to '%4' at '%2' have successfully been committed.	Changes to '%4' at '%2' have successfully been committed.
0xB000001E	Failed to commit changes to '%4' at '%2'.	Failed to commit changes to '%4' at '%2'.
0xB0000021	Unable to locate IIS_Schema.xml in '%1'.	Unable to locate IIS_Schema.xml in '%1'.
0xB0000024	Handle '%2' duplicated to '%3'	Handle '%2' duplicated to '%3'
0xB0000025	Unable to locate a site with SiteName '%1'.	Unable to locate a site with SiteName '%1'.
0xB0000026	Unable to locate a site with SiteId '%1'.	Unable to locate a site with SiteId '%1'.
0xB0000027	The SiteId '%1' has been assigned to more than one site. Please change your configuration such that each site is assigned a unique SiteId.	The SiteId '%1' has been assigned to more than one site. Please change your configuration such that each site is assigned a unique SiteId.
0xB0000028	The SiteName '%1' has been assigned to more than one site. Please change your configuration such that each site is assigned a unique SiteName.	The SiteName '%1' has been assigned to more than one site. Please change your configuration such that each site is assigned a unique SiteName.
0xB0000029	Failed to instantiate '%3' when attempting to populate dynamic configuration for '%1'. This COM component may not be registered.	Failed to instantiate '%3' when attempting to populate dynamic configuration for '%1'. This COM component may not be registered.
0xB000002A	Failed to initialize the '%3' encryption provider in '%1'. Please check your configuration.	Failed to initialize the '%3' encryption provider in '%1'. Please check your configuration.
0xB000002B	Failed to encrypt attribute '%4'.	Failed to encrypt attribute '%4'.
0xB000002C	Failed to decrypt attribute '%4'.	Failed to decrypt attribute '%4'.
0xB000002D	Unable to map '%1' to the subpath of any known virtual directory.	Unable to map '%1' to the subpath of any known virtual directory.
0xB000002E	Virtual directory mapping from '%4' to '%5' created.	Virtual directory mapping from '%4' to '%5' created.
0xB000002F	The location of the configuration file whose config path is '%1' was mapped to '%2'.	The location of the configuration file whose config path is '%1' was mapped to '%2'.
0xB0000031	Config/child source file for configuration '%6' specified in '%2' is being loaded.	Config/child source file for configuration '%6' specified in '%2' is being loaded.
0xB0000032	Changes have successfully been committed to '%1'.	Changes have successfully been committed to '%1'.
0xB0000033	Failed to commit changes to '%2' because file on the disk has been changed.	Failed to commit changes to '%2' because file on the disk has been changed.
0xB0000034	Checking whether file '%2' has changed on the disk returned '%9'.	Checking whether file '%2' has changed on the disk returned '%9'.
0xB0000035	Unable to create a path mapping for the virtual directory, /system.applicationHost/sites/site[@name='%1']/application[@path='%2']/virtualDirectory[@path='%3'] because the mapping with the relative virtual path, '%5' was already created for another virtual directory.	Unable to create a path mapping for the virtual directory, /system.applicationHost/sites/site[@name='%1']/application[@path='%2']/virtualDirectory[@path='%3'] because the mapping with the relative virtual path, '%5' was already created for another virtual directory.
0xB0000036	A commit operation has been initiated.	A commit operation has been initiated.
0xB0000037	A commit operation has completed. The status code is: '%1'.	A commit operation has completed. The status code is: '%1'.
0xB0000038	A kernel transaction for a commit operation has been created.	A kernel transaction for a commit operation has been created.
0xB0000039	Failed to create a kernel transaction for the commit operation. The commit operation will proceed without a kernel transaction.	Failed to create a kernel transaction for the commit operation. The commit operation will proceed without a kernel transaction.
0xB000003A	Changes have successfully been committed with a kernel transaction.	Changes have successfully been committed with a kernel transaction.
0xB000003B	Failed to commit the changes with a kernel transaction. The changes will be reverted.	Failed to commit the changes with a kernel transaction. The changes will be reverted.
0xB000003C	A file write operation in a commit operation has been initiated.	A file write operation in a commit operation has been initiated.
0xB000003D	The contents of the file '%2' could not be erased. The operation will be tried '%4' more time(s).	The contents of the file '%2' could not be erased. The operation will be tried '%4' more time(s).
0xB000003E	The contents of the file '%2' have successfully been erased. The size of the file is now zero.	The contents of the file '%2' have successfully been erased. The size of the file is now zero.
0xB000003F	The new contents of the file '%2' could not be written to.	The new contents of the file '%2' could not be written to.
0xB0000040	A file write operation in a commit operation has completed. The status code is: '%1'.	A file write operation in a commit operation has completed. The status code is: '%1'.
0xB0000041	A change listener of type '%2' has been informed about a configuration change at '%3'.	A change listener of type '%2' has been informed about a configuration change at '%3'.
0xBC001838	date %2 time %3 s-sitename %6 s-computername %7 s-ip %8 cs-method %9 cs-uri-stem %10 cs-uri-query %11 s-port %17 cs-username %5 c-ip %4 cs-version %21 cs(User-Agent) %18 cs(Cookie) %19 cs(Referer) %20 cs-host %22 sc-status %12 sc-substatus %23 sc-win32-status %13 sc-bytes %14 cs-bytes %15 time-taken %16 %24	date %2 time %3 s-sitename %6 s-computername %7 s-ip %8 cs-method %9 cs-uri-stem %10 cs-uri-query %11 s-port %17 cs-username %5 c-ip %4 cs-version %21 cs(User-Agent) %18 cs(Cookie) %19 cs(Referer) %20 cs-host %22 sc-status %12 sc-substatus %23 sc-win32-status %13 sc-bytes %14 cs-bytes %15 time-taken %16 %24
0xC0000005	Error: %1.	Error: %1.
0xC0000006	Error: %1, %2.	Error: %1, %2.
0xC0000007	Error: %1, %2, %3.	Error: %1, %2, %3.
0xC0000008	Error: %1, %2, %3, %4.	Error: %1, %2, %3, %4.
0xC0000013	Failed to create an ASP Session due to Access Denied when activating COM+ Partition %1.	Failed to create an ASP Session due to Access Denied when activating COM+ Partition %1.
0xC0000014	Failed to create ASP Application %1 due to invalid or missing COM+ Partition ID.	Failed to create ASP Application %1 due to invalid or missing COM+ Partition ID.
0xC0000015	Failed to retrieve the Anonymous User Token for ASP Application %1. Global.ASA OnEnd routines will not be executed.	Failed to retrieve the Anonymous User Token for ASP Application %1. Global.ASA OnEnd routines will not be executed.
0xC0000016	Failed to impersonate the Anonymous User for ASP Application %1. Global.ASA OnEnd routines will not be executed.	Failed to impersonate the Anonymous User for ASP Application %1. Global.ASA OnEnd routines will not be executed.
0xC0000066	The server was unable to load ODBC32.DLL for sql logging due to the following error: %1 The data is the error code.	The server was unable to load ODBC32.DLL for sql logging due to the following error: %1 The data is the error code.
0xC0000067	The server was unable to open ODBC Data source %1, Table: %2, under UserName %3. The ODBC Error is: %4. The data is the error code.	The server was unable to open ODBC Data source %1, Table: %2, under UserName %3. The ODBC Error is: %4. The data is the error code.
0xC0000068	The parameters specified for logging are too long. Field: %1; Data Given: %2.	The parameters specified for logging are too long. Field: %1; Data Given: %2.
0xC0000069	The server was unable to register the administration tool discovery information. The administration tool may not be able to see this server. The data is the error code.	The server was unable to register the administration tool discovery information. The administration tool may not be able to see this server. The data is the error code.
0xC000006A	The Creation of InetLog Context failed. The data is the error code.	The Creation of InetLog Context failed. The data is the error code.
0xC000006B	Logging information failed. The log object was never created possibly due to wrong configuration.	Logging information failed. The log object was never created possibly due to wrong configuration.
0xC000006C	The server was unable to find the log file directory %1. The data is the error code.	The server was unable to find the log file directory %1. The data is the error code.
0xC000006D	The server has suspended request logging because an error occurred writing a log record. The data is the error code. The error code text is: %1.	The server has suspended request logging because an error occurred writing a log record. The data is the error code. The error code text is: %1.
0xC000006E	The server has resumed request logging.	The server has resumed request logging.
0xC000006F	The service could not initialize the socket library. The data is the error code.	The service could not initialize the socket library. The data is the error code.
0xC0000070	The service could not find module %1. The data is the error code.	The service could not find module %1. The data is the error code.
0xC0000073	The service could not bind instance %1. The data is the error code.	The service could not bind instance %1. The data is the error code.
0xC0000074	The service metabase path '%1' could not be opened. The data is the error code.	The service metabase path '%1' could not be opened. The data is the error code.
0xC00001F4	UNC Access failed for file - %s with the error = %d	UNC Access failed for file - %s with the error = %d
0xC00003EB	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The URL may be invalid. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The URL may be invalid. The site has been disabled. The data field contains the error number.
0xC00003EC	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The site has been disabled. The data field contains the error number.
0xC00003ED	The World Wide Web Publishing Service (WWW Service) is stopping because it encountered an error. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) is stopping because it encountered an error. The data field contains the error number.
0xC00003EF	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number.
0xC00003FA	The World Wide Web Publishing Service was not able to initialize performance counters. The service will run without the performance counters. Please restart the World Wide Web Publishing Service to reinitialize the performance counters. The data field contains the error number.	The World Wide Web Publishing Service was not able to initialize performance counters. The service will run without the performance counters. Please restart the World Wide Web Publishing Service to reinitialize the performance counters. The data field contains the error number.
0xC00003FC	The World Wide Web Publishing Service (WWW Service) failed to configure the HTTP.SYS control channel property '%1' properly. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to configure the HTTP.SYS control channel property '%1' properly. The data field contains the error number.
0xC0000402	The World Wide Web Publishing Service (WWW Service) encountered an error when it tried to secure the handle of application pool %1 from HTTP.sys. Edit the identification information for the application pool so that the WWW Service can secure the handle of the application pool again. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) encountered an error when it tried to secure the handle of application pool %1 from HTTP.sys. Edit the identification information for the application pool so that the WWW Service can secure the handle of the application pool again. The data field contains the error number.
0xC0000403	Application pool %1 has been disabled. The HTTP.sys request to enable the application pool failed. The data contains the error number.	Application pool %1 has been disabled. The HTTP.sys request to enable the application pool failed. The data contains the error number.
0xC0000405	The World Wide Web Publishing Service (WWW Service) did not configure bindings for an application in site %1. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not configure bindings for an application in site %1. The site has been disabled. The data field contains the error number.
0xC0000408	The World Wide Web Publishing Service (WWW Service) did not configure logging properties for site %1. The site's log file directory path may be a mapped network path. Using a mapped network path as the site's log file directory is not supported by IIS. Use a UNC path instead.	The World Wide Web Publishing Service (WWW Service) did not configure logging properties for site %1. The site's log file directory path may be a mapped network path. Using a mapped network path as the site's log file directory is not supported by IIS. Use a UNC path instead.
0xC0000409	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory may contain an invalid computer or share name.	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory may contain an invalid computer or share name.
0xC000040A	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The server does not have permission to access the site's log file directory.	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The server does not have permission to access the site's log file directory.
0xC000040B	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory is not fully qualified, which may be because it is missing the drive letter or other important information.	The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory is not fully qualified, which may be because it is missing the drive letter or other important information.
0xC000040D	The HTTP control channel for the World Wide Web Publishing Service (WWW Service) did not open. The data field contains the error number.	The HTTP control channel for the World Wide Web Publishing Service (WWW Service) did not open. The data field contains the error number.
0xC0000426	The World Wide Web Publishing Service (WWW Service) failed to configure the logging properties for the HTTP control channel. Logging Enabled is '%1'. Log File Directory is '%2'. Log Period is '%3'. Log Truncate Size is '%4'. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to configure the logging properties for the HTTP control channel. Logging Enabled is '%1'. Log File Directory is '%2'. Log Period is '%3'. Log Truncate Size is '%4'. The data field contains the error number.
0xC000043B	HTTP.SYS provided inconsistent site performance counter data to the World Wide Web Publishing Service (WWW Service), so the WWW Service will ignore the data.	HTTP.SYS provided inconsistent site performance counter data to the World Wide Web Publishing Service (WWW Service), so the WWW Service will ignore the data.
0xC000043C	Application pool %1 was not disabled. The HTTP.sys request to disable the application pool failed. The data contains the error number.	Application pool %1 was not disabled. The HTTP.sys request to disable the application pool failed. The data contains the error number.
0xC000043E	The World Wide Web Publishing Service failed to properly configure the load balancer capabilities on application pool '%1'. The data field contains the error number.	The World Wide Web Publishing Service failed to properly configure the load balancer capabilities on application pool '%1'. The data field contains the error number.
0xC000043F	The World Wide Web Publishing Service failed to properly configure the application pool queue length on app pool '%1'. The data field contains the error number.	The World Wide Web Publishing Service failed to properly configure the application pool queue length on app pool '%1'. The data field contains the error number.
0xC0000441	The World Wide Web Publishing Service (WWW Service) did not issue a demand start to HTTP.sys for application pool %1. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not issue a demand start to HTTP.sys for application pool %1. The data field contains the error number.
0xC0000447	The World Wide Web Publishing Service failed to delete the config group for the application '%1' in site '%2'. The data field contains the error number.	The World Wide Web Publishing Service failed to delete the config group for the application '%1' in site '%2'. The data field contains the error number.
0xC0000448	The World Wide Web Publishing Service failed to remove the urls for the application '%1' in virtual site '%2'. The data field contains the error number.	The World Wide Web Publishing Service failed to remove the urls for the application '%1' in virtual site '%2'. The data field contains the error number.
0xC0000449	The World Wide Web Publishing Service failed to set the application pool for the application '%1' in site '%2'. The data field contains the error number.	The World Wide Web Publishing Service failed to set the application pool for the application '%1' in site '%2'. The data field contains the error number.
0xC000044A	The World Wide Web Publishing Service failed to set the max connections for the virtual site '%1'. The data field contains the error number.	The World Wide Web Publishing Service failed to set the max connections for the virtual site '%1'. The data field contains the error number.
0xC000044B	The World Wide Web Publishing Service failed to set the connection timeout for the virtual site '%1'. The data field contains the error number.	The World Wide Web Publishing Service failed to set the connection timeout for the virtual site '%1'. The data field contains the error number.
0xC0000455	The World Wide Web Publishing Service (WWW Service) failed to set the filter configuration for the control channel. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to set the filter configuration for the control channel. The data field contains the error number.
0xC0000460	The World Wide Web Publishing Service (WWW Service) failed to obtain cache counters from HTTP.SYS. The performance counters that were reported do not include performance counters for this gathering from HTTP.SYS. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to obtain cache counters from HTTP.SYS. The performance counters that were reported do not include performance counters for this gathering from HTTP.SYS. The data field contains the error number.
0xC0000461	The World Wide Web Publishing Service (WWW Service) failed to obtain site performance counters from HTTP.SYS. The performance counters that were reported do not include counters for this gathering from HTTP.SYS. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to obtain site performance counters from HTTP.SYS. The performance counters that were reported do not include counters for this gathering from HTTP.SYS. The data field contains the error number.
0xC0000462	The World Wide Web Publishing Service (WWW Service) failed to publish the performance counters that it gathered from HTTP.SYS. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to publish the performance counters that it gathered from HTTP.SYS. The data field contains the error number.
0xC0000463	The World Wide Web Publishing Service (WWW Service) failed to cancel the timer for gathering performance counters. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to cancel the timer for gathering performance counters. The data field contains the error number.
0xC0000464	The World Wide Web Publishing Service (WWW Service) failed to cancel the timer for the performance counter. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to cancel the timer for the performance counter. The data field contains the error number.
0xC0000465	The World Wide Web Publishing Service (WWW Service) failed to start the timer for gathering performance counters. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to start the timer for gathering performance counters. The data field contains the error number.
0xC0000466	The World Wide Web Publishing Service (WWW Service) failed to copy a change notification for processing, so the service may not be in sync with data currently in the IIS configuration store. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to copy a change notification for processing, so the service may not be in sync with data currently in the IIS configuration store. The data field contains the error number.
0xC0000468	The World Wide Web Publishing Service (WWW Service) failed to initialize ASP performance counters. The service will run without ASP performance counters. Restart the WWW Service to start ASP performance counter gathering. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to initialize ASP performance counters. The service will run without ASP performance counters. Restart the WWW Service to start ASP performance counter gathering. The data field contains the error number.
0xC0000469	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. Either the network endpoint for the site's IP address could not be created or the IP listen list for HTTP.sys did not have any usable IP addresses. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. Either the network endpoint for the site's IP address could not be created or the IP listen list for HTTP.sys did not have any usable IP addresses. The site has been disabled. The data field contains the error number.
0xC000046A	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The IP address for the site is not in the HTTP.sys IP listen list. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The IP address for the site is not in the HTTP.sys IP listen list. The site has been disabled. The data field contains the error number.
0xC000046B	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. HTTP.sys has been configured to listen to too many ports. The site has been disabled. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. HTTP.sys has been configured to listen to too many ports. The site has been disabled. The data field contains the error number.
0xC000046E	The World Wide Web Publishing Service (WWW Service) failed to configure centralized W3C logging properly. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to configure centralized W3C logging properly. The data field contains the error number.
0xC000046F	The World Wide Web Publishing Service (WWW Service) failed to configure the centralized W3C logging properties on the HTTP control channel. Logging Enabled is '%1'. Log File Directory is '%2'. Log Period is '%3'. Log Truncate Size is '%4'. Log Ext File Flags is '%5'. Local Time Rollover is '%6'. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to configure the centralized W3C logging properties on the HTTP control channel. Logging Enabled is '%1'. Log File Directory is '%2'. Log Period is '%3'. Log Truncate Size is '%4'. Log Ext File Flags is '%5'. Local Time Rollover is '%6'. The data field contains the error number.
0xC0000490	The World Wide Web Publishing Service (WWW Service) did not create a relationship between %1 and application %2 in site %3. The site will be stopped because the WWW Service cannot notify HTTP.sys about the application. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not create a relationship between %1 and application %2 in site %3. The site will be stopped because the WWW Service cannot notify HTTP.sys about the application. The data field contains the error number.
0xC0000495	The World Wide Web Publishing Service (WWW Service) did not initialize the HTTP driver, and was unable start. Please verify that the HTTP service is in an executable state. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) did not initialize the HTTP driver, and was unable start. Please verify that the HTTP service is in an executable state. The data field contains the error number.
0xC0000496	The World Wide Web Publishing Service (WWW Service) failed to create binding string for site %1. Please verify that site binding (%2) is in correct format and do not contain any invalid characters.	The World Wide Web Publishing Service (WWW Service) failed to create binding string for site %1. Please verify that site binding (%2) is in correct format and do not contain any invalid characters.
0xC0000497	The World Wide Web Publishing Service (WWW Service) failed to enable end point sharing for the HTTP control channel. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to enable end point sharing for the HTTP control channel. The data field contains the error number.
0xC0000498	The World Wide Web Publishing Service (WWW Service) failed to start dynamic site registration handler. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to start dynamic site registration handler. The data field contains the error number.
0xC0000499	The World Wide Web Publishing Service (WWW Service) failed to update dynamic site registration handler from configuration change. The data field contains the error number.	The World Wide Web Publishing Service (WWW Service) failed to update dynamic site registration handler from configuration change. The data field contains the error number.
0xC00007D0	Unable to query the W3SVC (HTTP) service performance data. The error code returned by the service is data DWORD 0.	Unable to query the W3SVC (HTTP) service performance data. The error code returned by the service is data DWORD 0.
0xC00007D1	It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.	It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.
0xC00007D2	Setting up Web Service counters failed, please make sure your Web Service counters are registered correctly.	Setting up Web Service counters failed, please make sure your Web Service counters are registered correctly.
0xC00007D3	It has taken too long to refresh the W3SVC counters, the stale counters are being used instead. This is the second message within the past %1 (hours, minutes, seconds). No more stale counter messages will be logged for this client session until the time limit expires. %nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://go.microsoft.com/fwlink?linkid=538.	It has taken too long to refresh the W3SVC counters, the stale counters are being used instead. This is the second message within the past %1 (hours, minutes, seconds). No more stale counter messages will be logged for this client session until the time limit expires. %nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://go.microsoft.com/fwlink?linkid=538.
0xC0000899	HTTP Server could not initialize its security. The data is the error.	HTTP Server could not initialize its security. The data is the error.
0xC000089B	HTTP Server could not initialize the socket library. The data is the error.	HTTP Server could not initialize the socket library. The data is the error.
0xC000089C	HTTP Server was unable to initialize due to a shortage of available memory. The data is the error.	HTTP Server was unable to initialize due to a shortage of available memory. The data is the error.
0xC000089E	HTTP Server could not create the main connection socket. The data is the error.	HTTP Server could not create the main connection socket. The data is the error.
0xC00008A0	HTTP Server could not create a client connection object for user at host %1. The connection to this user is terminated. The data is the error.	HTTP Server could not create a client connection object for user at host %1. The connection to this user is terminated. The data is the error.
0xC00008A6	The HTTP Filter DLL %1 failed to load. The data is the error.	The HTTP Filter DLL %1 failed to load. The data is the error.
0xC00008A8	The script started from the URL '%1' has not responded within the configured timeout period. The HTTP server is terminating the script.	The script started from the URL '%1' has not responded within the configured timeout period. The HTTP server is terminating the script.
0xC00008AA	The HTTP server encountered an error processing the server side include file '%1'.The error was '%2'.	The HTTP server encountered an error processing the server side include file '%1'.The error was '%2'.
0xC00008AB	The HTTP server encountered an unhandled exception while processing the ISAPI Application '%1'.	The HTTP server encountered an unhandled exception while processing the ISAPI Application '%1'.
0xC00008AC	The HTTP server was unable to load the ISAPI Application '%1'. The data is the error.	The HTTP server was unable to load the ISAPI Application '%1'. The data is the error.
0xC00008AD	A server side include file has included itself or the maximum depth of server side includes has been exceeded.	A server side include file has included itself or the maximum depth of server side includes has been exceeded.
0xC00008B3	The server was unable to acquire a license for a SSL connection.	The server was unable to acquire a license for a SSL connection.
0xC00008BE	Job object query failed. The data is the error.	Job object query failed. The data is the error.
0xC00008BF	Job object set limit failed. The data is the error.	Job object set limit failed. The data is the error.
0xC00008C0	Schedule a work item for CPU Accounting or Limits failed. The data is the error.	Schedule a work item for CPU Accounting or Limits failed. The data is the error.
0xC00008D3	The COM Application '%1' at '%2' failed to activate out of process.	The COM Application '%1' at '%2' failed to activate out of process.
0xC00008D5	An attempt was made to load filter '%1' but it requires the SF_NOTIFY_READ_RAW_DATA filter notification and this notification is not supported in this IIS version.	An attempt was made to load filter '%1' but it requires the SF_NOTIFY_READ_RAW_DATA filter notification and this notification is not supported in this IIS version.
0xC00008DC	Could not load all ISAPI filters for site '%1'. Therefore site startup aborted.	Could not load all ISAPI filters for site '%1'. Therefore site startup aborted.
0xC00008DD	The worker process for app pool '%1', PID='%2', failed to initialize the http.sys communication when asked to start processing http requests and therefore will be considered ill by W3SVC and terminated. The data field contains the error number.	The worker process for app pool '%1', PID='%2', failed to initialize the http.sys communication when asked to start processing http requests and therefore will be considered ill by W3SVC and terminated. The data field contains the error number.
0xC00008DE	IIS Client certificate mapping configuration for site %1 failed to be loaded. The data field contains the error number.	IIS Client certificate mapping configuration for site %1 failed to be loaded. The data field contains the error number.
0xC00008DF	Could not initialize the logging module for site %1. The site will therefore be non-functional.	Could not initialize the logging module for site %1. The site will therefore be non-functional.
0xC00008E2	ISAPI Filter '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.	ISAPI Filter '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
0xC00008E4	The worker process failed to initialize correctly and therefore could not be started. The data is the error.	The worker process failed to initialize correctly and therefore could not be started. The data is the error.
0xC00008E8	The Module DLL %1 failed to load. The data is the error.	The Module DLL %1 failed to load. The data is the error.
0xC00008E9	The worker process failed to initialize communication with the W3SVC and therefore could not be started. The data is the error.	The worker process failed to initialize communication with the W3SVC and therefore could not be started. The data is the error.
0xC00008EA	The Module DLL '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.	The Module DLL '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
0xC00008F5	The Module name %1 path %2 returned an error from registration. The data is the error.	The Module name %1 path %2 returned an error from registration. The data is the error.
0xC00008F6	The worker process failed to pre-load .Net Runtime version %1.	The worker process failed to pre-load .Net Runtime version %1.
0xC00008F7	Failed to find the RegisterModule entrypoint in the module DLL %1. The data is the error.	Failed to find the RegisterModule entrypoint in the module DLL %1. The data is the error.
0xC00008F8	The Module name '%1' path '%2' has an invalid precondition '%3'.	The Module name '%1' path '%2' has an invalid precondition '%3'.
0xC00008F9	The worker process for application pool '%1' encountered an error '%2' trying to read global module configuration data from file '%3', line number '%4'. Worker process startup aborted.	The worker process for application pool '%1' encountered an error '%2' trying to read global module configuration data from file '%3', line number '%4'. Worker process startup aborted.
0xC00008FB	An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: %1. The data is the error.	An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: %1. The data is the error.
0xC00008FE	There was an error during processing of the managed application service auto-start for configuration path: '%1'. The error message returned is: '%2'. The worker process will be marked unhealthy and be shutdown. The data field contains the error code.	There was an error during processing of the managed application service auto-start for configuration path: '%1'. The error message returned is: '%2'. The worker process will be marked unhealthy and be shutdown. The data field contains the error code.
0xC0000900	There was an unexpected error during the loading of managed runtime version: '%1'. The managed runtime loader '%2' was unable to load the managed runtime. The data field contains the error code.	There was an unexpected error during the loading of managed runtime version: '%1'. The managed runtime loader '%2' was unable to load the managed runtime. The data field contains the error code.
0xC0000903	The worker process for application pool '%1' encountered an error '%2' trying to read configuration data from file '%3', line number '%4'. The data field contains the error code.	The worker process for application pool '%1' encountered an error '%2' trying to read configuration data from file '%3', line number '%4'. The data field contains the error code.
0xC0000904	The loghttp module in the worker process with id '%2' could not obtain custom log data for '%1' requests. The data field contains the error code.	The loghttp module in the worker process with id '%2' could not obtain custom log data for '%1' requests. The data field contains the error code.
0xC0000905	The loghttp module in the worker process with id '%2' removed custom log data for '%1' request(s) which was not claimed by the W3C Logging Service.	The loghttp module in the worker process with id '%2' removed custom log data for '%1' request(s) which was not claimed by the W3C Logging Service.
0xC00009C5	Error processing SSI file	Error processing SSI file
0xC00009C6	Invalid SSI Tag	Invalid SSI Tag
0xC00009C7	Cannot perform flastmod(): Win32 Error Code = %2!.20s!	Cannot perform flastmod(): Win32 Error Code = %2!.20s!
0xC00009C8	Cannot perform fsize(): Win32 Error Code = %2!.20s!	Cannot perform fsize(): Win32 Error Code = %2!.20s!
0xC00009C9	Variable '%1!.40s!' cannot be found	Variable '%1!.40s!' cannot be found
0xC00009CA	Variable '%1!.40s!' cannot be evaluated	Variable '%1!.40s!' cannot be evaluated
0xC00009CB	SSI feature not supported	SSI feature not supported
0xC00009CC	Error handling SSI File : Win32 Error Code = %2!.20s!	Error handling SSI File : Win32 Error Code = %2!.20s!
0xC00009CD	Failed to process SSI file	Failed to process SSI file
0xC00009CE	Failed to execute CMD : Win32 Error Code = %2!.20s!	Failed to execute CMD : Win32 Error Code = %2!.20s!
0xC00009CF	Failed to execute CGI : Win32 Error Code = %2!.20s!	Failed to execute CGI : Win32 Error Code = %2!.20s!
0xC00009D0	Failed to execute ISAPI extension : Win32 Error Code = %2!.20s!	Failed to execute ISAPI extension : Win32 Error Code = %2!.20s!
0xC00009D1	Cannot #EXEC file due to lack of EXECUTE permission	Cannot #EXEC file due to lack of EXECUTE permission
0xC00009D2	Cannot process file due to access denied	Cannot process file due to access denied
0xC00009D4	The CMD option is not enabled for #EXEC calls	The CMD option is not enabled for #EXEC calls
0xC00009D5	#EXEC calls have been disabled for this virtual path	#EXEC calls have been disabled for this virtual path
0xC00009D6	There is a recursive #INCLUDE chain	There is a recursive #INCLUDE chain
0xC00009D7	Failed to execute script: Http Status Code = %2!.20s!	Failed to execute script: Http Status Code = %2!.20s!
0xC0000A2A	The form you just filled in requires the %1 entry to be filled in. Please fill in that entry in the form and resubmit the form.	The form you just filled in requires the %1 entry to be filled in. Please fill in that entry in the form and resubmit the form.
0xC0000A2B	The query file could not be opened. The file may not exist or you may have insufficient permission to open the file.	The query file could not be opened. The file may not exist or you may have insufficient permission to open the file.
0xC0000A2D	The template file contains an else tag without a matching if tag.	The template file contains an else tag without a matching if tag.
0xC0000A2E	The template file contains an endif tag without a matching if tag.	The template file contains an endif tag without a matching if tag.
0xC0000A2F	The template file contains an expression with parameters that are of different type. For example, an if tag comparing a string with a number would cause this error.	The template file contains an expression with parameters that are of different type. For example, an if tag comparing a string with a number would cause this error.
0xC0000A30	The template file contains an expression using the CONTAINS operator where one or both parameters are not strings. CONTAINS is only valid with string values.	The template file contains an expression using the CONTAINS operator where one or both parameters are not strings. CONTAINS is only valid with string values.
0xC0000A31	The template file contains an expression that uses a quoted string but the close quote is missing.	The template file contains an expression that uses a quoted string but the close quote is missing.
0xC0000A32	The template file contains an expression with an unrecognized operator. Valid operators are GT, LT, EQ and CONTAINS.	The template file contains an expression with an unrecognized operator. Valid operators are GT, LT, EQ and CONTAINS.
0xC0000A33	The query file contains an unrecognized field %1.	The query file contains an unrecognized field %1.
0xC0000A34	The query file must contain a valid, non-empty Datasource: field and SQLStatement: field.	The query file must contain a valid, non-empty Datasource: field and SQLStatement: field.
0xC0000A35	Content-type: text/htmlThe page cannot be displayedThe library odbc32.dll could not be loaded to perform the query. Make sure ODBC has been properly installed on the server.	Content-type: text/htmlThe page cannot be displayedThe library odbc32.dll could not be loaded to perform the query. Make sure ODBC has been properly installed on the server.
0xC0000A37	Content-type: text/htmlThe page cannot be displayedError performing query.%1	Content-type: text/htmlThe page cannot be displayedError performing query.%1
0xC0000A38	The maximum number of SQLStatement fields in the IDC file has been exceeded.	The maximum number of SQLStatement fields in the IDC file has been exceeded.
0xC0000A8C	Configuration file '%1' does not contain a root tag	Configuration file '%1' does not contain a root tag
0xC0000A8D	Configuration file is not well-formed XML	Configuration file is not well-formed XML
0xC0000A8E	Only one element allowed. It must be the first child element of the root element	Only one element allowed. It must be the first child element of the root element
0xC0000A8F	Unrecognized element '%1'	Unrecognized element '%1'
0xC0000A90	Unrecognized attribute '%1'	Unrecognized attribute '%1'
0xC0000A91	The '%1' attribute must be one of the following values: %2	The '%1' attribute must be one of the following values: %2
0xC0000A92	The '%1' attribute must be specfied on the '%2' tag	The '%1' attribute must be specfied on the '%2' tag
0xC0000A93	There is a duplicate '%1' section defined	There is a duplicate '%1' section defined
0xC0000A94	There is a duplicate '%1' section group defined	There is a duplicate '%1' section group defined
0xC0000A95	The configuration section '%1' cannot be read because it is missing a section declaration	The configuration section '%1' cannot be read because it is missing a section declaration
0xC0000A96	Error parsing the schema file: %1	Error parsing the schema file: %1
0xC0000A97	Missing required attribute '%1'	Missing required attribute '%1'
0xC0000A98	Cannot add duplicate collection entry	Cannot add duplicate collection entry
0xC0000A99	Attribute '%1' has already been set	Attribute '%1' has already been set
0xC0000A9A	Configuration element '%1' already defined	Configuration element '%1' already defined
0xC0000A9B	This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=\"Deny\"), or set explicitly by a location tag with overrideMode=\"Deny\" or the legacy allowOverride=\"false\".	This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=\"Deny\"), or set explicitly by a location tag with overrideMode=\"Deny\" or the legacy allowOverride=\"false\".
0xC0000A9C	Config section '%1' already defined. Sections must only appear once per config file. See the help topic for exceptions	Config section '%1' already defined. Sections must only appear once per config file. See the help topic for exceptions
0xC0000A9D	String value must not be empty string	String value must not be empty string
0xC0000A9E	Timespan value must be between %1 and %2 seconds. Its granularity must be %3 seconds	Timespan value must be between %1 and %2 seconds. Its granularity must be %3 seconds
0xC0000A9F	Integer value must be between %1 and %2	Integer value must be between %1 and %2
0xC0000AA0	section path attributes must be unique per config file	section path attributes must be unique per config file
0xC0000AA1	lockAttributes contains unknown attribute '%1'	lockAttributes contains unknown attribute '%1'
0xC0000AA2	Only one of 'lockAttributes'/'lockAllAttributesExcept' must be specified	Only one of 'lockAttributes'/'lockAllAttributesExcept' must be specified
0xC0000AA3	lockAllAttributesExcept contains no known attributes	lockAllAttributesExcept contains no known attributes
0xC0000AA4	lockElements contains unknown element '%1'	lockElements contains unknown element '%1'
0xC0000AA5	Only one of 'lockElements'/'lockAllElementsExcept' must be specified	Only one of 'lockElements'/'lockAllElementsExcept' must be specified
0xC0000AA6	Lock violation	Lock violation
0xC0000AA7	lockItem must be either true/false	lockItem must be either true/false
0xC0000AA9	element can only contain	element can only contain
0xC0000AAA	Can not have duplicate provider names	Can not have duplicate provider names
0xC0000AAB	Encryption provider must specify 'name' attribute	Encryption provider must specify 'name' attribute
0xC0000AAC	Encryption provider must specify 'type' attribute	Encryption provider must specify 'type' attribute
0xC0000AAD	Failed to decrypt attribute '%1'	Failed to decrypt attribute '%1'
0xC0000AAE	Location path contains invalid characters	Location path contains invalid characters
0xC0000AAF	Can not find matching virtual directory	Can not find matching virtual directory
0xC0000AB0	Can not log on locally to %1 as user %2 with virtual directory password	Can not log on locally to %1 as user %2 with virtual directory password
0xC0000AB1	Configuration section not allowed in a tag	Configuration section not allowed in a tag
0xC0000AB2	Configuration section not allowed to be set below application	Configuration section not allowed to be set below application
0xC0000AB3	Configuration section can only be set in ApplicationHost.config	Configuration section can only be set in ApplicationHost.config
0xC0000AB4	Unrecognized configuration path '%1'	Unrecognized configuration path '%1'
0xC0000AB5	Timespan must be of form [-][d.]hh:mm:ss[.ff]	Timespan must be of form [-][d.]hh:mm:ss[.ff]
0xC0000AB6	Not a valid integer	Not a valid integer
0xC0000AB7	Boolean must be either 'true' or 'false'	Boolean must be either 'true' or 'false'
0xC0000AB8	The '%1' attribute is invalid. %2	The '%1' attribute is invalid. %2
0xC0000AB9	Enum must be one of %1	Enum must be one of %1
0xC0000ABA	Flags must be some combination of %1	Flags must be some combination of %1
0xC0000ABB	Timespan value must be between %1 and %2 seconds inclusive, with a granularity of %3 seconds	Timespan value must be between %1 and %2 seconds inclusive, with a granularity of %3 seconds
0xC0000ABC	Integer value must be between %1 and %2 inclusive	Integer value must be between %1 and %2 inclusive
0xC0000ABD	String must not be empty	String must not be empty
0xC0000ABE	configSource must exist alone in an element	configSource must exist alone in an element
0xC0000ABF	configSource not allowed in element	configSource not allowed in element
0xC0000AC0	Specified configSource cannot be parsed	Specified configSource cannot be parsed
0xC0000AC1	configSource must only be specified at an empty element	configSource must only be specified at an empty element
0xC0000AC2	Element is missing required attributes %1	Element is missing required attributes %1
0xC0000AC3	Must specify only one lockdown directive ('allowOverride' or 'overrideMode')	Must specify only one lockdown directive ('allowOverride' or 'overrideMode')
0xC0000AC4	Location path ends with an invalid character	Location path ends with an invalid character
0xC0000AC5	Cannot read configuration file	Cannot read configuration file
0xC0000AC6	String value must not start or end with white space	String value must not start or end with white space
0xC0000AC7	Cannot overwrite defaultProvider	Cannot overwrite defaultProvider
0xC0000AC8	Invalid application pool name	Invalid application pool name
0xC0000AC9	Invalid site name	Invalid site name
0xC0000ACA	Missing required element '%1'	Missing required element '%1'
0xC0000ACB	Invalid section name '%1'	Invalid section name '%1'
0xC0000ACC	lockAllElementsExcept contains no known elements	lockAllElementsExcept contains no known elements
0xC0000ACD	Filename: %1Line number: %2Error: %3	Filename: %1Line number: %2Error: %3
0xC0000ACE	The attribute '%1' is required and cannot be locked.	The attribute '%1' is required and cannot be locked.
0xC0000ACF	Integer value must not be between %1 and %2 inclusive	Integer value must not be between %1 and %2 inclusive
0xC0000AD0	Timespan value must not be between %1 and %2 seconds inclusive, with a granularity of %3 seconds	Timespan value must not be between %1 and %2 seconds inclusive, with a granularity of %3 seconds
0xC0000AD1	Invalid application path	Invalid application path
0xC0000AD2	Invalid virtual directory path	Invalid virtual directory path
0xC0000AD3	Expected element '%1'	Expected element '%1'
0xC0000AD4	Cannot overwrite %1 behavior in collections with multiple element schemas	Cannot overwrite %1 behavior in collections with multiple element schemas
0xC0000AD5	Collection defaults not allowed for this collection	Collection defaults not allowed for this collection
0xC0000AD6	Add/remove/clear element '%1' already specified for this collection	Add/remove/clear element '%1' already specified for this collection
0xC0000AD7	Could not find collection's defaultElement	Could not find collection's defaultElement
0xC0000AD8	Validation parameter '%1' is invalid	Validation parameter '%1' is invalid
0xC0000AD9	Both '%1' and '%2' can not be specified	Both '%1' and '%2' can not be specified
0xC0000ADA	Schema for '%1' already exists	Schema for '%1' already exists
0xC0000ADB	Failed to open schema file '%1'	Failed to open schema file '%1'
0xC0000ADC	Configuration section can only be set in machine.config	Configuration section can only be set in machine.config
0xC0000ADD	Configuration section can only be set in machine.config or root web.config	Configuration section can only be set in machine.config or root web.config
0xC0000ADE	Not a valid unsigned integer	Not a valid unsigned integer
0xC0000ADF	Cannot read configuration file due to insufficient permissions	Cannot read configuration file due to insufficient permissions
0xC0000AE0	Macro '%1' is not defined	Macro '%1' is not defined
0xC0000AE1	Only one '%1' element must be specified	Only one '%1' element must be specified
0xC0000AE2	No suitable default for given attribute	No suitable default for given attribute
0xC0000AE3	This configuration section cannot be modified at this path because allowSubDirConfig=\"false\" is set on the parent virtual directory	This configuration section cannot be modified at this path because allowSubDirConfig=\"false\" is set on the parent virtual directory
0xC0000AE4	Cannot read configuration file because it exceeds the maximum file size	Cannot read configuration file because it exceeds the maximum file size
0xC0000AE5	Failed to decrypt attribute '%1' because the keyset does not exist	Failed to decrypt attribute '%1' because the keyset does not exist
0xC0000AE6	Cannot add duplicate collection entry of type '%1' with unique key attribute '%2' set to '%3'	Cannot add duplicate collection entry of type '%1' with unique key attribute '%2' set to '%3'
0xC0000AE7	Cannot add duplicate collection entry of type '%1' with unique key attributes '%2' respectively set to '%3'	Cannot add duplicate collection entry of type '%1' with unique key attributes '%2' respectively set to '%3'
0xC0000AE8	Cannot add duplicate collection entry of type '%1' with combined key attributes '%2' respectively set to '%3'	Cannot add duplicate collection entry of type '%1' with combined key attributes '%2' respectively set to '%3'
0xC0000AE9	Cannot add duplicate collection entry of type '%1' with unique key attribute '%2' set to '%3' and combined key attributes '%4' respectively set to '%5'	Cannot add duplicate collection entry of type '%1' with unique key attribute '%2' set to '%3' and combined key attributes '%4' respectively set to '%5'
0xC0000AEA	Cannot add duplicate collection entry of type '%1' with unique key attributes '%2' respectively set to '%3' and combined key attributes '%4' respectively set to '%5'	Cannot add duplicate collection entry of type '%1' with unique key attributes '%2' respectively set to '%3' and combined key attributes '%4' respectively set to '%5'
0xC0000AEB	The root element of a childSource configuration file cannot have any attributes	The root element of a childSource configuration file cannot have any attributes
0xC0000AEC	There is a duplicate flag name '%1' defined	There is a duplicate flag name '%1' defined
0xC0000AED	There is a duplicate enumeration name '%1' defined	There is a duplicate enumeration name '%1' defined
0xC0000AEE	Attribute '%1' is not part of a collection element. Therefore '%2' cannot be 'true'	Attribute '%1' is not part of a collection element. Therefore '%2' cannot be 'true'
0xC0000AEF	Configuration section encryption is not supported	Configuration section encryption is not supported
0xC0000AF0	The configuration section '%1' cannot be read because it is missing schema	The configuration section '%1' cannot be read because it is missing schema
0xC0000AF1	Can not log on locally to %1 as user %2 with redirection.config password	Can not log on locally to %1 as user %2 with redirection.config password
0xC0000AF2	Cannot read configuration file because the network path is not found	Cannot read configuration file because the network path is not found
0xC0000AF3	Cannot commit configuration changes because the file has changed on disk	Cannot commit configuration changes because the file has changed on disk
0xC0000AF4	This configuration section cannot be modified because it has been opened for read only access	This configuration section cannot be modified because it has been opened for read only access
0xC0000AF5	Cannot write configuration file due to insufficient permissions	Cannot write configuration file due to insufficient permissions
0xC0000AF6	Filename: %1Error: %2	Filename: %1Error: %2
0xC0000AF7	Cannot write configuration file	Cannot write configuration file
0xC0000AF8	Invalid validationType '%1'	Invalid validationType '%1'
0xC0000FA8	Failed to process input.	Failed to process input.
0xC0000FA9	Failed to initialize the COM subsystem (HRESULT=%%08x).	Failed to initialize the COM subsystem (HRESULT=%%08x).
0xC0000FAA	Failed to obtain the executable handle (HRESULT=%%08x).	Failed to obtain the executable handle (HRESULT=%%08x).
0xC0000FAB	Failed to initialize command processor: %%ws (HRESULT=%%08x).	Failed to initialize command processor: %%ws (HRESULT=%%08x).
0xC0000FAC	Please specify an object. Run 'appcmd.exe' to display supported objects.	Please specify an object. Run 'appcmd.exe' to display supported objects.
0xC0000FAD	Object '%ws' is not supported. Run 'appcmd.exe /?' to display supported objects.	Object '%ws' is not supported. Run 'appcmd.exe /?' to display supported objects.
0xC0000FAE	Command '%ws' is not supported on object '%ws'. Run 'appcmd.exe %ws /?'to display supported commands.	Command '%ws' is not supported on object '%ws'. Run 'appcmd.exe %ws /?'to display supported commands.
0xC0000FAF	Failed to setup command processor (HRESULT=%%08x).	Failed to setup command processor (HRESULT=%%08x).
0xC0000FB0	Failed to obtain output filters.	Failed to obtain output filters.
0xC0000FB1	Failed to obtain input for command: %0	Failed to obtain input for command: %0
0xC0000FB5	Command execution failed.	Command execution failed.
0xC0000FB6	Failed to generate item output.	Failed to generate item output.
0xC0000FB7	Failed to commit configuration changes.	Failed to commit configuration changes.
0xC0000FB8	Failed to process input: %%ws (HRESULT=%%08x).	Failed to process input: %%ws (HRESULT=%%08x).
0xC0000FB9	The parameter '%1' must begin with a / or -%0	The parameter '%1' must begin with a / or -%0
0xC0000FBA	The /text parameter is not allowed when using /xml or /config%0	The /text parameter is not allowed when using /xml or /config%0
0xC0000FBB	Too many parameters to display%0	Too many parameters to display%0
0xC0000FBC	Unknown tool parameter '%1'%0	Unknown tool parameter '%1'%0
0xC0000FBD	Invalid XML input - please make sure that your XML is well-formed and follows the required format%0	Invalid XML input - please make sure that your XML is well-formed and follows the required format%0
0xC0000FBE	(required)%0	(required)%0
0xC0000FBF	Duplicate parameters passed: %1	Duplicate parameters passed: %1
0xC000138A	Application pool '%1' is being automatically disabled due to a series of failures in the process(es) serving that application pool.	Application pool '%1' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
0xC000138D	Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.	Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.
0xC000138E	WAS_NOT_USED_5006	WAS_NOT_USED_5006
0xC0001397	A process serving application pool '%1' was orphaned but the specified orphan action %2 could not be executed. The data field contains the error number.	A process serving application pool '%1' was orphaned but the specified orphan action %2 could not be executed. The data field contains the error number.
0xC00013A0	Virtual site '%1' is configured to truncate its log every '%2' bytes. Since this value must be at least 1048576 bytes ( 1 megabyte ), 1048576 bytes will be used.	Virtual site '%1' is configured to truncate its log every '%2' bytes. Since this value must be at least 1048576 bytes ( 1 megabyte ), 1048576 bytes will be used.
0xC00013A4	The Windows Process Activation Service failed to add the worker process '%1' to the job object representing application pool '%2'. The data field contains the error number.	The Windows Process Activation Service failed to add the worker process '%1' to the job object representing application pool '%2'. The data field contains the error number.
0xC00013A6	Windows Process Activation Service terminated unexpectedly and the system was not configured to restart it. The Windows Process Activation Service has shut down.	Windows Process Activation Service terminated unexpectedly and the system was not configured to restart it. The Windows Process Activation Service has shut down.
0xC00013AC	The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number.	The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number.
0xC00013BD	The Windows Process Activation Service received a change notification, but was unable to process it correctly. The data field contains the error number.	The Windows Process Activation Service received a change notification, but was unable to process it correctly. The data field contains the error number.
0xC00013BE	Windows Process Activation Service (WAS) did not run the automatic shutdown executable %2 for application pool %1. The data field contains the error number.	Windows Process Activation Service (WAS) did not run the automatic shutdown executable %2 for application pool %1. The data field contains the error number.
0xC00013C3	Application pool %1 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.	Application pool %1 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
0xC00013C4	The job object associated with application pool '%1' encountered an error during configuration. CPU monitoring may not function as expected. The data field contains the error number.	The job object associated with application pool '%1' encountered an error during configuration. CPU monitoring may not function as expected. The data field contains the error number.
0xC00013C5	The job object attached to application pool '%1' failed to start its timer. The application pool's CPU usage is being monitored and will eventually reach the limit and report a failure. The data field contains the error number.	The job object attached to application pool '%1' failed to start its timer. The application pool's CPU usage is being monitored and will eventually reach the limit and report a failure. The data field contains the error number.
0xC00013C7	The Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications. The data field contains the error number.	The Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications. The data field contains the error number.
0xC00013C8	The Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications during recovery from inetinfo terminating unexpectedly. While the Windows Process Activation Service will continue to run, it is highly probable that it is no longer using current metabase data. Please restart the Windows Process Activation Service to correct this condition. The data field contains the error number.	The Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications during recovery from inetinfo terminating unexpectedly. While the Windows Process Activation Service will continue to run, it is highly probable that it is no longer using current metabase data. Please restart the Windows Process Activation Service to correct this condition. The data field contains the error number.
0xC00013CA	The Windows Process Activation Service encountered an error attempting to configure centralized logging. It is not configured as expected. The data field contains the error number.	The Windows Process Activation Service encountered an error attempting to configure centralized logging. It is not configured as expected. The data field contains the error number.
0xC00013DD	The Windows Process Activation Service (WAS) did not apply configuration changes to application pool %1. The data field contains the error number.	The Windows Process Activation Service (WAS) did not apply configuration changes to application pool %1. The data field contains the error number.
0xC00013E0	The Windows Process Activation Service failed to properly configure the job object for application pool '%1'. The data field contains the error number.	The Windows Process Activation Service failed to properly configure the job object for application pool '%1'. The data field contains the error number.
0xC00013E3	The Windows Process Activation Service (WAS) did not run the automatic shutdown executable for application pool %1. The data field contains the error number.	The Windows Process Activation Service (WAS) did not run the automatic shutdown executable for application pool %1. The data field contains the error number.
0xC00013E4	The Windows Process Activation Service failed to issue a request for the worker process '%2' of application pool '%1' to supply its performance counters. The data field contains the error number.	The Windows Process Activation Service failed to issue a request for the worker process '%2' of application pool '%1' to supply its performance counters. The data field contains the error number.
0xC00013E5	The Windows Process Activation Service failed to overlap recycle for application pool '%1' worker process '%2'. The data field contains the error number.	The Windows Process Activation Service failed to overlap recycle for application pool '%1' worker process '%2'. The data field contains the error number.
0xC00013E6	The Windows Process Activation Service failed to disassociate the application '%1' from the virtual site '%2'. The data field contains the error number.	The Windows Process Activation Service failed to disassociate the application '%1' from the virtual site '%2'. The data field contains the error number.
0xC00013EC	The Windows Process Activation Service failed to create the application '%2' in site '%1'. The data field contains the error number.	The Windows Process Activation Service failed to create the application '%2' in site '%1'. The data field contains the error number.
0xC00013ED	The Windows Process Activation Service (WAS) did not create application pool %1. The data field contains the error number.	The Windows Process Activation Service (WAS) did not create application pool %1. The data field contains the error number.
0xC00013EE	Windows Process Activation Service (WAS) did not create site %1. The data field contains the error number.	Windows Process Activation Service (WAS) did not create site %1. The data field contains the error number.
0xC00013EF	The Windows Process Activation Service failed to delete the application '%2' in site '%1'. The data field contains the error number.	The Windows Process Activation Service failed to delete the application '%2' in site '%1'. The data field contains the error number.
0xC00013F0	The Windows Process Activation Service (WAS) did not delete application pool %1. The data field contains the error number.	The Windows Process Activation Service (WAS) did not delete application pool %1. The data field contains the error number.
0xC00013F1	The Windows Process Activation Service failed to delete site '%1'. The data field contains the error number.	The Windows Process Activation Service failed to delete site '%1'. The data field contains the error number.
0xC00013F2	The Windows Process Activation Service failed to modify the application '%2' in site '%1'. The data field contains the error number.	The Windows Process Activation Service failed to modify the application '%2' in site '%1'. The data field contains the error number.
0xC00013F3	The Windows Process Activation Service (WAS) did not modify application pool %1. The data field contains the error number.	The Windows Process Activation Service (WAS) did not modify application pool %1. The data field contains the error number.
0xC00013F4	The Windows Process Activation Service failed to modify site '%1'. The data field contains the error number.	The Windows Process Activation Service failed to modify site '%1'. The data field contains the error number.
0xC00013FE	After recovering from an unexpected termination of the inetinfo process, Windows Process Activation Service (WAS) did not identify records that require deletion from the metadata cache. The data field contains the error number.	After recovering from an unexpected termination of the inetinfo process, Windows Process Activation Service (WAS) did not identify records that require deletion from the metadata cache. The data field contains the error number.
0xC0001410	Windows Process Activation Service (WAS) was unable to register protocol %1. The listener adapter for protocol %1 may not have received information about all application pools and applications for this protocol. To resolve this issue, restart the listener adapter. The data field contains the error number.	Windows Process Activation Service (WAS) was unable to register protocol %1. The listener adapter for protocol %1 may not have received information about all application pools and applications for this protocol. To resolve this issue, restart the listener adapter. The data field contains the error number.
0xC0001416	Windows Process Activation Service (WAS) encountered an error trying to determine the correct security identifier (SID) for the listener adapter identity for protocol %1. Because of this error, the service will not be able to allow the listener adapter to connect. To fix this, check and/or modify the identity value for this protocol in the configuration file. WAS was unable to determine the SID for the listener adapter identity for protocol %1. This error will prevent the listener adapter from connecting.	Windows Process Activation Service (WAS) encountered an error trying to determine the correct security identifier (SID) for the listener adapter identity for protocol %1. Because of this error, the service will not be able to allow the listener adapter to connect. To fix this, check and/or modify the identity value for this protocol in the configuration file. WAS was unable to determine the SID for the listener adapter identity for protocol %1. This error will prevent the listener adapter from connecting.
0xC0001417	Windows Process Activation Service (WAS) did not process changes that affect supported protocols for site %1. The site will be stopped because the system is unable to guarantee that all messages intended for the site will be processed. The data field contains the error number	Windows Process Activation Service (WAS) did not process changes that affect supported protocols for site %1. The site will be stopped because the system is unable to guarantee that all messages intended for the site will be processed. The data field contains the error number
0xC0001418	Application pool %1 has been disabled. Windows Process Activation Service (WAS) was unable to enable application pool %1, because the request that WAS sent to protocol %2 failed. The data field contains the error number.	Application pool %1 has been disabled. Windows Process Activation Service (WAS) was unable to enable application pool %1, because the request that WAS sent to protocol %2 failed. The data field contains the error number.
0xC0001419	Application pool %1 was not be disabled. The request from protocol %2 to disable the application pool failed. Restart the application pool so that Windows Process Activation Service (WAS) can determine the correct state of the protocol. The data field contains the error number.	Application pool %1 was not be disabled. The request from protocol %2 to disable the application pool failed. Restart the application pool so that Windows Process Activation Service (WAS) can determine the correct state of the protocol. The data field contains the error number.
0xC000141A	Application pool %1 has been disabled. The request from protocol %2 to create the application pool failed. Restart the application pool so that Windows Process Activation Service (WAS) can determine the correct state of the protocol. The data field contains the error number.	Application pool %1 has been disabled. The request from protocol %2 to create the application pool failed. Restart the application pool so that Windows Process Activation Service (WAS) can determine the correct state of the protocol. The data field contains the error number.
0xC000141B	Windows Process Activation Service (WAS) disabled protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle WAS.	Windows Process Activation Service (WAS) disabled protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle WAS.
0xC000141E	The request for protocol %1 to configure application %3 in virtual site %2 failed. The virtual site will be disabled because the protocol cannot configure the application. The data field contains the error number.	The request for protocol %1 to configure application %3 in virtual site %2 failed. The virtual site will be disabled because the protocol cannot configure the application. The data field contains the error number.
0xC000141F	Windows Process Activation Service (WAS) did not send a request to protocol %1 to remove configuration for application %3 in virtual site %2. WAS will assume that the protocol is disabled. To guarantee the state, start and stop the virtual site. The data field contains the error number.	Windows Process Activation Service (WAS) did not send a request to protocol %1 to remove configuration for application %3 in virtual site %2. WAS will assume that the protocol is disabled. To guarantee the state, start and stop the virtual site. The data field contains the error number.
0xC0001427	Windows Process Activation Service (WAS) did not register protocol %1, because WAS cannot register a protocol when there are listener channels from a previous listener adapter connection for the protocol. This may occur because you have worker processes running under debuggers and because orphaning may not be turned on. In this condition, WAS can detect the stop of a listener adapter, but it cannot kill the processes that contain listener channels. For this reason, WAS must wait for an admin to end these processes before a new listener adapter can connect. The data field contains the error number.	Windows Process Activation Service (WAS) did not register protocol %1, because WAS cannot register a protocol when there are listener channels from a previous listener adapter connection for the protocol. This may occur because you have worker processes running under debuggers and because orphaning may not be turned on. In this condition, WAS can detect the stop of a listener adapter, but it cannot kill the processes that contain listener channels. For this reason, WAS must wait for an admin to end these processes before a new listener adapter can connect. The data field contains the error number.
0xC0001428	Windows Process Activation Service failed to create the internal protocol app pool object for app pool '%1' and protocol '%2'. The virtual site of the application needing this app pool protocol combination will be disabled (see next message). The data field contains the error number.	Windows Process Activation Service failed to create the internal protocol app pool object for app pool '%1' and protocol '%2'. The virtual site of the application needing this app pool protocol combination will be disabled (see next message). The data field contains the error number.
0xC0001429	Site %1 has no root application defined, so the site will be ignored.	Site %1 has no root application defined, so the site will be ignored.
0xC000142B	Windows Process Activation Service (WAS) was unable to determine the security identifier (SID) for the worker process identity in application pool %1. WAS will be unable to provide the correct identity to listener adapters, which may prevent the worker process or processes in the application pool from processing requests for this protocol. To resolve this issue, change the worker process identity to a new identity and then change it back to the previous identity. The data field contains the error number.	Windows Process Activation Service (WAS) was unable to determine the security identifier (SID) for the worker process identity in application pool %1. WAS will be unable to provide the correct identity to listener adapters, which may prevent the worker process or processes in the application pool from processing requests for this protocol. To resolve this issue, change the worker process identity to a new identity and then change it back to the previous identity. The data field contains the error number.
0xC000142C	Windows Process Activation Service (WAS) was unable to notify protocol %2 about an identity change for application pool %1. This may prevent the worker process or processes in the application pool from processing requests for this protocol. To resolve this issue, change the worker process identity to a new identity and then change it back to the previous identity. The data field contains the error number.	Windows Process Activation Service (WAS) was unable to notify protocol %2 about an identity change for application pool %1. This may prevent the worker process or processes in the application pool from processing requests for this protocol. To resolve this issue, change the worker process identity to a new identity and then change it back to the previous identity. The data field contains the error number.
0xC000142D	Windows Process Activation Service (WAS) did not notify protocol %1 to enable request processing. Requests made to this protocol may be rejected. If this error occurred when WAS was starting, the service will not start. To resolve this issue, restart WAS. The data field contains the error number.	Windows Process Activation Service (WAS) did not notify protocol %1 to enable request processing. Requests made to this protocol may be rejected. If this error occurred when WAS was starting, the service will not start. To resolve this issue, restart WAS. The data field contains the error number.
0xC000142F	Windows Process Activation Service encountered an error trying to track worker process '%1' that belongs to app pool '%2'. This will result in this worker process not showing up in global queries enumerating all worker processes. It will also disable clients from being able to directly create a WORKER_PROCESS object to monitor this worker process. A client can see find this worker process by querying all worker processes in the app pool that this process belongs to. The data field contains the error number.	Windows Process Activation Service encountered an error trying to track worker process '%1' that belongs to app pool '%2'. This will result in this worker process not showing up in global queries enumerating all worker processes. It will also disable clients from being able to directly create a WORKER_PROCESS object to monitor this worker process. A client can see find this worker process by querying all worker processes in the app pool that this process belongs to. The data field contains the error number.
0xC0001431	The Windows Process Activation Service couldn't process configuration information for listener adapter '%1'. The data field contains the error number.	The Windows Process Activation Service couldn't process configuration information for listener adapter '%1'. The data field contains the error number.
0xC0001432	The Windows Process Activation Service failed to process configuration information to delete listener adapter '%1'. The data field contains the error number.	The Windows Process Activation Service failed to process configuration information to delete listener adapter '%1'. The data field contains the error number.
0xC0001433	The Windows Process Activation Service had an error setting the identity for listener adapter '%1'. The data field contains the error number.	The Windows Process Activation Service had an error setting the identity for listener adapter '%1'. The data field contains the error number.
0xC0001434	The Windows Process Activation Service encountered an error trying to read configuration data from file '%1', line number '%2'. The error message is: '%3'. The data field contains the error number.	The Windows Process Activation Service encountered an error trying to read configuration data from file '%1', line number '%2'. The error message is: '%3'. The data field contains the error number.
0xC0001435	The Windows Process Activation Service encountered an error trying to read configuration data for config section '%1' from file '%2', line number '%3'. The error message is: '%4'. The data field contains the error number.	The Windows Process Activation Service encountered an error trying to read configuration data for config section '%1' from file '%2', line number '%3'. The error message is: '%4'. The data field contains the error number.
0xC0001436	The '%1' '%2' has an invalid value for property '%3'. The configured value '%4' is invalid. The value will default to '%5'.	The '%1' '%2' has an invalid value for property '%3'. The configured value '%4' is invalid. The value will default to '%5'.
0xC0001437	The listener adapter serving the '%1' protocol disconnected unexpectedly.	The listener adapter serving the '%1' protocol disconnected unexpectedly.
0xC0001439	Windows Process Activation Service (WAS) did not create a relationship between protocol %1 and application %2, which belongs to site %3. The listener adapter for this protocol will not be notified about this application. To resolve this issue, restart WAS. The data field contains the error number.	Windows Process Activation Service (WAS) did not create a relationship between protocol %1 and application %2, which belongs to site %3. The listener adapter for this protocol will not be notified about this application. To resolve this issue, restart WAS. The data field contains the error number.
0xC000143A	An attempt was made to register protocol '%1', however protocol '%1' is all ready being handled by another listener adapter. Therefore the registration was rejected. The data field contains the error number.	An attempt was made to register protocol '%1', however protocol '%1' is all ready being handled by another listener adapter. Therefore the registration was rejected. The data field contains the error number.
0xC000143B	The config node '%1' has an invalid value for property '%2'. The configured value '%3' is invalid. The value will default to '%4'.	The config node '%1' has an invalid value for property '%2'. The configured value '%3' is invalid. The value will default to '%4'.
0xC000143C	The config node '%1' has an invalid value for property '%2'. The configured value '%3' is invalid. The value will default to '%4'. Valid values are: '%5'.	The config node '%1' has an invalid value for property '%2'. The configured value '%3' is invalid. The value will default to '%4'. Valid values are: '%5'.
0xC000143D	The protocol 'HTTPS' is not allowed in the property \"enabledProtocols\". If you wish to enable HTTPS, you must specify HTTP as the protocol. The data field contains the error number.	The protocol 'HTTPS' is not allowed in the property \"enabledProtocols\". If you wish to enable HTTPS, you must specify HTTP as the protocol. The data field contains the error number.
0xC000143E	No virtual sites have been configured for the hostable web core instance. The data field contains the error number.	No virtual sites have been configured for the hostable web core instance. The data field contains the error number.
0xC000143F	Only one application pool is allowed for the hostable web core instance. The data field contains the error number.	Only one application pool is allowed for the hostable web core instance. The data field contains the error number.
0xC0001443	Windows Process Activation Service was unable to create a listener adapter with a blank name '%1'. Please provide a name for your listener adapter protocol. The data field contains the error number.	Windows Process Activation Service was unable to create a listener adapter with a blank name '%1'. Please provide a name for your listener adapter protocol. The data field contains the error number.
0xC0001444	The directory specified for the temporary application pool config files is either missing or is not accessible by the Windows Process Activation Service. Please specify an existing directory and/or ensure that it has proper access flags. The data field contains the error number.	The directory specified for the temporary application pool config files is either missing or is not accessible by the Windows Process Activation Service. Please specify an existing directory and/or ensure that it has proper access flags. The data field contains the error number.
0xC0001445	The Windows Process Activation Service failed to generate an application pool config file for application pool '%1'. The error type is '%2'. To resolve this issue, please ensure that the applicationhost.config file is correct and recommit the last configuration changes made. The data field contains the error number.	The Windows Process Activation Service failed to generate an application pool config file for application pool '%1'. The error type is '%2'. To resolve this issue, please ensure that the applicationhost.config file is correct and recommit the last configuration changes made. The data field contains the error number.
0xC0001446	The Windows Process Activation Service has encountered an error during the SID mapping for the application pool '%1'. The application pool will be disabled. This typically happens if there are more than one application pool name that maps to the same SID. To resolve this issue, please change the name of the app pool and recommit the configuration changes. The data field contains the error number.	The Windows Process Activation Service has encountered an error during the SID mapping for the application pool '%1'. The application pool will be disabled. This typically happens if there are more than one application pool name that maps to the same SID. To resolve this issue, please change the name of the app pool and recommit the configuration changes. The data field contains the error number.
0xC0001447	The directory specified for the temporary application pool config files is a UNC path, which is not allowed. Please specify an existing local directory instead. The data field contains the error number.	The directory specified for the temporary application pool config files is a UNC path, which is not allowed. Please specify an existing local directory instead. The data field contains the error number.
0xC000144E	The application pool '%1' has enabled 32-bit worker processes, but no SysWOW64 support has been found. The Windows Process Activation Service (WAS) will disable the application pool. To resolve this issue, either disable running as 32-bit worker processes or install the SysWOW64 support. The data field contains the error number.	The application pool '%1' has enabled 32-bit worker processes, but no SysWOW64 support has been found. The Windows Process Activation Service (WAS) will disable the application pool. To resolve this issue, either disable running as 32-bit worker processes or install the SysWOW64 support. The data field contains the error number.
0xC000144F	Application pool '%1' has identity type which is not allowed by the administrator. Contact system administrator to allow application pool to run as current identity or change the identity of the application pool to something else.	Application pool '%1' has identity type which is not allowed by the administrator. Contact system administrator to allow application pool to run as current identity or change the identity of the application pool to something else.
0xC0001450	System doesn't allow application pools to run as LocalSystem. WAS tried to run orphan action '%1' for application pool '%2' as application pool identity and failed. Contact system administrator to allow application pool to run as LocalSystem or verify identity of this application pool has permissions to run orphan action.	System doesn't allow application pools to run as LocalSystem. WAS tried to run orphan action '%1' for application pool '%2' as application pool identity and failed. Contact system administrator to allow application pool to run as LocalSystem or verify identity of this application pool has permissions to run orphan action.
0xC0001452	The Windows Process Activation Service (WAS) was not able to add the mapping to the 'IIS APPPOOL' namespace and thus is unable to create or use application pool identities. The operation error code is '%1'. The data field contains the error number.	The Windows Process Activation Service (WAS) was not able to add the mapping to the 'IIS APPPOOL' namespace and thus is unable to create or use application pool identities. The operation error code is '%1'. The data field contains the error number.
0xC0001453	A process serving application pool '%1' reported a failure trying to read configuration during startup. The process id was '%2'. Please check the Application Event Log for further event messages logged by the worker process on the specific error. The data field contains the error number.	A process serving application pool '%1' reported a failure trying to read configuration during startup. The process id was '%2'. Please check the Application Event Log for further event messages logged by the worker process on the specific error. The data field contains the error number.
0xC000145E	The Windows Process Activation Service encountered an error trying to read configuration data with AppHostProvider. The error message is: %1. The data field contains the error number.	The Windows Process Activation Service encountered an error trying to read configuration data with AppHostProvider. The error message is: %1. The data field contains the error number.
0xC000145F	The Windows Process Activation Service (WAS) failed to execute initialization for offline setup. The data field contains the error number.	The Windows Process Activation Service (WAS) failed to execute initialization for offline setup. The data field contains the error number.
0xC0001771	W3C Logging Service failed to start.	W3C Logging Service failed to start.
0xC0001772	W3C Logging Service failed to create the log file directory '%2' for site id '%1'.	W3C Logging Service failed to create the log file directory '%2' for site id '%1'.
0xC0001773	W3C Logging Service failed to create log file '%2' for site id '%1'.	W3C Logging Service failed to create log file '%2' for site id '%1'.
0xC0001774	W3C Logging Service failed to write to the log file '%2' for site id '%1'.	W3C Logging Service failed to write to the log file '%2' for site id '%1'.
0xC0001775	W3C Logging Service failed to connect to the pipe server in the worker process with pipe name '%1'.	W3C Logging Service failed to connect to the pipe server in the worker process with pipe name '%1'.
0xC0001776	W3C Logging Service failed to write message to the pipe server in the worker process with id '%1'.	W3C Logging Service failed to write message to the pipe server in the worker process with id '%1'.
0xC0001777	W3C Logging Service failed to stop.	W3C Logging Service failed to stop.
0xC0001778	W3C Logging Service is stopping because it encountered an error. The data field contains the error number.	W3C Logging Service is stopping because it encountered an error. The data field contains the error number.
0xC0001779	Owner of log file or directory '%2' for site id '%1' is invalid.	Owner of log file or directory '%2' for site id '%1' is invalid.
0xC000177A	W3C Logging Service failed to read config for site id '%1'.	W3C Logging Service failed to read config for site id '%1'.
0xC000177B	'%1' ETW session events to W3C Logging Service were dropped. You will not find some entries in the log file.	'%1' ETW session events to W3C Logging Service were dropped. You will not find some entries in the log file.
0xC0001B5C	Listener Adapter protocol '%1' is unable to connect to Windows Process Activation Service because it has been disabled. Cause: Listener Adapter protocol '%1' has been marked as disabled by Windows Process Activation Service due catastrophic failure. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.	Listener Adapter protocol '%1' is unable to connect to Windows Process Activation Service because it has been disabled. Cause: Listener Adapter protocol '%1' has been marked as disabled by Windows Process Activation Service due catastrophic failure. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.
0xC0001B5D	Listener Adapter protocol '%1' attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state. Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.	Listener Adapter protocol '%1' attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state. Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.
0xC0001B5E	Listener Adapter protocol '%1' received bad data from Windows Process Activation Service and is shutting itself down. Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.	Listener Adapter protocol '%1' received bad data from Windows Process Activation Service and is shutting itself down. Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.
0xC0002328	The Application Host Helper Service encountered an error while reading the data for SID mapping. Please ensure that the application pool name data is correct in the configuration file. To resolve this issue, please recommit the changes or restart this service. The data field contains the error number.	The Application Host Helper Service encountered an error while reading the data for SID mapping. Please ensure that the application pool name data is correct in the configuration file. To resolve this issue, please recommit the changes or restart this service. The data field contains the error number.
0xC0002329	The Application Host Helper Service encountered an error while adding the mapping for the application pool name '%1' to its SID. That particular SID is already mapped to another application pool name, causing a conflict. To resolve this issue, please change the name of this application pool. The data field contains the error number.	The Application Host Helper Service encountered an error while adding the mapping for the application pool name '%1' to its SID. That particular SID is already mapped to another application pool name, causing a conflict. To resolve this issue, please change the name of this application pool. The data field contains the error number.
0xC000232A	The Application Host Helper Service encountered an error while mapping the application pool names to their respective SIDs. Some app pool SIDs will not be resolved properly under the 'IIS APPPOOL' namespace. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.	The Application Host Helper Service encountered an error while mapping the application pool names to their respective SIDs. Some app pool SIDs will not be resolved properly under the 'IIS APPPOOL' namespace. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.
0xC000232B	The Application Host Helper Service encountered an error while removing the mapping for the application pool name '%1' to its SID. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.	The Application Host Helper Service encountered an error while removing the mapping for the application pool name '%1' to its SID. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.
0xC000232C	The Application Host Helper Service encountered an error while adding multiple mappings for application pool names to their SIDs. To resolve this issue, please recommit the changes and restart the service. The data field contains the error number.	The Application Host Helper Service encountered an error while adding multiple mappings for application pool names to their SIDs. To resolve this issue, please recommit the changes and restart the service. The data field contains the error number.
0xC000232D	The Application Host Helper Service encountered an error while adding the mapping for the application pool name '%1' to its SID. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.	The Application Host Helper Service encountered an error while adding the mapping for the application pool name '%1' to its SID. To resolve this issue, please recommit the changes or restart the service. The data field contains the error number.
0xC000232E	The Application Host Helper Service encountered an error trying to process the configuration data for config history. The feature will be disabled. To resolve this issue, please confirm that the configuration file is correct, has correct attribute values for config history and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.	The Application Host Helper Service encountered an error trying to process the configuration data for config history. The feature will be disabled. To resolve this issue, please confirm that the configuration file is correct, has correct attribute values for config history and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.
0xC000232F	The Application Host Helper Service encountered an error trying to read configuration data from file '%1', line number '%2'. The error message is: '%3'. The feature will be disabled. To resolve this issue, please fix the configuration file and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.	The Application Host Helper Service encountered an error trying to read configuration data from file '%1', line number '%2'. The error message is: '%3'. The feature will be disabled. To resolve this issue, please fix the configuration file and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.
0xC0002330	The Application Host Helper Service encountered an error trying to read the property '%1' from configuration data from file '%2', line number '%3'. The feature will be disabled. To resolve this issue, please fix the property in the file and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.	The Application Host Helper Service encountered an error trying to read the property '%1' from configuration data from file '%2', line number '%3'. The feature will be disabled. To resolve this issue, please fix the property in the file and recommit the changes. The feature will be enabled again if the configuration is correct. The data field contains the error number.
0xC0002332	The Application Host Helper Service encountered an error trying to access the root history directory '%1'. The directory either doesn't exist or the permissions on it don't allow the history service to access it. The config history feature is disabled for now and will be re-enabled after the issue is resolved. To resolve this issue, please ensure that the directory exists and that the Administrators group have read and write access to it. The data field contains the error number.	The Application Host Helper Service encountered an error trying to access the root history directory '%1'. The directory either doesn't exist or the permissions on it don't allow the history service to access it. The config history feature is disabled for now and will be re-enabled after the issue is resolved. To resolve this issue, please ensure that the directory exists and that the Administrators group have read and write access to it. The data field contains the error number.
0xC0002333	The directory specified for the root history directory is a UNC path, which is not allowed. The feature will be disabled. To resolve this issue, please set it to a local directory. The feature will be enabled again if the configuration is correct. The data field contains the error number.	The directory specified for the root history directory is a UNC path, which is not allowed. The feature will be disabled. To resolve this issue, please set it to a local directory. The feature will be enabled again if the configuration is correct. The data field contains the error number.
0xC0002334	The Application Host Helper Service has detected that %1 file doesn't contain valid configuration. Config history backup feature has been disabled. It will be re-enabled automatically once the configuration file is fixed.	The Application Host Helper Service has detected that %1 file doesn't contain valid configuration. Config history backup feature has been disabled. It will be re-enabled automatically once the configuration file is fixed.
0xC0040001	FTP Server could not initialize its security. The data is the error.	FTP Server could not initialize its security. The data is the error.
0xC0040003	FTP Server could not initialize the socket library. The data is the error.	FTP Server could not initialize the socket library. The data is the error.
0xC0040004	FTP Server was unable to initialize because of a shortage of available memory. The data is the error.	FTP Server was unable to initialize because of a shortage of available memory. The data is the error.
0xC0040005	FTP Server could not locate the FTP/TCP service. The data is the error.	FTP Server could not locate the FTP/TCP service. The data is the error.
0xC0040006	FTP Server could not create the main connection socket. The data is the error.	FTP Server could not create the main connection socket. The data is the error.
0xC0040007	FTP Server could not create the main connection thread. The data is the error.	FTP Server could not create the main connection thread. The data is the error.
0xC0040008	FTP Server could not create a client worker thread for user at host %1. The connection to this user is terminated. The data is the error.	FTP Server could not create a client worker thread for user at host %1. The connection to this user is terminated. The data is the error.
0xC0040009	A call to a system service failed unexpectedly. The data is the error.	A call to a system service failed unexpectedly. The data is the error.
0xC004000F	Failed to read metabase property PassivePortRange under the FTP Service node %1.	Failed to read metabase property PassivePortRange under the FTP Service node %1.
0xC0040010	The FTP Service configuration property PassivePortRange has invalid value: %1.	The FTP Service configuration property PassivePortRange has invalid value: %1.
0xD0000001	Standard	Standard
0xD0000002	Application Isolation	Application Isolation
0xD0000003	AppHostChangeHandler	AppHostChangeHandler
0xD0000004	Add	Add
0xD0000005	Delete	Delete
0xD0000006	Modify	Modify
0xD0000007	ConfigurationReadFailure	ConfigurationReadFailure
0xD0000008	UuencodeApiFailure	UuencodeApiFailure
0xD0000009	UudecodeApiFailure	UudecodeApiFailure
0xD000000A	CryptAcquireContextApiFailure	CryptAcquireContextApiFailure
0xD000000B	CryptGetUserKeyApiFailure	CryptGetUserKeyApiFailure
0xD000000C	CryptExportKeyApiFailure	CryptExportKeyApiFailure
0xD000000D	CryptImportKeyApiFailure	CryptImportKeyApiFailure
0xD000000E	CryptGetKeyParamApiFailure	CryptGetKeyParamApiFailure
0xD000000F	ThreadImpersonationFailure	ThreadImpersonationFailure
0xD0000010	InvalidKeyAlgorithmForAesProviderr	InvalidKeyAlgorithmForAesProviderr
0xD0000011	CryptProtectDataApiFailure	CryptProtectDataApiFailure
0xD0000012	CryptUnprotectDataApiFailure	CryptUnprotectDataApiFailure
0xD0000013	CryptEncryptApiFailure	CryptEncryptApiFailure
0xD0000014	CryptDecryptApiFailure	CryptDecryptApiFailure
0xD0000015	CryptGenKeyApiFailure	CryptGenKeyApiFailure
0xD0000016	CryptGenRandomApiFailure	CryptGenRandomApiFailure
0xD0000018	Xml	Xml
0xD0000019	Config	Config
0xD000001A	Other	Other

File Name:	iisres.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-i..libraries.resources_31bf3856ad364e35_10.0.15063.0_en-us_614e0d75f40af5d9\
File Size:	491 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	502272
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	IIS Resource DLL
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	iisres.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	iisres.dll.mui
Product Name:	Internet Information Services
Product Version:	10.0.15063.0
Directory:	%WINDIR%\WinSxS\wow64_microsoft-windows-i..libraries.resources_31bf3856ad364e35_10.0.15063.0_en-us_6ba2b7c8286bb7d4\

iisres.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file iisres.dll (IIS Resource DLL).

File Description:	IIS Resource DLL
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	iisres.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	iisres.dll.mui
Product Name:	Internet Information Services
Product Version:	10.0.15063.0
Translation:	0x409, 1200