I am building a Windows Server 2003 Standard print server to replace an existing Windows 2000 Server print server. The new server is running SP1 and is fully patched. Here's the problem: Users can print to printers on the new server -- the print jobs come out complete and correct -- but the spool files (.SHD and .SPL) do not delete after the job prints. Instead, they go to 0 (zero) bytes but are still listed in the C:\Windows\System32\Spool\Printers folder.
If another job is printed across the network (by the same or another user), it uses the existing spool file pair. However, if a print job is issued locally (on the server while logged in as the domain admin), it also uses the existing pair of files for the spool -- I see the size and date/time stamp change -- and then they are deleted as they should be. If there are no spool files and a local print job is issued, the files are created and immediately deleted, as expected.
Other data:
• The spool files do not have the Read-Only attribute set.
• This occurs for all printers & all users printing to the W2K3 server & no printers or users on the W2K server.
• I have done nothing unusual in the setup of the new server other than run the "Manage your Server" wizard and add the Print Server role (which simply runs the "Add Printers" wizard).
• I changed the permissions on the C:\Windows\System32\Spool\Printers so that the "Everyone" group has full rights to the Printers folder. I added the Domain Users group & gave it full permissions. I gave all groups all permissions to the printers (Print, Manage Printers, and Manage Documents). Still no luck.
• I set up the same scenario on another W2K3 box and had the same problem, so it's not an issue related to this particular server. I also set it up on another W2K Server box and it was OK. The permissions on the C:\...\Printers folders are identical (and the default).
How do I get the spool files to delete once the print job is done on the W2K3 boxes? Is there some subtle difference between W2K Server and W2K3 Server? Is this even something that I should be worried about?
TIA,
roshan
If another job is printed across the network (by the same or another user), it uses the existing spool file pair. However, if a print job is issued locally (on the server while logged in as the domain admin), it also uses the existing pair of files for the spool -- I see the size and date/time stamp change -- and then they are deleted as they should be. If there are no spool files and a local print job is issued, the files are created and immediately deleted, as expected.
Other data:
• The spool files do not have the Read-Only attribute set.
• This occurs for all printers & all users printing to the W2K3 server & no printers or users on the W2K server.
• I have done nothing unusual in the setup of the new server other than run the "Manage your Server" wizard and add the Print Server role (which simply runs the "Add Printers" wizard).
• I changed the permissions on the C:\Windows\System32\Spool\Printers so that the "Everyone" group has full rights to the Printers folder. I added the Domain Users group & gave it full permissions. I gave all groups all permissions to the printers (Print, Manage Printers, and Manage Documents). Still no luck.
• I set up the same scenario on another W2K3 box and had the same problem, so it's not an issue related to this particular server. I also set it up on another W2K Server box and it was OK. The permissions on the C:\...\Printers folders are identical (and the default).
How do I get the spool files to delete once the print job is done on the W2K3 boxes? Is there some subtle difference between W2K Server and W2K3 Server? Is this even something that I should be worried about?
TIA,
roshan