We have an email exchange and a couple of apple mac's which we use pop3 for. Pretty much every time the exchange is rebooted it will start up with pop3 not working, even though it says it has started. I stop the service, then kill it, then start it again. This seems to do the trick - If I recall this info is from another site (thanks to that smart person!):
If you ever have trouble with a service being stuck in a starting or stopping state, you can run a couple of simple commands to kill the service.
1. Query the process
To kill the service you have to know its PID or Process ID. To find this just type the following in at a command prompt: (i.e. pop3svc)
sc queryex servicename
Replace servicename with the services registry name. For example: Print Spooler is spooler.
2. Identify the PID
After running the query you will by presented with a list of details. You will want to locate the PID.
3. Run the Taskkill command
Now that you have the PID, you can run the following command to kill the hung process:
taskkill /f /pid [PID]
This will force kill the hung service.
0 comments:
Post a Comment