Frequent 101,102,104, 111,112,113,114, 116,117,118 events appear in the application logs

This article applies to the following products:
     Messageware OWA Suite 2000 and 2003





Frequent 101,102,104, 111,112,113,114, 116,117,118  events appear in the application logs.


The DefaultApplicationPool may be set to shutdown after a specified period to time after inactivity.

In Windows 2003, the Messageware Core Service filter loads into all application pools and each time an application pool starts or stops the event will be logged. This will result in a "core services stopped" message, and on the next request will load the DefaultApplicationPool, resulting in a "core services started" message.

The idle timeout is partly a safety factor to mitigate the risk of having an application that leaks memory. Having the DefaultApplicationPool shut down every 20 minutes when idle is not really necessary unless there is a problem application operating in that pool. We would recommend to either set it to not shutdown, or to have it shut down periodically at a much longer interval.


To avoid these messages please follow the steps below.

1.       On the server Messageware is installed on, open the IIS Manager and navigate to \Application Pools

2.       View the properties on the DefaultAppPool and move to the Performance tab

3.       In the “Idle Timeout” section, either unselect the “Shutdown worker processes after being idle for (time in minutes):” option or increase the time between shutting down

After applying these settings please monitor the server to confirm that this change has reduced the number of messages created in the event log.


Please refer to the following two Microsoft articles for more information on this issue.

Configuring Idle Time-out for Worker Processes (IIS 6.0)

Configuring Worker Processes for Idle Timeout (IIS 6.0)


This article applies to the following products:
     Messageware OWA Suite 2000 and 2003