Quantcast
Channel: Comments on: Please wait for the System Event Notification Service…
Viewing all 38 articles
Browse latest View live
↧

By: Jeff Fogel

November 10, 2010, 2:25 pm
$
0
0

The system event notifacation 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 requrie a reboot like all the millions of thread out there about this issue, because the issue isn’t resolved by a reboot.

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

jefffogel1974@hotmail.com
Thanks
Jeff

↧
Search

By: graham ross

September 7, 2011, 8:11 pm
$
0
0

Hi Mike,
We’ve had the same issue and have found a different way to resolve the issue which doesn’t require a server reboot.
Start Remote Desktop Services Manager
Identify the user ID in the Users tab
In the Processes tab sort by ID
Go down to the user ID and end the winlogon.exe process
the user session will be logged off
A server reboot will probably be beneficial at the end of the day
Regards
Graham

↧
↧

By: Shawn Mortensen

October 19, 2012, 12:12 pm
$
0
0

Graham, you are my hero, nothing work, but your suggestion did :) Thank you!!

↧

By: Himanshu

January 13, 2013, 6:06 pm
$
0
0

Thanks Graham…your solution is still working in 2013. Cheers

↧

By: Abbi Gail Bianca Durias

February 12, 2013, 8:02 pm
$
0
0

mine is different. after i restart my laptop, it neve opens back. i can’t follow your advices since none of the programs opened.. it’s just the message that keeps on saying “Please wait for the System Event Notification Service…” and I spent the whole night waiting for it. up until now it is loading and I can’t do anything.. :(

↧
↧

By: random701

March 10, 2013, 2:08 pm
$
0
0

Here is how I got around it. From a command prompt on my PC or another computer on the domain I ran this to find out the PID of the svchost.exe associated with SENS

sc \\servername queryex SENS

Then I kill that process with this command

taskkill /S servername /PID xxxx /F

where xxxx is the PID from the first command.

Now I can connect to the server with RDP and I didn’t have to restart the server.

Obviously this is not a fix for the actual problem, but it lets you log on to your server.

↧

By: Abo Ebraheem

June 5, 2013, 12:00 am
$
0
0

Thank nyou very very very much random701 .
I had the same problem and you helped me

↧

By: Gusac

June 13, 2013, 12:46 pm
$
0
0

Problem with random701′s solution is that the sc command will give the PID of svchost.exe process which host several other services too. they are:

Appinfo, AppMgmt, BDESVC, BITS,
CertPropSvc, EapHost, gpsvc, IKEEXT,
iphlpsvc, LanmanServer, MMCSS, ProfSvc
RasMan, Schedule, seclogon, SENS,
SessionEnv, ShellHWDetection, Themes,
Winmgmt, wuauserv

So, question is, if you are willing to kill so many services, why not reboot it manuaally and GRACEFULLY using shutdown command?

↧
Search

By: awanxxxxxx

August 4, 2013, 10:27 pm
$
0
0

same with me…i don”t know what should i do to repair my note book

↧
↧

By: Jeff Fogel

November 10, 2010, 2:25 pm
$
0
0

The system event notifacation 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 requrie a reboot like all the millions of thread out there about this issue, because the issue isn’t resolved by a reboot.

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

jefffogel1974@hotmail.com
Thanks
Jeff

↧

By: graham ross

September 7, 2011, 8:11 pm
$
0
0

Hi Mike,
We’ve had the same issue and have found a different way to resolve the issue which doesn’t require a server reboot.
Start Remote Desktop Services Manager
Identify the user ID in the Users tab
In the Processes tab sort by ID
Go down to the user ID and end the winlogon.exe process
the user session will be logged off
A server reboot will probably be beneficial at the end of the day
Regards
Graham

↧

By: Shawn Mortensen

October 19, 2012, 12:12 pm
$
0
0

Graham, you are my hero, nothing work, but your suggestion did :) Thank you!!

↧

By: Himanshu

January 13, 2013, 6:06 pm
$
0
0

Thanks Graham…your solution is still working in 2013. Cheers

↧
↧

By: Abbi Gail Bianca Durias

February 12, 2013, 8:02 pm
$
0
0

mine is different. after i restart my laptop, it neve opens back. i can’t follow your advices since none of the programs opened.. it’s just the message that keeps on saying “Please wait for the System Event Notification Service…” and I spent the whole night waiting for it. up until now it is loading and I can’t do anything.. :(

↧

By: random701

March 10, 2013, 2:08 pm
$
0
0

Here is how I got around it. From a command prompt on my PC or another computer on the domain I ran this to find out the PID of the svchost.exe associated with SENS

sc \servername queryex SENS

Then I kill that process with this command

taskkill /S servername /PID xxxx /F

where xxxx is the PID from the first command.

Now I can connect to the server with RDP and I didn’t have to restart the server.

Obviously this is not a fix for the actual problem, but it lets you log on to your server.

↧
Search

By: Abo Ebraheem

June 5, 2013, 12:00 am
$
0
0

Thank nyou very very very much random701 .
I had the same problem and you helped me

↧

By: Gusac

June 13, 2013, 12:46 pm
$
0
0

Problem with random701′s solution is that the sc command will give the PID of svchost.exe process which host several other services too. they are:

Appinfo, AppMgmt, BDESVC, BITS,
CertPropSvc, EapHost, gpsvc, IKEEXT,
iphlpsvc, LanmanServer, MMCSS, ProfSvc
RasMan, Schedule, seclogon, SENS,
SessionEnv, ShellHWDetection, Themes,
Winmgmt, wuauserv

So, question is, if you are willing to kill so many services, why not reboot it manuaally and GRACEFULLY using shutdown command?

↧
↧

By: awanxxxxxx

August 4, 2013, 10:27 pm
$
0
0

same with me…i don”t know what should i do to repair my note book

↧

By: Al

April 24, 2014, 7:50 pm
$
0
0

Did anyone ever truly resolve this issue? I am having it on Server 2012 Standard.

↧

By: Gwen

June 16, 2014, 7:41 am
$
0
0

I’m seeing it on a 2012R2 installation now.

↧
Viewing all 38 articles
Browse latest View live
Search