Symantec Antivirus temp data file taking too much space

Hi experts,

This morning we had a problem with space on one of our production servers. After doing a search for large file I found one file without extension
C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5\000001AF

The size is more than 900 MB, it was created and last modified at 1:24am this morning. I'm not sure what type of file is it and why it is taking so much space. This problem first occured 2 months, same location, maybe slightly different file name (can't remember either way), and the size was more than 1.5GB. I just simple deleted the file and everything was ok.

This server has Windows Server 2003 Standard SP2, it has Symantec Antivirus client installed and managed from our Symantec Antivirus server. No other servers have this problem.

I suppose deleting this large file won't permanently get rid of this issue.
Your advices are appreciated !
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TG TranIT guyCommented:
Have you check to see if the scheduled scan complete successfully?   The most likely culprit is the scheduled scan encountered problems and this large file is the log file.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The only permanent fix is to find the location where the file is, and carefully go through the program's settings or config options, and find out where this path is specified.  There too you will probably find a setting to either save log files or perhaps even make a backup of the system to this location.  Once you find the setting, you will be able to figure out how to handle it.  Don't delete the file until you find out why it is being written.
Johnny_NguyenAuthor Commented:
I guess tqtran has figured this out.
For some reason when I changed the scan schedule from Saturday night to Friday night, this problem was gone. Previously we did have a schedule restart of all server at 12:00am Sunday, which might caused the scan from Saturday night to fail.

Thank you very much for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps

From novice to tech pro — start learning today.