Search This Blog

Thursday, August 11, 2011

Waiting for System Event Notification Service………..

Found this article and its response while experiencing an issue while logging out of a administration RDP session to an win2k8 R2.

I had tried stopping the SENS service which did hung, as described. But I think there is a timeout and the session did finally sort itself out.

I include the content for this article response more for my sanity in the future…

The system event notification issue isn’t an issue with Windows Live messenger… Read below on what I have found.

The fix for this issue is very simple.

First we will examine what causes the issue to begin with. The cause is the COM+ Event Service detects a bad code and hangs. When you go to services.msc you won’t see the service hang but believe me it is. If you try to stop the server you will then see it hang and you won’t be able to get it back started. You can’t kill the process via taskmgr because its a svchost.exe service so you’ll never know which one to kill unless you download a little program call Processor Explorer from Sysinternals.

1. Open Eventviewer and select Application and filter the list so all you see are Error logs

2. Scroll through al Error logs till you come to one EventSystem (EventID=4621) (The COM+ Event System could not remove the EventSystem.EventSubscription object {C986B80D-E6CE-4FB0-9A44-F19BF27C165A}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 800706be.)

3. Ok now open Process Explorer and sort by process name

4. Find the list of svhost.exe and start right clicking each and selecting Properties.

5. After hitting Properties on each services make sure you are selecting the Services tab and look for the svchost.exe process that has the EventSystem service which its display name is COM+ Event System

6. Now close the box and right click on the svchost.exe process and select Restart

7. Instantly once the service shuts down and restarts you will notice in your taskmgr that the users that were hung are now gone and they can now login and logout as they please

8. There are some services that won’t start back up after restarting this service so make sure you go back into services.msc and sort services by automatic and start up the ones that aren’t running.

This should resolve your issue until you get another SystemEvent error in Event View, but then just follow these steps and you are fine. The greatest thing about this fix is it doesn’t require a reboot like all the millions of thread out there about this issue, because the issue isn’t resolved by a reboot.

I am definitely interested in hearing if this has worked for you so please let me know.


There is also a large thread on the Microsoft forums about this, and it may be worth going through this if you don’t have any joy here.


No comments:

Post a Comment