????

Your IP : 18.188.100.179

Current Path : C:/Windows/System32/inetsrv/en-US/
Upload File :
Current File : C:/Windows/System32/inetsrv/en-US/iisres.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!�

��g@ 8�8.rdata�@@.rsrc� �@@
�9
T88
�9$��8.rdata8x.rdata$zzzdbg P.rsrc$01P9pC	.rsrc$02 �8[��I�h���7��p,7�!}Kl�A�

�90�0�H������q(�@�
X�p����� ��&��?��@�~�0��H��`��x�������9��x��~���� ��8��P��h�������������������3��(��@��X��p���������������������0�H�`�x�����������	�	 	�
8	�P	�h	�
�	��	��	��	��	��	�
�(
�@
�X
�p
��
��
��
��
� �
�!�#�$0�'H�(`�)x�*��+��,��-��.����� �8�P�Th�k���	���	���	��6��7��8
�U(
�V@
�WX
�Xp
�Y�
�Z�
�[�
�\�
�]�
�^�_�`0�aH�t`�ux�v��w������	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 86���6h�`=���E���H��LI���Jx�HM���M\�XN��P���V�
�|dd��rl�L�X������|�p����x��	� ������ȟ��P��	������
��z�h�l�Խ��h��������&�������P����������6��,�H�>����� .�P�,�89H��Jx&��p������\�l�Ȱ���#���,����)8��5��C���Wt�j���������z���,�2	�`�F��������$	��N�H'J��C��|R��l��<u���}�
�|�"���P�����������������!�|���0������t
��T�!�8;�TM��O�P���^,��`��dm ��mV��q��v:�0{<�lL���6����p�d�Ԋ��|���t������P�8�����p������Ԫ����x�4�*�`���@�����������������x�MUI���!�=��W��]���u%Z��6��q�aZ]�?����MUIen-US>007~ASP 0100~Out of memory~Unable to allocate required memory.6007~ASP 0101~Unexpected error~The function returned |.K007~ASP 0102~Expecting string input~The function expects a string as input.L007~ASP 0103~Expecting numeric input~The function expects a number as input.#007~ASP 0104~Operation not Allowed~?007~ASP 0105~Index out of range~An array index is out of range.B007~ASP 0106~Type Mismatch~An unhandled data type was encountered.b007~ASP 0107~Data size too large~Size of data being sent in the request is over the allowed limit.�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.TrueFalsee006~ASP 0211~Object out of scope~A built-in ASP object has been referenced, which is no longer valid.a006~ASP 0226~Cannot modify StaticObjects~StaticObjects collection cannot be modified at run time.|No further information is available. (Error description is too long; please check for missing end delimiters, such as '%>'.)�The Template Persistent Cache initialization failed for Application Pool '%s' because of the following error: %s. The data may have additional error codes.jASP unhealthy because %d%% of executing requests are not responding and %d%% of the request queue is full.ZASP will not serve requests because it could not perform the first request initialization.0ASP unhealthy due to an out of memory condition.�006~ASP 0251~Response Buffer Limit Exceeded~Execution of the ASP page caused the Response Buffer to exceed its configured limit.)The Disk Cache Directory Name is too longDCould not create a Disk Cache Sub-directory for the Application PoolVThe Disk Cache Sub-directory for the Application Pool is missing or cannot be accessed?The generated name for the Disk Cache Cleanup Event is too longCThe Event for the Disk Cache Directory Cleanup could not be createdPAError: Access is Denied.bAn error occurred on the server when processing the URL.  Please contact the system administrator.7The server is under heavy load, please try again later.VBScriptaInternet Information Services is not installed, Active Server Pages requires IIS installed first.1%SystemDrive%\inetpub\temp\ASP Compiled TemplatesPA <font face="Arial" size=2>
<p></font> !<font face="Arial" size=2>error ''</font>
<p>
<font face="Arial" size=2></font>
<p>
<font face="Arial" size=2></font>!<font face="Arial" size=2>, line </font>

<pre></pre>
<p>
<font face="Arial" size=2>
</font> PAMicrosoft Active Server PagesIIS log failed to write entry, Active Server Pages CompilerActive Server PagesFile Line 6Metabase key %d is out of range.  Using %d as default.|ASPAError while reading default settings. please do regsvr32 asp.dll.ASP Script Errorerror ''$ - Application Debugging is Disabled204 No Content
403 Forbidden
404 Not Found500 Server Error401 Access DeniedPA *** Encrypted ASP File *** 

O006~ASP 0108~Create object failed~An error occurred while creating object '%s'.006~ASP 0109~Member not found~006~ASP 0110~Unknown name~006~ASP 0111~Unknown interface~006~ASP 0112~Missing parameter~PA�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 0114~Object not free threaded~The application object accepts only free threaded objects; object '%s' is not free threaded.x007~ASP 0115~Unexpected error~A trappable error (%X) occurred in an external object. The script cannot continue running.DAn external object raised an error.  No Error Description Available.[007~ASP 0240~Script Engine Exception~A ScriptEngine threw exception '%X' in '%s' from '%s'.Q007~ASP 0241~CreateObject Exception~The CreateObject of '%s' caused exception %X.007~ASP 0242~Query OnStartPage Interface Exception~Querying Object '%s''s OnStartPage or OnEndPage methods caused exception %X.PAASP Preprocessor Error$Error in script file '|' on line |: c006~ASP 0116~Missing close of script delimiter~The Script block lacks the close of script tag (%>).006~ASP 0117~Missing close of script tag~The Script block lacks the close of script tag (</SCRIPT>) or close of tag symbol (>).006~ASP 0118~Missing close of object tag~The Object block lacks the close of object tag (</OBJECT>) or close of tag symbol (>).~006~ASP 0119~Missing Classid or Progid attribute~The object instance '|' requires a valid Classid or Progid in the object tag.z006~ASP 0120~Invalid Runat attribute~The Runat attribute of the Script tag or Object tag can only have the value 'Server'.�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 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.Y006~ASP 0123~Missing Id attribute~The required Id attribute of the Object tag is missing.e006~ASP 0124~Missing Language attribute~The required Language attribute of the Script tag is missing.`006~ASP 0125~Missing close of attribute~The value of the '|' attribute has no closing delimiter.G006~ASP 0126~Include file not found~The include file '|' was not found.m006~ASP 0127~Missing close of HTML comment~The HTML comment or server-side include lacks the close tag (-->).�006~ASP 0128~Missing File or Virtual attribute~The Include file name must be specified using either the File or Virtual attribute.^006~ASP 0129~Unknown scripting language~The scripting language '|' is not found on the server.PAe006~ASP 0130~Invalid File attribute~File attribute '|' cannot start with forward slash or back slash.n006~ASP 0131~Disallowed Parent Path~The Include file '|' cannot contain '..' to indicate the parent directory.Q006~ASP 0132~Compilation Error~The Active Server Page '|' could not be processed.T006~ASP 0133~Invalid ClassID attribute~The object tag has an invalid ClassID of '|'.N006~ASP 0134~Invalid ProgID attribute~The object has an invalid ProgID of '|'.�006~ASP 0135~Cyclic Include~The file '|' is included by itself (perhaps indirectly). Please check include files for other Include statements.�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 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 0138~Nested Script Block~A script block cannot be placed inside another script block.T006~ASP 0139~Nested Object~An object tag cannot be placed inside another object tag.m006~ASP 0140~Page Command Out Of Order~The @ command must be the first command within the Active Server Page.e006~ASP 0141~Page Command Repeated~The @ command can only be used once within the Active Server Page.s006~ASP 0201~Invalid Default Script Language~The default script language specified for this application is invalid.B006~ASP 0202~Missing Code Page~The code page attribute is missing.L006~ASP 0203~Invalid Code Page~The specified code page attribute is invalid.�006~ASP 0209~Illegal value for TRANSACTION property~The TRANSACTION property can only be REQUIRED, REQUIRES_NEW, SUPPORTED or NOT_SUPPORTED.u006~ASP 0215~Illegal value for ENABLESESSIONSTATE property~The ENABLESESSIONSTATE property can only be TRUE or FALSE.[006~ASP 0217~Invalid Scope in object tag~Object scope must be Page, Session or Application.8006~ASP 0218~Missing LCID~The LCID attribute is missing.>006~ASP 0219~Invalid LCID~The specified LCID is not available.X006~ASP 0221~Invalid @ Command directive~The specified '|' option is unknown or invalid.g006~ASP 0222~Invalid TypeLib Specification~METADATA tag contains an invalid Type Library specification.y006~ASP 0223~TypeLib Not Found~METADATA tag contains a Type Library specification that does not match any Registry entry.X006~ASP 0224~Cannot load TypeLib~Cannot load Type Library specified in the METADATA tag.�006~ASP 0225~Cannot wrap TypeLibs~Cannot create a Type Library Wrapper object from the Type Libraries specified in METADATA tags.`006~ASP 0232~Invalid Cookie Specification~METADATA tag contains an invalid cookie specification.r006~ASP 0233~Cannot load cookie script source~Cannot load cookie script source file specified in the METADATA 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 <SCRIPT> tag.d006~ASP 0236~Invalid Cookie Specification~METADATA tag contains an invalid or missing SRC parameter.e006~ASP 0237~Invalid Cookie Specification~METADATA tag contains an invalid or missing NAME parameter.R006~ASP 0238~Missing attribute value~No value was specified for the '|' attribute.E006~ASP 0239~Cannot process file~UNICODE ASP files are not supported.g006~ASP 0243~Invalid METADATA tag in Global.asa~Only METADATA TYPE="TypeLib" may be used in Global.asa.v006~ASP 0244~Cannot Enable Session State~Session state cannot be enabled when it has been disabled in the application.�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.518~0~204 No Content~518~0~404 Not Found~q006~ASP 0216~MSDTC Service not running~Transactional web pages cannot be run if the MSDTC service is not running.#518~0~401 Error: Access is Denied.~PAObject Not Found4Error, Script file '%s' was not found on the server.!Error, Script file '%s' is empty.>006~ASP 0142~Thread token error~A thread token failed to open.M006~ASP 0143~Invalid Application Name~A valid application name was not found.[006~ASP 0144~Initialization Error~The page level objects list failed during initialization.K006~ASP 0145~New Application Failed~The new Application could not be added.B006~ASP 0146~New Session Failed~The new Session could not be addedW006~ASP 0150~Application Directory Error~The Application directory could not be opened.Z006~ASP 0151~Change Notification Error~The change notification event could not be created.]006~ASP 0152~Security Error~An error occurred while processing a user's security credentials.006~ASP 0147~500 Server Error~006~ASP 0148~Server Too Busy~8006~ASP 0198~Server shutting down~Cannot process requestm006~ASP 0149~Application Restarting~The request cannot be processed while the application is being restarted.n006~ASP 0220~Requests for GLOBAL.ASA Not Allowed~Requests with the URL pointing to GLOBAL.ASA are not allowed.A006~ASP 0246~Too many concurrent users.  Please try again later.~g006~ASP 0250~Invalid Default Code Page~The default code page specified for this application is invalid.6006~ASP 0153~Thread Error~A new thread request failed.Response objecta006~ASP 0154~Write HTTP Header Error~The HTTP headers could not be written to the client browser.b006~ASP 0155~Write Page Content Error~The page content could not be written to the client browser.�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.V006~ASP 0157~Buffering On~Buffering cannot be turned off once it is already turned on.+006~ASP 0158~Missing URL~A URL is required.0006~ASP 0159~Buffering Off~Buffering must be on.;006~ASP 0160~Logging Failure~Failure to write entry to log.f<head><title>Object moved</title></head>
<body><h1>Object Moved</h1>This object may be found <a HREF="">here</a>.</body>
U006~ASP 0161~Data Type Error~The conversion of a Variant to a String variable failed.m006~ASP 0162~Cannot Modify Cookie~The cookie 'ASPSessionID' cannot be modified. It is a reserved cookie name.i006~ASP 0163~Invalid Comma Use~Commas cannot be used within a log entry. Please select another delimiter.x006~ASP 0212~Cannot Clear Buffer~Response.Clear is not allowed after a Response.Flush while Client Debugging is Enabled.M006~ASP 0210~Method not implemented~This method has not yet been implemented.Session object	SessionIDJ006~ASP 0164~Invalid TimeOut Value~An invalid TimeOut value was specified.B006~ASP 0165~SessionID Error~A SessionID string cannot be created.X006~ASP 0166~Uninitialized Object~An attempt was made to access an uninitialized object.b006~ASP 0167~Session Initialization Error~An error occurred while initializing the Session object.b006~ASP 0168~Disallowed object use~An intrinsic object cannot be stored within the Session object.�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.F006~ASP 0170~Delete Session Error~The Session did not delete properly.i006~ASP 0188~Disallowed object use~Cannot add objects created using object tags to the session intrinsic.M006~ASP 0199~Disallowed object use~Cannot add JScript objects to the session.L006~ASP 0204~Invalid CodePage Value~An invalid CodePage value was specified.
Server objectServer.MapPath()V006~ASP 0171~Missing Path~The Path parameter must be specified for the MapPath method.u006~ASP 0172~Invalid Path~The Path parameter for the MapPath method must be a virtual path. A physical path was used.t006~ASP 0173~Invalid Path Character~An invalid character was specified in the Path parameter for the MapPath method.u006~ASP 0174~Invalid Path Character(s)~An invalid '/' or '\' was found in the Path parameter for the MapPath method. z006~ASP 0175~Disallowed Path Characters~The '..' characters are not allowed in the Path parameter for the MapPath method. i006~ASP 0176~Path Not Found~The Path parameter for the MapPath method did not correspond to a known path.�006~ASP 0195~Invalid Server Method Call~This method of the Server object cannot be called during Session_OnEnd and Application_OnEnd.*006~ASP 0177~Server.CreateObject Failed~%s�006~ASP 0178~Server.CreateObject Access Error~The call to Server.CreateObject failed while checking permissions. Access is denied to this object.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.Z006~ASP 0214~Invalid Path parameter~The Path parameter excedes the maximum length allowed.D006~ASP 0227~Server.Execute Failed~The call to Server.Execute failed[006~ASP 0228~Server.Execute Error~The call to Server.Execute failed while loading the page.o006~ASP 0231~Server.Execute Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.F006~ASP 0229~Server.Transfer Failed~The call to Server.Transfer failed]006~ASP 0230~Server.Transfer Error~The call to Server.Transfer failed while loading the page.p006~ASP 0235~Server.Transfer Error~Invalid URL form or fully-qualified absolute URL was used. Use relative URLs.PAApplication objectj006~ASP 0179~Application Initialization Error~An error occurred while initializing the Application object.f006~ASP 0180~Disallowed object use~An intrinsic object 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.�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.m006~ASP 0189~Disallowed object use~Cannot add objects created using object tags to the application intrinsic.�006~ASP 0187~Object addition conflict~Could not add object to application. Application was locked down by another request for adding an object.w006~ASP 0197~Disallowed object use~Cannot add object with apartment model behavior to the application intrinsic object.P006~ASP 0205~Change Notification~Failed to create event for change notification.PACookies objectJ006~ASP 0183~Empty Cookie Key~A cookie with an empty key cannot be stored.G006~ASP 0184~Missing Cookie Name~A name must be specified for a cookie.�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.PARequest object_006~ASP 0206~Cannot call BinaryRead~Cannot call BinaryRead after using Request.Form collection.a006~ASP 0207~Cannot use Request.Form~Cannot use Request.Form collection after calling BinaryRead.v006~ASP 0208~Cannot use generic Request collection~Cannot use the generic Request collection after calling BinaryRead.�006~ASP 0249~Cannot use IStream on Request~Cannot use IStream on Request object after using Request.Form collection or Request.BinaryRead.X006~ASP 0247~Bad Argument to BinaryRead~The argument to BinaryRead must be non-negative.
Server object\007~ASP 0190~Unexpected error~A trappable error occurred while releasing an external object.i007~ASP 0191~Unexpected error~A trappable error occurred in the OnStartPage method of an external object.g007~ASP 0192~Unexpected error~A trappable error occurred in the OnEndPage method of an external object.PAb007~ASP 0193~OnStartPage Failed~An error occurred in the OnStartPage method of an external object.^007~ASP 0194~OnEndPage Failed~An error occurred in the OnEndPage method of an external object.Certificate object&006~ASP 0186~Error parsing certificateObjectContext objecto006~ASP 0248~Script isn't transacted~This ASP file must be transacted in order to use the ObjectContext object.PAV006~ASP 0185~Missing Default Property~A default property was not found for the object.[To Parent Directory]dir}<head><title>Document Moved</title></head>
<body><h1>Object Moved</h1>This document may be found <a HREF="%s">here</a></body>�<head><title>Site Access Denied</title></head>
<body><h1>Access Denied</h1>Your site has been denied access to this server.</body>PAOToo Many Users</h1>There are too many connected users.  Please try again later.�All of the available licenses are in use.  Talk to the system administrator to increase the number of available licenses on this server.9This Virtual Directory does not allow objects to be read.=This Virtual Directory does not allow objects to be executed.ZThis Virtual Directory requires a browser that supports the configured encryption options.<This Virtual Directory does not allow objects to be written.PAZThis Virtual Directory requires a browser that supports the configured encryption options.3Access to this server is forbidden from your clientZThis Virtual Directory requires a browser that supports the configured encryption options.#The server configuration is invalid+Access denied using this Client Certificate$Error: Unable to read footer file.

�<head><title>Unsupported Content-Type</title></head>
<body><h1>The Content-Type of the request is not supported by this server.</h1></body>,No license available to access this computer%The specified method is not supported'The client certificate has been revoked/The client certificate is untrusted or corrupt.PA7The client certificate has expired or is not yet valid.<This Virtual Directory does not allow contents to be listed.<head><title>Server Application Error</title></head>
<body><h1>Server Application Error</h1>The server has reached the maximum recovery limit for the application during the processing of your request. Please contact the server administrator for assistance.</body>?<head><title>Server Application Error</title></head>
<body><h1>Server Application Error</h1>The 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.</body>FThe specified request cannot be executed from current Application Pool`The configured user for the current Application Pool does not have enough privileges to run CGIsGAuthentication credentials received by the server are bad or incompleteIThis Virtual Directory does not allow the specified authentication method@The ACL on this resource denied access to the authenticated user.An ISAPI filter serving this request denied it.The application serving this request denied itCThe ISAPI/CGI configured for this request is not allowed to executeNThe file-extension for this static request is not present in the mime-map list*No handler could be found for this request$The specified URL sequence is deniedThe specified verb is denied&The specified file extension is denied5The namespace for this URL is hidden by configurationDThis file has a hidden attribute which prevents it from being served<One of the request header is longer than the specified limitGThis URL is denied because it is susceptible to double-escaping attacks5This URL is denied because it has high-bit characters:The Content-Length is longer than allowed by configuration/The URL is longer than allowed by configuration7The QueryString is longer than allowed by configuration�<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
<html xmlns="http://www.w3.org/1999/xhtml"> 
<head> 
<title>IIS 10.0 Detailed Error - %u.%u - %S</title> 
%s 
</head> 
<body> 
<div id="content"> 
<div class="content-container"> 
  <h3>HTTP Error %u.%u - %S</h3> 
  <h4>%s</h4> 
</div> 
%s 
<div class="content-container"> 
 <fieldset><h4>Detailed Error Information:</h4> 
  <div id="details-left"> 
   <table border="0" cellpadding="0" cellspacing="0"> 
    <tr class="alt"><th>Module</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr><th>Notification</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr class="alt"><th>Handler</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr><th>Error Code</th><td>&nbsp;&nbsp;&nbsp;0x%08x</td></tr> 
    %s 
   </table> 
  </div> 
  <div id="details-right"> 
   <table border="0" cellpadding="0" cellspacing="0"> 
    <tr class="alt"><th>Requested URL</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr><th>Physical Path</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr class="alt"><th>Logon Method</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    <tr><th>Logon User</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
    %s 
   </table> 
   <div class="clear"></div> 
  </div> 
 </fieldset> 
</div> 
%s 
<div class="content-container"> 
 <fieldset><h4>More Information:</h4> 
  %s 
  <p><a href="%s&amp;IIS70Error=%u,%u,0x%08x,%d">View more information &raquo;</a></p> 
  %s 
 </fieldset> 
</div> 
</div> 
</body> 
</html> 
�<tr class="alt"><th>Config Error</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr> 
<tr><th>Config File</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr>&<span class="highlight-code">%s</span>	AnonymousNot yet determined0<p>Microsoft Knowledge Base Articles:</p> 
 %s 
�<div class="content-container"> 
 <fieldset><h4>Most likely causes:</h4> 
  %s 
 </fieldset> 
</div> 
<div class="content-container"> 
 <fieldset><h4>Things you can try:</h4> 
  %s 
 </fieldset> 
</div> 
PAT<tr class="alt"><th>Request Tracing Directory</th><td>&nbsp;&nbsp;&nbsp;%s</td></tr>Server Error Server Error in Application "%s"Unknown�<style type="text/css"> 
<!-- 
body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} 
code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} 
.config_source code{font-size:.8em;color:#000000;} 
pre{margin:0;font-size:1.4em;word-wrap:break-word;} 
ul,ol{margin:10px 0 10px 5px;} 
ul.first,ol.first{margin-top:5px;} 
fieldset{padding:0 15px 10px 15px;word-break:break-all;} 
.summary-container fieldset{padding-bottom:5px;margin-top:4px;} 
legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} 
legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; 
font-weight:bold;font-size:1em;} 
a:link,a:visited{color:#007EFF;font-weight:bold;} 
a:hover{text-decoration:none;} 
h1{font-size:2.4em;margin:0;color:#FFF;} 
h2{font-size:1.7em;margin:0;color:#CC0000;} 
h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;} 
h4{font-size:1.2em;margin:10px 0 5px 0; 
}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif; 
 color:#FFF;background-color:#5C87B2; 
}#content{margin:0 0 0 2%;position:relative;} 
.summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} 
.content-container p{margin:0 0 10px 0; 
}#details-left{width:35%;float:left;margin-right:2%; 
}#details-right{width:63%;float:left;overflow:hidden; 
}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF; 
 background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal; 
 font-size:1em;color:#FFF;text-align:right; 
}#server_version p{margin:5px 0;} 
table{margin:4px 0 4px 0;width:100%;border:none;} 
td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;} 
th{width:30%;text-align:right;padding-right:2%;font-weight:bold;} 
thead th{background-color:#ebebeb;width:25%; 
}#details-right th{width:20%;} 
table tr.alt td,table tr.alt th{} 
.highlight-code{color:#CC0000;font-weight:bold;font-style:italic;} 
.clear{clear:both;} 
.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;} 
--> 
</style> 
�  <div class="config_source content-container"> 
    <fieldset> 
    <h4>Config Source:</h4> 
    <pre><code>%s</code></pre> 
    </fieldset> 
  </div> 
Unavailable (Config Isolation)Request started: "%s" %s
)Response sent: %s with HTTP status %d.%d
Child request started: "%s"8Child request ended: "%s" for site "%s" application "%s"?Successfully registered URL "%s" for site "%s" application "%s")Failed to register URL "%s" for site "%s"PA6The custom error module does not recognize this error.C<ul> 	<li>A module set an infrequently used status code.</li> </ul>8<li>Investigate why the module set the status code.</li>�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. :You do not have permission to view this directory or page.m<ul> 	<li>The authenticated user does not have access to a resource needed to process the request.</li> </ul>�<ul> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>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.<ul><li>907273</li></ul>PAbYou do not have permission to view this directory or page using the credentials that you supplied.-<ul> 	<li>The username supplied to IIS is invalid.</li> 	<li>The password supplied to IIS was not typed correctly. </li> 	<li>Incorrect credentials were cached by the browser.</li> 	<li>IIS could not verify the identity of the username and password provided.</li> 	<li>The resource is configured for Anonymous authentication, but the configured anonymous account either has an invalid password or was disabled.</li> 	<li>The server is configured to deny login privileges to the authenticating user or the group in which the user is a member.</li> 	<li>Invalid Kerberos configuration may be the cause if all of the following are true:</li> 	<ul> 		<li>Integrated authentication was used.</li> 		<li>the application pool identity is a custom account.</li> 		<li>the server is a member of a domain.</li> 	</ul> </ul>�<ul> 	<li>Verify that the username and password are correct, and are not cached by the browser.</li> 	<li>Use a different username and password.</li> 	<li>If you are using a custom anonymous account, verify that the password has not expired.</li> 	<li>Verify that the authenticating user or the user's group, has not been denied login access to the server.</li> 	<li>Verify that the account was not locked out due to numerous failed login attempts.</li> 	<li>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.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.6<ul><li>907273</li><li>871179</li><li>896861</li></ul>OYou are not authorized to view this page due to invalid authentication headers.s<ul> 	<li>No authentication protocol (including anonymous) is selected in IIS.</li> 	<li>Only integrated authentication is enabled, and a client browser was used that does not support integrated authentication.</li> 	<li>Integrated authentication is enabled and the request was sent through a proxy that changed the authentication headers before they reach the Web server.</li> 	<li>The Web server is not configured for anonymous access and a required authorization header was not received.</li> 	<li>The "configuration/system.webServer/authorization" configuration section may be explicitly denying the user access.</li> </ul>�<ul> 	<li>Verify the authentication setting for the resource and then try requesting the resource using that authentication method.</li> 	<li>Verify that the client browser supports Integrated authentication.</li> 	<li>Verify that the request is not going through a proxy when Integrated authentication is used.</li> 	<li>Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.'<ul><li>907273</li><li>253667</li></ul>�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.�<ul> 	<li>The user authenticated by the Web server does not have permission to open the file on the file system.</li> 	<li>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.</li> 	<li>The file is encrypted.</li> </ul>
<ul> 	<li>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.</li> 	<li>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.</li> 	<li>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.)</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.PA'<ul><li>907273</li><li>332142</li></ul>�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.{<ul> 	<li>An ISAPI filter running on the Web server has failed the authentication process or denied the request.</li> </ul>�<ul> 	<li>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.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li>907273</li></ul>�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.�<ul> 	<li>A custom ISAPI extension, CGI application, ASP page, or handler failed the request with an Access Denied error.</li> </ul>f<ul> 	<li>Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li>907273</li></ul>:You do not have permission to view this directory or page.u<ul> 	<li>This is a generic 403 error and means the authenticated user is not authorized to view the page.</li> </ul>�<ul> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>/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. |You have attempted to run a CGI, ISAPI, or other executable program from a directory that does not allow executables to run.<ul> 	<li>The "Scripts" or "Scripts and Executables" flag is not configured in Rights and Permissions at the server, site, application, or page level.</li> 	<li>The configuration/system.webServer/handlers@accessPolicy attribute does not have Script or Execute configured.</li> 	<li>Execute access is denied when you try to run a CGI file or other executable.</li> 	<li>Script access is denied when you try to access an ASP, ASP.NET or other dynamic scripting file.</li> 	<li>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).</li> 	<li>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.</li> </ul>�<ul> 	<li>           Enable scripts to run for the requested resource.           <ol> 			<li>Open IIS Manager and navigate to the level you want to manage.</li> 			<li>On the Features page, double-click the Handler Mappings feature.</li> 			<li>On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions.</li> 			<li>In the Edit Handler Mappings dialog box, select Scripts to enable handlers that require script rights.</li> 		</ol> 	</li> 	<li>Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level.</li> 	<li>Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>^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.<ul><li>318380</li></ul>EYou have attempted to view a resource that does not have Read access.�<ul> 	<li>The Rights and Permissions setting for the requested resource does not allow Read access.</li> 	<li>The default document specified for the Web site does not exist. For example, you specified Default.htm but this file does not exist.</li> 	<li>Directory browsing is not enabled.</li> 	<li>The configuration/system.webServer/handlers@accessPolicy attribute does not have "Read" configured for the requested resource at the server, site, application, or page level.</li> </ul>�<ul> 	<li>           Enable Read access for the requested resource.           <ol> 			<li>Open IIS Manager and navigate to the level you want to manage.</li> 			<li>On the Features page, double-click the Handler Mappings feature.</li> 			<li>On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions.</li> 			<li>In the Edit Handler Mappings dialog box, select Read to enable handlers that require read access.</li> 		</ol> 	</li> 	<li>Verify the default document does exist and matches what is specified in the Web site properties.</li> 	<li>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).</li> 	<li>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.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>OThis 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.'<ul><li>247677</li><li>838790</li></ul>HYou have attempted to write to a folder that does not have Write access.)<ul> 	<li>The Rights and Permissions setting for the requested resource does not allow Write access.</li> 	<li>The configuration/system.webServer/handlers@accessPolicy attribute does not have "Write" configured for the requested resource at the server, site, application, or page level.</li> </ul>�<ul> 	<li>Enable Write access for the requested resource.</li> 	<li>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.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>ZThis 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.<ul><li>248072</li></ul>MThe page you are trying to access is secured with Secure Sockets Layer (SSL).�<ul> 	<li>Secure Sockets Layer (SSL) is enabled for the URL requested.</li> 	<li>The page request was made over HTTP, but the server requires the request from a secure channel that uses HTTPS.</li> </ul>�<ul> 	<li>Browse to the URL over a secure channel by using the "https:" prefix instead of "http:".</li> 	<li>If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting.</li> 	<li>Verify the SSL Settings in IIS Manager by connecting to the server, site, application or page and opening the SSL Settings feature.</li> 	<li>Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.</li> </ul>~This error means that the requested Web page requires SSL. Try to browse to the same URL, but use "https:" instead of "http:". �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.�<ul> 	<li>The Web server requires a 128-bit SSL connection for the requested resource, but the browser is using something less than 128-bit encryption.</li> </ul>�<ul> 	<li>Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions.</li> 	<li>Verify the SSL Settings in IIS Manager by connecting to the server, site, application, or page and opening the SSL Settings feature.</li> 	<li>Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.</li> </ul>�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.PA ]The IP address from which you are browsing is not permitted to access the requested Web site.�<ul> 	<li>The server, site, application, or page requested has explicitly denied the IP address of the client computer.</li> </ul>�<ul> 	<li>Verify the IP and domain restrictions in IIS Manager.</li> 	<li>Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.</li> </ul>|Set IP restrictions at the server, site, application, or file level. Verify or change the IP restrictions at the site level. �The page you are attempting to access requires your browser to have a Secure Sockets Layer (SSL) client certificate that the Web server recognizes.~<ul> 	<li>The page you are attempting to access requires an SSL client certificate.</li> 	<li>You are browsing to the page using HTTP.</li> 	<li>The client certificate has expired or the effective time has not been reached.</li> 	<li>The root certificate (the Certificate Authority certificate) of the client certificate issuing server is not installed on the Web server.</li> </ul>b<ul> 	<li>Contact the site administrator to obtain a valid client certificate for the Web site.</li> 	<li>Try browsing to the page using HTTPS.</li> 	<li>If you have a client certificate installed, check if it has expired or if the effective time has not been reached.</li> 	<li>Verify that the root certificate is installed on the Web server.</li> </ul>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. oThe DNS name of the computer from which you are browsing is not permitted to access the Web site you requested.<ul> 	<li>The server, site, application, or page requested has explicitly denied the DNS name of the client machine.</li> </ul><ul> 	<li>Verify or change the DNS restrictions for the requested resource.</li> 	<li>Remove the DNS restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the applicable server, site, application or page.</li> </ul>�This error occurs when a DNS restriction is set for the requested resource. Set DNS restrictions at the server, site, application, or file level.<ul><li>248032</li></ul>qThe account to which your client certificate is mapped on the Web server has been denied access to this Web site.�<ul> 	<li>The requested file or directory does not allow the user to whom the client certificate is mapped to access to the resource.</li> </ul>_<ul> 	<li>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.</li> 	<li>Check the effective date on the client certificate and ensure that the certificate is valid.</li> 	<li>Check the expiration date and ensure that the certificate has not expired.</li> 	<li>Check with the Certificate Authority that provided the certificate to see if your certificate has expired.</li> 	<li>Verify that the certificate was not explicitly denied access.</li> 	<li>Ensure that the client certificate is installed properly in the browser.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>kThe user account that the client certificate used to access the Web site was denied access to the resource.<ul><li>248075</li></ul>VYour client certificate was revoked, or the revocation status could not be determined.h<ul> 	<li>The client certificate was revoked or the revocation server could not be contacted.</li> </ul>4<ul> 	<li>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.</li> 	<li>Verify the client certificate's validity by contacting the issuer of the client certificate.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.'<ul><li>248058</li><li>294305</li></ul>HThe Web server is configured to not list the contents of this directory.�<ul> 	<li>A default document is not configured for the requested URL, and directory browsing is not enabled on the server.</li> </ul>0<ul> 	<li>If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.</li> 	<li>           Enable directory browsing using IIS Manager.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Features view, double-click Directory Browsing.</li> 			<li>On the Directory Browsing page, in the Actions pane, click Enable.</li> 		</ol> 	</li> 	<li>Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.</li> </ul>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. <Your client certificate is either not trusted or is invalid.c<ul> 	<li>The client certificate used for this request is not trusted by the Web server.</li> </ul>x<ul> 	<li>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.</li> 	<li>Verify that the client certificate is trusted by the Web server.</li> 	<li>Verify that the root certificate is properly installed and trusted on the Web server.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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. 8Your client certificate has expired or is not yet valid.j<ul> 	<li>The client certificate used to access the Web server has expired or is not yet valid.</li> </ul>�<ul> 	<li>Verify that the client certificate has not expired.</li> 	<li>Verify that the client machine's date is set correctly.</li> 	<li>Obtain a new client certificate.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>4A 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.PA yThe specified request cannot be processed in the application pool that is configured for this resource on the Web server.�<ul> 	<li>An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL.</li> 	<li>An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL.</li> 	<li>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.</li> 	<li>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.</li> </ul>�<ul> 	<li>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.</li> 	<li>If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature.</li> 	<li>Verify that the application pool for the application exists.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>%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. jThe configured user for this application pool does not have sufficient privileges to run CGI applications.�<ul> 	<li>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.</li> 	<li>If CreateProcessAsUser is true, then CGI applications are launched as the authenticated user.</li> 	<li>If CreateProcessAsUser is false, then CGI applications are launched as the process identity.</li> 	<li>           The user account under which the application pool is configured to run does not have the following privileges:           <ul> 			<li>Replace a process level token - SE_ASSIGNPRIMARYTOKEN_NAME.</li> 			<li>Adjust memory quotas for a process - SE_INCREASE_QUOTA_NAME.</li> 		</ul> 	</li> </ul>�<ul> 	<li>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.</li> 	<li>           Add the necessary privileges to the user account the application pool is running as by completing the following:           <ol> 			<li>Open the Local Security Policy settings MMC. Start %windir%\System32\Secpol.msc.</li> 			<li>Expand the Local Policies node and then click User Rights Assignment.</li> 			<li>In the right-hand pane, double-click Adjust memory quotas for a process.</li> 			<li>Add the application pool identity to this user right and then click OK.</li> 			<li>In the-right hand pane, double-click Replace a process token.</li> 			<li>Add the application pool identity to this user right and then click OK.</li> 			<li>Restart IIS for the changes to take effect.</li> 		</ol> 	</li> </ul>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. gThe resource you are looking for has been removed, had its name changed, or is temporarily unavailable.�<ul> 	<li>The directory or file specified does not exist on the Web server.</li> 	<li>The URL contains a typographical error.</li> 	<li>A custom filter or module, such as URLScan, restricts access to the file.</li> </ul>PAj<ul> 	<li>Create the content on the Web server.</li> 	<li>Review the browser URL.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�This error means that the file or directory does not exist on the server. Create the file or directory and try the request again. vThe page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server.W<ul> 	<li>No handler mapping for this request was found. A feature may have to be installed.</li> 	<li>The Web service extension for the requested resource is not enabled on the server.</li> 	<li>The mapping for the extension points to the incorrect location.</li> 	<li>The extension was misspelled in the browser or the Web server.</li> </ul>�<ul> 	<li>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.</li> 	<li>           Verify that the Web service extension requested is enabled on the server.           <ol> 			<li>Open the IIS Manager and navigate to the server level.</li> 			<li>In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed.</li> 			<li>If the extension is not in the list, click Add in the Actions pane.</li> 			<li>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.</li> 			<li>In the Description box, type a brief description of the restriction.</li> 			<li>(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.</li> 			<li>Click OK.</li> 		</ol>           NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list.         </li> 	<li>Verify that the location of the extension is correct.</li> 	<li>Verify that the URL for the extension is spelled correctly both in the browser and the Web server.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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. �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.�<ul> 	<li>It is possible that a handler mapping is missing. By default, the static file handler processes all content.</li> 	<li>The feature you are trying to use may not be installed.</li> 	<li>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.)</li> 	<li>If ASP.NET is not installed.</li> </ul>a<ul> 	<li>In system.webServer/handlers:           <ul> 			<li>Ensure that the expected handler for the current page is mapped.</li> 			<li>Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.</li> 			<li>Pay extra attention to typographical errors in the expected handler line.</li> 		</ul> 	</li> 	<li>Please verify that the feature you are trying to use is installed.</li> 	<li>           Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.           <ol> 			<li>To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']</li> 			<li>The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.</li> 			<li>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']</li> 		</ol>           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.         </li> 	<li>Install ASP.NET.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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. PALThe resource you are looking for does not have a handler associated with it.�<ul> 	<li>The file extension for the requested URL does not have a handler configured to process the request on the Web server.</li> </ul>�<ul> 	<li>If the file extension does not have a handler associated with it, add a handler mapping for the extension.</li> 	<li>Verify that the handler associated with the file extension is properly installed and configured.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>$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. DThe request filtering module is configured to deny the URL sequence.m<ul> 	<li>Request filtering is configured for the Web server and the URL sequence is being denied.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/denyUrlSequences settings in the applicationHost.config or web.config file.</li> </ul>�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. AThe request filtering module is configured to deny the HTTP verb.�<ul> 	<li>Request filtering is configured for the Web server and the HTTP verb for this request is explicitly denied.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/verbs settings in applicationHost.config and web.config.</li> </ul>�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.PA FThe request filtering module is configured to deny the file extension.�<ul> 	<li>Request filtering is configured for the Web server and the file extension for this request is explicitly denied.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/fileExtensions settings in applicationhost.config and web.config.</li> </ul>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. kThe request filtering module is configured to deny a path in the URL that contains a hiddenSegment section.�<ul> 	<li>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.</li> </ul>�<ul> 	<li>Verify configuration/system.webServer/security/requestFiltering/hiddenSegments settings in the applicationhost.config or the web.config file.</li> </ul>(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. QThis error occurs when the requested file is marked as hidden on the file system.O<ul> 	<li>The requested file is marked as hidden on the file system.</li> </ul>T<ul> 	<li>If IIS should serve the file, remove the hidden file attribute.</li> </ul>�This is a security feature that prevents displaying hidden files. Make sure the file should be served before removing the hidden file attribute. VThe request filtering module is configured to deny a request header that is too large.�<ul> 	<li>Request filtering is configured for the Web server and it is denying the request because the request header was too large.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/requestLimits/headerLimits settings in the applicationhost.config or web.config file.</li> </ul>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. dThe request filtering module is configured to deny a request that contains a double escape sequence.�<ul> 	<li>The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.</li> </ul>�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. cThe request filtering module is configured to deny a request URL that contains high-bit characters.�<ul> 	<li>The request contained high-bit characters and request filtering is configured on the Web server to deny high-bit characters.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering@allowHighBitCharacters setting in the applicationhost.config or web.config file.</li> </ul>�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. eThe request filtering module is configured to deny a request that exceeds the request content length.�<ul> 	<li>Request filtering is configured on the Web server to deny the request because the content length exceeds the configured value.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting in the applicationhost.config or web.config file.</li> </ul>�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. JThe request filtering module is configured to deny a URL that is too long.t<ul> 	<li>Request filtering is configured on the Web server to deny the request when the URL is too long.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxUrl setting in the applicationhost.config or web.config file.</li> </ul>�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.PA `The request filtering module is configured to deny a request where the query string is too long.�<ul> 	<li>Request filtering is configured on the Web server to deny the request because the query string is too long.</li> </ul>�<ul> 	<li>Verify the configuration/system.webServer/security/requestFiltering/requestLimits@maxQueryString setting in the applicationhost.config or web.config file.</li> </ul>�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. eThe page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.�<ul> 	<li>The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request.</li> 	<li>A request was sent to the server that contained an invalid HTTP verb.</li> 	<li>The request is for static content and contains an HTTP verb other than GET or HEAD.</li> 	<li>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.</li> </ul>�<ul> 	<li>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.</li> 	<li>Check the IIS log file to see which verb is not allowed for the request.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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. bThe resource cannot be displayed because the file extension is not being accepted by your browser.�<ul> 	<li>The request was rejected because it contained an Accept header for a MIME type that is not supported for the requested file extension.</li> </ul>�<ul> 	<li>Verify the MIME settings for the file extension that was requested to make sure this MIME type is acceptable.</li> </ul>�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. VThe request was not completed due to preconditions that are set in the request header.�<ul> 	<li>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.</li> </ul>V<ul> 	<li>Get a network trace and verify that these headers are correct when sending to the Web server.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>HPreconditions 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. KThe page cannot be displayed because an internal server error has occurred.�<ul> 	<li>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.</li> 	<li>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.</li> 	<li>IIS was not able to process configuration for the Web site or application.</li> 	<li>The authenticated user does not have permission to use this DLL.</li> 	<li>The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.</li> </ul>Q<ul> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Install the .NET Extensibility feature if the request is mapped to a managed handler.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li>294807</li></ul>PADThe request was not processed because the Web site is shutting down.\<ul> 	<li>A request was sent to the Web server while the worker process configured to host the Web site was shutting down.</li> 	<li>The worker process tried to shut down but experienced a hang during the shutdown process.</li> 	<li>The worker process is shutting down unexpectedly.</li> 	<li>The application pool is recycling too often.</li> </ul>
<ul> 	<li>Wait for the worker process to finish shutting down and then try the request again.</li> 	<li>           Verify the application pool settings to make sure the recycling options are not causing the application pool to restart frequently.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Connections pane, expand the server node and click Application Pools.</li> 			<li>On the Application Pools page, select the Application Pool that is recycling frequently.</li> 			<li>In the Actions pane, under Edit Application Pool, click Recycling.</li> 			<li>Review the recycling settings to ensure that the settings are not making the application pool recycle too often.</li> 		</ol> 	</li> 	<li>           Manually restart the worker process.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Connections pane, expand the server node and click Application Pools.</li> 			<li>On the Application Pools page, select the Application Pool that is recycling frequently.</li> 			<li>In the Actions pane, under Application Pool Tasks, click Stop.</li> 			<li>In the Actions pane, under Application Pool Tasks, click Start.</li> 		</ol> 	</li> 	<li>Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.</li> </ul>>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. <The request cannot process while the Web site is restarting.�<ul> 	<li>The global.asa file for the ASP application requested was modified. This caused the application to restart.</li> 	<li>Antivirus software is configured to scan the global.asa file for the ASP application.</li> </ul>�<ul> 	<li>Prevent antivirus software from scanning the global.asa file.</li> 	<li>Wait until the Web application has restarted and try the request again.</li> 	<li>Look in the event logs for messages related to application restart.</li> </ul>uThis error occurs when the global.asa file for an application was modified and caused the Web application to restart.<ul><li>248013</li></ul>iThe request cannot be processed because the amount of traffic exceeds the Web site's configured capacity.<ul> 	<li>The Web server is running at capacity and cannot accept any more requests.</li> 	<li>The server has become unstable and the ASP application cannot allocate enough memory for a new request.</li> 	<li>The ASP queue is full (ASPRequestQueueMax was reached).</li> </ul>�<ul> 	<li>           Determine which requests are running for the application and whether they are running for an abnormal amount of time.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Connections pane, select the server node in the tree.</li> 			<li>In the Features view, double-click Worker Processes to view the currently running requests.</li> 		</ol> 	</li> 	<li>Use the IIS Debugging Tools to troubleshoot the issue as a hang.</li> </ul>�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.PA TThe global.asax is a special file that you cannot access directly from your browser.J<ul> 	<li>A request was made for the global.asax file directly.</li> </ul>M<ul> 	<li>This is not allowed by the server for security purposes.</li> </ul>�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. �You cannot access the page you are requesting because the UNC authorization settings are configured incorrectly on the Web server.Z<ul> 	<li>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.</li> 	<li>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.</li> </ul>z<ul> 	<li>           Verify the credentials set for accessing the remote file share.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Connections pane, click the site that is having the problem.</li> 			<li>In the Actions pane, under Edit Site, choose Advanced Settings.</li> 			<li>Verify that the username and password are correct.</li> 		</ol> 	</li> 	<li>Check the security settings and sharing permissions for the remote UNC share hosting the content.</li> 	<li>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.</li> </ul>�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. eThe requested page cannot be accessed because the related configuration data for the page is invalid.3<ul> 	<li>The worker process is unable to read the applicationhost.config or web.config file.</li> 	<li>There is malformed XML in the applicationhost.config or web.config file.</li> 	<li>The server cannot access the applicationhost.config or web.config file because of incorrect NTFS permissions.</li> </ul><ul> 	<li>Look in the event logs for information about why the configuration files are not readable.</li> 	<li>Make sure the user identity specified for the application pool, or the authenticated user, has the required permissions to access the web.config file.</li> </ul>�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. 6The page cannot be displayed due to an error with ASP.�<ul> 	<li>This is a generic ASP error that means there was a problem while processing the requested page.</li> 	<li>Turn off Show Friendly HTTP Errors in the browser to see more information about the failure.</li> </ul><<ul> 	<li>Look in the IIS log file for additional information on the failure.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�This error occurs when the URL requested is for an ASP application and a problem occurred on the server while processing the request. }The page you are looking for cannot be displayed because a header value in the request does not match configuration settings.�<ul> 	<li>The request contains the HTTP verb "TRACE" and the registry value to enable this method is not configured on the server.</li> </ul><ul> 	<li>           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.<br></br><br></br>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters         </li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.  PAYThe specified CGI application encountered an error and the server terminated the process.�<ul> 	<li>The CGI application did not return a valid set of HTTP errors.</li> 	<li>A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.</li> </ul>�<ul> 	<li>Use DebugDiag to troubleshoot the CGI application.</li> 	<li>Determine if a proxy or gateway is responsible for this error.</li> </ul>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. [The CGI application exceeded the time allowed for processing and the process was shut down.�<ul> 	<li>The CGI application handling the request took longer than the configured CGI timeout to process the request.</li> 	<li>The CGI application is taking too long to process the request.</li> </ul>T<ul> 	<li>Verify the configured timeout for the CGI application.           <ol> 			<li>Open IIS Manager.</li> 			<li>In the Connections pane, click the site or application where the problem is occurring.</li> 			<li>In the Features pane, double-click CGI.</li> 			<li>In the CGI page, under Behavior, verify that a value is set for the Timeout property.</li> 			<li>Change the timeout value, if necessary, and then in the Actions pane click Apply.</li> 		</ol> 	</li> 	<li>Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.</li> </ul>OThis 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. LThe specified CGI application did not return a complete set of HTTP headers.�<ul> 	<li>The CGI process was shut down or terminated unexpectedly before it finished processing the request.</li> 	<li>The CGI process has a flaw and does not return a complete set of HTTP headers.</li> </ul>�<ul> 	<li>Check the event logs on the system to see whether the CGI process is shutting down unexpectedly.</li> 	<li>Troubleshoot the CGI application to determine why it is not sending a complete set of HTTP headers.</li> </ul>qThis error occurs when the CGI process handling the request exits before it finishes sending the response to IIS.PA {You have attempted to run a CGI, ISAPI or other executable program from a directory that does not allow programs to be run.L<ul> 	<li>The directory does not have Execute permission enabled.</li> </ul>J<ul> 	<li>If appropriate, add Execute access to this directory.</li> </ul>�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. TYou must be authenticated by a proxy before the Web server can process your request.h<ul> 	<li>A proxy between the client and the Web server requires some form of authentication.</li> </ul>�<ul> 	<li>To troubleshoot this error depends on the proxy. You may need to get a network trace to resolve this problem.</li> </ul>�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. {The page cannot be displayed because the client took too long to complete its request and the server closed the connection.d<ul> 	<li>The client took too long to complete its request and the connection was closed.</li> </ul>PA�<ul> 	<li>Troubleshooting this error requires the client. You may need a network trace to determine why the request was not completed by the client.</li> </ul>GThis error occurs when a client takes too long to complete its request. 8The page was not displayed because there was a conflict.q<ul> 	<li>The request could not be completed due to a conflict with the current state of the resource.</li> </ul>H<ul> 	<li>To troubleshoot this error depends upon the client.</li> </ul>RThis error occurs when there is a conflict with the current state of the resource. #The page you requested was removed./<ul> 	<li>The file has been removed.</li> </ul>�<ul> 	<li>This status code occurs when a file or resource has been removed, or when the resource is permanently unavailable and has no forwarding address.</li> </ul>pThis error occurs when a resource has been removed and the resource is not available or has no redirect address. PA`The page cannot be displayed because the server requires a Content-Length header in the request.*<ul> 	<li>The file was removed.</li> </ul>�<ul> 	<li>This status code occurs when a file or resource has been removed, or when the resource is permanently unavailable and has no forwarding address.</li> </ul>�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. ?The page was not displayed because the Request URI is too long.�<ul> 	<li>The server is refusing to service the request because the requested URL is too long.</li> 	<li>The client has encountered a redirection problem (for example, a redirected URL prefix that points to a suffix of itself).</li> 	<li>The client has improperly converted a POST request to a GET request with long query information.</li> 	<li>The Web server is under attack by the client.</li> </ul>_<ul> 	<li>Verify that the Request URI is not too long or try the request without it.</li> </ul>�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. LThe server cannot service the request because the media type is unsupported.e<ul> 	<li>The requested file is in a format that the server is configured not to download.</li> </ul>I<ul> 	<li>Verify that the requested file is in a valid format.</li> </ul>bThis error occurs when the server cannot service the request because the file type is unsupported. KThe page cannot be displayed because the request range was not satisfiable.C<ul> 	<li>The requested range of a resource was invalid.</li> </ul>><ul> 	<li>Verify that the requested range is valid.</li> </ul>XThis error occurs when the requested range is invalid or could not be met by the server. <The page cannot be displayed because the expectation failed.�<ul> 	<li>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.</li> </ul>'<ul> 	<li>Some proxy servers may not support the "100 continue" expectation. Remove this expectation or try the request without the proxy.</li> 	<li>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.</li> </ul>*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. The service is unavailable.
<ul> 	<li>An invalid identity in the application pool could cause this error.</li> 	<li>The application pool is no longer running because of configuration or reaching application failure limits.</li> 	<li>The concurrent application request limit was reached.</li> </ul>PAW<ul> 	<li>Check the event logs and the HTTP error logs for more information.</li> </ul>�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. 6The page cannot be displayed due to a gateway timeout.M<ul> 	<li>A proxy or gateway has timed out waiting for a response.</li> </ul>{<ul> 	<li>Verify that a proxy or gateway is not responsible for this error. You may need to get a network trace.</li> </ul>�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. GThe page cannot be displayed because the HTTP version is not supported.Z<ul> 	<li>The server does not support the HTTP version requested by the client.</li> </ul>a<ul> 	<li>Verify that the client is requesting an invalid or unsupported HTTP version.</li> </ul>�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. TThere is a problem with the resource you are looking for, so it cannot be displayed.s<ul> 	<li>The path to the ISAPI Filter is incorrect.</li> 	<li>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.</li> 	<li>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.</li> 	<li>IIS was not able to process configuration for the Web site or application.</li> 	<li>The authenticated user does not have permission to use this DLL.</li> </ul>-<ul> 	<li>Ensure that the path to the ISAPI DLL is correct.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li>294807</li></ul>TThere is a problem with the resource you are looking for, so it cannot be displayed.�<ul> 	<li>The ISAPI Filter has dependencies that are not available on the Web server.</li> 	<li>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.</li> 	<li>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.</li> 	<li>IIS was not able to process configuration for the Web site or application.</li> 	<li>The authenticated user does not have permission to use this DLL.</li> </ul>/<ul> 	<li>Try running Reskit tool "depends" on the ISAPI DLL.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li>294807</li></ul>CThe page was not displayed because the request entity is too large.�<ul> 	<li>The Web server is refusing to service the request because the request entity is too large.</li> 	<li>The Web server cannot service the request because it is trying to negotiate a client certificate but the request entity is too large.</li> 	<li>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.</li> </ul>v<ul> 	<li>Verify that the request is valid.</li> 	<li>If using client certificates, try:           <ul> 			<li>Increasing system.webServer/serverRuntime@uploadReadAheadSize</li> 			<li>Configure your SSL endpoint to negotiate client certificates as part of the initial SSL handshake. (netsh http add sslcert ... <b>clientcertnegotiation=enable</b>)</li> 		</ul> 	</li> </ul>�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.PA TThere is a problem with the resource you are looking for, so it cannot be displayed.�<ul> 	<li>A module is referenced in configuration, but the module has not been installed or the name of the module is misspelled.</li> 	<li>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.</li> 	<li>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.</li> 	<li>IIS was not able to process configuration for the Web site or application.</li> 	<li>The authenticated user does not have permission to use this DLL.</li> </ul>%<ul> 	<li>Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error.</li> 	<li>If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li></li></ul>TThere is a problem with the resource you are looking for, so it cannot be displayed.g<ul> 	<li>The module could not be found.</li> 	<li>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.</li> 	<li>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.</li> 	<li>IIS was not able to process configuration for the Web site or application.</li> 	<li>The authenticated user does not have permission to use this DLL.</li> </ul>�<ul> 	<li>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.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�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.<ul><li></li></ul>.A DAV request went to the static file handler.<ul> 	<li>DAV is installed and the &lt;handler&gt; entry is missing.</li> 	<li>A module set the DAV server-variable.</li> </ul>PA[<ul> 	<li>Re-install DAV.</li> 	<li>Try removing any recently installed modules.</li> </ul>�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. ]The requested content appears to be script and will not be served by the static file handler.�<ul> 	<li>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.</li> </ul>b<ul> 	<li>If you want to serve this content as a static file, add an explicit MIME map.</li> </ul>`Sometimes preconditions and a wildcard MIME map can unintentionally cause serving script source. +The specified handler mapping is incorrect.�<ul> 	<li>Managed handler is used; however, ASP.NET is not installed or is not installed completely.</li> 	<li>There is a typographical error in the configuration for the handler module list.</li> 	<li>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.</li> </ul>{<ul> 	<li>Install ASP.NET if you are using managed handler.</li> 	<li>Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".</li> 	<li>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.)</li> 	<li>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.)</li> </ul>'IIS core does not recognize the module. ]An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.b<ul> 	<li>This application defines configuration in the system.web/httpModules section.</li> </ul>�<ul> 	<li>Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, <b>%SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/"</b>. 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.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> 	<li>Alternatively, switch the application to a Classic mode application pool - for example, <b>%SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool"</b>. Only do this if you are unable to migrate your application.</li> </ul>       (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)     \Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and above. ]An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.c<ul> 	<li>This application defines configuration in the system.web/httpHandlers section.</li> </ul>�<ul> 	<li>Migrate the configuration to the system.webServer/handlers section. You can do so manually or by using AppCmd from the command line - for example, <b>%SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/"</b>. 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.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> 	<li>Alternatively, switch the application to a Classic mode application pool - for example, <b>appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool"</b>. Only do this if you are unable to migrate your application.</li> </ul>       (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)     \Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and above. ]An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.D<ul> 	<li>system.web/identity@impersonate is set to true.</li> </ul>J<ul> 	<li>If the application supports it, disable client impersonation.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> 	<li>Move this application to an application pool using Classic .NET mode - for example, <b>%SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool"</b></li> </ul>       (You can set "Classic .NET AppPool" to the name of another application pool running in Classic managed pipeline 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.PA FThe serverRuntime@appConcurrentRequestLimit setting is being exceeded.k<ul> 	<li>Setting is too low.</li> 	<li>The application is taking too long for the current load.</li> </ul>�<ul> 	<li>Try increasing the value of the setting.</li> 	<li>Check that external resources (for example, disk, database, etc..) are performing at expected levels.</li> 	<li>Check that the application has not deadlocked.</li> </ul>IIS will not allow more concurrent requests to an application than the serverRuntime@appConcurrentRequestLimit setting permits. Bad Request<ul> 	<li></li> </ul>�<ul> 	<li>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 <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>JThe request could not be understood by the server due to malformed syntax.<ul><li></li></ul>CASP.NET rejected this request because the queue limit was exceeded.~<ul> 	<li>The queue limit for ASP.NET has been exceeded. (machine.config system.web/processModel@requestQueueLimit)</li> </ul>PA�<ul> 	<li>Try increasing the value of the setting.</li> 	<li>Check that external resources (for example, disk, database, etc..) are performing at expected levels.</li> 	<li>Check that the application has not deadlocked.</li> </ul>  #The FastCGI queue has been exceededc<ul> 	<li>The system.webServer/fastCgi/application@queueLength setting has been exceeded</li> </ul>�<ul> 	<li>Try increasing the value of the setting.</li> 	<li>Check that external resources (for example, disk, database, etc..) are performing at expected levels.</li> 	<li>Check that the application has not deadlocked.</li> </ul>  No default document.�<ul> 	<li>A default document is not configured for the site.</li> 	<li>The URL contains a typographical error.</li> 	<li>Directory browsing is not enabled.</li> </ul>�<ul> 	<li>Configure a default document for this site. This is commonly default.aspx for ASP.NET and index.php for PHP. </li> 	<li>Review the browser URL.</li> 	<li>Enable directory browsing to allow listing the contents of the directory.</li> </ul>2A default document is not configured for the site. PAThe page could not be loaded.Z<ul> 	<li>PHP is not installed.</li> 	<li>PHP is not enabled for this web site.</li> </ul>�<ul> 	<li>Install PHP and configure handlers correctly.</li> 	<li>Install and enable PHP for this web site.</li> 	<li>If you are using WebMatrix, follow these steps to enable PHP:           <ul> 			<li>Open the web site in WebMatrix.</li> 			<li>Select the Site workspace and click on Settings.</li> 			<li>Check the "Enable PHP" checkbox to install and enable PHP.</li> 		</ul> 	</li> </ul>aThis error occurs when there is no handler configured to serve the document specified in the URL. The page could not be loaded.]<ul> 	<li>ASP.NET is not installed.</li> 	<li>ASP.NET is not configured correctly.</li> </ul>�<ul> 	<li>Install ASP.NET.</li> 	<li>If ASP.NET is already installed, make sure that handlers are configured correctly.</li> </ul>aThis error occurs when there is no handler configured to serve the document specified in the URL. The page could not be loaded.q<ul> 	<li>ASP.NET Web Pages is not installed.</li> 	<li>ASP.NET Web Pages is not configured correctly.</li> </ul>�<ul> 	<li>Install ASP.NET Web Pages.</li> 	<li>If ASP.NET Web Pages is already installed, make sure that handlers are configured correctly.</li> </ul>aThis error occurs when there is no handler configured to serve the document specified in the URL.PA PAModule "%s" could not be foundtOften, if SslRequireCert is set at configuration/system.webServer/access@sslFlags, then SslNegotiateCert is intended'Module "%s" has a bad precondition "%s"(Handler "%s" has a bad precondition "%s"7Handler "%s" has a bad module "%.*s" in its module list1Calling LoadLibraryEx on ISAPI filter "%s" failed2Calling GetProcAddress on ISAPI filter "%s" failed4Calling GetFilterVersion on ISAPI filter "%s" failedLISAPI filter "%s" tried to register for SF_NOTIFY_READ_RAW_DATA notificationAThe config for ISAPI filter "%s" has an unrecognized preconditionError loading ISAPI filter "%s"PA#Tracing area "%s" is not recognized'Tracing provider "%s" is not recognized%Tracing status "%s" is not recognizedPA6Hidden Segments may not contain a '/' or '\' character<The httpExpires value '%s' is not recognized as a valid dateThe CGI application exceeded the time allowed for processing and the process was terminated.  The output from the CGI was "%S".~The specified CGI application misbehaved by not returning a complete set of HTTP headers.  The headers it did return are "%S".�Absolute physical path "%s" is not allowed in system.webServer/httpErrors section in web.config file.  Use relative path instead.�<ul> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Verify that the username and password are correct, and are not cached by the browser.</li> 	<li>Use a different username and password.</li> 	<li>If you are using a custom anonymous account, verify that the password has not expired.</li> 	<li>Verify that the authenticating user or the user's group, has not been denied login access to the server.</li> 	<li>Verify that the account was not locked out due to numerous failed login attempts.</li> 	<li>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.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Verify the authentication setting for the resource and then try requesting the resource using that authentication method.</li> 	<li>Verify that the client browser supports Integrated authentication.</li> 	<li>Verify that the request is not going through a proxy when Integrated authentication is used.</li> 	<li>Verify that the user is not explicitly denied access in the "configuration/system.webServer/authorization" configuration section.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>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.</li> 	<li>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.</li> 	<li>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.)</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>PA�<ul> 	<li>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.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>=<ul> 	<li>Contact the vendor of the ISAPI extension, CGI application, ASP page, or handler that is failing the request.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>t<ul> 	<li>           Enable scripts to run for the requested resource.           <ol> 			<li>Go to the IIS Express install directory.</li> 			<li>Run <b>appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Script</b></li> 			<li>Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly.</li> 		</ol> 	</li> 	<li>Verify the configuration/system.webServer/handlers@accessPolicy setting at the server, site, application and page level.</li> 	<li>Verify that the script mapping is configured to recognize the HTTP verb you are using, and that the verb is in uppercase.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>`<ul> 	<li>           Enable Read access for the requested resource.           <ol> 			<li>Go to the IIS Express install directory.</li> 			<li>Run <b>appcmd set config /section:system.webServer/handlers /[name='HANDLER_NAME'].requireAccess:Read</b></li> 			<li>Note: Because the 'requireAccess' property is a flag property, you may have to set multiple entries in order for the handler to work properly.</li> 		</ol> 	</li> 	<li>Verify the default document does exist and matches what is specified in the Web site properties.</li> 	<li>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).</li> 	<li>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.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Enable Write access for the requested resource.</li> 	<li>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.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Browse to the URL over a secure channel by using the "https:" prefix instead of "http:".</li> 	<li>If the Web site does not have an SSL certificate or should not require HTTPS, disable the setting.</li> 	<li>If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct.</li> 	<li>Verify the configuration/system.webserver/security/access@sslFlags attribute at the server, site, application, or page level.</li> </ul>�<ul> 	<li>Configure your Web browser to use 128 bit SSL. Consult your browser documentation for configuration instructions.</li> 	<li>If you are using WebMatrix, verify the SSL settings by going to the site "Settings" location and ensuring the SSL settings are correct.</li> 	<li>Verify the configuration/system.webServer/security/access@sslFlags attribute at the server, site, application or page level.</li> </ul>PA�<ul> 	<li>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.</li> 	<li>Remove the IP restrictions from the configuration/system.webServer/security/ipSecurity section of the configuration file for the server, site, application, or page.</li> </ul>6<ul> 	<li>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.</li> 	<li>Check the effective date on the client certificate and ensure that the certificate is valid.</li> 	<li>Check the expiration date and ensure that the certificate has not expired.</li> 	<li>Check with the Certificate Authority that provided the certificate to see if your certificate has expired.</li> 	<li>Verify that the certificate was not explicitly denied access.</li> 	<li>Ensure that the client certificate is installed properly in the browser.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul><ul> 	<li>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.</li> 	<li>Verify the client certificate's validity by contacting the issuer of the client certificate.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.</li> 	<li>           Enable directory browsing.           <ol> 			<li>Go to the IIS Express install directory.</li> 			<li>Run <b>appcmd set config /section:system.webServer/directoryBrowse /enabled:true</b> to enable directory browsing at the server level.</li> 			<li>Run <b>appcmd set config ["SITE_NAME"] /section:system.webServer/directoryBrowse /enabled:true</b> to enable directory browsing at the site level.</li> 		</ol> 	</li> 	<li>Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.</li> </ul>O<ul> 	<li>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.</li> 	<li>Verify that the client certificate is trusted by the Web server.</li> 	<li>Verify that the root certificate is properly installed and trusted on the Web server.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>p<ul> 	<li>Verify that the client certificate has not expired.</li> 	<li>Verify that the client machine's date is set correctly.</li> 	<li>Obtain a new client certificate.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>k<ul> 	<li>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.</li> 	<li>If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature.</li> 	<li>Verify that the application pool for the application exists.</li> 	<li>Check the failed request tracing log and see if ExecuteURL is being called. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul><ul> 	<li>Create the content on the Web server.</li> 	<li>Review the browser URL.</li> 	<li>Check the failed request tracing log and see which module is calling SetStatus. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>           Verify that the Web service extension requested is enabled on the server.           <ol> 			<li>To list handlers, go to the IIS Express install directory, and run <b>appcmd list config /section:system.webServer/handlers</b>. Ensure that the configuration for the desired handler is correct. Run <b>appcmd set config /section:system.webServer/handlers /parameters</b> to configure the handler.</li> 			<li>Check the ISAPI and CGI restriction list. In the IIS Express install directory, run <b>appcmd list config /section:system.webServer/security/isapiCgiRestriction</b>. To change the properties, run <b>appcmd set config /section:system.webServer/security/isapiCgiRestriction /parameters</b>.</li> 		</ol>           NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list.         </li> 	<li>Verify that the location of the extension is correct.</li> 	<li>Verify that the URL for the extension is spelled correctly both in the browser and the Web server.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>F<ul> 	<li>In system.webServer/handlers:           <ul> 			<li>Ensure that the expected handler for the current page is mapped.</li> 			<li>Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.</li> 			<li>Pay extra attention to typographical errors in the expected handler line.</li> 		</ul> 	</li> 	<li>Please verify that the feature you are trying to use is installed.</li> 	<li>           Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.           <ol> 			<li>To set a MIME type, run the following command in the IIS Express install directory: <b>appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']</b></li> 			<li>The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.</li> 			<li>For example, to add a MIME map for a file which has the extension ".xyz": <b>appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']</b></li> 		</ol>           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.         </li> 	<li>Install ASP.NET.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>If the file extension does not have a handler associated with it, add a handler mapping for the extension.</li> 	<li>Verify that the handler associated with the file extension is properly installed and configured.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>PA�<ul> 	<li>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.</li> 	<li>Check the IIS log file to see which verb is not allowed for the request.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>-<ul> 	<li>Get a network trace and verify that these headers are correct when sending to the Web server.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>(<ul> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Install the .NET Extensibility feature if the request is mapped to a managed handler.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul><ul> 	<li>Ensure that the path to the ISAPI DLL is correct.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul><ul> 	<li>Try running Reskit tool "depends" on the ISAPI DLL.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>PA�<ul> 	<li>Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error.</li> 	<li>If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>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.</li> 	<li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.</li> 	<li>Check the event logs to see if any additional information was logged.</li> 	<li>Verify the permissions for the DLL.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Wait for the worker process to finish shutting down and then try the request again.</li> 	<li>           Manually restart the worker process.           <ul> 			<li>If you are using WebMatrix, open the site, and in the ribbon, click "Start".</li> 		</ul> 	</li> 	<li>Look in the event logs to determine whether the worker process is shutting down and to see the reason for the shutdown.</li> </ul>p<ul> 	<li>           Determine which requests are running for the application and whether they are running for an abnormal amount of time.           <ul> 			<li>If you are using WebMatrix, open the site. Select the Site workspace, and in the ribbon, click "Requests".</li> 		</ul> 	</li> 	<li>Use the IIS Debugging Tools to troubleshoot the issue as a hang.</li> </ul>Z<ul> 	<li>           Verify the credentials set for accessing the remote file share.           <ol> 			<li>Go to the IIS Express install directory.</li> 			<li>Run <b>appcmd list config /section:system.applicationHost/sites.</b></li> 			<li>Verify that the username and password are correct for the application.</li> 		</ol> 	</li> 	<li>Check the security settings and sharing permissions for the remote UNC share hosting the content.</li> 	<li>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.</li> </ul>kThis 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.<p></p><p></p>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.d<ul> 	<li>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 <b>appcmd migrate config "Default Web Site/"</b>. 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.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> 	<li>Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run <b>appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool"</b>. Only do this if you are unable to migrate your application.</li> </ul>PAe<ul> 	<li>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 <b>appcmd migrate config "Default Web Site/"</b>. 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.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> 	<li>Alternatively, switch the application to a Classic mode application pool. For example, from the IIS Express install directory, run <b>appcmd set app "Default Web Site/" /applicationPool:"Clr4ClassicAppPool"</b>. Only do this if you are unable to migrate your application.</li> </ul>�<ul> 	<li>If the application supports it, disable client impersonation.</li> 	<li>If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.</li> </ul><ul> 	<li>Look in the IIS log file for additional information on the failure.</li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>           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.<br></br><br></br>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters         </li> 	<li>Check the failed request tracing logs for additional information about this error. For more information, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul>�<ul> 	<li>Verify the configured timeout for the CGI application.           <ol> 			<li>Go to the IIS Express install directory.</li> 			<li>Run <b>appcmd set config /section:system.webServer/cgi /timeout:time</b> The 'time' property should be in the format hh:mm:ss.</li> 		</ol> 	</li> 	<li>Use DebugDiag to troubleshoot the CGI application and determine why it is taking so long to process the request.</li> </ul>PAWeb Management Service�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.+Internet Information Services (IIS) Manager@The IIS Manager allows you to manage the Web Application Server.10.0.0.0PA:Usage: %ws -s <site id> | -h [application host file]  
                           -w <optional root web.config file>  
                           -in <optional instance name>  
 
	-%ws 
		 This option launches a worker process using the default 
		 application host config file.  By default, it will use 
		 site id 1. 
 
	-s <site id> 
		 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 <Instance Name> 
		 Optional instance name to use.  Defaults to 'HWC-<PID>' 
 
	-w <Root web config filename> 
		 Optional root web config file to use. 
 
	-tt <Shutdown timeout in seconds> 
		 Optional parameter for graceful shutdown when user launched w3wp.exe directly, default 30s. 
		 Graceful shutdown will only be triggered by ctrl+break signal  
 
	-g  <Enable locale> 
		 Optional parameter for enabling locale to use user's setting on language,  
		 environment and culture at a cost of performance, default true.  
"Press 'Q' to shutdown the process:

Shutting down the process.

�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: There was an error reading the configuration. Please check that the configuration file is exists, is accessible and contains valid configuration.�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: There are too many application pools defined in the given configuration file. Please ensure that the configuration file contains only one application pool configuration.uERROR: There was an error processing one of the parameters.  Please ensure that all parameters are correct and valid.�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."Windows Process Activation Service�The Windows Process Activation Service (WAS) provides process activation, resource management and health management services for message-activated applications.!World Wide Web Publishing Service^Provides Web connectivity and administration through the Internet Information Services ManagerFTP Publishing Service�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.IIS Admin Service#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.ASP.NET State Service�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.Application Host Helper ServiceProvides 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.Web HostingW3C Logging Service�Provides W3C logging for Internet Information Services (IIS). If this service is stopped, W3C logging configured by IIS will not work.*Failed to initialize configuration system.&Failed to create configuration system.*Cannot find factory qualifier on class %s.%Cannot cocreate factory for class %s..Cannot get access to the process runtime data.Failed to impersonate client.)Mandatory input parameter is missing: %s.,Cannot obtain mandatory input parameter: %s.'Unsupported input parameter format: %s..Object instance properties are not loaded: %s.%s: failed to load property %s.+HTTP request runtime data is not available.Failed to enumerate appdomains.Failed to unload appdomain %s.PA7Failed to enumerate server SSL certificate information.Failed to convert parameter %s.,Failed to store SSL certificate information.-Failed to delete SSL certificate information./Cannot find section path qualifier on class %s.+Failed to create configuration for path %s.%Failed to get section %s for path %s.-Cannot get default collection for section %s.Cannot get collection count.Cannot get collection element./Cannot get schema for configuration element %s.4Cannot get property %s for configuration element %s.Cannot get element name.Object %s already exists.$Failed to create collection element..Cannot get default collection from element %s.PA!Failed to add collection element.Object %s cannot be found.+Cannot get access to the site runtime data."Failed to get site runtime status.Failed to start site.Failed to stop site.Failed to delete %s.7Cannot get access to the application pool runtime data..Failed to get application pool runtime status.!Failed to start application pool. Failed to stop application pool.#Failed to recycle application pool.)Cannot call method on abstract CIM class.VCannot change configuration path between calls to BeginUpdateBatch and EndUpdateBatch.PAWAS_W3WPWAS_W3WPjThis counter set exposes Windows Process Activation Service (WAS) related counters for the worker process.Total Requests ServedTotal Requests Served�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 Health Pings.Total Health Pings.5Total number of health pings received by the process.Total Runtime Status QueriesTotal Runtime Status Queries?Total number of Runtime Status queries received by the process.Active Listener ChannelsActive Listener ChannelsCNumber of currently active listener channels in the worker process.Active Protocol HandlersActive Protocol HandlersCNumber of currently active protocol handlers in the worker process.Total WAS Messages ReceivedTotal WAS Messages ReceivedfTotal number of messages received by the worker process from Windows Process Activation Service (WAS).Total Messages Sent to WASTotal Messages Sent to WAS`Total number of messages sent to Windows Process Activation Service (WAS) by the worker process.Health Ping Reply LatencyHealth Ping Reply LatencyYTime, in 100 nanosecond increments, taken by worker process to reply to last health ping.PA
W3SVC_W3WP
W3SVC_W3WPYThis counter set exposes HTTP request processing related counters for the worker process.Total HTTP Requests ServedTotal HTTP Requests Served;Total number of HTTP requests served by the worker process.Requests / SecRequests / Sec8HTTP requests/sec being processed by the worker process.Active RequestsActive RequestsACurrent number of requests being processed by the worker process.
Total Threads
Total ThreadsLTotal number of threads available to process requests in the worker process.Active Threads CountActive Threads CountENumber of threads actively processing requests in the worker process.Maximum Threads CountMaximum Threads CountFMaximum number of threads to which the thread pool can grow as needed.Current File Cache Memory UsageCurrent File Cache Memory Usage5Current number of bytes used by user-mode file cache.Maximum File Cache Memory UsageMaximum File Cache Memory Usage5Maximum number of bytes used by user-mode file cache.!Output Cache Current Memory Usage!Output Cache Current Memory Usage-Current number of bytes used by output cache.Current Files CachedCurrent Files CachedFCurrent number of files whose contents are present in user-mode cache.PATotal Files CachedTotal Files CacheddTotal number of files whose contents were ever added to the user-mode cache (since service startup).File Cache HitsFile Cache HitsWTotal number of successful lookups in the user-mode file cache (since service startup).File Cache MissesFile Cache MissesYTotal number of unsuccessful lookups in the user-mode file cache (since service startup).File Cache FlushesFile Cache FlushesOTotal number of files removed from the user-mode cache (since service startup).PAActive Flushed EntriesActive Flushed EntriescNumber of file handles cached in user-mode that will be closed when all current transfers complete.Total Flushed FilesTotal Flushed FileseTotal number of file handles that have been removed from the user-mode cache (since service startup).Current URIs CachedCurrent URIs Cached8URI information blocks currently in the user-mode cache.Total URIs CachedTotal URIs Cached\Total number of URI information blocks added to the user-mode cache (since service startup).URI Cache HitsURI Cache HitsVTotal number of successful lookups in the user-mode URI cache (since service startup).URI Cache MissesURI Cache MissesXTotal number of unsuccessful lookups in the user-mode URI cache (since service startup).URI Cache FlushesURI Cache Flushes:Total number of URI cache flushes (since service startup).Total Flushed URIsTotal Flushed URIsmThe number of URI information blocks that have been removed from the user-mode cache (since service startup).PACurrent Metadata CachedCurrent Metadata CachedKNumber of metadata information blocks currently present in user-mode cache.Total Metadata CachedTotal Metadata CachedaTotal number of metadata information blocks added to the user-mode cache (since service startup).Metadata Cache HitsMetadata Cache Hits[Total number of successful lookups in the user-mode metadata cache (since service startup).Metadata Cache MissesMetadata Cache Misses]Total number of unsuccessful lookups in the user-mode metadata cache (since service startup).Metadata Cache FlushesMetadata Cache FlushesITotal number of user-mode metadata cache flushes (since service startup).Total Flushed MetadataTotal Flushed MetadataeTotal number of metadata information blocks removed from the user-mode cache (since service startup).Output Cache Current ItemsOutput Cache Current Items0Number of items current present in output cache.Output Cache Total HitsOutput Cache Total HitsKTotal number of successful lookups in output cache (since service startup).PAOutput Cache Total MissesOutput Cache Total MissesMTotal number of unsuccessful lookups in output cache (since service startup).Output Cache Total FlushesOutput Cache Total Flushes@Total number of flushes of output cache (since service startup)."Output Cache Current Flushed Items"Output Cache Current Flushed Items�Number of items that have been flushed from output cache but are still being used by outgoing responses so are still taking up memory. Output Cache Total Flushed Items Output Cache Total Flushed ItemsHTotal number of items flushed from output cache (since service startup).PAFile Cache Hits / secFile Cache Hits / secERate of successful lookups in file cache during last sample interval.Metadata Cache Hits / secMetadata Cache Hits / secIRate of successful lookups in metadata cache during last sample interval.Output Cache Hits / secOutput Cache Hits / secGRate of successful lookups in output cache during last sample interval.Uri Cache Hits / secUri Cache Hits / secDRate of successful lookups in URI cache during last sample interval.PAFile Cache Misses / secFile Cache Misses / secGRate of unsuccessful lookups in file cache during last sample interval.Metadata Cache Misses / secMetadata Cache Misses / secKRate of unsuccessful lookups in metadata cache during last sample interval.Output Cache Misses / secOutput Cache Misses / secIRate of unsuccessful lookups in output cache during last sample interval.Uri Cache Misses / secUri Cache Misses / secFRate of unsuccessful lookups in URI cache during last sample interval.PA% 401 HTTP Response Sent% 401 HTTP Response Sent;Percentage of 401 HTTP response sent by the worker process.% 403 HTTP Response Sent% 403 HTTP Response Sent;Percentage of 403 HTTP response sent by the worker process.% 404 HTTP Response Sent% 404 HTTP Response Sent;Percentage of 404 HTTP response sent by the worker process.% 500 HTTP Response Sent% 500 HTTP Response Sent;Percentage of 500 HTTP response sent by the worker process.WebSocket Active RequestsWebSocket Active RequestsCWebSocket requests currently being processed by the worker process.#WebSocket Connection Attempts / Sec#WebSocket Connection Attempts / SecHWebSocket connection attempts/sec being processed by the worker process.$WebSocket Connections Rejected / Sec$WebSocket Connections Rejected / Sec9WebSocket connections rejected/sec by the worker process.$WebSocket Connections Accepted / Sec$WebSocket Connections Accepted / Sec9WebSocket connections accepted/sec by the worker process.PAAPP_POOL_WASAPP_POOL_WASHThis counter set exposes WAS related counters for IIS Application Pools.Current Worker ProcessesCurrent Worker ProcessesPThe current number of worker processes that are running in the application pool.Maximum Worker ProcessesMaximum Worker Processes�The maximum number of worker processes that have been created for the application pool since Windows Process Activation Service (WAS) started.Total Application Pool RecyclesTotal Application Pool RecycleswThe number of times that the application pool has been recycled since Windows Process Activation Service (WAS) started.Current Application Pool UptimeCurrent Application Pool Uptime`The length of time, in seconds, that the application pool has been running since it was started.Total Application Pool UptimeTotal Application Pool Uptime�The length of time, in seconds, that the application pool has been running since Windows Process Activation Service (WAS) started.PARecent Worker Process FailuresRecent Worker Process FailurestThe number of times that worker processes for the application pool failed during the rapid-fail protection interval.Total Worker Process FailuresTotal Worker Process Failures^The number of times that worker processes have crashed since the application pool was started.Current Application Pool StateCurrent Application Pool State�The current status of the application pool (1 - Uninitialized, 2 - Initialized, 3 - Running, 4 - Disabling, 5 - Disabled, 6 - Shutdown Pending, 7 - Delete Pending).%Total Worker Process Startup Failures%Total Worker Process Startup FailurescThe number of times that Windows Process Activation Service (WAS) failed to start a worker process.PA&Total Worker Process Shutdown Failures&Total Worker Process Shutdown FailuresgThe number of times that Windows Process Activation Service (WAS) failed to shut down a worker process."Total Worker Process Ping Failures"Total Worker Process Ping Failures�The number of times that Windows Process Activation Service (WAS) did not receive a response to ping messages sent to a worker process.&Time Since Last Worker Process Failure&Time Since Last Worker Process FailurehThe length of time, in seconds, since the last worker process failure occurred for the application pool.Total Worker Processes CreatedTotal Worker Processes CreatedwThe number of worker processes created for the application pool since Windows Process Activation Service (WAS) started.PA�:������-88`@u@x@x@2@:@8A]@]@4B�@�@PB	@	@LE�@�@�F�@�@@L�@�@�M�@�@<Y@@B@8ZH@H@�]J@K@p`M@M@\eU@U@�f[@[@�gZ@[@�h@@nPP�n	�	�@o��do��pd�e��pq�r��r�����s�����s�����t�����u����\w���w���w���w�"�p})�)��}+�1��}g�g�܁l�m������������h����������P�����X�����������\�����L�����������������,������	�	������,�����H�����������T�����������L�����������������������h�����������
����� ����� �&��*�*�I�I�`L�L��Q�Q�lT�T��
W�Z��
\�]��Y�Y�A�A��1#�1#��
�
��
��@����lA8�A8�������� ��!��X!���!���!��D"���"���"��#��L#���#���#��t$�
��$���&���-���/!�!��1$�/��11�A�D98�8�`E���G���Hf�p��Ks�t��T�����U����PV����X\����t\�����^��� `��X`��0n��Ln#�(��n*�*�0q;�\�Lq^�f�d�h�k���n�o�����������������������������������������������l��������������\����������p�����������$����������������|�������������	�	���	�	�4�	�	���	��	���*
�+
�@�-
�5
�t�7
�8
���
��
�t�����������#�����'����+����X,�����,����T-�����.����<6����X6�����8�����B����D���hZ��d_��$a��td���r'�)��v+�-�0~/�?�̇C�G���N�P���R�S���^�a��q�{���\�^���(#�0#�`�2#�4#�<���,��	���������,�<
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.

<Status for %1 ( %2 ) : %3

Stopped

$Stop pending

Running

,Continue pending

$Pause pending

Paused

Unknown

$Start pending

XInternet services successfully started

XInternet services successfully stopped

 Rebooting !

\Internet services successfully restarted

�Error processing command, attempting to reboot the server.

tAccess to IIS restart API disabled to this computer 

lRestarting of Internet Services has been enabled.

pRestarting of Internet Services has been disabled. 

TInternet services successfully killed

0Attempting kill...

�Access denied, you must be an administrator of the remote computer to use this

command. Either have your account added to the administrator local group of

the remote computer or to the domain administrator global group.

4Start attempt failed.

4Stop attempt failed.

8Restart attempt failed.

8Reboot attempt failed.

4Kill attempt failed.

0Attempting start...

0Attempting stop...

4Attempting reboot...

�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.

@General purpose IIS command line administration tool.



APPCMD (command) (object-type) <identifier> </parameter1:value1 ...>



Supported object types:



�

(To list commands supported by each object use /?, e.g. 'appcmd.exe site /?')



General parameters:



/?               Display context-sensitive help message.



/text<:value>    Generate output in text format (default).

                 /text:* shows all object properties in detail view.

                 /text:<attribute> 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".

�%ws



APPCMD (command) %ws <identifier> <-parameter1:value1 ...>



Supported commands:



�

(To get help for each command use /?, e.g. 'appcmd.exe add site /?'.)

|

APPCMD %ws %ws <identifier> <-parameter1:value1 ...>



@ 

Supported parameters:



$

Examples:



LMetabase 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

PMetabase 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 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 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 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 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 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 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 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

dMetabase 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 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

lMetabase 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 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

Classic

0%1 Service started.

0%1 Service stopped.

0%1 Service paused.

0%1 Service resumed.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

�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".

�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.

�IIS start 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.

�IIS reboot 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.

�Your computer is being shut down by %1. Save any work that may be lost!

$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.

8Ignoring metadata tag.

�The input contained an error element, which may indicate that the operation

producing the input has failed.

,Executed command.

TA 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 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 scheduled recycle time.

 A worker process with process id of '%1' serving application pool '%2' has requested a recycle because it reached its virtual memory limit.

dAn 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 administrator has requested a recycle of all worker processes in application pool '%1'.

�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.

hThe 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.

�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 serving application pool '%1' has requested a recycle because it reached its private bytes memory limit.

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 site '%1'.  See previously logged event(s).

�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.

tThe 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 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.

PA 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.

\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 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) started with '%1' mode using '%2'

�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 <listenerAdapters> 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 <listenerAdapters> section, and that another process has not already connected as the Listener Adapter for that protocol.

�Listener Adapter protocol '%1' successfully connected to Windows Process Activation Service.

tAnonymous logon request received from %1 at host %2.

hUser logon request received from %1 at host %2.

Error

Warning

 Information

Verbose

$Warning: %1.

,Warning: %1, %2.

4Warning: %1, %2, %3.

<Warning: %1, %2, %3, %4.

�No Default Script Language specified for Application %s.  Using default: %s.

�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 add the virtual root '%1' for the directory '%2' due to the following error: %3 The data is the error code.

hInstance %1 has invalid binding descriptor %2.

�Instance %1 has invalid secure binding descriptor %2 (host name ignored).

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

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) failed to intialize performance counters properly. The performance counters will run, but counter data may be inaccurate. The data field contains the error number.

