Print Job Watcher could not be started.

Skip Navigation LinksHome  /  Support  /  Forums  /  DynamicPDF PrintManager for .NET (v4)  /  Print Job Watcher could not be started.

DynamicPDF PrintManager for .NET (v4) Forum

Ever since these big spooler security issues have been coming out we are seeing more of this occurring on customer systems.
I believe the stations have had Microsoft's Spooler Security "Fix" pushed out to them and it is giving errors.


Windows 10


File: DynamicPDF.Printing.NET4.x86.dll 
File description: "DynamicPDF PrintManager PE for .NET" 
Product version: 4.0.0 (Build 37436)


            ' Print using CETE Print Manager
            Using MyPrintJob As New Printing.PrintJob(sPrinterName, sFile)

               MyPrintJob.DocumentName = Path.GetFileNameWithoutExtension(sFile)
               MyPrintJob.PrintOptions.Color = False

            End Using


cete.DynamicPDF.Printing.PrintingException: Print Job Watcher could not be stated.  Failed to create job change handles.  Error code:1936
Posted by a ceTe Software moderator

We recommend updating to the latest version (v4.19). You can download latest product from NuGet (Package ID: ceTe.DynamicPDF.Printing.NET) or from our website here.

Error code 1936 indicates that, remote connections to the Print Spooler are blocked by a policy set on your machine. This is returned by the spooler and PrintManger is passing on the error it received from the spooler while creating the PrintJob.

ceTe Software Support Team

All times are US Eastern Standard time. The time now is 5:35 PM.