We have not experience the "restart problem" for about 3 weeks now since setting our app to recycle every 6 hours. What happens if you try to convert again without restarting after you hit this error? Thanks! Sorry for the late reply I did not notice your post. However we have not been able to reproduce the other issue: having to restart the app in order to convert again. Hi, We have made changes on our end so that when you receive this error again, the exceptions' InnerException will contain more information about why it fails.
Pdf conversion failed 8 primo software code#
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. Parameter is not valid." until a restart. It still occurs and when it does all PDFs fail with "Conversion failed. 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.
Pdf conversion failed 8 primo software pdf#
After a restart all seems OK and every PDF builds just fine. Stack trace: at EO.(Exception A_0) at EO.(af5 A_0) at EO.(PdfDocument doc) at EO.(String url, PdfDocument doc, HtmlToPdfOptions options) at EO.(String url, PdfDocument doc) at (HttpContext context, kpiUser loggedinUser, String FilterString) in. The stack traces look like this Message: Conversion failed. No other part if the app seemed affected. 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. Our customers create PDFs throughout the day via the "webpage to PDF" conversion. 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. Hi We have been using eo.pdf for about 4-5 years without any issues.
0 kommentar(er)