Not used.

Not used.

Not used.

Not used.

@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'.

pThe 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 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 application pool ID for the site is null.

Not Used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

(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 failed to enable bandwidth throttling on site '%1'.  The data field contains the error number.

4The World Wide Web Publishing Service failed to enable global bandwidth throttling because QoS Packet Scheduler is not installed or it's not running.

Not used.

Not used.

�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) 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: "\"" "/" "\\" "[" "]" ":" "|" " " "<" ">" "+" "=" ";" "," "?" "*" "%" "#" "@" "{" "}" "^" "`". To fix this problem please remove invalid characters from the site bindings.

�The server was unable to read the file %1 due to a lack of access permissions.

The server stop serving requests for application '%1' because the number of Out of Process component crashes exceed a limit.

�The server failed to shut down application '%1'.  The error was '%2'.

�The server was unable to read the file %1. The file does not exist.

�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 file exceeds the maximum allowable size of %2.

�The server was unable to allocate a buffer to read the file %1.

�The server failed to load application '%1'.  The error was '%2'.

|Out of process application '%1' terminated unexpectedly.

lSite '%1' hit its CPU Limit. No action was taken.

�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. All processes on that site have been terminated.

xSite '%1' hit its CPU Limit. The site has been paused.

�The server certificate for instance '%1' has expired or is not yet valid.

