Process Model Settings for an Application Pool

To set an AppPool to run under a different user, in poqwershell :

Set-ItemProperty IIS:\AppPools\MyAppPool -name processModel.identityType -value X

Where X =
0 = LocalSystem
1 = LocalService
2 = NetworkService
3 = SpecificUser
4 = ApplicationPoolIdentity

http://www.iis.net/configreference/system.applicationhost/applicationpools/add/processmodel

List all IIS Web Applications with the .net version, the state of the Web Application and the assigned user/identity.

List all IIS Web Applications with the .net version, the state of the Web Application and the assigned user/identity.

try{
Import-Module WebAdministration
Get-WebApplication

$webapps = Get-WebApplication
$list = @()
foreach ($webapp in get-childitem IIS:\AppPools\)
{
$name = "IIS:\AppPools\" + $webapp.name
$item = @{}

$item.WebAppName = $webapp.name
$item.Version = (Get-ItemProperty $name managedRuntimeVersion).Value
$item.State = (Get-WebAppPoolState -Name $webapp.name).Value
$item.UserIdentityType = $webapp.processModel.identityType
$item.Username = $webapp.processModel.userName
$item.Password = $webapp.processModel.password

$obj = New-Object PSObject -Property $item
$list += $obj
}

$list | Format-Table -a -Property "WebAppName", "Version", "State", "UserIdentityType", "Username", "Password"

}catch
{
$ExceptionMessage = "Error in Line: " + $_.Exception.Line + ". " + $_.Exception.GetType().FullName + ": " + $_.Exception.Message + " Stacktrace: " + $_.Exception.StackTrace
$ExceptionMessage
}

the output is a table:

WebAppName	Version	State	UserIdentityType	Username	Password
Web123	v2.0	Started	SpecificUser	test\webuser	P@55w04D

From : https://melcher.it/2013/03/powershell-list-all-iis-webapplications-net-version-state-identity/

Rename website, virtual directory and/or application in IIS 7, 8, 8.5

There is no way to rename a newly created website and an application running beneath via the GUI.

You'd have to delete and recreate your entire site to be able to correct any issue.

However it can be performed from the command line using the appcmd.exe tool.

Start CMD Prompt and ensure you “Run as Administrator” and use the following commands:

                    cd C:\Windows\SysWOW6\inetsrv\

                    appcmd set site ExistingSiteName -name:NewSiteName

Done!

If you need to rename a Virtual Directory

appcmd set VDIR “Default Web Site/oldVDirName” -path:/newVDirName

For Applications under that virtual directory.

 appcmd set APP “Default Web Site/oldVDirName/MyApplication” -path:/newVDirName/MyApplication

To test run the following command to list results.

appcmd list Site

appcmd list VDIR

appcmd list APP

Show unused / disconnected devices in Device Manager

Normally the device manager only shows currenly loaded and in use drivers and devices.

This makes removing none connected devices and unused drivers difficult.

from windows, run cmd.exe, type: set devmgr_show_nonpresent_devices=1

Then start devmgmt.msc

From the gui select "View" -> "Show hidden devices"

now you can delete non-used drivers /devices.

Force a network drive to disconnect in Windows with NET USE /delete

An undocumented switch exists to force to disconnect a network drive using NET USE :

NET USE K: /DELETE /YES

The /YES switch forces the disconnection, also if files are open, the disconnect succeeds without promting the user.

Without this the user will be prompted yes / no to continue

Graceful Logoff from a Published Application Renders the Session in Active State

Taken from : http://support.citrix.com/article/ctx891671

Symptoms or Error

Graceful logoffs from a published application launched in a seamless, fixed window, or as an RDP Initial Program, might result in the session not closing and the user being logged off. Sessions can be reset or exited correctly by manually resetting them, or by terminating remnant user processes in Terminal Services Administration, the Management Console, or Access Suite Console.

---

Solution

Complete the following steps:

1. Determine if the application in question and its associated processes correctly exit on a windows workstation outside of a Terminal Services environment.
2. If they do not, then it is possible that this mechanism might not work or it might be necessary to contact the application manufacturer.
3. Add the process file name to the following registry key:
   Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
   Value Name:LogoffCheckSysModules
   Type:REG_SZ
   String:MyAppName.exe

