Video Screencast Help

SEP service will not start

Created: 07 Jan 2008 • Updated: 21 May 2010 | 3 comments
I have pushed the client to 5 workstations so far, and the 5th is giving me major problems.  The Symantec Endpoint Protection service will not start.

When I try to manually start it, I get the following error:
Could not start the Symantec Endpoint Protection service on Local Computer
Error 1053: The service did not respond to the start or control request in a timely fashion
The event log shows 2 errors each time I try to start the service.  The first is:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date:  1/7/2008
Time:  8:57:11 PM
Computer: 111-4
DCOM got error "The service did not respond to the start or control request in a timely fashion. " attempting to start the service Symantec AntiVirus with arguments "" in order to run the server:
For more information, see Help and Support Center at
The second error is:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date:  1/7/2008
Time:  10:00:03 PM
User:  N/A
Computer: 111-4
Timeout (30000 milliseconds) waiting for the Symantec Endpoint Protection service to connect.
For more information, see Help and Support Center at
I can't figure out what is going on, I have stopped all services and processes but no matter what I do, no matter how many times I uninstall/re-install, the service will not start. 

Any ideas on resolution please?

Comments 3 CommentsJump to latest comment

Damar Software Solutions's picture


I had a similar issue with one machine a few weeks ago, the only thing i can suggest is checking that you have all the latest windows updates, turned out i had a update missing that was essential to Symantec running properly or so it would seem.

Hope this helps


M Riley

cwb124's picture
I installed all critical and recommended updates but the SEP service will not start. 

Does anyone have any other suggestions to try? 
ENS-Inc's picture
I too had this issue.  After hours of troubleshooting I found that the particular PCs which were experiencing the issue were missing a dll file...  What you can try doing is to find the following dll:  ODBCBCP.DLL  you should be able to find it on your SEPM server (if that is running correctly it should show up there).  Take that dll and copy it into the windows/system32 folder, then register it (regsvr32 odbcbcp.dll).  Mine failed the registration but still appeared to work...sep started right up.