�The server certificate for instance '%1' has been revoked.

�The server certificate chain does not include a trusted root certificate.

�A certificate in the server certificate chain has an invalid signature.

�CPU Limits/Accounting failed to queue work item. The data is the error.

�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'.

HThe 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 the certificate could not be found in a certificate store. The error is '%2'.

HThe 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 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 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) 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'.

DThe 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 server failed to close client connections to the following URLs during shutdown:  '%1'.

�ISAPI '%1' reported itself as unhealthy for the following reason: '%2'.

�ISAPI '%1' reported itself as unhealthy.  No reason was given by the ISAPI.

�The directory specified for caching compressed content %1 is invalid.  Static compression is being disabled.

The registry key for IIS subauthenticator is not configured correctly on local machine, the anonymous password sync feature is 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.

The registry key for IIS subauthenticator is not configured correctly on domain controller, the Digest feature is disabled.

�Worker process could not access IIS configuration store due to disconnection error.  Marking process as unhealthy.

PETW 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.

�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 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 detected invalid configuration on path '%4'. Trace provider or tracing area name '%3' is not recognized. Check the <traceProviderDefinitions> 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'. 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.

PFailedRequestTracing 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. 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.

lFailedRequestTracing 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 encountered runtime error. The problem happened at least %1 times in the last %2 minutes. The data is the error.