Notes:

• Do not place the executable name of the main published application in this key because this might result in failure to properly launch the published application. There is an issue if the main executable for the specified published application is not terminating correctly.
• Do not place the executable name of a secondary process that has a visible window in this key. This mechanism is designed to exit secondary processes that do not have a visible window, as it is expected that if an application window is visible, then it is intended for the user to see it, and therefore close it themselves.
  The application might not appear to present a visible window or a system tray icon in a seamless session. Run the application in a fixed window, perform the function within the application that spawns the secondary process and minimize the main application window. The spawned window is displayed in the background. An RDP initial application session configured on the RDP listener exhibits the same behavior. If a customer uses a logoff script, the logoff script could be used to check for the spawned process and terminate the process. Ideally, the application should close all child process that it spawns.
• Enter the list of executable names with a comma and NO spaces between them, for example:
  App1.exe,app2.exe,app3.exe

Common HTTP status codes and the causes

Common HTTP status codes and the causes

Code	Description	Notes
200	OK	IIS 7.0, IIS 7.5, and IIS 8.0 successfully processed the request.
304	Not modified	The client browser requests a document that is already in the cache, and the document has not been modified since the document was cached. The client browser uses the cached copy of the document instead of downloading the document from the server.
400	Bad request	The Http.sys file blocks IIS 7.0, IIS 7.5, and IIS 8.0 from processing the request because of a problem in the request. Typically, this HTTP status code means that the request contains characters or sequences that are not valid or that the request contradicts the security settings in the Http.sys file.
401.1	Logon failed	The logon attempt is unsuccessful probably because of a user name or a password that is not valid. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942044 Error message when you try to run a web application that is hosted on IIS 7.0: "HTTP Error 401.1 - Not Found"
401.2	Logon failed due to server configuration	This HTTP status code indicates a problem in the authentication configuration settings on the server. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942043 Error message when you try to visit a webpage that is hosted on IIS 7.0: "HTTP Error 401.2 - Unauthorized"
401.3	Unauthorized due to ACL on resource	This HTTP status code indicates a problem in the NTFS file system permissions. This problem may occur even if the permissions are correct for the file that you are trying to access. For example, this problem occurs if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942042 Error message when you try to browse a webpage that is hosted on a server that is running IIS 7.0: "HTTP Error 401.3 - Unauthorized"
401.4	Authorization failed by filter	An ISAPI filter does not let the request be processed because of an authorization problem. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942079 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 401.4 - Authorization failed by filter"
401.5	Authorization failed by ISAPI/CGI application	An ISAPI application or a Common Gateway Interface (CGI) application does not let the request be processed because of an authorization problem. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942078 Error message when you visit a website that is hosted on a computer that is running IIS 7.0: "HTTP Error 401.5 - Authorization failed by ISAPI/CGI application"
403.1	Execute access forbidden	The appropriatelevel of the Execute permission is not granted. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942065 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.1 - Forbidden"
403.2	Read access forbidden	The appropriate level of the Read permission is not granted. Verify that you have set up IIS 7.0, IIS 7.5, and IIS 8.0 to grant the Read permission to the directory. Additionally, if you use a default document, verify that the default document exists. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942036 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.2 - Forbidden"
403.3	Write access forbidden	The appropriate level of the Write permission is not granted. Verify that the IIS 7.0, IIS 7.5, and IIS 8.0 permissions and the NTFS file system permissions are set up to grant the Write permission to the directory. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942035 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.3 - Forbidden"
403.4	SSL required	The request is made over a nonsecure channel, and the web application requires a Secure Sockets Layer (SSL) connection. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942070 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.4 - Forbidden"
403.5	SSL 128 required	The server is configured to require a 128-bit SSL connection. But, the request is not sent by using 128-bit encryption. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942069 Error message when you try to browse a webpage that is hosted on IIS 7.0: "HTTP Error 403.5 - Forbidden"
403.6	IP address rejected	The server is configured to deny access to the current IP address. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942068 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.6 - IP Address Rejected"
403.7	Client certificate required	The server is configured to require a certificate for client authentication. But, the client browser does not have an appropriate client certificate installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942067 Error message when you try to run a web application that is hosted on a server that is running IIS 7.0: "HTTP Error 403.7 - Forbidden"
403.8	Site access denied	The server is configured to deny requests based on the Domain Name System (DNS) name of the client computer. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942066 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.8 - Forbidden"
403.12	Mapper denied access	The page that you want to access requires a client certificate. But, the user ID that is mapped to the client certificate is denied access to the file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942064 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.12 - Client Certificate Denied"
403.13	Client certificate revoked	The client browser tries to use a client certificate that was revoked by the issuing certification authority. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942063 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.13 - Forbidden"
403.14	Directory listing denied	The server is not configured to display a content directory listing, and a default document is not set. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942062 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.14 - Forbidden"
403.16	Client certificate is untrusted or invalid.	The client browser tries to use a client certificate that is not trusted by the server that is running IIS 7.0, IIS 7.5, or IIS 8.0 or that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942061 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.16 - Forbidden"
403.17	Client certificate has expired or is not yet valid.	The client browser tries to use a client certificate that is expired or that is not yet valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942038 Error message when you try to visit a webpage that is hosted on Internet Information Services 7.0: "HTTP Error 403.17 (Forbidden) - The client certificate has expired"
403.18	Cannot execute requested URL in the current application pool.	A custom error page is configured, and the custom error page resides in a different application pool than the application pool of the requested URL. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942037 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.18 - Forbidden"
403.19	Cannot execute CGI applications for the client browser in this application pool.	The identity of the application pool does not have the Replace a process level token user right. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942048 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 403.19 - Forbidden"
404.0	Not found.	The file that you are trying to access was moved or does not exist. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942041 Error message when you try to open a webpage that is hosted on IIS 7.0: "HTTP Error 404.0 - Not Found"
404.2	ISAPI or CGI restriction.	The requested ISAPI resource or the requested CGI resource is restricted on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942040 Error message when you try to visit a webpage that is hosted on a computer that is running IIS 7.0: "HTTP Error 404.2 – Not Found"
404.3	MIME type restriction.	The current MIME mapping for the requested extension type is not valid or is not configured. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942032 Error message when users visit a website that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.3 - Not Found"
404.4	No handler configured.	The file name extension of the requested URL does not have a handler that is configured to process the request on the Web server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942052 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.4 - Not Found"
404.5	Denied by request filtering configuration.	The requested URL contains a character sequence that is blocked by the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942053 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.5 - URL Sequence Denied"
404.6	Verb denied.	The request is made by using an HTTP verb that is not configured or that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942046 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.6 - VERB_DENIED"
404.7	File extension denied.	The requested file name extension is not allowed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942045 Error message when you try to browse a webpage that is hosted on IIS 7.0: "HTTP Error 404.7 - FILE_EXTENSION_DENIED"
404.8	Hidden namespace.	The requested URL is denied because the directory is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942047 Error message when you try to visit a webpage that is hosted on IIS 7.0: "HTTP Error 404.8 - HIDDEN_NAMESPACE"
404.9	File attribute hidden.	The requested file is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942049 Error message when you try to visit a website that is hosted on IIS 7.0: "HTTP Error 404.9 - File Attribute Hidden"
404.10	Request header too long.	The request is denied because the request headers are too long. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942077 Error message when you visit a website that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.10 - REQUEST_HEADER_TOO_LONG"
404.11	Request contains double escape sequence.	The request contains a double escape sequence. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942076 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.11 - URL_DOUBLE_ESCAPED"
404.12	Request contains high-bit characters.	The request contains high-bit characters, and the server is configured not to allow high-bit characters. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942075 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.12 - URL_HAS_HIGH_BIT_CHARS"
404.13	Content length too large.	The request contains a Content-Length header. The value of the Content-Length header is larger than the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942074 Error message when you visit a website that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE"
404.14	Request URL too long.	The requested URL exceeds the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942073 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.14 - URL_TOO_LONG"
404.15	Query string too long.	The request contains a query string that is longer than the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942071 Error message when you visit a website that is hosted on a server that is running IIS 7.0: "HTTP Error 404.15 - Not Found"
404.17	Dynamic content mapped to the static file handler.	For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2019689 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 404.17 - Not Found"
405.0	Method not allowed.	The request is made by using an HTTP method that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942051 Error message when a user visits a website that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 405.0 - Method not allowed"
406.0	Invalid MIME type.	The request is made by using an Accept header that contains a MIME value that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942050 Error message when you visit a website that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 406 - Not Acceptable"
412.0	Precondition failed.	The request is made by using an If-Match request header that contains a value that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942056 Error message when you visit a website that is hosted on Internet Information Services (IIS) 7.0: "HTTP Error 412 - Precondition failed"
500	Internal server error.	This HTTP status code may occur for many server-side reasons. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942031 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 500.0 - Internal Server Error"
500.11	Application is shutting down on the web server.	The request is not processed because the destination application pool is shutting down. Wait for the worker process to finish shutting down, and then try the request again. If this problem persists, the web application may be experiencing problems that prevent the web application from shutting down correctly.
500.12	Application is busy restarting on the web server.	The request is not processed because the destination application pool is restarting. This HTTP status code should disappear when you refresh the page. If this HTTP status code appears again after you refresh the page, the problem may be caused by antivirus software that is scanning the Global.asa file. If this problem persists, the web application may be experiencing problems that prevent the web application from restarting correctly.
500.13	Web server is too busy.	The request is not processed because the server is too busy to accept any new incoming requests. Typically, this HTTP status code means that the number of incoming concurrent requests exceeds the number that the IIS 7.0, IIS 7.5, or IIS 8.0 web application can process. This problem may occur because the performance configuration settings are set too low, the hardware is insufficient, or a bottleneck occurs in the IIS 7.0, IIS 7.5, or IIS 8.0 web application. A common troubleshooting method is to generate a memory dump file of the IIS 7.0, IIS 7.5, or IIS 8.0 processes when the error is occurring and then to debug the memory dump file.
500.15	Direct requests for Global.asax are not allowed.	A direct request for the Global.asa file or for the Global.asax file is made. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942030 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 500.15 - Direct request for global.asa are not allowed"
500.19	Configuration data is invalid.	This HTTP status code occurs because of a problem in the associated Applicationhost.config file or in the associated Web.config file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942055 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 500.19 - Internal Server Error"
500.100	Internal ASP error.	An error occurs during the processing of an Active Server Pages (ASP) page. To obtain more specific information about the error, disable friendly HTTP error messages in the web browser. Additionally, the IIS log may show an ASP error number that corresponds to the error that occurs. For more information about ASP error messages and about the meaning of ASP error messages, click the following article number to view the article in the Microsoft Knowledge Base: 294271ASP error codes
501.0	Not implemented.	The client browser sends an HTTP-Trace verb, and the server is not configured to process the HTTP-Trace verb. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942058 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 501.0 - Not Implemented"
502.1	CGI application timeout.	A CGI application does not return a valid HTTP response in the configured time limit. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942059 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 502.1 - Bad Gateway"
502.2	Bad gateway: Premature Exit	A CGI application returns an HTTP response that is not valid to the server that is running IIS 7.0, IIS 7.5, or IIS 8.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942057 Error message when you visit a website that is hosted on IIS 7.0: "HTTP Error 502.2 - Bad Gateway"
503.0	Service unavailable.	The request is sent to an application pool that is currently stopped or that is currently disabled. To resolve this issue, make sure that the destination application pool is started. The event log may give information about why the application pool is stopped or disabled.
503.2	Concurrent request limit exceeded.	The appConcurrentRequestLimit property is set to a value that is lower than the current number of concurrent requests. IIS 7.0, IIS 7.5, and IIS 8.0 do not allow more concurrent requests than the value of the appConcurrentRequestLimit property.

