Endpoint Protection Small Business Edition

 View Only
  • 1.  invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 01:08 AM

    I need solution for my problem.

    My problem is invalid folder appeared when i put .jdb pattern file into inbox folder.

    In later day, it is ok.

    In my enviroment, 1 SEP 12.x connected with 3 client. all my client installed windows 7 has occurred geniue error and free space is 600MB.

    I want to know symantec pattern can do updating when there is windows was not geniue error and has little space to extract pattern file.

    How many size do we need to extract pattern file especially .jdb file?

     



  • 2.  RE: invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 01:17 AM

    Hi,

    Basically 1 GB Free space required for updating SEP client ?

    Try to clear some space and check again..

    Check this artical also

    Symantec Endpoint Protection Manager is unable to update Virus Definitions via JDB with an Error: "Failed to initialize COM" in SesmLu.log

     

    Article:TECH147268  |  Created: 2010-12-31  |  Updated: 2013-06-19  |  Article URL http://www.symantec.com/docs/TECH147268

     



  • 3.  RE: invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 05:51 AM

    First of all, I would like to thanks for your answer, James007.

    I used third party management tool to update pattern for just only client. Purpose is to test.

    After that, i will deploy this pattern into all client from SEPM server.

    When i put .jdb pattern file into inbox folder of client, invalid error was occurred.

    I would like to know what matters make to be invalid error.

     



  • 4.  RE: invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 08:07 AM

    jdb file is for 32 bit and 64 bit client respectively.

    Make sure you have downloaded the correct one.  Does it work if you download a fresh jdb?

    why dont use intelligent updater which is single exe instead of jdb?

    http://www.symantec.com/security_response/definitions/download/detail.jsp?gid=savce



  • 5.  RE: invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 08:42 AM

    Thanks for your answer.

    .jdb is only one file for 32bit or 64bit. I downloaded the URL: which you pointed.

    But the error is still occurred. Why I don't use intelligent updater is i would like to use the same file with the using one on SEPM.

    I just want to know is why this error occurred.

    is it because of less free space on client or windows has geniue error?

    I would forward your reply...



  • 6.  RE: invalid folder appear when put .jdb into inbox folder

    Posted Jul 08, 2013 09:12 AM

    Here are the possible reasons

    If a TPM update fails, the content copied to the inbox will be moved to a folder called "invalid". Possible reasons:
     

    •     TPM has not been enabled
    •     The file type is not supported
    •     The file structure is incorrect
    •     The content being installed via TPM is already installed or is older than what is installed

    Is your liveupdate on the client working fine?

    was the inbox folder created automatically after you enabled third part in SEPM or you manually created it, this is the path for 11 and 12

    SEP 11.x:
    %ALLUSERSPROFILE%\Symantec\Symantec Endpoint Protection\inbox

    SEP 12.1.x:
    %ALLUSERSPROFILE%\Symantec\Symantec Endpoint Protection\CurrentVersion\inbox

    check the event viewer and also the log.lue under

    On Windows Vista, Windows 7, and Windows Server 2008:
    C:\Program Data\Symantec\Symantec Endpoint Protection\<silo_id>\Data\Lue\Logs

    check these logs it will give you the reason. You can post it  here as well.



  • 7.  RE: invalid folder appear when put .jdb into inbox folder

    Trusted Advisor
    Posted Jul 09, 2013 08:15 AM

    Hello,

    Agreed with above comment - 

    If a TPM update fails, the content copied to the inbox will be moved to a folder called "invalid".

    Possible reasons:

    •     TPM has not been enabled
    •     The file type is not supported
    •     The file structure is incorrect
    •     The content being installed via TPM is already installed or is older than what is installed

    For more details on TPM and updates regarding SEP 12.1 clients, see HOWTO80942, "<subhead>How to Use a Third Party Tool for Content Deployment</subhead>" and HOWTO80914"Preparing unmanaged clients to receive updates from third-party distribution tools".

    Also check the below downloads which may be of some interest to you:

    Script That Downloads .JDB Automatically

    Script to download Definitions from SEPM

    Hope that helps!!