hFailedRequestTracing module detected invalid configuration on path '%4'. Attribute "guid" in <traceProviderDefinitions> 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 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.

�The globalModules list is empty. No requests can be served successfully.

@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.

�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 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'.  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 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.

Not used.

Not used.

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' failed to respond to a ping. The process id was '%2'.

�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' exceeded time limits during start up. The process id was '%2'.

�A process serving application pool '%1' exceeded time limits during shut down. The process id was '%2'.

�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.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

\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 Windows Process Activation Service failed to create a worker process for the application pool '%1'. The data field contains the error number.

xApplication pool '%1' exceeded its job limit settings.

A process serving application pool '%1' reported a failure. The process id was '%2'.  The data field contains the error number.

@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'.

hThe 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 virtual site %1 is invalid because valid site bindings could not be configured or no site bindings exist for the site.

Not used.

Not used.

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 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 invalid AppPoolId '%3' set.  Therefore, the application will be ignored.

dThis message has become deprecated in IIS 7.

TThe 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.

TAn 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.

�The application '%2' belongs to an invalid site '%1'.  Therefore, the application will be ignored.

�Site %1 was disabled because the application pool defined for site %2 is not a valid application pool.

lSite %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.

�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.

�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.

PCentralized 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.

tThe 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.

Not used.

