I have come across this scenario quite a few times. When you try to start a service some how windows screws up and comes back with an error saying that the service could not be started and the reason for the failure (as expected) is useless. The worst part is that after failure the service still stays in the 'starting' mode for quite some time and there is nothing that you can do to stop it, i mean there is no option to force stop the service.
I am still trying to figure out some way to get the service to recover faster but can't seem to find any help, google is not helping me either. So the best solution for the moment is to wait till the service recovers on its own and then restart it or you reboot the OS itself (isn't that the universal fix for any problem on windows. ;))
I am still trying to figure out some way to get the service to recover faster but can't seem to find any help, google is not helping me either. So the best solution for the moment is to wait till the service recovers on its own and then restart it or you reboot the OS itself (isn't that the universal fix for any problem on windows. ;))
Powered by ScribeFire.