HTTP status code in IIS 7.0, IIS 7.5, and IIS 8.0

When you try to access content on a server that is running Internet Information Services (IIS) 7.0, 7.5, or 8.0 by using the HTTP protocol, IIS returns a numeric code that indicates the status of the response.

The HTTP status code is recorded in the IIS log. Additionally, the HTTP status code may be displayed in the client browser.

The HTTP status codes

This section describes the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 use.

Note This article does not list every possible HTTP status code as dictated in the HTTP specification. This article includes only the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 can send. For example, a custom Internet Server API (ISAPI) filter or a custom HTTP module can set its own HTTP status code.

1xx - Informational

These HTTP status codes indicate a provisional response. The client computer receives one or more 1xx responses before the client computer receives a regular response.

IIS 7.0, IIS 7.5, and IIS 8.0 use the following informational HTTP status codes:

• 100 - Continue.
• 101 - Switching protocols.

2xx - Success

These HTTP status codes indicate that the server successfully accepted the request.

IIS 7.0, IIS 7.5, and IIS 8.0 use the following success HTTP status codes:

• 200 - OK. The client request has succeeded.
• 201 - Created.
• 202 - Accepted.
• 203 - Nonauthoritative information.
• 204 - No content.
• 205 - Reset content.
• 206 - Partial content.