Not used.

TThe Windows Process Activation Service failed to issue recycle requests to all worker processes of application pool '%1'.  The data field contains the error number.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

�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.

�Enable32bitAppOnWin64 setting will be ignored because IIS is currently running in IIS5 Compatibility mode.

pEvent id used by World Wide Web Publishing Service.

\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 stop a listener channel for protocol '%4' in the allotted time.  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.

dWindows 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.

dThis message has become deprecated in IIS 7.

�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.

@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 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'.

tThe 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.

 Available.

 Available.

 Available.

 Available.

`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.

DThe 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 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.

�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.

LA 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.

�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 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 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

\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.

xCPU time for application pool '%1' has been throttled.

The Windows Process Activation Service (WAS) failed to insert data for registration site '%1'. The data field contains the error number.

4Binding information '%1' is unsupported with dynamic mode. The Windows Process Activation Service (WAS) restart is required to register that binding.

�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.

�The Web Management Service was stopped because it did not respond.

0The 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.

�User %1 at host %2 has timed-out after %3 seconds of inactivity.

�User %1 failed to log on, could not access the home directory %2.

�User %1 denied access to the current directory %2 due to a security change.

(Invalid ProgID.

HThe 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.

PMicrosoft-Windows-IIS-Configuration

pMicrosoft-Windows-IIS-Configuration/Administrative

hMicrosoft-Windows-IIS-Configuration/Operational

dMicrosoft-Windows-IIS-Configuration/Analytic

\Microsoft-Windows-IIS-Configuration/Debug

<Microsoft-Windows-IIS-FTP

XMicrosoft-Windows-IIS-IisMetabaseAudit

HMicrosoft-Windows-IIS-IISReset

HMicrosoft-Windows-IIS-W3SVC-WP

\Microsoft-Windows-IIS-W3SVC-PerfCounters

TMicrosoft-Windows-WAS-ListenerAdapter

4Microsoft-Windows-WAS

@Microsoft-Windows-IIS-W3SVC

@Microsoft-Windows-IIS-WMSVC

LMicrosoft-Windows-IIS-APPHOSTSVC

HMicrosoft-Windows-IIS-W3LOGSVC

DMicrosoft-Windows-IIS-Logging

PMicrosoft-Windows-IIS-Logging/Logs

hA cache node for '%3' has been added to cache.

�Configuration cache is handling change notification for '%1'.

pConfiguration cache is polling for changes at '%1'.

�Configuration cache is discarding all config files whose configuration path is equal to or a subpath of '%1'.

<An error has occurred: %4

�Unable to find schema for config section '%4'. This section will be ignored.

<Parsing config file '%2'.

�MACHINE/WEBROOT/APPHOST configuration redirection has been enabled. The redirected physical path is '%1'.

`Attempting to open file or directory '%2'.

