Hi

We have been using eo.pdf for about 4-5 years without any issues.

Recently we have been experiencing a number of repeating failures which seem only resolved after recycling the application pool of IIS in which the PDF app is running.

Our customers create PDFs throughout the day via the "webpage to PDF" conversion.

We started to receive errors about every 2 days when the pdf functionality would fail on every build and stay failed until the app was manually restarted. No other part if the app seemed affected.

The stack traces look like this
Message: Conversion failed. Conversion failed. error code = 8. Parameter is not valid.
Stack trace: at EO.Pdf.HtmlToPdfException.b(Exception A_0) at EO.Internal.a3e.a(af5 A_0) at EO.Pdf.HtmlToPdfSession.RenderAsPDF(PdfDocument doc) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc, HtmlToPdfOptions options) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc) at KPIDash.Library.kpiDashboard.GenerateReport(HttpContext context, kpiUser loggedinUser, String FilterString) in...

After a restart all seems OK and every PDF builds just fine. We then changed our IIS settings to recycle the apppool every 8 hours (was 24hrs) and this seems to have reduced the problem to once per week. It still occurs and when it does all PDFs fail with "Conversion failed. error code = 8. Parameter is not valid." until a restart.

To my knowledge we have made no code changes in this area of our system for around 4 years
2 weeks ago we upgraded to the very latest version downloaded from your website.

Any ideas????

Thanks

Johnathan

Unfortunately we cant replicate this error. It seems to occur occasionally and then this is for every document PDFed until the app is restarted.

Please keep me posted on any changes that might help.

Sorry for the late reply I did not notice your post.

We have not experience the "restart problem" for about 3 weeks now since setting our app to recycle every 6 hours. We could experiment with increasing this again.


We are however experiencing a number of other failures. Our code is mainly unchanged for many years so these failures are confusing us.
For example
We are seeing this exception randomly every couple of days.

Can not create additional conversion task. All engines are busy.,
Stack Trace: at EO.Internal.alx.a(ax A_0, sq& A_1) at EO.Internal.o9..ctor(ax A_0, HtmlToPdfOptions A_1) at EO.Pdf.HtmlToPdfSession.a(HtmlToPdfOptions A_0) at EO.Pdf.HtmlToPdfSession..ctor(HtmlToPdfOptions A_0, Boolean A_1) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc, HtmlToPdfOptions options) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc) at


Or this 2-3 times per week.

Conversion failed. Browser engine failed to render page. Failed on command 1,
Stack Trace: at EO.Pdf.HtmlToPdfException.b(Exception A_0) at EO.Internal.a3e.a(af5 A_0) at EO.Pdf.HtmlToPdfSession.RenderAsPDF(PdfDocument doc) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc, HtmlToPdfOptions options) at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc) at KPIDash.Library.kpiDashboard.savePDFtoFile(HttpContext context, Guid userid, DateTime nowdate, String filterstring, Boolean landscape, String filename, Int32 _reportType)


In both cases the PDF is created in a separate thread.
In most cases triggering the same PDF again will normally build it just fine, so I fairly sure it does not relate the contents of the PDF.

Where do we get the new update with the more details exceptions?

Thanks.

Johnathan

Hi

Can you tell me what the default value of HtmlToPdf.MaxConcurrentTaskCount is please, so I know what value to change it to.

Thanks

Johnathan

Hi,

This is just to let you know that we have posted the new build that will contain more detailed information in the Exception's InnerException property. If it occurs again, please post the full stack trace from the exception object and we will be happy to look further.

Thanks!