3xx - Redirection

These HTTP status codes indicate that the client browser must take more action to fulfill the request. For example, the client browser may have to request a different page on the server. Or, the client browser may have to repeat the request by using a proxy server.

IIS 7.0, IIS 7.5, and IIS 8.0 use the following redirection HTTP status codes:

• 301 - Moved permanently.
• 302 - Object moved.
• 304 - Not modified.
• 307 - Temporary redirect.

4xx - Client error

These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information.

IIS 7.0, IIS 7.5, and IIS 8.0 use the following client error HTTP status codes:

• 400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 400 error:
  • 400.1 - Invalid Destination Header.
  • 400.2 - Invalid Depth Header.
  • 400.3 - Invalid If Header.
  • 400.4 - Invalid Overwrite Header.
  • 400.5 - Invalid Translate Header.
  • 400.6 - Invalid Request Body.
  • 400.7 - Invalid Content Length.
  • 400.8 - Invalid Timeout.
  • 400.9 - Invalid Lock Token.
• 401 - Access denied.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define several HTTP status codes that indicate a more specific cause of a 401 error. The following specific HTTP status codes are displayed in the client browser but are not displayed in the IIS log:
  • 401.1 - Logon failed.
  • 401.2 - Logon failed due to server configuration.
  • 401.3 - Unauthorized due to ACL on resource.
  • 401.4 - Authorization failed by filter.
  • 401.5 - Authorization failed by ISAPI/CGI application.