�An impersonation token with handle '%4' for the credentials of '%1\%2' has been created.

�File change notification monitor that watches for changes in '%3' has been created.

�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' received a change notification.

�File change notification monitor that watches for changes in '%3' is processing notified changes.

�File change notification monitor that watches for changes in '%3' has been destroyed.

�A change listener of type '%2' is being informed about a configuration change at '%3'.

�During schema file enumeration, the file '%1' was detected in the schema directory.

�The virtual path '%1' has been mapped to the physical path '%2'.

�The '%6' metadata of a configuration system object was set to '%7'.

�Thread is impersonating an access token belonging to handle '%2'.

|Changes to '%4' at '%2' have successfully been committed.

\Failed to commit changes to '%4' at '%2'.

\Unable to locate IIS_Schema.xml in '%1'.

HHandle '%2' duplicated to '%3'

`Unable to locate a site with SiteName '%1'.

\Unable to locate a site with SiteId '%1'.

 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 SiteName '%1' has been assigned to more than one site. Please change your configuration such that each site is assigned a unique SiteName.

Failed to instantiate '%3' when attempting to populate dynamic configuration for '%1'. This COM component may not be registered.

�Failed to initialize the '%3' encryption provider in '%1'. Please check your configuration.

LFailed to encrypt attribute '%4'.

LFailed to decrypt attribute '%4'.

�Unable to map '%1' to the subpath of any known virtual directory.

tVirtual directory mapping from '%4' to '%5' created.

�The location of the configuration file whose config path is '%1' was mapped to '%2'.

�Config/child source file for configuration '%6' specified in '%2' is being loaded.

lChanges have successfully been committed to '%1'.

�Failed to commit changes to '%2' because file on the disk has been changed.

�Checking whether file '%2' has changed on the disk returned '%9'.

 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.

XA commit operation has been initiated.

�A commit operation has completed. The status code is: '%1'.

�A kernel transaction for a commit operation has been created.

Failed to create a kernel transaction for the commit operation. The commit operation will proceed without a kernel transaction.

�Changes have successfully been committed with a kernel transaction.

�Failed to commit the changes with a kernel transaction. The changes will be reverted.

�A file write operation in a commit operation has been initiated.

�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' have successfully been erased. The size of the file is now zero.

�The new contents of the file '%2' could not be written to.

�A file write operation in a commit operation has completed. The status code is: '%1'.

�A change listener of type '%2' has been informed about a configuration change at '%3'.

tdate %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

 Error: %1.

(Error: %1, %2.

0Error: %1, %2, %3.

8Error: %1, %2, %3, %4.

�Failed to create an ASP Session due to Access Denied when activating COM+ Partition %1.

�Failed to create ASP Application %1 due to invalid or missing COM+ Partition ID.

�Failed to retrieve the Anonymous User Token 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.

�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 open ODBC Data source %1, Table: %2, under UserName %3. The ODBC Error is: %4. The data is the error code.

�The parameters specified for logging are too long. Field: %1; Data Given: %2.

`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 Creation of InetLog Context failed. The data is the error code.

