Occasionally when a server instance reboots, WebConnect starts more than the specified number of instances and keeps 'orphaned' instances alive rather than shutting them down. I'm not sure if it's just the added machine load during startup, or perhaps I have an .ini or .web setting set too low. Maybe the PollTime ???

I do monitor them and I can remote in to kill the extra instances when alerted but I'd rather not have to worry about it after a Windows update is applied to the server.

Suggestions?

What version of WWC are you using? Rick made a lot of excellent changes to instance management in 8.x and this sounds like a 7.x or earlier thing.

This customer is using Web Connection Server Version 25.2.4, according to the admin page.

Tha's not any version I'm aware of but Rick will know better. For example, here's my version info from my admin page:

Yes - I see. That must be the 'DLL Version'. In my customer's case, that is: 6.21 (.NET Handler)

As Richard has stated, there have been major improvements in v8 that better handle orphaned instances. If that is a concern the upgrade is definitely going to help...

Upgrade from 6.x should be pretty painless, unless you're using Web Control Framework in which case a few startup changes are required.

+++ Rick ---

Perfect - thanks. I'll pass that on.