Endpoint Protection

 View Only
  • 1.  SEP: Can't start scanning, not enough disk space

    Broadcom Employee
    Posted May 19, 2010 10:42 AM

    SEP insalled on Terminal Server, working about 10 users. When starting scaning from console, GUI or SEPM getting error "not enough disk space"
    Application Error log shows:
    Source: Symantec Antivirus
    Event Id: 21
    http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.5002.290&language=english&module=1000&error=0021&build=symantec_ent


  • 2.  RE: SEP: Can't start scanning, not enough disk space
    Best Answer

    Broadcom Employee
    Posted May 19, 2010 10:47 AM


    Title: 'You receive the following error:
    "Event ID 21 - not enough disk space to launch the scan"'
    Document ID: 2009052109433548
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009052109433548?Open&seg=ent



  • 3.  RE: SEP: Can't start scanning, not enough disk space

    Broadcom Employee
    Posted May 19, 2010 02:19 PM
    I highly recommend this tool for quickly/easily finding disk space that can be freed up...

    http://windirstat.info


  • 4.  RE: SEP: Can't start scanning, not enough disk space

    Broadcom Employee
    Posted May 19, 2010 07:28 PM
    Hi DaMu,

    Please write back and let us know if you are actually out of disk space. I am assuming you are not otherwise you would just check that : ) Just to let you know the min requirements for the SEPM are 4g hard drive space plus another 4 gigs for the database. So if you are flirting with the min requirements you should just up the harddrive space to 20gb or so and you shouldn't have any more trouble.

    Grant-


  • 5.  RE: SEP: Can't start scanning, not enough disk space

    Broadcom Employee
    Posted May 20, 2010 01:47 AM

    Thank You for your replies, they were very helpful. I have already 11 Gb free space and checked permissions on temp folders. After that I noticed in system settings that %temp% variable was pointing to other folder. I changed %TEMP% and %TMP% variables to default folders and I could run scanning after restarting "Symantec Endpoint Protection" service.