Running IIS 6 on Windows Server 2003 Web.
We have some 3rd party components that leak memory so we've scheduled periodic jobs to restart IIS. The jobs are simply calling iisrestart /reset
which seems to do the job... but it sure generates a big ol' pile of Event log events -- including 3 errors and a warning. Perhaps we're doing it wrong?
Is there a "cleaner" way to recycle the IIS process(es) without Windows getting all upset with us? As our monitoring improves, error events on the prod web servers cause unnecessary distractions.
For those curious, here's what the events "cycle" looks like (I've abridged the description text a bit for brevity). These all happen in a span of 1 - 2 seconds:
Warning - WinRM - ID 10149 - WinRM service is not listening for WS-Management Requests
Info - IISCTLS - ID 6 - IIS Reset encountered an error while stopping services
Info - Service Control Manager - ID 7035 - SMTP service was successfully sent a stop control
Info - Service Control Manager - ID 7035 - Windows Remote Management Service successfully sent a stop control
Info - Service Control Manager - ID 7036 - Windows Remote Management entered stopped state
Error - Service Control Manager - ID 7034 - World Wide Web publishing service terminated unexpectedly. It has done this x times
Error - Service Control Manager - ID 7034 - IIS Admin Service terminated unexpectedly
Error - Service Control Manager - ID 7034 - SMTP service terminated unexpectedly
Info - IISCTLS -ID 4 - IIS kill command received from user.
Info - IISCTLS - ID 2 - IIS stop command received from user.
Info - Service Control Manager - ID 7035 - IIS Admin Service service was successfully sent a start control
Info - Service Control Manager - ID 7035 - World Wide Web Publishing Service service was successfully sent a start control
Info - Service Control Manager - ID 7035 - SMTP service was successfully sent a start control
Info - Service Control Manager - ID 7035 - Windows Remote Management service was successfully sent a start control