Soumen
Reputable Poster
We have noticed that sometimes when a job is set for print immediate and if the remote print server has any isuses or is not responding the job will wait in processing state. On the Windows Enterprise server when we check the process id of the job and analyze the wait chain - it seems to be waiting on spoolsvr.exe.
If we kill the spool service on the entrprise server, the job finishes fine. Also we direct the default printer to a dummy (let's say Eone Default Printer) the job completes normally. It almost seems like the job is waiting for an acknoledgement from the print server before finishing.
My question is this a normal behaviour? or are there any ways we can avoid having the job wait or keep processing incase there are issues with the print server.
------------------------------------------
E9.2, 9.2.4.4
Windows 2016 Server, WebLogic 12c
SQL Server 2016
If we kill the spool service on the entrprise server, the job finishes fine. Also we direct the default printer to a dummy (let's say Eone Default Printer) the job completes normally. It almost seems like the job is waiting for an acknoledgement from the print server before finishing.
My question is this a normal behaviour? or are there any ways we can avoid having the job wait or keep processing incase there are issues with the print server.
------------------------------------------
E9.2, 9.2.4.4
Windows 2016 Server, WebLogic 12c
SQL Server 2016