none
Print queue on Windows Server 2012 doesn't refresh to show jobs printed for several minutes RRS feed

  • Pergunta

  • We print hundreds of documents from a Robot on a Win 2012 server to a Corporate Print Queue. When printing from the server the job spools and we can observe it in the queue from a Windows 10 user workstation but the print queue utility on the server doesn't show the jobs for several minutes (5-15).

    Clicking refresh has no effect, you just have to wait until the queue decides to refresh.

    There is no traffic blocked between the Win 2012 server and the Print server itself.
    We observe no latency across the network, no retries and no dropped packets based on packet captures on both sides/servers.
    There are no error messages in the event logs of either server.
    There is no WAN optimization or other caching/compression type devices in play.
    The jobs spool just fine and we can observe them locally on Win 10 user machines in the Print server queue immediately.
    We are using the Canon Uni-flow driver and Canon reports no errors and point to some issue with Windows Print Queue Manager.

    sexta-feira, 8 de novembro de 2019 15:44

Todas as Respostas

  • Hi Donny,

    The queue view from a client machine are the locally rendered print jobs before they are copied to the print server PLUS any print jobs that have been copied to the print server.

    It sounds like the jobs have not been copied to the server yet.

    You can check the spooled jobs on the client machine in C:\Windows\system32\spool\server\SERVERNAME

    There should be some SPL and SHD files here when the Robot application is creating jobs.  Note, the SPL file is NOT a ShockWave file.

    Normally the time the jobs stays on the client machine before transfer to the server is milliseconds, it is hard to spot the transition.  I would start be reviewing the local storage for the print jobs on the client system.

    It's possible the Robot application is not properly releasing all resources to the job so the file is not sent immediately.

    Another route may be to force the print job rendering on the server rather than the client but that might put some CPU resource strain on the print server.

    Let us know what you see regarding the files on the client machine.

    Thanks


    Alan Morris formerly with Windows Printing Team

    domingo, 10 de novembro de 2019 22:48
    Usuário que responde
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    quinta-feira, 14 de novembro de 2019 01:40
    Moderador
  • Hi Alan

    The jobs queue immediately and are available to print from the printers attached to the print server. It's just not displaying on the queue manager window on the initiating server for anywhere form 5-15 minutes.


    -DonnyMcJr

    quinta-feira, 14 de novembro de 2019 03:13
  • Hi Eve

    We have a case open with Microsoft and they have asked us to run advanced traces - we expect to do that tomorrow and I'll share any results we receive from Microsoft. Canon (w use the Canon Uni flow driver) is also reviewing the issue as well.

    Thanks!@


    -DonnyMcJr

    quinta-feira, 14 de novembro de 2019 03:14
  • Hi,

    Thank you for your updating. If there is more questions or concerns, please feel free to post on the forum.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    quinta-feira, 14 de novembro de 2019 06:56
    Moderador
  • What is " queue manager window "?  Can you send a screenshot?

    Thanks


    Alan Morris formerly with Windows Printing Team

    quinta-feira, 14 de novembro de 2019 16:44
    Usuário que responde