Skip to main content
Question

IFS Cloud print agent Errors

  • February 25, 2026
  • 4 replies
  • 167 views
R
Hero (Partner)
Forum|alt.badge.img+13

We are having errors in print agent version 24.1.14

 

  1. The print job could not be printed due to an error in the rendering service
  2. [020] 2/23/2026 11:01:46 AM: Error Message: Initial DocumentProperties call failed. Error 6: The handle is invalid
    [020] 2/23/2026 11:01:46 AM: StackTrace of Error:    at PdfPrintingNet.PdfPrint.c6e27125e412036c9e584c2e46cb51f7a(Byte[] cdbbe4698d85f704fb0f22ac792e56f47, String c4f15c193045594e277ed09e85e293fa6, String cc035c63003d26e77cf79bef83c7e504f, String cceb9b617f6e8532922232e6cdc63cb66, PrinterSettings c4a5d3cfb3105d0d72441638a2332f4dc, PdfWatermark cd6cc9058a2d92015b56d02d2020b2023)
       at PdfPrintingNet.PdfPrint.Print(Byte[] pdfArray, String password, String printerJobName, Boolean renderBeforePrint)
       at IFSPrintAgent.RemoteJob.<perform>d__29.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at IFSPrintAgent.RemotePrintingNode.<>c__DisplayClass9_0.<<timer1_TickAsync>b__0>d.MoveNext()

Both of the errors seem to be random and there is no specific user, printer, report causing the error. Same print job is getting completed when tried multiple times. There are no any blocking AVs installed on the print agent server currently

Cheers | Ruchira

4 replies

N
Sidekick (Partner)
Forum|alt.badge.img+6
  • NuwanK
  • Sidekick (Partner)
  • March 31, 2026

​Hi @Ruchira did manage to resolve this issue ?

SaraCrank
Sidekick (Customer)
Forum|alt.badge.img+9
  • SaraCrank
  • Sidekick (Customer)
  • April 28, 2026

​@NuwanK ​@Ruchira Did either of you figure this out? I’m running into the same issue. 

N
Sidekick (Partner)
Forum|alt.badge.img+6
  • NuwanK
  • Sidekick (Partner)
  • April 28, 2026

In our case the error cleared after a planned VM change, which points to the Windows printing subsystem as the culprit rather than anything within the IFS application or report design.

  • This type of issue tends to be intermittent and can affect multiple reports and printers
  • It's usually tied to printer drivers or the Windows print spooler, not the report content itself
  • Windows printer handles can become invalid due to driver instability, third-party software or antivirus interference, or the spooler running low on resources under load
L
Hero (Partner)
Forum|alt.badge.img+9
  • Lingesan08
  • Hero (Partner)
  • April 28, 2026

Hi ​@Ruchira and ​@SaraCrank ,

We faced the same issue — the "Handle is invalid" error is a Windows print spooler problem, not IFS itself. The retry success confirms this.

Quick fixes to try:

  • Restart the Print Spooler service on the Print Agent server regularly
  • Reinstall printer drivers — corrupted or outdated drivers trigger this exact error
  • Check spooler memory under peak load — it can run out of handles under heavy print volume
  • Upgrade Print Agent if a newer version is available — some spooler race conditions were fixed in later releases

As ​@NuwanK mentioned, a VM change fixed it on their end — which confirms it's environmental on the Windows side rather than anything in IFS or your report design.

Focus on the Windows printing subsystem and you should get there. Good luck!

Thanks, Lingesan R
Terms & ConditionsAccessibility statement