Sign in
 

none
Could not connect to System Event Notification Service RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I get the error: Windows could not connect to the System Event Notification Service service.

    Regular users are unable to log on to the machine but Administrators are. The Event Viewer does not have any useful information. I performed a system restore to a previously working day but the error came back eventually. I have ran the command netsh winsock reset many times to no avail. When I log in to the machine as Admin I can see that the service is started and it is set to Automatic yet the error persists. This has occurred on 2 Dell machines of different models. I had to completely reinstall the first one to get the user back working but this is not really a solution.

    Thanks

    Monday, July 8, 2013 2:54 PM
    |

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote
    I reinstalled Symantec Endpoint Protection from the computer and it now appears to be working. But I am skeptical and intend to keep a close eye. If anyone has any experience with this feel free to still chime in.
    • Marked as answer by Ewido Friday, July 19, 2013 10:25 PM
    Monday, July 8, 2013 4:03 PM
    |

All replies

  • Question
    Sign in to vote
    3
    Sign in to vote
    I reinstalled Symantec Endpoint Protection from the computer and it now appears to be working. But I am skeptical and intend to keep a close eye. If anyone has any experience with this feel free to still chime in.
    • Marked as answer by Ewido Friday, July 19, 2013 10:25 PM
    Monday, July 8, 2013 4:03 PM
    |
  • Question
    Sign in to vote
    10
    Sign in to vote

    Hi Ewido,

    Here are some suggestions to solve this issue:

    Method 1: Perform a clean boot. A clean boot helps to verify if any third party application service or startup item is causing this issue. For your information, please review this KB article to put the computer in clean boot:

    How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista

    Note: Make sure you put the computer back to Normal Startup once you have done with the troubleshooting.

    Method 2: In some cases, the issue is caused by faulty Font Cache files. Please review the following steps to solve this issue:

    1. Click Start, click All Programs, click Administrative Tools and then double-click Services.                                                                                OR: Click Start, type services.msc in the Search box, and then press Enter.
    2. In the right pane of the Services snap-in, locate the Windows Font Cache Service.
    3. Right-click the Windows Font Cache Service, and then select Stop in the context menu.
    4. Go to this location C:\Windows\ServiceProfiles\LocalService\AppData\Local                                                                                                    Note: please ensure your computer can display hidden files. For your information, please review this article show hidden files.
    5. Rename the file FontCache-System.dat to FontCache-System.old.
    6. Restart.

    Method 3: Please review this KB article The desktop does not load and only displays a black or blue background after you log on to a computer that is running Windows 7 or Windows Server 2008 R2 to get more help.

    For your information, please review the similar issues to get more help:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-could-not-connect-to-the-system-event/e8de1ee3-159f-4dae-9e9e-9a648cd85478?page=10

    http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/983e0736-57ef-4c6a-bb10-cfb2712dde24/limited-user-account-cannot-log-on-due-to-error-could-not-connect-to-the-system-event-notification

    Regards,

    Lany Zhang

    • Marked as answer by Bennie ChenModerator Thursday, July 18, 2013 2:22 PM
    • Unmarked as answer by Ewido Friday, July 19, 2013 10:24 PM
    Tuesday, July 9, 2013 9:52 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the response Lany.

    I have the computer back to a working level so I am currently unable to test these methods. However I will should it occur again.

    Thursday, July 11, 2013 3:07 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am Chetan Savade from Symantec Technical Support team.

    Why did you uninstall SEP? Do you see any conflict between SEP and Windows System Event Notification service. Do you see any error in the event viewer?

    Actually Symantec management client sevice depends on the System Event Notifcation service.

    Reference: http://www.symantec.com/docs/TECH146279

    Regards,

    Chetan Savade

    Monday, July 15, 2013 3:38 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I uninstalled it because I was testing everything I could to get it to work. Uninstalling it solved the problem. Reinstalling it did not recreate the problem so far.
    Friday, July 19, 2013 10:25 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I wanted to say thank-you, as these instructions solved my problem.

    Tuesday, February 18, 2014 12:16 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks, i have followed these and the error was gone. But will this problem return again?

    Wednesday, April 9, 2014 3:58 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Lany's solutions worked for me for several desktop logons, but the trouble came back.
    Thursday, May 1, 2014 9:21 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank You.  Deleting the font cache solved it for me.

    Tominator

    Friday, June 6, 2014 2:08 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    I was having this issue in Win 8.1. The mention of the font cache made me realize that I had CCleaner running at startup and the tick box for cleaning the font cache was checked. I removed it and the problem has disappeared.
    Thursday, July 17, 2014 7:45 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks guys method 2 i tried now its working for me..........................god bless you buddy
    Wednesday, April 8, 2015 4:28 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    So I'm having this issue right now. And I've followed the instructions to a T. But my laptop still says the same thing and hasn't gone back to normal at all. What do I do now?
    Friday, June 12, 2015 6:31 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Lany,

       Step 2 solved this problem on my pc. I noticed that the font changed somewhat when my laptop had this problem. The startup time has become normal. Thank you.

    William Tang

    Wednesday, March 2, 2016 5:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Click on Start Button

    Search "cmd.exe" open with Admin

    and Type in - "netsh winsock reset" press enter

    Then Restart your computer.

    Issue Solved
    Wednesday, February 1, 2017 2:30 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Click on Start Button

    Search "cmd.exe" open with Admin

    and Type in - "netsh winsock reset" press enter

    Then Restart your computer.

    Issue Solved
    My network connection suddenly stopped working on windows 7. I could see is connected and enabled however red cross on the connection. The network has been set up as DHCP. After running above command and restarting the PC it started working. Thank you
    Thursday, November 23, 2017 8:25 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I know this is an old thread, but we have a user facing this same problem.

    Only an admin level account can sign in.  Limited user accounts can not.  To get this user on we need to sign on with admin account, run netsh winsock reset, log off and they can log on.  However that is only good for one logon.  EVERY SINGLE TIME the computer is rebooted, an admin account MUST be logged on first, the command run, and then limited user accounts can run.

    I'd almost want to set it as a logoff script in local computer policy, however it needs to run as an admin so when the limited user shuts down it wont run (nor would it run on improper shutdowns). We are not sure what to do, besides tell them to NEVER shut down (only do sleep or hibernate).  It is a laptop if that matters.

    Friday, April 20, 2018 12:02 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    You are the best Lany, Renaming FontCache-System.dat to FontCache-System.old. fixed the issue. 

    Keep up the good work. 

    Thank you 

    Abusha

    Wednesday, June 13, 2018 4:32 PM
    |