Endpoint Protection

 View Only
Expand all | Collapse all

SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

  • 1.  SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 13, 2010 01:51 PM
      |   view attached
    I'm trying to set up SEP on two new Dell laptop running Windows 7 and cannot get the Symantec Management Client service to run on either one.

    When trying to run the program after installation I get the following error:

    "Failed to start the Symantec Management Client Application.  Error Code returned 0x80070102"

    I can go to the services panel and start the process, but Windows 7 stops the process after a couple of seconds with no error message.

    I've tried installing the unmanaged client and copying the sylink.xml file from one of my other clients as described in another post, but this did not solve the problem.

    Any help resolving this would be greatly appreciated.

    Thanks.

    Attachment(s)



  • 2.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 13, 2010 02:01 PM
    1. 0Make sure you are installing 11.0.5002.33 client on this WIndows 7 machine.
    2. Disable UAC
    3.Did you have any other Security app running on this machine ? or a older version of SEP or Norton etc ?
    4. Scan you machine once with any NSS or malwarebytes to check if any security risk is blocking sep from running.

    What is the error you get in the Event viewer ?
     


  • 3.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 13, 2010 04:10 PM
    Thanks for the response.

    I am installing the 11.0.5002.33 client on the Windows 7 machine.  I created a new unmanaged client install package after reading some other suggestions on the site.

    I had disabled UAC.

    This laptop just came out of the box from Dell.  There was no other anti-virus software installed on it.

    Once I had installed SEP, it did do a scan and didn't report any problems.

    This is the information from the System Event Viewer Log:

    When I start the SEP client and get the message stating that the management client service isn't running and do I want to start it, this is the error generated in the system log:

    - System
       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7030
          [ Qualifiers] 49152
       
      Version 0
       
      Level 2
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-01-13T20:56:16.275126600Z
       
      EventRecordID 4384
       
      Correlation
       
    - Execution
          [ ProcessID] 568
          [ ThreadID] 3152
       
      Channel System
       
      Computer gwlaptop2010.dashiell.local
       
      Security
    - EventData
        param1 Symantec Management Client

    The error is followed by this information entry:
    - System
       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7036
          [ Qualifiers] 16384
       
      Version 0
       
      Level 4
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-01-13T21:02:37.793629900Z
       
      EventRecordID 4385
       
      Correlation
       
    - Execution
          [ ProcessID] 568
          [ ThreadID] 4416
       
      Channel System
       
      Computer gwlaptop2010.dashiell.local
       
      Security
    - EventData
        param1 Symantec Management Client
        param2 running
          53006D00630053006500720076006900630065002F0034000000

    Binary data:
     

    In Words

    0000: 006D0053 00530063 00720065 00690076
    0008: 00650063 0034002F 0000
     

    In Bytes

    0000: 53 00 6D 00 63 00 53 00 S.m.c.S.
    0008: 65 00 72 00 76 00 69 00 e.r.v.i.
    0010: 63 00 65 00 2F 00 34 00 c.e./.4.
    0018: 00 00 ..

    I wait for about a minute and the the "failed to start" message appears.  The following information entry in the system log is then created:

    - System

       
    - Provider
          [ Name] Service Control Manager
          [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
          [ EventSourceName] Service Control Manager
       
    - EventID 7036
          [ Qualifiers] 16384
       
      Version 0
       
      Level 4
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2010-01-13T21:02:49.807521600Z
       
      EventRecordID 4386
       
      Correlation
       
    - Execution
          [ ProcessID] 568
          [ ThreadID] 2696
       
      Channel System
       
      Computer gwlaptop2010.dashiell.local
       
      Security

    - EventData

        param1 Symantec Management Client
        param2 stopped
          53006D00630053006500720076006900630065002F0031000000

    Binary data:
     

    In Words

    0000: 006D0053 00530063 00720065 00690076
    0008: 00650063 0031002F 0000
     

    In Bytes

    0000: 53 00 6D 00 63 00 53 00 S.m.c.S.
    0008: 65 00 72 00 76 00 69 00 e.r.v.i.
    0010: 63 00 65 00 2F 00 31 00 c.e./.1.
    0018: 00 00 ..

    I hope this helps.

    Thanks again.



  • 4.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 13, 2010 07:02 PM
    Run the SEP Support Tool and see if that leads us anywhere..
    http://service1.symantec.com/support/ent-security.nsf/docid/2008071709480648 


  • 5.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 02:19 PM
    I've run the support tool and I will send you the report it generated.

    Thanks.


  • 6.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 02:28 PM
     It would be better if you could post it as a link in your original post. That way we can all view it : )

    Grant-


  • 7.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 02:31 PM
    I'll do that.  I was looking for a way to attach the file to a response, but guess there isn't a way to do that.


  • 8.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 02:38 PM
     Edit you post...the top one..on the bottom you will see a attachment button.


  • 9.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 03:22 PM
    This was found in the System log in the log file

    Error
     The Symantec Management Client service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.


  • 10.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 05:47 PM
    Is the SMC supposed to be an interactive service?  If so, any idea on how to allow interactive services on Windows 7.  Everything I can find is for Vista and basically says that Microsoft removed support for interactive services.

    I checked the SMC service and the 'Allow service to interact with desktop' was checked, so I unchecked it as recommended here: technet.microsoft.com/en-us/library/dd349385%28WS.10%29.aspx, but it still will not run.


  • 11.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 14, 2010 08:52 PM
    Give it a try

    go to services.msc snap-in and identify the service named Interactive Services Detection. Now stop and disable it.

    You have to reinstall the software needs to interact with your desktop and this time you will not get any trouble.



  • 12.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 15, 2010 11:40 AM
    I'll give that a try and will let you know the results.

    Thanks.


  • 13.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 16, 2010 12:09 AM
    If above suggestion not helps try by repairing the client from add/remove programs...
     


  • 14.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 18, 2010 05:06 PM
    I tried disabling the Interactive Services Detection Service (it was off & set to manual before), uninstalled SEP and reinstalled (for about the 8th time) and still have the same problem. 

    I ran the dianostic tool before I reinstalled and the pre-installation check showed no potential problems, but something is just not letting this service run.

    I've submitted a case on this,  maybe tech support will have some other suggestions.


  • 15.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start

    Posted Jan 18, 2010 05:39 PM
      The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
     
    File Name: \Device\HarddiskVolume3\Windows\System32\drivers\WPSDRVnt.sys

    Try installing just Antivirus and Antispyware without Network Threat Protection.


  • 16.  RE: SEP Version 11.0.5002.333 - new Windows 7 Client - Symantec Management Client Service won't start
    Best Answer

    Posted Jan 20, 2010 12:23 PM
    I finally solved my problem with help from Jon with Symantec support.

    Even though I was logged on to the computer administrator's account, SEP was not being installed using administrator permissions (Thanks, Microsoft!).  Basically, I just had to run the setup file by right clicking and selecting "run as administrator"

    Here is the link to the Knowlege Base article on the issue:

    service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009110401211048

    Thanks to everyone who took the time to try to help me with this.