Endpoint Protection

 View Only
  • 1.  Issue with JDB files error

    Posted Feb 09, 2016 05:42 AM

    Hi, I am having an issue with the FBP JDB as it keeps giving .err

    SEPM 12.1. RU6 build 6608 - Server 2012 r2.

    I manually copy the jdb's via USB to 3 different environments.

    The other 2 environments have successfully updated with all 3 JDB's.

    1 environment updated with SONAR and IPS but not with the FBP JDB. This was successfully completed yesterday but errors today.

    I have restarted the services, copied across new JDB's, restarted the server. Other suggestions I have read are to repair the application which I have not done yet and to uninstall/install live update. Disk space on ther server is fine.

    Last part of the sesmlu.log showing the errors:

    02/09 09:50:13 [17b4:17b8] INFO(Low)   ProductUtil ConfProp: scm.http.port=9090
    02/09 09:50:13 [17b4:17b8] INFO(Med)   TomcatServerXml Entered Init().
    02/09 09:50:13 [17b4:17b8] INFO(Med)   ProductUtil Initialize Tomcat server xml file successfully.

    02/09 09:50:13 [17b4:17b8] INFO(Med)   SesmLu http://127.0.0.1:9090/servlet/ConsoleServlet?ActionType=ConfigServer&FilePath=E:\Symantec\Symantec%20Endpoint%20Protection%20Manager\data\inbox\content\tmp99f5d9da.tmp&Hash=5451FDDA520461AE1186C89031AB3B5F&Language=SymAllLanguages&Product=SEPM%20Virus%20Definitions%20Win32%2012.1%20RU6&SequenceNum=160208041&SequenceTag=CurDefs&ServerMoniker={D2EE983B-0AB4-F6D4-00BE-1539CD0C259E}&Version=MicroDefsB.CurDefs&action=UploadLuContent
    02/09 09:50:13 [17b4:17b8] INFO(Low)   SesmLu <?xml version="1.0" encoding="UTF-8" standalone="no"?><Response ResponseCode="268500992"/>0
    02/09 09:50:13 [17b4:17b8] INFO(Med)   ProductUtil Response code: 0x10010000
    02/09 09:50:13 [17b4:17b8] ERROR       SesmLu Servlet returned unexpected server errorat SesmLu.cpp[1719]
    02/09 09:50:13 [17b4:17b8] ERROR       SesmLu Failed to notify SESM servlet of new LiveUpdate package.at SesmLu.cpp[1502]
    02/09 09:50:13 [17b4:17b8] INFO(Med)   SesmLu Notified server about new LiveUpdate content
    02/09 09:50:13 [17b4:17b8] ERROR       SesmLu Fail to notify server of new content.at SesmLu.cpp[654]
    02/09 09:50:13 [17b4:17b8] INFO(Low)   DefaultDefUtilsContentHandler CDefUtils::~CDefUtils(): destructor exiting. (File = defutils.cpp, Line = 430



  • 2.  RE: Issue with JDB files error
    Best Answer

    Posted Feb 09, 2016 12:04 PM

    Duplicate post:

    https://www-secure.symantec.com/connect/forums/jdbs-err-1216-sepm?cid=11546341#comment-11546341



  • 3.  RE: Issue with JDB files error

    Posted Feb 10, 2016 05:25 AM

    Try a full re-cycle

     

    Turn off the SEPM managers one by one, then reboot the server/servers with the SQL database, then bring the SEPM manager servers online on by one.  I have an environment that has to use the jdb file everyday and therefore have found this tends to work if the stop start of the services fails to stop the file from erroring.

     

    The other factor can be disk space ensure that due to the file size increase of the jdb over time that you havent hit a threshold where disk space is now an issue.



  • 4.  RE: Issue with JDB files error

    Posted Feb 10, 2016 05:33 AM

    It resolved itself and later that afternoon it accepted the file with no issues. Thanks for the replies.



  • 5.  RE: Issue with JDB files error

    Broadcom Employee
    Posted Feb 10, 2016 07:05 AM

    Glad to know it's working, SEPM might have tried to purge corrupted files.