We are using spire to pdf and xls files.
The code was working for a long time without issues, but now it throws following error (seemingly at random times):
- Code: Select all
System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush, RectangleF layoutRectangle, StringFormat format)
at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush, PointF point, StringFormat format)
at spr?.?(Graphics A_0, spr? A_1, Boolean A_2)
at spr?.?(Graphics A_0, spr? A_1, Boolean A_2)
at spr?.?(String A_0, spr? A_1, String A_2, Boolean A_3)
at spr?.?(String[] A_0, String A_1)
at spr?.?(spr? A_0)
at spr?.?(Boolean A_0)
at spr?.?()
at spr?.?(PrintPageEventArgs A_0, PdfPageBase A_1, RectangleF A_2)
at spr?.?(PrintPageEventArgs A_0)
at spr?.?(Object A_0, PrintPageEventArgs A_1)
at System.Drawing.Printing.PrintDocument.OnPrintPage(PrintPageEventArgs e)
at System.Drawing.Printing.PrintDocument._OnPrintPage(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 spr?.?()
at Spire.Pdf.PdfDocument.Print()
or
- Code: Select all
System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush, RectangleF layoutRectangle, StringFormat format)
at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush, PointF point, StringFormat format)
at spr?.?(Graphics A_0, spr? A_1, Boolean A_2, Boolean A_3)
at spr?.?(Graphics A_0, spr? A_1, Boolean A_2, Boolean A_3)
at spr?.?(String A_0, spr? A_1, String A_2, Boolean A_3)
at spr?.?(String[] A_0, String A_1)
at spr?.?(spr? A_0)
at spr?.?()
at spr?.?(Boolean A_0)
at spr?.?(Graphics A_0, spr? A_1, spr? A_2)
at spr?.?(String[] A_0)
at spr?.?(spr? A_0)
at spr?.?()
at spr?.?(Boolean A_0)
at spr?.?(Graphics A_0, spr? A_1, spr? A_2)
at spr?.?(String[] A_0)
at spr?.?(spr? A_0)
at spr?.?()
at spr?.?(Boolean A_0)
at spr?.?(Graphics A_0, spr? A_1, spr? A_2)
at spr?.?(String[] A_0)
at spr?.?(spr? A_0)
at spr?.?()
at spr?.?(Boolean A_0)
at spr?.?(Graphics A_0, spr? A_1, spr? A_2, spr? A_3, Image A_4)
at spr?.?(PrintPageEventArgs A_0, PdfPageBase A_1, RectangleF A_2)
at spr?.?(PrintPageEventArgs A_0)
at spr?.?(Object A_0, PrintPageEventArgs A_1)
at System.Drawing.Printing.PrintDocument.OnPrintPage(PrintPageEventArgs e)
at System.Drawing.Printing.PrintDocument._OnPrintPage(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 Spire.Pdf.PdfDocument.Print()
We have tried to replicate it unsuccessfully and only the european production environment is affected (the load on this environment is significantly higher).
We have tried:
- updating the spire packages spire.xls and spire.pdf to the latest versions
- updating the spire package spire.xls and removing the spire.pdf package (as it doesn't seem to contain anything necesairy to make it work)
- removing both and using the lastest version of spire.office
all of these changes worked during testing, but made the error seem more frequent on the live environment.
The problem also does not lie with the documents printed as these have been tested extensively.
Is there any knowns issues when using printing under high load?
Kind regards,
Chris Brouwers