none
SBS 2003 R2 - event ID 7023 The System Event Notification service terminated with the following error: The specified module could not be found. RRS feed

  • Question

  • Event ID 7023 The System Event Notification service terminated with the following error:
    The specified module could not be found.

    I keep getting this error every 30 seconds - before this I get the 7035 and 7036 event ids where the server attempts to start the service and then stops - if you try manually the error 126 is shown. All my attempts to fix the SENS service have failed. also, the server is extremely fragile and freezes completely for no apparent reason - not sure if this is related but it's the only consistent error message that appears. I have searched over lots of sites for a fix for this but all to no avail.

    Help please somebody?

     

     

    Wednesday, December 15, 2010 11:12 AM

Answers

  • This is sorted now - in one last desperate attempt I rescanned the computer after swapping the memory and found a little virus tucked awayand then after getting rid of that when I checked the registry path for the SENS service I found the path had been changed to that virus file. So changed that back to the correct path and lo and behold all worked well and server stopped freezing - all working fine now.
    Monday, January 17, 2011 9:42 AM

All replies

  • Hi

    check this MS KB article

    http://support.microsoft.com/kb/892501

    thanks


    Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist
    Wednesday, December 15, 2010 11:27 AM
  • Hi Naeem

    Sorry I don't see the relevance of this Windows Time issue - as it happens the Windows Time Service is running fine.

    My server has just crashed again for no good reason that I could see - I sat and watched the performance counter for Pages/sec on memory top out but according to event viewer no RAM usage and no unusual or high processes running argh!

    Thanks

     

    Mark

     

     

    Wednesday, December 15, 2010 12:36 PM
  • Disabling event logging is often a first step in hiding one's tracks. You say the server is very fragile. Has this been the case for some time or is this all new behavior for this server?

    Good and current backups?

    Likely you should be considering a Microsoft support call unless you can pinpoint some cause / effect.


    /kj
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, December 15, 2010 5:11 PM
    Moderator
  • We took this under support last week and since then it has frozen once or twice sometimes more a day - when it is running, all appears well, but suddenly it freezes and needs rebooting - driving my customer absolutely mad!

    I have managed to get some backups off it but have had no chance to verify these so it is guesswork whether they will work.

    The server is 16 months old and about 4 months ago completely died and another company spent weeks on it eventually having to restore it from backup - since then it has been fragile.

    There is no good apparent cause it just freezes and stops serving, sometimes you can reboot it other times a hard reset is required.

    So frustrating...

    Mark

    Wednesday, December 15, 2010 6:59 PM
  • Weeks on a restore? Yikes.

    Doesn't sound like hardware problems have been elimated. You might consider trying to disk2vhd it and diagnose it in a virtual enviroment seperate from the physical server.

    Otherwise, event logs, vendor diagnostics, memory diags, etc....


    /kj
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, December 15, 2010 7:12 PM
    Moderator
  • This is sorted now - in one last desperate attempt I rescanned the computer after swapping the memory and found a little virus tucked awayand then after getting rid of that when I checked the registry path for the SENS service I found the path had been changed to that virus file. So changed that back to the correct path and lo and behold all worked well and server stopped freezing - all working fine now.
    Monday, January 17, 2011 9:42 AM
  • HI,

    Having the same problems.  Can you tell us what registry path you found to be wrong and what you changed it to.  Did it previously point to subesofilcom.dat.

     

    Thanks

    Monday, October 31, 2011 11:25 PM