• 403 - Forbidden.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 403 error:
  • 403.1 - Execute access forbidden.
  • 403.2 - Read access forbidden.
  • 403.3 - Write access forbidden.
  • 403.4 - SSL required.
  • 403.5 - SSL 128 required.
  • 403.6 - IP address rejected.
  • 403.7 - Client certificate required.
  • 403.8 - Site access denied.
  • 403.9 - Forbidden: Too many clients are trying to connect to the web server.
  • 403.10 - Forbidden: web server is configured to deny Execute access.
  • 403.11 - Forbidden: Password has been changed.
  • 403.12 - Mapper denied access.
  • 403.13 - Client certificate revoked.
  • 403.14 - Directory listing denied.
  • 403.15 - Forbidden: Client access licenses have exceeded limits on the web server.
  • 403.16 - Client certificate is untrusted or invalid.
  • 403.17 - Client certificate has expired or is not yet valid.
  • 403.18 - Cannot execute requested URL in the current application pool.
  • 403.19 - Cannot execute CGI applications for the client in this application pool.
  • 403.20 - Forbidden: Passport logon failed.
  • 403.21 - Forbidden: Source access denied.
  • 403.22 - Forbidden: Infinite depth is denied.
  • 403.502 - Forbidden: Too many requests from the same client IP; Dynamic IP Restriction limit reached.
• 404 - Not found.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 404 error:
  • 404.0 - Not found.
  • 404.1 - Site Not Found.
  • 404.2 - ISAPI or CGI restriction.
  • 404.3 - MIME type restriction.
  • 404.4 - No handler configured.
  • 404.5 - Denied by request filtering configuration.
  • 404.6 - Verb denied.
  • 404.7 - File extension denied.
  • 404.8 - Hidden namespace.
  • 404.9 - File attribute hidden.
  • 404.10 - Request header too long.
  • 404.11 - Request contains double escape sequence.
  • 404.12 - Request contains high-bit characters.
  • 404.13 - Content length too large.
  • 404.14 - Request URL too long.
  • 404.15 - Query string too long.
  • 404.16 - DAV request sent to the static file handler.
  • 404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
  • 404.18 - Querystring sequence denied.
  • 404.19 - Denied by filtering rule.
  • 404.20 - Too Many URL Segments
