• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7791
  • Last Modified:

How do I determine if I can delete a .tmp file from the print spool folder?

Windows 2003 Server: Print Spooling

How do I determine if I can delete a .tmp file from the print spool folder?  There are 3 different files in this folder .SHD, .SPL, .tmp.
Can someone tell me what these .tmp files might be and can I delete them?  One of the temp file name is Tcp44.tmp.

Location of files: C:\WINDOWS\system32\spool\PRINTERS
0
cmleavitt
Asked:
cmleavitt
  • 2
  • 2
1 Solution
 
Scott AndersonPrincipal Support EngineerCommented:
Generally, there shouldn't be any files permanently in the \spool\printers folder.  If the .tmp file isn't in use, I'd delete it.  However, in the case that it might be needful, you can copy it to another location to get it out of the way and have it available if it needs to be put back.  Definately delete the .SHD & .SPL files if they are more than 30 minutes old - they're hung/orphaned print jobs that are stuck in your spooler.
0
 
cmleavittAuthor Commented:
Thanks!

The reason why I want to delete these files is becasuse I've ran out of space on my DC and all printing has stopped.

Do you know if it's possible to relocate the print spool folder?
0
 
Scott AndersonPrincipal Support EngineerCommented:
Absolutely... Open up Printers & Faxes from the Start menu.
Go to  File:Server Properties  and navigate to the "Advanced" tab... you can specify where you want the Spooler folder located...

On the bigger picture of your C: drive being full, you can move out all the Windows Patch Uninstaller folders that are located at:  c:\windows\$NTUinstallKB#######  - that should get you around 300-500MB back.  I typically move those in case they are needed in the future, but usually they aren't needed if your system has been running OK since the install of the patches.  As well, they have to be rolled back in the reverse sequence that they were applied - so pretty much anything over 3 months old will be a lot of work to roll back (you'd have to roll back everything that had been applied since that patch).
Other help would be to move your paging file under SystemProperties:Advanced tab,  then go to PerformanceSettings button, then go to Advanced Tab and leave yourself a 100MB paging file on the C: drive and then put the rest on the D: drive...  you'll want to leave a smaller paging file on your C: drive in case you ever have a BSOD - then it can write out a kernel memory dump to help troubleshoot the issue.

Other things to hit:
1.  c:\windows\temp folder
2.  User profiles on the server (delete any old ones)
3.  Shrink the IE cache in anyone's profile that uses the server

Good Luck.
0
 
PlaceboC6Commented:
I agree with Scooter.
0
 
cmleavittAuthor Commented:
That works!  I appreciate your help!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now