�Logging information failed. The log object was never created possibly due to wrong configuration.

�The server was unable to find the log file directory %1. The data is the error code.

0The 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.

XThe server has resumed request logging.

�The service could not initialize the socket library.  The data is the error code.

�The service could not find module %1.  The data is the error code.

�The service could not bind instance %1.  The data is the error code.

�The service metabase path '%1' could not be opened.  The data is the error code.

pUNC Access failed for file - %s with the error = %d

Not used.

�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 site has been disabled. 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.

Not used.

�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.

Not used.

Not used.

8The 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.

XThe 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.

Not Used.

Not used.

�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.

Application pool %1 has been disabled. The HTTP.sys request to enable the application pool failed. The data contains the error number.

Not used.

pThe 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.

Not used.

Not Used.

4The 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.

xThe 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.

xThe 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 site's log file directory is not fully qualified, which may be because it is missing the drive letter or other important information.

Not used.

The HTTP control channel for the World Wide Web Publishing Service (WWW Service) did not open. The data field contains the error number.

Not Used.

Not Used.

Not used.

Not used.

Not used.

Not used.

Not used.

 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.

Not used.

Not used.

Not used.

DHTTP.SYS provided inconsistent site performance counter data to the World Wide Web Publishing Service (WWW Service), so the WWW Service will ignore the data.

Application pool %1 was not disabled. The HTTP.sys request to disable the application pool failed. The data contains the error number.

Not used.

XThe World Wide Web Publishing Service failed to properly configure the load balancer capabilities on application pool '%1'.  The data field contains the error number.

LThe 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.

Not used.

LThe 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.

Not used.

Not used.

Not used.

Not used.

Not used.

<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 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 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 max connections 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.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

DThe World Wide Web Publishing Service (WWW Service) failed to set the filter configuration for the control channel. The data field contains the error number.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

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 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 publish the performance counters that it gathered from HTTP.SYS. The data field contains the error number.

DThe World Wide Web Publishing Service (WWW Service) failed to cancel the timer for gathering performance counters. The data field contains the error number.

4The 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 start the timer for gathering performance counters. 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.

 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) 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. 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. HTTP.sys has been configured to listen to too many ports. The site has been disabled. The data field contains the error number.

0The 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 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) 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 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) 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.

HThe 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 start dynamic site registration handler. 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.

�Unable to query the W3SVC (HTTP) service performance data. The error code returned by the service is data DWORD 0.

�It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.

�Setting up Web Service counters failed, please make sure your Web Service counters are registered correctly.

