Endpoint Protection

 View Only

  • 1.  SEPM Database Issue

    Posted Mar 30, 2011 08:35 PM

    Hi Guys,

    I'm having a little issue with our embedded database for SEPM. I have run the dbvalidator.bat after having some issues with a disaster recovery. I had to complete a disaster recovery after some server issues. Now when I log onto the SEPM console the Domain and Server tabs on the admin page do not show and the clients do not communicate to the manager. Please see below the results of running the dbvalidator.bat minus a lot of unhelpful script. Any help would be appreciated. The Server is a Win 2003 SP2 x64 Edition.

    2011-03-30 19:33:09.289 INFO: *********************************************

     

    2011-03-30 19:33:09.289 INFO: Following ids are not present in the database.
    2011-03-30 19:33:09.289 INFO: *********************************************
    2011-03-30 19:33:09.289 INFO: Link is broken for [0] target ids :
    2011-03-30 19:33:09.289 INFO: *********************************************
    2011-03-30 19:33:09.289 INFO: Link is broken for [2] physical file ids :
    2011-03-30 19:33:09.289 INFO: TargetId:[0DF5109DF0746AB29C930587ACC3B13E] TargetType:[ExPhysicalFileStream] ObjectTypeName:[ObjReference] ParentObjectTypeName :[PhysicalFile] Parent's TopLevelObject's GUID:[2329D0B142EF2E06665CB3DDF7BCBCC7]
    2011-03-30 19:33:09.289 INFO: <?xml version="1.0" encoding="UTF-8"?>
    <PhysicalFile CreationTime="1271165456265" Description="Symantec Endpoint Protection version 11.0.5002.333 for WIN32BIT" FileChecksum="9DC72858D55DBC4184EEB5406CA258D0" FileLastModifiedTime="1271165456265" FileName="C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\Packages\SAV32.dat" FileSize="100496899" Id="2329D0B142EF2E06665CB3DDF7BCBCC7" Name="ClientPackageFile" NameSpace="schema" _d="false" _i="25B58AC7DD6351DD80AE14FAAEF4BBCE" _t="1271165456265" _v="15">
      <ObjReference Name="LinkToFileContent" TargetId="0DF5109DF0746AB29C930587ACC3B13E" TargetType="ExPhysicalFileStream" _d="false" _i="6AF1C940335BE6058ED3F52312CEF7FF" _t="1271165456265" _v="7"/>
    </PhysicalFile>
     
    2011-03-30 19:33:09.289 INFO: TargetId:[C85ADF024610D6BF9FC342CD3706A5EA] TargetType:[ExPhysicalFileStream] ObjectTypeName:[ObjReference] ParentObjectTypeName :[PhysicalFile] Parent's TopLevelObject's GUID:[8AEE818BF4AE2A0FD0124A0C22DC154C]
    2011-03-30 19:33:09.289 INFO: <?xml version="1.0" encoding="UTF-8"?>
    <PhysicalFile CreationTime="1271165625312" Description="Symantec Endpoint Protection version 11.0.5002.333 for WIN64BIT" FileChecksum="51CBB93FD2F77A3E7E65B6187890712A" FileLastModifiedTime="1271165625312" FileName="C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\Packages\SAV64.dat" FileSize="103621943" Id="8AEE818BF4AE2A0FD0124A0C22DC154C" Name="ClientPackageFile" NameSpace="schema" _d="false" _i="9ED766C1A5D8EA16A068AA5E4A2A142F" _t="1271165625312" _v="15">
      <ObjReference Name="LinkToFileContent" TargetId="C85ADF024610D6BF9FC342CD3706A5EA" TargetType="ExPhysicalFileStream" _d="false" _i="66251D24A432BF89151B5CE3F77D04A6" _t="1271165625312" _v="7"/>
    </PhysicalFile>
     
    2011-03-30 19:33:09.305 INFO: *********************************************
    2011-03-30 19:33:09.305 INFO: Database validation failed.
    2011-03-30 19:33:09.305 INFO: Finished.


  • 2.  RE: SEPM Database Issue

    Posted Mar 30, 2011 08:53 PM

    Try loading an older backup if you have one to test the integrity of the database.



  • 3.  RE: SEPM Database Issue

    Posted Mar 31, 2011 02:34 AM
    2011-03-30 19:33:09.289 INFO: Following ids are not present in the database.
    2011-03-30 19:33:09.289 INFO: *********************************************
    2011-03-30 19:33:09.289 INFO: Link is broken for [0] target ids :
    2011-03-30 19:33:09.289 INFO: *********************************************
     
    The above log states the Db is corrupt , try suggestion as above or workaround would be to perform clean install with Fresh db
     


  • 4.  RE: SEPM Database Issue

    Posted Mar 31, 2011 02:42 AM

    mon is correct if you have known good database backup then restore.

    Did you followed the same procedure while validation

    http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/a5f9153ff7a6add0882574430060dc04?OpenDocument

    And if you dont have any good one databse backup then try for  Disaster Recovery .

    Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

    http://www.symantec.com/business/support/index?page=content&id=TECH102333&locale=en_US



  • 5.  RE: SEPM Database Issue

    Broadcom Employee
    Posted Mar 31, 2011 04:14 AM

    Disaster Recovery is a good choice.

    In the Restoring client communications section follow Restoring client communications without a database backup



  • 6.  RE: SEPM Database Issue

    Posted Mar 31, 2011 11:14 AM

    Yep, unfortunately no backup is available for this database other than the one taken for the disaster recovery purposes and that is the one that appears corrupt. Although a clean install with a new database or following the "Restoring client communications without a database backup" section of the DRP are both possible and I believe would work it is not the desired course of action as yet. The hope is that the database can be repaired somehow.

     

    Thank you all for your insight so far.



  • 7.  RE: SEPM Database Issue

    Posted Mar 31, 2011 11:17 AM

    if you have the JKS key stroke file you can restore the communication.

    https://www-secure.symantec.com/connect/forums/sepm-cannot-see-clients



  • 8.  RE: SEPM Database Issue

    Posted Mar 31, 2011 06:51 PM

    I do have the JKS Keystroke file from the disaster recovery procedure but on restoring this it does not allow the clients to comunicate.



  • 9.  RE: SEPM Database Issue

    Posted Apr 01, 2011 02:15 AM

    Do you have a list of all the clients? If yes, you can use the sylink replacer on all of them.