Does anyone know why .SHD and .SPL files become orphaned in the Windows 2003 print spool directory:
C:\WINDOWS\system32\spool\PRINTERS
The files are usually named:
FP000173.SPL & FP000173.SHD, etc.
I am getting about six files (two pair of each) on average, each 0(zero)KB in size, camping out in the "PRINTERS" directory. Our XP clients and Unix (via Citrix Windows desktop) print through our Windows 2003 print server via lpd port which sends the print jobs right through 2003 print server to a Unix printer server where the lpd daemon processes the jobs. We have a card swipe system where students claim their print jobs by swiping their id cards which then grabs the job from the queue on the Unix side. Sometimes print jobs just disappear. I'm not sure if it has anything to do with the orphaned .SHD and .SPL files on the Windows 2003 printer server. I've looked high and low and can't find and answer. Does anyone else use lpd printing in combination with a Windows 2003 print server?
Thanks,
Tim
C:\WINDOWS\system32\spool\PRINTERS
The files are usually named:
FP000173.SPL & FP000173.SHD, etc.
I am getting about six files (two pair of each) on average, each 0(zero)KB in size, camping out in the "PRINTERS" directory. Our XP clients and Unix (via Citrix Windows desktop) print through our Windows 2003 print server via lpd port which sends the print jobs right through 2003 print server to a Unix printer server where the lpd daemon processes the jobs. We have a card swipe system where students claim their print jobs by swiping their id cards which then grabs the job from the queue on the Unix side. Sometimes print jobs just disappear. I'm not sure if it has anything to do with the orphaned .SHD and .SPL files on the Windows 2003 printer server. I've looked high and low and can't find and answer. Does anyone else use lpd printing in combination with a Windows 2003 print server?
Thanks,
Tim
