Windows messenger service hung while stopping

But sometimes this is just not possible, as nothing seems to be related. In the event viewer, check the system logs and check for events by name Service Control manager event ID , mostly. That will give you the ID what happened to which service. This event will only be generating if any service's status is changing, like from start to stop or vice versa.

This means spooler service has crashed. Specific to this error, there could be many reasons. Any 3rd part printer driver,Print provider or print monitor can cause this issue. To find that out we need to take the ADPlus dump during the time service is crashing. Here are the links to configure ADPlus Dump on a machine. By analysing the ADPlus, we would get the tag name which is causing service to crash.

Based on that we can serch for the update of that. So, there is no specific troubleshooting steps. Generally, you have to investigate more on logged events to have more details. Also, your system should up-to-date since many services may fail if your system is not up-to-date. I am not familiar with it but I will get. This is now my homework. It does not stop nor can I start it. I cant find anything in the Event Logs to indicate why. Sometimes when I restart my PC it will kick in again and start working.

Other times it doesnt. And it will also allow any user to send a popup message to any other user, if they dont already do this then its only a matter of time before they figure out how.

Also when you start to upgrade to Windows 7 or even vista , you wont be able to use this bit of software as the Messenger server has quite rightly , been removed. My advice would be to get the hell away from any piece of software that makes use of or relies on a feature that has been deemed a security risk at worst, at best an annoyance and has been removed from newer versions of the OS after being disabled by one of their own updates! Have you tried manually stopping the messenger service from services.

The messenger service got disabled by default in one of the XP service packs I dont remember which exactly , and in newer versions of Windows it doesnt even exist any more. Isn't there a way to force XP to realize that the service has finally finished stopping? Is there anyone else that has experienced this problem and knows how to resolve it without reinstalling XP? Thanks for your suggestions. SC Communicates with the Service Controller and installed services.

You can use SC. You could try reregistering the msgsvc. Regsvr32 msgsvc. If you try to send commands to the service using the SC tool, it just returns "The Service can not accept control messages at this time". If you try to start the service, it states that an instance is already running. Any hope that System Restore might fix it if you go back a couple of points?

Try running ChkDsk to check your drive for errors. Have you been able to "disable" the service via the service properties utilizing the service or computer manager mmc?

Once that is done, reboot. That should get you back to "normal". Wasn't able to send any commands to the service while stuck in the stopping mode. What finally cleared the problem was a shut-down. Reboots didn't resolve it, but powering it down for 30 seconds and powering it back up cleared it right up. Thanks for your help. Red Flag This Post Please let us know here why this post is inappropriate.