Endpoint Protection

 View Only
  • 1.  ASA 9.0 Error on SEPM

    Posted Jan 21, 2013 12:10 AM

    Hi everybody

    My SEP Error bellow :

    "The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:ASANYs_sem5, *** ERROR *** Assertion failed: 101412 (9.0.2.3347)"

    I did do it :

    1. restart the Symantec Embedded Database service but stoped by itself. I can not start this services
    2. My disk have 73% free ( that container database )

    Please hep me solve this issue

    Thanks/Duy

     



  • 2.  RE: ASA 9.0 Error on SEPM

    Posted Jan 21, 2013 12:17 AM

    hi,

    Try to repair SEPM ADD/remove programe.

    Check this thread

    https://www-secure.symantec.com/connect/forums/embedded-database-not-running



  • 3.  RE: ASA 9.0 Error on SEPM

    Broadcom Employee
    Posted Jan 21, 2013 12:20 AM

    do you have DB backup?

    try repair, if it does not solve try restoring last good backup



  • 4.  RE: ASA 9.0 Error on SEPM

    Posted Jan 21, 2013 03:10 AM

    Usually the error would be due to lack of space for database:

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

    ...but have a look as well at these threads:

     

    https://www-secure.symantec.com/connect/forums/embedded-database-not-running#comment-2354491

    https://www-secure.symantec.com/connect/forums/symantec-embedded-database-wont-start



  • 5.  RE: ASA 9.0 Error on SEPM

    Trusted Advisor
    Posted Jan 21, 2013 09:34 AM

    Hello,

    What version of SEP are you running?

    Are you running SEP 11.0.5002 or above??

    Could you try following steps - 

    1. Stop Symantec Embedded Database service

    2. Delete sem5.log from the location indicated in logs

    3. Start Symantec Embedded Database service

    If the Above steps does not help, do you have a backup of the SEPM database??

    If yes, please perform a Disaster Recovery steps - http://www.symantec.com/docs/TECH102333

    Hope that helps!!