Share via

Are there any settings that will allow a print queue to resume if the data stream of a print job is stopped briefly??

MISAdmin 386 Reputation points
2022-03-21T15:57:10.46+00:00

I have a network shared print queue that occasionally gets stuck. The job inside in unable to be deleted and any job submitted afterwards is stopped. I can restart the Print Spooler and the stuck job will delete and the rest will continue.

I tracked this down a wireless client that must drop it's connection for a second or so causing the data stream to the queue to stop and not recover. I have various settings such as...

  • Enable bi-directional support unchecked
  • Spool print documents so program finishes printing faster - Start printing immediately
  • Print spooled documents first
  • Enabled advanced printing features

Is there another setting or do I need to modify my settings to allow the queuing job to resume when the connection recovers after a drop? I did a test printing directly via IP and it appears to recover. I unplugged the network cable and re-plugged.

Windows for business | Windows Server | User experience | Print jobs
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alan Morris 1,336 Reputation points
    2022-03-24T13:38:51.467+00:00

    Hi, this is the setting getting in your way.

    Printer properties / Advanced
    Start printing immediately.

    Change this to
    Start printing after last page spooled

    I have a feeling the name is different, sorry on my not Windows phone,

    If the job starts printing while still spooling, then client hangs, no other jobs can print.

    This will speed up printing since folks won't get stuck in the queue.

    We used this setting at Microsoft for the same reason you are looking for a solution, jobs that get stuck while spooling.

    Thanks

    1 person found this answer helpful.
    0 comments
  2. Limitless Technology 39,931 Reputation points
    2022-03-23T18:57:54.723+00:00

    Hello @MISAdmin

    It would be recommeded to check with the printer manufacturer forums or support, as usually there are firmware or settings that allows to control this.

    From Windows perspective, you can try to control the printer connection timeout in the failing client so the printer will stop listening to the connection and the job will be deleted.

    The value to modify is LprAckTimeout, the value is expressed in seconds, default is 180

    To change it, locate
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitor\

    Add key
    Standard TCP/IP Port
    Add String Value; value name=Driver; value data=tcpmon.dll

    under Standard TCP/IP Port
    Add Key, name it "Ports"

    Add three DWORD values inside Ports, data in decimal:

    LprAckTimeout value data= 180
    StatusUpdateEnabled value data= 1
    StatusUpdateInterval value data= 10

    stop and start spooler

    Hope this helps with your query,

    -----------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments
  3. MISAdmin 386 Reputation points
    2022-03-24T11:15:59.54+00:00

    Hi. Thank you for the info. We have "Monitors" with an "s", I'm sure you must have meant that. Those 3 entries inside PORT already exist here.

    0 comments
  4. MISAdmin 386 Reputation points
    2022-03-24T14:25:31.41+00:00

    Thanks Alan. I made this change on my test printer and unplugging / re-plugging the network cable to simulate the drop did NOT cause the job to get stuck. Now, I made the change on the queues that were getting stuck. We'll see how it works under their real wireless environment in the warehouse. Thank you... I have hope.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.