• 405 - Method Not Allowed.
• 406 - Client browser does not accept the MIME type of the requested page.
• 408 - Request timed out.
• 412 - Precondition failed.

5xx - Server error

These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

IIS 7.0, IIS 7.5, and IIS 8.0 use the following server error HTTP status codes:

• 500 - Internal server error.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 500 error:
  • 500.0 - Module or ISAPI error occurred.
  • 500.11 - Application is shutting down on the web server.
  • 500.12 - Application is busy restarting on the web server.
  • 500.13 - Web server is too busy.
  • 500.15 - Direct requests for Global.asax are not allowed.
  • 500.19 - Configuration data is invalid.
  • 500.21 - Module not recognized.
  • 500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
  • 500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
  • 500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
  • 500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
    Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
  • 500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
    Note Here is where the global rules configuration is read.
  • 500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
  • 500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
  • 500.100 - Internal ASP error.
• 501 - Header values specify a configuration that is not implemented.
• 502 - Web server received an invalid response while acting as a gateway or proxy.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 502 error:
  • 502.1 - CGI application timeout.
  • 502.2 - Bad gateway: Premature Exit.
  • 502.3 - Bad Gateway: Forwarder Connection Error (ARR).
  • 502.4 - Bad Gateway: No Server (ARR).
• 503 - Service unavailable.
  
  IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 503 error:
  • 503.0 - Application pool unavailable.
  • 503.2 - Concurrent request limit exceeded.
  • 503.3 - ASP.NET queue full

View Currently Executing Requests in a Worker Process

When you notice that a worker process is using many resources on your Web server, or requests are taking a long time to process, you can view a list of current requests that are processing in a specific worker process. 

This information can help you determine where a problem occurs in a specific area of a site or application. 

You can view which requests are currently processing in the worker process, and then use that information to investigate why a certain request takes so much time to process.

The currently executing request information in IIS Manager returns the following information about requests in a worker process:

• Site ID. The site identifier (ID) for the specific request.
• Url. The requested Uniform Resource Locator (URL).
• Verb. The Hypertext Transfer Protocol (HTTP) verb used in the request.
• Client IP. The Internet Protocol (IP) address of the client who made the request.
• State. The current pipeline module state that the request is in.
• Module Name. The current module that the request is in.
• Time Elapsed. The period of time the request has been in process.

Via the GUI

Open IIS Manager. 

In the Connections pane, select the server node in the tree.

In Features View, double-click Worker Processes.

Select a worker process from the grid.

Click View Current Requests in the Actions pane.

View the list of requests in the grid.

Via the Command Line

cd Windows\System32\inetsrv

appcmd list requests - show all current requests 

appcmd list requests /elapsed:4000 - show all current requests taking longer than 4 seconds to execute

Task Scheduler Error Codes

Run result error code list.

Common Exit codes :

0x0 - ok
0x1 - incorrect function
0x2 - access denied
0x41301 - task is currently running

Other codes :

0x41300 - The task is ready to run at its next scheduled time.
0x41302 - The task will not run at the scheduled times because it has been disabled.
0x41303 - The task has not yet run.
0x41304 - There are no more runs scheduled for this task.
0x41305 - One or more of the properties that are needed to run this task on a schedule have not been set.
0x41306: Task is terminated.
0x8004130F: Credentials became corrupted (*)
0x8004131F: An instance of this task is already running.
0x800704DD: The service is not available (is 'Run only when an user is logged on' checked?)
0xC000013A: The application terminated as a result of a CTRL+C.
0xC06D007E: Unknown software exception.

Common fixes

0x2 - access denied

Problem
You are using Task Scheduler in Windows Server 2008 R2, Windows Server 2012, Windows Vista, Windows 7, or later to execute a .bat or .cmd file that contains statements that require administrator privileges. For example, you may be attempting to stop and/or start a Windows service with net.exe. In Task Scheduler, you have assigned an account that has administrative rights to the task. You have selected "Run whether user is logged on or not" and have entered and stored the password. You have confirmed that you can execute the .bat or .cmd file in a command window. When you attempt to execute the file via Task Scheduler, however, it does not work. While Task Scheduler does fire the task, it fails with a "Last Run Result" of "(0x2)", which means "access denied".

