Hi,

I have a problem with EO.Pdf library that I cannot really resolve or even debug properly on my own. I will describe it as best I can and include all the information I managed to gather.
We are using EO.Pdf to convert HTML to PDFs using the following method:



This code has been running in our production servers for quite some time now (two years at least) and there were no obvious problems with it. Recently however we update the version of EO.Pdf from 19.2.91 to 22.1.94. Nothing else in our setup changed. It seemed to work fine in testing, but after deploying the version to production it turned out that images are no longer rendering properly. We managed to reproduce this behavior in our testing environments as well, but it never occurred in our dev environments. There is no exception of any kind either, the whole conversion passes, but simply doesn't render the images.

The dev environments are the following:
Windows 10 Enterprise, version 21H2, OS build 19044.2130 running on a physical machine
The testing environments where the bug reproduces are the following:
Windows Server 2019 Datacenter running on Amazon EC2

The images in question are like this:


The src is a valid link to a file that is accessible from the web (I tried using links to images on wikipedia)
Also worth noting that in the final PDF the alt is always rendered.
I tried opening the HTML file before the PDF conversion (the input file) in Chrome separately and in renders the images correctly.
If the src is not a link but instead a base64 image the image renders correctly.

I tried increasing the min timeout to 3 seconds, but that didn't change anything.

The license is correctly applied in production. We run a trial on testing environments. We also run a trial on dev environments. To reiterate, the bug happens on prod and testing but doesn't happen on dev, so it seems it's not related to the correct license.

I tried updating the license to the newest 22.2.49 but it didn't help at all.

Any help here would be greatly appreciated, because for now the only solution we have is to roll back the version upgrade to 19.2.91.

Thanks a lot

Hi.
I did the steps you mentioned above and when I generate the PDF from the EOPdfDemo app it renders the images. Our conversion process still doesn't work though, even when using the machine that has this EOPdfDemo app installed.

Hi,

Unfortunately it doesn't look like it's a permissions problem because if instead of using I use the images start to render (and the image links point to the same resource in the HTML and on the live website).
If it were a permissions issue I would expect the library to not be able to access the internet at all. Instead it looks like there is some problem in ConvertHtml that is not present in ConvertUrl.

As to the RDP access to the test environment, I don't even have access there, let alone giving anyone access to it. Company policies and such.

I could maybe run through all the version of EO from the one that worked and see which one breaks down. Would that info help you in any way?

Thanks a lot.

To answer on this question. What I mean by sayin I don't have RDP access to test environments is me personally. There are people in my organization who do and I asked them to perform this test.

As to the other part, like I say, it's not possible as far as I'm aware to let you RDP to our test environments for security and company policy reasons.
Is there maybe a debug or extended logging version of EO.Pdf that we could utilize? I could send you those logs afterwards and maybe try figuring something out that way?