Event ID - 5196

Event Id5196
SourceMicrosoft-Windows-WAS
DescriptionA 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.
Event Information According to Microsoft :

Cause :

This event is logged when request to create a new worker process has arrived.

Resolution :

Configure the dynamic idle threshold

If Web server performance is impacted, you may want to configure the dynamicIdleThreshold attribute of the system.applicationHost/webLimits section in the ApplicationHost.config file.

Note : For more information about the values to use for the dynamicIdleThreshold attribute, see IIS 7.0: webLimits Element (IIS Settings Schema).

To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority.

To specify a value for the dynamicIdleThreshold attribute:
  1. Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator .
  2. Type cd %Windir%\system32\inetsrv\ .
  3. Type appcmd set config /section:webLimits /dynamicIdleThreshold :number where number is a value from 0 to 10000.
  4. To verify that the value has changed, type appcmd list config /section:webLimits /config:* The changed value will be displayed.
Verify :

Because the dynamic idle feature works in real time, its threshold value is transient. However, you can verify whether dynamic idling has been enabled, or specify a value for the dynamic idle threshold if you want.

To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority.

To verify whether dynamic idling is enabled:
  1. Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator .
  2. Type cd %Windir%\system32\inetsrv\ .
  3. Type appcmd list config /section:webLimits /config:*
The output will resemble the following:

webLimits maxGlobalBandwidth="4294967295" connectionTimeout="00:02:00" demandStartThreshold="2147483647" dynamicIdleThreshold="0" headerWaitTimeout="00:00:00"
minBytesPerSecond="240" /&gr;

If the value of dynamicIdleThreshold attribute is non-zero, the feature is enabled. In the example here, it is disabled; this is the default setting.
Reference LinksEvent ID 5196 from Microsoft-Windows-WAS

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.