One stuck file could not be deleted. It just hung and hung. I then restarted the spooler. The stuck file was then gone and I was able to successfully print. Thank you MSC!! Your Fix worked for me! While I've had this fix printing issues in the past, it didn't work for me. This time it was because of a simple paper jam. The printer didn't show any indication of a jam other than to simply be 'processing' a print job. This worked for me on Windows Server R2, but I chose only to delete today's files and nothing older.
I am not sure if this folder stores jobs if a printer has such functionality with its drivers. The exe files were tied to a couple of TMP files somehow. I skipped those and my printer queue was fixed. If you want to surgically delete only files associated with the problem printer's queue, then delete files with matching timestamps rather than the entire directory's contents. Home Windows General Windows How-tos. Clearing a Print Queue when Jobs won't Delete.
General Windows. Active Oldest Votes. I know that you said you set them up the same, but since they're not behaving the same, and you are asking for help, I'm going to assume that something has been overlooked, so please don't be offended if I mention something that you've already checked: One may be using Postscript, while the other may be using PCL One may always be sending fonts to the printer every time, while the other is allowing the printer to use fonts stored in memory on the printer One may have been set up to use less memory than the other for the print queue Something that was not clear from your question is whether the two servers are doing the printing, or if a client is printing to the printer via the two servers' print queues.
To be sure, you may want to try doing the following on the client machine : Delete both printer connections Uninstall the printer driver s for that printer Remove all remaining traces of the driver files from your client machine including removing the driver from your installation folder s , e.
Improve this answer. Thank you for the detailed response. However, both servers have the PCL 5e driver installed and both have the same font settings. Also, the server performs the printing, not the clients -- so that takes the client out of the equation. Actually, it might be interesting to see what happens when connecting a single client to both servers to see if the behavior is the same when using the two servers from the client. Also, Evan's registry comparison might also help track down the issue.
Using the same client to connect to both servers sees the same behavior I mentioned above. I have run into this when the client has set their printer driver preference, under advanced settings, to a higher dpi than the system default. Evan Anderson Evan Anderson k 18 18 gold badges silver badges bronze badges. I compared to reg entries for the two printers. DLL" Any ideas from these values? Here's what I've come up with.
There was no change after deleting the printer and it's drivers from the server and reloading. I even deleted the old port and recreated a new one. I have deleted printer and driver from several client test machine and had my group policy recreate the printers. This didn't seem to have any effect on the printing issue. Here's what I have found since the last post: Because I was remoting into the servers I'm trying to fix I didn't see the following message that was only displayed on the console.
This can be caused by you printer being turned off, the cable being unplugged, or being connected to a VPN, which will block you access to your local network" When this message is displayed on the servers console nothing from the print queue in question will print until the message is responded to. Once you respond to the message printing will resume. So now my question is how do I get this message to go away on its own or never be displayed in the first place.
I have over 50 printers, they run out of paper, toner, trays get left open and left off line all the time.
I don't want to have to respond to that message every time there's a printer problem. I just want the queue to resume sending to the printer when the printer brought back on line. Any thoughts? Been there, done that. Did anyone find an answer for this. We are having the same problem. I was having this problem for months and tried several different things.
It was happening multiple times a day. I haven't had to restart the spooler since 3 weeks. Hi I found that some of the drivers were 16bit and this caused printer spooler services to stop. I then went to print server properties, deleted any printers with drivers other than windows and up version, installed the latest drivers of the deleted printers and this has resolved my problem. We resolved the issue by doing a couple of things: 1. Therapeutic restarts of the spooler service on an interval shorter than the average amount of time between hangs.
Switching to MS print processor vs. Switching to MS drivers vs. Here's a synopsis of all the possible steps: 1. Remove the dependencies for the hpzpp38q. Configure Antivirus not to scan the extensions. BUD files b. Apply the latest spooler binaries by install Hotfixes.
0コメント