Cause
The Task Scheduler in Windows Server 2008 R2 and later and Windows Vista and later executes tasks under a "least privileges" security context by default.

Solution
Open the properties of the task and check Run with highest privileges. Press OK, then enter the password for the administrative account when prompted. This will override the default "least privileges" behavior and will allow the task to run with administrative privileges.

How to enable Schannel event logging in IIS

Enable logging

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Start Registry Editor. To do this, click Start, click Run, type regedt32, and then click OK.

Locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL

On the Edit menu, click Add Value, and then add the following registry value:
Value Name: EventLogging
Data Type: REG_DWORD

Note After you add this property, you must give it a value.
See the table in the "Logging options" section to obtain the appropriate value for the kind of events that you want to log.

Exit Registry Editor and restart the computer.
Logging does not take effect until after you restart the computer

Logging options

The default value for Schannel event logging is 0x0000 which means that no Schannel events are logged.
Additionally, you can log multiple events by specifying the hexadecimal value that equates to the logging options that you want. For example, to log error messages (0x0001) and warnings (0x0002), set the value to 0x0003.
Value Description
0x0000 Do not log
0x0001 Log error messages
0x0002 Log warnings
0x0004 Log informational and success events

Applies to

Microsoft Internet Information Services 8.0
Microsoft Internet Information Services 7.5
Microsoft Internet Information Services 7.0
Microsoft Internet Information Services 6.0
Microsoft Internet Information Services 5.1
Microsoft Internet Information Services 5.0
Microsoft Internet Information Server 4.0

Setting Environment Variables in Windows

Environment variables hold values related to the current environment, like the Operating System or user sessions.

Setting Environment variables via the GUI

1. Open Control Panel » System » Advanced » Environment Variables.
2. Type control sysdm.cpl,,3 in the Run dialog (+R) and click Environment Variables.
   For editing user variables you can also type

   %windir%\System32\rundll32.exe sysdm.cpl,EditEnvironmentVariables
   

   in the Run dialog.
3. Right-click (My) Computer and click on Properties, or simply press +Break.
   • In XP click on Advanced » Environment Variables.
   • In Vista+ click on Advanced system settings » Environment Variables.
4. There are many other ways of reaching the same place, such as by typing "environment variables" in the Start Menu/Screen search box and so on.

Environment variables in Windows are separated into user and machine/system specific values. You can view and edit their values there. Their current values upon launch are made available to all programs.

Setting Environment variables via the Command Line

Format

Environment Variables in Windows are denoted with percent signs (%) surrounding the name:

%name%

echo

To display an environment variable's value in cmd.exe, type echo %name%.

C:\>echo %USERPROFILE%
C:\Users\Daniel

set

To create/set a variable, use set varname=value:

C:\>set FunnyCatPictures=C:\Users\Daniel\Pictures\Funny Cat Pictures

C:\>set FunnyCatPicturesTwo=%USERPROFILE%\Pictures\Funny Cat Pictures 2

To append/add a variable, use set varname=value;%varname%:

C:\>set Penguins=C:\Linux

C:\>set Penguins=C:\Windows;%Penguins%

C:\>echo %Penguins%
C:\Windows;C:\Linux

Environment variables set in this way are available for (the rest of) the duration of the Command Prompt process in which they are set, and are available to processes that are started after the variables were set.

setx

To create/set a variable permanently, use setx varname "value":

C:\>setx FunnyCatPictures "C:\Users\Daniel\Pictures\Funny Cat Pictures"

[Restart CMD]

C:\>echo %FunnyCatPictures%
C:\Users\Daniel\Pictures\Funny Cat Pictures

Unlike set, there is no equals sign and the value should be enclosed in quotes if it contains any spaces. Note that variables may expand to a string with spaces (e.g., %PATH% becomes C:\Program Files), so it is best to include quotes around values that contain any variables.

List of Windows Environment Variables

Here is a list of default environment variables, which are built into Windows. Some examples are:%WINDIR%, %SystemRoot%, %USERPROFILE%, and %APPDATA%. Like most names in Windows, these are case-insensitive.