Hi,

Please try to increase HtmlToPdf.Options.MinLoadWaitTime. When EO.Pdf converts a page, it first load that page into it's internal browser engine, then wait for a short period of time before the conversion actually starts. This wait time is controlled by HtmlToPdf.Options.MinLoadWaitTime. The purpose of this wait period is to give the script in your web page sometime to run. In your case, it appears that this wait period wasn't long enough and the conversion started earlier before your AJAX script has fetched all the data from your server. Increasing HtmlToPdf.Options.MinLoadWaitTime should solve this problem for you.

If you do not want to specify a fixed HtmlToPdf.Options.MinLoadWaitTime, you can use our manual trigger feature. The manual trigger allows you to explicitly tell the converter when to start conversion instead of just waiting for a specific amount of time. you can find more information on how to use manual trigger here:

http://www.essentialobjects.com/ViewDoc.aspx#manual_trigger


Please feel free to let us know if you still have any more questions.

Thanks!

Hi,

In that case you will want to troubleshoot the JavaScript in your page to make sure that it is indeed being called. You can use the debug console feature to add debug output:

http://www.essentialobjects.com/doc/4/htmltopdf/js.aspx

There is no such thing as "calling JavaScript function eopdf.convert() on page life cycle of OnLoadComplete". OnLoadComplete happens on the server side inside your web server and eopdf.convert is a client side JavaScript that is called on the client side by the browser. So these two are completely unrelated. Also you never "collect data in PdfDocument" either. You do whatever you do to get your HTML right and then pass the HTML to our converter. So anything you do you do it in your HTML.

Thanks!

Hi,

The time out is controlled by HtmlToPdf.Options.MaxLoadWaitTime. Note that the real time out value is based on MaxLoadWaitTime, but not the same value. There are a number of situations where you may receive timeout error. One situation is your HTML is too big, so it is unable to finish loading/conversion in time, another situation is it is waiting on the web server to serve the resource (for example, a dynamically generated image). Particularly, if you call ConvertUrl/ConvertHtml on the same web server then you can easily run into ASP.NET session lock issue. In that case you should use ASPXToPDF or MVCToPDF class instead.

You do not need to explicitly clean up with EO.Pdf if you use ASPXToPDF, MVCToPDF, or the static version of ConvertHtml/ConvertUrl. If you use HtmlToPdfSession object, then you will need to explicitly dispose that object.

Thanks!

Hi,

If you are only getting timeout on a single page, then it's almost certain the problem is related to that page. You will want to try to comment out the code in your page block by block to find out exactly what triggered it.

You can not configure HtmlToPdf.ConvertUrl time out directly. The only value you can change is HtmlToPdf.Options.MaxLoadWaitTime. The actual time out value is based on this value.

You can not use before render event to render watermark. This is because an HTML file will always have a solid background (the default is white, obviously you can use CSS to change to something else). You should be able to use after render event to render watermark though. You can also render watermark after the conversion is done. For example:



Hope this helps.

Thanks!

Hi Arun,

You will want to use the manual trigger feature for this:

http://www.essentialobjects.com/doc/4/htmltopdf/eo_js.aspx#manual_trigger

Thanks!

Hi,

The exact point of manual trigger is to disregard all the automatic waiting logics, including MaxLoadWaitTime. If you choose to use manual trigger but never actually call the trigger, then the conversion will time out. As such if you say you are going to call the manual trigger (by setting HtmlToPdf.Options.TriggerMode to Manual), then you must do what you say (calling eopdf.convert()).

If you are not sure why eopdf.convert is not called, you can use the debugger console feature to debug your JavaScript to find out:

http://www.essentialobjects.com/doc/4/htmltopdf/js.aspx

Thanks!

Hi Arun,

You definitely do not call eopdf.convert() from $(window).load. Doing so has absolutely no benefit.

The exact purpose of having you to call eopdf.convert() explicitly instead of automatically is so that you will ONLY call it when you are truly ready. For example, if you use AJAX call to load contents in your page, then you might not be ready UNTIL AFTER your AJAX calls are done. And because our converter would have no way of knowing when you have finished all your AJAX calls, the solution would be for you to use manual trigger and call eopdf.convert() AFTER you are done with your AJAX calls. The point is not just to make sure eopdf.convert() is called, but also only calls it when you are truly ready. We don't need you to tell us that your window's onload event has been fired. We can detect that automatically. So calling that from window.onload over the default automatic trigger would not solve any problems for you.

As previous replies have already pointed you, another option you can try is to increase MinLoadWaitTime. However this would not solve the problem of your AJAX calls might take longer than expected since whatever MinLoadWaitTime you set, it would always be a fixed value.

Thanks!

We are not sure how we can explain it better. $(window).load is for the initial load. But you are talking about AJAX calls. These are two different things. If you have no AJAX calls and everything in your page is ready on $(window).load then you do not need to do anything special. By default, our converter will wait for that before starting the conversion. If your page uses AJAX calls, the the converter will not know when you are done with those calls. That's when you may need manual trigger. This has everything to do with your AJAX calls and has NOTHING to do with $(window).load.



There is no fixed limit because it all depends on your system. You will need to reduce your file size if you keep running into problems.



You can only see JavaScript errors. Please see here for more details (look for "Debug Console" section):

http://www.essentialobjects.com/doc/4/htmltopdf/js.aspx

Thanks!

You are very welcome. Glad that you found a workaround. Please let us know if you still have any questions.

Thanks!

Hi Ranjeet,

We do not have any other suggestions except for:

1. Using manual trigger properly;
2. Use the JavaScript debug console feature to find out whether a JavaScript error has occurred when the conversion result is not correct;

Both points have already been suggested previously in this thread. You must follow those first. We don't work in "let's try this let's try that" and see which one sticks approach.

Thanks!