Windows 7 and error "Could not connect to the System Event Notification Service"  

Page 1 / 2 Next
  RSS

Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
13/01/2013 9:34 pm  

At the moment I work at a company with about 8000 to 9000 workstations. A couple of users called in an issue that they had trouble logging in into Windows 7. Once in a while they got the following error message during the logon process.

"Windows could not connect to the Event Notification Service service. Please consult your System Administrator"

 

Only one or more reboot(s) seemed to bypass the error. This was not an acceptable situation and I was asked to look into this problem.

Environment description:

  • Windows 2008 R2
  • Window 7
  • SCCM 2007 R2
  • RES Workspace Manager 2011
  • App-V 4.6 SP1

Underneath a screenshot of the error message:

 

After checking the event viewer I noticed that not only the "System Event Notification Service" was failing but also several other services failed to start. Underneath a list of services that are involved.

  • Certificate Propagation
  • Extensible Authentication Protocol
  • Group Policy Client
  • IKE and AuthIP IPsec Keying Modules
  • IP Helper
  • Server
  • Multimedia Class Scheduler
  • User Profile Service
  • Task Scheduler
  • System Event Notification Service
  • Shell Hardware Detection
  • Themes
  • Windows Management Instrumentation

With the knowledge that not only the "System Event Notification Service" service was failing to start I searched the web for a solution. I found several articles but they didn't solve my problem. Than I stumbled onto the following Hotfix:

http://support.microsoft.com/kb/2590550/en-us?fr=1

This hotfix solved my problem. But in the meanwhile several users were still experiencing this problem. Due a backlog on the change management side, it would take a while to get this hotfix in production. I decided to look for a workaround for the customers who were experiencing this problem more frequently.  It seemed, like described in the article, that the "Microsoft Virtualization client" had something to do with it. I quote:

"Cause: This issue occurs when a new drive is added to the system while background services are still starting.  The most common example of this is with Microsoft Application Virtualization Client.  When this service starts, it creates a virtual drive.  When this drive is created during system startup, the Server service may crash the shared service host process.  This process contains other services which are important for completing user logins.  When these services fail at startup, a blue or black background image is displayed instead of the user’s desktop."

When trying to find a workaround I found that delaying the startup of the "Microsoft Virtualization Client" service seemed to work. This should give the other services time to start-up. It's a quick and dirty method but it did solve the problem for the users who were experiencing this problem on a frequent base. We decided to use it as a temporally workaround until the hotfix was applied.

The hotfix is also applicable for Windows Server 2008 R2 in case you are experiencing the same issues on a server.

Greetings,


ReplyQuote
Goat
 Goat
(@Goat)
Guest
Joined: 5 years  ago
Posts: 1
06/07/2013 1:18 am  

[worship worship worship]

Thank you for solving a problem in one easy post I couldn't manage to get anyone from Microsoft to even admit existed for TWO YEARS.


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
06/07/2013 7:42 am  

Hi Goat,

Thank you, always nice to hear that! Hopefully it will help more people with the same problem.


ReplyQuote
Kenneth Nyanzi
 Kenneth Nyanzi
(@Kenneth Nyanzi)
Guest
Joined: 5 years  ago
Posts: 1
21/07/2013 8:04 pm  

Thanks, This worked in just a snap 😉
Marco..this surely will help a lot of people 😉 You wont believe how much stressed I was before the resolution


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
21/07/2013 8:52 pm  

Dear Kenneth,

Glad to be of help, it's always nice to get a feedback from people like this 😉

Greets,

Marco


ReplyQuote
Suresh
 Suresh
(@Suresh)
Guest
Joined: 5 years  ago
Posts: 1
26/08/2013 2:04 pm  

Thanks Marco. Your post really helped. I managed to apply the hot fix and resolve the issue. It has been bugging my desktop since the past two weeks! Microsoft support couldn't help.

One of the many benefits of the Internet is having folks like you around!


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
26/08/2013 2:21 pm  

Hi Suresh,

Thank you 🙂 and your welcome. Glad to be of help.

It's strange that Microsoft support couldn't help you out cause after all it's Microsoft's own hotfix which is fixing the issue.


ReplyQuote
flipside
 flipside
(@flipside)
Guest
Joined: 5 years  ago
Posts: 1
19/09/2013 9:16 am  

I had this error and found that the COM+ System Application service was listed as a service that depended (that is, listed in the lower box under dependencies) on the System Event Notification Service, and the COM+ service was stopped. After starting this service and setting to Automatic startup the issue was fixed.

I don't know how this service was configured before the error nor why it should suddenly be a problem but discovered the only program to update just prior to error was Rapport by Trusteer, something I use for online banking. Might just be coincidence but I have had issues with this software before.


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
19/09/2013 11:29 am  

Hi Flipside,

I don't know the program "Rapport by Trusteer" but it is possible that multiple applications could cause this issue. Haven't looked at the COM+ service tho but it could be of some help to other people who come here.

Thanks for sharing your solution in this case 🙂


ReplyQuote
Peter
 Peter
(@Peter)
Guest
Joined: 5 years  ago
Posts: 1
24/09/2013 7:26 pm  

Hi Marco, great post!

I have the same issue with XenServer 5.6 with Citrix Provisioning Services 5.6.1, i donwload the hotfix but not work for me, any suggestion?

Regards.


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
24/09/2013 9:06 pm  

Hi Peter,

First of all thanks :), second I'm afraid I'm not that familiar with Xenserver 5.6 and I think it needs some more troubleshooting in your case.

Here are a few things I would check for:

- Scan the event viewer log for errors on which services did not start correctly and/or check services list
- Does rebooting (maybe several times) solve the issue?
- On which OS are you running Xenserver?
- Are there applications that use/create a (virtual) drive at start up, like App-V does? If so and if it's a service than try to delay that service, like mentioned in my workaround.

Hopefully u can find something with this.


ReplyQuote
Ali hashmi
 Ali hashmi
(@Ali hashmi)
Guest
Joined: 5 years  ago
Posts: 1
26/11/2013 8:02 am  

hope this will help you.....

1. go to run and find (services.msc)
2. find: ( system event notification manager)
3. then ( disable it)
4. reboot your computer
5.open ( services.msc)
6.(system event notification manager)
7.( enable it : automatic )
8. reboot your computer
hope pc will work fine

thnx..


ReplyQuote
Peter vdB
 Peter vdB
(@Peter vdB)
Guest
Joined: 5 years  ago
Posts: 2
29/11/2013 11:58 pm  

Hi,

on my Windows 7 32-bit PC I have the same problem with SENS and a freezing window.
Following the link of the Hotfix I end up with a X86 and x64 platform.

Is it safe - or does it work - on a 32-bit platform?

Brgds

Peter


ReplyQuote
Marco Nuijens
(@manu)
Member Admin
Joined: 2 years  ago
Posts: 50
30/11/2013 8:49 am  

Hi peter,

X86 = 32-bit so it's save to use this hotfix.

Kind regards,

Marco Nuijens


ReplyQuote
Peter vdB
 Peter vdB
(@Peter vdB)
Guest
Joined: 5 years  ago
Posts: 2
03/12/2013 1:30 pm  

Dear Marco,

I downloaded the hotfix and started the hotfix. Thanks for the link.
Unfortunalely the Guest user is still not able to be connected to SENS - this, although whilethis service is now deactived...
If you might see a solution? I already disactiveted the user and reactivated it - something that worked in the past - but his time something got stuck bady...

Check settings in my company and changed setting of SENS to manual. And yes, the computer gets slower...

Brgds

Peter


ReplyQuote
Page 1 / 2 Next
Share:
  
Working

Please Login or Register