`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.

�HTTP Server could not initialize its security.  The data is the error.

�HTTP Server could not initialize the socket library.  The data is the error.

�HTTP Server was unable to initialize due to a shortage of available memory.  The data is the error.

�HTTP Server could not create the main connection socket.  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.

�The HTTP Filter DLL %1 failed to load.  The data is the error.

The script started from the URL '%1' has not responded within the configured timeout period.  The HTTP server is terminating the script.

�The HTTP server encountered an error processing the server side include file '%1'.<BR>The error was '%2'.<BR>

�The HTTP server encountered an unhandled exception while processing the ISAPI Application '%1'.

�The HTTP server was unable to load the ISAPI Application '%1'. The data is the error.

�A server side include file has included itself or the maximum depth of server side includes has been exceeded.

�The server was unable to acquire a license for a SSL connection.

hJob object query failed. The data is the error.

pJob object set limit failed. The data is the error.

�Schedule a work item for CPU Accounting or Limits failed. The data is the error.

�The COM Application '%1' at '%2' failed to activate out of process.

PAn 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.

�Could not load all ISAPI filters for site '%1'.  Therefore site startup aborted.

�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.

�IIS Client certificate mapping configuration for site %1 failed to be loaded. The data field contains the error number.

�Could not initialize the logging module for site %1.  The site will therefore be non-functional.

�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.

�The worker process failed to initialize correctly and therefore could not be started.  The data is the error.

|The Module DLL %1 failed to load.  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.

�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 name %1 path %2 returned an error from registration.  The data is the error.

�The worker process failed to pre-load .Net Runtime version %1.

�Failed to find the RegisterModule entrypoint in the module DLL %1.  The data is the error.

�The Module name '%1' path '%2' has an invalid precondition '%3'.

|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.

An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: %1. The data is the error.

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 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.

pThe 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 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.

0The 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 worker process for application pool '%1', PID='%2', failed to duplicate the request queue handle and therefore will not be able to provide transport-level telemetry data during request processing.  The data field contains the error number.

T<B>Error processing SSI file</B><BR>

@<B>Invalid SSI Tag</B><BR>

�<B>Cannot perform flastmod(): Win32 Error Code = %2!.20s!</B><BR>

�<B>Cannot perform fsize(): Win32 Error Code = %2!.20s!</B><BR>

h<B>Variable '%1!.40s!' cannot be found</B><BR>

p<B>Variable '%1!.40s!' cannot be evaluated</B><BR>

T<B>SSI feature not supported</B><BR>

�<B>Error handling SSI File :  Win32 Error Code = %2!.20s!</B><BR>

T<B>Failed to process SSI file</B><BR>

�<B>Failed to execute CMD :  Win32 Error Code = %2!.20s!</B><BR>

�<B>Failed to execute CGI :  Win32 Error Code = %2!.20s!</B><BR>

�<B>Failed to execute ISAPI extension :  Win32 Error Code = %2!.20s!</B><BR>

�<B>Cannot #EXEC file due to lack of EXECUTE permission</B><BR>

p<B>Cannot process file due to access denied</B><BR>

�<B>A server side include file has included itself or the maximum depth of server side includes has been exceeded.</B><BR>

|<B>The CMD option is not enabled for #EXEC calls</B><BR>

�<B>#EXEC calls have been disabled for this virtual path</B><BR>

h<B>There is a recursive #INCLUDE chain</B><BR>

�<B>Failed to execute script:  Http Status Code = %2!.20s!</B><BR>

,<p>

The form you just filled in requires the <b>%1</b> entry to be filled in. Please fill in that entry in the form and resubmit the form.

</p>

<p>

The query file could not be opened. The file may not exist or you may have insufficient permission to open the file.

</p>

�<p>

The template file contains an <i>else</i> tag without a matching <i>if</i> tag.

</p>

�<p>

The template file contains an <i>endif</i> tag without a matching <i>if</i> tag.

</p>

x<p>

The template file contains an expression with parameters that are of different type. For example, an <i>if</i> tag comparing a string with a number would cause this error.

</p>

x<p>

The template file contains an expression using the <i>CONTAINS</i> operator where one or both parameters are not strings. <i>CONTAINS</i> is only valid with string values.

</p>

�<p>

The template file contains an expression that uses a quoted string but the close quote is missing.

</p>

@<p>

The template file contains an expression with an unrecognized operator. Valid operators are <i>GT</i>, <i>LT</i>, <i>EQ</i> and <i>CONTAINS</i>.

</p>

�<p>

The query file contains an unrecognized field <b>%1</b>.

</p>

�<p>

The query file must contain a valid, non-empty <i>Datasource:</i> field and <i>SQLStatement:</i> field.

</p>

xContent-type: text/html



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<html dir=ltr>

<head>

<META NAME="ROBOTS" CONTENT="NOINDEX">

<title>The page cannot be displayed</title>

<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">

</head>

<body>

<h1>

The library odbc32.dll could not be loaded to perform the query. Make sure ODBC has been properly installed on the server.

</h1>

</body>

</html>

�Content-type: text/html



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<html dir=ltr>

<head>

<META NAME="ROBOTS" CONTENT="NOINDEX">

<title>The page cannot be displayed</title>

<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">

</head>

<body>

<h1>

Error performing query.

</h1>

%1

</body>

</html>

�<p>

The maximum number of SQLStatement fields in the IDC file has been exceeded.

</p>

�Configuration file '%1' does not contain a root <configuration> tag

\Configuration file is not well-formed XML

�Only one <configSections> element allowed.  It must be the first child element of the root <configuration> element   

<Unrecognized element '%1'

@Unrecognized attribute '%1'

�The '%1' attribute must be one of the following values: %2

pThe '%1' attribute must be specfied on the '%2' tag

\There is a duplicate '%1' section defined

hThere is a duplicate '%1' section group defined

�The configuration section '%1' cannot be read because it is missing a section declaration

LError parsing the schema file: %1

HMissing required attribute '%1'

TCannot add duplicate collection entry

PAttribute '%1' has already been set

`Configuration element '%1' already defined

(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".

Config section '%1' already defined. Sections must only appear once per config file. See the help topic <location> for exceptions

TString value must not be empty string

�Timespan value must be between %1 and %2 seconds.  Its granularity must be %3 seconds

XInteger value must be between %1 and %2

�<location> section path attributes must be unique per config file

hlockAttributes contains unknown attribute '%1'

�Only one of 'lockAttributes'/'lockAllAttributesExcept' must be specified

tlockAllAttributesExcept contains no known attributes

`lockElements contains unknown element '%1'

�Only one of 'lockElements'/'lockAllElementsExcept' must be specified

(Lock violation

PlockItem must be either true/false

Only one <configProtectedData> element allowed.  It must be the first child element of the root <configuration> element   

�<configProtectedData> element can only contain <providers>

TCan not have duplicate provider names

lEncryption provider must specify 'name' attribute

lEncryption provider must specify 'type' attribute

LFailed to decrypt attribute '%1'

\Location path contains invalid characters

XCan not find matching virtual directory

�Can not log on locally to %1 as user %2 with virtual directory password

tConfiguration section not allowed in a <location> tag

�Configuration section not allowed to be set below application

�Configuration section can only be set in ApplicationHost.config

TUnrecognized configuration path '%1'

dTimespan must be of form [-][d.]hh:mm:ss[.ff]

0Not a valid integer

\Boolean must be either 'true' or 'false'

PThe '%1' attribute is invalid.  %2

8Enum must be one of %1

TFlags must be some combination of %1

�Timespan value must be between %1 and %2 seconds inclusive, with a granularity of %3 seconds

lInteger value must be between %1 and %2 inclusive

<String must not be empty

`configSource must exist alone in an element

PconfigSource not allowed in element

XSpecified configSource cannot be parsed

xconfigSource must only be specified at an empty element

\Element is missing required attributes %1

�Must specify only one lockdown directive ('allowOverride' or 'overrideMode')

dLocation path ends with an invalid character

HCannot read configuration file

pString value must not start or end with white space

LCannot overwrite defaultProvider

DInvalid application pool name

,Invalid site name

DMissing required element '%1'

<Invalid section name '%1'

llockAllElementsExcept contains no known elements

\Filename: %1

Line number: %2

Error: %3

tThe attribute '%1' is required and cannot be locked.

tInteger value must not be between %1 and %2 inclusive

�Timespan value must not be between %1 and %2 seconds inclusive, with a granularity of %3 seconds

<Invalid application path

HInvalid virtual directory path

4Expected element '%1'

�Cannot overwrite %1 behavior in collections with multiple element schemas

pCollection defaults not allowed for this collection

�Add/remove/clear element '%1' already specified for this collection

`Could not find collection's defaultElement

TValidation parameter '%1' is invalid

XBoth '%1' and '%2' can not be specified

HSchema for '%1' already exists

HFailed to open schema file '%1'

xConfiguration section can only be set in machine.config

�Configuration section can only be set in machine.config or root web.config

DNot a valid unsigned integer

�Cannot read configuration file due to insufficient permissions

<Macro '%1' is not defined

XOnly one '%1' element must be specified

XNo suitable default for given attribute

This configuration section cannot be modified at this path because allowSubDirConfig="false" is set on the parent virtual directory

�Cannot read configuration file because it exceeds the maximum file size

�Failed to decrypt attribute '%1' because the keyset does not exist

�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 attributes '%2' respectively set to '%3'

�Cannot add duplicate collection entry of type '%1' with combined key attributes '%2' respectively set to '%3'

8Cannot add duplicate collection entry of type '%1' with unique key attribute '%2' set to '%3' and combined key attributes '%4' respectively set to '%5'

TCannot 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'

�The root element of a childSource configuration file cannot have any attributes

`There is a duplicate flag name '%1' defined

pThere is a duplicate enumeration name '%1' defined

�Attribute '%1' is not part of a collection element.  Therefore '%2' cannot be 'true'

lConfiguration section encryption is not supported

�The configuration section '%1' cannot be read because it is missing schema

�Can not log on locally to %1 as user %2 with redirection.config password

�Cannot read configuration file because the network path is not found

�Cannot commit configuration changes because the file has changed on disk

�This configuration section cannot be modified because it has been opened for read only access

�Cannot write configuration file due to insufficient permissions

8Filename: %1

Error: %2

HCannot write configuration file

@Invalid validationType '%1'

<Failed to process input.

xFailed to initialize the COM subsystem (HRESULT=%%08x).

xFailed to obtain the executable handle (HRESULT=%%08x).

�Failed to initialize command processor: %%ws (HRESULT=%%08x).

�Please specify an object.  Run 'appcmd.exe' to display supported objects.

�Object '%ws' is not supported.  Run 'appcmd.exe /?' to display supported objects.

�Command '%ws' is not supported on object '%ws'. Run 'appcmd.exe %ws /?'

to display supported commands.

pFailed to setup command processor (HRESULT=%%08x).

LFailed to obtain output filters.

XFailed to obtain input for command: %0

@Command execution failed.  

LFailed to generate item output.  

\Failed to commit configuration changes.  

hFailed to process input: %%ws (HRESULT=%%08x).

dThe parameter '%1' must begin with a / or -%0

�The /text parameter is not allowed when using /xml or /config%0

LToo many parameters to display%0

DUnknown tool parameter '%1'%0

�Invalid XML input - please make sure that your XML is well-formed and follows the required format%0

$ (required)%0

HDuplicate parameters passed: %1

Application pool '%1' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.

,WAS_NOT_USED_5006

pEvent id used by World Wide Web Publishing Service.

<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.

Not used.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

Not Used.

LVirtual 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.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

dThe 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.

pEvent id used by World Wide Web Publishing Service.

PWindows Process Activation Service terminated unexpectedly and the system was not configured to restart it.  The Windows Process Activation Service has shut down.

Not Used.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number.

pEvent id used by World Wide Web Publishing Service.

Not Used.

Not Used.

<The Windows Process Activation Service received a change notification, but was unable to process it correctly.  The data field contains the error number.

DWindows Process Activation Service (WAS) did not run the automatic shutdown executable %2 for application pool %1. The data field contains the error number.

TApplication pool %1 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

|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 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.

pEvent id used by World Wide Web Publishing Service.

LThe Windows Process Activation Service encountered a failure requesting IIS configuration store change notifications.  The data field contains the error number.

pThe 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.

tThe 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.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

0The Windows Process Activation Service (WAS) did not apply configuration changes to application pool %1. The data field contains the error number.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

8The Windows Process Activation Service failed to properly configure the job object for application pool '%1'. The data field contains the error number.

pEvent id used by World Wide Web Publishing Service.

Not used.

DThe 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 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 overlap recycle for application pool '%1' worker process '%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.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

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 (WAS) did not create application pool %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.

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 (WAS) did not delete application pool %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.

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 (WAS) did not modify application pool %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.

pEvent id used by World Wide Web Publishing Service.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

�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.

Not used.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pEvent id used by World Wide Web Publishing Service.

pWindows 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) 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.

4Windows 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

�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.

8Application 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.

0Application 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.

�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.

�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.

HWindows 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 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.

HWindows 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.

�Site %1 has no root application defined, so the site will be ignored.

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 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) 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 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.

 Available.

8The Windows Process Activation Service couldn't process configuration information for listener adapter '%1'.  The data field contains the error number.

HThe 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 had an error setting the identity for listener adapter '%1'.  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.

�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 '%1' '%2' has an invalid value for property '%3'.  The configured value '%4' is invalid.  The value will default to '%5'.

�The listener adapter serving the '%1' protocol disconnected unexpectedly.

 Available.

`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.

�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.

The config node '%1' has an invalid value for property '%2'.  The configured value '%3' is invalid.  The value will default to '%4'.

DThe 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'.

xThe 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.

�No virtual sites have been configured 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.

�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.

8The 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 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.

0The 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 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 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.

�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.

�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.

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.

PA 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.

xThe 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 (WAS) failed to execute initialization for offline setup. The data field contains the error number.

tThe Windows Process Activation Service (WAS) encountered an error while handling migration. This will prevent WAS from starting corrently. The data field contains the error number.

|The Windows Process Activation Service (WAS) encountered an error while handling key generation. This will prevent WAS from starting corrently. The data field contains the error number.

TW3C Logging Service failed to start.

�W3C Logging Service failed to create the log file directory '%2' for site id '%1'.

�W3C Logging Service failed to create log file '%2' for site id '%1'.

�W3C Logging Service failed to write to the log file '%2' for site id '%1'.

�W3C Logging Service failed to connect to the pipe server in the worker process with pipe name '%1'.

�W3C Logging Service failed to write message to the pipe server in the worker process with id '%1'.

PW3C Logging Service failed to stop.

�W3C Logging Service is stopping because it encountered an error. The data field contains the error number.

�Owner of log file or directory '%2' for site id '%1' is invalid.

�W3C Logging Service failed to read config for site id '%1'.

�'%1' ETW session events to W3C Logging Service were dropped. You will not find some entries in the log file.

\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' 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' 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.

lThe 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 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 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 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 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 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.

DThe 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 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 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 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.

TThe 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 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.

�FTP Server could not initialize its security.  The data is the error.

�FTP Server could not initialize the socket library.  The data is the error.

�FTP Server was unable to initialize because of a shortage of available memory. The data is the error.

�FTP Server could not locate the FTP/TCP service.  The data is the error.

�FTP Server could not create the main connection socket.  The data is the error.

�FTP Server could not create the main connection thread.  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.

�A call to a system service failed unexpectedly.  The data is the error.

�Failed to read metabase property PassivePortRange under the FTP Service node %1.

�The FTP Service configuration property PassivePortRange has invalid value: %1.

Standard

4Application Isolation

4AppHostChangeHandler

Add

Delete

Modify

<ConfigurationReadFailure

0UuencodeApiFailure

0UudecodeApiFailure

DCryptAcquireContextApiFailure

<CryptGetUserKeyApiFailure

<CryptExportKeyApiFailure

<CryptImportKeyApiFailure

@CryptGetKeyParamApiFailure

@ThreadImpersonationFailure

PInvalidKeyAlgorithmForAesProviderr

@CryptProtectDataApiFailure

DCryptUnprotectDataApiFailure

8CryptEncryptApiFailure

8CryptDecryptApiFailure

4CryptGenKeyApiFailure

<CryptGenRandomApiFailure

Unknown

Xml

Config

Other

x4VS_VERSION_INFO��
|O
|O?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationJFileDescriptionIIS Resource DLLh$FileVersion10.0.20348.1 (WinBuild.160101.0800)6InternalNameiisres.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenameiisres.dll.mui\ProductNameInternet Information Services>
ProductVersion10.0.20348.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX