How it is possible to configure a print queue so all jobs are printed in their submited order ? Thanks in advance. Nicolas Kempnich
How it is possible to configure a print queue so all jobs are printed in their submited order ? Thanks in advance. Nicolas Kempnich
1.Print job in queue gets port from next print job
Hi, this happens with printer connected to non-existent LPT1 port or TCP/IP port. 1) Send first print job, when calling StartDoc set DOCINFO lpszOutput to NULL, it sits in front of queue, no problem. 2) Send second print job, same as first job, it sits behind first job in queue, no problem. 3) Send third print job, but this time when calling StartDoc set DOCINFO lpszOutput to a file path. The file is new and it is on either ProgramData or a network drive which gives permission to create. The second print job magically gets the 3rd print jobs file in it's port, as shown when viewing the print queue. Futhermore, third print job hangs waiting for EndDoc.
2.Print Job Respools in the middle of a Large Print job
I have a particular user that cannot print a full print job from a PDF document. It is 220 pages, and is 15.1 MB when spooled. About half way through printing (thereabouts) it will pause, then restart the print job from the beginning. Any ideas?
3.Which print queue settings guarantee printing in FIFO order
I am trying to keep my sanity, and yet still be able to print effectively. My application must generate output to remote printer in a specific sequence. Thankfully, I can control which documents are printed and in what order, but have run afoul of the print spooler, which prints them out of sequence. In order of difficulty: is there a setting that guarantees a document printed at 1:00 will print after a document queued at 12:59:59, regardless of size or complexity? Is there a tool that will print documents (RTF, Word, HTML, MHTML, etc) in this way? Can you help? Stuart
4.an extra empty print job for each print job
Hi all, I have a remote site which has this very consistent problem: they can print on their WASP lable printer fine (it runs off of one of the PCs), but when trying to print to their local printer (an HP 2600n, through a TCP/IP port), they keep getting an extra print jobs: - which are empty - first one can't be deleted - first one stalls the PC's printer queue and the printer itself Restarting the spooler clears the problematic first empty print job, but my long suffering network users don't get access to windows services...so they end up rebooting their PC instead. The local printers can't be reached directly from the terminal server, as this would require investing in a VPN endpoint. They are not getting a windows 2008 server neither (to run a TS gateway). Since the label printer works fine, I reckon the HP2600n should too. HP support is coming up blank so far. Anybody else out there came across this empty print job problem? WFR, Wim Wauters UnisoftDesign.co.uk IT sysadmin
5.HP: deleted large print job stuck, blocking all other print jobs
Hello: I tried to delete a large print job (240 MB) after waiting 20 mins for it print. But it is now stuck in the delete phase and is blocking all other print jobs. PLEASE HELP!
6. deleted large print job stuck, blocking all other print jobs
Users browsing this forum: No registered users and 8 guest