The AspRequestQueueMax property specifies the maximum number of concurrent ASP requests that are permitted into the queue. Any client browser that attempts to request ASP files when the queue is full is given an HTTP 500 Server Too Busy error.
Setting this property at the IIsWebService level applies to all in-process and pooled out-of-process application keys, at all levels. Metabase settings at the IIsWebServer level or lower are ignored for in-process and pooled out-of-process applications. However, settings at the IIsWebServer level or lower are used if that key is an isolated out-of-process application.
This property is a process-level property.
You can configure this property at the following locations in the IIS metabase.
Though the metabase schema allows you to set the AspRequestQueueMax metabase property at the IIsWebServer, IIsWebDirectory, and IIsWebVirtualDirectory level, IIS only honors the property when set globally at the IIsWebService level
IIS Admin Object Type
Client: Requires Windows XP Professional, Windows 2000 Professional, or Windows NT Workstation 4.0.
Server: Requires Windows Server 2003, Windows 2000 Server, or Windows NT Server 4.0.