HUGE GLC*.tmp Temp File

  • Thread starter Thread starter Bryan McDaniel
  • Start date Start date
B

Bryan McDaniel

Has anyone else seen this issue. We are having numerous machines that are
generating a huge temp file. They are named GLC***.tmp and located in
C:\windows\temp. Where * are apparently random numbers. When I say huge I
mean they take up 32 gigs on a 40 Gig Harddrive. I have come close to
exausting my resources and have not found a solution. I have searched the
event logs of these machines, and there is nothing written around the same
time the files were created. And as far as I can tell there is no software
that is common among these machines.

Bryan McDaniel

Technical Support Specialist II

Information Systems

Cardinal Health Systems Inc.

(765)747-3939
 
Bryan McDaniel said:
Has anyone else seen this issue. We are having numerous machines that are
generating a huge temp file.
Click to expand...

I did a search and came up with one copy of GLC***.tmp (exactly - no
numerical substitution) labelled google groups. On mine its a very tiny
file.

Dont know if this is any help??

Having a nasty suspicious mind I also wondered if someone at work is using
your system for an ftp server ( not sure if thats the correct term)?? 15 or
so films would probably use up that amount of space?
 
They should be safe to delete.

I would delete some by leaving them in the Recycle Bin. If it does not create an issue then continue deleting a section at a time from the *.tmp file as per above.
 
I know I can delete them with no problem. The issue is that they are
growing so fast, and are not automatically getting deleted, and the users
are getting low disk space errors.
I want to stop them from ever growing to that size.



They should be safe to delete.

I would delete some by leaving them in the Recycle Bin. If it does not
create an issue then continue deleting a section at a time from the *.tmp
file as per above.
 
Bryan McDaniel said:
I know I can delete them with no problem. The issue is that they are
growing so fast, and are not automatically getting deleted, and the users
are getting low disk space errors.
I want to stop them from ever growing to that size.
Click to expand...


Hello Bryan

Perhaps you could try using something like Sysinternals' Process
Explorer http://www.sysinternals.com/ProcessesAndThreadsUtilities.html
to find out what program is creating these files?
 
It is not an issue of can we delete it. It is an issue of why is this
happening. I don't want to have to go to 15 different machines a day to
clear this temp file.


They should be safe to delete.

I would delete some by leaving them in the Recycle Bin. If it does not
create an issue then continue deleting a section at a time from the *.tmp
file as per above.
 
Possibility of a corrupt installation of a 3rd party software. What does the Properties of this file indicate. It has nothing to do with Windows file or installation
 
It looks as if an application is creating log files. A few months ago
Webroot Spycatcher did this and I stopped using it. You will have to delete
the files and try to identify the application in running processes by
monitoring the folder for the appearance of new ones.
 
Bryan said:
Has anyone else seen this issue. We are having numerous machines that
are
generating a huge temp file. They are named GLC***.tmp and located in
C:\windows\temp. Where * are apparently random numbers. When I say
huge I
mean they take up 32 gigs on a 40 Gig Harddrive. I have come close to
exausting my resources and have not found a solution. I have searched
the
event logs of these machines, and there is nothing written around the
same
time the files were created. And as far as I can tell there is no
software
that is common among these machines.

Bryan McDaniel

Technical Support Specialist II

Information Systems

Cardinal Health Systems Inc.

(765)747-3939
Click to expand...

Did you ever determine what was causing the issue you originally posted
about? (c:\window\temp\glc***.tmp generating a huge temp file. Where *
are apparently random numbers. I am seeing the same thing in the env I
support. Please let me know.
 
Back
Top