Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Issue Related to Low disk space.

Created: 01 Jun 2011 • Updated: 02 Jun 2011 | 8 comments
Language Translations
Mithun Sanghavi's picture
+9 9 Votes
Login to vote

Problem: Receiving pop-up Error message stating "Low Disk Space" after installing Symantec Endpoint Protection Manager (SEPM) or Symantec Endpoint Protection(SEP) on Machines.

Error: Receiving pop-up Error message stating "Low Disk Space"

 

Cause: There may be lots of causes for this issue.

Solution

 

There may be lots of causes for this issue.

Before we start Troubleshooting the Issue, we need to know which drive is running Low on Disk Space and which folder is using the highest space on the Drive.

Once, we have Figured out, we can start with Troubleshooting.

If in case, Windows Files using the Space.

1) Run a Windows Disk Cleanup Manually.

2) Make sure you Uninstall the Unwanted Softwares from the machines.

 

If in case, Symantec Files using the Space, work on the Steps below:

 

Stop the Symantec service

  • Symantec Endpoint Protection

    • Click Start, then Run
    • Type: smc -stop
    • Click OK

Deleting the files

NOTE: The following instructions are to be done from the Command Prompt as attempting to perform the deletions from the Windows user interface may result in delays and application hangs due to the large amount of files that can reside in these locations. Please note that these instructions will delete the files in the targeted directories, not the directories themselves. Do not remove the directories themselves, only the contents of those directories.

 

Open the Command Prompt

Deleting files from User Temp folder

  • Click Start, then Run
  • Type: cmd
  • Click OK

1. Type the following command in Command Prompt. (The following string will vary depending on the user name.) Replace "<NAMEOFUSER>" with the username of the desired Windows user you wish to empty the temp folder for:

 

  • For Windows 2000/XP/2003
     DEL /F /Q "C:\Documents and Settings\<NAMEOFUSER>\Local Settings\Temp"
  •  For Windows Vista/7/2008
     DEL /F /Q "C:\Users\<NAMEOFUSER>\AppData\Local\Temp"

2. Deleting the contents of the temp folder at the root of C:\

  • Type the following command in Command Prompt:

    DEL /F /Q C:\temp

3. Deleting the contents of the Windows Temp folder

  • Type the following command in Command Prompt:

    DEL /F /Q C:\WINDOWS\Temp

4. Deleting the contents of the xfer and/or xfer_temp directories

  • Type the following command in Command Prompt:
      • Windows 2000/XP/2003
        DEL /F /Q "C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\xfer_tmp\"

        DEL /F /Q "C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\xfer\"

      • Windows Vista/7/2008
        DEL /F /Q "C:\ProgramData\Symantec\Symantec Endpoint Protection\xfer_tmp\"

        DEL /F /Q "C:\ProgramData\Symantec\Symantec Endpoint Protection\xfer\"

 

The Quarantine Folder

NOTE: The following instructions are to be done from the Command Prompt as attempting to open the Quarantine folder in the Windows user interface may result in delays and Windows Explorer application hangs due to the large amount of files that can reside there.

 

Delete the Quarantine Folder

Type the following commands in the Command Prompt:

  • Windows 2000/XP/2003
    DEL /F /S /Q "C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\Quarantine"

    RD /S /Q "C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\Quarantine"

  • Windows Vista/7/2008
    DEL /F /S /Q "C:\ProgramData\Symantec\Symantec Endpoint Protection\Quarantine"

    RD /S /Q "C:\ProgramData\Symantec\Symantec Endpoint Protection\Quarantine"

Recreate the Quarantine Folder

Type the following command in Command Prompt:

  • Windows 2000/XP/2003
    MD "C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\Quarantine"
  • Windows Vista/7/2008
    MD "C:\ProgramData\Symantec\Symantec Endpoint Protection\Quarantine"

Start the Symantec service

  • Click Start, then Run
  • Type: smc -start
  • Click OK

 

 

 

Sometimes, we see that the catalina.out file is 6 GB in size

 

  • Stop the Symantec Endpoint Protection Manager service. Browse to C:\ProgramFiles\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\
  • Open the conf.properties file and delete the line that says: scm.log.loglevel=FULL Save and close the conf.properties file
  • While the SEPM service is stopped you can delete all the log files located in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs folder
  • Start the SEPM service.

 

 

 

NOTE: According to the product system requirements, the SEP client requires at least 600 MB of free hard disk space.

Note: the LiveUpdate component is always installed in the C: unit regardless an eventual custom installation path selected for the SEP client. LiveUpdate required at least 130 MB of free space in C:.

 

Check to make sure enough disk space is available

It is receommended to Follow the Articles Below as per the Issue:

 

1) Disk Space Management procedures for the Symantec Endpoint Protection Manager

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

2) Symantec Endpoint Protection virus definition folder consumes a large amount of disk space

 

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

3) Incase, you we want to Monitoring Server Health from Symantec Endpoint Protection Manager and Receive Notification, follow the Article below:

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

 

 

Some Best Practice Articles:

1) Best Practices for configuring the number of content revisions to keep in Symantec Endpoint Protection Manager

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

2) Troubleshooting Content Delivery to the Symantec Endpoint Protection client

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

Group Ownership:

Comments 8 CommentsJump to latest comment

dsmith1954's picture

Whenever I've received this error, it is when I've created a single exe file. If I don't use a single exe file, it will install without all that cleanup. Don't know why. It just works. So for those PCs that I know usually have the problem, I'll use a full installation. For all others, I'll create a single exe.

0
Login to vote
John Santana's picture

Cool, many thanks for the article shared here.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

0
Login to vote
John Cooperfield's picture

Test first!

With both SEP and SEPM, run through the installation on test machines first until you are sure of how it behaves in your environment  e.g. how much space is used.

With the SEPM, remember that every client group you add will consume noticeably more space.

 

+1
Login to vote
John Santana's picture

Yes that does make sense John.

Thanks for sharing the comment here.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

0
Login to vote
technical_specialist's picture

Nice Article Mithun yes

0
Login to vote
Ch@gGynelL_12's picture

very nice article. we need this a lot coz many clients are experiencing this kind of issue/s.. Thanks.

0
Login to vote
dsmith1954's picture

Symantec needs to put stuff where I as a customer tell the application to install, which is usually not on the System drive. We don't install apps on the System drive, and don't expect apps to install anything there when we're telling them to install elsewhere.

One thing that can be done to help alleviate this problem created by Symantec, is to move all temp folders to another drive for SEPM anyway.

+2
Login to vote
John Santana's picture

Mr. Smith yes that does make sense. I agree with you.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

0
Login to vote