Endpoint Protection

 View Only
  • 1.  Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 15, 2012 09:55 PM

     

    Hi,

    I just logged in to one of the Windows Server 2008, but then I found this error:

     

     
    ---------------------------
    Symantec Endpoint Protection
    ---------------------------
    Failed to start the Symantec Management Client application. Error code returned: 0x80070102
    ---------------------------
    OK   
    ---------------------------
     
     
    what can I do to make sure that SEP is working fine ?
     


  • 2.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 15, 2012 10:09 PM

    Reboot the box.

    Is the SEP icon showing in the task tray with the green dot? If so, you should be ok.



  • 3.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 15, 2012 10:26 PM

    Reboot the box as Brian81 said... Let us know whats happening..

    What is the SEP client version.....

    is it SEP 11.0.7 or 12.1 & Above....

    We have compatibility issues with previous version of SEP 11.x & 12.0

    Supported version is SEP 11.0.7 or 12.1 & Above....



  • 4.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Broadcom Employee
    Posted Nov 15, 2012 10:28 PM

    check this link

    http://www.symantec.com/docs/TECH173484

    The following fix was added in 12.1 RU1:

    SMC.exe fails to start when the policy file (serdef.dat) is corrupt
    Fix ID: 2359517
    Symptom: SMC.exe will fail to start when the policy file (serdef.dat) is corrupt.
    Solution: SMC.exe will now use the backup.dat and server.dat instead of serdef.dat, if serdef.dat cannot be loaded

     

    Manual workaround (if already on 11.0 RU7 MP1 or  12.1 RU1):

    In situations where the clients have already been updated to 11.0 RU7 MP1 or 12.1 RU1, this would point to corruption that extends beyond serdef.dat and serdef.dat.bak. Investigate a client and determine if the additional corruption resides in cltdef.dat, cltdef.dat.bak, server.dat, or backup.dat. The only time SMC will fail to start during a policy corruption scenario in 11.0 RU7 MP1 or 12.1 RU1 is if the corruption resides in cltdef.dat and cltdef.dat.bak or serdef.dat, serdef.dat.bak, server.dat, and backup.dat simultaneously. Here are the steps to perform if the corruption resides in cltdef.dat and cltdef.dat.bak:

    1. Disable Tamper Protection (if applicable)
    2. Stop SMC (smc –stop)
    3. Replace the corrupt cltdef.dat and cltdef.dat.bak with known-good copies from another client
    4. Start SMC (smc –start)
    5. Re-enable Tamper Protection (if applicable)

    Note: In 11.0 RU7 MP1 and 12.1 RU1 there is no need to manually replace serdef.dat and serdef.dat.bak.

    To manually correct clients that have had their serdef.dat/serdef.dat.bak replaced with one from an incorrect group, make a modification to any policy applied to the group that the client should reside in on the SEPM-side and it will correct the client to reflect the proper group again on the client-side. Note that the policy you modify has to be changed enough to generate a new policy ID number. Verify in the client SEP GUI for the policy number change. When the updated policy is pushed to the clients of that group the *.dat files will be updated with the new policy information.

    It is also possible to replace the cltdef.dat and cltdef.dat.bak or serdef.dat, serdef.dat.bak, server.dat, and backup.dat with good files from a working client that is in the group you would like the client to belong to. You can also update the sylink.xml of the client along with the other changes with one exported from the target group. Performing these changes will effectively update the client and it will attach itself to the group you targeted it to.



  • 5.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 15, 2012 10:40 PM

    Thanks to all, this is SEP 12.1 RU1 MP1 installation that was done automatically, I'll reboot the server over the weekend and then report back to you.



  • 6.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Broadcom Employee
    Posted Nov 15, 2012 10:46 PM

    check if the manual workaround works on this client machine.



  • 7.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 15, 2012 10:57 PM

    John Santana 

    i hope u r installing the SEP 12.1.2 .... It will fix the issue...............

    Hugs...



  • 8.  RE: Failed to start the Symantec Management Client application. Error code returned: 0x80070102

    Posted Nov 16, 2012 10:19 AM

    Yes mister Babu, that is why I've been closely looking at the forum for the SEP 12.1 RU2