Endpoint Protection

 View Only
Expand all | Collapse all

The Symantec Management Client service entered the stopped state

  • 1.  The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 06:10 PM

    Have installed SEP client (12.1) on a Windows Server 2003 computer, this client install has run fine on all other computers (approx 500) on the network, except on THIS machine, the install completes, the services attempt to start, and the Symantec Management Client services starts and stops! Try to start this service manually and you get the "The Symantec Management Client service on Local Computer started and then stopped. Some services stop automatically if they have no work to do..." Well this service DOES have work to do, and I'd like it to do it!

    I haven't found anything else in trawling these forums that can helop me, does anyone have any ideas? I have even installed a generic client installation without the specific sylink.xml file pointing to the group on the SEPM server, but no joy.

    Any help or suggestions would be appreciated!

    Thanks
    Harvansh Singh

     



  • 2.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 06:50 PM

    What components do you have installed?

    Have you tried doing a complete uninstall/reinstall?

    I would suggest running cleanwipe to completely remove. See this thread on getting cleanwipe:

    https://www-secure.symantec.com/connect/forums/how-get-cleanwipe-tool-endpoint-removal



  • 3.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 07:48 PM

    I have not unstall the SEP. I need solution without unstallution and reboot if there is any way.

    Please help how to stat the SEP services without take reboot to system.



  • 4.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 07:51 PM

    Try running a repair on the client. This will not require a reboot.

    In my experience, however, this issue has needed a reboot to correct more often than not.



  • 5.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 08:01 PM

    Hi Sir,

    In that system all services are running properly apart from SEP services. As per my knowledge machine is not having any problem but in SEP some issue is there so SEP services is not able to start. Please let me know any option is posibale from registry and SEP program file end . But we can not take reboot the machine any condition.

    Regards

    Harvansh Singh



  • 6.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 08:58 PM

    There is no option from registry that I know of, especially one that will not cause a reboot.

    I would try a repair from add/remove programs. This will not require a reboot.



  • 7.  RE: The Symantec Management Client service entered the stopped state

    Posted Oct 28, 2012 09:37 PM

    Hi,

    Could you share SEP file details and how these exists with the registry. Please share all SEP file details and registry value for Best practice documents.

    Regards

    Harvansh Singh



  • 8.  RE: The Symantec Management Client service entered the stopped state



  • 9.  RE: The Symantec Management Client service entered the stopped state



  • 10.  RE: The Symantec Management Client service entered the stopped state
    Best Answer

    Posted Nov 01, 2012 03:31 AM

    Hi all,

    Thanks for valuable support, now this issue got resolved.

    Regards

    Harvansh Singh

     



  • 11.  RE: The Symantec Management Client service entered the stopped state

    Posted Nov 01, 2012 03:33 AM

    HI,

    If any comments help you please don't forgot mark as solution.

    If not please provide Solution



  • 12.  RE: The Symantec Management Client service entered the stopped state

    Broadcom Employee
    Posted Nov 01, 2012 04:10 AM

    Hi,

    Thanks for an update, however could you please confirm which steps helped you to resolved the issue.