This is what my issue was:

I had one Win95 PC that was causing 99% of these orphaned .SPL files with 0 bytes. I wasn’t able to remotely configure the CA eTrust Anti-Virus setup because the software was originally installed incorrectly. So I reinstalled the software, configured it to exclude RealTime scanning of the local print spool folder and all *.SPL and *.SHD files.

After that, no more .SPL files, at least from this PC. It doesn’t explain why some WinXP Pro or Win2K Pro PCs cause the .SPL orphaned files, but those are few and far between, which I can live with.

Thanks again for taking the time and helping me out.

Keith

Thanks for the suggestions. And yes, the events corresponding to the spool files do refer to a `remote downlevel document.?

I apologize. Before sending the previous message out, I probably should have listed out the KB articles that I viewed. I already looked at 312015, which why I said that I scanned for viruses on the server in the original message. I also looked at 134779. It says it applies to Windows 95 and the only resolution was to upgrade your NT server to 3.51, so I ignored it because I have Win2K SP4 servers. However, I do have one Win95 with this problem, but I also have some Win2K Pro, WinXP SP1 and SP2 that are having this same problem. Other KB articles that I looked at where: 104923, 162447, and 312015, which none of them helped.

The last suggestion you gave, though, has food for thought: a corrupted print driver. I will look into this.

I suspect that there are a select few PCs that have a corrupted local print driver, because I have other PCs printing to the same printer that do not give me this problem. Also, I do have one Win95 PC that is also causing this `remote downlevel document? problem where its anti-virus is not configured to by-pass scanning for SPL, SHD, local print spooler, and network drives ? hmmmm ? looks like I will have take a look at that one also.

Thanks for the help, and I will let you all know what happens.

Keith