Fix eGain v11 services and instances stuck in 'Starting' state

eGain v11 will sometimes get stuck its service instances stuck in a 'starting' state where you can't manually start or stop them, and they remain in this state even after reboot (because the interfaces is just reading a database field, not the actual state of the service). Here's an SQL statement to set all instances in the 'starting' state to the 'stopped' state:

UPDATE [eGMasterDB].[dbo].[EGPL_DSM_INSTANCE] SET STATE = 4 WHERE STATE = 6

If you have a system service (as opposed to an instance of that service) that is stuck, use this instead:

UPDATE [eGMasterDB].[dbo].[EGPL_DSM_PROCESS] SET STATE = 4 WHERE STATE = 6

Obviously, if your eGain Master database has a different name, you'll need to change that. You can also limit this down to a single service or instance by changing the WHERE STATE = 6 to narrow down the search using the instance or process name/id. Just have a look at those tables to see what you need to use. For reference, here are the states:
0 = Undefined
1 = Error
2 = Waiting
3 = Running
4 = Stopped
5 = Undefined
6 = Starting