Failed to load - eeCtrl
Created: 01 Nov 2012 | 4 comments
Windows Server 2003 32 bit SP2
Event ID 7026 failed to load eeCTRL
This server is a SEPM v 12.1.1101.401 with SEP client installed 12.1.1101.401.
Pop message on startup, all services runnning. Not sure what service , if any, this is associates with.
How to fix?
Discussion Filed Under:
Comments 4 Comments • Jump to latest comment
I would do a fresh install of SEP
The file is related to the ERASER control engine, its possible it was either being updated (through the defs) during the logon process, or some upgrade process that needed to complete (file rename, etc) was still running after the reboot. If it is working now, and not reproducible I wouldn't worry about it - its not affected the clients ability to detect threats - just potentially the ability to perform advanced cleanup. If it has started now then you will be fine.
https://www-secure.symantec.com/connect/forums/following-boot-start-or-system-start-drivers-failed-load-eectrl
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
How would I know if it is started now?? It is not a service as far as I can tell.
Check this:
https://www-secure.symantec.com/connect/forums/following-boot-start-or-system-start-drivers-failed-load-eectrl
Simson Homer,
How does that link answer the question?
How would I know if it is started now?? It is not a service as far as I can tell.
Would you like to reply?
Login or Register to post your comment.