Spooling a large print (5690 pages) with Crytal Reports fails on page 1700

[Former Member]

If we export to PDF and print from there, the print succeeds, but going directly to the printer fails every time after spooling 1700 pages, with the error below, which seems to indicate that there is a limit on either the time taken or the size of the spooled print. How can I increase that limit?

Exception Information System.Threading.ThreadAbortException: Thread was being aborted. at System.Drawing.SafeNativeMethods.ResetDC(HandleRef hDC, HandleRef lpDevMode) at System.Drawing.Printing.StandardPrintController.OnStartPage(PrintDocument document, PrintPageEventArgs e) at System.Drawing.Printing.PrintController.PrintLoop(PrintDocument document) at System.Drawing.Printing.PrintController.Print(PrintDocument document) at System.Drawing.Printing.PrintDocument.Print() at CrystalDecisions.CrystalReports.Engine.FormatEngine.PrintToPrinter(Int32 nCopies, Boolean collated, Int32 startPageN, Int32 endPageN) at CrystalDecisions.CrystalReports.Engine.ReportDocument.PrintToPrinter(Int32 nCopies, Boolean collated, Int32 startPageN, Int32 endPageN) at Karmak.BusinessServices.PM.Reporting.Process.DocumentPrinter.PrintDocument(ReportDocument document, ReportPrinterSettings settings) at Karmak.BusinessServices.PM.Reporting.Process.ReportJob.Print() Call Stack at Karmak.Utilities.ExceptionManager.Publish(Exception exception, NameValueCollection additionalInfo) at Karmak.BusinessServices.PM.Reporting.Process.ReportJob.Print() at Karmak.Services.PrintManager.Server.PrintJobSerializer.RunJob(Object state) at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj) 2018-08-31 13:49:04.006 Debug JOBJob: ef345607-a9c6-49cd-8b4e-c99ff8365bc1, Report: 1096, Printer: 1136 complete with status -1 - This job was killed as a long running job 2018-08-31 13:49:04.006 LogAlways QUEUE_JOB_KILLED:JOBJob: ef345607-a9c6-49cd-8b4e-c99ff8365bc1, Report: 1096, Printer: 1136 - 'R1096A1C10073P5759:S1132P1136T2130' by User '-1'

[former_member11696 · Accepted solution]

Hi Josh,

What version of Crystal reports are you using?

What printer are you using?

Are you printing in an application you wrote using the .NET SDK or from a third party app you are using?

If an app what version of the SDK is installed, look in Programs and Features for SAP runtime.

Don

[Former Member · Accepted solution]

Hey Don,

Thanks for the reply. We are using a .NET app. Over the weekend, a coworker of mine discovered a timeout further upstream on the print that was causing this issue. Turns out this wasn't a crystal issue at all. Thanks for trying to help, though!