Troubleshooting

This troubleshooting guide for EvoPdf Chromium for .NET contains the necessary information to allow you identify and solve the possible issues that you might encounter during the usage of our software. If you cannot find the solution to your issue in this guide then you can contact our support at any time to help you solve the problem.

Most frequently this issue occurs when the resources are referenced by relative URLs in your HTML code and you don't pass the correct base URL parameter to converter method. As an alternative you can use only full URLs in your HTML page.

The LicenseKey property of each HtmlToPdfConverter and HtmlToImageConverter object must be set with the purchased license key. If you are confident that all these objects have this property properly set then make sure that you don't set a demo license key somewhere else in your code and the purchased license key is the only one used in your code.

The HtmlToPdfConverterConversionDelay property can be used to specify an additional period of time in seconds to wait for asynchronous content to be loaded before starting PDF rendering.

If you cannot estimate the time to entirely load the HTML page, then you can use the manual triggering mode to trigger the conversion directly from the code of the HTML page being converted. You can find more details about manual triggering mode in the Conversion Triggering Modes topic.

Some web pages might be designed using the lazy loading technique for images such that only the images visible in the viewport defined by the HtmlViewWidth and HtmlViewerHeight properties are loaded.

For HTML to PDF Converter the solution is to make sure the HtmlToPdfConverterLoadLazyImages property is set to 'true', which is the default value. Additionally, it is possible to choose between the browser’s internal mechanism and a custom algorithm for loading lazy images using the HtmlToPdfConverterLazyImagesLoadMode property. By default, the Browser mode is used by the converter.

For HTML to Image Converter the solution is to make sure the HtmlToImageConverterCaptureEntirePage property is set to 'true', which is the default value. Additionally, it is possible to choose between the browser’s internal mechanism and a custom algorithm for capturing the entire page using the HtmlToImageConverterCaptureEntirePageMode property. By default, the Browser mode is used by the converter.

This error indicates that the conversion ended unexpectedly for some reason, such as some required shared libraries not being available on the machine running the conversion. To find more details about the error, you can try manually running the loadhtml executable from the 'runtimes\win-x64\native' folder on Windows machines or from the 'runtimes\linux-x64\native' folder on Linux machines, using the command line.

Reference

Other Resources